Knowledge Site Creator

Problem

Building a themed learning site by hand often repeats the same work: copy, card data, learning paths, local progress, styling, and deployment details. Copying a template can start quickly, but different topics can mix together, code boundaries become unclear, and specific pages can be mistaken for reusable architecture.

How it works

knowledge-site-creator breaks the job into an executable flow: analyze the topic, audience, and tone, then generate wordData.js and siteConfig.js, and create pages using references such as design-system.md and core-patterns.md. Core capabilities include:
- Flashcards for quick recall and card flipping
- Learn for progressive cards and mastered-item marking
- Quiz for concept checks and feedback
- Index for search, filters, and a card grid
- Progress for stats, achievements, and local tracking

The specification also requires release details: wrap LocalStorage calls in try-catch, avoid unescaped content in innerHTML, check DOM nodes before use, include meta, sitemap.xml, and robots.txt, and generate manifest.json plus sw.js for PWA offline access.

Boundaries

This fits structured concept sites, learning workshops, or installable personal knowledge sites. Clear, discrete entries work best; complex curricula, authentication, real-time data, or backend services are outside the described scope. Deployment and batch updates depend on the target environment and scripts, so check styles, affected projects, and rollback behavior first.