Write org standards wiki pages and push to mokogitea-private #312

New Issue

2026-06-22T00:28:10Z

jmiller commented

2026-06-22 00:28:10 +00:00

Summary

The MokoCLI wiki has stub pages under reference/ that need full content. These are the org-wide standards that all repos must follow. The standards documentation also needs to be referenced from mokogitea-private.

Pages to Write (MokoCLI wiki reference/)

All pages exist as empty stubs. Need full content based on current org practices:

BRANCH-STRATEGY - Branch flow (feature->dev->rc->main), protected branches, naming conventions, synonym protections
CHANGELOG-STANDARD - Keep a Changelog format, CI enforcement, VERSION comment
VERSION-SCHEME - XX.YY.ZZ format, suffixes, auto-bump, CI versioning
ISSUE-WORKFLOW - Issue types, lifecycle, branch auto-creation, labeling, test tickets
CONTENT-POLICY - What goes where (wiki vs docs/ vs issues), files never committed, README/CLAUDE.md standards
MANIFEST-STANDARD - Metadata via API (not manifest.xml), required fields, update server
RELEASE-LIFECYCLE - Automated release flow, stages, assets, update server, skip conditions
VALIDATION - PHP lint, PHPCS, XML validation, language file checks
JOOMLA6-PATTERNS - Joomla 6 DI container, SubscriberInterface, Table operations, namespace conventions

Standards Documentation in mokogitea-private

Create policy pages that reference the MokoCLI wiki standards:

Branch protection enforcement policy
Release approval policy
Code review requirements
Security scanning requirements

Context

Branch protections are now enforced org-wide (11 branches per repo). The auto-release workflow skips doc-only changes. Makefiles removed from all Joomla repos. All infrastructure is in place - just needs documentation.

## Summary The MokoCLI wiki has stub pages under `reference/` that need full content. These are the org-wide standards that all repos must follow. The standards documentation also needs to be referenced from `mokogitea-private`. ## Pages to Write (MokoCLI wiki reference/) All pages exist as empty stubs. Need full content based on current org practices: 1. **BRANCH-STRATEGY** - Branch flow (feature->dev->rc->main), protected branches, naming conventions, synonym protections 2. **CHANGELOG-STANDARD** - Keep a Changelog format, CI enforcement, VERSION comment 3. **VERSION-SCHEME** - XX.YY.ZZ format, suffixes, auto-bump, CI versioning 4. **ISSUE-WORKFLOW** - Issue types, lifecycle, branch auto-creation, labeling, test tickets 5. **CONTENT-POLICY** - What goes where (wiki vs docs/ vs issues), files never committed, README/CLAUDE.md standards 6. **MANIFEST-STANDARD** - Metadata via API (not manifest.xml), required fields, update server 7. **RELEASE-LIFECYCLE** - Automated release flow, stages, assets, update server, skip conditions 8. **VALIDATION** - PHP lint, PHPCS, XML validation, language file checks 9. **JOOMLA6-PATTERNS** - Joomla 6 DI container, SubscriberInterface, Table operations, namespace conventions ## Standards Documentation in mokogitea-private Create policy pages that reference the MokoCLI wiki standards: - Branch protection enforcement policy - Release approval policy - Code review requirements - Security scanning requirements ## Context Branch protections are now enforced org-wide (11 branches per repo). The auto-release workflow skips doc-only changes. Makefiles removed from all Joomla repos. All infrastructure is in place - just needs documentation.

Sign in to join this conversation.

Priority Medium

Type Feature

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: MokoConsulting/MokoCLI#312