Skip to content
Platform documentation

ExtensionFlow platform documentation

Release-operator, architecture and internal documentation for the ExtensionFlow platform. Product documentation stays with each extension and is not mixed into the platform manual.

Platform wiki

Documentation sections

Public platform docs

Public portal behavior, catalog pages, product pages, documentation pages, changelog, roadmap and status pages.

3 items
Downloads and installation

Release workflow for Joomla installers

How to choose a release, read its metadata, download the package and install it through Joomla Administrator.

Read article
Compatibility and trust

Compatibility labels and checksums

How to read Joomla/PHP compatibility, file size and checksum metadata before deploying a release.

Read article
Public portal reference

Public portal pages and buttons

A field-by-field and button-by-button reference for the public ExtensionFlow portal: catalog, product pages, documentation, changelog, roadmap, status and downloads.

Read article

Release/operator docs for ExtensionFlow

Admin release form, status behavior, checksums, Joomla XML metadata, compatibility matrix, private releases and archived/yanked release behavior.

4 items
Admin release form

Release fields and what each one controls

A field-by-field guide to release identity, release artifacts, Joomla XML metadata, compatibility rules, private metadata and update delivery.

Read article
Admin extension form

Extension fields and public product records

How extension metadata controls catalog cards, product pages, child artifacts, update feed aliases and support links.

Read article
Joomla, PHP and database registry

Compatibility registry, lifecycle warnings and version order

How Joomla, PHP and database version registries drive release-form choices, warnings and generated update XML compatibility metadata.

Read article
Visibility and policy

Public access policy

How public, unlisted, private and archived states affect pages, downloads and update feeds.

Read article

Platform architecture docs

ERD, API notes, package model ADRs, update-feed architecture, data model and release-builder internals.

6 items
Platform overview

What ExtensionFlow is

A public Joomla extension delivery portal for products, release history, release artifacts, update feeds, roadmap items and changelog records.

Read article
Joomla XML delivery

Joomla update feeds

How ExtensionFlow exposes XML update URLs for active public and unlisted extensions.

Read article
Products and dependencies

Package artifacts and child extensions

How parent products, bundled plugins, libraries, modules and language packs are represented on public pages.

Read article
Related documentation files

Related documentation files, ADRs and PDFs

How supporting files are attached to extension documentation without treating them as installable artifacts or separate catalog products.

Read article
Platform stack

Platform stack and runtime boundary

How ExtensionFlow is built on CodeIgniter 4, MySQL/MariaDB storage, CI migrations, public controllers and admin-only release workflows.

Read article
API documentation

Справочник API ExtensionFlow

Authenticated JSON and XML endpoints for integrations that need extension, release, update or changelog data.

Read article

Internal seed/migration notes

Baseline seeds, migrations and internal notes used to reproduce ExtensionFlow data without hand-editing live databases.

1 item
Internal notes

Internal seed and migration notes

How baseline seeds, migrations and platform changelog entries are used to reproduce ExtensionFlow state without manual database edits.

Read article

Suggested reading path

The platform manual is focused on ExtensionFlow operations and internals. Product-specific guides remain on their own extension documentation pages.

  1. ReadPublic portal pages and buttonsto understand what each public page and action does.
  2. ReadRelease fieldsbefore publishing packages, private metadata or archived/yanked records.
  3. ReadCompatibility registrybefore changing Joomla, PHP or database version rules.
  4. ReadPlatform stackandAPI referencefor architecture-level work.
  5. ReadInternal seed and migration notesbefore changing baseline data.

Product documentation stays with products

Module and artifact guides live on the corresponding extension documentation page. For example, a CTA module guide should explain CTA fields, presets, actions, template positions and troubleshooting, while this platform documentation explains ExtensionFlow release and update infrastructure.

Browse extension documentation · Open platform changelog · Open roadmap