Choose what future editing should feel like
Blocks suit content that benefits from WordPress's native editor. Styled HTML suits designs that rely on an authored code structure. The right choice depends on the source and who will maintain the page.
Use blocks when…
- Headings, text, images and supported layouts should be editable in the WordPress editor.
- The source maps cleanly to supported block structures.
- You are willing to adjust the result to fit native editing behavior.
Keep trusted styled HTML when…
- The design relies on code or layout details that conversion does not preserve.
- A qualified maintainer will own the HTML, CSS and any scripts.
- Preserving the design is more important than making every element a block control.
Explore the block families
The library offers building pieces for authored pages and ongoing site features. The examples below preserve the useful categories from the earlier documentation, not its historical runtime counts. Availability, settings and behavior depend on the installed release, permissions, license and dependencies. Check the block inserter and test each visitor-facing action.
Layout and calls to action
Hero sections, headings, buttons and button groups, calls to action, dividers, spacers, feature grids, footers and highlighted banners help establish page structure.
Content and structure
Rich text, image-and-text sections, lists, tables, tabs, accordions, timelines and process steps organize the story. Check heading order and keyboard access, especially in interactive sections.
Media and visual
Images, galleries, carousels, video, audio, before/after comparisons and hotspots present visual material. Supply appropriate alternative text and verify loading, captions and mobile behavior.
Forms and accounts
Form, subscription, login and registration blocks need configured handlers and a real submission test. Account, checkout and cart-related blocks depend on WooCommerce; a visible layout alone does not establish working commerce.
Commerce and business
Pricing tables, product displays, business hours, contact information, maps, team sections and testimonials support business pages. Product features may require WooCommerce. Publish only genuine reviews, accurate prices and authorized business information.
Social, data and navigation
Social links, sharing controls, ratings, counters, progress indicators, logo grids, post displays and search help visitors explore content. Counters and ratings are presentation tools, not evidence for invented metrics.
Advanced and interactive
Modal panels, off-canvas content, toggles, sliders, flip boxes, icons and tables of contents add behavior. Review focus, keyboard operation, reduced motion and fallback content before publishing.
Patterns
Precomposed hero, feature, pricing, testimonial, team, FAQ, contact and footer layouts provide starting points. Review the inserted content and its dependencies rather than treating a pattern as a finished page.
What to review after conversion
Compare the source and draft. Check nested layouts, spacing, headings, image crops, mobile order, links and unsupported elements. Confirm that the editor can reopen and save the page without losing the intended content.
Be deliberate about templates
A theme controls more than a page body. A custom blank or application-style template may intentionally omit parts of the normal rendering pipeline. Use an appropriate template for the content and verify the result rather than assuming every combination behaves alike.
Block availability changes with the release and installation. Inspect the block inserter and actual site capabilities instead of relying on a historical marketing count.
Next: prepare an import or start with a small draft.