Architecture

Architecture

Package Structure

pkg_mokoog
  com_mokoog              -- Admin component (dashboard, tag CRUD, batch, CSV, ACL)
  plg_system_mokoog       -- System plugin (frontend meta tag injection, sitemap, AI)
  plg_content_mokoog      -- Content plugin (editor form fields, live preview)
  plg_webservices_mokoog  -- WebServices plugin (REST API routes)

Targets Joomla 6+ and PHP 8.2+. All extensions use the modern namespaced DI architecture: services/provider.php providers, SubscriberInterface event subscribers, and namespaced MVC. No deprecated Factory::getDbo/getUser/getSession/getLanguage, Joomla\CMS\Filesystem, or jexit() calls remain (forward-compatible with Joomla 7).

Data Flow

Frontend (onBeforeCompileHead)

1. System plugin detects the current page (option, view, id)
2. Loads custom OG data from #__mokoog_tags (language-aware)
3. Falls back to category/menu OG data if available
4. Auto-generates missing fields from article/product content
5. Resolves the image URL, auto-resizes if enabled
6. Emits OG, Twitter, LinkedIn, Discord, Telegram, Fediverse, Pinterest meta tags
7. Builds JSON-LD schema(s) (Article/Product/WebPage + FAQ/HowTo/Event/Recipe/LocalBusiness/Video/custom)
8. Fires onMokoOGAfterRender for third-party extensions

Editor (content plugin)

1. Content plugin adds the OG fields tab to article/menu/category editor forms
2. On save, stores custom OG data to #__mokoog_tags keyed by language; JSON fields are validated as objects/arrays
3. Live preview updates the Facebook/Twitter/LinkedIn/Discord/Mastodon/Slack cards in real time

Admin component

1. Dashboard (default view) — DashboardModel computes coverage stats; View/Dashboard renders a donut + breakdown + missing-articles list
2. Tags — list view with publish/unpublish/delete (TagsController) and a single-record create/edit screen (TagController → View/Tag → tmpl/tag/edit.php)
3. Batch / Import-Export — BatchController, ImportExportController (CSRF + ACL gated)

API

1. WebServices plugin registers routes on onBeforeApiRoute
2. JSON:API controller provides full CRUD plus a content-lookup endpoint
3. A field whitelist (JsonapiView) prevents information leakage

Key Classes

Database

Single table: #__mokoog_tags

• Unique key: (content_type, content_id, language)
• Supports: com_content, com_content.category, menu, com_mokoshop
• Columns include og_*, seo_title, meta_description, robots, canonical_url, og_video, event_data, recipe_data, custom_schema, language, published
• Language-aware queries prefer a specific language over the * wildcard

Performance & Safety

• loadArticle() / loadShopProduct() use static per-request caching (including negative lookups) — one query instead of several when the image finder, date extractor, and JSON-LD builder all need the same record
• Batch processing is capped per request
• Generated images are cached under images/mokoog/generated/ and pruned after 30 days
• The sitemap excludes non-public content and writes via a temp file + atomic rename
• Custom JSON-LD is validated as an object/array on save and guarded on render, so malformed data cannot crash the public page

Printed from wiki · Architecture