Assessment

XML is an older concept than HTML and is primarily based around how data is catalogued on a computer and has multiple uses. In Effect, XML would be a bit like using a Linux OS in that there are no hard-coded boundaries in the use of your tools/files other than what you set yourself.

HTML on the other hand, is a language solely designed for the design of websites. The most notable different between XML and HTML is that the latter has a well-defined and rigid rule set that a web-designer must follow, in particular the ‘tags’ system.

1st: Atom: Probably the most lightweight editor out there, it starts with a bare-bones UI but countless ‘plug-ins’ can be added as needed which means that a user has a easy learning curve. However, the lack of features like a de-bugger means it is not suited for larger projects.

2nd: Sublime: Similar to “Atom” in appearance and function, one of the most notable features is that various functions and extensions can be disabled as needed which will help performance on slower computers as well as keep new users from feeling overwhelmed.

3rd: PyCharm: A proper IDE in terms of providing the full support of systems like de-buggers and analysers. PyCharm, in comparison to Atom and Sublime is better suited for much larger projects where repeat coding and other tedious tasks can be delegated. However, PyCharm is a very large program, and its constant analysing may slow down a computer.

While the internet officially came into existence in 1982, its actual use was heavily limited by the lack of tools for the wider public to make easy use of. It was not until 1993 that the ‘World Wide Web’ was made available and with it, the concept of a ‘web-page’.

From there on though, two major companies in the form of Microsoft and NetScape both tried to out-do each other with their own separate programming language, causing considerable strain and confusion on web-developers.

This continued until 1998 when a neutral party initiated the ‘web standards project’ that convinced the major companies into standardization.

Websites created from HTML documents can become vast edifices in which the smallest of details down to a single dot or slash will go by unnoticed. Two websites that greatly help in catching these small errors are: “W3C Markup Validation Service”: https://validator.w3.org/ and “Can I use”: https://caniuse.com/

“Validator” is very good for pointing out problems in your code for functionality while “can I use” is good for learning what attributes/CSS can be read by which browser.

As part of NT government law, a website must be functional for people who may have a wide-range of disabilities. Most notably, these disabilities would be visual impairments such as colour-blindness or outright blindness, or deafness.

A website can be made functional for these people by having spoken audio for the blind and subtitles for the deaf.

Have your under-construction website in its own folder. Within that folder, see to it that there is a folder for the images. As for the HTML documents, have them in progression from the main page to its subpages before finishing the list with the FTS file and CSS file.