| applyTo | content/**/*.md |
|---|
Frontmatter reference: DOCS-FRONTMATTER.md Shortcodes reference: DOCS-SHORTCODES.md Working examples: content/example.md
For complete content editing workflow, see .claude/skills/content-editing/SKILL.md which covers:
- Creating and editing content with CLI tools
- Shared content management and testing
- Fact-checking with MCP server
- Complete validation workflows
The unified docs CLI provides tools for content creation and editing. For decision guidance on when to use CLI vs direct editing, see .claude/skills/docs-cli-workflow/SKILL.md.
Use docs create for AI-assisted scaffolding:
# Create from draft
docs create drafts/feature.md --products influxdb3_core
# Create and open files in editor (non-blocking)
docs create drafts/feature.md --products influxdb3_core --open
# Create and open, wait for editor (blocking)
docs create drafts/feature.md --products influxdb3_core --open --waitUse docs edit to quickly find and open content files:
# Find and list files (no editor)
docs edit /influxdb3/core/admin/databases/ --list
# Open in editor (non-blocking, exits immediately)
docs edit /influxdb3/core/admin/databases/
# Open and wait for editor (blocking, interactive)
docs edit /influxdb3/core/admin/databases/ --wait
# Use specific editor
docs edit /influxdb3/core/admin/databases/ --editor nanoOptions:
- Both commands are non-blocking by default (agent-friendly)
- Use
--waitfor interactive editing sessions - Use
--listwithdocs editto see files without opening - Accepts both product keys (
influxdb3_core) and paths (/influxdb3/core)
# Add placeholder syntax to code blocks
docs placeholders <file.md>
# Audit documentation coverage
docs audit --products influxdb3_core
# Generate release notes
docs release-notes v3.1.0 v3.2.0 --products influxdb3_coreFor complete CLI reference, run docs --help.
When editing files with source: frontmatter (shared content):
- Recommended: Use
docs edit <url>- automatically finds and opens all related files - Manual: If editing directly, remember to touch sourcing files to trigger Hugo rebuild
For complete shared content workflow, see .claude/skills/content-editing/SKILL.md.
Every content file needs:
title: # Page h1 heading
description: # SEO meta description
menu:
product_menu_key: # Identifies the Hugo menu specific to the current product
name: # Navigation link text
parent: # Parent menu item (if nested)
weight: # Sort order (1-99, 101-199, 201-299...)# 1. Verify Hugo build
hugo --quiet
# 2. Validate links
yarn test:links
# 3. Test code blocks (if applicable)
yarn test:codeblocks:allFor comprehensive testing workflows, see .claude/skills/content-editing/SKILL.md.
- Use semantic line feeds (one sentence per line)
- Test all code examples before committing
- Use appropriate shortcodes for UI elements
- Follow Google Developer Documentation Style Guide
- Use active voice, present tense, second person
Callouts:
> [!Note]
> [!Warning]
> [!Caution]
> [!Important]
> [!Tip]Required elements:
{{< req >}}
{{< req type="key" >}}Code placeholders:
```sh { placeholders="DATABASE_NAME|API_TOKEN" }
curl -X POST https://cloud2.influxdata.com/api/v2/write?bucket=DATABASE_NAME
```Replace the following:
- {{% code-placeholder-key %}}
DATABASE_NAME{{% /code-placeholder-key %}}: your database name
**Tabbed content**:
```markdown
{{< tabs-wrapper >}}
{{% tabs %}}
[Tab 1](#)
[Tab 2](#)
{{% /tabs %}}
{{% tab-content %}}
Content for tab 1
{{% /tab-content %}}
{{% tab-content %}}
Content for tab 2
{{% /tab-content %}}
{{< /tabs-wrapper >}}
For complete shortcodes reference, see DOCS-SHORTCODES.md.
- Complete workflow: .claude/skills/content-editing/SKILL.md
- CLI decision guidance: .claude/skills/docs-cli-workflow/SKILL.md
- Frontmatter: DOCS-FRONTMATTER.md
- Shortcodes: DOCS-SHORTCODES.md
- Contributing: DOCS-CONTRIBUTING.md