ALL ABOUT RECIPES

A1. XML sitemaps improve indexing, while HTML sitemaps help human visitors to assist with site navigation.

XML Sitemap

Benefits:

1. Faster, more thorough indexing.
2. Include information like the last modified date, update frequency, and relative importance of a page.
3. Can be submitted directly to tools like Google Search Console to speed up indexing.

Disadvantages:

1. Difficult for humans to read.
2. Creating one manually requires more technical expertise than a standard web page.
3. Requires technical setup or automated plugins to function.

HTML Sitemap

Benefits:

1. Better user experience & navigation.
2. Improves site navigation.

Disadvantages:

1. Harder to maintain manually.
2. Can become cluttered on large sites.
3. Often requires manual updates to keep links current.

A2. Below is an evaluation of three prominent Integrated Development Environments across modern production workflows:

VS Code

PROS:

1. Fast.
2. Massive plugin library.
3. Lightweight.

CONS:

1. Requires setup.
2. Not "smart" out of the box.

SUITABILITY:

It would suit an entry level trainee code developer because it’s simple to start and to grow skills with.

PyCharm

PROS:

1. Exceptional error catching.
2. Easy debugging.

CONS:

1. Heavy on RAM.
2. Interface is cluttered.

SUITABILITY:

It would suit an entry level trainee code developer because it corrects Python mistakes in real-time.

Thonny

PROS:

1. No complex menus or cluttered toolbars.
2. Provides a clear window showing you what values your variables hold at any given moment.

CONS:

1. It is built strictly for Python.
2. Not suitable for large-scale professional projects or heavy data processing.

SUITABILITY:

It would suit an entry level trainee code developer because it focuses entirely on learning rather than production.

A3. The World Wide Web Consortium (W3C) was formed to create "universal standards" (rules for how HTML and CSS should work) so that a website would look the same in every browser. However, developers faced major problems:

1. Proprietary Tags: During the 90s, browsers ignored standards to create their own features. If a developer used an IE-only feature, the site would break in Netscape, and vice-versa.
2. The "IE6" Nightmare: For nearly a decade, Internet Explorer 6 held a massive market share but refused to follow modern CSS standards. Developers had to write "CSS Hacks" (extra, messy code) just to make basic layouts look correct in IE.
3. Fragmentation: Developers had to test every site on multiple browsers and versions. This led to the era of "Best viewed in..." banners, which signaled a failure of the universal web.
4. Cross-Browser Inconsistency: Even today, while standards are much tighter, different browser engines (Blink, WebKit, Gecko) may interpret specific CSS properties or JavaScript functions slightly differently, requiring "polyfills" or "vendor prefixes" to ensure compatibility.

A4. Website testing methodologies ensure a site works perfectly for everyone, everywhere. They are broken down into two main categories:

Browser Compatibility

Ensures the site looks and acts the same across all platforms by testing on different engines like Chrome, Safari, and Firefox. Making sure the layout adjusts for Mobile, Tablet, and Desktop, and checking performance on Windows, macOS, iOS, and Android.

Website Functionality

Ensures every button and feature does what it is supposed to do by testing that no links are broken (404 errors), checking that login and contact fields work and catch errors, verifying "end-to-end" tasks, like completing a checkout or sign-up and confirming user info is saved and loaded correctly.

A5. The Northern Territory Government has endorsed the World Wide Web Consortium's Web Content Accessibility Guidelines (WCAG 2.0).

They are working towards making all our websites and web content meet WCAG 2.0 Level AA compliance.

A6. Website asset architecture is organized through a strict directory structure:

• Project (Root) Folder: This is the main folder for the project and contains ALL other files and folders. On the web it’s called the root folder. It’s not shown in the image above; consider it the grey box around everything.
• HTML files: these are all of the files that end with .html. These should be directly in the Project/Root folder and not in any sub folders. Doing that makes it easy to see all of your files and makes all of the paths to resources (images, css files) the same. The only required file is index.html but your sites will all have more .html files.
• CSS Folder: all .css files go here. In this class we will not write css either in style elements on the web page or in attributes of elements. Instead all CSS will go in external stylesheets and those will be put in the css folder. You will need to have at least one stylesheet called either main.css or style.css. I will generally use main, but some of my tutorials and others use style.css so it’s OK if you use that. But don’t use both. Other CSS files should have names referring to what they are styling.
• Images Folder: all images go here (.jpg, .png, .gif, etc). You can name the folder images or img.
• JavaScript Folder: all JavaScript files go here. They end in .js. You can name the folder javascript or js.