JavaScript Only Projects Curriculum

Public curriculum preview for visitors and enrolled students. Use this page to evaluate module scope, outcomes, and learning path.

Download PDFBack to Course
Curriculum

JavaScript Only Projects

Strengthen JS by building interactive projects (games, utilities, mini-apps) without frameworks.

Duration: 12 Weeks
Level: Intermediate
Study Time: 2 hours/week + labs
School: Hexadigitall Academy

Welcome to JavaScript Only Projects! 🎓

This curriculum is designed to take you from core understanding to confident delivery through weekly applied practice, measurable outcomes, and portfolio evidence.

Each week builds progressively with practical tasks, implementation checkpoints, and reflection points so you can convert knowledge into repeatable professional performance.

Your success is our priority. Stay consistent with weekly execution, document your work, and use feedback loops to continuously improve your delivery quality.

Essential Resources

  • Language-specific style guides, design patterns reference, and debugging tools inventory
  • Testing frameworks, mock libraries, and performance profiling instructions for your tech stack
  • Refactoring patterns, security best practices, and code quality tooling configurations

Learning Roadmap

  • Early Weeks: Language fundamentals, testing basics, and design patterns
  • Middle Weeks: Advanced architectures, performance optimization, and debugging
  • Late Weeks: Production systems, scalability, and cross-platform deployment
  • Consuming APIs with Fetch and Async or Await
  • Local Storage and Browser Persistence
  • Modular JavaScript and Project Organization
  • Building a To-Do or Notes Application
  • Building a Quiz, Game, or Calculator
  • Search, Filter, and Sort Interface Patterns
  • Charts, Dashboards, or Data-Driven Mini Apps
  • Debugging, Refactoring, and Project Polish
  • Capstone: Ship a Multi-Feature JavaScript Application

Detailed Weekly Curriculum

Each week includes outcomes and practical lab work aligned to the curriculum structure.

Week 1

DOM Selection, Events, and User Interface State Basics

2 hours/week + labs
Learning Outcomes
  • Understand the principles of DOM Selection, Events, and User Interface State Basics and link them to course outcomes through progressive practical delivery milestones.
  • Apply DOM Selection, Events, and User Interface State Basics in a guided scenario using realistic tools, constraints, and quality gates.
  • Analyze trade-offs, risks, and decision points for DOM Selection, Events, and User Interface State Basics, then record rationale for stakeholder review.
  • Document a portfolio-ready engineering implementation dossier for DOM Selection, Events, and User Interface State Basics with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 2

Form Handling and Client-Side Validation

2 hours/week + labs
Learning Outcomes
  • Understand the principles of Form Handling and Client-Side Validation and link them to course outcomes through progressive practical delivery milestones.
  • Apply Form Handling and Client-Side Validation in a guided scenario using realistic tools, constraints, and quality gates.
  • Analyze trade-offs, risks, and decision points for Form Handling and Client-Side Validation, then record rationale for stakeholder review.
  • Document a portfolio-ready engineering implementation dossier for Form Handling and Client-Side Validation with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 3

Timers, Animations, and Interactive Widgets

2 hours/week + labs
Learning Outcomes
  • Understand the principles of Timers, Animations, and Interactive Widgets and link them to course outcomes through progressive practical delivery milestones.
  • Apply Timers, Animations, and Interactive Widgets in a guided scenario using realistic tools, constraints, and quality gates.
  • Analyze trade-offs, risks, and decision points for Timers, Animations, and Interactive Widgets, then record rationale for stakeholder review.
  • Document a portfolio-ready engineering implementation dossier for Timers, Animations, and Interactive Widgets with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 4

Consuming APIs with Fetch and Async or Await

2 hours/week + labs
Learning Outcomes
  • Understand the principles of Consuming APIs with Fetch and Async or Await and link them to course outcomes through progressive practical delivery milestones.
  • Apply Consuming APIs with Fetch and Async or Await in a guided scenario using realistic tools, constraints, and quality gates.
  • Analyze trade-offs, risks, and decision points for Consuming APIs with Fetch and Async or Await, then record rationale for stakeholder review.
  • Document a portfolio-ready engineering implementation dossier for Consuming APIs with Fetch and Async or Await with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 5

Local Storage and Browser Persistence

2 hours/week + labs
Learning Outcomes
  • Apply the principles of Local Storage and Browser Persistence and link them to course outcomes through progressive practical delivery milestones.
  • Analyze Local Storage and Browser Persistence in a guided scenario using realistic tools, constraints, and quality gates.
  • Evaluate trade-offs, risks, and decision points for Local Storage and Browser Persistence, then record rationale for stakeholder review.
  • Justify a portfolio-ready engineering implementation dossier for Local Storage and Browser Persistence with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 6

Modular JavaScript and Project Organization

2 hours/week + labs
Learning Outcomes
  • Apply the principles of Modular JavaScript and Project Organization and link them to course outcomes through progressive practical delivery milestones.
  • Analyze Modular JavaScript and Project Organization in a guided scenario using realistic tools, constraints, and quality gates.
  • Evaluate trade-offs, risks, and decision points for Modular JavaScript and Project Organization, then record rationale for stakeholder review.
  • Justify a portfolio-ready engineering implementation dossier for Modular JavaScript and Project Organization with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 7

Building a To-Do or Notes Application

2 hours/week + labs
Learning Outcomes
  • Apply the principles of Building a To-Do or Notes Application and link them to course outcomes through progressive practical delivery milestones.
  • Analyze Building a To-Do or Notes Application in a guided scenario using realistic tools, constraints, and quality gates.
  • Evaluate trade-offs, risks, and decision points for Building a To-Do or Notes Application, then record rationale for stakeholder review.
  • Justify a portfolio-ready engineering implementation dossier for Building a To-Do or Notes Application with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 8

Building a Quiz, Game, or Calculator

2 hours/week + labs
Learning Outcomes
  • Apply the principles of Building a Quiz, Game, or Calculator and link them to course outcomes through progressive practical delivery milestones.
  • Analyze Building a Quiz, Game, or Calculator in a guided scenario using realistic tools, constraints, and quality gates.
  • Evaluate trade-offs, risks, and decision points for Building a Quiz, Game, or Calculator, then record rationale for stakeholder review.
  • Justify a portfolio-ready engineering implementation dossier for Building a Quiz, Game, or Calculator with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 9

Search, Filter, and Sort Interface Patterns

2 hours/week + labs
Learning Outcomes
  • Analyze the principles of Search, Filter, and Sort Interface Patterns and link them to course outcomes through progressive practical delivery milestones.
  • Evaluate Search, Filter, and Sort Interface Patterns in a guided scenario using realistic tools, constraints, and quality gates.
  • Create trade-offs, risks, and decision points for Search, Filter, and Sort Interface Patterns, then record rationale for stakeholder review.
  • Defend a portfolio-ready engineering implementation dossier for Search, Filter, and Sort Interface Patterns with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 10

Charts, Dashboards, or Data-Driven Mini Apps

2 hours/week + labs
Learning Outcomes
  • Analyze the principles of Charts, Dashboards, or Data-Driven Mini Apps and link them to course outcomes through progressive practical delivery milestones.
  • Evaluate Charts, Dashboards, or Data-Driven Mini Apps in a guided scenario using realistic tools, constraints, and quality gates.
  • Create trade-offs, risks, and decision points for Charts, Dashboards, or Data-Driven Mini Apps, then record rationale for stakeholder review.
  • Defend a portfolio-ready engineering implementation dossier for Charts, Dashboards, or Data-Driven Mini Apps with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 11

Debugging, Refactoring, and Project Polish

2 hours/week + labs
Learning Outcomes
  • Analyze the principles of Debugging, Refactoring, and Project Polish and link them to course outcomes through progressive practical delivery milestones.
  • Evaluate Debugging, Refactoring, and Project Polish in a guided scenario using realistic tools, constraints, and quality gates.
  • Create trade-offs, risks, and decision points for Debugging, Refactoring, and Project Polish, then record rationale for stakeholder review.
  • Defend a portfolio-ready engineering implementation dossier for Debugging, Refactoring, and Project Polish with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.
Week 12

Capstone: Ship a Multi-Feature JavaScript Application

2 hours/week + labs
Learning Outcomes
  • Analyze the principles of Capstone: Ship a Multi-Feature JavaScript Application and link them to course outcomes through progressive practical delivery milestones.
  • Evaluate Capstone: Ship a Multi-Feature JavaScript Application in a guided scenario using realistic tools, constraints, and quality gates.
  • Create trade-offs, risks, and decision points for Capstone: Ship a Multi-Feature JavaScript Application, then record rationale for stakeholder review.
  • Defend a portfolio-ready engineering implementation dossier for Capstone: Ship a Multi-Feature JavaScript Application with measurable success criteria and next actions.
  • Track measurable progress using rubric scores, defect/risk trends, and evidence completeness each week.
  • Run a short retrospective focused on what to retain, improve, and scale into the following week.
  • Incorporate peer or mentor feedback and revise the week deliverable to professional publication quality.
  • Publish the week output into your cumulative portfolio with concise outcome narrative and proof artifacts.

Capstone Projects

Project 1: API-Driven Utility App

Build a JavaScript utility application that consumes external APIs and supports offline-friendly persistence.

  • Async request orchestration with retry and error states
  • Persistent user preferences and cached response handling
  • UI and data validation checklist with bug log

Project 2: Productivity Workflow Application

Develop a feature-rich task or notes app with search, filter, sort, and accessibility-focused interactions.

  • Modular architecture and reusable UI controllers
  • Interactive workflows with keyboard and mouse support
  • Performance and usability review notes with improvements

Project 3: Final Multi-Feature JavaScript Capstone

Ship and present a polished JavaScript application demonstrating integration, quality, and maintainability.

  • End-to-end feature coverage and test evidence
  • Technical documentation, setup guide, and deployment notes
  • Demo narrative, trade-off analysis, and roadmap