Documentation Guidelines

Overview

Documentation Guidelines

This guide outlines the standards and best practices for creating and maintaining documentation in the ICMS Knowledge Hub.

Documentation Structure

All documentation should follow a consistent structure:

  1. Title - Clear and descriptive
  2. Overview - Brief summary of the document's purpose and content
  3. Prerequisites - Any required knowledge or resources
  4. Main Content - Organized in logical sections with clear headings
  5. References - Links to related resources
  6. Revision History - Record of major changes

Writing Style

Follow these writing guidelines:

  • Use clear, concise language
  • Write in active voice
  • Define acronyms on first use
  • Use numbered lists for sequential steps
  • Use bullet points for non-sequential items

Formatting Guidelines

Headings

Use proper heading hierarchy (H1, H2, H3) for document structure:

1# H1 - Document Title
2## H2 - Major Section
3### H3 - Subsection

Code Blocks

Format code samples using fenced code blocks with appropriate language specification:

1def example_function():
2    print("This is an example function")
3    return True

Tables

Use tables for structured data:

Column 1Column 2Column 3
Data 1Data 2Data 3
Data 4Data 5Data 6

Images

Guidelines for using images:

  1. Use descriptive filenames
  2. Include alt text for accessibility
  3. Optimize images for web (compression)
  4. Use screenshots only when necessary
  5. Add captions for clarity

Document Maintenance

Regular maintenance keeps documentation valuable:

  • Review documents quarterly
  • Update technical details when systems change
  • Remove obsolete information
  • Verify all links are working
  • Update the revision history

Templates

Standard templates are available for:

  • Technical guides
  • Process documentation
  • Reference materials
  • Troubleshooting guides

Final Review Checklist

Before publishing, ensure your document:

  • Has a clear title and description
  • Contains accurate technical information
  • Is properly categorized and tagged
  • Has been proofread for grammar and clarity
  • Includes appropriate links to related content
  • Has been reviewed by a subject matter expert

Following these guidelines helps maintain high-quality, consistent documentation throughout the ICMS Knowledge Hub.

Translations: