Questions and Answers

Question Answer

Q1. Describe the difference between an XML Sitemap and a HTML Sitemap. List the benefits and disadvantages of using each.

An XML sitemap is mainly made for search engines. It lists the important URLs on a website so search engines such as Google can find and crawl the pages easier. It can also include extra information such as when a page was last updated.

Benefits: Helps search engines find important pages, can include extra information about URLs, images and videos, and is useful for larger websites. Disadvantages: Normal users do not really use it to navigate a website and it can be harder to create and maintain. An HTML sitemap is a normal webpage that shows links to the main pages of a website. It is mainly made to help users understand the website structure and find pages.

Benefits: Easy for users to read and use, gives users another way to find pages and can make a large website easier to navigate. Disadvantages: It has to be updated when pages are added, removed or renamed and it does not provide search engines with as much sitemap information as XML can.

Q2. Evaluate three IDEs and explain the positive and negative parts of each and how they suit an entry level trainee developer.

Visual Studio Code: It is free, easy to customise and supports HTML, CSS and JavaScript. It has extensions, code suggestions, debugging and a built-in terminal. Too many extensions can make it confusing. I think it suits a beginner well because it is easy to start with.

Notepad++: It is free, lightweight and simple to use. It has syntax highlighting which makes code easier to read. It has fewer built-in development tools than a full IDE. I think it is good for a beginner learning basic HTML and CSS.

WebStorm: It has smart code completion, debugging, error checking and support for web development tools. It has a lot more features to learn and can feel more complicated. I would start with something simpler like VS Code first.

Q3. Provide a brief history on web browser development and issues with web standards.

Web browsers started as simple programs used to display basic web pages. As the web became more popular, browsers such as Netscape Navigator and Internet Explorer competed with each other. This became known as the browser wars. One problem was that browsers did not always support HTML, CSS and JavaScript in the same way. The W3C was created in 1994 to help develop common web standards. Modern browsers are more consistent now, but websites still need to be tested across different browsers and devices.

Q4. What are website testing methodologies?

Website testing methodologies are different ways of checking that a website works properly before and after it is published. Browser compatibility testing means testing the site in browsers such as Chrome, Edge, Firefox and Safari. Functionality testing checks links, buttons, forms, images and other features. Other testing can include accessibility, usability and performance testing.

Q5. What are the endorsed requirements of accessibility for all NT Government webpages?

The NT Government has endorsed the W3C Web Content Accessibility Guidelines and aims for websites and web content to meet Level AA compliance. This includes things such as alternative text for images, keyboard and screen reader access, readable text, good colour contrast and clear navigation. Content should also use plain English and appropriate webpage markup.

Q6. How do you think it is best to organise all the assets used for a specific webpage?

I think the best way is to keep everything in one main project folder and separate the different file types into their own folders. I would have the HTML pages, a CSS folder for stylesheets, an images folder for pictures and a scripts folder if JavaScript is being used. I would keep the same folder structure on my computer and on the web server so links and file paths do not break.