Project: Build a browsable product catalog
Organize and present a fictional product range through interaction, application components, or a CMS content model.
- Level 2 · Web Construction
- Level 3.1 · Web Development
- Level 3.2 · Content Management
Projects use one shared product brief and level-specific implementation requirements. Select your current level to narrow the list. Each project card also shows every level for which the project is suitable.
Create each source-code project in its own folder and Git repository. Connect that repository to its own private GitHub repository, commit coherent working checkpoints, and push the final verified state. For a CMS implementation, use one dedicated CMS workspace plus a local evidence folder for plans and restorable exports. Keep credentials and private data out of every folder, repository, and export.
Organize and present a fictional product range through interaction, application components, or a CMS content model.
Build the same accessible event website through the tools and implementation requirements of your current course level.
Create a searchable directory through an application data model or an editor-managed CMS structure.
Build a responsive Pokémon website with a playable map, random encounters, a small battle system, and a static Pokédex.
Create an accessible quiz with clear progress, answer feedback, results, and a route to try again.
Build a focused campaign microsite as a semantic static page or an editor-managed CMS publication.
Present selected work through an accessible portfolio built with the methods from your current course level.