content-management

Automates CMS content pipeline including path resolution, taxonomy registration, static pages and search indexing.

Updated Jun 14, 2026
One-click install
npx skills add https://github.com/baan-press/baan --skill content-management-baan-press
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: content-management
Source: https://github.com/baan-press/baan/tree/main/.claude/skills/content-management
Command: npx skills add https://github.com/baan-press/baan --skill content-management-baan-press

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Streamlines the content management pipeline, addressing path resolution, taxonomy, static pages, and search indexing for a seamless and efficient content organization.

Core Features & Use Cases

  • Path Resolution: Manages content paths for single and multilingual environments, ensuring correct file retrieval.
  • Taxonomy: Registers categories and tags in dual storage (DB and article frontmatter) for efficient content categorization.
  • Static Pages: Manages independent pages like About, Contact, Terms, and Privacy, with cloud storage support.
  • Search Indexing: Builds locale-specific search indexes for easy content discovery.
  • Frontmatter Required Fields: Ensures all necessary metadata is present for proper content management.

Quick Start

To update a static page, use the command writePage('contact', 'Updated contact information here.').

Frequently Asked Questions about content-management

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

FAQPage Schema
How do I automate content management for static pages and taxonomy registration?

Automating content management involves using path resolution, taxonomy registration, static page management, and search indexing to organize files efficiently. You can update static pages directly using commands like writePage to modify content.

How does path resolution work for multilingual content environments?

Path resolution for multilingual content manages file paths to ensure correct document retrieval across different locales. It maps the requested URLs to the appropriate localized files, maintaining structural consistency for single and multilingual environments.

Do I need specific frontmatter fields for taxonomy registration and search indexing?

Yes, specific frontmatter required fields must be present in your content files for proper taxonomy registration and search indexing. These metadata fields ensure categories and tags are correctly registered in both the database and the article frontmatter.

Can I manage independent pages like Terms and Privacy with cloud storage support?

Managing independent static pages like Terms and Privacy supports cloud storage integration. The system handles these standalone pages separately from regular content, ensuring they remain accessible and updatable through dedicated path resolution.

What is the best way to build locale-specific search indexes for content discovery?

Building locale-specific search indexes requires parsing content and frontmatter to generate localized searchable metadata. This approach ensures content discovery is optimized for each language environment by indexing only the relevant localized documents.

Why does taxonomy registration use dual storage in both the database and article frontmatter?

Taxonomy registration uses dual storage to synchronize categories and tags between the database and article frontmatter. This ensures data integrity and allows the content management system to retrieve taxonomy information quickly whether querying the database or reading the file directly.