Standardized templates for creating consistent, brand-endorsed documentation.
General-purpose template for most documentation needs.
- File:
standard.md - Use for: User guides, concept docs, general documentation
Step-by-step guide template with structured learning objectives.
- File:
tutorial.md - Use for: Tutorials, how-to guides, walkthroughs
Technical reference documentation for APIs.
- File:
api-reference.md - Use for: API documentation, SDK references
Problem-solution format for troubleshooting guides.
- File:
troubleshooting.md - Use for: Error resolution, debugging guides
Structured format for release announcements.
- File:
release-notes.md - Use for: Version releases, changelog entries
Condensed guide for getting started quickly.
- File:
quickstart.md - Use for: Getting started guides, quick references
# Copy a template to start a new document
cp templates/standard.md my-new-doc.md
# Or use the publishing service
curl -X POST https://api.docs-publishing.example.com/v1/documents/from-template \
-H "Authorization: Bearer YOUR_API_KEY" \
-d '{
"template": "standard",
"title": "My New Document",
"category": "guides"
}'- name: Create document from template
uses: ./docs-publishing-service/workflows/create-from-template
with:
template: standard
output: docs/my-new-doc.mdAll templates follow this basic structure:
- Frontmatter - Metadata in YAML format
- Title - Main document title
- Overview - Brief introduction
- Prerequisites - Required knowledge/setup (if applicable)
- Main Content - Core documentation
- Next Steps - What to do next
- Related Resources - Links to related docs
Templates can be customized per brand:
- Copy the template to
config/brands/{brand}/templates/ - Modify as needed
- The service will use brand-specific templates when available
Templates support variable substitution:
{{title}}- Document title{{author}}- Document author{{date}}- Current date{{version}}- Document version{{brand}}- Brand name{{category}}- Document category
Example:
# {{title}}
**Author:** {{author}}
**Version:** {{version}}
**Last Updated:** {{date}}- Start with a template - Don't write from scratch
- Keep frontmatter accurate - Metadata is used for organization
- Follow the structure - Consistency helps readers
- Fill in all sections - Remove sections that don't apply
- Use placeholders - Mark areas that need completion
To add a new template:
- Create the template file in
templates/ - Follow the standard structure
- Include comprehensive frontmatter
- Add documentation to this README
- Test with the validation service
For questions about templates, see the main Documentation Publishing Service README.