AT1 QUESTIONING AND ANSWERS

The differences between an XML sitemap and a HTML sitemap is first the type of format each uses. XML utilizes Extensible Markup language format whereas HTML utilises HTML format as stated in their names. They both serve different functions whilst also similarly used to list related links connected to that particular site. XML caters towards web crawlers and indexing mainly for website search engine optimization. Whereas HTML caters towards User Experience providing links to relevant information and categories related to that site, commonly found within the footer of these sites.

XML:

• Optimizes search engine indexing allowing for faster page crawlling
• Allows the creator to limit pages or content so search engines cant index them
• Provides details about pages such as when they were last updated and when they were last upddated
• Although it does provide important information and links it is catered towards machines not people so they cannot access this information (which may or may not be useful to them)
• If you intend to create manually requires knowledge of the format in order to be able to build it properly
• Can be vulnerable to XML injection, therefore can pose as a security risk as it lists potentially sensitive links and locations that are vulnerable to attacks giving them access

HTML:

• Improves User experience allowing for better navigation
• Requires basic skills as it utilises html format like rest of the site
• Doesn't primarily assist with search engine optimisation and indexing
• Generally has low user engagement therefore can be a maintenance burden

Visual studio code(VS code): Visual studio code is a free open source IDE that has very high customisability. Allows for coding in almost all major programming languages, as well as access to AI integration. Also includes a marketplace for extensions that are mostly free. Users may find issues with the program using vast resources potentially slowing pc, especially with multiple extensions and large code bases. VS code also comes with limited support for some enterprise features when first out-the-box which may be a problem for some users.

I believe it would suit an entry level code developer well, as it provides lots of customisability and included AI assistance providing ease of use. I also believe the wide range of available coding languages allows the user to use one app for all their coding which is great for a beginner, keeping their work centralised

IntelliJ IDEA: IntelliJ IDEA is an IDE that focuses on Java development with built in support for other languages. Has a similar plugin system to the Visual Studio code extension marketplace. And is ideal for developers whose focus is on Java scripting. There is a free and paid version, the paid version being quite costly which is not ideal for small teams/companies, it can also be quite resource intensive on low end systems, users may also face a steep learning curve

I belive it can suit an entry level developer whose priorities lie with Java scripting providing great range of tools specified to their task. And despite there being a steep learning curve if the user can get past this, they would have the ability to use a powerful tool which can be helpful on their resume and tasks. It's lack of a wide range of coding languages can be a concern though

NetBeans: NetBeans is a free open source IDE that has support for Java, PHP and HTML5 ideal for web development. It includes a built in debugger as well as a plug in system. Easy use interface ideal for beginners with an active community. Users may find that the IDE may be slower than other modern IDE's, as well as limited AI-support compared to other services.

NetBeans is an overall well equipped IDE and can serve an entry level developer quite well as it primarily focuses on web development tools whilst also being user friendly/easy to use. Where it might fall off is it's flexibility when compared to more proffessional tools such as visual studio code which has lots of features

The birth of the web began during the 90's with multiple corporations racing to become the primary browser, this competition also created issues with standards. Developers needing to create multiple multiple versions of same sites to support functionality on different browsers, as not all functionalities and features were equal making them incompatitble. In 1994 W3C was founded whose intention was to ensure web standardisation allowing accessibility to as many people as possible, although at the time these standards were not enforced therefore did not mean companies conformed to these standards. Web standards only started to really pick up in the 2000's where developers and browsers started to conform to the W3C standards. Standards went through many iterations including HTML 4 and XHTML 1.0 and 2.0, though XHTML 2.0 did not take off as it was not backwards compatible and did not work with internet explorer which was the primary browser choice of users at the time. Eventually HTML5 was created setting the standard for web developers ever since

Website testing methodologies are a set of tests that check:

• That it is Functional and adheres to its requirements and intended purpose
• Performance of the website, such as speed and and its responsiveness under various loads
• Security of the site, checking for any vulenerabilities the site may have
• Compatability between different browsers and devices ensuring that the site functions properly between browsers and devices and other various operating systems
• User Experience, that the site is visually appealing and has good user experience
• Payment testing, ensuring payment functions work as intended and securely if the sites contains such features

The endorsed requirements of accessibility for all government webpages is the W3C's Web content accessibility guidelines (WCAG 2.0)