Blog
Thinking in patterns
Notes on building, syncing, and sharing WordPress block patterns — from the team behind Pattern Builder.
-
The wordpress.org Pattern Directory — and the easier way
The wp.org directory proved that patterns are how WordPress sites want to be built. Here is what it still makes you do…
-
A pattern workflow for freelancers: build once, deploy to every client site
Stop rebuilding the same five sections on every project. Keep one cloud library of your best work and pull it onto each…
-
Block bindings + patterns: dynamic content without custom blocks
The Block Bindings API connects core block attributes to dynamic data. Put bindings inside a pattern and you get reusable, dynamic sections…
-
Designing patterns that survive a theme switch
A portable pattern speaks the theme’s language instead of shouting over it: presets over hex codes, the spacing scale over pixel values,…
-
Converting user patterns to theme patterns (and back)
The editor is the best place to design a pattern; a theme file is often the best place to keep it. Conversion…
-
Synced Patterns for Themes: synced patterns that ship in your theme
Synced patterns normally live in one site’s database. One file header — Synced: yes — makes a theme pattern behave the same…
-
Synced patterns, explained
Edit once, update everywhere. What actually happens when a pattern is synced, how overrides let instances differ where you allow it, and…
-
Pattern categories your clients will actually understand
Categories are the interface to your pattern library. Name them for the job, keep the list short, and they become the unit…
-
Anatomy of a great hero pattern
Heroes are the pattern you will reuse most, so they repay the most care. Six habits that separate a hero you reuse…
-
Theme patterns vs. user patterns: where should a pattern live?
WordPress gives a pattern two possible homes — a PHP file in your theme or a post in the database. The right…