Files
MokoSuite/docs/reference/plugin-overview.md
T
Jonathan Miller 00d44256b4 refactor: rename MokoWaaS to MokoSuite across entire codebase
Rebrand all 17 sub-extensions from mokowaas to mokosuite naming,
including component, plugins, modules, task plugins, and webservices.
Updates package manifest, workflows, docs, wiki, and issue templates.
Adds new plg_system_mokosuite_license extension.
2026-06-07 09:25:45 -05:00

1.5 KiB

MokoSuite Plugin Overview

Executive Summary

The MokoSuite 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.