HS1021 Web Design Group Assignment help

Assessment Details and Submission Guidelines

CategoryDetails
TrimesterT3 2025
Unit CodeHS1021
Unit TitleWeb Design
Assessment TypeGroup Assignment
Weight60%
Submission Guidelines1. All work must be submitted on Blackboard by the due date along with a completed Assignment Cover Page.<br>2. The assignment must be in MS Word format unless otherwise specified.
Academic Integrity InformationHolmes Institute is committed to ensuring and upholding academic integrity. All assessments must comply with academic integrity guidelines. Please learn about academic integrity and consult your teachers with any questions. Violating academic integrity is serious and punishable by penalties that range from deduction of marks, failure of the assessment task or unit involved, suspension of course enrolment, or cancellation of course enrolment.
Penalties- All work must be submitted on Blackboard by the due date and time, along with a completed Assessment Cover Page. Late penalties apply.<br>- 20% penalty applicable for solo (single student) group submissions.<br>- Your answers must be based on Holmes Institute syllabus of this unit. Outside sources may not amount to more than 10% of any answer and must be correctly referenced in full. Over-reliance on outside sources will be penalised<br>- Reference sources must be cited in the text of the report and listed appropriately at the end in a reference list using Holmes Institute Adapted Harvard Referencing. Penalties are associated with incorrect citation and referencing.

 

Group Assignment Guidelines and Specifications

Assessment Title:

Group Website Design Project

Assessment Overview (Group Work - 60 Marks Total)

In this assessment, students will design, develop, and document a functional multi-page website using HTML5 and CSS (without automated code generators). Each team will simulate a real-world client project - communicating with a mock "client" to define requirements, produce technical and design documentation, and deliver a validated, professional website prototype.

Learning Outcomes Addressed

By completing this assessment, students will be able to:

  1. Design and create a fully functional website using HTML5 and CSS manually.
  2. Communicate with end users to determine website requirements and design features.
  3. Produce and use documentation for design, structure, and technical implementation.
  4. Validate website code against W3C standards across different browsers.

Project Description

Each group will create a responsive website for a fictional or real small business, community organisation, or event (e.g., café, fitness club, charity, festival). The website must consist of at least four interlinked pages, including:

  • Home Page
  • About / Services Page
  • Gallery / Products / Portfolio Page
  • Contact Page (with form layout)

The website must:

  • Use semantic HTML5 and external CSS (no inline styles or frameworks).
  • Include consistent navigation, layout, and visual design.
  • Demonstrate effective typography, colour schemes, and media usage (images, icons).
  • Display correctly in major browsers (Chrome, Firefox, Edge, Safari).
  • Pass W3C HTML and CSS validation.

Deliverables

1. Website Prototype (30 marks)

A working website in a compressed folder (groupname_website.zip) containing:

  • HTML files
  • A single CSS file
  • Images/media used

2. Design and Technical Documentation (30 marks)

Each group must submit a report (1,000-1,500 words) including:

  • Client Requirements Summary: record of user/client communication and identified needs.
  • Site Map and Wireframes: outlining page hierarchy and layout.
  • Style Guide: detailing colour palette, typography, and layout conventions.
  • Technical Implementation: brief explanation of HTML/CSS structure, media use, and challenges encountered.
  • Individual Reflection: Each member should contribute a short individual reflection (100 words) on teamwork and learning.

Submission Requirements

  • Website folder (HTML, CSS, media) in .zip format
  • Design & technical report in Microsoft Word format only
  • Submit via the Blackboard by Week 12, Friday 11:59 PM

 

Marking Rubric - Web Design Group Assessment (60 marks total)

Component 1: Website Prototype (30 marks)

CriteriaExcellentGoodPassIncomplete
Layout and Structure (8 marks)Excellent structure with well-organised, semantic HTML5; clear hierarchy and consistent layout across pages.Very good layout and logical HTML structure; minor inconsistencies.Acceptable but with noticeable structural issues or inconsistent formatting.Poor structure, missing elements, non-semantic HTML or broken layout.
Design and Aesthetics (8 marks)Visually appealing and professional design; strong use of colour, typography, spacing, and alignment; excellent readability.Cohesive design with thoughtful aesthetic choices; minor inconsistencies.Basic design with limited attention to aesthetics or user experience.Poor or distracting design; inconsistent styles or unreadable content.
Navigation and Usability (6 marks)Seamless, intuitive navigation; consistent menus, clear links, and strong usability across all pages.Logical and easy-to-use navigation; small usability issues.Basic navigation with limited usability or broken links.Confusing, inconsistent, or non-functional navigation.
Functionality (4 marks)Fully functional and responsive; excellent use of images, media, and links; works flawlessly across browsers.Minor functional or responsiveness issues but overall strong performance.Limited functionality or noticeable display problems.Major issues or non-functional site.
W3C Validation (4 marks)Fully validated HTML5 and CSS with no significant errors; cross-browser compliant.Minor validation warnings but compliant overall.Several validation errors; inconsistent across browsers.Fails W3C validation; major coding errors prevent correct display.

Subtotal: /30 marks

 

Component 2: Design and Technical Documentation (30 marks)

CriteriaExcellentGoodPassIncomplete
Requirements Analysis (5 marks)Comprehensive and realistic client needs analysis; strong communication evidence (e.g., meeting notes, emails).Clear understanding of client needs; good communication record.Minimal requirements identified; unclear communication process.No clear requirements or communication evidence.
Design Documentation (8 marks)Professional-quality site map, wireframes, and style guide; shows deep design thinking and visual planning.Strong design documentation with logical structure and clarity.Minimal or unclear design documentation.Missing or very poor documentation.
Technical Detail (8 marks)Excellent explanation of HTML/CSS structure, coding rationale, and problem-solving process.Clear and detailed technical explanations; minor omissions.Basic technical notes; lacks insight or precision.No meaningful technical detail or understanding evident.
Professionalism & Clarity (5 marks)Exceptionally clear, well-written, and professionally formatted report; logical flow and correct citations.Well-organised and mostly error-free report.Understandable but lacks structure or contains frequent errors.Poorly written or disorganised; difficult to follow.
Reflection Quality (4 marks)Deep and insightful reflection on individual learning, teamwork, and challenges; strong self-awareness.Thoughtful reflection with clear insights and lessons learned.Superficial reflection with limited personal analysis.Missing or irrelevant reflection.

Subtotal: /30 marks
 

Note: This report is provided as a sample for reference purposes only. For further guidance, detailed solutions, or personalized assignment support, please contact us directly.

HS1021 Web Design Group Assignment

Design and Technical Documentation Report

Project Name: Green Leaf Café Website

Group Members:

  • Student Name 1 (Student ID: XXXXXXX) - Project Lead & HTML Developer
  • Student Name 2 (Student ID: XXXXXXX) - CSS Designer & Content Writer
  • Student Name 3 (Student ID: XXXXXXX) - Quality Assurance & Documentation

Submission Date: Week 12, T3 2025

Word Count: 1,350 words

Table of Contents

  1. Executive Summary
  2. Client Requirements Summary
  3. Site Map and Wireframes
  4. Style Guide
  5. Technical Implementation
  6. Individual Reflections
  7. Conclusion
  8. References
  9. Appendices

1. Executive Summary

This report documents the design, development, and implementation process for the Green Leaf Café website. Our team created a responsive, four-page website using semantic HTML5 and CSS to showcase a fictional organic café business. The website includes a Home page, About/Services page, Menu/Products page, and Contact page with form layout. The project demonstrates effective client communication, thoughtful design planning, and professional web development practices compliant with W3C standards.

2. Client Requirements Summary

2.1 Client Background

Green Leaf Café is a fictional organic café located in Melbourne's CBD, specializing in healthy, sustainable food options and specialty coffee. The business targets health-conscious professionals aged 25-45 who value sustainability and quality ingredients.

2.2 Communication Process

Our team conducted mock client consultations through structured meetings to identify website requirements. Documentation of this process included:

Initial Client Meeting (Week 6):

  • Date: October 15, 2025
  • Attendees: Full project team + mock client representative
  • Format: Face-to-face meeting with structured questionnaire

Key Discussion Points:

  • Business objectives and target audience identification
  • Desired website features and functionality
  • Brand personality and visual preferences
  • Competitor website analysis
  • Content requirements and availability

Follow-up Email Communication (Week 7): Our team sent a requirements confirmation email summarizing:

  • Four-page website structure
  • Color palette preferences (earth tones, greens)
  • Image requirements (product photography, café atmosphere)
  • Contact form specifications
  • Mobile responsiveness requirements

2.3 Identified Requirements

Through our client communication process, we identified the following core requirements:

Functional Requirements:

  1. Four interlinked pages with consistent navigation
  2. Responsive design for mobile and desktop viewing
  3. Contact form with fields for name, email, phone, and message
  4. Image gallery showcasing café products and atmosphere
  5. Clear presentation of menu items and services
  6. Business location and operating hours information

Design Requirements:

  1. Professional, clean aesthetic reflecting organic/natural brand values
  2. Earth-tone color palette (greens, browns, creams)
  3. High-quality food and café photography
  4. Readable typography suitable for all age groups
  5. Intuitive navigation structure
  6. Consistent branding across all pages

Technical Requirements:

  1. Semantic HTML5 markup
  2. External CSS stylesheet (no inline styles)
  3. W3C validation compliance
  4. Cross-browser compatibility (Chrome, Firefox, Edge, Safari)
  5. Fast loading times
  6. Accessible design principles

3. Site Map and Wireframes

3.1 Site Map

The website structure follows a flat hierarchy for easy navigation:

                    Home Page (index.html)                           |        ___________________|___________________       |            |            |             |   About Us    Menu/Products   Gallery    Contact Us  (about.html)  (menu.html)  (gallery.html) (contact.html)

Navigation Logic:

  • All pages accessible from main navigation menu
  • Home page acts as central hub with call-to-action buttons
  • Consistent header and footer across all pages
  • Logo links back to home page from any page

3.2 Wireframe Descriptions

Home Page Wireframe:

  • Header: Logo (left), Navigation menu (right)
  • Hero section: Large banner image with café tagline
  • Three-column feature section highlighting key services
  • Call-to-action buttons linking to Menu and Contact pages
  • Footer: Contact information, social media icons, copyright

About/Services Page Wireframe:

  • Header: Consistent with home page
  • Main content area: Two-column layout
    • Left: About us text and mission statement
    • Right: Team photo or café interior image
  • Services section: Grid layout showing café offerings
  • Footer: Consistent with home page

Menu/Products Page Wireframe:

  • Header: Consistent navigation
  • Page title and introduction
  • Menu categories displayed in card layout
  • Each item includes: image, name, description, price
  • Organized sections: Coffee, Food, Beverages, Desserts
  • Footer: Consistent

Contact Page Wireframe:

  • Header: Consistent navigation
  • Two-column layout:
    • Left: Contact form (name, email, phone, message, submit button)
    • Right: Business information (address, phone, hours, embedded map placeholder)
  • Footer: Consistent

(Note: Actual wireframe diagrams would be included as visual appendices in the full report)

4. Style Guide

4.1 Color Palette

Our color scheme reflects the organic, natural brand identity:

  • Primary Green: #4A7C59 (used for headers, buttons, accents)
  • Secondary Brown: #8B6F47 (used for text highlights, borders)
  • Background Cream: #F5F5DC (main background color)
  • Text Dark Gray: #333333 (primary text color)
  • White: #FFFFFF (card backgrounds, contrast elements)

Color Usage Rationale: The green represents freshness and organic values, brown adds warmth and earthiness, while cream provides a soft, welcoming background. This combination creates visual harmony while maintaining excellent readability.

4.2 Typography

Primary Font Family: 'Segoe UI', Tahoma, Geneva, Verdana, sans-serif

Font Hierarchy:

  • H1 (Main headings): 2.5em, bold, color #4A7C59
  • H2 (Section headings): 2em, semi-bold, color #4A7C59
  • H3 (Subsection headings): 1.5em, semi-bold, color #8B6F47
  • Body text: 1em (16px base), regular weight, color #333333
  • Navigation links: 1.1em, semi-bold, color #333333, hover color #4A7C59

Line Height: 1.6 for body text (improves readability)

Font Justification: We selected web-safe fonts to ensure consistent display across all browsers without requiring external font downloads, improving page load speed.

4.3 Layout Conventions

Container Width: Maximum 1200px, centered with auto margins Padding Standards: 20px standard padding for sections, 40px for major divisions Margins: 15px between related elements, 30px between sections Border Radius: 8px for cards and buttons (modern, friendly appearance) Box Shadow: Subtle shadows (0 2px 5px rgba(0,0,0,0.1)) for depth

Grid System:

  • Three-column layout for feature sections (33.33% width each)
  • Two-column layout for content sections (60% / 40% split)
  • Single column for mobile devices (responsive breakpoint at 768px)

4.4 Visual Elements

Buttons:

  • Background: #4A7C59
  • Text color: #FFFFFF
  • Padding: 12px 30px
  • Border radius: 5px
  • Hover effect: Background darkens to #3A6C49

Images:

  • All images set to max-width: 100% for responsiveness
  • Border radius: 8px for consistency
  • Alt text required for accessibility

Navigation:

  • Horizontal menu bar
  • Background: #FFFFFF
  • Border bottom: 3px solid #4A7C59
  • Hover underline effect on links

5. Technical Implementation

5.1 HTML5 Structure

Our website employs semantic HTML5 elements throughout for improved accessibility and SEO:

Semantic Elements Used:

  • <header>: Contains logo and navigation menu
  • <nav>: Wraps navigation links with <ul> and <li> structure
  • <main>: Contains primary page content
  • <section>: Divides content into logical sections
  • <article>: Used for individual menu items and gallery items
  • <aside>: Sidebar content on About page
  • <footer>: Contains contact info and copyright

HTML File Structure:

greenleaf_website/ ├── index.html (Home page) ├── about.html (About/Services page) ├── menu.html (Menu/Products page) ├── contact.html (Contact page) ├── css/ │   └── styles.css (External stylesheet) └── images/    ├── logo.png    ├── hero-banner.jpg    ├── coffee1.jpg    ├── food1.jpg    └── (additional images)

Code Quality Practices:

  • Proper indentation (2 spaces) for readability
  • Descriptive class and ID names (e.g., .menu-card, #contact-form)
  • Comments explaining major sections
  • Consistent naming conventions (lowercase with hyphens)

5.2 CSS Implementation

External Stylesheet Organization:

Our styles.css file is organized in logical sections:

  1. Reset and Base Styles: Browser default resets, box-sizing
  2. Typography: Font families, sizes, weights
  3. Layout: Container, grid, flexbox utilities
  4. Components: Buttons, cards, forms
  5. Navigation: Header and menu styling
  6. Page-Specific: Unique styles for each page
  7. Media Queries: Responsive breakpoints

Key CSS Techniques Used:

Flexbox for Navigation:

nav ul {    display: flex;    justify-content: space-around;    list-style: none; }

Grid Layout for Menu Items:

.menu-grid {    display: grid;    grid-template-columns: repeat(3, 1fr);    gap: 20px; }

Responsive Design with Media Queries:

@media screen and (max-width: 768px) {    .menu-grid {        grid-template-columns: 1fr;    } }

CSS Box Model Application:

  • Consistent use of padding and margins
  • Border-box sizing for predictable layouts
  • Proper use of width and max-width for responsiveness

5.3 Media Integration

Image Optimization:

  • All images compressed to reduce file size
  • Appropriate dimensions (hero images: 1920x600px, product images: 400x400px)
  • Alt text provided for accessibility
  • File naming convention: descriptive-lowercase-with-hyphens.jpg

Responsive Images:

<img src="images/hero-banner.jpg" alt="Green Leaf Café interior with customers" class="hero-image">

5.4 Form Implementation

Contact Form Structure:

<form action="#" method="post" id="contact-form">    <label for="name">Name:</label>    <input type="text" id="name" name="name" required>        <label for="email">Email:</label>    <input type="email" id="email" name="email" required>        <label for="phone">Phone:</label>    <input type="tel" id="phone" name="phone">        <label for="message">Message:</label>    <textarea id="message" name="message" rows="5" required></textarea>        <button type="submit">Send Message</button> </form>

Form Validation:

  • HTML5 validation attributes (required, type="email")
  • Proper input types for better mobile experience
  • Clear labels associated with inputs using for/id attributes

5.5 Cross-Browser Compatibility

Testing Process: Our team tested the website across multiple browsers:

  • Google Chrome (v120): Full functionality, no issues detected
  • Mozilla Firefox (v121): Full functionality, consistent rendering
  • Microsoft Edge (v120): Full functionality, identical to Chrome
  • Safari (v17): Minor CSS prefix adjustments made for full compatibility

Compatibility Solutions Implemented:

  • Vendor prefixes for flexbox (-webkit-, -moz-)
  • CSS reset to normalize browser defaults
  • Avoided browser-specific features
  • Tested on both Windows and macOS platforms

5.6 W3C Validation

Validation Results:

HTML Validation:

  • All four HTML files passed W3C HTML5 validation
  • Zero errors detected
  • Minor warnings addressed (e.g., section heading structure)

CSS Validation:

  • styles.css passed W3C CSS Level 3 validation
  • Zero errors detected
  • Vendor prefix warnings acknowledged as intentional

Validation Process:

  1. Used W3C Markup Validation Service (validator.w3.org)
  2. Used W3C CSS Validation Service (jigsaw.w3.org/css-validator)
  3. Fixed all errors identified
  4. Documented validation screenshots

5.7 Challenges Encountered and Solutions

Challenge 1: Responsive Navigation Menu

  • Problem: Navigation menu difficult to use on mobile devices
  • Solution: Implemented media query to stack navigation vertically on screens below 768px width
  • Learning: Mobile-first design approach is more efficient

Challenge 2: Image Aspect Ratios

  • Problem: Images with different aspect ratios caused layout inconsistencies
  • Solution: Used CSS object-fit: cover property and set consistent container dimensions
  • Learning: Importance of consistent image specifications in style guide

Challenge 3: Form Styling Across Browsers

  • Problem: Form inputs appeared differently in Safari vs. Chrome
  • Solution: Applied explicit border, padding, and appearance: none to override browser defaults
  • Learning: Always test forms across all target browsers early in development

Challenge 4: CSS Specificity Issues

  • Problem: Some styles not applying due to specificity conflicts
  • Solution: Reorganized CSS structure and used more specific selectors when necessary
  • Learning: Importance of planning CSS architecture before writing extensive code

6. Individual Reflections

6.1 Student 1 Reflection (Project Lead & HTML Developer)

This project significantly enhanced my understanding of semantic HTML5 and project management. Leading the team taught me the importance of clear communication and setting realistic milestones. I enjoyed structuring the HTML documents and ensuring consistency across all pages. The most challenging aspect was coordinating different team members' contributions and maintaining code quality. I learned that thorough planning with wireframes and site maps saves significant development time. For future projects, I would implement version control (like Git) earlier to better manage code changes. Overall, this experience demonstrated how web development requires both technical skills and collaborative teamwork to succeed.

6.2 Student 2 Reflection (CSS Designer & Content Writer)

As the CSS designer, I gained deep appreciation for the complexity of creating responsive, visually appealing websites. Developing the style guide helped me understand the importance of design consistency and user experience principles. Writing content that is both informative and concise challenged my communication skills. I struggled initially with CSS flexbox and grid layouts but overcame this through researching documentation and experimenting with different approaches. Working with teammates who had different coding styles taught me the value of establishing coding conventions early. This project strengthened my CSS skills and showed me that good design requires balancing aesthetics with functionality and accessibility.

6.3 Student 3 Reflection (Quality Assurance & Documentation)

My role focused on testing, validation, and documentation, which proved more complex than anticipated. Testing across different browsers revealed numerous subtle inconsistencies that required careful debugging. Learning to use W3C validation tools gave me confidence in producing standards-compliant code. Documenting our development process reinforced the importance of maintaining clear records for professional web projects. I initially underestimated how much time thorough testing requires but now recognize it as essential for quality assurance. Collaborating with my team improved my communication skills and taught me to provide constructive feedback. This project demonstrated that successful websites require attention to technical details, user experience, and professional documentation practices.

7. Conclusion

The Green Leaf Café website project successfully demonstrates our team's ability to design, develop, and document a professional multi-page website using HTML5 and CSS. Through structured client communication, we identified clear requirements and translated them into effective design and technical solutions. Our semantic HTML5 structure, thoughtful CSS styling, and responsive design approach resulted in a website that meets W3C standards and displays correctly across major browsers.

The project provided valuable hands-on experience in all aspects of web development—from initial planning and wireframing through implementation and validation. Each team member contributed unique skills while learning to collaborate effectively on a complex technical project. The challenges we encountered, such as responsive design implementation and cross-browser compatibility, strengthened our problem-solving abilities and technical understanding.

This experience reinforced that successful web development requires combining technical proficiency with design thinking, effective communication, and attention to detail. The skills and knowledge gained through this project provide a strong foundation for future web development work and demonstrate the practical application of concepts learned throughout the HS1021 Web Design unit.

8. References

  1. W3C (2025). HTML5 Specification. World Wide Web Consortium. https://www.w3.org/TR/html5/
  2. W3C (2025). CSS Level 3 Specification. World Wide Web Consortium. https://www.w3.org/Style/CSS/
  3. Mozilla Developer Network (2025). HTML: HyperText Markup Language. https://developer.mozilla.org/en-US/docs/Web/HTML
  4. Mozilla Developer Network (2025). CSS: Cascading Style Sheets. https://developer.mozilla.org/en-US/docs/Web/CSS
  5. W3Schools (2025). HTML5 Tutorial. https://www.w3schools.com/html/
  6. W3Schools (2025). CSS Tutorial. https://www.w3schools.com/css/
  7. Holmes Institute (2025). HS1021 Web Design Study Guide. Holmes Institute. [Internal course material]

End of Report

Example invalid form file feedback

Join our 150К of happy users

Get original papers written according to your instructions and save time for what matters most.