CloudFest
Hackathon 2026
Proposal

Redesigning Extension Pages
on typo3.org

A proposal to improve extension detail pages on extensions.typo3.org — informed by competitive analysis of WordPress.org, VS Code Marketplace, and Shopify App Store.

by Joost de Valk
CloudFest Hackathon — March 2026

What's in this proposal

Homepage
Discovery & curation

Curated sections replacing the raw upload feed: featured extensions, categories, most popular, and recently updated.

Search Results
Filtering & browsing

Scannable list view with modern filters, sort controls, and cleaner result cards showing the info that matters.

Extension Detail Page Examples

Y
Yoast SEO for TYPO3
SEO analysis & content optimisation

A well-known commercial extension with a smaller but active user base. Shows how branding and screenshots would work.

v11.1.0 1.3M+ downloads ♥ 26
N
News system
Extbase & Fluid news management

The most downloaded TYPO3 extension, with broad version support back to 6.2. Shows how a mature community extension would look.

v14.0.1 3.7M+ downloads ♥ 145
C
Container
Custom container content elements

A popular developer-focused extension by b13 for building grid layouts. Shows how a technical utility extension would look.

v3.2.2 2.8M+ downloads ♥ 77

The problem

The TYPO3 Extension Repository (TER) at extensions.typo3.org serves three key functions: helping people discover extensions, helping them evaluate and compare options, and helping them install. The current site underserves all three.

Homepage & discovery

The homepage is a raw chronological feed of recently uploaded extensions — not recently updated, but uploaded. There are no featured extensions, no curated categories, and no "most popular" or "trending" sections. A new visitor has no way to discover the ecosystem's best work. The result: extensions.typo3.org functions as a lookup tool for people who already know what they want, not as a marketplace that helps people find what they need.

Search & filtering

Search results appear in a two-column card grid where each card is dominated by TYPO3 version badges and a large orange download bar. The actual information that helps someone decide — description, author, download count, last update date — is secondary. Sort options are loose pills in a sidebar rather than a proper dropdown. Filters are text badges with counts, not clean checkboxes. The result layout wastes space and makes it hard to scan and compare extensions quickly.

Extension detail pages

The most prominent content above the fold is TYPO3 version compatibility — phrased confusingly as "This version supports TYPO3" — followed by a composer command, tags, and a download chart. There are no screenshots, no header images, no structured description, and no tabbed navigation. A developer evaluating an extension is trying to answer: What does it do? What does it look like? Is it maintained? How do I install it? Does it work with my TYPO3 version? The current page answers only the last two — and puts them first.

Competitive Analysis

How other extension/plugin marketplaces handle homepage discovery, search, and detail pages

WordPress.org

wordpress.org/plugins

The gold standard for CMS plugin directories, strong across all three page types.

  • Home: Featured, Popular, Favorites sections with category tabs
  • Search: List view, active install counts, "tested with" version, star ratings
  • Detail: Banner image, screenshot gallery, tabbed content, sidebar metadata
  • Star ratings and review system across all views
  • Active installations metric (not just downloads)

VS Code Marketplace

marketplace.visualstudio.com

Developer-focused but strong on curation and search UX.

  • Home: Featured, Most Popular, Recently Added, Trending sections
  • Search: Sortable results with install count and rating inline
  • Detail: README-driven content, tabs, one-click install, publisher badges
  • Category browsing with extension packs
  • No hero/banner images on detail pages

Shopify App Store

apps.shopify.com

The most polished of all — treats apps as products, not code packages.

  • Home: Staff picks, trending, curated collections, categories
  • Search: Compact cards with rating, pricing, and install count
  • Detail: Video + screenshot gallery, review responses, pricing tiers
  • "Works with" compatibility and single prominent CTA
  • Developer-facing analytics dashboard

TYPO3 TER (Current)

extensions.typo3.org

Functional but focused on raw data rather than user decision-making.

  • Home: Raw upload feed, no curation, no featured/popular sections
  • Search: 2-col grid dominated by version badges, loose filter pills
  • Detail: No screenshots, no banner, no tabs, compat info above description
  • No ratings, reviews, or quality signals
  • Composer command visible, download stats, version history

Proposed Changes

Homepage

1. Add a prominent search-first hero

The current homepage opens with a plain list of extensions sorted by last update date. There is no clear call to action and no visual hierarchy. The redesign leads with a bold search bar and a clear value proposition ("Over 2,500 free extensions"), making search the primary interaction — just as users expect from any modern marketplace or app store.

BeforeA flat list of recently updated extensions. No hero, no search prominence, no editorial curation.
AfterFull-width hero with centered search. Immediate signal of scale and purpose.

2. Introduce browsable categories

There is currently no way to browse extensions by category from the homepage. Users either search or scroll through a chronological list. Adding a visual category grid (Backend, Frontend, Content, SEO, E-Commerce, Security, Communication, Developer Tools) lets users explore by intent, which is especially valuable for newcomers who don't yet know what to search for.

BeforeNo categories on the homepage. The only way to filter is via the search page.
AfterAn 8-category grid with icons, enabling intent-based browsing from the first page.

3. Curate featured, popular, and recent extensions

WordPress.org, VS Code Marketplace, and Shopify all use editorial curation on their homepages — featured picks, trending items, and recent updates. The current TER homepage has none of this. Adding "Featured Extensions," "Most Popular," and "Recently Updated" sections creates social proof, surfaces quality, and gives returning visitors a reason to check back.

4. Switch to a list-based result layout with richer metadata

The current search results show extension names with minimal context — no descriptions, no download counts, no version info. The redesign uses a single-column list where each result shows the extension name, author, description excerpt, download count, version, and TYPO3 compatibility at a glance. This mirrors how WordPress.org and npm present results: enough information to evaluate without clicking through.

BeforeSparse list with extension name, version, and a truncated description. No visual hierarchy.
AfterRich result cards with icon, author, download stats, version, compatibility badges, and description.

5. Add sidebar filters and sort controls

The current search has no filtering options and no way to sort results. The redesign adds a persistent sidebar with checkbox filters for TYPO3 version, category, and stability, plus a sort dropdown (Relevance, Most Downloads, Recently Updated, Most Liked). This brings the TER in line with every modern marketplace and dramatically improves the ability to find relevant extensions.

6. Show composer commands inline with copy buttons

Composer is the standard installation method for modern TYPO3 extensions. Showing the composer require command directly in each search result — with a one-click copy button — removes a step from the workflow. Developers can find and install an extension without ever visiting the detail page. This is a small change with high impact on daily developer experience.

Extension Detail Pages

7. Add a header image that doubles as og:image

Every major plugin marketplace (WordPress.org, Shopify) leads with a visual. This immediately communicates what the extension is about before the visitor reads a single word. By requiring the same image to work as the og:image, extension authors are incentivized to create high-quality marketing assets that improve sharing on social media, Slack, and other platforms.

BeforeText-only title with small icon. No visual context. Social shares show a generic TYPO3 logo.
AfterFull-width branded banner with screenshot preview. Social shares show the extension's own branding.

8. Add a screenshot carousel

Screenshots are the single most important decision-making tool for someone evaluating whether to install an extension. WordPress.org has a dedicated Screenshots tab. Shopify leads with screenshots and video. The current TYPO3 TER has zero visual content — you have to install the extension to find out what it looks like.

BeforeNo screenshots. Users must install or find third-party resources to see what the extension looks like.
AfterScrollable carousel on the Overview tab + a dedicated Screenshots tab. Lightbox for full-size viewing.

9. Reorganize information by audience priority

The target audience for an extension page is a TYPO3 developer or integrator deciding whether to install. Their decision process is roughly: (1) what does it do? (2) what does it look like? (3) is it actively maintained? (4) how do I install it? (5) does it work with my TYPO3 version? The current page puts #5 at the very top and skips #1 and #2 entirely.

BeforeOrder: version compat → composer command → tags → "last upload comment" → download chart → installation → version history
AfterOrder: hero image → title + key stats → screenshots → description → changelog. Compat and install in sidebar. Stats behind a tab.

10. Move TYPO3 compatibility to the sidebar

The current "This version supports TYPO3" and "Older versions also support TYPO3" blocks take up prime real estate above the fold with confusing wording. Moving it to a sidebar card with clearer labels keeps it accessible without dominating the page. Older version compatibility is collapsed by default.

11. Add tabbed navigation and consolidate sidebar actions

Both WordPress.org and VS Code Marketplace use tabs to organize content (Overview, Screenshots, Installation, Version History, Stats). This reduces scroll fatigue and creates logical sections. The sidebar is also consolidated: 7 large colored buttons become a focused Install card (composer command + download) and a Resources card (icon-labeled links).

Cross-cutting

12. Future consideration: Ratings and reviews

Every major marketplace has user ratings. The TYPO3 TER currently has no review system — only a "heart" count. Adding even a simple star rating system would improve the ability to evaluate extension quality across search results and detail pages alike. This is a larger feature that could be phased in separately, but the designs should anticipate it.