Skip to content
ExtensionFlowJoomla Update Platform
System OK
← Documentation Products and dependencies

Package artifacts and child extensions

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

Documentation Platform changelog Roadmap
01

What it is

A relationship model between a top-level product and the child artifacts it ships or references.

02

Why it helps

The catalog remains readable even when a product has many language packs or supporting plugins.

03

How to navigate

Open the parent product first, then expand artifact groups below the release history when you need child details.

Complex Joomla products often include multiple artifacts. ExtensionFlow keeps the public catalog focused on products while preserving separate version history and documentation for child items when needed.

Artifact groups

  • Language packs belong under the parent product and can be collapsed as a group.
  • Bundled libraries and plugins can be marked required when the parent depends on them.
  • Optional add-ons can keep their own release history while staying visually attached to the parent product.

Why artifacts are below releases

Release history is usually the primary task on a product page. Placing artifacts below releases prevents long lists from forcing users to scroll through dozens of child cards before finding downloads and notes.

Independent child pages

A child item can expose its own detail page, changelog, documentation and update feed when its relationship settings allow that behavior. Otherwise it stays documented through the parent product.