Rhonda's Recipes

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

HTML Sitemaps are created for human visitors. They are coded using HTML markup and displayed as a webpage with clickable links. The advantage of HTML sitemaps is that they improve user experience and site navigation and only require basic HTML skills. However, they don't directly assist with SEO and search index.

XML Sitemaps are designed for search engines and use XML markup, making them machine-readable. Their primary benefit is optimizing search indexing by guiding crawlers, and they can be automatically created and updated using CMS plugins. However, they are not visible to website visitors and require XML skills for manual construction.

Websites should use both HTML and XML to be fully functional nowadays.

Q2 Evaluate three IDE’s... Also, in your own words include how it would suit an entry level trainee code developer.

The three IDE’s evaluated are Visual Studio, PyCharm, and IntelliJ IDEA — many sites list these as the most common in 2025.

Visual Studio

Pros:

  • Comes with a wide range of features such as debugging, testing, and project management.
  • Support for all MS ecosystem and many other languages.
  • Can be used to work in teams.
  • Powerful debugging.
  • Large community.
  • The community edition is free.

Cons:

  • Can be heavy on system resources and slower on old machines.
  • Difficult learning curve.
  • Limited cross-platform development.

PyCharm

Pros:

  • Designed for Python, includes intelligent code completion, debugging, and Python-specific tools.
  • User-friendly and intuitive interface.
  • Smart code analysis.
  • Good community support.

Cons:

  • Not versatile, focused on Python.
  • Resource-intensive.
  • Autocomplete could slow learning progress.

IntelliJ IDEA

Pros:

  • Excellent support for Java and Android.
  • Intelligent code assistance.
  • Powerful debugging.
  • Cross-platform compatible.

Cons:

  • Full edition is expensive.
  • Resource-intensive.
  • Steep learning curve.
  • Free version has huge limitations.
Q3 Provide a brief history on web browser development and the issues encountered by web developers...

The beginning of web browsers was characterized by competition and a lack of standards. The browser war between Netscape and Internet Explorer (1990–2000) led to the implementation of proprietary features.

Web developers had to face browser-specific code, and websites had to be coded in multiple versions, leading to inconsistent user experiences, long development times, and rising costs.

The World Wide Web Consortium (W3C) pushed for the application of standards to solve these issues. However, browser companies were reluctant and slow to adopt these standards (HTML, CSS, JavaScript). Since then, significant progress has been made, but developers today still need to test different browsers and versions.

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

Website testing methodologies are required to ensure that a site is performing the way it is supposed to and providing the same experience across every platform.

Website functionality testing encompasses several critical aspects:

  • Functionality: Having all the features such as forms, links, and interactive functionality work as expected.
  • Usability: Ensuring the website is user-friendly and intuitive.
  • Compatibility: Ensuring that the site works well on various browsers, devices, and operating systems.
  • Security: Identifying and fixing potential weaknesses to protect users' information.

One of the main issues of website testing is getting the same results on various technologies. Websites must function seamlessly on multiple browsers (like Chrome, Firefox, Safari), browser versions, operating systems, and devices, including mobile phones.

This can complicate testing, especially when script-based automated tests are used, which are usually very developer-dependent and may be hard to maintain.

To address these challenges, a visual no-code approach to test automation could be used. This method allows testers to create and manage tests using visual building blocks. This simplifies the testing process, improves collaboration with team members, and ensures a reliable user experience on all platforms.

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

The Northern Territory Government uses WCAG 2.0 (Web Content Accessibility Guidelines) and aims for a level AA compliance for all its websites and web content.

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

I would use a folder and subfolder structure, keeping images, fonts, and stylesheets in separate folders and in the same order used for the website in construction:

WEBSITE/
├── CSS/
├── Images/
└── Fonts/
                    

This should help keep everything clean and organized, making it easier to manage.