An XML Sitemap is a file designed for search engine 'crawlers' to take URLs and sometimes metadata from your site and use it to index your site. The benfits of this are that it ensures that important pages are found, and it scales well, which is ideal for large websites with lots of URLs. The disadvantages of this are that it requires maintenance to make sure it is up to date, or it could mislead crawlers. Another disadvantage is that it does not gaurantee indexing, it only suggests URLs; the search engines still decide what to index.

A HTML Sitemap is a regular web page that conatins links to key pages on your site. This is designed for human visitors and looks like a structured directory of your content. The benifts of using this are that it improves user navigation and it is simple to create. The disadvantages of using this is that it has limited scalability, which becomes obvious for larger sites. It also is less detailed compared to XML, as it has no metadata like update frequency or priority.

The first IDE is VSC (Visual Studio Code) and it is very well known and free. It has a beginner friendly UI and an integrated terminal. It has a huge extension marketplace, adding coding language support for many different types. The downsides is that it isn't a full IDE out of the box. You must download extension for the different languages, frameworks and other such things.

The second IDE is IntelliJ IDEA. This IDE is mainly associated with Java and other similar languages. There is a free version (community) and a paid version (ultimate). The postives of using this are that it has integrated testing tools and code quailty tools. It also has strong support for web stacks and languages like Spring and Jakarta EE. The negatives are that it is heavy on resources compared to other IDE's. It also has a steep learning curve due to the many features and shortcuts.

The third IDE is Microsoft Visual Studio. This IDE is designed for complex, large-scale .NET and C++ projects. Compared to VSC which a lightweight, beginner friendly IDE, Visual Studio is a full IDE. This means it uses a lot of resources, it is primarily for Windows, and has free and premium versions. This IDE has deep .NET and C++ suppport and has live unit testing and an excellent debugger. The downsides of this are that is is Windows focused with limited macOS support. It is also very complex and resource heavy.

Overall I would recommend VSC (Visual Studio Code) as it has a beginner friendly interface, is cross platform and free, and has support for practically any language you need. You can start simple and gradually add things as you learn.

The first web browser, WorldWideWeb, was created by Tim Berners-Lee in 1990. Another web browser, Mosaic, was developed in 1993 and intorduced images inline with text and popularised the graphical web. As the web was new, most pages were simple HTML with no standards. This lack of standards meant developers relied on whatever each browser supported.

Problems that developers faced were non standard HTML, CSS, and JavaScript implementations. “Best viewed in Internet Explorer/Netscape” banners became common because pages often broke in competing browsers. CSS support was also inconsistent, and JavaScript behaved differently depending on the engine.

The W3C (World Wide Web Consortium) pushed standardized HTML, CSS, and XML-based approaches. This meant browsers were now adhering to standards, making developers lives easier.

Some website testing methodologies are functionality testing. This testing ensure that forms work with no errors, navigation is linked and displayed correctly, any interactive elements like sliders, dropdowns and searchbars work correctly.

Another method is browser compatability testing. This ensure the website functions correctly across different browsers. Typcial browsers that are tested include Chrome. Firefox, Edge, Safari and mobile browsers. Factors tested are HTML and CSS rendering, media compatability and feature support.

The Northern Territory Government has endorsed the World Wide Web Consortium's Web Content Accessibility Guidelines (WCAG 2.0). They are working towards making all their websites and web content meet WCAG 2.0 Level AA compliance.

The best way to organise all of the assets used for a webpage is to create a folder for each section, for example, a project folder which is the root folder of the project. This includes all of the other files and folders.

HTML files are all your files that end with .HTML. These shouldn't be in a sub folder and should be put directly into the root folder. This allows you to be able to see the files easier and makes the paths to recsources the same.

The CSS folder is where all of your .CSS files go. All CSS files will go into an external stylesheet which will be be put into this CSS folder. You would need at least one stylesheet named main.css or style.css.