Jonathan Miller
4b9a675d0f
Generic: Project CI / Tests (push) Blocked by required conditions
Platform: moko-platform CI / Gate 2: Unit Tests (8.1) (push) Blocked by required conditions
Platform: moko-platform CI / Gate 2: Unit Tests (8.2) (push) Blocked by required conditions
Platform: moko-platform CI / Gate 2: Unit Tests (8.3) (push) Blocked by required conditions
Platform: moko-platform CI / Gate 3: Self-Health Check (push) Blocked by required conditions
Platform: moko-platform CI / Gate 4: Governance (push) Blocked by required conditions
Platform: moko-platform CI / Gate 5: Template Integrity (push) Blocked by required conditions
Platform: moko-platform CI / CI Summary (push) Blocked by required conditions
Generic: Repo Health / Scripts governance (push) Blocked by required conditions
Generic: Repo Health / Repository health (push) Blocked by required conditions
Generic: Repo Health / Report Issues (push) Blocked by required conditions
Generic: Repo Health / Site Health (push) Has been skipped
Generic: Repo Health / Access control (push) Successful in 1s
Generic: Project CI / Lint & Validate (push) Successful in 36s
Platform: moko-platform CI / Gate 1: Code Quality (push) Failing after 40s
All Joomla element names, PHP classes, language files, folder structure, and manifest references renamed from mokosuite to mokosuiteclient. This repo is now the client-facing tracker for the MokoSuite platform.
33 lines
1.6 KiB
Markdown
33 lines
1.6 KiB
Markdown
# MokoSuiteClient Plugin Overview
|
|
|
|
## Executive Summary
|
|
The MokoSuiteClient plugin operates as a core enablement layer within the Suite delivery stack, aligning platform branding, terminology, and visual identity across administrative and user-facing touchpoints. It standardizes language, reinforces Suite positioning, and reduces fragmentation risk across templates and extensions.
|
|
|
|
## Purpose
|
|
- Replace default Joomla terminology with Suite aligned naming.
|
|
- Provide a consistent brand experience in the administrator interface.
|
|
- Establish a baseline layer for future identity and UX governance.
|
|
|
|
## Key Capabilities
|
|
- Terminology substitution for core labels and messages.
|
|
- Footer and powered by messaging alignment.
|
|
- Optional concealment of native Joomla identifiers where appropriate.
|
|
- Foundation for extended branding controls through templates and language packs.
|
|
|
|
## System Requirements
|
|
- Joomla 5.x
|
|
- PHP 8.1 or higher
|
|
- Compatible Suite template and language stack
|
|
- Ability to run as a system plugin before template rendering
|
|
|
|
## High Level Lifecycle
|
|
1. Install the plugin via the Joomla Extension Manager.
|
|
2. Enable the plugin in the System Plugin list.
|
|
3. Clear cache to propagate new language strings.
|
|
4. Validate administrator and frontend views for correct Suite branding.
|
|
|
|
## Operational Notes
|
|
- The plugin should remain enabled on all Suite managed instances.
|
|
- Changes to terminology may impact documentation and training materials and should be coordinated with internal teams.
|
|
- Third party extensions may require additional overrides for full branding alignment.
|