Files
Jonathan Miller b73c1eba25
Generic: Repo Health / Scripts governance (push) Has been cancelled
Generic: Repo Health / Repository health (push) Has been cancelled
Generic: Repo Health / Report Issues (push) Has been cancelled
Generic: Project CI / Tests (pull_request) Has been cancelled
Platform: mokoplatform CI / Gate 2: Unit Tests (8.1) (pull_request) Has been cancelled
Platform: mokoplatform CI / Gate 2: Unit Tests (8.2) (pull_request) Has been cancelled
Platform: mokoplatform CI / Gate 2: Unit Tests (8.3) (pull_request) Has been cancelled
Platform: mokoplatform CI / Gate 3: Self-Health Check (pull_request) Has been cancelled
Platform: mokoplatform CI / Gate 4: Governance (pull_request) Has been cancelled
Platform: mokoplatform CI / Gate 5: Template Integrity (pull_request) Has been cancelled
Platform: mokoplatform 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
Generic: Repo Health / Scripts governance (pull_request) Has been cancelled
Generic: Repo Health / Repository health (pull_request) Has been cancelled
Generic: Repo Health / Report Issues (pull_request) Has been cancelled
Generic: Repo Health / Site Health (push) Has been cancelled
Generic: Repo Health / Access control (push) Has been cancelled
Generic: Repo Health / Site Health (pull_request) Has been cancelled
Universal: PR Check / Branch Policy (pull_request) Has been cancelled
Generic: Repo Health / Access control (pull_request) Has been cancelled
Universal: Build & Release / Promote to RC (pull_request) Has been cancelled
RC Revert / Rename rc/ back to dev/ (pull_request) Has been cancelled
Universal: Security Audit / Dependency Audit (pull_request) Has been cancelled
Branch Cleanup / Delete merged branch (pull_request) Has been cancelled
Universal: Secret Scanning / Gitleaks Secret Scan (pull_request) Has been cancelled
Universal: PR Check / Validate PR (pull_request) Has been cancelled
Universal: Build & Release / Build & Release Pipeline (pull_request) Has been cancelled
Generic: Project CI / Lint & Validate (pull_request) Has been cancelled
Platform: mokoplatform CI / Gate 1: Code Quality (pull_request) Has been cancelled
feat: add manifest_detect.php CLI tool for auto-detecting manifest fields
Scans source files to detect platform, name, version, element_name,
package_type, language, entry_point, description, and license_spdx.
Supports Joomla, Dolibarr, Go, MCP/Node, and generic platforms.

Includes --diff and --update modes for comparing against and pushing
to the Gitea manifest API. Warns on missing core fields.

Also removes deprecated mcp/servers/mokowaas_api (consolidated to
separate repo) and syncs dev branch changes.
2026-06-07 15:37:24 -05:00
..

Documentation Templates

Purpose

This directory contains governed documentation templates for the mokoplatform 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