add-docs-page

Add documentation pages and categories to a Docusaurus site with sidebar ordering and frontmatter.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/khsacc/FluoRaPressee --skill add-docs-page
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-docs-page
Source: https://github.com/khsacc/FluoRaPressee/tree/main/.claude/skills/add-docs-page
Command: npx skills add https://github.com/khsacc/FluoRaPressee --skill add-docs-page

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill simplifies the process of adding new pages or categories to the FluoRaPressée online manual, ensuring consistent sidebar ordering and preventing broken links in the Docusaurus-based documentation site.

Core Features & Use Cases

  • Automated Sidebar Management: Guides users on how to leverage filesystem-based autogeneration for sidebars without manual configuration.
  • Standardized Structure: Provides clear rules for frontmatter, category indexing, and cross-linking to maintain site integrity.
  • Use Case: When adding a new API endpoint documentation page, this Skill ensures the correct sidebar position is chosen and that the new page adheres to the project's specific Japanese-language documentation style.

Quick Start

Use the add-docs-page skill to guide you through creating a new documentation page in the docs-site directory by following the step-by-step instructions for frontmatter and sidebar positioning.

Frequently Asked Questions about add-docs-page

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new documentation page to a Docusaurus site without breaking the sidebar?

To add a Docusaurus documentation page safely, you must configure the frontmatter, ensure correct sidebar positioning via filesystem-based autogeneration, and implement relative cross-linking to prevent build-time errors and broken links.

Why does Docusaurus throw a build error when I add a new markdown page?

Docusaurus throws a build error when onBrokenLinks is set to 'throw' and new markdown pages lack valid relative cross-linking. You must ensure all internal links resolve correctly before the local build completes.

What is the best way to organize technical writing categories in Docusaurus?

The best way to organize technical writing categories in Docusaurus is by leveraging filesystem-based autogeneration for sidebars, which eliminates manual configuration and maintains consistent sidebar ordering across the documentation site.

How do I configure frontmatter and sidebar ordering for a technical manual in Docusaurus?

Configuring frontmatter and sidebar ordering requires following standardized rules for category indexing and page positioning within the docs-site directory, ensuring the technical manual maintains site integrity and consistent navigation.

Does filesystem-based sidebar autogeneration work without manual configuration in Docusaurus?

Yes, filesystem-based sidebar autogeneration works without manual configuration in Docusaurus, allowing you to add new documentation pages and categories by simply placing files in the correct directory structure.

Can I use relative cross-linking to prevent broken links in a Docusaurus manual?

Yes, you can and must use relative cross-linking to prevent broken links in a Docusaurus manual, ensuring compliance with build-time constraints like onBrokenLinks: 'throw' during local verification procedures.