Download the PHP package thelia/backoffice-default-twig-template without Composer

Thelia back-office — Twig template (default-twig)

Modern Bootstrap 5 / Twig / Stimulus port of the legacy Smarty back-office. Lives side by side with templates/backOffice/default/ during the transition.

Activation

URL: https://thelia-3.ddev.site/admin

Architecture

Stack

• Bootstrap 5.3 with overrides aligned on the thelia.net public palette (orange #f26041, soft slate text).
• Bootstrap Icons (1.13).
• Symfony UX (Stimulus, TwigComponent, LiveComponent).
• HTMX 2 for progressive enhancement.
• Symfony forms with the custom bo_form_theme.html.twig theme.

Working on the back-office

Local dev

Adding a new admin domain

The proven recipe (Folder → Content → CustomerTitle → Country → State → Newsletter → Message):

1. Form — src/Form/<Group>/<Name>Type.php: final class extends AbstractType, options include_id / include_description.
2. Controller — src/Controller/<Group>/<Name>Controller.php: #[Route('/admin/...', name: 'admin.X.')]. Inject AdminFormAction, AdminAccessChecker, Environment, FormFactoryInterface, UrlGeneratorInterface, TokenProvider, TranslatorInterface.
3. Methods — list() (GET), create() (POST), updateView({id}) (GET), processUpdate() (POST), delete() (POST/GET), updatePosition() (POST/GET).
4. Events — use $this->action->submit(form: ..., eventFactory: ..., eventName: TheliaEvents::X_CREATE) for forms; $this->action->tokenAction(event: ..., eventName: ...) for single-shot actions.
5. Templates — list.html.twig (DataTable + create modal), edit.html.twig (form_start + form_end).

ACL

Resources live in core/lib/Thelia/Core/Security/Resource/AdminResources.php. Check with is_granted('VIEW', 'admin.foo') or $this->access->check(self::RESOURCE, [], AccessManager::VIEW).

Hooks (back-office)

Twig functions exposed by BackOfficeDefaultTwigBundle\Twig\HookExtension:

Most hook names are kept iso with the legacy Smarty template. The few that were renamed are bridged to their legacy name (see Cohabitation & breaking changes), so third-party modules keep working unchanged.

Hook contract for third-party modules

The back-office emits ~200 native hooks. The conventional extension points a module can rely on are emitted systematically:

Hooks consumed by bundled modules (CustomerFamily, SEOne, HookAdminHome, VirtualProductControl, TheliaBlocks) are all wired. A hook code that is not emitted is considered deprecated for the Twig back-office — open an issue if your module needs one that is missing. The <screen>.js / <entity>.edit-js script hooks are emitted on a per-screen basis as screens are migrated.

Tests

• PHPStan: ddev exec composer phpstan (baseline 60 errors).
• Coding style: ddev exec composer cs / ddev exec composer cs-diff.
• PHPUnit: ddev exec composer test.
• Playwright (BO Twig):

Cohabitation & breaking changes

This template runs side by side with the legacy Smarty back-office. A few names diverge from the legacy ones; here is how third-party modules are affected.

Hooks — bridged, no change required

Renamed hooks are replayed under their legacy Smarty name by Service\Hook\LegacyHookAliases (wired into HookExtension), so a module listening on the old name keeps contributing. Render arguments follow the new (Twig) convention — adapt listeners that read a renamed argument.

The wysiwyg.js hook on the hook-edit screen keeps its legacy wysiwyg-hook-edit-js location.

ACL — bridged

The advanced-configuration screen accepts both the new admin.configuration.advanced resource and the legacy admin.cache one, so existing profiles keep access without a data migration.

Routes — update your module

Renamed route names are not aliased. A module referencing an old name through path() / url() must update it:

The ACL resource for the mailing system stays admin.configuration.mailing-system.

License

LGPL-3.0+ — same as Thelia core.