/handbook/developing-for-block-editor-and-site-editor/should-we-look-at-the-most-atomic-elements-first-bottom-up-or-should-we-look-at-pages-patterns-top-down/
What We Do
Digital Platform MigrationsKey SolutionsManaged ServicesArtificial IntelligenceIndustriesProducts
OnePress
Unify multiple brands on one governed WordPress platform.
Design & UI/UX
Gutenberg-native UX, UI, and design systems for visitors and editors.
WordPress Modernization
Modernize WordPress for better performance, architecture, and AI readiness.
WordPress as a DXP
WordPress as a composable DXP when monolithic systems no longer cut it.
Headless WordPress
Omnichannel content delivery without sacrificing marketing autonomy.
Frappe/ERPNext
Build scalable ERP and custom applications, from implementation to ongoing support.
Discovery
Strategic consultancy & project roadmap
Growth Services
On demand development & consultation
Site Maintenance
Annual maintenance. Done for you
QE Services
Testing across SDLC for assured quality
Hosting Migration
Move to a performant hosting with zero downtime
WooCommerce
Enterprise commerce delivered without lock-in
Staff Augmentation
Expert WordPress engineers, onboarded in a week
All Services
A suite of services for any need
Publishio : Publish on your WordPress website from Claude & ChatGPT
Extending the WordPress AI Plugin Releasing Connectors for OpenRouter, LM Studio & Universal OpenAI
How rtCamp saves 100 hours of teams using AI powered Sales Qualification
eCommerce
Scale your e-commerce with WooCommerce, integrations, and custom extensions for growth.
EasyEngine
Server management tool that makes using WordPress on Nginx easy.
Web Auditor
Performance Audit & Insights for your Website.
rtMedia
A complete media management plugin for WordPress.
Resources
About Us
CLEAR
Resources Developing for Block Editor and Site Editor Development approaches Bottom-up vs top-down
Topics
On this page
1. Bottom-Up Approach (Atomic Design)
Process in Gutenberg
Challenges in Gutenberg
2. Top-Down Approach (Pages/Patterns)
Process in Gutenberg
Benefits in Gutenberg
Challenges in Gutenberg
3. Hybrid Approaches in Gutenberg
Implementation in Gutenberg
Takeaway
Last updated on May 26, 2026
Should we look at the most atomic elements first (bottom-up) or should we look at pages/patterns (top-down)?
In the context of Gutenberg, choosing between the top-down and bottom-up approaches for block design can significantly influence your development workflow, user experience, and the overall quality of your project.
1. Bottom-Up Approach (Atomic Design)
The bottom-up approach, often referred to as atomic design, is particularly well-suited for Gutenberg’s block-based architecture. By focusing on creating smaller, reusable blocks, developers can construct a library of components that can be assembled into larger layouts within the editor.
Process in Gutenberg
- Atoms: Start by creating fundamental blocks like text, images, and buttons, which will serve as the building blocks of your site.
- Molecules: Combine these atomic blocks to form more complex structures, such as a call-to-action component that includes a button, an icon, and descriptive text.
- Organisms: Assemble these molecules into complete sections, such as a hero section that features a heading, an image, and a button, enhancing user engagement.
- Templates and Pages: Use these organisms to create templates that define the layout and structure for various pages or post types, ensuring consistency across the site.
- Reusable Components: This approach naturally aligns with Gutenberg’s ethos of reusability. By creating modular blocks, you can easily maintain and update your site’s components, ensuring a uniform experience across pages.
- Consistency: By developing a set of atomic components, you reduce the risk of inconsistencies, ensuring that your site looks and behaves predictably.
- Faster Iteration: With a library of ready-to-use components, designers and developers can quickly prototype and iterate on new layouts, significantly speeding up the development process.
Challenges in Gutenberg
- Initial Setup Time: The upfront investment in designing and developing each component can be time-consuming, particularly for smaller projects.
- Complexity Management: As the number of components grows, managing them can become cumbersome, necessitating effective organization and documentation strategies.
2. Top-Down Approach (Pages/Patterns)
The top-down approach emphasizes designing entire pages or patterns first, which can be particularly effective when the user experience is paramount. This method allows developers to envision how users will interact with the site as a whole.
Process in Gutenberg
- Define Page Layouts: Start by sketching out the overall layout for each type of page or post, considering how various components will work together.
- Create Patterns: Design reusable patterns that can be employed across different pages. For example, a blog post pattern that combines a title, featured image, and content area.
- Component Breakdown: Once the overall design is clear, identify and develop the individual blocks needed to realize the page layout.
Benefits in Gutenberg
- User-Centric Design: This approach allows for a holistic view of user experience, helping developers create more intuitive and engaging layouts.
- Faster Prototyping: By focusing on high-level design, developers can quickly visualize how users will interact with the site, facilitating stakeholder feedback and design iterations.
- Focused Block Development: With a clear understanding of what blocks are needed to create a cohesive layout, developers can design components specifically tailored to fit into the larger structure.
Challenges in Gutenberg
- Risk of Redundancy: The tendency to create components tailored to specific patterns can lead to redundancy, increasing the maintenance burden if those components are not reused elsewhere.
- Less Flexibility: As the project evolves, changes in the overarching layout may require substantial rework of individual components, complicating the development process.
3. Hybrid Approaches in Gutenberg
Given the strengths and weaknesses of both methodologies, many developers opt for a hybrid approach. This strategy allows for the integration of top-down and bottom-up techniques, maximizing the advantages of each while mitigating their drawbacks.
Implementation in Gutenberg
- Component First, Then Layout: Start with a few critical reusable components to establish a foundation, then design the layouts and patterns around them. This ensures that the site remains consistent while providing flexibility to adapt to new requirements.
- Iterative Prototyping: Develop a pattern that encompasses several blocks and use it to test usability and engagement before refining individual components.
- Continuous Feedback Loop: Encourage ongoing feedback from stakeholders and users, which can inform adjustments in both component design and overall page structure.
Takeaway
Understanding the top-down and bottom-up approaches in the context of Gutenberg enables developers to tailor their block development strategies effectively. By choosing the right methodology—or a hybrid approach—developers can enhance the user experience, maintain code quality, and streamline their workflows. Adopting a strategic approach to block design ensures that projects are not only functional but also deliver a cohesive and engaging experience for users.
FSE components compared
PREVIOUS
Three ways to build blocks
NEXT
Credits
Utsav Patel
Author
Utsav Patel
Author
Good Work. Good People.
Industry partnerships
Compliance certifications
United States India
© rtCamp Inc. since 2009. All rights reserved.
Terms of Service · Privacy Policy · Trust Center
Company
Solutions
Subscribe to Campfire for fresh insights and stories from people behind rtCamp
Δ
Email(Required)
Submit
United States India
© rtCamp Inc. since 2009. All rights reserved.
Terms of Service · Privacy Policy · Trust Center
Cookie Consent
We value your privacy
We use cookies to give you the best possible experience. By clicking “Accept,” you consent to our use of cookies to improve site functionality, analyze usage, and personalize content and communications. Your privacy matters to us, and we are committed to handling your data responsibly and transparently. Please check our Privacy Policy for more details.
Manage PreferencesDon’t AllowAllow All
Why do we use cookies?
×
By clicking "Accept" or "Decline All" at the bottom, you consent to the use of cookies and other tools as described in our Cookie Policy in accordance with your settings and accept our Terms of Service.
Toggle EssentialEssential
Essential cookies enable basic functions and are necessary for the proper function of the website.
Name
Description
Duration
Geolocation Config
This cookie is used to store the consent settings based on the visitor's location.
30 days
Cookie Preferences
This cookie is used to store the user's cookie consent preferences.
30 days
Toggle CloudFlareCloudFlare
CloudFlare provides web performance and security solutions, enhancing site speed and protecting against threats.
Service URL: developers.cloudflare.com (opens in a new window)
Name
Description
Duration
cf_clearance
Whether a CAPTCHA or Javascript challenge has been solved.
session
Toggle CommentsComments
These cookies are needed for adding comments on this website.
Name
Description
Duration
comment_author
Used to track the user across multiple sessions.
Session
comment_author_email
Used to track the user across multiple sessions.
Session
comment_author_url
Used to track the user across multiple sessions.
Session
Toggle GodamGodam
GoDAM" is primarily a specialized WordPress plugin and media management service designed to enhance video hosting, marketing, and asset management directly within the WordPress dashboard.
Service URL: godam.io (opens in a new window)
Name
Description
Duration
user_image
Temporarily stores the path to the user's avatar or profile picture for quick rendering in the website header.
session
user_id
Stores the numerical ID of the logged-in user to maintain session continuity and basic site operations.
session
full_name
Stores the logged-in user's display name to personalize the site interface without needing database queries.
session
system_user
First-party cookie used to store basic application state identifying the current system user role.
session
sid
A generic session ID cookie used to maintain user state and functionality as the visitor navigates through the site.
session
Toggle Google reCAPTCHAGoogle reCAPTCHA
Google reCAPTCHA helps protect websites from spam and abuse by verifying user interactions through challenges.
Name
Description
Duration
_GRECAPTCHA
Google reCAPTCHA sets a necessary cookie (_GRECAPTCHA) when executed for the purpose of providing its risk analysis.
179 days
Toggle Google Tag ManagerGoogle Tag Manager
Google Tag Manager simplifies the management of marketing tags on your website without code changes.
Name
Description
Duration
cookiePreferences
Registers cookie preferences of a user
2 years
td
Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator.
session
Toggle StatisticsStatistics
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Toggle Factors AIFactors AI
Factors.ai is a B2B account intelligence and marketing analytics platform that helps Go-To-Market (GTM) teams identify anonymous website visitors, track buyer journeys, and measure the ROI of marketing campaigns.
Service URL: www.factors.ai (opens in a new window)
Name
Description
Duration
_fuid
It is sent to capture session details and track user behavior across your website to provide behavioral data and intent signals.
1 Year
Toggle Google AnalyticsGoogle Analytics
Google Analytics is a powerful tool that tracks and analyzes website traffic for informed marketing decisions.
Service URL: policies.google.com (opens in a new window)
Name
Description
Duration
FPGSID
Stores a session or user identifier to track how visitors interact with a website. This helps Google Analytics measure website performance, user engagement, and usage patterns.
Session
FPLC
Used by Google Analytics to link visitor interactions and sessions across multiple related domains.
20 hours
FPID
A server-side Google Analytics cookie used as an alternative user identifier when third-party cookies are restricted.
2 years
_ga
ID used to identify users
2 years
_ga_
ID used to identify users
2 years
Toggle Jetpack StatsJetpack Stats
Jetpack's built-in visitor analytics. It records page views, referring sites, search terms, and outbound link clicks, and also carries the shared visitor-tracking library used by Jetpack Instant Search and WooCommerce Analytics.
Service URL: automattic.com (opens in a new window)
Name
Description
Duration
tk_aip
Stores a list of anonymous visitor IDs so they can be merged into one identity once a visitor is recognized.
Up to 5 years
tk_tc
Used once per page load to work out which cookie domain the Tracks library should use, then removed as soon as it's read back.
Session (deleted immediately after use)
tk_qs
Queues analytics events for Jetpack's Tracks library so none are lost if the page closes before they can be sent.
30 minutes
tk_ai
Stores a randomly-generated anonymous visitor ID so Jetpack's Tracks analytics library can link tracking events to the same visitor.
Session in wp-admin; up to 5 years on the frontend
Toggle Microsoft ClarityMicrosoft Clarity
Clarity is a web analytics service that tracks and reports website traffic.
Service URL: clarity.microsoft.com (opens in a new window)
Name
Description
Duration
CLID
Identifies the first-time Clarity saw this user on any site using Clarity.
12 months
ANONCHK
Indicates whether MUID is transferred to ANID, a cookie used for advertising. Clarity doesn't use ANID and so this is always set to 0.
Session
_clck
Persists the Clarity User ID and preferences, unique to that site is attributed to the same user ID.
12 months
_clsk
Connects multiple page views by a user into a single Clarity session recording.
12 months
Toggle Parse.lyParse.ly
Parse.ly is a content analytics platform that helps publishers optimize audience engagement and content performance.
Name
Description
Duration
_parsely_session
JSON document storing information identifying a browsing session according to Parsely’s proprietary definition
30 minutes
_parsely_visitor
JSON document uniquely identifying a browser and counting its sessions
13 months
cookies.js_dtest
This cookie determines whether the browser accepts cookies.
session
Toggle MarketingMarketing
Marketing cookies are used to follow visitors to websites. The intention is to show ads that are relevant and engaging to the individual user.
Toggle Bing / MicrosoftBing / Microsoft
Bing, powered by Microsoft, is a search engine providing web, image, video, and map search capabilities.
Name
Description
Duration
MR
Used to collect information for analytics purposes.
6 months
ANONCHK
Used to store session ID for a users session to ensure that clicks from adverts on the Bing search engine are verified for reporting purposes and for personalisation
10 minutes
SM
Used by Microsoft in synchronizing the MUID across multiple Microsoft domains to track users for advertising.
session
MUID
Identifies unique web browsers visiting Microsoft sites. These cookies are used for advertising, site analytics, and other operational purposes.
1 year
Toggle DoubleClick/Google MarketingDoubleClick/Google Marketing
A comprehensive digital advertising platform for managing campaigns, optimizing performance, and analyzing audience data.
Name
Description
Duration
IDE
This cookie is used for targeting, analyzing and optimisation of ad campaigns in DoubleClick/Google Marketing Suite
2 years
ar_debug
Store and track conversions
Persistent
Toggle LinkedInLinkedIn
LinkedIn is a professional networking platform for job seekers, employers, and industry connections.
Name
Description
Duration
bscookie
Used by LinkedIn to track the use of embedded services.
1 year
AnalyticsSyncHistory
Used to store information about the time a sync with the lms_analytics cookie took place for users in the Designated Countries
30 days
bcookie
Used by LinkedIn to track the use of embedded services.
1 year
li_sugr
Used to make a probabilistic match of a user's identity outside the Designated Countries
90 days
lidc
Used by the social networking service, LinkedIn, for tracking the use of embedded services.
1 day
UserMatchHistory
Used by LinkedIn Ads to synchronize and match user IDs across different ad networks and data providers.
30 days
Toggle LinkedIn InsightLinkedIn Insight
LinkedIn Insight is a web analytics service that tracks and reports website traffic.
Service URL: www.linkedin.com (opens in a new window)
Name
Description
Duration
li_sugr
Used to make a probabilistic match of a user's identity.
90 days
lidc
Used for routing and session management.
24 hours
Toggle LiveIntentLiveIntent
LiveIntent provides a platform for email advertising and identity-driven marketing solutions.
Name
Description
Duration
_lc2_fpi_js
Companion cookie to _lc2_fpi used by JavaScript to facilitate cross-domain ad tracking and user identification.
1 year
_lc2_fpi
First-party tracking cookie usually associated with LiveRamp to identify users across devices for targeted advertising.
1 Year
_li_ss
Sets a unique ID for the visitor, that allows third party advertisers to target the visitor with relevant advertisement. This pairing service is provided by third party advertisement hubs, which facilitates real-time bidding for advertisers.
1 month
lidid
Collects data on visitors' behaviour and interaction - This is used to make advertisement on the website more relevant. The cookie also allows the website to detect any referrals from other websites.
2 years
Toggle Cookie PolicyCookie Policy
You can find more information in our Privacy Policy.
Allow AllDecline All
Accept