copilot-swe-agent[bot]
04b99e0216
Co-authored-by: jmiller-moko <230051081+jmiller-moko@users.noreply.github.com>
3.7 KiB
MokoWaaS-Brand Configuration Guide (VERSION: 01.04.00)
1. Objective
This guide outlines the configuration parameters available within the MokoWaaS-Brand system plugin and establishes recommended defaults for WaaS governed environments. Proper configuration ensures consistent branding behavior across templates, modules, and administrative surfaces.
2. Accessing Plugin Configuration
- Log in to Joomla Administrator.
- Navigate to System > Plugins.
- Search for MokoWaaS-Brand.
- Select the plugin name to open the configuration panel.
3. Configuration Sections
The plugin provides several configuration areas designed to control branding behavior.
3.1 Brand Terminology Controls
These toggles replace Joomla native labels with WaaS aligned naming conventions.
Use cases include:
- Standardizing administrator UI language
- Reinforcing WaaS platform identity across components
Recommended Default: Enabled
3.2 Footer and Attribution Controls
Controls platform level branding elements including:
- Footer identification
- Powered By statements
- Attribution placements
Recommended Default: Enabled
3.3 Visibility Controls
Options for concealing or modifying native Joomla identifiers when appropriate.
Examples include:
- Hiding Joomla version labels
- Suppressing default metadata references
Recommended Default: Enabled for WaaS managed sites.
3.4 Rendering Enhancements
Controls adjustments to UI elements to ensure consistent presentation.
Examples:
- Header text alignment
- Replacement of naming strings
Recommended Default: Enabled
4. Configuration Change Workflow
To ensure continuity across managed environments:
- Document the change request.
- Apply updates in a staging environment.
- Validate branding presentation.
- Promote changes to production following WaaS change controls.
5. Troubleshooting Configuration Issues
- If changes do not appear, clear Joomla and browser cache.
- Confirm that no template override is superseding plugin outputs.
- Review logs for load order conflicts.
- Confirm that extension priority does not conflict with other system plugins.
6. Validation Checklist
- Branding reads consistently across administrator screens.
- No Joomla specific identifiers remain where replacement is expected.
- Frontend and backend output align with WaaS design expectations.
Revision History
| Version | Date | Author | Description |
|---|---|---|---|
| 01.02.00 | 2025-12-11 | Jonathan Miller (@jmiller-moko) | Initial standalone configuration guide created |