AgilePress

Tag: Full Site Editing (FSE)

  • The AgilePress Theme Protocol: How to Configure a Theme Correctly

    Installing a theme is not the end of the setup; it is barely the beginning. In the era of Full Site Editing (FSE), a theme like Ollie or Frost is just a container. If you start building pages immediately after activating the theme, you are creating technical debt.

    You need a system.

    At AgilePress, we follow a strict Initialization Protocol to ensure every site is performant, GDPR-compliant, and update-proof. Here is the step-by-step guide to configuring your theme the right way.

    Phase 1: Choose Your Architecture

    Before you touch a single color, you must decide how you will relate to the theme. In 2026, you have three paths.

    Option A: The Native Route (Database Only)

    You install the theme (e.g., Ollie) and make all changes directly in the Site Editor. You do not create a Child Theme or a Clone.

    • How it works: Your changes are saved in the WordPress database (wp_global_styles table).
    • Pros: Fastest setup. Zero file management.
    • Cons: If the theme author changes the internal name (slug) of a color or font in a future update, your site might lose those references.
    • Best For: Simple brochure sites, personal blogs, or “Disposable” landing pages.

    Option B: The Child Theme (The Safety Net)

    The classic approach, modernized. You create a minimal Child Theme that holds your theme.json configuration while inheriting the templates from the parent.

    • How it works: You use the Create Block Theme plugin to generate a child theme.
    • Pros: You get security updates and bug fixes from the parent theme, but your design settings are safe in your own files.
    • Cons: Risk of “Inheritance Conflicts” if the parent theme radically changes a template structure.
    • Best For: Twenty Twenty-Five users and GeneratePress users. (Always use Child Themes for PHP-based themes).

    Option C: The Clone (The Agency Standard)

    You take a theme like Frost, and you “Fork” it. You create a copy with a new name (e.g., “ClientName Base”).

    • How it works: You use Create Block Theme -> “Clone current theme”.
    • Pros: Absolute stability. You own the code. No external update can ever break your site visually.
    • Cons: You won’t receive new features added by the original author.
    • Best For: Client Client Sites. When you deliver a project, you want it to look exactly the same in 3 years.

    Phase 2: The “Reset” (Cleaning the Canvas)

    Most FSE themes come with “opinions”—pre-made templates for bold headers, specific blog layouts, etc. We want a blank canvas.

    1. Go to Appearance > Editor > Templates.
    2. Audit the Index & Single: Open the “Index” (Blog Home) and “Single Post” templates.
    3. The Purge: If the design is too complex, select all blocks and delete them.
    4. Rebuild Semantically: Add a simple structure:
      • Header (Template Part)
      • Group (Tag: Main) -> Content Block
      • Footer (Template Part)
    5. Save: This overrides the parent theme’s template in your database.

    Phase 3: The Design System (Global Styles)

    Now, we configure the theme.json visually. Go to Appearance > Editor and click the Styles (Eye/Half-Moon) Icon.

    1. Typography & Local Fonts (GDPR)

    Do not rely on the default fonts.

    • The Old Way: Uploading fonts via FTP to a theme folder.
    • The AgilePress Way: Use the Native Font Library.
      1. Go to Typography > Manage Fonts (Icon).
      2. Click Install Fonts (Connect to Google).
      3. Select your font (e.g., Inter) and click Install.
      4. Crucial Note: When you click “Install,” WordPress downloads the .woff2 files to your server (/wp-content/uploads/fonts/). It does not link to Google. Your visitors will never connect to Google’s servers, ensuring 100% GDPR compliance and better performance.

    2. The Color Palette

    Don’t just pick colors randomly. Define a Semantic Palette:

    • Base: Your background (usually white or slight off-white).
    • Contrast: Your main text (usually dark grey, avoid pure #000000).
    • Primary: The main brand color (Buttons, Links).
    • Secondary: Accents.
    • Tertiary: Subtle backgrounds or borders.

    3. Layout Dimensions

    Go to Styles > Layout.

    • Content Width: Standard is roughly 800px (for readability).
    • Wide Width: Standard is roughly 1200px (for cards and grids).
    • Padding: Set your default root padding so your content never touches the edge of mobile screens.

    Phase 4: Block Defaults (The Secret Weapon)

    This is where you save hours of future work. Instead of styling every button individually on every page, configure the Block Defaults.

    1. In the Styles sidebar, click Blocks.
    2. Search for Button.
    3. Set the default styles:
      • Background: Primary Color.
      • Text: White.
      • Radius: 4px (or Round).
      • Typography: Bold.
    4. Repeat for Headings: Set the default margins for H1, H2, and H3 so your typography always has the correct breathing room.

    Phase 5: Export (Locking it in)

    If you chose Option A (Native), you are done. Your settings are saved in the database.

    If you chose Option B (Child) or Option C (Clone):

    1. Install/Activate the plugin Create Block Theme.
    2. Go to Appearance > Create Block Theme.
    3. Select “Save changes to the theme”.

    This takes everything you just did in the editor (Fonts, Colors, Layout) and writes it into the theme.json file of your active theme. Now, your configuration is code, not just database entries.

    Summary Checklist

    1. Select Strategy: Native (Fast), Child (Safe Updates), or Clone (Total Control).
    2. Reset Templates: Clear out the “opinionated” designs from the Index and Single templates.
    3. Install Fonts: Use the Native Library to download Google Fonts locally.
    4. Define Palette: Set your 5 core semantic colors.
    5. Configure Blocks: Set defaults for Buttons and Headings.
    6. Add Logic: Install FluentSnippets for any PHP/JS needs (Analytics, CPTs).

    By following this protocol, you ensure that your theme is a robust, lightweight foundation for your content, not a bloated cage.

  • The Last Theme You Will Ever Install: Why theme.json Killed ThemeForest

    For the last decade, the WordPress ecosystem told you a lie: “To get a professional design, you need to buy a Premium Theme.”

    So you went to ThemeForest. You bought Avada, The7, or BeTheme. You installed it, and suddenly your dashboard was flooded with “Required Plugins,” sliders you didn’t ask for, and a proprietary “Options Panel” that slowed down your backend.

    Then, two years later, you wanted to redesign. But you couldn’t. Your content was locked inside proprietary shortcodes. You were trapped.

    In 2026, the era of the “Multipurpose Theme” is dead.

    At AgilePress, we don’t buy themes anymore. We install a Base Framework. This is the Full Site Editing (FSE) revolution. Here is the definitive list of what to use, what to avoid, and why.

    Part 1: The AgilePress Standard (Pure FSE Frameworks)

    These themes meet our strict criteria: Native FSE (Blocks only), Zero Bloat, and Zero “Nagging” (no admin banners).

    1. Ollie (Free)

    The Visual Standard. Created by Mike McAlister, Ollie is the most user-friendly entry into FSE. While most FSE themes give you a blank screen, Ollie includes a setup wizard that helps you define your Brand Identity (Colors, Typography) before you start.

    • Best for: Agencies and Implementers who want a beautiful starting point without coding.
    • The Vibe: Modern, clean, and designer-approved.

    2. Frost (Free)

    The Engineering Standard. Backed by WP Engine, Frost is the gold standard for developers. It embraces “Atomic Design.” It exposes powerful utility classes via theme.json that allow you to build complex layouts natively.

    • Best for: Developers building custom client sites.
    • The Vibe: Brutalist, functional, and rock-solid. It will never break because it powers WP Engine’s own demo infrastructure.

    3. Indio & Powder (Free)

    The Minimalist Standard. Brian Gardner (the godfather of WordPress themes) created these. Powder is a raw framework for building from scratch. Indio is its “soulful” brother—a theme that proves minimalism doesn’t have to be cold. It features elegant serif typography and plenty of whitespace.

    • Best for: Blogs, Portfolios, and sophisticated brands.
    • The Vibe: Editorial and calm.

    4. Blockbase (Free)

    The Academic Standard. Created by Automattic (the makers of WordPress), this is the “Universal Parent Theme.” It is designed to be the foundation for Child Themes. It has zero opinion. It is just raw code.

    • Best for: Hardcore developers who want to build their own Child Themes on top of a maintained parent.

    5. Twenty Twenty-Five (Free)

    The “Reset” Protocol. The default WordPress theme. It is maintained by the Core team and will last forever.

    • The Agile Strategy: Install it, go to the Editor, and delete all the templates. Use the “shell” of the theme for its stability, but strip away its opinionated design.
    • Best for: Long-term projects (NGOs, Universities) that cannot risk a theme developer abandoning the project.

    Part 2: The “Hybrid” Kings (The Exception)

    These themes are not Pure FSE. They still use PHP for headers/footers, but they are so performant that we make an exception.

    6. GeneratePress (Freemium)

    The Stability King. Tom Usborne has maintained this for a decade. It is the most stable piece of software in the WordPress ecosystem.

    • Why we use it: For high-stakes business sites (WooCommerce doing $1M+) where we cannot afford the slight “beta” feel of the Site Editor.
    • The Cost: Free version is limited. You need Premium for the real power (Elements).

    Part 3: The “Noisy” Neighbors (Why we avoid them)

    You will see these names everywhere: Astra, Kadence, Neve, OceanWP. Are they bad themes? No. They are technically competent. So, why doesn’t AgilePress recommend them?

    1. The “Freemium” Noise: These themes are businesses. When you install them, they often add banners to your dashboard asking you to upgrade to Pro. AgilePress believes your dashboard should be a sanctuary, not a marketplace.
    2. The “Customizer” Trap: They rely heavily on the old WordPress Customizer (Appearance > Customize). This creates a split experience: you design the header in one place and the content in another. In FSE (Ollie/Frost), everything is the same editor.
    3. Spectra One: This is a good FSE theme, but it is designed to lock you into the Spectra plugin ecosystem. If you use GenerateBlocks or native blocks, it feels like fighting the theme.

    Verdict: Use them if you are already locked into their ecosystem, but don’t start a new project with them in 2026.

    Conclusion: The Final Matrix

    Choosing a theme is not about style; it is about architecture. Here is the AgilePress recommendation based on your profile:

    For Agencies & Implementers: Choose Ollie. It has the best onboarding wizard and the most polished pattern library. It makes your site look expensive immediately.

    For Developers: Choose Frost. It provides the cleanest code and the best utility classes. It is backed by WP Engine, ensuring enterprise-grade longevity.

    For Minimalists & Bloggers: Choose Indio. It offers the most elegant typography and whitespace out of the box. It is pure soul.

    For Enterprise Stability: Choose GeneratePress. If you are running a high-traffic WooCommerce store, stability beats modernity. It is bulletproof.

    For Long-Term Safety: Choose Twenty Twenty-Five. It will never be abandoned. Just remember to use the “Reset Protocol” (delete the templates) to remove its default styling.

    The AgilePress Rule: The best theme is the one you don’t notice. It should be a ghost frame for your content. Stop buying style; start building systems.

  • The ThemeForest Trap: Why “Multipurpose” Means “Future Debt”

    We have all been there. You (or your client) browse ThemeForest. You see a $59 theme called “Titan” or “Jupiter” or “Avada” that promises 500+ pre-built demos.

    It looks incredible. It has sliders, flying animations, and a portfolio grid that spins. You buy it, install the demo, and suddenly… you are trapped.

    In the WordPress world, the theme you choose dictates your site’s destiny. And for years, the industry has been pushing “Multipurpose Themes”—Swiss Army Knives that try to do everything but end up doing nothing well.

    At AgilePress, we have moved on. We don’t use “Multipurpose” monoliths. We don’t use “Hybrid” crutches. We build with the future of WordPress: Full Site Editing (FSE).

    Here is a breakdown of the market and why we ditched the best-sellers for a new generation of minimalist block themes.

    The Monoliths: Avada, Enfold, and Divi

    These are the giants of the past decade. They are massive software suites disguised as themes.

    • The Suspects: Divi, Avada, The7, Enfold, BeTheme.
    • The Trap: To make those 500 demos work, they ignore native WordPress standards and force their own proprietary systems (Fusion Builder, Divi Builder, Muffin Builder).
    • The “Lock-In” Nightmare: If you ever switch themes, your content disappears. You are left with a mess of “shortcodes” ([et_pb_section]...[/et_pb_section]) that are unreadable. You are married to that theme forever.
    • The Performance Cost: They load megabytes of CSS and JavaScript just to render a simple About page. It is like buying a bus to drive one person to work.

    The Empty Shell: “Hello Elementor”

    Then came the reaction. Developers wanted speed, so Elementor released “Hello Elementor”.

    • The Promise: It is super lightweight. Almost zero code.
    • The Reality: It is a Trojan Horse designed to make you 100% dependent on Elementor Pro.
      • Because the theme has no styling, no header logic, and no footer logic, you must build everything with the heavy Elementor Page Builder.
      • You are not using WordPress anymore; you are using Elementor. If you stop paying their subscription, your entire site breaks.

    The “Hybrids”: Kadence, GeneratePress, Neve & Blocksy

    We have huge respect for this category. For years, these were the “Agile” choice.

    • The Suspects: Kadence, GeneratePress, Neve, Blocksy, Astra.
    • The Good: They are incredibly fast, well-coded, and much lighter than the Monoliths. They respect WordPress standards much better than Divi.
    • The Friction: They are “Hybrid” themes. They try to bridge the gap between the old “Classic PHP” world and the new “Block” world.
      • You control the Header/Footer in the Customizer (Old way).
      • You control the content in the Block Editor (New way).
    • Why we moved on: Working with them now feels like straddling two eras. While excellent tools, they rely on PHP templates that limit the true flexibility of the new WordPress. They represent the peak of the past, not the foundation of the future.

    The Future: Native Block Themes (FSE)

    This is the AgilePress Standard.

    With WordPress 6.0+, the platform became a full design engine. We use Full Site Editing (FSE) themes like Twenty Twenty-Five, Ollie, Frost, or Spectra One.

    Why are these superior?

    • Zero PHP Bloat: These themes are mostly HTML and JSON configuration files. There are no heavy PHP functions running in the background. They are blazingly fast by default.
    • Visual Control: You edit the Header, Footer, and Templates using the same block editor you use for posts. No more jumping between “Theme Options,” “Customizer,” and the editor.
    • Portability: Everything is standard WordPress blocks. If you switch from Ollie to Twenty Twenty-Five, your content still works. Your layout might change, but your data is safe.
    • Design Systems, Not Demos: Instead of importing a heavy “Demo Site,” we import lightweight Global Styles (fonts, colors, spacing). We define the system, and the site builds itself consistently.

    Conclusion: Don’t Buy a Theme, Adopt a Framework

    The era of buying a $59 theme that “does it all” is over. Those themes are technical debt waiting to happen.

    At AgilePress, we use modern, native Block Themes.

    • We use Ollie for its incredible UX.
    • We use Frost or Spectra One for clean, agency-style minimalism.
    • We use Twenty Twenty-Five for maximum longevity.

    We don’t build sites that look good only on the launch day. We build sites that remain fast, editable, and standard-compliant for years to come.

    The theme is dead. Long live the Blocks.