Building Custom Themes in TYPO3: Step-by-Step

Top TYPO3 Extensions Every Developer Should Know

TYPO3 is a powerful, flexible CMS with a vibrant extension ecosystem that can dramatically speed development and add advanced features. Below are essential extensions every TYPO3 developer should know, why they matter, and practical tips for using them.

1. EXT:news

• Purpose: Content-driven news and blog system.
• Why it matters: Provides a robust, ready-made structure for articles, categorization, tags, and RSS/JSON feeds while integrating smoothly with TYPO3’s routing and templates.
• When to use: Any site requiring posts, announcements, or a blog with flexible frontend rendering.
• Quick tips:
  • Use the provided Fluid templates as a starting point and override partials for custom output.
  • Leverage the category and tag features to power listing filters.
  • Enable caching and configure the plugin’s cache settings for high-traffic sites.

2. EXT:flux (and EXT:fluidpages)

• Purpose: Flexible content element and page configuration using Fluid and FlexForms.
• Why it matters: Flux lets developers define custom content elements and page templates using Fluid, providing fine-grained control over backend forms and frontend rendering without heavy TCA editing.
• When to use: When building custom content elements, changeable page templates, or when you want developers and editors to have a clean, modular setup.
• Quick tips:
  • Combine Flux with VHS (ViewHelpers) for powerful templating helpers.
  • Keep Fluid templates modular; use partials and sections to reuse markup.
  • Document custom fields for editors to reduce confusion.

3. EXT:realurl or EXT:slug

• Purpose: Human-readable and SEO-friendly URLs.
• Why it matters: Clean URLs improve usability and SEO. Depending on TYPO3 version, RealURL (older) or native slug handling (newer versions) manage path generation and routing.
• When to use: Always—SEO and link readability are essential for public sites.
• Quick tips:
  • For TYPO3 v9+ prefer the built-in slug field and routing configuration; RealURL is legacy.
  • Test redirects and reserved slugs to avoid collisions.
  • Implement canonical URLs and hreflang if running multilingual sites.

4. EXT:powermail

• Purpose: Advanced form creation and handling.
• Why it matters: Powermail offers a flexible form builder with validation, conditional logic, file uploads, and hooks for integrations (CRM, mailing systems).
• When to use: Contact forms, surveys, lead capture forms, or any form needing complex behavior.
• Quick tips:
  • Use Ajax submissions for better UX on long forms.
  • Secure file uploads and set limits on file types and sizes.
  • Integrate with external services via powermail hooks or middleware.

5. EXT:solr (Apache Solr) or EXT:fluid_styled_content + EXT:search

• Purpose: Full-text search and advanced indexing.
• Why it matters: For large sites with many pages or documents, a dedicated search engine (Solr/Elasticsearch) delivers fast, relevant results with faceting and advanced relevance control.
• When to use: Large content sites, e-commerce catalogs, or knowledge bases.
• Quick tips:
  • Use field boosting and custom analyzers to improve result relevance.
  • Keep the index up to date via hooks or cron jobs.
  • Provide autocomplete and did-you-mean features for better UX.

6. EXT:mask

• Purpose: Visual content element builder for editors.
• Why it matters: Mask lets editors and developers create custom content elements through a GUI instead of coding TCA manually—great for rapid prototyping and empowering non-technical users.
• When to use: Projects needing many custom content elements defined quickly.
• Quick tips:
  • Use mask for editor-facing elements and Flux for more complex developer-controlled elements.
  • Maintain naming conventions to avoid confusion in the backend.

7. EXT:beuser / EXT:felogin

• Purpose: Backend and frontend user management / authentication.
• Why it matters: Felogin handles frontend user login, registration, and password recovery out of the box; beuser extensions improve backend user handling.
• When to use: Any site with member areas or editorial roles.
• Quick tips:
  • Always enable secure password policies and HTTPS.
  • Use user groups and granular permissions to restrict access properly.
  • Integrate with social login or SSO where required.

8. EXT:masking (Content staging) and EXT:workspaces

• Purpose: Editorial workflows and staging environments.
• Why it matters: Workspaces enable content review and staged publishing, essential for editorial processes and larger teams.
• When to use: Multi-editor sites and workflows requiring review/approval before publishing.
• Quick tips:
  • Define clear workspace stages (draft, review, publish).
  • Train editors on the publish workflow to avoid accidental live changes.

9. EXT:form (Core) and EXT:formhandler

• Purpose: Form management (core extension) and legacy advanced form handling.
• Why it matters: The core Form framework provides drag-and-drop form building integrated with TYPO3, while Formhandler offers advanced processing options for older installations.
• When to use: When you want a supported, integrated form solution or need advanced legacy features.
• Quick tips:
  • Prefer core EXT:form for newer projects.
  • Use custom finisher plugins for integrations like Salesforce or Mailchimp.

10. EXT:seo

• Purpose: Improve on-page SEO metadata and Site configuration.
• Why it matters: Helps manage meta tags, Open Graph, JSON-LD, and sitemap generation, improving search visibility.
• When to use: Any public-facing website.
• Quick tips:
  • Configure per-page meta templates and preview snippets for editors.
  • Generate XML sitemaps and submit them to search engines.
  • Use structured data (JSON-LD) for rich results.

Recommended approach to choosing extensions

1. Assess project needs: Start with requirements (content types, search, workflows).
2. Prefer core or actively maintained extensions: Check TER/GitHub activity and compatibility with your TYPO3 version.
3. Minimize overlap: Avoid multiple extensions that solve the same problem.
4. Performance and security: Review extension code, caching, and injection points.
5. Document and train editors: Provide short guides for any editor-facing extensions.

Final checklist before installing

• Confirm compatibility with your TYPO3 version.
• Check maintenance, open issues, and community adoption.
• Review required PHP/extensions and server requirements.
• Backup before installing and test in a staging environment.
• Configure caching and monitoring after deployment.