| Question | Answer |
|---|---|
| Question 1: Describe the difference between an XML Sitemap and a HTML Sitemap. List the benefits and disadvantages of using each. | XML site maps are designed for web crawlers, this allows better search engine optiminzation while being unfriendly for humans users. HTML site maps are designed for humans and are often optimixed with user experience, allowing people to search your website, but it does not allow greater search engine optiminzation. |
| Question 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 great IDE as it is user friendly and offers a lot of extensions for users. Its very well suited for beginners but may lack some advanced features for more advanced programmers Thonny is a very simple IDE and offers a step by step debugger which can be extremely useful. Same as visual studio code, its simplicity restricts it. It also focuses mainly on python and may not be useful if you want to use multiple languages. Pycharm is a great IDE filled with exhaustive libararies and features to be used, it also mostly focuses python so can be limiting. It is also resourse intensive. |
| Question 3: Provide a brief history on web browser development and the issues encountered by web developers, specifically, the adherence to web standards. | The world wide web browser was invented by Berners-Lee in 1990, it was later known as nexus,
during this time other browser such as mosaic appeared helping popularise the web. In the late 90s
microsoft found themselves in a war with netscape over browsers, this help accelerate advancements in
the area, although due to may parties trying to advance a lot of uncomatibility issues. During the 2000s
organisations began to advocated for better web standards, this helped lead to the formatio of the world
wide web consortium who helped define standards for HTML and java and browser soon adopted these standards. Over these years, web developers faced a lot of issues as the web advanced, in the early years browser compatibility was harder to come by and a lot of experimental code led to a lot of complexities. Older browsers can be difficult to maintain and update due to this. A lot of web developers would struggle to keep up with the rapid changes over these years, needing to stay up to date with standards and be able in implement them. This proved challenging as assessbility and other standards came into effect, meaning more consideration and effort was required. |
| Question 4: What are website testing methodologies? Your answer MUST cover browser compatibility, and website functionality. | Website testing methodologies are a range of processes to make sure a website funtions as intended across platforms. Browser compatibility is used to ensure a website works across different browsers. This can include testing the website on different browsers, devices, OS. Website functionality focuses on making sure the websites features work as intended. This can include performace testing for loading speed and resonsiveness, testing funtionality to test if interactive elements work properly. |
| Question 5: What are the endorsed requirements of accessibility for all NT Government webpages? | The NT government has endorsed he world wide web consortiums web content accessibility guidelines (WCAG 2.0) The WCAG has set guidelines to help accessibility in relation to web content. |
| Question 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. | It is best practice to keep both your local files and remote files stored in the same way. Start with a main folder, then add subdirectories for types of assets. (images, html, css, ect). Depending on the scope of your project it may be useful to add more subdirectories and manage your files that way. |