h4tcher-docusaurus-generator

To generate a Docusaurus documentation site, this Skill analyzes your repository's structure, scaffolds a Docusaurus 3.x project, configures the site hierarchy, and runs build and preview steps automatically.

The best way to turn scattered README files into a cohesive user guide is using automated repo analysis to extract documentation signals, producing a structured Docusaurus 3.x site with installation, features, and FAQ sections.

Yes, you can automatically configure navbar, footer, and i18n settings. The generation process writes these preferences directly into your docusaurus.config.ts file during the site scaffolding step.

Yes, the Docusaurus generator works with partially documented projects. It inspects existing configuration signals and docs to decide what needs documenting, then reuses or creates a buildable docs-site directory.

Frontmatter is added automatically during the documentation generation phase. The process analyzes your codebase routes and components, then applies practical frontmatter to the newly created Docusaurus markdown files.

Analyzing package.json and repo structure is necessary to identify existing documentation signals and dependencies. This ensures the generated static site accurately reflects your project's features and configuration requirements.