Files
MokoCLI/templates/docs
jmiller d4947a7a80
Universal: PR Check / Branch Policy (pull_request) Successful in 2s
Universal: PR Check / Validate PR (pull_request) Failing after 9s
Branch Cleanup / Delete merged branch (pull_request) Failing after 2s
Universal: PR Check / Secret Scan (pull_request) Successful in 14s
RC Revert / Rename rc/ back to dev/ (pull_request) Has been skipped
Platform: mokocli CI / Gate 1: Code Quality (pull_request) Failing after 1m6s
Platform: mokocli CI / Gate 2: Unit Tests (8.1) (pull_request) Has been cancelled
Platform: mokocli CI / Gate 2: Unit Tests (8.2) (pull_request) Has been cancelled
Platform: mokocli CI / Gate 2: Unit Tests (8.3) (pull_request) Has been cancelled
Platform: mokocli CI / Gate 3: Self-Health Check (pull_request) Has been cancelled
Platform: mokocli CI / Gate 4: Governance (pull_request) Has been cancelled
Platform: mokocli CI / Gate 5: Template Integrity (pull_request) Has been cancelled
Platform: mokocli CI / CI Summary (pull_request) Has been cancelled
Universal: PR Check / Build RC Package (pull_request) Has been cancelled
Universal: PR Check / Report Issues (pull_request) Has been cancelled
fix(templates): CODEOWNERS use .mokogitea/workflows not .github/workflows
The synced CODEOWNERS templates deployed to MokoGitea repos pointed at
`.github/workflows/` (and other `.github/` config paths), which never
match the real `.mokogitea/` files — so code-owner protection on
workflows/config was silently a no-op. Also refreshes the stale,
consolidated-away workflow filename list to the current canonical set.

- templates/mokogitea/CODEOWNERS: repoint workflow + config paths to
  .mokogitea/; replace obsolete workflow names (deploy-dev, auto-dev-issue,
  standards-compliance, ci-joomla, update-server, branch-freeze, …) with
  the current set (auto-release, pre-release, cascade-dev, ci-generic,
  pr-check, cleanup, branch-cleanup, notify, repo-health, gitleaks,
  issue-branch, ci-issue-reporter, sync-on-merge, version-set, …).
- templates/docs/required/CODEOWNERS: same .github -> .mokogitea repoint.

Deliberately NOT changed (not simple path-swaps): template-SECURITY.md's
codeql-analysis / dependabot refs (GitHub-only features with no MokoGitea
equivalent), and the schema/gitignore/doc-example refs — see #337.

Closes #337

Claude-Session: https://claude.ai/code/session_01WbGBN9VyRK61zczYWcCQ2i
2026-07-05 15:49:44 -05:00
..

Documentation Templates

Purpose

This directory contains governed documentation templates for the mokocli organization. These templates ensure consistency, completeness, and compliance across all documentation artifacts.

Intended Use

Use these templates when:

  • Creating new documentation files
  • Establishing documentation in new repositories
  • Ensuring compliance with documentation standards
  • Maintaining consistency across projects

Instructions

Template Categories

Templates are organized into two categories:

  1. Required Templates - /templates/docs/required/

    • Mandatory documentation files for all repositories
    • Must be present and maintained
    • Subject to compliance review
  2. Extra Templates - /templates/docs/extra/

    • Optional documentation files
    • Recommended for specific use cases
    • Enhance documentation quality

Using Templates

To use a template:

  1. Navigate to appropriate template category (required or extra)
  2. Copy the template file to your target location
  3. Rename the file removing the template- prefix
  4. Replace all placeholder content with actual information
  5. Complete all required fields
  6. Remove example sections or mark them explicitly as examples
  7. Follow the template instructions section
  8. Validate against Document Formatting Policy

Template Maintenance

Templates are governed assets and must:

  • Follow Document Formatting Policy requirements
  • Include all required sections for templates
  • Contain no production data
  • Use placeholder values only
  • Be reviewed per governance schedule
  • Have Project task entries

Required Fields

When using templates, ensure these fields are completed:

  • All section headers and content
  • Metadata fields specific to the document
  • Revision history
  • Purpose and scope statements
  • Responsibilities and governance rules (where applicable)

Example Usage

Creating a New Repository README

# Copy template to target location
cp /templates/docs/required/template-README.md /path/to/repo/README.md

# Edit the file
# - Replace "[Repository Name]" with actual repository name
# - Complete all sections
# - Update metadata
# - Customize content for your repository

Creating a New Policy Document

# Use policy template structure
# Follow /docs/policy/ examples
# Ensure all mandatory policy sections included
# Obtain required approvals per policy

Metadata

  • Document Type: overview
  • Document Subtype: catalog
  • Owner Role: Documentation Owner
  • Approval Required: No
  • Evidence Required: Yes
  • Review Cycle: Annual
  • Retention: Indefinite
  • Compliance Tags: Governance
  • Status: Published

Revision History

  • Initial template catalog established
  • Template categories and usage instructions defined
  • Template maintenance requirements documented