Q&A

Frequently Asked Questions

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

XML Sitemap:

Primarily for search engines, written in XML. Helps with crawling and indexing but is not user-friendly.

  • Pros: Improved SEO, ensures indexing, supports large sites, includes metadata.
  • Cons: Not user-friendly, requires submission, no direct navigation benefit.

HTML Sitemap:

For users, written in HTML, improves navigation, and is visible on the website.

  • Pros: Helps users navigate, improves internal linking, indexed by search engines, easy to create.
  • Cons: Needs manual updates, less effective for large sites, lacks SEO metadata.

Evaluate three IDEs and how they suit an entry-level trainee code developer.

1. Visual Studio Code

Lightweight, supports many languages, has useful extensions.

  • Pros: Simple, flexible, and easy to expand.
  • Cons: Needs extensions for full features, may feel overwhelming at first.

2. PyCharm

Smart Python tools, built-in debugging, good for web development.

  • Pros: Excellent for Python learners.
  • Cons: Heavy on system resources, free version is limited.

3. Eclipse

Strong for Java, great debugging, many plugins.

  • Pros: Powerful for Java development.
  • Cons: Slow, complex interface, can feel outdated for beginners.

Brief history of web browser development and issues encountered by web developers.

History:

  • 1990s: Netscape vs Internet Explorer led to inconsistent standards.
  • 2000s: W3C promoted standardization; Firefox and Chrome improved speed/security.
  • 2010s–Present: Chrome, Edge, Firefox focus on performance and standards compliance.

Common Issues:

  • Different browsers interpret code differently.
  • Older browsers lack support for modern features.
  • Vendor-specific features cause compatibility issues.
  • Performance varies across platforms.

Solutions:

  • Use HTML5, CSS3, and ES6 JavaScript.
  • Test on multiple browsers.
  • Use progressive enhancement techniques.

What are website testing methodologies?
  • Browser Compatibility Testing: Checks across Chrome, Firefox, Safari, Edge, etc.
  • Functionality Testing: Ensures forms, links, navigation, and features work correctly.
  • Performance Testing: Tests site speed, load time, and responsiveness.
  • Security Testing: Detects vulnerabilities like data leaks or authentication flaws.
  • Usability Testing: Verifies accessibility, user experience, and mobile-friendliness.

Endorsed accessibility requirements for all NT Government webpages
  • WCAG 2.0 Level AA Compliance: Ensures accessibility for users with disabilities.
  • Focus on content being perceivable, operable, understandable, and robust.
  • Applies to all NT Government websites and services.
  • Users can report accessibility issues online.

How should assets be organized for a webpage?

Local Project Structure:

    Websites
    ├── RhondasMangoChutney
    │   ├── assets
    │   │   ├── images
    │   │   ├── css
    │   │   ├── js
    │   │   ├── fonts
    │   │   ├── downloads
    │   ├── index.html
    │   ├── recipe.html
    │   ├── about.html

Hosting (public_html folder):

    public_html
    ├── assets
    │   ├── images
    │   │   ├── mango-chutney.jpg
    │   │   ├── cooking-process.jpg
    │   │   ├── bottled-chutney.jpg
    │   ├── css
    │   │   ├── style.css
    │   ├── js
    │   │   ├── script.js
    │   ├── fonts
    │   ├── downloads
    ├── index.html
    ├── recipe.html
    ├── about.html