Issue Epic In Progress

#108915Page Creation Wizard

Andreas Nedbal 02/09/26, 13:52 updated 11/14/26, 10:39

Description

Our current page creation workflow is a barrier to entry for new editors. It is technically complex, not mobile-ready, and fails to guarantee data integrity, resulting in a slow and frustrating ‘time-to-content’ experience.

Our goal is to streamline the page creation process by introducing a guided, accessible, and error-proof wizard that empowers editors to build high-quality page structures without requiring deep technical knowledge.

Goals

Data Integrity and Content Readiness

We want to ensure that all mandatory fields are populated during page creation so that we avoid “broken” or incomplete page records (e.g. missing configurations for news detail pages).

Key Points:
  • Validation of required fields during the creation step.

Intuitive and Guided User Experience

Editors should get a consistent and guided process for creating pages to achieve results quickly without having to navigate complex TYPO3-specific settings.

Key Points:
  • Fast-track to results, avoid unnecessary steps.
  • Standardized workflow for all page types.
  • Zero TYPO3-specific expertise required for basic setup.

Accessibility and Responsive Design

We want to build pages using an interface that follows accessibility guidance and modern web standards.

Key Points:
  • WCAG 2.2-compliant accessibility for the entire wizard workflow.
  • Responsive layout.

Workflow Flexibility and Efficiency

It should be possible to start the wizard from different entry points in the backend, with pre-defined parameters depending on context. Creating multiple pages should also be supported.

Examples:
  • Current Drag&Drop behavior would pre-fill the page type and position.
  • Creating a page from the Records module would pre-fill the position property.
Key Points:
  • Wizard can be repeated, instead of finishing, “Create New Page”, to support a workflow of creating multiple pages.
  • Context-aware start (Wizard respects pre-selected positions or types).

Extensibility and Modularity

The page creation wizard should be modular and extensible, so that integrators can implement custom steps for their own page types or extend existing ones.

Key Points:
  • The concept “page creation wizard” should be implemented generic enough to later be adopted to improve further TYPO3 workflows (e.g., content element creation).
  • Developers should be able to extend existing configuration, but not be able to remove required steps defined by the TYPO3 Core.

Technical Concept: Frontend/User

frontend-user-page-creation-flow-compact.png

Initialization and Type Selection

The process begins with the initialization of the Wizard UI, triggered via different actions in the Backend, the prototype suggesting a new button in the page tree actions. In the first step, the system fetches all available Page Types (doktype) through a fetch request to a JSON endpoint. This ensures that only relevant types, including custom icons and labels, are presented to the user. Once a type is selected, a frontend validation check confirms the choice before moving forward.

Dynamic Content Loading

Upon proceeding, the Wizard sends the selected doktype to the server to determine the specific requirements for the following steps. The goal is to receive a server-side rendered form using the TYPO3 FormEngine. This approach ensures that all TCA-based rules and field configurations are respected.

Positioning and Page Tree Integration

The second step presents a page tree to the user. This allows the user to select an origin and define the exact position, such as “above page”, “below page” or “as subpage”.

Data Entry and Validation

The subsequent steps gather the actual page information, divided into required fields and optional/recommended fields + additional steps. Required fields like the page title and URL slug are handled first, followed by optional metadata or SEO settings. Each transition between these steps is protected by frontend validation to ensure that all mandatory fields are correctly filled according to TCA requirements.

Review and Persistence

Before any data is written to the database, a summary screen provides an overview of all entries. This allows the user to verify the page type, position, and values at a glance. Once confirmed, the data is transmitted to the the TYPO3 DataHandler to create the record, ensuring that all system hooks and permission checks are properly executed.

Success Feedback and Workflow

The final step informs the user of a successful creation through a clear feedback message. Instead of simply closing the Wizard, the UI offers contextual follow-up actions. The user can choose to jump directly into the Layout Module to add content, start the process over to create another page, or exit the Wizard to return to their previous task.

Technical Concept: Backend

Naming of the class and method names below is not final and open to discussion.

  • A generic WizardController will be called as soon as initial data is requested.
    • The controller will be generic, wizard specific logic is to be implemented in WizardProvider classes.
    • Initial data can be anything, in the case of the Page Creation Wizard its the available page types.

Design Pattern:

The generic WizardController has three endpoints. Each endpoint gets passed the wizard type, which is internally resolved to a WizardProvider implementation

Endpoints:
  • Fetching initial data
  • Fetching wizard steps
  • Persisting wizard result
The logic for each endpoint is implemented in a wizard-specific WizardProvider:
  • WizardProviders are resolved using a WizardProviderFactory that gets the requested type passed from the controller
  • The WizardProviders should be tagged with an Attribute that allows the factory to resolve them, e.g. #[AsWizardProvider(wizard: 'page-creation')]
Example PageWizardProvider implementation:
  • Initial data request returns all available page types and their count of steps for the wizard.
  • Wizard step resolving:
    • One wizard step returns all required fields (fields marked as required in TCA)
    • Another wizard step returns all recommended fields (fields marked as recommended in TCA)
    • Markup of these steps should be rendered with FormEngine.
  • Persistance step:
    • Resulting page data should be persisted via DataHandler.

See:
!initialData.png!
!getSteps.png!
persist.png

Reviews 42

Subtasks 43

Files 4

History 6068

Show 3543 earlier messages
  1. Andreas Nedbal changed attached frontend-user-page-creation-flow-compact.png description <span data-processor="relativetime" data-value="2026-02-10T14:36:22+00:00" > 02/10/26, 14:36 </span>

  2. Bastien Lutz changed attached persist.png attached getSteps.png attached initialData.png description <span data-processor="relativetime" data-value="2026-02-11T12:40:12+00:00" > 02/11/26, 12:40 </span>

  3. Florian Keitgen commented and changed status Under Review Resolved done 54 % 100 % <span data-processor="relativetime" data-value="2026-03-23T07:55:11+00:00" > 03/23/26, 07:55 </span>

    Applied in changeset commit:24e5e394d3ba9ef80e85a6763c69f871fd40aacf.