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. While 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, XML 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 nowdays.

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.

While 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, XML 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 nowdays.

Q2	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.
The three IDE’s evaluated are Visual Studio, PyCharm and IDEA for many sites these are the most used and common on 2025. Visual Studio: Is powerfull but potentially overwhelming for new users due to the complexity. It is suits well for focus primarely on Microsoft tehcnology (.NET, C#). Pros: Comes with a wide range of features such as debugging, testing and project management. Support for all MS ecosystem and many othe languages Can be used to work in team Powerfull debugging Large community The community edition is free Cons: Can be heavy on system resources slower performance on old machines Difficult learning curve Limited cross-platform development PyCharm: Great choice for beginner especially for learning Python. The dedicated features make learning process smoother but has an high demand in resources. 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: Suitable for beginners, but not optimal, is primarely focused on Java and Android development. The the limitations of the free version and the IDE's overall complexity might make it less ideal for beginners and pricey. Pros: Exellent support for Java and Android Intelligent code assistance Powerfull debugging Cross-platform compatible Cons: Full edition is expensive Resources intensive> Steep learning curve Free version has huge limitations

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.

The three IDE’s evaluated are Visual Studio, PyCharm and IDEA for many sites these are the most used and common on 2025.

Visual Studio: Is powerfull but potentially overwhelming for new users due to the complexity. It is suits well for focus primarely on Microsoft tehcnology (.NET, C#).

Pros:

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

Cons:

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

PyCharm: Great choice for beginner especially for learning Python. The dedicated features make learning process smoother but has an high demand in resources.

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: Suitable for beginners, but not optimal, is primarely focused on Java and Android development. The the limitations of the free version and the IDE's overall complexity might make it less ideal for beginners and pricey.

Pros:

Exellent support for Java and Android
Intelligent code assistance
Powerfull debugging
Cross-platform compatible

Cons:

Full edition is expensive
Resources 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, specifically, the adherence to web standards
The beginning of of the web browsers were characterized by competition and a lak of standards. The browswer war between Netscape and internet explorer 1990-2000 led to the implementation of proprietary features. Web developers had to face browsers specific code and websites had to be coded in multiple versions leading to inconsistent user experience, long developing times and raising 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.

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

The beginning of of the web browsers were characterized by competition and a lak of standards. The browswer war between Netscape and internet explorer 1990-2000 led to the implementation of proprietary features. Web developers had to face browsers specific code and websites had to be coded in multiple versions leading to inconsistent user experience, long developing times and raising 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: Ensure that the site work 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 usually a visual no code approach to test the automation could be used. This method allows testers to create and manage tests using visual building blocks. Thus simplifies the testing process, improve collaboration with team members and ensure reliable user experience on all platforms.

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: Ensure that the site work 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 usually a visual no code approach to test the automation could be used. This method allows testers to create and manage tests using visual building blocks. Thus simplifies the testing process, improve collaboration with team members and ensure reliable user experience on all platforms.

Q5	What are the endorsed requirements of accessibility for all NT Government webpages?
Northern Territory Government uses as requirement for their websites The WCAG 2.0 (Web Content Accessibilityy Giudelines) and aiming for a level AA compliance for all the websites and web content.

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.
I would use a folder and subfolder structure, keeping images, fonts, and stylesheet in separate folders and in the same order used for the website in construction WEBSITE/ (as main) └── CSS/ └── Images/ └── Fonts/ This shoul help to keep everything in clean and organised, make it easier to manage.