


Getting the WordPress Block Editor to Look Like the Front End Design
Apr 01, 2025 am 04:45 AMMake the appearance of WordPress block editor consistent with the front-end design!
As a WordPress user, do you often need to open two tabs at the same time for article editing? One tab shows the new Gutenberg block editor, and the other previews the front-end effect of the article to ensure that the final rendering is not wrong?
WordPress theme styles only affect the front end of the website, and backend editors are usually very different from the front end. But this is not unchangeable! With a custom stylesheet, you can make the WordPress editor mirror the front-end look almost perfectly.
This takes only two simple steps:
- Add a few lines of PHP code to the theme's
functions.php
file to inform the editor to load the custom stylesheet. - Create and configure this custom style sheet.
Let's start!
Step 1: Modify functions.php
file
If you are using a non-self-developed WordPress theme, it is highly recommended that you create a sub-theme before making any modifications to the main theme.
Open the theme's functions.php
file (usually located in the root directory of the theme folder) and add the following code at the end of the file:
// Gutenberg custom stylesheet add_theme_support('editor-styles'); add_editor_style( 'editor-style.css' ); // Make sure the path is correctly pointing to the stylesheet file
This code tells WordPress that you support using custom stylesheets to work with Gutenberg and specifies the location of the stylesheet file ( editor-style.css
).
Step 2: Write CSS Style
Now, we enter the CSS writing process.
Due to the wide variety of WordPress themes, it is impossible to write a style sheet that works for all themes. The following example is based on the topics used by my website and hopefully helps you understand how to build style sheets for your website. At the end of the article, a template will be provided to help you get started quickly.
Create a new file named editor-style.css
and place it in the root directory of the theme (or child theme directory).
The CSS style of the block editor is slightly different from the standard CSS. For example, the following code cannot correctly apply text size in an article:
h2 { font-size: 1.75em; }
To set the style correctly, you need to locate the blocks in the block editor. This means<h2></h2>
Elements need to be scoped using .rich-text.block-editor-rich-text__editable
class:
h2.rich-text.block-editor-rich-text__editable { font-size: 1.75em; }
I've created a base CSS file that follows this pattern to style common block editor elements. You can get the file from GitHub and replace the style to match your theme.
I won't expand the stylesheet build process in detail here, but the template should give you a clear idea. A good starting point is to copy elements from your front-end stylesheet, but you may need to change some element classes so that they apply to the block editor window.
If in doubt, use the browser developer tool to check elements and determine their corresponding class name. The templates for the above links should cover most elements.
Effect display
First, let's take a look at the WordPress editor without a custom stylesheet:
Then, compare my test website front-end:
The difference between the two is significant, right? My test site uses a lot of gradients, custom fonts, button styles, and reference blocks, and the container is not a simple square.
Like it or not, you'll agree that this is a big difference from the default Gutenberg editor UI. This is why I need to open a tab page separately to preview the article.
Now, let's load the custom style and see the effect:
Look! The editor UI now looks almost exactly the same as the front end of my website. Content width, font, color and various elements are consistent with the front end. I even have the same beautiful background as the title of the article!
This means – no longer need to preview in another tab. Isn't it cool?
Keeping WordPress editor consistent with the front-end appearance can greatly improve efficiency. For me, frequently switching tabs to view front-end effects when editing articles will interrupt my thinking, so I prefer to avoid this.
Hope the above steps can help you achieve the same effect!
The above is the detailed content of Getting the WordPress Block Editor to Look Like the Front End Design. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

There are three ways to selectively include CSS on a specific page: 1. Inline CSS, suitable for pages that are not frequently accessed or require unique styles; 2. Load external CSS files using JavaScript conditions, suitable for situations where flexibility is required; 3. Containment on the server side, suitable for scenarios using server-side languages. This approach can optimize website performance and maintainability, but requires balance of modularity and performance.

CSS blocks page rendering because browsers view inline and external CSS as key resources by default, especially with imported stylesheets, header large amounts of inline CSS, and unoptimized media query styles. 1. Extract critical CSS and embed it into HTML; 2. Delay loading non-critical CSS through JavaScript; 3. Use media attributes to optimize loading such as print styles; 4. Compress and merge CSS to reduce requests. It is recommended to use tools to extract key CSS, combine rel="preload" asynchronous loading, and use media delayed loading reasonably to avoid excessive splitting and complex script control.

In the following tutorial, I will show you how to create Lottie animations in Figma. We'll use two colorful designs to exmplify how you can animate in Figma, and then I'll show you how to go from Figma to Lottie animations. All you need is a free Fig

We put it to the test and it turns out Sass can replace JavaScript, at least when it comes to low-level logic and puzzle behavior. With nothing but maps, mixins, functions, and a whole lot of math, we managed to bring our Tangram puzzle to life, no J

ThebestapproachforCSSdependsontheproject'sspecificneeds.Forlargerprojects,externalCSSisbetterduetomaintainabilityandreusability;forsmallerprojectsorsingle-pageapplications,internalCSSmightbemoresuitable.It'scrucialtobalanceprojectsize,performanceneed

No,CSSdoesnothavetobeinlowercase.However,usinglowercaseisrecommendedfor:1)Consistencyandreadability,2)Avoidingerrorsinrelatedtechnologies,3)Potentialperformancebenefits,and4)Improvedcollaborationwithinteams.

CSSCounters is a tool for creating automatic numbers. 1. Basic usage: define and operate counters through counter-reset and counter-increment, such as "SectionX." before h2. 2. Advanced usage: Use nested counters to create complex numbers, such as chapter and section numbers. 3. Notes: Ensure the counter is reset correctly, optimize performance, and simplify counter logic. 4. Best practice: clear naming, define counters in CSS, and use counter-increment and counter-reset reasonably.

CSSismostlycase-insensitive,butURLsandfontfamilynamesarecase-sensitive.1)Propertiesandvalueslikecolor:red;arenotcase-sensitive.2)URLsmustmatchtheserver'scase,e.g.,/images/Logo.png.3)Fontfamilynameslike'OpenSans'mustbeexact.
