Module System and Catalog

Module types

Tagixo includes modules for:

• content (text, heading, image, button, etc.)
• advanced content (accordion, tabs, slider, popup, etc.)
• form fields and form wrappers

Registry behavior

The component registry tracks:

• module identity (id, class)
• label, icon, category
• contexts
• children constraints
• metadata used by the picker and renderer

Context filtering

Module visibility in the builder is context-aware.

If a module is not available in current context, it should not be offered in the picker.

Layout hierarchy

Standard hierarchy:

• section -> row -> column -> module

Special container modules may declare custom child rules.

Catalog planning recommendation

For enterprise usage, define:

• approved base module set
• optional premium modules
• deprecation policy per module

Then expose this policy in team documentation.

Stability tip

When introducing custom modules, avoid changing type IDs in production. Type ID changes can break previously saved structures.