Category: Block Editor

Margin creates space outside a block. Padding creates space inside its boundary. Block gap controls space between children owned by one container. Each tool answers a different relationship. Use theme spacing presets whenever possible. Shared values remain easier to maintain than random numbers. Compare margin, padding, and gap Margin separates one block from neighbouring content.…

Normal alignment uses the content width. Wide alignment uses the theme’s wider boundary. Full alignment fills the available parent width. It does not always equal the browser viewport. The parent layout, template, theme, and block support determine every visible result. Compare the three width levels Normal content stays inside the readable content boundary. Wide content…

WordPress blocks usually follow their saved source order when layouts stack. List View reveals that order. Columns enables mobile stacking by default. Media and Text provides its own Stack on mobile setting. Rows may wrap, Stacks remain vertical, and Grids may retain multiple tracks. Test the actual theme output. Start with the source order Desktop…

$546, $299, or $226 — depending on how you buy. Those are the three honest answers for one full premium block stack. Bought as four separate lifetime licences, $546. Bundled as WP Block Suite, $299 one-time. On annual licences, $226 in the first year, then $177 a year. One rule before the math: we only…

Responsive WordPress layouts can use core blocks, flexible sizing, and theme design tokens. A page builder is optional. Start with content order and available space. Let layouts change when their content becomes uncomfortable. Test narrow, wide, and awkward intermediate widths. Those checks reveal more than three polished device screenshots. Define responsive design correctly Responsive design…

Save a revision, identify which layer owns the formatting, then remove the smallest unwanted layer. Do not rebuild the page immediately. Use Clear unknown formatting for unrecognised rich-text markup. Reset local block styles separately. Investigate theme or plugin CSS when several pages match. Cleanup should preserve meaning, links, language, code, emphasis, and structure. “Plain-looking” is…

Paste Google Docs content into a clean WordPress draft, one reviewed section at a time. Preserve useful headings, lists, emphasis, and links. Then clear unknown formatting and upload media separately. Inspect block structure and complete WordPress settings before publication. Use plain-text paste when the document carries unreliable styling. Rebuild semantic structure inside WordPress instead of…

Back up WordPress, create staging, and convert one representative Classic block. Inspect the resulting blocks before saving or scaling. Use the Classic block’s Convert to blocks action. Then repair headings, lists, media, shortcodes, custom HTML, and page-specific settings. Stable legacy content can remain classic temporarily. Conversion should solve editing or maintenance problems, not satisfy architectural…

Choose an export method by scope. Clipboard suits a few blocks. WXR suits collections. APIs support controlled automation. Block markup can travel inside post content. Providers, media files, theme styles, shared records, configuration, and licences may not. Import into staging first. Map dependencies, preserve dates and ownership, then verify rendered output before any production release.…

Move blocks between WordPress sites only after matching their providers and required design support. Then transfer serialized markup into staging. Audit media, links, identifiers, shared records, queries, and frontend output before publication. Cross-site copying is a dependency migration. Core text blocks travel easily. Dynamic plugin blocks, synced patterns, forms, and theme-led layouts need much more…