New Pro + Launch: pick a template and our developers set up your site in 2 business days.
See how it works
Design · Front-end development

Front-ends that stay fast, accessible and editable in Joomla

From your Figma to a Joomla template: T4 and Bootstrap 5, clean overrides, small web components instead of plugin soup, and assets loaded through the Web Asset Manager. Editors keep working in Joomla; Core Web Vitals stay green.

Reviews on Trustpilot →

View:

Home / 1440Figma file → design tokens: brand #0b3b5b, accent #f2a93b, headings Inter 800, spacing 8 · 16 · 32T4 template: html/layouts/hero.php, local/css/custom.css, assets in joomla.asset.json – no page builderEditors own the content: 1 menu, 1 module, 3 custom fields – the layout stays put
Built forNorCal CarciNETWARMTHIGADMarina Bay Cruise Centre SingaporeReelReviews
How we build

From design file to a page your editors own

Agencies send a Figma file and get a template back in their repository.

01 · Design

Your Figma, turned into tokens

States and breakpoints checked; colours, type and spacing become CSS variables.

02 · Build

T4 layouts, overrides, components

Blocks editors can move, overrides only where the HTML must change, components with no jQuery.

03 · Live

Content in Joomla, not in the template

Articles, modules and fields – the team edits; Core Web Vitals stay inside the budget.

Real projects

Front-ends we built

All projects
What we build

A template you can live with for years

Most slow, fragile Joomla sites have the same story: a page builder, ten extensions for small UI pieces and overrides nobody can find. We build the other way.

Template

  • T4 framework, Bootstrap 5, SCSS tokens from your design
  • Layouts and blocks your editors can rearrange
  • Dark mode and RTL when you need them

UI pieces

  • Sliders, tabs, filters as small web components
  • React or Vue only for app-like widgets
  • Every script loaded through the Web Asset Manager

Editors

  • Content stays in articles, modules and custom fields
  • No hard-coded text in templates
  • A short guide for your team
How we build

What every front-end gets

The same checklist on every project, from the first layout to launch.

Design tokens

Colours, type and spacing from your design system, set once.

  • SCSS / CSS custom properties
  • T4 theme settings
  • Figma → tokens

Overrides

Core and extension output rewritten only where the design needs it.

  • templates/*/html/**
  • layouts/** for shared bits
  • documented list

Components

Interactive pieces as small, dependency-free components.

  • custom elements
  • no jQuery
  • progressive enhancement

Assets

One registry for scripts and styles, loaded only where used.

  • joomla.asset.json
  • defer / type=module
  • preload LCP image

Accessibility

Checked by keyboard and screen reader, not only by a tool.

  • WCAG 2.2 AA
  • focus + contrast
  • landmarks + labels

Performance

A budget per template and a measurement before launch.

  • LCP < 2.5s · INP < 200ms
  • CLS < 0.1
  • images: WebP / AVIF, srcset
How it runs

Six steps from design to launch

Agencies can hand us a Figma file and get back a template in their repository.

  1. Design review

    Your Figma or design files checked for states, breakpoints and content that Joomla has to produce.

    You getBuild spec, fixed quote
  2. Template base

    T4 template, tokens, typography, header and footer.

    You getStaging URL, repository access
  3. Layouts & overrides

    Page layouts, blocks and the overrides the design needs.

    You getCommits you can review
  4. Components

    Interactive pieces as web components, registered in the asset manager.

    You getComponent list with usage
  5. Test

    Browsers, devices, keyboard and screen reader, Core Web Vitals.

    You getTest report
  6. Launch & handover

    Go live, editor guide, and the list of every override.

    You getHandover notes
For developers

Assets in the registry, markup in overrides

No inline script tags, no extension shipping its own copy of a library. Every asset has a name, dependencies and loading attributes.

  • Assets declared in joomla.asset.json
  • Used from the override that needs them
  • ES modules, deferred by default
  • Escaped output in every override
{
  "$schema": "https://developer.joomla.org/schemas/json-schema/web_assets.json",
  "name": "tpl_example",
  "version": "1.0.0",
  "assets": [
    {
      "name": "tpl_example.slider",
      "type": "script",
      "uri": "slider.js",
      "attributes": { "type": "module" }
    },
    { "name": "tpl_example.slider", "type": "style", "uri": "slider.css" }
  ]
}
<?php // html/mod_articles_category/slider.php
$app->getDocument()->getWebAssetManager()
    ->useScript('tpl_example.slider')
    ->useStyle('tpl_example.slider');
?>
<px-slider aria-label="<?= htmlspecialchars($module->title) ?>">
  <?php foreach ($list as $item) : ?>
    <a href="<?= $item->link ?>"><?= htmlspecialchars($item->title) ?></a>
  <?php endforeach; ?>
</px-slider>
A news slider as a web component: registered once, used by one module override.
Tools

What we use, and when

The default is the smallest thing that does the job.

ToolWhenWhy
Bootstrap 5DefaultShips with Joomla and T4; editors and extensions already speak it.
Web componentsUI pieces: sliders, tabs, filters, mapsNo framework, no build step for editors, work in any module or article.
React / VueApp-like widgets: configurators, dashboardsMounted inside a module, loaded only on the pages that use it.
TailwindWhen your design system is built on itCompiled and purged per template, not loaded from a CDN.
Page buildersRarelyLayouts get locked in a builder format; we use T4 layouts and modules instead.
Who we work with

Agencies, in-house teams and site owners

Much of our work comes from other developers: agencies with client sites on Joomla, and teams who know their site but want senior Joomla hands for the hard part.

Agencies

We work under your name, in your repository and your ticket system.

  • White-label, NDA on request
  • One quote per site, or for a batch of client sites
  • Your client talks to you – we stay in the background

Developers

Hand us only the hard part and keep the rest.

  • One extension, one integration, or a review of your code
  • Commits and pull requests you approve

Site owners

One team for the whole job, explained without jargon.

  • A fixed quote before work starts
  • Maintenance after launch if you want it
What clients say

Clients on our design and front-end work

Vincenzo Galliano
Vincenzo GallianoCTO at Vivi City Network
“ThePixel led a full revamp of vivi.city … Their technical depth and reliable delivery made a real difference.”
Laravel · API · redesign
Outstanding UI and UX
John BarsonPublisher of Total Health Magazine
“The team is endlessly helpful, flexible and always quick to respond.”
Magazine site · UI/UX
John Brett
John BrettCreator, Curator of HikingAmerica.com
“They’re attentive, creative, and professional, and they really take the time to understand our needs.”
Joomla site · several projects
User-friendly but also incredibly fast
Volker AlsenOwner and CEO of Posada Nena
“They built a stunning website and an efficient travel booking platform for Posada Nena.”
Website + booking platform
Brent Williams
Brent WilliamsChief Insider at Multifamily Insiders
“They do a good job of walking through each new project to fully understand the scope, and then are responsive throughout.”
Several projects, several years
FAQ

Front-end development questions

Not here? Ask in the forum or send us your project.

Can you build from our Figma file?

Yes – that is the usual start. We check it for missing states and breakpoints first, then build the template and overrides from it.

Will our editors still manage content in Joomla?

Yes. Text, images and lists stay in articles, modules and custom fields. Nothing a client changes weekly is hard-coded in the template.

Do you use page builders?

Rarely. They lock layouts into their own format and usually slow pages down. T4 layouts and modules give editors the same freedom without that.

Can you work inside our existing template?

Yes. We add overrides and components to it, or build a child of it, and keep a list of every file we change.

How do you test accessibility?

By keyboard and screen reader on the real pages, plus automated checks, against WCAG 2.2 AA.

Get a quote

Send us the design. We reply in under 12 hours

“The team is endlessly helpful, flexible and always quick to respond.”
John Barson · Magazine site · UI/UX
Reviews on Trustpilot →
  1. 01Send the Figma file or the pages you need, and your Joomla setup.
  2. 02We review it: you get a build spec and a fixed quote.
  3. 03You decide. Nothing starts before you agree to the plan.
Cron Job Starts