/handbook/developing-for-block-editor-and-site-editor/react-best-practices/
What We Do
Digital Platform MigrationsKey SolutionsManaged ServicesStaffing SolutionsIndustriesProducts
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
AI
Unlock real use cases and integrations
All Services
A suite of services for any need
Technology STACK
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 Coding best practices React best practices
Topics
On this page
Use Functional Components and Hooks over Class Components
Implement Proper State Management (useState, useReducer, useContext)
Utilize Memoization (useMemo, useCallback) to Optimize Performance
Break Down Complex Components into Smaller, Reusable Parts
Use PropTypes or TypeScript for Better Type Checking
Avoid Prop Drilling by Using Context or State Management Libraries
Implement Error Boundaries to Catch and Handle Errors Gracefully
Use Keys Properly in Lists to Help React Identify Changes
Prefer Composition over Inheritance for Component Structure
Prefer Named Export
Useful links
Last updated on May 26, 2026
React Best Practices
To build efficient and maintainable React components in Gutenberg block development, it’s important to follow established best practices. Below are key practices extended with explanations and code examples.
Use Functional Components and Hooks over Class Components
Functional components are simpler and more concise than class components. They allow you to use React hooks for state management and side effects, leading to cleaner and more readable code. Additionally, functional components are the future of React development, with hooks providing powerful features that were previously only available in class components.
Example of a Functional Component with Hooks:
import { useState } from 'react';
const Counter = () => {
const [count, setCount] = useState(0);
const increment = () => {
setCount(prevCount => prevCount + 1);
};
return (
<div>
<p>Count: {count}</p>
<button onClick={increment}>Increment</button>
</div>
);
};
export default Counter;
Implement Proper State Management (useState, useReducer, useContext)
Use the appropriate hook for state management based on the complexity of your component:
- useState: For simple state management of individual values.
- useReducer: For more complex state logic involving multiple sub-values or when the next state depends on the previous one.
- useContext: For passing data through the component tree without having to pass props down manually at every level.
import { useState } from 'react';
const ToggleSwitch = () => {
const [isOn, setIsOn] = useState(false);
const toggle = () => {
setIsOn(prevState => !prevState);
};
return (
<button onClick={toggle}>
{isOn ? 'Switch Off' : 'Switch On'}
</button>
);
};
export default ToggleSwitch;
Example using useState:
import { useReducer } from 'react';
const initialState = { count: 0 };
function reducer(state, action) {
switch (action.type) {
case 'increment':
return { count: state.count + 1 };
case 'decrement':
return { count: state.count - 1 };
default:
throw new Error();
}
}
const Counter = () => {
const [state, dispatch] = useReducer(reducer, initialState);
return (
<div>
<p>Count: {state.count}</p>
<button onClick={() => dispatch({ type: 'decrement' })}>-</button>
<button onClick={() => dispatch({ type: 'increment' })}>+</button>
</div>
);
};
export default Counter;
Example using useReducer:
Utilize Memoization (useMemo, useCallback) to Optimize Performance
Memoization helps to optimize performance by caching the result of expensive function calls and reusing them when the same inputs occur again. In React, useMemo memoizes the result of a function, and useCallback memoizes the function itself.
Example using useMemo:
import { useState, useMemo } from 'react';
const ExpensiveCalculationComponent = ({ num }) => {
const [multiplier, setMultiplier] = useState(1);
const expensiveCalculation = number => {
console.log('Calculating...');
// Simulate a CPU-intensive calculation
return number 2;
};
const memoizedValue = useMemo(() => expensiveCalculation(num), [num]);
return (
<div>
<p>Result: {memoizedValue * multiplier}</p>
<button onClick={() => setMultiplier(multiplier + 1)}>
Increase Multiplier
</button>
</div>
);
};
export default ExpensiveCalculationComponent;
In this example, the expensive calculation only runs when num changes, not when multiplier changes.
Example using useCallback:
import { useState, useCallback } from 'react';
import List from './List';
const ParentComponent = () => {
const [items, setItems] = useState([]);
const fetchItems = useCallback(async () => {
// Fetch items from an API or perform some action
const newItems = await getItemsFromAPI();
setItems(newItems);
}, []);
return (
<div>
<List fetchItems={fetchItems} />
</div>
);
};
export default ParentComponent;
By using useCallback, the fetchItems function is only recreated if its dependencies change, preventing unnecessary re-renders of the List component.
Break Down Complex Components into Smaller, Reusable Parts
Breaking down components improves readability, reusability, and testability. Smaller components are easier to manage and can be reused in different parts of your application.
Example:
Suppose you have a complex form component. You can break it down into smaller components like InputField, SelectField, and SubmitButton.
// InputField.js
const InputField = ({ label, value, onChange }) => (
<div>
<label>{label}</label>
<input value={value} onChange={onChange} />
</div>
);
export default InputField;
// SelectField.js
const SelectField = ({ label, options, value, onChange }) => (
<div>
<label>{label}</label>
<select value={value} onChange={onChange}>
{options.map(option => (
<option key={option.value} value={option.value}>
{option.label}
</option>
))}
</select>
</div>
);
export default SelectField;
// SubmitButton.js
const SubmitButton = ({ onClick }) => (
<button onClick={onClick}>Submit</button>
);
export default SubmitButton;
// ComplexForm.js
import { useState } from 'react';
import InputField from './InputField';
import SelectField from './SelectField';
import SubmitButton from './SubmitButton';
const ComplexForm = () => {
const [name, setName] = useState('');
const [option, setOption] = useState('');
const handleSubmit = event => {
event.preventDefault();
// Handle form submission
};
return (
<form onSubmit={handleSubmit}>
<InputField label="Name" value={name} onChange={e => setName(e.target.value)} />
<SelectField
label="Options"
value={option}
onChange={e => setOption(e.target.value)}
options={[
{ label: 'Option 1', value: '1' },
{ label: 'Option 2', value: '2' },
]}
/>
<SubmitButton />
</form>
);
};
export default ComplexForm;
Use PropTypes or TypeScript for Better Type Checking
Using type checking helps catch bugs early and makes your code more predictable and easier to understand. PropTypes is a runtime type checking system, while TypeScript provides compile-time type checking.
Example using PropTypes:
import PropTypes from 'prop-types';
const Greeting = ({ name }) => <p>Hello, {name}!</p>;
Greeting.propTypes = {
name: PropTypes.string.isRequired,
};
export default Greeting;
type GreetingProps = {
name: string;
};
const Greeting: React.FC<GreetingProps> = ({ name }) => (
<p>Hello, {name}!</p>
);
export default Greeting;
Avoid Prop Drilling by Using Context or State Management Libraries
Prop drilling occurs when you pass props through multiple levels of components that don’t need them, just to reach a deeply nested component. Using React Context or a state management library like Redux can help avoid this issue.
Example using React Context:
import { createContext, useContext } from 'react';
const UserContext = createContext();
const ParentComponent = () => {
const user = { name: 'Alice' };
return (
<UserContext.Provider value={user}>
<ChildComponent />
</UserContext.Provider>
);
};
const ChildComponent = () => <GrandchildComponent />;
const GrandchildComponent = () => {
const user = useContext(UserContext);
return <p>User: {user.name}</p>;
};
export default ParentComponent;
In this example, the user object is available in GrandchildComponent without passing it through ChildComponent.
Implement Error Boundaries to Catch and Handle Errors Gracefully
Error boundaries catch JavaScript errors anywhere in their child component tree, log those errors, and display a fallback UI instead of the component tree that crashed.
Example of an Error Boundary:
import { Component } from 'react';
class ErrorBoundary extends Component {
constructor(props) {
super(props);
this.state = { hasError: false };
}
static getDerivedStateFromError(error) {
// Update state to render fallback UI
return { hasError: true };
}
componentDidCatch(error, errorInfo) {
// Log the error to an error reporting service
logErrorToService(error, errorInfo);
}
render() {
if (this.state.hasError) {
// Render fallback UI
return <h1>Something went wrong.</h1>;
}
return this.props.children;
}
}
export default ErrorBoundary;
Usage:
<ErrorBoundary>
<MyComponent />
</ErrorBoundary>
Use Keys Properly in Lists to Help React Identify Changes
Keys help React identify which items have changed, are added, or are removed. They should be given to elements inside an array to give the elements a stable identity.
Example:
const TodoList = ({ todos }) => (
<ul>
{todos.map(todo => (
<li key={todo.id}>{todo.text}</li>
))}
</ul>
);
In this example, todo.id is used as a key because it uniquely identifies each item.
Prefer Composition over Inheritance for Component Structure
Composition is a way of combining components where you include a component within another. It leads to more flexible and reusable code compared to inheritance.
Example:
const FancyBorder = ({ children }) => (
<div className="fancy-border">
{children}
</div>
);
const WelcomeDialog = () => (
<FancyBorder>
<h1>Welcome</h1>
<p>Thank you for visiting our spacecraft!</p>
</FancyBorder>
);
export default WelcomeDialog;
Prefer Named Export
Named exports make it easier to refactor and import multiple components from a single file. They also improve the clarity of what is being imported.
Example:
// components.js
export const Button = () => {
/* ... */
};
export const Input = () => {
/* ... */
};
// Usage
import { Button, Input } from './components';
This is preferred over default exports when multiple exports are involved, as it provides better tooling support and makes the codebase more maintainable.
By following these React best practices with the provided examples, you can develop more efficient, maintainable, and scalable components within Gutenberg blocks, leading to better overall application performance and developer experience.
Useful links
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 our newsletter and get a few email updates every month.
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
cookies.js_dtest
This cookie determines whether the browser accepts cookies.
session
_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
Toggle SalespanelSalespanel
Salespanel is a B2B marketing and sales software that identifies, tracks, and qualifies website visitors and leads in real-time using first-party data. It helps businesses monitor customer journeys, score leads based on behavior, and syncs this data with CRMs (like Pipedrive or HubSpot) to improve conversion rates.
Service URL: salespanel.io (opens in a new window)
Name
Description
Duration
track_uid
Identify and tracking a lead
12 moths
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