.mokogitea/manifest.xml Standard

The .mokogitea/manifest.xml file is the canonical identity and build metadata file for all MokoConsulting repositories. It is required in every repo.

Schema (v1.0)

<?xml version="1.0" encoding="UTF-8"?>
<moko-platform xmlns="https://standards.mokoconsulting.tech/moko-platform/1.0" schema-version="1.0">
    <identity>
        <name>{RepoName}</name>
        <org>MokoConsulting</org>
        <description>{Description}</description>
        <version>{XX.YY.ZZ}</version>
        <license spdx="GPL-3.0-or-later">GNU General Public License v3</license>
    </identity>
    <governance>
        <platform>{joomla|dolibarr|go|node|rust|generic}</platform>
        <standards-version>05.00.00</standards-version>
        <standards-source>https://git.mokoconsulting.tech/MokoConsulting/moko-platform</standards-source>
    </governance>
    <build>
        <language>{PHP|Go|JavaScript|Rust|Python}</language>
        <package-type>{joomla-extension|dolibarr|application|library|mcp-server}</package-type>
        <entry-point>{src/|htdocs/custom/|./}</entry-point>
    </build>
</moko-platform>

Fields

identity

Field	Required	Description
`name`	Yes	Repository/extension display name
`org`	Yes	Organization name (always `MokoConsulting`)
`description`	Yes	One-line project description
`version`	Yes	Canonical version number in `XX.YY.ZZ` format. This is the controlling version used by CI workflows for releases, update-server.xml entries, and version bumps
`license`	Yes	License with SPDX identifier attribute

governance

Field	Required	Description
`platform`	Yes	Target platform: `joomla`, `dolibarr`, `go`, `node`, `rust`, `generic`
`standards-version`	Yes	MokoStandards version this repo conforms to
`standards-source`	Yes	URL to moko-platform repo

build

Field	Required	Description
`language`	Yes	Primary programming language
`package-type`	Yes	Package type: `joomla-extension`, `dolibarr`, `application`, `library`, `mcp-server`
`entry-point`	Yes	Source directory for packaging (e.g., `src/`, `htdocs/custom/`, `./`)

Usage by CI Workflows

The update-server.yml workflow reads this manifest to:

Determine platform and packaging strategy
Read the canonical version number
Find the source entry point for ZIP packaging
Set extension metadata (name, type, element)

Version Field

The <version> field is the single source of truth for the project version. The version_read.php and version_bump.php CLI tools read and write this field. All other version references (Joomla XML manifests, README badges, etc.) are synced from this value.

Platform Values

Platform	Package Type	Entry Point	Examples
`joomla`	`joomla-extension`	`src/`	MokoJoomGallery, MokoJoomHero
`dolibarr`	`dolibarr`	`htdocs/custom/`	MokoCRM, MokoDoliAuth
`go`	`application`	`./`	MokoGitea
`node`	`mcp-server`	`./`	mcp-mokowaas-api
`generic`	`library`	`./`	moko-platform