add-template

Customize a Template — Sylius Stack

Ask the user what they want to customize:

• Override an existing block (replace its template)
• Add a new block on a page
• Disable an existing block

To create a new Show page for a resource, use /sylius-stack:add-operation Show instead — it scaffolds the hook and a minimal template.

---

How Twig Hooks work

Sylius admin pages are composed of nested hookable blocks. Each block is attached to a hook name. The admin templates declare two hook names on the same spot — a resource-specific one and a common one:

{% hook ['sylius_admin.book.show.content', 'sylius_admin.common.show.content'] %}

A hookable defined on the resource-specific hook takes priority, so you can target either:

• sylius_admin.{model_snake}.{operation}.{block} → applies only to this resource
• sylius_admin.common.{operation}.{block} → applies to every resource that has no specific override

Hook names can be deeply nested (content.header.title_block.actions) and some hooks use a #fragment notation (sylius_admin.common.create#title). There are also non-CRUD hooks: sylius_admin.base#stylesheets, sylius_admin.common.component.sidebar, sylius_admin.dashboard.index.content, etc.

Discovering hooks

Use sylius:debug:twig-hooks as the source of truth — never guess a hook name:

# List all hooks in the application
bin/console sylius:debug:twig-hooks

# Filter by prefix (all admin hooks, or all hooks for one resource)
bin/console sylius:debug:twig-hooks sylius_admin
bin/console sylius:debug:twig-hooks sylius_admin.{model_snake}

# Inspect one hook: lists its hookables, their template and priority
bin/console sylius:debug:twig-hooks sylius_admin.{model_snake}.show.content

# Add -c to also print context, configuration and props passed to hookables
bin/console sylius:debug:twig-hooks -c sylius_admin.{model_snake}.show.content

# Tree view of the whole hook graph under a prefix
bin/console sylius:debug:twig-hooks -t sylius_admin.{model_snake}