Need help with flynt?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

431 Stars 48 Forks MIT License 2.2K Commits 5 Opened issues


Component based WordPress starter theme, powered by ACF Pro and Timber, optimized for a11y and fast page load results.

Services available


Need anything else?

Contributors list


standard-readme compliant Build Status Code Quality

Short Description

Flynt is a WordPress theme for component-based development using Timber and Advanced Custom Fields.

Table of Contents


  1. Clone this repo to
  2. Change the host variable in
    to match your host URL:
    const host = 'your-project.test'
  3. Navigate to the theme folder and run the following command in your terminal:
    # wp-content/themes/flynt
    composer install
    npm i
    npm run build
  4. Open the WordPress back-end and activate the Flynt theme.
  5. Run
    npm run start
    and start developing. Your local server is available at



In your terminal, navigate to

and run
npm start
. This will start a local server at

All files in

will now be watched for changes and compiled to the
folder. Happy coding!

Flynt comes with a ready to use Base Style built according to our best practices for building simple, maintainable components. Go to

to see it in action.



folder contains all global JavaScript, SCSS, images, and font files for the theme. Files inside this folder are watched for changes and compile to


file is compiled to
which is enqueued in the front-end.


file is compiled to
which is enqueued in the administrator back-end of WordPress, so styles added to this file will take effect only in the back-end.

Lib & Inc


folder includes helper functions and basic setup logic. You will most likely not need to modify any files inside
All files in the
folder are autoloaded via PSR-4.


folder is a more organised version of WordPress'
and contains all custom theme logic. All files in the
folder are automatically required.

For organisation,

has three subfolders. We recommend using these three folders to keep the theme well-structured:
  • customPostTypes

    Use this folder to register custom WordPress post types.
  • customTaxonomies

    Use this folder to register custom WordPress taxonomies.
  • fieldGroups

    Use this folder to register Advanced Custom Fields field groups. (See Field Groups for more information.)

After the files from

are loaded, all components from the
folder are loaded.

Page Templates

Flynt uses Timber to structure its page templates and Twig for rendering them. Timber's documentation is extensive and up to date, so be sure to get familiar with it.

There is one Twig function added in Flynt to render components into templates: *

renderComponent(componentName, data)
renders a single component. For example, in the

Besides the main document structure (in

), everything else is a component.


A component is a self-contained building-block. Each component contains its own layout, its ACF fields, PHP logic, scripts, and styles.

  ├── functions.php
  ├── index.twig
  ├── screenshot.png
  ├── script.js
  ├── style.scss


file for every component in the
folder is executed during the WordPress action
. This is run from the
file of the theme.

To render components into a template, see Page Templates.

Advanced Custom Fields

Defining Advanced Custom Fields (ACF) can be done in

for each component. As a best practise, we recommend defining your fields inside a function named
which you can then call in a field group.

For example:

namespace Flynt\Components\BlockWysiwyg;

function getACFLayout() { return [ 'name' => 'blockWysiwyg', 'label' => 'Block: Wysiwyg', 'sub_fields' => [ [ 'label' => __('Content', 'flynt'), 'name' => 'contentHtml', 'type' => 'wysiwyg', 'delay' => 1, 'media_upload' => 0, 'required' => 1, ], ] ]; }

Field Groups

Field groups are needed to show registered fields in the WordPress back-end. All field groups are created in the

folder. Two field groups exist by default:

We call the function

defined in the
file of each component to load fields into a field group.

For example:

use ACFComposer\ACFComposer;
use Flynt\Components;

add_action('Flynt/afterRegisterComponents', function () { ACFComposer::registerFieldGroup([ 'name' => 'pageComponents', 'title' => 'Page Components', 'style' => 'seamless', 'fields' => [ [ 'name' => 'pageComponents', 'label' => __('Page Components', 'flynt'), 'type' => 'flexible_content', 'button_label' => 'Add Component', 'layouts' => [ Components\BlockWysiwyg\getACFLayout(), ] ] ], 'location' => [ [ [ 'param' => 'post_type', 'operator' => '==', 'value' => 'page' ], [ 'param' => 'page_type', 'operator' => '!=', 'value' => 'posts_page' ] ] ] ]); });

Here we use the ACF Field Group Composer plugin, which provides the advantage that all fields automatically get a unique key.

ACF Option Pages

Flynt includes several utility functions for creating Advanced Custom Fields options pages. Briefly, these are:

  • Flynt\Utils\Options::addTranslatable

    Adds fields into a new group inside the Translatable Options options page. When used with the WPML plugin, these fields will be returned in the current language.
  • Flynt\Utils\Options::addGlobal

    Adds fields into a new group inside the Global Options options page. When used with WPML, these fields will always be returned from the primary language. In this way these fields are global and cannot be translated.
  • Flynt\Utils\Options::getTranslatable

    Retrieve a translatable option.
  • Flynt\Utils\Options::getGlobal

    Retrieve a global option.

Timber Dynamic Resize & WebP Generation

Timber provides a

filter to resize images on first page load. Resizing many images at the same time can result in a server timeout.

That's why Flynt provides a

filter, that resizes images asynchronously upon first request of the image itself. The filter optionally generates additional WebP file versions for faster loading times.

Resized images are stored in

. To regenerate all image sizes and file versions, delete the folder.

To enable Dynamic Resize and WebP Support, go to Global Options -> Timber Dynamic Resize. ​


​ If

is enabled and image requests result in 404 errors, try the following solutions: ​ 1. If you're using nginx and the server (not WordPress) responds with a 404 error, check your server configuration against the recommended standard. If the standard configuration cannot be used, resolve the image requests correctly by adding the following rule to your configuration:
location ~ "^(.*)/wp-content/uploads/(.*)$" {
  try_files $uri $uri/ /index.php$is_args$args;
  1. Some plugins (like WPML) manipulate the
    in such a way that
    cannot resolve the path to images correctly. In that case, set the relative upload path manually in Global Options -> Timber Dynamic Resize. Example: The relative upload path in Bedrock installs with WPML needs to bet set to



In some setups images may not show up, returning a 404 by the server.

The most common reason for this is that you are using nginx and your server is not set up in the default way. You can see that this is the case, if an image url return a 404 from nginx, not from WordPress itself.

In this case, please add something like

location ~ "^(.*)/wp-content/uploads/(.*)$" {
  try_files $uri $uri/ /index.php$is_args$args;

to your site config.

Other issues might come from Flynt not being able to determine the relative url of your uploads folder. If you have a non-standard WordPress folder structure, or if you use a plugin that manipulates

(for example, WPML) this can cause problems when using

In this care try to set the relative upload path manually and refresh the permalink settings in the back-end:

add_filter('Flynt/TimberDynamicResize/relativeUploadDir', function () {
    return '/app/uploads'; // Example for Bedrock installs.


If browsersync is not working and you are not serving WordPress on https, try changing the

value to
in the file


This project is maintained by bleech.

The main people in charge of this repo are: * Steffen Bewersdorff * Dominik Tränklein


To contribute, please use GitHub issues. Pull requests are accepted. Please also take a moment to read the Contributing Guidelines and Code of Conduct.

If editing the README, please conform to the standard-readme specification.


MIT © bleech

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.