Questions and Answers

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

An HTML sitemap was created as a navigation tool for humans convenience to assist in navigating through websites by displaying links graphically on a browser. Created from HTML the “language of the web”, allowing for text-based content in user-friendly manner. Whereas, an XML sitemap is not designed for humans but for search engine crawlers. With it’s primary purpose to allow search engines to discover and index web pages and also enable data storing and interchange between computer systems including databases, websites and, third-party applications.

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: Provides fast performance and a lightweight, customizable and extensible environment with the intergration of github support and a user-friendly interface. However, These benefits are offset by the fact that this IDE necessitates manual setup for debuggers, compilers, and language-specific functionality. It also relies on basic plugins for debugging, syntax highlighting, and IntelliSense. VSCODE is a free easy to download IDE, it allows new users to learn the basics of how plugins work, with HTML, CSS and Javascript.

Eclipse: Offers an integrated development environment (IDE) for writing computer programmes in Python, PERL, Java, C/C++, and Ruby, among other languages. It was, however, mitigated by its complex debugging process, especially for beginners, and its high memory utilisation, which could lead to system slowdown and subpar performance. For an entry-level developer looking to start studying more complex coding languages, Eclipse would be ideal.

IntelliJ IDEA: With tools for renaming, extracting methods, and optimising imports, developers may write error-free code rapidly and perform thorough refactoring. This IDE also features a plugin ecosystem to support additional languages, frameworks, and tools. The drawback of this IDE, however, is that it isn't as cost-effective as other IDEs because sophisticated capabilities like language injectors, AI support, live templates, and many more demand payment from the user. Although using IntelliJ IDEA requires paying for certain capabilities in order to get the most out of it, an entry level coder would discover that this IDE is suitable for them and that using the paid features is easy.

Provide a brief history on web browser development and the issues encountered by web developers, specifically, the adherence to web standards.

British scientist Tim Berner-Lee created the World Wide Web (WWW), the first web browser, in 1989 while he was employed at CERN. The main motivation for the development and design of the web was the need for automatic information interchange among scientists at universities and research facilities around the globe. Even though Berners-Lee invented the World Wide Web, Mosaic was the first web browser to be made available to the general public and gain widespread recognition among internet users in 1993. Because browsers did not support early web standards fully, there were problems with inappropriate HTML, CSS, and JavaScript rendering. Developers had to use workarounds or browser-specific code, which led to fragmentation. Cross-browser compatibility has increased with the introduction of standards like HTML5 and CSS3, as well as JavaScript advancements (through ECMAScript standards). However, comprehensive and consistent implementation of standards by all browsers remains a difficulty.

What are website testing methodologies? Your answer MUST cover browser compatibility, and website functionality.

Website testing methodologies are essential for ascertaining whether a website functions appropriately from the user's perspective. It is imperative to do browser compatibility testing to ensure that the website operates correctly across a range of browsers. This can be done automatically using technologies like BrowserStack and LambdaTest, which replicate how the website works across many browsers and devices, or manually by testers going through the website in multiple browsers. Functionality testing confirms that all technical and business criteria are met by the website. This can be accomplished manually by setting up particular test scenarios, including inputting false data or abusing functions, and seeing how the website reacts. These tests can also be carried out automatically by programmes like Selenium or Robot Framework, guaranteeing that the website functions as intended in the absence of human participation.

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

The Web Content Accessibility Guidelines (WCAG) 2.2 includes a broad range of suggestions for improving the accessibility of Web information. The guidelines aim to make content accessible to people with varying diabilities including but not limited to blindness, deafness, hearing loss, impaired movement, photosensitivity, some will accommodate for learning disabilities and cognitive limitations, yet it won't address of all the needs of users who have certain limitations. The accessibility of web content on PCs, laptops, tablets, and mobile devices is covered by these rules. Additionally, adhering to these rules will frequently improve the overall usability of Web content for users.

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.

The best way to keep your asset list virtually modest is to organise your files inside the VSCODE. For example, in my case, I have a main folder called "web0" that contains sub-folders named after the assets within. For example, my css files are all in a folder called "css," and my website's images are all in a folder called "images." To make it easier to access the website, I also have a link to it on a different server.