From cc6546dcd1d486079e92fd7f4b048246be581d4a Mon Sep 17 00:00:00 2001 From: Brian O Grady Date: Fri, 2 Aug 2024 17:22:54 +0200 Subject: [PATCH] Update HTML-CSS-Project-1-Implementati0on-Guide-Dynamic.html --- ...oject-1-Implementati0on-Guide-Dynamic.html | 195 ++++++++++-------- 1 file changed, 108 insertions(+), 87 deletions(-) diff --git a/HTML-CSS-Project-1-Implementati0on-Guide-Dynamic.html b/HTML-CSS-Project-1-Implementati0on-Guide-Dynamic.html index 4debb7e..ea3ed5e 100644 --- a/HTML-CSS-Project-1-Implementati0on-Guide-Dynamic.html +++ b/HTML-CSS-Project-1-Implementati0on-Guide-Dynamic.html @@ -118,12 +118,21 @@
-

Project Implementation Guide

+

Project Implementation Guide

The phased approach to project implementation is designed to ensure a structured, manageable, and systematic process for developing a website project. By dividing the project into distinct phases, learners can focus on specific tasks and objectives, making it easier to track progress, identify issues, and achieve high-quality results. This methodical approach allows for iterative development, regular testing, and refinement, ensuring that the final product meets all specified requirements and standards.

Phase 1: Ideation & Initial Setup (4 hours)

Description: In this phase, the primary goal is to lay a solid foundation for the project by defining its purpose, audience, and design. This involves brainstorming ideas, creating user stories, and setting up the project environment.

- +

Ideation and User Story Definition: This task involves brainstorming and refining project ideas, defining user stories that capture the project's essential features and functionality, and documenting these stories in the README. This process helps clarify the project's goals and ensures that the development is user-centered.

+

Initial Planning and Wireframing: Learners will outline the website's structure and design through wireframes. This includes sketching key pages, choosing color schemes and fonts, and planning content placement. Documenting these decisions helps in creating a clear design blueprint and facilitates a user-centric approach.

+

Environment Setup and Version Control: Setting up the development environment includes creating a GitHub repository, organizing project files, and linking necessary resources. Proper documentation of this setup ensures that the project is well-organized and version-controlled from the start.

+

Pass Grade - Expected Outcomes:

+ +

Ideation and User Story Definition (1.5 hours)

@@ -374,21 +392,22 @@

Must User Stories Implementation (10 hours)

  • Distinction Grade: Expected Performance (Do's):
      -
    • Ensure that navigation is intuitive and links work correctly. (User Control)
      • +
    • Ensure that navigation is intuitive and links work correctly. (Information Hierarchy)
    • Design must meet accessibility guidelines and have good contrast. (Accessibility)
    • Ensure clear organization of information with headers and prioritized content. (Information Hierarchy)
      • -
    • Provide comprehensive documentation of key coding decisions and challenges. (Clean Code)
      • -
    • Code is clean, well-documented, and follows best practices. (Compliant Code)
      • -
    • The finished project is judged to be publishable in its current form with a professional-grade user interface and interaction. (Real-world application)
      • +
    • Provide comprehensive documentation of key coding decisions and challenges. (Comments)
      • +
    • Ensure all code is well-structured and adheres to best practices. (Clean Code)
      • +
    • Provide a thorough testing report with documented issues and resolutions. (Compliant Code)
  • Distinction Grade Areas for Improvement (Don'ts):
      -
    • Have broken navigation links. (User Control)
      • +
    • Have broken navigation links. (Information Hierarchy)
    • Overlook accessibility guidelines. (Accessibility)
    • Have disorganized content layout. (Information Hierarchy)
      • -
    • Provide incomplete or unclear documentation of coding decisions. (Clean Code)
      • -
    • Project is not of publishable quality. (Real-world application)
      • +
    • Fail to document coding decisions and challenges faced. (Comments)
      • +
    • Have poorly structured code with significant issues. (Clean Code)
      • +
    • Provide an incomplete testing report with unresolved issues. (Compliant Code)
    • @@ -519,6 +538,13 @@

    Adjustments & Refinement (2 hours)

    Phase 3: Should User Stories Implementation & Advanced Features (7 hours)

    Description: In this phase, advanced features and enhancements are added based on Should user stories. This includes implementing interactive elements, refining design, and completing comprehensive documentation.

    +

    Should User Stories Implementation: Advanced features are integrated, such as interactive elements and responsive design. Documentation of these features ensures that the implementation details are captured.

    +

    Documentation: The README is finalized to cover the project's purpose, features, setup instructions, and any complex code sections. Comprehensive documentation provides clarity for users and developers and ensures that the project is well-documented.

    +

    Pass Award - Expected Outcomes:

    +

    Should User Stories Implementation (5 hours)