home / skills / coollabsio / coolify-docs / adding-documentation-pages

adding-documentation-pages skill

/.claude/skills/adding-documentation-pages

This skill creates structured documentation pages in docs/ with frontmatter, sidebars, and images to support guides, knowledge-base articles, and

npx playbooks add skill coollabsio/coolify-docs --skill adding-documentation-pages

Review the files below or copy the command above to add this skill to your agents.

Files (3)
SKILL.md
3.1 KB
---
name: adding-documentation-pages
description: Creates documentation pages for guides, tutorials, knowledge base articles, and troubleshooting content in docs/. Use when adding how-to guides, writing KB articles, creating troubleshooting docs, adding pages to get-started/, applications/, databases/, knowledge-base/, or integrations/. NOT for service pages - use adding-service-documentation for docs/services/.
allowed-tools: Read, Grep, Glob, Write, Edit
---

# Add Documentation Page

Create new documentation pages for the Coolify docs (guides, tutorials, KB articles, troubleshooting).

## When NOT to Use This Skill

**Use `adding-service-documentation` instead for:**
- Service pages in `docs/services/`
- One-click services from Coolify's catalog

Services require List.vue registration and logo handling covered by that skill.

## Quick Start

1. **Create file** in the appropriate section directory
2. **Add frontmatter** with `title` and `description`
3. **Write content** with clear headings
4. **Update sidebar** in `docs/.vitepress/config.mts` (if needed)
5. **Add images** using `<ZoomableImage>` component

## Documentation Sections

| Section | Path | Content Type |
|---------|------|--------------|
| Get Started | `docs/get-started/` | Introduction, installation, basics |
| Applications | `docs/applications/` | Framework deployment guides |
| Databases | `docs/databases/` | Database deployment docs |
| Knowledge Base | `docs/knowledge-base/` | How-tos, concepts, guides |
| Troubleshoot | `docs/troubleshoot/` | Problem-solution articles |
| Integrations | `docs/integrations/` | Third-party integration guides |

## Required Frontmatter

```yaml
---
title: "Page Title"
description: "SEO-friendly description (used in meta tags)."
---
```

## File Naming

- Use lowercase kebab-case: `my-guide.md`
- Be descriptive but concise

## Detailed References

**Page-specific:**
- [TEMPLATES.md](./TEMPLATES.md) - Ready-to-use page templates
- [SIDEBAR.md](./SIDEBAR.md) - How to update sidebar configuration

**Shared guidelines:**
- [FRONTMATTER.md](../_shared/FRONTMATTER.md) - Title, description, Open Graph
- [IMAGES.md](../_shared/IMAGES.md) - Image syntax and optimization
- [LINKS.md](../_shared/LINKS.md) - Internal and external link formatting
- [CONTAINERS.md](../_shared/CONTAINERS.md) - VitePress callout containers

## Key Rules

1. **Images**:
   - Small images/icons: use standard markdown `![alt](path)`
   - Screenshots/large images: use `<ZoomableImage>` component
   - Format: `.webp` preferred, absolute paths (`/docs/images/...`)
2. **Links**: Internal use absolute paths; external add `?utm_source=coolify.io`
3. **Sidebar**: Update `docs/.vitepress/config.mts` (starts ~line 130)

## Verification

- [ ] Frontmatter has `title` and `description`
- [ ] Screenshots use `<ZoomableImage>`
- [ ] External links have UTM parameters
- [ ] Page added to sidebar (if applicable)
- [ ] Renders at http://localhost:5173/docs/[path]

## Related Skills

- `adding-service-documentation` - For `docs/services/` pages
- `renaming-services` - Renaming service docs
- `disabling-services` - Deprecating services

Overview

This skill creates documentation pages for guides, tutorials, knowledge-base articles, and troubleshooting content under docs/. It standardizes frontmatter, file naming, image handling, links, and sidebar updates so new pages render correctly in the docs site. Use it to add content to get-started/, applications/, databases/, knowledge-base/, troubleshoot/, or integrations/.

How this skill works

The skill guides you to create a markdown file in the correct docs/ section, add required frontmatter (title and description), and write structured content with clear headings. It enforces image rules (small images vs. screenshots using <ZoomableImage>), requires absolute internal links and UTM-tagged external links, and reminds you to update the site sidebar configuration so the page appears in navigation. Finally, it verifies rendering locally at the dev server URL.

When to use it

  • Adding how-to guides to docs/knowledge-base/ or docs/get-started/
  • Writing tutorials or step-by-step walkthroughs for applications or integrations
  • Creating troubleshooting articles for docs/troubleshoot/
  • Adding database deployment guides under docs/databases/
  • Adding integration instructions to docs/integrations/

Best practices

  • Add frontmatter with title and SEO-friendly description at the top of every page
  • Use lowercase kebab-case file names (e.g., my-guide.md) that are concise and descriptive
  • Use <ZoomableImage> for screenshots and large images; prefer .webp and absolute /docs/images/ paths
  • Use absolute internal links and append ?utm_source=coolify.io to external links
  • Update docs/.vitepress/config.mts sidebar entries so the page is discoverable in navigation
  • Run the local dev server and confirm the page renders at the expected path before merging

Example use cases

  • Create a get-started guide: docs/get-started/installation.md with setup steps and screenshots
  • Add an application framework guide under docs/applications/express-deploy.md that shows deployment commands and config
  • Write a knowledge-base article describing a common configuration pattern and link to related pages
  • Publish a troubleshooting article that lists symptoms, root causes, and step-by-step fixes in docs/troubleshoot/
  • Document a third-party integration with API keys, permissions, and example requests under docs/integrations/

FAQ

What frontmatter fields are required?

Every page needs title and description in the YAML frontmatter; description is used for meta and SEO.

How should I add images?

Use standard markdown for small images; use <ZoomableImage> for screenshots and large images. Prefer .webp files and use absolute /docs/images/ paths.

Do I always need to update the sidebar?

If the page should appear in site navigation, add it to docs/.vitepress/config.mts. For standalone or auxiliary pages you may skip sidebar changes.