skills.rest
angrybeagles
angrybeaglesCOMMUNITY
Explore all skills by this author →
GitHub

fumadocs

Generate meta.json navigation files from blog-structure.ts for Fumadocs.

Updated Apr 13, 2026
Search Tags:#documentation#navigation#content-collections#fumadocs#blog-structure#meta.json
One-click install
npx skills add https://github.com/angrybeagles/weather-dashboard --skill fumadocs-angrybeagles
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fumadocs
Source: https://github.com/angrybeagles/weather-dashboard/tree/main/.claude/skills/fumadocs
Command: npx skills add https://github.com/angrybeagles/weather-dashboard --skill fumadocs-angrybeagles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fumadocs centralizes blog and documentation navigation by generating a single source of truth for menus and sections, reducing manual updates and version drift.

Core Features & Use Cases

  • Centralized meta.json system that derives all navigation from a single blog-structure.ts
  • Simplified workflow for adding posts and sections without touching multiple files
  • Consistent, predictable sidebars and content collections across projects

Quick Start

Run pnpm generate:meta after editing blog-structure.ts and then start the dev server to view updated navigation.

Frequently Asked Questions about fumadocs

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

FAQPage Schema
How do I centralize documentation navigation across a large content catalog?▼

To centralize documentation navigation, you can generate a single source of truth from a blog-structure.ts file. This approach automatically produces meta.json files to create predictable sidebar structures without manual updates.

How do I generate meta.json files for a fumadocs blog structure?▼

You generate meta.json files by editing your blog-structure.ts source file and running the pnpm generate:meta command. After generating the metadata, start your dev server to view the updated navigation menus.

Why does my documentation sidebar drift out of sync across content collections?▼

Documentation sidebars drift out of sync when navigation is updated manually across multiple files. Deriving all menus and sections from a single source of truth eliminates version drift and ensures consistent navigation.

Does this approach work for teams maintaining large content collections?▼

Yes, this centralized meta.json system is specifically designed for teams maintaining large content catalogs. It provides a streamlined posting workflow that enables predictable sidebar structures across projects.

What is the best way to add new sections to documentation without breaking sidebars?▼

The best way to add new sections without breaking sidebars is updating a single blog-structure.ts file. This simplified workflow lets you add posts and sections without touching multiple files.

What happens if I start the dev server before running the metadata generator?▼

If you start the dev server before running the metadata generator, your navigation will not reflect recent edits. You must run pnpm generate:meta after editing blog-structure.ts to view updated navigation.

Related Skills

Explore More Content & Communication Skills→
sanity-iosanity-io
28

pnpm

Manage Node.js monorepos with pnpm workspace-aware dependency management.

Official
Advanced
dezverevdezverev

animal-kernel-web-dev

Start the AnimalKernel.Web dev server and verify UI with Cursor's browser.

Community
Intermediate
DidierRLopesDidierRLopes
8

convert-beehiiv-newsletter

Convert Beehiiv newsletter posts into blog markdown files with front matter and images.

Community
Advanced
documensodocumenso
14.3k

create-documentation

Generate MDX documentation pages with Fumadocs components and meta.json navigation updates.

Official
Intermediate