Describe the difference between an XML Sitemap and a HTML Sitemap. List the benefits and disadvantages of using each.
XML Sitemap
The XML sitemap is the machine-readable sitemap created in an Extensible Markup Language (XML) that contains information about all of your website URLs along with the metadata. It is designed for search engines, providing a machine-readable list of a website's URLs along with metadata like importance and update frequency. This aids in better indexing by search engines.
Benefits: Helps for efficient crawling and indexing; supports metadata for pages.
Disadvantages: This is not user-friendly as it is meant to be used by spiders.
HTML Sitemap
An HTML sitemap is a sitemap written in hypertext markup language that serves as a directory of links or table of contents for your website pages. It is a page with a general overview of all website pages that visitors can easily jump across your site from. The HTML Sitemap is meant for human users, offering a webpage with a directory of links to different parts of the site, enhancing navigation and user experience.
Benefits: Enhances User Experience and helps in website navigation to general users.
Disadvantages: This does not have direct influence on SEO.
Q2
Evaluate three IDEs (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
Positive: Lightweight and fast, providing a smooth coding experience. Negative: Can be overwhelming due to many features. Suitability: May be overwhelming for a trainee code developer.
Sublime Text
Positive: Known for its speed and efficiency; wide range of plugins. Negative: Not free, requires a license. Suitability: Not ideal for entry-level developers due to cost.
Atom
Positive: Open source and user-friendly; great for collaboration. Negative: Slower performance; uncertain future development. Suitability: Good for entry-level developers due to its user-friendly interface and no cost.
Q3
Provide a brief history on web browser development and the issues encountered by web developers, specifically, the adherence to web standards.
Web Browser History
The first web browser, called WorldWideWeb (later renamed Nexus), was created by Sir Tim Berners-Lee in 1989. This was made publicly available on 30 April 1993. The early web browser development saw rapid innovation but lacked standardization, leading to compatibility issues. Developers had to write different versions of their websites for compatibility with different web browsers. This was because there were no web standards set forth by the World Wide Web Consortium (W3C).
Q4
What are website testing methodologies? Your answer MUST cover browser compatibility, and website functionality.
Website Testing Methodologies
Website testing methodologies are a set of processes to ensure the website functions correctly and provides a consistent experience across different browsers and devices. Website testing methodologies are an important step for delivering a high-quality web product. Browser Compatibility Testing: Developers open the same website in different browsers, devices, etc., to check if the website can be accessed from any browser and website. Website Functionality: Developers verify that all the features/links in the website work as intended, such as database connections, form submissions, etc.
Q5
What are the endorsed requirements of accessibility for all NT Government webpages?
Accessibility Requirements
The Northern Territory Government has endorsed the World Wide Web Consortium's Web Content Accessibility Guidelines (WCAG 2.0).
Q6
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.
Organising Website Assets
The best way to organise the website assets is by creating a folder structure locally on the computer and within the root folder of the website based on the kinds of files they contain. The following folder structure can be followed:
Project (Root) Folder: Main Folder for the project, containing all files and folders.
HTML Files: Reside directly in the root folder; "index.html" is essential, alongside additional .html files.
CSS Folder: Dedicated to .css files, employing external stylesheets named "main.css" or "style.css."
Images Folder: Should contain image files (.jpg, .png, .gif, etc.), named "images" or "img."
JavaScript Folder: Should contain .js files, in a folder named "javascript" or "js."
