Yalla Download

You did the work, earned the tassel, and crossed the stage. Now what?

Whether you’re job-hunting, applying to grad school, or figuring out next steps, now’s the time to build something that sets you apart: a personal website. It’s your digital home base for showcasing your skills, experience, and what makes you you.

Show potential employers, collaborators, or admissions teams what you bring to the table with a site that grows with you. We’re giving graduates 25% off a new website for a limited time.

The smartest move you haven’t made yet

Chances are, your future employer or admissions officer will Google you. Do you know what they’ll find?

Whether you’re a job seeker, grad school applicant, freelancer, or creator, a personal website allows you to proactively manage and curate your online presence. It serves as a centralized platform to present a professional image to potential employers or academic institutions, and tailor how you present your skills and experience for each opportunity.

Your future, your website, your rules

Whatever you’re working on next, WordPress.com helps you share it with the world.

From portfolios to blogs to passion projects, here are just a few ways grads are putting WordPress.com to work:

• Build a digital resume: Create a standout online resume that goes beyond a PDF. Share your story, showcase your work, and prove why you’re the right choice.
• Showcase class projects and portfolios: Bring your best work together in one place. Whether you’re designing, writing, coding, or researching, your portfolio deserves more than a shared Google Drive link.
• Start a blog or newsletter: Turn your interests into opportunities. Whether you’re into travel, tech, or hot takes, a blog or newsletter helps you build credibility, showcase your expertise, and grow a following that sets you apart.
• Promote your research or passion projects: Working on a passion project or your next big idea? Your site can help you share it, fund it, and grow your audience. Add donation buttons, sell digital content, and build momentum with every visitor.
• Teach what you know: Use tools like Sensei LMS to create and sell online courses, whether you’re helping underclassmen get ahead or teaching your niche to a wider audience.
• Document your school experience: From first-year memories to final exams, preserve your college story in your own words and photos. Your friends can follow along and leave comments, too.

A little graduation gift from us

Every grad deserves a personal site, so we have a graduation gift just for you.

New graduates (K-12, college, and graduate) can snag 25% off an annual Personal, Premium, or Business WordPress.com plan today through June 16. 

Plus, with the purchase of your discounted annual hosting plan, your first year of a custom domain is on us. This means you can build your brand-new site with a domain (like yourgroovydomain.com) that reflects your personal brand, perfect for resumes, portfolios, and more.

This offer’s only here for a limited time, so don’t wait around. You’ve already done the hard part (hello, diploma), and now’s your chance to launch your site and show the world what’s next. Future you will thank you.

Make a site that says, “this is me”

Never built a website before? No problem. 

When you build a website on WordPress.com, hosting, performance, and security are all handled for you, so you can focus on presenting yourself in a true-to-you way.

Not only that, all WordPress.com sites are built with the most popular website builder in the world (WordPress), and the drag-and-drop editor, stylish themes, and custom domains help you build a site that aligns with your ambitions.

And if you want even more guidance to help you build a site you’re genuinely proud of, our new Create your website on WordPress.com course was made for you. 

This free course walks you through every step of the website-building process. You’ll learn how to:

• Find and activate a theme.
• Build a homepage and add content using blocks and patterns.
• Create additional pages for your site.
• Customize your header and footer.
• Style your site for a cohesive look and feel.
• Edit templates for structural changes.
• Launch your site for the world to see.

If time is of the essence, you can also use our new AI website builder to help you get your site up and running in just minutes.

Your future is calling, answer with a website

Take control of your future and own your online presence with a personal website. Show what you’ve done and be ready for whatever comes next: job interviews, applications, or unexpected opportunities.

With WordPress.com, we take care of hosting, performance, and security for your site, so you can tell your story the way you want it to be told.

Fine print: Graduating students with valid institutional email addresses (K-12, college, and graduate) qualify for this promotion. The discount ends June 16, 2025, and is valid for 25% off one full year of a Personal, Premium, or Business WordPress.com hosting plan. Only for annual plans and new purchases.

Did you know that the first Asians to enter what we now know as the United States were Filipino sailors on Spanish galleon ships who arrived in central California in 1587? 

As a proud Filipino-American who only arrived here as part of the wave of Asian immigration to the U.S. in the ‘70s and ‘80s, I’m thrilled to showcase some of my favorite Asian-American and Pacific Islander (AAPI) creators and bloggers who have made WordPress.com their home. 

Food, glorious food

Millions of us make up the global Asian diaspora in nearly every country in the world, hailing from one or more of the 48 Asian countries. We may come from unique cultures, but there’s one thing that binds us all together: our deep and abiding love of food. 

Check out these mouth-watering food blogs, complete with step-by-step recipes and, of course, plenty of colorful photos to inspire you to break out your favorite wok or kawali. 

My Bay Kitchen

Although this blog hasn’t been updated in a while, with literally hundreds of recipes in the archive, you’ll never run out of dishes to try. Inspired by his years learning traditional cooking techniques from his mother, the author, a San Francisco-based Filipino-American, weaves personal stories into each meticulously developed recipe. 

Jama’s Alphabet Soup

An eclectic mix of book reviews, poetry, recipes, and personal essays, this site is a whimsical journey through the writer’s culinary and reading adventures. 

Pop culture

These sites dive into the vibrant, ever-evolving world of AAPI pop culture, amplifying voices, dissecting trends, and celebrating representation.

Nerds of Color

The dazzling mosaic of pop culture-infused images in the header of this site lifts my mood every time I visit. Although it’s not specifically positioned as an Asian-American pop culture site, a quick perusal of its posts makes clear its creative roots in our community. 

Generasian

Yes, this blog is written by and for students at New York University, but it’s really for anyone who shares their passion for AAPI representation in pop culture, especially among Gen Alpha. 

Add to your TBR

I think just about every other site publishes “to be read” listicles of AAPI authors and books in May. Let’s give it up to those creators and bloggers who focus their reviews on our community’s literary output year-round. 

READING (AS)(I)AN (AM)ERICA

Thirty-something Taiwanese-American blogger Shenwei shines a spotlight on YA, adult fiction, and middle-grade books through an “Asian-Americanist lens.” She doesn’t just provide quick summaries; she also includes author interviews and curated playlists for select books. 

Little Corner Reads

There is a specific subgroup of book lovers who love books about books. And bookstores. I’m a card-carrying member of this special subgroup, and when I saw this particular post show up on my Reader feed, I knew I’d found a kindred spirit. She’s a voracious reader, and I love her joyful and authentic voice. 

Stories that stay with you

When identity spans countries, cultures, and histories, stories like these delve deeply into questions of culture, family, and what it means to find one’s place in the world.

Red Thread Broken

This blog powerfully documents the singular experiences and challenges of transracial adoptions. The writer, herself one of 80,000 adoptees from China who now live in the US, is a professional social worker, prolific author, and speaker on the topic. 

I’m always looking for more blog recommendations about the AAPI experience, so please share your favorites in the comments!

And if you’re feeling inspired to start your own, WordPress.com has everything you need to bring your story to life, like beautiful themes, powerful tools, and a community that’s got your back.

Meta descriptions might not appear on the frontend of your site for your readers to see, but they play a significant role behind the scenes. These short blurbs can influence whether someone clicks through from search or scrolls right on past. 

In this post, we’ll break down what meta descriptions are, why they matter, and how to write descriptions that actually get clicks.

1. What are meta descriptions?
2. How do meta descriptions impact SEO?
3. What happens if pages are missing meta descriptions?
4. Do meta descriptions need to be unique?
5. How long should meta descriptions be?
6. Using tools to preview your meta descriptions
7. Some simple (and overlooked) tips for writing meta descriptions
   1. Keep your title tag in mind
   2. Get aligned with search intent
   3. Keep voice search in mind
   4. Leverage emotional sentiment
   5. Include calls to action
8. Updating meta descriptions on WordPress websites
   1. Jetpack
   2. Other plugins
9. Go optimize your meta descriptions

What are meta descriptions?

A meta description is a line of text in web pages that summarizes their contents. Have you ever seen the summaries underneath the blue links on search results pages? Those are meta descriptions. Here is an example direct from Google:

Meta descriptions may also appear in link previews on social media posts, text messages, and chat apps. When written as HTML, they are wrapped in a <meta> tag within the <head> section of your page.

<meta name="description" content="INSERT YOUR META DESCRIPTION HERE" />

You can also see the meta description on any web page by right-clicking and selecting View Page Source. Here is an example from the entertainment website Polygon:

Meta descriptions are closely related to title tags, which appear as the actual blue links in search results. Together, they tell search engines and users what your site’s pages (from your homepage to individual blog posts and pages) are about.

How do meta descriptions impact SEO?

Unlike title tags, meta descriptions do not directly influence search engine rankings. However, they do affect how your pages appear in search results and tell users why they should click.

Reddit user Neither-Emu7933 summarized this concept well:

Think of your meta description as a brief pitch—it won’t directly boost your content rankings, but it can help it win the click. Paired with a strong title tag, it’s your best chance to stand out in a crowded search result.

What happens if pages are missing meta descriptions?

If a page is missing a meta description, the short answer is that nothing bad is likely to happen. But the long answer is a bit more nuanced. Meta descriptions can influence click-through rates, so leaving them out means missing an opportunity to shape how your content appears in search results.

If the meta description tag is missing, then Google will use other text from the page to generate its own snippet. Some people prefer to let Google handle meta descriptions instead of writing one manually. In fact, former Googler Matt Cutts once said he doesn’t include meta descriptions on all of his blog posts: 

So should you leave meta descriptions blank? Google’s own AI says that it may be risky:

Leaving meta descriptions blank can result in inaccurate page descriptions and, therefore, less search traffic.

Do meta descriptions need to be unique?

Duplicative meta descriptions are confusing for search engines and unhelpful for users, so the meta descriptions across your website should all be unique.

If your site or blog has many posts and pages that are missing meta descriptions, writing unique meta descriptions for each one could take a long time. In this instance, we recommend following Matt Cutts’ timeless advice from the video we shared earlier in this post:

• Include meta descriptions on your most important pages.
• Make sure your meta descriptions are unique.
• Leave the rest of your meta descriptions blank.

Once you’ve done that, make it a habit to include meta descriptions on new pages and posts. This is a compromise between time-consuming manual effort and setting yourself up for future success.

How long should meta descriptions be?

The traditional advice is that meta descriptions should be 150 characters or less. This will ensure search engines don’t cut them off. However, this isn’t the whole story.

Google measures meta description length in pixels rather than characters. Depending on the specific letters, words, and numbers in your meta description, the total maximum length may be more or less than 150 characters. 

Sometimes Google will overwrite the meta description you wrote and use text from the page itself to create a new meta description. Generally, Google will do this if your meta description is too short, or if it thinks it can create an alternative that’s more useful for the reader.

In these instances, the meta description that users see may be more than 300 characters. This makes it difficult to confidently say how long they should be. 

So what should you do? As a best practice, stick with the 150-character guideline (but be aware that this isn’t a firm rule). 

Using tools to preview your meta descriptions

It’s nice to actually see how meta descriptions will appear in search results before you publish a page. Fortunately, there are plenty of free tools you can use to preview them. Here are a few:

• Portent’s Google SERP Preview Tool
• Spotibo Google Search Results Preview Tool
• To The Web Title Tag and Meta Description Tester

Some simple (and overlooked) tips for writing meta descriptions

Ready to get serious about writing meta tags? They aren’t difficult to write, but there are some tips and general best practices you can follow to make sure you get them right.

Keep your title tag in mind

Search engine users will see your meta descriptions underneath your title tags. Keep this in mind when writing them, and ensure they read well together and accurately represent your content.

Need help writing title tags too? Here are some tips for writing excellent title tags to boost your search traffic. 

Get aligned with search intent

If you’ve never heard the term “search intent,” it means understanding what a user is trying to do when they search for a specific keyword. There are a few different types of search intent:

• Navigational intent means the user is looking for a specific website or page.
• Informational intent applies when someone seeks an answer to a question or wants to learn more about a topic.
• Commercial intent involves researching products or services before making a decision.
• Transactional intent indicates the user is ready to buy a product or service.

When writing meta descriptions, ask yourself what someone looking for that specific page is trying to do, and promise them that the page will provide precisely what they are looking for.

Keep voice search in mind

When crafting meta descriptions, remember voice search and visitors who use screen readers. 

Try reading your meta description out loud to see how it sounds. If something sounds clunky or awkward, consider rewriting it to ensure that it’s accessible to all.

Leverage emotional sentiment

Writing a meta description is like writing any other copy or content on your site. 

Since emotional language drives action, here are 801 power words that can help make your meta description copy more motivating. 

Include calls to action

Meta descriptions are essentially ads for web pages. They should motivate the reader to click through to your site (instead of a different search result). If you’ve never written a call-to-action before, start with this guide from Barefoot Writer.

Updating meta descriptions on WordPress websites

All of the advice we’ve shared so far applies no matter which CMS or website builder you choose. But this is the WordPress.com blog; if you’re here, you probably want to know how to implement better meta descriptions on your own WordPress site.

Here are a few options for updating your meta descriptions:

Jetpack

Every WordPress.com website comes with Jetpack, which enables tons of awesome features, and sites on the Business plan and above can use Jetpack’s SEO features to edit title tags and meta descriptions. 

If your site is hosted with a different provider, you can use Jetpack’s SEO tools too.

Other plugins

There are several popular WordPress SEO plugins that enable title tag and meta description editing (and a whole lot more). Here are three options:

• Yoast
• All in One SEO (AIOSEO)
• Rank Math SEO

WordPress.com users can use third-party plugins on the Business plan and above.

Go optimize your meta descriptions

If you take anything away from this article, it should be this: meta descriptions may be short, but they can influence how often your pages appear and get clicked in search results. 

Now you know how to write ones that work, so give your pages the click-worthy summaries they deserve. Want to keep sharpening your SEO skills? Check out our guide to optimizing your WordPress.com site for search.

WordPress 6.8.1 is now available!

This minor release includes fixes for 15 bugs throughout Core and the Block Editor addressing issues affecting multiple areas of WordPress including the block editor, multisite, and REST API. For a full list of bug fixes, please refer to the release candidate announcement.

WordPress 6.8.1 is a short-cycle maintenance release. More maintenance releases will be made available throughout 2025.

If you have sites that support automatic background updates, the update process will begin automatically.

You can download WordPress 6.8.1 from WordPress.org, or visit your WordPress Dashboard, click “Updates”, and then click “Update Now”. For more information on this release, please visit the HelpHub site.

Thank you to these WordPress contributors

This release was led by Aaron Jorbin.

WordPress 6.8.1 would not have been possible without the contributions of the following people. Their asynchronous coordination to deliver maintenance fixes into a stable release is a testament to the power and capability of the WordPress community.

Aaron Jorbin, Adam Silverstein, Aki Hamano, Ankit Panchal, bernhard-reiter, Carolina Nymark, Code Amp, Daniel Richards, David Baumwald, David Levine, Dilip Bheda, Dion Hulse, dsawyers, eduwass, Erick Hitter, Estela Rueda, Fabian Kägy, George Mamadashvili, Greg Ziółkowski, H. Kabir, hideishi, Himanshu Pathak, jarekmorawski, Jb Audras, Jeffrey Paul, Jeffro, Jeremy Felt, Joe Dolson, Joe McGill, Joen A., John James Jacoby, Jonathan Desrosiers, Jonny Harris, Joshua Goode, Karthikeya Bethu, Kingsley Felix, Konstantin Obenland, Lena Morita, LilGames, megane9988, Michelle Schulp Hunt, Mitchell Austin, Mukesh Panchal, nickwilmot, Nikunj Hatkar, Pascal Birchler, Paul Biron, Peter Wilson, Pratik Londhe, Presskopp, Sainath Poojary, Scott Kingsley Clark, Scott Reilly, Sergey Biryukov, SirLouen, Sören Wünsch, Sourav Pahwa, Stephen Bernhardt, takuword, Tushar Patel, Weston Ruter, Yogesh Bhutkar

How to contribute

To get involved in WordPress core development, head over to Trac, pick a ticket, and join the conversation in the #core and #6-8-release-leads channels. Need help? Check out the Core Contributor Handbook.

Props to @estelaris and @joedolson for proofreading.

As I said, we’re dropping all the human blocks. Community guidelines, directory guidelines, and such will need to be followed going forward, but whatever blocks were in place before are now cleared. It may take a few days, but any pre-existing blocks are considered bugs to be fixed.

Each WordPress release celebrates an artist who has left an indelible mark on music.  WordPress 6.8, code-named “Cecil,” honors the legendary pianist and jazz pioneer Cecil Taylor.

Classically trained yet relentlessly unconventional, Taylor reimagined the piano as a percussive instrument—layering tone clusters, polyphony, and rhythm into a sound both chaotic and precise. His music defied expectation, finding form in disorder and harmony in dissonance.

That same spirit drives WordPress 6.8. Embrace its bold new features with the same curiosity and experimentation that defined Cecil’s sound.

Welcome to WordPress 6.8!

WordPress 6.8 polishes and refines the tools that you use every day, making your site faster, more secure, and easier to manage.  The Style Book now has a structured layout and works with Classic themes, giving you more control over global styles. Speculative loading speeds up navigation by preloading links before users navigate to them, bcrypt hashing strengthens password security automatically, and database optimizations improve performance.

Download WordPress 6.8 “Cecil”

A release polished to a high sheen.

The Style Book gets a cleaner look—and a few new tricks.

The Style Book has a new, structured layout and clearer labels, to make it even easier to edit colors, typography—almost all your site styles—in one place.

Plus, now you can see it in Classic themes that have editor-styles or a theme.json file.  Find the Style Book under Appearance > Design and use it to preview your theme’s evolution, as you edit CSS or make changes in the Customizer.

Editor improvements

Easier ways to see your options in Data Views, and you can exclude sticky posts from the Query Loop.  Plus, you’ll find lots of little improvements in the editor that smooth your way through everything you build.

Near-instant page loads, thanks to Speculative Loading

In WordPress 6.8, pages load faster than ever.  When you or your user hovers over or clicks a link, WordPress may preload the next page, for a smoother, near-instant experience. The system balances speed and efficiency, and you can control how it works, with a plugin or your own code.  This feature only works in modern browsers—older ones will simply ignore it without any impact.

Stronger password security with bcrypt

Now passwords are harder to crack with bcrypt hashing, which takes a lot more computing power to break.  This strengthens overall security, as do other encryption improvements across WordPress.  You don’t need to do anything—everything updates automatically.

Accessibility improvements

100+ accessibility fixes and enhancements touch a broad spectrum of the WordPress experience.  This release includes fixes to every bundled theme, improvements to the navigation menu management, the customizer, and simplified labeling.  The Block Editor has over 70 improvements to blocks, DataViews, and to its overall user experience.

Performance updates

WordPress 6.8 packs a wide range of performance fixes and enhancements to speed up everything from editing to browsing.  Beyond speculative loading, WordPress 6.8 pays special attention to the block editor, block type registration, and query caching.  Plus, imagine never waiting longer than 50 milliseconds—for any interaction.  In WordPress 6.8, the Interactivity API takes a first step toward that goal.

And much more

For a comprehensive overview of all the new features and enhancements in WordPress 6.8, please visit the feature-showcase website.

Check out what’s new

Learn more about WordPress 6.8

Learn WordPress is a free resource for new and experienced WordPress users.  Learn is stocked with how-to videos on using various features in WordPress, interactive workshops for exploring topics in-depth, and lesson plans for diving deep into specific areas of WordPress.

Read the WordPress 6.8 Release Notes for information on installation, enhancements, fixed issues, release contributors, learning resources, and the list of file changes.

Explore the WordPress 6.8 Field Guide.  Learn about the changes in this release with detailed developer notes to help you build with WordPress.

The 6.8 release squad

Every release comes to you from a dedicated team of enthusiastic contributors who help keep things on track and moving smoothly.  The team that has led 6.8 is a cross-functional group of contributors who are always ready to champion ideas, remove blockers, and resolve issues.

• Release Lead: Matt Mullenweg
• Release Coordination: Jeffrey Paul and Michelle Frechette
• Tech Leads: Joe McGill, Jonathan Desrosiers, and George Mamadashvili
• Triage Lead: Jb Audras
• Design Lead: Tammie Lister
• Performance Lead: Felix Arntz
• Test Lead: Krupa Nanda

Thank you, contributors

The mission of WordPress is to democratize publishing and embody the freedoms that come with open source.  A global and diverse community of people collaborating to strengthen the software supports this effort.

WordPress 6.8 reflects the tireless efforts and passion of more than 900 contributors in more than 60 countries all over the world. This release also welcomed over 250 first-time contributors! 

Their collaboration delivered more than 320 enhancements and fixes, ensuring a stable release for all—a testament to the power and capability of the WordPress open source community.

Aaron Jorbin · Aaron Robertshaw · Aashish Sharma · Abha Thakor · Abhay Kulkarni · abhi3315 · AdaKaleh · Adam Silverstein · Adam Zieliński · Adhun Anand · Aditya Bansode · Adrian Jagusch · aduth · Ahir Hemant · Ahmar Zaidi · Ahmed Kabir Chaion · Ahmed Saeed · Ahsan Khan · Aishwarrya Pande · Ajay Ghaghretiya · Ajay Maurya · Ajit Bohra · Akanshu Singh · Aki Hamano · Akira Tachibana · aks30498 · Akshat Kakkad · Akshay Dhere · Albert Juhé Lluveras · Alessio · Alex Concha · Alex Florisca · Alex Lende · Alex Stine · Alexander Bigga · Alexandre Buffet · Alexei Samarschi · alexschmitz · Ali Akbar Reyad · allilevine · alpipego · Alvaro Gómez · Amaan Khan · Amber Hinds · Amimul Ihsan · Amin · Amit Bhosale · Amit Raj · Ammar Mohamed Fath Allah Abd-Elaaty Massoud · amolebonde · Anand Raj · Anders Norén · Andrea Fercia · Andrea Roenning · Andreas Pedersen · Andrei Draganescu · Andrei Lupu · Andrew Nacin · Andrew Ozz · Andrew Serong · Andrew Ssanya · Andrey "Rarst" Savchenko · André Maneiro · Andy Fragen · Anh Tran · Ankit Gade · Ankit K Gupta · Ankit Kumar Shah · Ankit Panchal · Ankit Patel · Anmol Verma · annchichi · Anne-Mieke Bovelett · annezazu · Anthony Burchell · Anthony Hortin · Anton Vlasenko · Anuj Singh · Anveshika Srivastava · Ari Stathopoulos · Ariel Maidana · arnaudbroes · arnoutblueshell · Artemio Morales · Asish Chandra Mohon · Au · autotutorial · Ayesh Karunaratne · Béryl de La Grandière · BackuPs · Balu B · Barry · Beatriz Fialho · ben · Ben Dwyer · Ben Sutcliffe · Benazeer · Benedikt Ledl · Benjamin Zekavica · Benoit Chantre · bernhard-reiter · Bero · bgermann · Bhavik Kalpesh · Bijit Deb · Birgir Erlendsson (birgire) · Birgit Pauli-Haack · Bishal Shrestha · BjornW · bluantinoo · BogdanUngureanu · Boro Sitnikovski · Brad · Brad Jorsch · Bradley Taylor · Brandon Hubbard · Brandon Payton · brettsmason · brevilo · Brian Alexander · Brian Coords · Brian Haas · Bronson Quick · Bryan Schneidewind · burak · burnuser · Calvin Alkan · Calvin Alkan · Carlos Bravo · Carolina Nymark · cbirdsong · cgastrell · charleslf · chiilog (Chiaki Okamoto) · chintanmachhi207 · ChriCo · chriscct7 · chrisdotdotdot · Christoph Daum · claimableperch · Claudiu Lodromanean · codebymikey · codersantosh · Colin Stewart · ColinD · colinleroy · Corey Worrell · Courtney Robertson · Cris Busquets · Crisoforo Gaspar · ctienshi · cweiske · cybeardjm · Cyrille · Cyrille Sanson · Daedalon · Dakota Chichester · Damien Alleyne · Damon Cook · Dan Knauss · danht · Dani Guardiola · Daniel Bachhuber · Daniel Post · Daniel Richards · Daniele Scasciafratte · danielpataki · danielvann · darerodz · Darren Hewer · Dave Loodts · David Aguilera · David Arnado · David Baumwald · David Biňovec · David Bowman · David Calhoun · David FARGIER · David Herrera · David Innes · David Levine · David Rozando · David Shanske · David Smith · daymobrew · deadduck169 · Dean Sas · Debabrata Karfa · DEBARGHYA BANERJEE · Deep Patel · Deepak Rohilla · Dennis Ploetner · Dennis Snell · Densi Nakum · designsimply · Devansh Chaudhary · Dhananjay Kuber · Dharmesh Patel · Dhaval Kapadane · Dheeraj Bhosale · Dhrumil Kumbhani · Dhruvang21 · Dhruvi Shah · Dhruvik Malaviya · dilip · Dilip Bheda · Dilip Hingarajiya · Dilip Modhavadiya · DingGuodong · Dion Hulse · Divyesh_kakrecha · dj.cowan · Django · dnnsjsk · Doeke Norg · dogee · domenicdenicola · Dominik Schilling · donalirl · dooperweb · Doug Wollison · dretzlaff · Drew Jaynes · Drivingralle · Dwain Maralack · Earthman Media · eclev91 · Eddy · Edward Caissie · efc · Elena Brescacin · elizaan36 · Ella van Durpe · Emerson Maningo · Emilie LEBRUN · Emmanuel Atsé · Enrico Battocchi · Eric Dye · Erick Hitter · Erik · Erik · Eshaan Dabasiya · Estela Rueda · Evan Herman · Even Tobiesen · Fabian Kägy · Fabian Todt · Faisal Ahammad · Faisal Alvi · Faizan Nabi · Felix Arntz · Felix Renicks · finntown · Firoz Sabaliya · Francesca Marano · Francis Cabusas · Francisco · Frank B. · Frank Klein · Fransisca H · frkly · fushar · FX Bénard · gaellebesson · Gajendra Singh · Galib Hayder · Gan Eng Chin · Garrett Hyder · Gary Jones · Gary Pendergast · Gennady Kovshenin · George Mamadashvili · Gerardo Pacheco · ghinamt · Girish Panchal · giuriani · Glen Davies · Glynn Quelch · Gopal Krishnan · Grant M. Kinney · Greg Ziółkowski · gregbenz · grgarside · Guido · Guillaume TURPIN · Gulamdastgir Momin · Héctor Prieto · Halil Kaya · Halyna Yampolska · Hameem Mahdad Kader · Hannes Leismann · Hans-Gerd Gerhards · Hareesh S · harrym · Harshal Kadu · Haz · hekuranredev · Helen Hou-Sandi · Hemant Kothari · Henrique Iamarino · Henry Wright · Herve THOMAS · hideishi · Hidekazu Ishikawa · Hilay Trivedi · Himani Panchal · Himanshu Pathak · Hit Bhalodia · Hitesh Dhokai · Hovhannes Hovakimyan · hueitan · humanify · hussain896 · huubl · Huzaifa Al Mesbah · Ian Dunn · ilovecats7 · Imran · Imran Hossain (a11n) · Indira Biswas · indithemes · Isabel Brison · iseulde · Isu · Ivan Kristianto · Jack · Jagir Bahesh · Jainil Shah · Jake Spurlock · James Koster · James Monroe · James Payne · James Robinson · James Sansbury · Jamie Blomerus · jammycakes · Jan Lysý · janak Kaneriya · janusdev · Jarda Snajdr · jarekmorawski · Jason Cosper · Jason LeMahieu (MadtownLems) · Jason Sauerwald · Javier Casares · Jayaram · JD Ahir · jdnd · Jean-Baptiste Audras · Jeff Chi · Jeff Golenski · Jeff Ong · Jeff Paul · jeflopo · Jenny Dupuy · jepperask · Jeremy Felt · jeremy80 · jeremyroman · jeryj · jessedyck · Jessica Lyschik · Jigar Bhanushali · Jigar Panchal · jnweaver · Joan Artes · jodamo5 · Joe Dolson · Joe Hoyle · Joe McGill · joecsmalley · Joen Asmussen · Johannes Jülg · John Blackbourn · John James Jacoby · John Regan · Jomar Jay Corona · Jomon Thomas Lobo · Jon Surrell · Jonathan Bossenger · Jonathan Desrosiers · Jong · Joni Erkkilä · Jonny Harris · jonnyauk · joomskys · Joost de Valk · jordesign · Jorge Costa · Jos Velasco · Jose Varghese · Josef Seidl · Joseph Scott · Joshua Wold · jottevanger · Jouni Kananen · Joy · Juan Aldasoro · juanbuis · JuanMa Garrido · juanwp22 · Jules Colle · julianmar · Julie Moynat · Juliette Reinders Folmer · Julio Potier · Justin Tadlock · Juzar · K. Adam White · KafleG · Kai Hao · Kaito Hanamori · Kamal Hosen · KAP ASIAs · Kapil Paul · karlgroves · Karol Manijak · Karthick Murugan · Karthik Thayyil · Karthikeya Bethu · Kaspars · Kathryn Presner · Kausar Alam · keithdevon · Kel Santiago-Pilarski · Kelly Choyce-Dwan · Kelly Mears · keoshi · Ketan Niruke · Ketan Patel · Kevinleary.net · Kharis Sulistiyono · Kira Schroder · KJ Roelke · kkmuffme · Knut Sparhell · kohheepeace · Konstantinos Galanakis · Konstantinos Xenos · kristastevens · Krupa Nanda · Krupal Lakhia · laurelfulford · Laurent MILLET · Lax Mariappan · Laxman Prajapati · lcarevic · Lee · Lee Willis · leedxw · Lena Morita · lenasterg · leszeks · leup · levskipg · Liam Gladdy · Louis · Lourens · Love Soni · Lovekesh Kumar · lovewpmu · Lovro Hrust · Lox · ltrihan · Luigi Teschio · Luis Felipe Zaguini · luisherranz · Lukasz · Luke Cavanagh · Mário Santos · maciejmackowiak · Madhu Dollu · madpeter · Magda Rogier · Maggie Cabrera · Mahesh Prajapati · Mai · maikelraow · Maja Benke · Makarand G. Mane · mallorydxw-old · manfcarlo · Manoj Maharrshi · Manzoor Wani (a11n) · Marc · Marcelo de Moraes Serpa · marchalyoan · Marchetti Design · Marco Ciampini · Maria Yohana · marian1 · Marianna · Marie · Marin Atanasov · Marine EVAIN · Mario Peshev · Mario Santos · Marius L. J. · Mark Howells-Mead · Mark Uraine · Mark-k · martin.krcho · Mary Baum · Masud Rana · Mathieu Paapst · Matias Benedetto · Matias Ventura · Matt (Thomas) Miklic · Matt Mullenweg · Matt Robinson · Matt West · Matthew · Matthew Boynes · mattryanwalker · Mauriac AZOUA · Maxime Meganck · maximebj · Mayank Tripathi · Mayur Prajapati · Md Abdullah Al Arif · Md Abul Bashar · Md Hafijur Rahman · MD Kawsar Chowdhury · Md Mahdi Hasan · Md. Ibrahim Khalil · Md. Najmul Islam · Md.Mehedi Hasan · mdviralsampat · megane9988 · MelissaH · metropolis_john · Michael Adams (mdawaffe) · Michael Burridge · Michael Willman · Michal Czaplinski · Michelle Frechette · micromadness · Miguel Fonseca · Miguel Torres · Mijo T J · Mikael Korpela · Mike Bijon · Mike Ritter · Mikin Chauhan · Milana Cap · Milind More · mimi · miroku · Mitchell Austin · Modi Sahil · modulbuero · Mohamed Aboelfotoh Mohamed · Mohit Dadhich · mojorob · Morais Junior · Moses Cursor Ssebunya · Mosne / Paolo Tesei · mr660 · mreishus · mrwweb · mt · Muddassir Rahman Nasim · Muhibul Haque · mujuonly · Mukesh Panchal · Mukul Singh · My1 · n8finch · Nadir Seghir · nandow · NANI SAMIREDDY · Narendra Sishodiya · Naresh Bheda · Natalia T · Nathan Johnson · navneet · Navneet Kaur · Nazmul Hasan Robin · Ned Zimmerman · neotrope · NerQuiles · net · Nick Diego · nickgalvez · Nicolas RIVIERE · nicolasleroy · nidhidhandhukiya · Nik Tsekouras · Nikan Radan · Nikita Solanki · Nikunj Hatkar · Nilesh Shiragave · Niraj Giri · Nithin SreeRaj · Noam Eppel · Noruzzaman · nosilver4u · oceantober · Olaf Lederer · Olga Gleckler · Oliver Campion · Omer Korner · Oscar Arzola · Oskari Groenroos · othernoel · Ov3rfly · Paal Joachim Romdahl · pampfelimetten · Parin Panjari · Parth Dodiya · Parth vataliya · Pascal Birchler · Pascal Casier · Patel Jaymin · Patrick Lumumba · Paul · Paul Bearne · Paul Biron · Paul English · Paul Kevan · paullb · Paulo Pinto · Paulo Trentin · Pavan Patil · Pawan Kumar · Pedro Mendonça · Peter Rubin · Peter Westwood · Peter Wilson · peter8nss · peterdavehello · petitphp · philliproth · philwebs · Pitam Dey · pixlpirate · podpirate · Pooja Bhimani · Pooja Killekar (Muchandikar) · pooja9712 · Praful Patel · Prasad Karmalkar · prashant · Prashant Baldha · Prashant Patil · Prathamesh Shirke · prathameshbhagat1511 · Pratik Bhatt · Pratik Gandhi · Pratik Londhe · Presskopp · Priyank Vadhavana · Pushpender Singh · Q · qhaensler · Rafael Fischmann · Rahul Prajapati · Raj Patel · Rajat Patel · Rajendra Patel · Rajendra Patil · Rajesh Radadiya · Rajesh Rathod · Rajin Sharwar · Ramon Ahnert · Ramon Corrales · Ramon James · Ravi Gadhiya · redkite · Rehan Ali · Rejaul Alom Khan · Remco · Renatho · Renz Jay Sanchez · Riad Benguella · Rich Tabor · Riddhi Dave · Rinkal Pagdar · Rishav Dutta · Rishi Mehta · Rishi Shah · Rishit Gupta · rkyburz · Robert Anderson · Robert Chapin · Robert Ghetau · Robert Seyfriedsberger · robertstaddon · Robin Martijn · Rodrigo Arias · Rodrigo Primo · Rogier Lankhorst · Rohan Jha · rohitmathur7 · rohjay · room34 · Rotem Gelbart · Roy Orbitson · Roy Tanck · roybellingan · rseigel · Ruchir Goswami · Rudrakshi Gupta · Rupesh Patil · rupw · Ruturaj Raval · rvoigt · Ryan Fredlund · Ryan Hellyer · Ryan McCue · Ryan Welcher · Ryo · S P Pramodh · Sébastien SERRE · Sérgio Gomes · Sören Wünsch · Sabbir Ahmed · sabrineg · Saeed Piri · Sagar Lakhani · Sagar Prajapati · Sagar Tamang · sailpete · Sainath Poojary · sally · samiamnot · Sampat Viral · Samsul Islam Rana · Samuel Wood (Otto) · Sanyogg Shelar · Sarah Norris · Sarath AR · Sarthak Nagoshe · Sathiya Venkatesan · Saul Fougnier · saurabh.dhariwal · Saxon Fletcher · Sayan Datta · Sayedul Sayem · sbathompson · Scott Arciszewski · scribu · Sean Fisher · seanlanglands · Sebastian Pisula · Seif Radwane · Sergey Biryukov · sergiogutierrez · Seth Rubenstein · Shadi G شادي جـ · Shail Mehta · Shalin Shah · Shane Muirhead · Shoe · Shraddha Gore · shreyashd21 · Shubham Kumar Bansal · Shubham Patil · shulard · Shyam Kariya · Siddharth Thevaril · siliconforks · Simone Maranzana · SirLouen · sjefen6 · Slava Abakumov · Slavco Mihajloski · smerriman · Sneha Patil · Sourabh Jain · Sourav Pahwa · soyeb salar · Spencer Finnell · Spenser Hale · spmultidots · spncr · Sridhar Katakam · Stefan Seidner-Britting · Stefano Minoia · stein2nd · Stephen Bernhardt · Stephen Edgar · Steve Dufresne · stimul · strarsis · Stuart McAlpine · Subodh Rajpopat · Subrata Sarkar · SUHAS SUTAR · Sukhendu Sekhar Guria · Sumit Bagthariya · Sumit Singh · Sumon Sarker · SunilPrajapati · Suraj Sutar · swalkinshaw · Sybre Waaijer · Synchro · t.schwarz · Taco Verdonschot · Taegon Kim · Takashi Irie · Takashi Kitajima · Takayuki Miyoshi · takuword · Tammie Lister · Tanbir Ahmod · Tapan Kumer Das · th23 · Thakor Darshil · thelmachido a11n · thomaswm · Thrijith Thankachan · tiago · TigriWeb · Till Krüss · Tim Brathärig · Tim Sheehan · Tim W · Timi Wahalahti · Timothée Brosille · Timothy Jacobs · Timur Kamaev · Tirth Doshi · TJarrett · Tobias Bäthge · tobifjellner (Tor-Bjorn “Tobi” Fjellner) · Tom Gugel · Tom Rhodes · Tomoki Shimomura · Toni Viemerö · Tonya Mork · Toro_Unit (Hiroshi Urabe) · Torsten Landsiedel · tropicalista · Troy Chaplin · Trupti Kanzariya · Trusha · tunetheweb · Tung Du · Tushar Patel · TyB · tysonlmao · Ugyen Dorji · Umesh Singh · Unsal Korkmaz · up1512001 · upadalavipul · utrenkner · Vagelis · Vaibhav Singh Web · Vaibhav Tukaram Nawale · Vania · vee · Vegard S. · vgnavada · Vicente Canales · Victoria - a11n · Vijayan · Vijaysinh Zala · Viktor Szépe · Vinit · Vipul Gupta · Vipul Patil · Virgildia · Virginie Garnier · virginienacci · Vishy Moghan · vivekawsm · Vrishabh Jasani · vykesmac · wadowad · Web-Pepper · WebMan Design | Oliver Juhas · Wes Theron · Weston Ruter · whaze · Will Skora · williampatton · wongjn · World Web Technology · wpgerd · wwdes · xate · xavilc · xpurichan · Yahil Madakiya · Yani · Yash Kukreja · yellowafterlife · Yogesh Bhutkar · Yui · Yuliyan Slavchev · yuu · zaoyao · Zargarov · Zebulan Stanphill · zeelthakkar · Zunaid Amin · 耗子

More than 60 locales have fully translated WordPress 6.8 into their language making this one of the most translated releases ever on day one.  Community translators are working hard to ensure more translations are on their way.  Thank you to everyone who helps make WordPress available in 200 languages.

Last but not least, thanks to the volunteers who contribute to the support forums by answering questions from WordPress users worldwide.

Get involved

Participation in WordPress goes far beyond coding. And learning more and getting involved is easy.  Discover the teams that come together to Make WordPress and use this interactive tool to help you decide which is right for you.

WordCamp Europe 2025 will be held in gorgeous Basel, Switzerland, from June 5 to 7. It will bring together open source enthusiasts, developers, and WordPress professionals from across the region—and the world!

This year’s event offers fresh perspectives, engaging conversations, and countless opportunities to connect with the WordPress community, agencies, and innovators over three action-packed days of learning, networking, and collaboration.

Keynotes, panels, and deep dives

The main conference, which will be held on June 6th and 7th, will feature a lineup of notable keynote sessions, including diverse sessions on business strategy and building innovative modern features, open-source advocacy, accessibility, and more. For those looking to sharpen their skills, presentations will dive deep into topics like SEO for WordPress, performance optimization, speed-builds, and leveraging AI.

Q&A Fireside Chat

You can join Mary Hubbard, the WordPress Executive Director, and Matt Mullenweg, co-founder of the WordPress project on June 7th to discuss WordPress and its community, followed by an in-person Q&A session here in Basel.

Explore Basel

Basel, the third-largest city in Switzerland, is filled with historical buildings, a cathedral, museums, and hidden gems! You can get around Basel and experience it yourself using your BaselCard, which allows you to hop on and off all public transportation without a worry. A walk down Basel’s river Rhine could be the perfect evening during your visit to WordCamp Europe!

Find accommodations in Basel
Learn about BaselCard benefits
Need a visa? Apply by May 10, 2025

Plan Your WordCamp Europe Experience See the full schedule, plan your sessions, and maximize your time in Basel.

Get WordCamp-ready

Make sure to secure your WordCamp Europe 2025 tickets (if you haven’t already!)

Follow WordCamp Europe news on Bluesky, Instagram, Facebook, LinkedIn, Threads, Mastodon, and X/Twitter for real-time updates!

You can also help us spread the word about WordCamp Europe this year! Post about your attendance using our ready-made texts or we also encourage you to use your own voice – you know your community best.

And as always, be part of the conversation! Whether you’re attending in-person in Basel or following along online, share your experiences using the tags #WCEU and #WordPress on all social media networks!

Basel is calling—see you at WordCamp Europe 2025!

Thank you to @dolgelukkig for drafting this copy.

The third release candidate (“RC3”) for WordPress 6.8 is ready for download and testing!

This version of the WordPress software is under development.  Please do not install, run, or test this version of WordPress on production or mission-critical websites.  Instead, it’s recommended that you evaluate RC3 on a test server and site.

Reaching this phase of the release cycle is an important milestone.  While release candidates are considered ready for release, testing remains crucial to ensure that everything in WordPress 6.8 is the best it can be.

You can test WordPress 6.8 RC3 in four ways:

The current target for the WordPress 6.8 release is April 15, 2025. Get an overview of the 6.8 release cycle, and check the Make WordPress Core blog for 6.8-related posts leading up to next week’s release for further details.

What’s in WordPress 6.8 RC3?

Get a recap of WordPress 6.8’s highlighted features in the Beta 1 announcement. For more technical information related to issues addressed since RC2, you can browse the following links:

• GitHub commits for 6.8 since April 1
• Changes committed since April 1

How you can contribute

WordPress is open source software made possible by a passionate community that collaborates and contributes to its development. The resources below outline various ways you can help the world’s most popular open source web platform, regardless of your technical expertise.

Get involved in testing

Testing for issues is critical to ensuring WordPress is performant and stable. It’s also a meaningful way for anyone to contribute. This detailed guide will walk you through testing features in WordPress 6.8.  For those new to testing, follow this general testing guide for more details on getting set up.

If you encounter an issue, please report it to the Alpha/Beta area of the support forums or directly to WordPress Trac if you are comfortable writing a reproducible bug report. You can also check your issue against a list of known bugs.

Curious about testing releases in general?  Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack.

Search for vulnerabilities

From now until the final release of WordPress 6.8 (scheduled for April 15, 2025), the monetary reward for reporting new, unreleased security vulnerabilities is doubled.  Please follow responsible disclosure practices as detailed in the project’s security practices and policies outlined on the HackerOne page and in the security white paper.

Update your theme or plugin

For plugin and theme authors, your products play an integral role in extending the functionality and value of WordPress for all users.  For more details on developer-related changes in 6.8, please review the WordPress 6.8 Field Guide.

Thanks for continuing to test your themes and plugins with the WordPress 6.8 beta releases.  With RC3, you’ll want to conclude your testing and update the “Tested up to” version in your plugin’s readme file to 6.8.

If you find compatibility issues, please post detailed information to the support forum.

Help translate WordPress

Do you speak a language other than English?  ¿Español?  Français?  Русский?  日本語? हिन्दी? मराठी? বাংলা?  You can help translate WordPress into more than 100 languages.

An RC3 haiku

The launch draws closer,
Six-eight sings through RC3,
Almost time to shine.

Thank you to the following contributors for collaborating on this post: @audrasjb, @mamaduka, @krupajnanda, @benjamin_zekavica, @narenin, @joedolson, @courane01, @joemcgill, @marybaum, @kmgalanakis, @umeshsinghin, @wildworks, @mkrndmane.

The second Release Candidate (“RC2”) for WordPress 6.8 is ready for download and testing!

This version of the WordPress software is under development. Please do not install, run, or test this version of WordPress on production or mission-critical websites. Instead, it’s recommended that you evaluate RC2 on a test server and site.

Reaching this phase of the release cycle is an important milestone. While release candidates are considered ready for release, testing remains crucial to ensure that everything in WordPress 6.8 is the best it can be.

You can test WordPress 6.8 RC2 in four ways:

The current target for the WordPress 6.8 release is April 15, 2025.  Get an overview of the 6.8 release cycle, and check the Make WordPress Core blog for 6.8-related posts in the coming weeks for further details.

What’s in WordPress 6.8 RC2?

Get a recap of WordPress 6.8’s highlighted features in the Beta 1 announcement. For more technical information related to issues addressed since RC1, you can browse the following links:

• GitHub commits for 6.8 since March 25
• Closed Trac tickets since March 25

Want to look deeper into the details and technical notes for this release? These recent posts cover some of the latest updates:

• Speculative Loading in 6.8
• WordPress 6.8 will use bcrypt for password hashing
• Roster of design tools per block (WordPress 6.8 edition)
• More efficient block type registration in 6.8
• Updates to user-interface components in WordPress 6.8
• Interactivity API best practices in 6.8
• Internationalization improvements in 6.8

How you can contribute

WordPress is open source software made possible by a passionate community of people collaborating on and contributing to its development. The resources below outline various ways you can help the world’s most popular open source web platform, regardless of your technical expertise.

Get involved in testing

Testing for issues is critical to ensuring WordPress is performant and stable.  It’s also a meaningful way for anyone to contribute.  This detailed guide will walk you through testing features in WordPress 6.8.  For those new to testing, follow this general testing guide for more details on getting set up.

If you encounter an issue, please report it to the Alpha/Beta area of the support forums or directly to WordPress Trac if you are comfortable writing a reproducible bug report.  You can also check your issue against a list of known bugs.

Curious about testing releases in general?  Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack.

Search for vulnerabilities

From now until the final release of WordPress 6.8 (scheduled for April 15, 2025), the monetary reward for reporting new, unreleased security vulnerabilities is doubled. Please follow responsible disclosure practices as detailed in the project’s security practices and policies outlined on the HackerOne page and in the security white paper.

Update your theme or plugin

For plugin and theme authors, your products play an integral role in extending the functionality and value of WordPress for all users.

Thanks for continuing to test your themes and plugins with the WordPress 6.8 beta releases. With RC2, you’ll want to conclude your testing and update the “Tested up to” version in your plugin’s readme file to 6.8.

If you find compatibility issues, please post detailed information to the support forum.

Help translate WordPress

Do you speak a language other than English? ¿Español? Français? Русский? 日本語? हिन्दी? বাংলা? मराठी? ಕನ್ನಡ?  You can help translate WordPress into more than 100 languages. This release milestone (RC2) also marks the hard string freeze point of the 6.8 release cycle.

An RC2 haiku

Testing, 1, 2, 3
It’s almost April fifteenth
Squashing all the bugs

Thank you to the following contributors for collaborating on this post: @michelleames, @tacoverdo, @jopdop30, @vgnavada, @jeffpaul.

The first Release Candidate (“RC1”) for WordPress 6.8 is ready for download and testing!

This version of the WordPress software is under development.  Please do not install, run, or test this version of WordPress on production or mission-critical websites.  Instead, it’s recommended that you evaluate RC1 on a test server and site.

Reaching this phase of the release cycle is an important milestone.  While release candidates are considered ready for release, testing remains crucial to ensure that everything in WordPress 6.8 is the best it can be.

You can test WordPress 6.8 RC1 in four ways:

The current target for the WordPress 6.8 release is April 15, 2025.  Get an overview of the 6.8 release cycle, and check the Make WordPress Core blog for 6.8-related posts in the coming weeks for further details.

What’s in WordPress 6.8 RC1?

Get a recap of WordPress 6.8’s highlighted features in the Beta 1 announcement.  For more technical information related to issues addressed since Beta 3, you can browse the following links:

• GitHub commits for 6.8 since March 18
• Closed Trac tickets since March 18

Want to look deeper into the details and technical notes for this release? These recent posts cover some of the latest updates:

• Speculative Loading in 6.8
• WordPress 6.8 will use bcrypt for password hashing
• Roster of design tools per block (WordPress 6.8 edition)
• More efficient block type registration in 6.8
• Updates to user-interface components in WordPress 6.8
• Interactivity API best practices in 6.8
• Internationalization improvements in 6.8

How you can contribute

WordPress is open source software made possible by a passionate community of people collaborating on and contributing to its development.  The resources below outline various ways you can help the world’s most popular open source web platform, regardless of your technical expertise.

Get involved in testing

Testing for issues is critical to ensuring WordPress is performant and stable.  It’s also a meaningful way for anyone to contribute.  This detailed guide will walk you through testing features in WordPress 6.8.  For those new to testing, follow this general testing guide for more details on getting set up.

If you encounter an issue, please report it to the Alpha/Beta area of the support forums or directly to WordPress Trac if you are comfortable writing a reproducible bug report.  You can also check your issue against a list of known bugs.

Curious about testing releases in general?  Follow along with the testing initiatives in Make Core and join the #core-test channel on Making WordPress Slack.

Search for vulnerabilities

From now until the final release of WordPress 6.8 (scheduled for April 15, 2025), the monetary reward for reporting new, unreleased security vulnerabilities is doubled.  Please follow responsible disclosure practices as detailed in the project’s security practices and policies outlined on the HackerOne page and in the security white paper.

Update your theme or plugin

For plugin and theme authors, your products play an integral role in extending the functionality and value of WordPress for all users.

Thanks for continuing to test your themes and plugins with the WordPress 6.8 beta releases.  With RC1, you’ll want to conclude your testing and update the “Tested up to” version in your plugin’s readme file to 6.8.

If you find compatibility issues, please post detailed information to the support forum.

Help translate WordPress

Do you speak a language other than English?  ¿Español?  Français?  Русский?  日本語? हिन्दी? বাংলা? मराठी?  You can help translate WordPress into more than 100 languages.  This release milestone (RC1) also marks the hard string freeze point of the 6.8 release cycle.

An RC1 haiku

March fades, nearly there,
Six-eight hums—a steady beat,
RC greets the world.

Thank you to the following contributors for collaborating on this post: @joemcgill @benjamin_zekavica @courane01 @mkrndmane @audrasjb @areziaal @ankit-k-gupta @krupajnanda @bph.