A simple accordion built with accessibility in mind. Each accordion panel provides a title and formatted text content, which is toggled with a jQuery slide animation.
A component is a self-contained building-block. As such, each component is kept within its own folder which contains everything it requires; the layout, the Advanced Custom Fields field setup, all necessary WordPress filter and hook logic, scripting, styles, and images.
Flynt is relying on Timber for the template rendering. It’s great, because we don’t have to worry about WordPress loops and can compose page templates by stacking components on top of each other.
So on some page template, you could allow a flexible layout by adding any page component, on another, you could set a fixed header and footer component and only certain components to be placed in between (by specifying a separate Field Group).
Advanced Custom Fields options pages provide a way to create new, extra admin pages in the sidebar of the WordPress back end.
These are useful for creating content fields and settings that only need to be configured once and applied to the whole website. By default, the Flynt Starter Theme supports using two main options pages:
Global Options for fields that should keep the same value in all languages and Translatable Options for all fields that should be translated for each language the website uses (powered by WPML).
Well it could, as ACF has integration support for Gutenberg. But when we implemented that, we didn’t like the look of the backend, as in preview mode, all component fields are squished into the tiny sidebar.