| 1. Describe the difference between an XML Sitemap and a HTML Sitemap. List the benefits and disadvantages of using each. |
The difference between an XML Sitemap and a HTML Sitemap are that XML sitemaps are made for search engines bots to read the root directory, while HTML sitemaps are used more for human interaction and use a visible link. XML sitemaps help search engines discover pages, while HTML sitemaps help users navigate, but both can be cumbersome to maintain and neither guarantees indexing or strong SEO gains. |
| 2. Evaluate three IDE’s (Integrated development environments) and provide a brief summary on the positive and negative aspects of each. Also, in your own words include how it would suit an entry level trainee code developer. |
Visual Studio Code is a free, flexible, and beginner-friendly IDE that supports many languages and extensions, though it can use a lot of RAM on larger projects and may feel less complete without add-ons. IntelliJ IDEA is a powerful premium IDE with excellent code completion, refactoring, and Java support, but it can be heavy, slow at times, and a little confusing for new users because of its shortcuts and complexity. PyCharm is a strong choice for Python development with smart coding help, debugging, and data science support, but it can also take up significant memory and disk space, so it suits trainees best when they are focused on Python and want guided, professional tools. |
| 3. Provide a brief history on web browser development and the issues encountered by web developers, specifically, the adherence to web standards. |
Web browsers have evolved significantly since their inception. Early browsers like Mosaic and Netscape Navigator were limited in their capabilities and often incompatible with each other. This led to the need for web standards to ensure consistency and compatibility across different platforms and devices. The World Wide Web Consortium (W3C) was established to develop these standards, but inconsistent implementation has caused challenges for developers who must account for various browser quirks. |
| 4. What are website testing methodologies? Your answer MUST cover browser compatibility, and website functionality. |
Website testing methodologies are the different ways testers check that a website works properly and provides a good user experience. Browser compatibility testing makes sure the site looks and behaves correctly across browsers such as Chrome, Firefox, Safari, and Edge. Functionality testing checks that important features like links, forms, buttons, and menus work as expected. These methods help find issues before users do and reduce the chance of broken pages or failed interactions. Together, they make a website more reliable, consistent, and easier to use. |
| 5. What are the endorsed requirements of accessibility for all NT Government webpages? |
Compliance standards include adherence to WCAG 2.0 Level AA. Websites must support all users regardless of physical or environmental limitations, use plain English, deliver clear and helpful error messages, remain readable in common browsers, provide text-based alternatives for multimedia, and comply with metadata standards such as AGLS for discoverability. |
| 6. How do you think it’s best to organise all the assets used for a specific webpage? Think locally on your computer AND within the root folder of the website. |
Keeping website files organised makes them easier to manage and update later. On your computer, put the HTML file in the main project folder and keep things like CSS, JavaScript, images, and fonts in separate folders. In the website root folder, the HTML files should stay at the top level, with all other assets sorted into their own folders so everything is neat and simple to find. |