--- title: LolaCore for FSE canonical_url: https://lolacore.com/lolacore-for-fse/ last_updated: 2026-06-30T14:44:36+00:00 plugin_version: 1.2.2 --- # LolaCore for FSE LolaCore for FSE · Free Add-on · Requires LolaCore Orchestrate your block theme by conversation. ============================================= Describe a site-wide change and Lola edits the template, header part, global palette, and navigation in one reviewed pass: a seasonal refresh on a client block theme, a header reorder without opening four Site Editor screens, a palette swap that keeps typography and spacing intact. She remembers what your team customized last time, so you pick up the thread instead of re-learning the site from scratch. [ Get it free → ](https://lolacore.com/install-lolacore-for-fse) [ See what Lola can do → ](#fse-demo) ● 17 capabilities across 5 FSE layers● Works on any WordPress 7.0 block theme● wp-admin chat and MCP from your code editor ![LolaCore for FSE](https://lolacore.com/wp-content/uploads/2026/06/LolaCore-for-FSE.png) The Problem You think in whole-site changes. Full Site Editing makes you click them out one panel at a time. ------------------------------------------------------------------------------------------------ When a client asks for a seasonal refresh, the sentence is already in your head: "warmer palette, category template update, banner in the header." WordPress can do all of that. What the Site Editor asks of you first is the panel tour: templates on one screen, template parts on another, global styles in a third, navigation in a fourth. Multiply that across every client site you maintain, every "quick change," every theme you have not opened in three weeks. One real cross-layer refresh is forty minutes of clicking. Three client sites before lunch is most of a morning that never lands on an invoice. And when something looks wrong after a deploy, you are back in the editor, opening revisions screen by screen, reconstructing which layer changed. LolaCore for FSE removes that translation step. Same WordPress. Same blocks. Same theme structure. You stopped clicking through panels and started talking. You say the sentence to Lola, she shows you exactly what will change across layers, edits after you confirm, and points you to native Site Editor revisions for undo. Demo What changes when Lola handles your block theme ----------------------------------------------- One sentence, three Site Editor layers ![](https://lolacore.com/wp-content/uploads/2026/05/lolacore-favicon.png)LolaCross-layer refreshRefresh the category template for autumn. Warmer palette, and a seasonal banner in the header.![](https://lolacore.com/wp-content/uploads/2026/05/lolacore-favicon.png)That spans three layers of your block theme. Here is what I would change: 1. Global styles: swap to the warmer palette. Typography and spacing stay as they are. 2. Header part: add the seasonal banner above the navigation. 3. Category template: keeps its structure and picks up the new palette on its own. Apply all three, or start with the palette?All three.![](https://lolacore.com/wp-content/uploads/2026/05/lolacore-favicon.png)Saved. Each change rolls back from Site Editor, then Revisions. Want me to keep this warmer palette as the client's autumn set, so next year it is one sentence?✓ 3 layers merged · palette + header + template · purpose stored in memoryYou described a site-wide refresh in one breath. Lola mapped it to the right FSE layers, merged global styles without wiping typography, and saved with native revision history intact. Same abilities from Claude Code, Cursor, or any MCP client Claude Code · MCP\* Connected to LolaCore MCP on client-site.local> read the category template and summarize the header part it uses● lolacore-fse/get-template Category template renders the query loop at Wide content width. Header part: header-primary (site logo, primary navigation, search block).> move the search block to the end of the nav, after the last link● lolacore-fse/edit-template-part Preview: search block moved after last nav link in header-primary. Confirm to save? Undo stays in Site Editor revisions.\* Waiting for confirmation…>The developer stays in the terminal. Read a template, edit a header part, merge a palette into theme.json, reorder navigation, without opening wp-admin. Same LolaCore ability layer as the chat inside WordPress. Pick up the thread on a client site you have not touched in a month ![](https://lolacore.com/wp-content/uploads/2026/05/lolacore-favicon.png)LolaMemoryI have not opened this site in weeks. What is going on with the front page template?![](https://lolacore.com/wp-content/uploads/2026/05/lolacore-favicon.png)It is a customization of the theme default. It stacks a hero pattern, a three-column feature row, then the latest-posts loop. Last time here you pulled the hero into its own synced pattern called 'home-hero' so you could reuse it. It is still in use on two other pages.✓ Template summary · synced pattern reuse tracedYou did not scroll the Site Editor tree from scratch. Lola remembered the customized template, the synced pattern split, and where that pattern still lives. Two surfaces One addon. wp-admin and your code editor. ----------------------------------------- LolaCore for FSE is a mirror. Every ability Lola uses in the WordPress admin chat is registered over MCP, so your team manages site architecture from the tools they already work in. The account manager or designer on the same team works in the Lola chat inside WordPress admin. Same abilities, same client site, both surfaces. Everyone on your team works in the tool they are fastest in. wp-admin Lola chat inside WordPress Account managers and designers work in the Lola panel they already use. Same confirmation flow, same memory, same revision-based undo. MCP Your code editor or terminal Developers drive the same `lolacore-fse/*` abilities from Claude Code, Cursor, or any MCP client. One addon, both surfaces, the same client site. Cross-domain A flat category page is rarely just a template problem. ------------------------------------------------------- When a layout change underperforms, the cause often lives somewhere else: traffic held steady but bounce spiked, a pattern change pushed content below the fold, a redirect sent visitors elsewhere. Lola has affinity declared with Statistics and content, so when an FSE finding overlaps another domain she follows it across. ![](https://lolacore.com/wp-content/uploads/2026/05/lolacore-favicon.png)LolaCross-domainWe pushed the autumn palette live yesterday. Category traffic looks flat. Is the template the problem?![](https://lolacore.com/wp-content/uploads/2026/05/lolacore-favicon.png)Category template and global styles saved correctly. I cross-checked with Statistics: /product-category/autumn/ had 340 views this week, steady with last week. Bounce rate jumped from 41% to 68% after the hero pattern swap on the category template. The traffic is there. Visitors are leaving before the loop. The palette is fine. The layout change above the product grid is the signal worth reviewing.✓ Template ruled in · traffic steady · bounce spike correlated The template save was the starting point. The real finding was page behavior after the hero swap. Lola connected theme edits and traffic because she reads both sides in one conversation. Execution layer Lola edits the theme layer. The Site Editor stays where it is. -------------------------------------------------------------- Lola edits the five layers of a block theme by conversation: templates, template parts, synced patterns, global styles, and block navigation menus. The Site Editor remains the hand-editing surface for the work you want to do by hand. Lola is the faster path for the change you already know you need. She takes the repetitive panel-hopping off your team's day and returns those hours to architecture and design. Capabilities 17 capabilities across 5 FSE layers. ------------------------------------ Every capability works in the wp-admin chat and over MCP. Global style merges preserve typography and spacing. Template and part writes use native Site Editor revision history for undo. Site Editor status Block-theme detection, active stylesheet, template and part counts, and whether custom global styles already exist. Lola checks this before proposing any change. Templates & template parts List, read, edit, and reset block templates. List template parts by area (header, footer, sidebar). Edit header or footer parts with preview and confirmation before save. Global styles (theme.json) Read user global styles. Merge palette, typography, or spacing changes into existing theme.json. List and apply named style variations from the active theme. Patterns & page context List synced patterns with usage map. Create and update reusable blocks. Read page and post block trees for context (read-only; page content editing stays with LolaCore core). Navigation List block Navigation menus with link labels and URLs. Add, remove, or reorder links with confirmation and revision-based undo. Memory Lola remembers what your team customized ---------------------------------------- Every template tweak, palette choice, and synced pattern split leaves a trace. Not the raw markup, the purpose: the client's autumn set, the header reorder, the home-hero pattern split. Open a client site you have not touched in a month and Lola already carries its context, so you start from where you left off. The more client sites you run, the more that gap costs you, and the more this matters. The memory lives inside your WordPress install. It decays over time so old context fades, and it updates as you keep working. Safety Every write shows a preview and waits for your confirmation ----------------------------------------------------------- Editing a template, updating a header part, merging global styles, changing a synced pattern, reordering navigation: every write action passes through a confirmation step. Lola shows you exactly what will change before it changes. Templates, template parts, global styles, and navigation menus keep WordPress core's native revision history. After a change, Lola points you to Site Editor revisions where you can roll back. Read actions, including template summaries and Site Editor status, run directly. Requirements What you need ------------- LolaCoreFree, active on the same siteWordPress7.0 or higherPHP8.1 or higherBlock themeRequired for templates, parts, and global styles Full Site Editing is built into WordPress. This addon talks to core's Site Editor directly. The only things you install are LolaCore and this add-on. On a classic theme, pattern abilities and page reads keep working; template and global-style editing applies to block themes. For developers If you already work in a code editor ------------------------------------ Most of this page is written for the agency team maintaining client block themes. If you work through MCP already, three things matter. First, every capability runs against WordPress core FSE primitives: block templates, template parts, global styles, synced patterns, and block navigation. Same data, same revision history, no scraping, no bypassed internals. Second, abilities register as `lolacore-fse/*` through LolaCore's Abilities API. Your wp-admin chat and any connected IDE client share the same LolaCore ability layer. Third, this add-on does not run standalone. It needs LolaCore active, because LolaCore is what publishes the MCP server. Frequently asked questions Questions --------- Do I need LolaCore to use this? Yes. This addon adds the FSE domain to LolaCore. Install and activate LolaCore first. Do I need a separate plugin for Full Site Editing? Full Site Editing is built into WordPress 7.0. This addon talks to core's Site Editor through its PHP functions. Install LolaCore and this add-on. Can my team use it from Claude Code, Cursor, or another MCP client? Yes. The same abilities Lola uses in wp-admin are registered for MCP. Developers read templates, edit parts, merge global styles, and update navigation from a code editor or terminal. Who is this addon for? Anyone with a block theme can use it. It is built for developers, freelancers, and agencies whose week is template tweaks, theme.json edits, and navigation tickets across client sites. Do I need a block theme? For editing templates, template parts, and global styles, yes. On a classic theme, Lola reports the active theme type honestly and still reads and edits synced patterns and page block trees. What happens if I make a change I do not like? Templates, template parts, global styles, and navigation menus keep WordPress core's native revision history. Lola points you to Site Editor revisions where you can roll back. Can Lola edit the content of my pages and posts? She reads page and post block trees for context. Page content editing stays with LolaCore core's content tools. This addon focuses on the theme layer. Will a color change wipe out my fonts and spacing? Global style changes merge into your existing theme.json. A palette edit changes the palette and keeps your typography and spacing exactly as they were. Does this send my site anywhere? Reads and writes run inside your WordPress install through WordPress core's own functions. When you chat with Lola, your messages go to the AI provider you configured in WordPress itself. Orchestrate your block theme by conversation. --------------------------------------------- Install the add-on and Lola discovers all 17 capabilities automatically. There is no settings page to configure. [Get it free →](https://lolacore.com/install-lolacore-for-fse)Don't have LolaCore yet? LolaCore is the free AI agent that lives inside your WordPress admin. It reads your site, takes action with your approval, and remembers everything across sessions. [Get LolaCore free →](https://wordpress.org/plugins/lolacore) LolaCore for FSE is an independent add-on for WordPress Full Site Editing. It integrates with WordPress core. It is not built or endorsed by the WordPress project.