jmiller
56f26ca8cf
Drop the "Brand" suffix from all naming conventions: - PascalCase: MokoWaaSBrand → MokoWaaS - lowercase: mokowaasbrand → mokowaas - Display: MokoWaaS-Brand → MokoWaaS - Language keys: PLG_SYSTEM_MOKOWAASBRAND → PLG_SYSTEM_MOKOWAAS Renames 6 files and updates 28 files across PHP, XML, INI, Markdown, YAML, and shell scripts. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
33 lines
1.5 KiB
Markdown
33 lines
1.5 KiB
Markdown
# MokoWaaS Plugin Overview
|
|
|
|
## Executive Summary
|
|
The MokoWaaS plugin operates as a core enablement layer within the WaaS delivery stack, aligning platform branding, terminology, and visual identity across administrative and user-facing touchpoints. It standardizes language, reinforces WaaS positioning, and reduces fragmentation risk across templates and extensions.
|
|
|
|
## Purpose
|
|
- Replace default Joomla terminology with WaaS 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 WaaS 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 WaaS branding.
|
|
|
|
## Operational Notes
|
|
- The plugin should remain enabled on all WaaS 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.
|