This element covers the practical skills required to build and publish a basic website using industry-standard software. Learners will create structured HT
Topic Synopsis
This element covers the practical skills required to build and publish a basic website using industry-standard software. Learners will create structured HTML documents, apply CSS for styling, integrate multimedia content, and use web authoring tools to manage site assets. The goal is to produce a functional, accessible website that is published and live on the internet, demonstrating competence in front-end web development fundamentals.
Key Concepts & Core Principles
- Programming constructs: sequence, selection (if-else), and iteration (loops) – the building blocks of any program.
- Data types and structures: understanding integers, strings, arrays/lists, and how to manipulate them.
- Debugging techniques: using breakpoints, print statements, and error messages to identify and fix code issues.
- Software development lifecycle: stages from requirements gathering to design, coding, testing, and maintenance.
- Version control basics: using tools like Git to track changes and collaborate on code.
Exam Tips & Revision Strategies
- Use semantic HTML5 tags to structure your content, as this demonstrates an understanding of web standards and improves accessibility marks.
- Validate your HTML and CSS code using online tools (e.g., W3C validators) and include screenshots of the results in your evidence portfolio.
- Before submitting, test all internal and external hyperlinks, and ensure downloadable files (if any) are accessible and not blocked by the server.
- Document your publishing process with clear screenshots, including the FTP client settings and the live website URL, to provide full evidence for the assessor.
- Always start with a wireframe or site map to plan the structure; include this in your evidence to show planning skills.
- Use an external CSS file linked to all pages for consistency and easier maintenance; annotate your code to explain key styling choices.
- Before publishing, validate your HTML and CSS using online tools and document the results as evidence of quality assurance.
- Record a screen capture or use a testing log to demonstrate cross-browser and device testing, highlighting any adjustments made.
Common Misconceptions & Mistakes to Avoid
- Forgetting to include a valid DOCTYPE declaration, causing browsers to render pages in quirks mode with inconsistent results.
- Using absolute file paths (e.g., C:\Users\...) instead of relative paths when linking to stylesheets, images, or other pages, breaking the site when moved or published.
- Overlooking image optimisation, resulting in slow-loading pages due to uncompressed high-resolution images.
- Neglecting to test the published website in multiple browsers or on different devices, missing layout or functionality issues.
- Failing to maintain consistent styling across pages, leading to a disjointed look.
- Using absolute file paths instead of relative paths, causing broken links or missing media when published.
Examiner Marking Points
- Award credit for demonstrating correct use of HTML5 structural elements (header, nav, main, footer) to create a logical document outline.
- Award credit for applying CSS to control layout, typography, and colour, including the use of external stylesheets and consistent styling across multiple pages.
- Award credit for using web-authoring software to prepare and optimise images, multimedia, and other assets before insertion into web pages.
- Award credit for publishing a complete website to a web server using appropriate file transfer methods, ensuring all links and resources function correctly in a live environment.
- Award credit for demonstrating the ability to create a clear site structure (e.g., using a site map or folder hierarchy) and apply consistent CSS styling across all pages.
- Expect evidence of using website software tools to insert and optimise multimedia elements, such as images, audio, or video, with correct file paths and appropriate formats.
- Look for the implementation of interactive features like functional navigation links, forms, or JavaScript widgets, with a clear explanation of their purpose.
- Evidence of testing the website on multiple browsers/devices, documenting errors found and fixes applied, and successfully publishing to a live server with all links working.