Why this module exists

The original CTA was a static bottom block inside the Baby in Brazil gallery page. It had strong visual design, but it was tied to a single page, a gallery-* CSS namespace and hard-coded content. The module converts that static block into a reusable Joomla extension.

Architecture

Architecture decisions

The package now includes Architecture Decision Records (ADRs). ADRs document why the module uses administrator-generated feature presets, CSS Grid, partial layouts, inline SVG icons, helper-level data normalisation and a JED-preparation strategy without fake update URLs.

Render lifecycle

Template files should not parse raw module params. They receive a normalised $cta array and pass it to smaller layouts.

CTA data contract

The $cta array is produced by CtaHelper::getCtaData(). Keep this structure stable when extending the module; templates and partial layouts depend on it.

$cta = [
  'id' => 'mod-bib-cta-123',
  'moduleId' => 123,
  'preset' => 'birth',
  'variant' => 'default',
  'ariaLabel' => 'Planning to give birth in Brazil',
  'eyebrow' => '',
  'title' => 'Planning to give birth in Brazil?',
  'headingLevel' => 'h2',
  'text' => 'We are here to make your journey safe...',
  'media' => [
    'src' => 'images/cta.jpg',
    'alt' => 'Pregnant couple standing near the water',
    'position' => 'left',
    'fit' => 'cover',
    'width' => 320,
    'minHeight' => 224,
  ],
  'features' => [
    ['enabled' => true, 'icon' => 'check', 'title' => 'Full Support', 'text' => 'Before & During', 'url' => ''],
  ],
  'actions' => [
    ['enabled' => true, 'label' => 'Contact us', 'url' => 'https://...', 'style' => 'primary'],
  ],
  'grid' => [
    'mode' => 'exact',
    'columns' => ['mobile' => 1, 'tablet' => 2, 'desktop' => 4, 'wide' => 4],
  ],
];

PHP API reference

Layouts and overrides

Administrator preset UI

Feature presets intentionally use explicit actions. The select chooses a source; the buttons decide what happens.

The frontend renders only saved repeatable rows. Presets are not dynamic frontend data sources; they are administrator data-entry accelerators.

CSS API

The module is styled with a stable bib-cta namespace and per-instance CSS custom properties.

Presets

Presets currently include birth, services, doctors, hospitals, documents, legal, concierge, apartments, family, newborn, gallery and contact.

When adding a new preset, update all of the following:

• mod_bib_cta.xml — content and feature preset selects.
• CtaHelper::getPresetDefaults() — frontend fallback defaults.
• CtaHelper::getAdminContentPresetDefaults() — admin content-fill payload.
• CtaHelper::getFeaturePresetDefaults() — feature rows for insertion.
• Language files — human labels and descriptions.
• HTML documentation and examples.

Icons

Feature icons and action icons are defined by string identifiers, not by arbitrary SVG input. This keeps admin data safe and predictable.

JED readiness

This package includes a JED preparation checklist and update-server template. Before a public JED submission, the developer still needs to publish real project URLs, documentation URL, demo URL, support URL and update XML/download URL.

• GPL-compatible license file is included as LICENSE.txt.
• No encoded PHP, hidden backlinks or call-home requirement.
• Documentation and examples are included in the package.
• Distribution/update templates are included under dist/update-server/.
• JED submission notes are available in docs/JED_SUBMISSION_GUIDE.html.

Maintenance checklist

• Run PHP syntax checks for all .php files.
• Validate XML manifest and subform XML files.
• Validate media/joomla.asset.json.
• Run a JavaScript syntax check for admin-feature-presets.js.
• Install the ZIP on a clean Joomla site before tagging a release.
• Test all four layouts and all feature preset actions.
• Update CHANGELOG.md, HTML docs and legacy Markdown docs when behavior changes.