❌

Normal view

There are new articles available, click to refresh the page.
Before yesterdayHuman Made

Flash Facts: how we marked Black History Month at Human Made

12 November 2026 at 10:33

Black History Month celebrated its 100th anniversary this year. It began as a way to make sure the achievements, culture and history of Black communities didn’t get left out of the wider story, and to recognise that racism is still very much a reality today.

The theme for 2026 was “A Century of Black History Commemorations”, reflecting on a hundred years of achievements, struggles and cultural impact. We wanted to acknowledge it by making it something the whole company shaped together. So we tried something new: Flash Facts.

How Flash Facts worked

We randomly assigned every human at Human Made a country with a rich Afro-diasporic culture. The task was to spend some time finding ONE interesting piece of information about that country. It could be a musician, a piece of history, a book, a recipe or the story behind the flag. Whatever caught your eye first.

Everyone shared their fact on our internal blog in whatever format they liked: a sentence, a photo, a song or a video link.

The point wasn’t to become an expert overnight. It was to spend five minutes being curious about a culture outside your own, and by the end of the month build a better picture of Black history together, one small fact at a time.

A few minutes of curiosity led to new discoveries, personal stories and thoughtful conversations about Black history and culture. I was taken aback by how many people got involved, and I thoroughly enjoyed reading through all of them. Here’s a selection of what we learned.

Music with a much bigger story

Shipra explored Panama’s contribution to reggaeton, tracing its roots through Afro-Panamanian artists who adapted Jamaican dancehall into Spanish in the 1980s. Many were descendants of Caribbean workers who came to build the Panama Canal, and one of the pioneers, El General, is often called one of the fathers of the genre. Following that musical connection also led to learning about the discrimination those workers faced. In the US-run Canal Zone, mostly White workers were paid on the “gold roll” while mostly Black West Indian workers earned about half as much on the “silver roll”, a divide that reached into housing, schools and healthcare.

Samantha introduced us to Brazilian singer Elza Soares, whose music spoke out against racism, sexism and domestic violence. Her career spanned six decades and more than 30 albums, and she was 85 when she released A Mulher do Fim do Mundo (The Woman at the End of the World), which went on to win a Latin Grammy.

Will shared Lisbon’s batida scene, built by young people with family roots in Angola, Cape Verde, Guinea-Bissau and São Tomé. It starts with Angolan kuduro and mixes in house, techno and rhythms like funaná. Producers taught themselves on cheap laptops and passed tracks around on burned CDs and online forums, before the Lisbon label Príncipe Discos started releasing the music in 2011 and artists such as DJ Marfox and Nídia reached international audiences.

Matt explored the story of Angolan musician and athlete Bonga, who used travel through his sporting career to carry messages for the independence movement. He later recorded his debut album, Angola 72, while in exile in Rotterdam, three years before Angola gained independence. One track, “Mona Ki Ngi Xica”, is sung in Kimbundu and is usually translated as “The Child I’m Leaving Behind”. It became an anthem of the independence movement.

Firdaus introduced us to Cameroon’s makossa music, a dance style from the city of Douala, and Manu Dibango’s 1972 track “Soul Makossa”. Often described as the most sampled African song in history, its influence on songs by Michael Jackson and Rihanna means some of us may have recognised the sound before knowing where it came from.

Vladi answered France with a song instead of words, from Beninese-born singer Angélique Kidjo. And Gareth, who admits he’s not much of a dancer, found out that merengue comes from the Dominican Republic. It’s a partner dance with African and European roots, simple enough to give a go, and it has its own national day on 26 November.

Stories and traditions that connect communities

Ivan shared Grenada’s ’Nancy stories, featuring Anansi, the spider character from West African Akan folklore. Generations of storytellers have adapted these tales to local life and to French Creole, where Anansi is also called Compè Zayen: a little spider connecting cultures across an ocean.

Marian explored the Garifuna community in Belize, whose heritage brings together African and Indigenous Caribbean roots. Every year on 19 November, Garifuna Settlement Day celebrates that history through music, dancing and reenactments of ancestors arriving by boat. Garifuna language, music and dance are also recognised by UNESCO as Intangible Cultural Heritage of Humanity.

John introduced us to Uganda’s barkcloth-making tradition, one of the oldest cloth-making traditions in the world. Baganda craftspeople make cloth using bark from Mutuba fig trees, wrapping the trunks in banana leaves so the bark regrows within about a year. The material remains part of ceremonies including coronations and funerals, and UNESCO added it to its intangible cultural heritage list in 2008.

Jon shared the history behind Antigua’s Carnival, explaining its origins as a celebration of emancipation. When slavery was formally abolished across the British Caribbean on 1 August 1834, most enslaved people were pushed into a four-year “apprenticeship” that kept them working unpaid for the same planters. Antigua was one of only two colonies to grant full freedom on the day itself. Carnival was created in 1957 to celebrate that date, so behind the costumes, steel pan and calypso is a commemoration of freedom.

Zoe’s contribution on Veracruz, Mexico, gave us another musical connection: the roots of “La Bamba”. Zoe also highlighted traditions in which dancers contribute to the percussion, creating rhythm with their feet as well as their instruments.

Ryan C and Rob both found that Vodun, the religion often called Voodoo, is central to life along the old “Slave Coast”. Ryan learned that Vodun originated in Benin, where it’s an officially recognised religion and thousands gather in Ouidah every January for National Vodun Day. Next door in Togo, Rob discovered that the capital, Lomé, is home to the Akodessawa Fetish Market, the largest Vodun market in the world, and one of the ways Togo keeps its Indigenous identity alive.

Pioneers worth knowing about

Ant introduced us to Senegalese AI researchers Rose Dieng and Moustapha Cissé. Rose became the first African woman admitted to France’s École Polytechnique in the 1970s, and went on to be one of the early researchers on the semantic web, working on how knowledge could be captured and shared between people and software. Moustapha went on to lead Google’s first AI research centre in Africa, in Accra, and later founded a health technology company. Ant’s contribution explored Rose’s work on making knowledge easier to share and Moustapha’s efforts to build AI research and technology that serve communities in Africa. As Ant put it, he found no evidence the two ever met, “so this is a lineage rather than a handover”.

Tom reflected on Diane Abbott’s career, including becoming the UK’s first Black woman MP in 1987 and, today, Mother of the House. His contribution also raised an important point: greater representation matters, but it doesn’t mean racism or unequal treatment have disappeared.

Vojislav shared the story of Boy Ecury, an Aruban student who joined the Dutch resistance during the German occupation. His resistance work included sabotage operations and helping Allied pilots and people in hiding.

Leyla introduced us to Dame Eugenia Charles, Dominica’s first female lawyer and later its Prime Minister. In 1980 she became the first woman to lead a government in the Caribbean, and she served for 15 years. Leyla explored her fight for press freedom and the barriers she broke as a Black woman in law and politics.

Sarah told the story of Pedro Camejo, a Black general in Venezuela’s War of Independence who was said to always be the first to ride into battle. Mortally wounded at the Battle of Carabobo, he rode back to General Páez to say goodbye, telling him he had come to say farewell because he was already dead. A statue of him stands in Caracas today.

Petya discovered that in 2008 Rwanda became the first country in the world with an elected national parliament where women held a majority of seats. Women now hold around two-thirds of the seats in its Chamber of Deputies.

Jenny highlighted two Nobel laureates from Saint Lucia: economist Sir Arthur Lewis and poet Derek Walcott. Two more names to explore, with contributions spanning economics and literature.

Celebrating culture means listening to people, too

Person, Accessories, Gemstone

Dominic’s contribution on Honduras asked us to consider how Garifuna culture can be celebrated by the tourism industry while communities face threats to their ancestral land. He drew on Christopher A. Loperena’s book The Ends of Paradise, and traced a parallel from the banana industry to modern tourism: Black communities’ labour, land and culture can be central to an economy while the people themselves are treated as outsiders. Appreciating a community’s culture should go alongside listening to its concerns and respecting its rights.

Than explored Suriname’s Maroon communities, formed by people who escaped enslavement and won autonomy from the Dutch through peace treaties in the 18th century. His contribution connected that history of resistance with legal battles to protect ancestral land against logging and mining, cases the Maroons have taken to the Inter-American Court of Human Rights and won.

Simon shared the work of Costa Rican artist Adrián Gómez, whose paintings celebrate Black women and children and the Afro-Caribbean culture of Limón. One of his public artworks shows an Afro-descendant girl on a swing in San José. Simon’s reflection encouraged us to notice whose everyday lives appear in art and shared public spaces.

Ryan C’s research into Benin led to the port of Ouidah, on what was known as the Slave Coast. An estimated one million enslaved Africans were shipped from Ouidah alone to the Americas, a history remembered today at the Gate of No Return memorial.

Ryan M not only shared facts about his country, Liberia, founded as a US colony for formerly enslaved and freeborn Black Americans, but also some further context around Black History Month itself. The month was created in the US and centres on the descendants of the transatlantic slave trade. Ryan reminded us that it doesn’t cover every experience of being treated as “Black”: Aboriginal and Torres Strait Islander peoples, for example, have lived in Australia for at least 50,000 years, and their history and culture are celebrated during NAIDOC Week.

Megan shared some eye-opening political history about Guyana, previously colonised by the British, which only gained independence from colonial rule in 1966. She traced how outside interference in the country’s elections in the 1950s and 1960s deepened divisions between its Afro-Guyanese and Indo-Guyanese communities.

Fatima says she first got to know Zimbabwe as a kid, watching cricket with her brother but has since learned about Great Zimbabwe, the medieval stone city that gives the country its name (“houses of stone” in Shona), and Victoria Falls, known locally as Mosi-oa-Tunya, “the smoke that thunders”.

And a few things that made us smile…

I shared the Ethiopian legend of Kaldi, the goat herder said to have discovered coffee after noticing his goats becoming unusually energetic after eating coffee berries. Apparently, goats got the first coffee break. I also learned that Ethiopia follows its own calendar, with 13 months, running roughly seven to eight years behind the Gregorian one.

Owain kicked us off with our first flash fact, about a very rich emperor from Mali. In the 14th century, Mansa Musa is said to have handed out so much gold on his journey through Egypt that he crashed the Egyptian economy. Owain also shared that the Malians were his favourite civilisation to play in Age of Empires IV.

Kirsty Burgoine discovered that Kevin Lyttle, whose “Turn Me On” reached number 2 in the UK charts, was born in Saint Vincent. She also found that the 1812 eruption of Saint Vincent’s La Soufrière volcano inspired a painting by J. M. W. Turner, which now hangs in Liverpool and which she’s seen in person.

Simon’s exploration of Costa Rican history and art kept bringing him back to Limón, where the arrival of Jamaican railway workers in 1872 shaped so much of the region’s Afro-Caribbean culture: “all roads lead back there, all rail roads anyway”. We’ll allow it.

Petya shared a lovely mention for Ncuti Gatwa, who was born in Rwanda and who she absolutely adores, but whose name she can never learn to pronounce. Mike then pointed out that Ncuti himself got told off by his mum for not pronouncing the “N”, so Petya is in good company.

Kirsty S learned that since the mid-1980s, the government of Côte d’Ivoire has asked other countries not to translate its name, so it’s “Côte d’Ivoire” rather than “Ivory Coast”. It also grows around 40% of the world’s cocoa, so there’s a good chance your chocolate started there.

Ryan C shared lots of great facts about Benin, including that it has the highest rate of twin births in the world, and that its UNESCO-listed W-Arly-Pendjari Complex “harbors the only viable population of lions in the region”.

Jenny found that Saint Lucia is said to be the first country named after a woman (Saint Lucy of Syracuse), and that it’s home to Sulphur Springs, billed as the world’s only “drive-in” volcano.

A couple of us had a map moment. Ivan thought Grenada was a mistake, picturing the Spanish city of Granada, before discovering the Caribbean island nation (not to be confused with nearby Saint Vincent and the Grenadines). Leyla confessed she’d assumed Dominica and the Dominican Republic were the same country. They’re not: Dominica is a small, mountainous island between Guadeloupe and Martinique, known as the “Nature Isle of the Caribbean” and home to the Boiling Lake, the second-largest hot lake in the world.

Jon’s fun aside on Antigua: if you’ve ever played Sid Meier’s Pirates!, you’ve probably docked at English Harbour without realising it’s a real UNESCO World Heritage Site.

Sander learned that Colombia holds roughly 10% of all species on the planet on less than 1% of its land, and Sarah found that Venezuela’s Angel Falls is the world’s highest uninterrupted waterfall, dropping 979 metres.

And Pawel, in true Pawel fashion, turned his flash fact on Burkina Faso into a very smart fact sheet. Zoe was inspired to do the same for Veracruz.

Beyond the month

Several people started by saying how little they knew about their assigned country. That willingness to be curious was the point. Thank you to everyone who shared what caught their attention and gave the rest of us somewhere new to start learning.

Flash Facts was one part of how we marked the month. We also used it to review our hiring practices, looking at more diverse ways to advertise our roles and source candidates from a variety of backgrounds. The first step has been to look at diverse job sites and to make sure our EMEA roles are actively advertised in Africa too.

There’s still work to do to create genuinely inclusive workplaces and communities for everyone, regardless of your background, what language you speak or what colour your skin is. So let’s keep that curiosity going beyond Black History Month: support Black-owned businesses and creators, explore the Black history connected to your own city or region, and make learning about Black history and tackling racism something that happens throughout the year.

The post Flash Facts: how we marked Black History Month at Human Made appeared first on Human Made.

How AI makes me a better engineering manager

9 November 2026 at 11:29

I’m Kirsty, an Engineering Manager at Human Made, where I look after a team of engineers working on projects for enterprise clients.

There have been a lot of conversations about AI recently. A lot of them are understandably focused on technical skills, productivity and making sure we still own our output.

I’ve noticed that when AI comes up in conversations with engineers, the discussion often gravitates towards technical solutions: writing skills, generating code, automating tasks, building tools and making things faster.

Those things are interesting, but they’re not where I’ve personally found the biggest benefit.

I recently read a LeadDev article called AI made me a better engineering leader, which made me think about whether I was measuring the right things. It also made a good point about using AI to get imperfect thinking onto the page, rather than waiting until an idea is fully formed.

That connected with a recent internal discussion at Human Made about readability and our use of AI, particularly the importance of editing AI-generated content and thinking about the audience rather than just accepting whatever it produces.

Both got me thinking about my own use of AI.

I haven’t used AI to vibe-code a revolutionary new tool, and I’m certainly not 1000% more productive. I am still mulling over building a dashboard for my team, though 😉

What I do think is that AI has made me a better Engineering Manager.

Not because it makes decisions for me, or because it has somehow removed the thinking from my job. It has removed some of the bad friction around doing the job.

It’s made it easier for me to get thoughts out of my head, turn conversations into useful documentation, make sense of large amounts of information and communicate things that I probably wouldn’t have got around to communicating before.

TL;DR

AI hasn’t removed the thinking from my job. It’s removed some of the friction around doing it well.

I use it to communicate more clearly, turn conversations into documentation, analyse information, and challenge my own thinking.

I still own the thinking, the decisions and the final output.

There are plenty of ways I use AI, but I’ll focus on three examples where I’ve found the difference particularly noticeable:

  1. Writing – Getting ideas out of my head and into something I can actually share
  2. Documentation – Turning conversations and existing information into something the team can use
  3. Performance reviews – Using AI to help me see the bigger picture across a whole review period

There are plenty of other examples I could give, but these are three where I’ve found the difference particularly noticeable. If you’re mainly interested in the practical examples, feel free to skip straight to them.

The tools I use

I use a few different tools, and I’ve found they each have slightly different strengths.

ChatGPT is the one I tend to reach for when I’m writing. I’ve found the output generally fits my own writing style better, which means I spend less time fighting with the tone of voice and more time actually editing the content. It’s the tool I use most for internal blog posts and generally turning my messy thoughts into something readable.

Claude is particularly useful when I need to work across multiple sources, pull together a lot of information, create technical documentation or build a framework for analysing something. It’s also the tool I tend to use for things like performance reviews, where I’m asking it to find themes across a large amount of information rather than produce something I’m going to publish directly.

Granola sits slightly differently. I use it to capture conversations and meetings, which gives me much better source material to work from afterwards. The important bit for me is that, while I will publish meeting summaries – edited for accuracy of course – I generally go back to the original transcript, rather than relying on the AI-generated meeting summary for bigger tasks.

I’m sure other people have very different experiences with these tools, and I suspect a lot of this comes down to how you prompt them and what you’re asking them to do. These are just the combinations that I’ve found work well for me.

1. Writing: things I actually want to share

One of the biggest changes for me has been writing posts for our internal blog.

As an engineer, I used to love writing documentation. If you’ve ever had me code review something you’d written, you’ll probably remember just how many comments I would leave trying to make things easier to follow and remove assumptions.

Writing things for the wider company was different.

I would agonise over the wording, structure and tone, and whether I’d explained something properly. I wanted things to be perfect.

The inevitable result was that writing took forever, and a lot of things never got published at all.

AI has changed that.

I now start in my markdown notepad, Bear, writing down all my thoughts, arguments, examples and things I think are important. I don’t worry about structure or making it readable. I just get the thinking out of my head.

I then give that to ChatGPT and ask it to turn it into a draft, usually with some guidance about the audience, structure and what I want people to take away.

That’s not normally the finished piece. I’ll edit it myself, changing anything I disagree with, adding what’s missing and removing what’s unnecessary. Then I’ll give it back to ChatGPT to look for repetition, improve awkward sentences or flag anything that doesn’t sound like me.

The important distinction is that the ideas, opinions and decisions are mine. AI is helping me get them into a form other people can actually read.

And I think the results speak for themselves.

Since around July 2025, I’ve written more internal blog posts than I did in all my previous years as an engineer. These aren’t AI-generated thoughts; they’re things I wanted to say but previously struggled to find the time and headspace to communicate.

They’ve covered everything from introducing new tech lead handover documentation and getting better at team communication, to onboarding freelancers into an existing engineering organisation and what we learned from growing the team.

What works for me

  • Get my actual thoughts down before worrying about the prose.
  • Tell the AI who the audience is and what I want them to take away.
  • Edit the output myself, including checking facts and anything important.
  • Use AI again to refine the final version, but make sure it still sounds like me.

The things I try to avoid are pretty simple: letting AI decide what I think, publishing something just because it sounds polished, or using “AI can write it for me” as an excuse not to think about what I actually want to say.

2. Documentation: turning conversations into something useful

The same approach has been incredibly useful for documentation.

When we onboarded five freelancers into my team, for example, we realised our onboarding documentation needed some serious improvement. As a result, we now have a much more robust team wiki that covers onboarding, our approach to project visibility, communication and more.

More recently, one of our engineers had ended up with a huge amount of technical knowledge about a new client project. We had an audit to refer to, but much of the migration work had been done by them and we didn’t yet have much project documentation. Then, unexpectedly, they needed to step away for a few months.

This could have been a serious problem, so I got them on a call and we talked through everything that someone taking over the project would need to know. That conversation was recorded in Granola.

I took the original transcript, not the AI-generated summary, and used Claude to help turn that conversation into a structure for useful project documentation. I then reviewed it, added any information I could from notes they had left, asked Claude to pull in anything relevant from the GitHub repository and the original audit, and then used ChatGPT to make some of the language easier to read without removing the technical detail.

That gave the team a useful starting point much faster than trying to write everything from scratch.

It wasn’t perfect, and that’s important.

I’m not the engineer working on that project, so I couldn’t personally verify every technical detail. I asked engineers in the team to review it, and the expectation is that the documentation continues to evolve as people use it.

AI got us from “all of this information is in one person’s head” to “we have something we can work with” very quickly.

I’ve used similar approaches elsewhere. Conversations about handling support requests on small retainers became a documented support process for one client, which has since evolved into a broader team approach and client-facing documentation. In cases like this, one conversation can end up producing useful documentation for more than one project.

What works for me

  • Start with the original source material wherever possible.
  • Give AI enough context to understand what the documentation is actually for.
  • Get people with the relevant subject-matter knowledge to review it.
  • Treat the first version as a starting point and keep updating it as you learn more.

The main thing I try to avoid is treating an AI summary as a substitute for the original conversation, or letting documentation become “AI-generated and therefore nobody’s responsibility”.

3. Performance reviews: finding the bigger picture

This one is a little less visible because the output isn’t something I’m publishing.

Performance reviews are something I take seriously. I want to understand what has happened over the whole review period, whether someone has genuinely progressed, how that compares with their previous review and where they should focus next.

Historically, that meant manually going through 1:1 notes, project conversations, Slack messages and meeting notes.

Granola has made it much easier to have meaningful conversations without simultaneously worrying about capturing every detail, and I now use Claude to analyse the meeting transcripts and relevant Slack conversations from the review period.

I don’t ask whether someone has had a good review. I ask it to identify themes and pull out the specific conversations so I can review them myself. The judgement and feedback remain mine.

That gives me a much better starting point for asking myself:

What’s the story of this review period?

It helps me avoid over-weighting whatever happened most recently or whatever conversation happens to be freshest in my head.

AI just helps me see the forest rather than spending all my time looking at individual trees.

And, yes, I also occasionally ask it to make my review shorter because apparently I am physically incapable of writing a small amount of text.

What I’ve learned

1. Give AI something real to work with.

The better the raw material, the better the output.

2. Don’t outsource the thinking.

I want AI to help me communicate what I think, not decide what I think.

3. Treat the output as a starting point.

I expect to edit it, challenge it and have other people validate it where appropriate.

4. Be careful what you put into these tools.

Think about what you’re sharing, which tools you’re using, and what your organisation’s policies say. “AI is useful” isn’t a reason to ignore confidentiality, privacy or security.

I’ve been careful throughout to keep things within the tools Human Made has approved, and private where they need to be.

So, has AI made me a better Engineering Manager?

I think it has.

But not because it has made me faster at doing the job. It’s helped me do more of the things I already believed were important.

I communicate more. I document more. I capture more of what we learn. I’m more consistent in things like performance reviews. I’m able to challenge my own thinking more often. And, perhaps most importantly, I’m less likely to have a good idea and then never do anything with it because the friction of writing it down feels like a monumental task.

One of the things from the LeadDev article that has stuck with me is the warning not to confuse feeling faster with actually improving our work. I’m not particularly interested in how many words AI helped me write, how many minutes it saved me, or how many things I can get through in a day.

The improvements I care about are harder to measure:

  • Am I communicating things I wouldn’t otherwise have communicated?
  • Are we capturing knowledge that might otherwise be lost?
  • Are my reviews better because I have more time to look at the bigger picture?
  • Are decisions clearer for the people who need to act on them?

Ultimately, AI hasn’t replaced my judgement. It has made it easier for me to apply it.

So rather than asking “What can AI do for us?”, I’m increasingly interested in asking:

“What good work am I currently not doing because the friction around it is too high?”

That’s where I’ve found the biggest gains.

And for those of you who think I still haven’t answered the most important questions: yes, AI helped me write this, yes, I did ask it to shorten it (this is the best it could do), and no, I still haven’t built that team dashboard.

Yet…

The post How AI makes me a better engineering manager appeared first on Human Made.

Security is a business capability, not a technical function

30 October 2026 at 12:04

WordPress security governance covers the decisions an organisation makes about who owns its platform, who can access it, how the software it depends on stays up to date, and which third parties and AI tools connect to it. In the enterprise estates we audit, most security incidents trace back to one of those decisions.

At Human Made, we work with global publishers, government departments and large enterprises. Across all of them, the organisations with the best security outcomes treat security as something the whole business maintains over time. Their results come from clear ownership, regular access reviews and a defined process for handling change.

This article explains where enterprise security risk starts, why it belongs to the whole business, and how to measure your organisation’s maturity. If you want the practical side first, our WordPress security page covers how Human Made secures enterprise platforms.

Is WordPress secure enough for enterprise organisations?

Yes, when organisations deploy and operate it to meet their security requirements. Many enterprise organisations run WordPress, including major publishers, universities, government agencies and financial services organisations such as Standard Chartered. Those platforms stay secure because their teams patch on a schedule, review who has access and control what gets installed.

WordPress does attract more public discussion of vulnerabilities than most proprietary platforms. That’s partly a matter of scale: it is among the most popular technologies on the web, so more people examine it. It’s also because when someone has fixed a reported issue in core, the WordPress Security Team publishes the details alongside the release. How a WordPress security release happens walks through that process from report to patch in more detail.

A proprietary CMS with the same number of flaws would rarely show them in the same way, because its review happens inside one vendor and customers depend on what the vendor chooses to disclose. A count of public disclosures measures scrutiny. To judge safety, you need to know how quickly fixes ship and how quickly installations apply them.

For an enterprise, the useful test is practical: can the organisation see every system the platform touches, name who manages each one, and respond when something changes?

Where do enterprise security risks come from?

Most security incidents on enterprise platforms start outside the CMS core. A typical estate depends on hosting infrastructure, third-party services, CRM and marketing integrations, analytics, custom code, user accounts and, increasingly, AI applications. Each of those adds a point of exposure.

In WordPress environments, most of the risk falls into four categories.

Third-party software

Plugins, integrations and external services usually carry the largest share of risk. A plugin that its developer maintained well at installation can lose that developer two years later, and an integration added for one campaign can stay connected long after the campaign ends. Without a review process for new additions and a record of what already runs, dependencies accumulate faster than anyone can assess them.

Access management

Enterprise sites rarely have only a handful of administrators. Editorial teams, marketers, regional teams, developers and external agencies all need some level of access, and permissions tend to grow. An agency keeps its login after a project closes, or an editor receives administrator rights to fix one problem and keeps them for years. Any of those accounts could give an attacker a route in.

Operational discipline

Delayed updates, undocumented customisations and unclear ownership weaken a platform gradually. They rarely look urgent on their own, so they tend to persist.

AI tools and new data flows

Teams now connect AI services to content repositories, customer data and internal systems, often quickly and sometimes without central approval. Each connection raises questions about what data the tool can read and where it goes, and about which vendor is now responsible for it.

With the right processes, an organisation can manage all four, and it would face the same four on any other CMS. Our Definitive Guide to Enterprise WordPress Security covers each of these risk areas in more depth, including the operational gaps that tend to build up unnoticed.

Why does WordPress security governance belong to the whole organisation?

Most security failures start with people and processes that no single technical team controls. Marketing chooses tools, regional teams commission microsites, procurement signs agency contracts and legal sets data-handling obligations. When IT alone owns security, every one of those decisions happens without it.

The consequences also reach well beyond IT. A breach on a public platform can trigger regulatory reporting, take revenue-generating services offline, and damage trust with customers and partners. Those outcomes land with the executive team, the board and the compliance function. Treating security as a business capability means the people who carry those consequences also help manage the risk.

In large digital estates, the problem is easy to see. An enterprise might run a main website, a dozen regional platforms, campaign microsites and an internal publishing environment, often on WordPress Multisite. When each owning team secures its property on its own terms, standards drift. One site might enforce single sign-on while another relies on shared passwords, or one team reviews plugins before installing them while another installs whatever the agency recommends. Over time, gaps open up between teams that nobody is responsible for.

WordPress suits this model because organisations can bring it inside their existing security frameworks. Teams choose their own hosting, connect the platform to their identity provider, apply their own access policies and run it through their own audit processes. That makes it possible to set one security standard and apply it across every property in the estate.

What does good WordPress security governance look like?

The organisations with the strongest results tend to have three things in common: named ownership, security built into normal delivery, and standards that apply across every site they run.

Named ownership

Uncertainty over who is responsible for what causes many security problems. As platforms grow, integrations get added and staff and priorities change, so decisions about patching, access reviews or vendor risk fall between departments and wait.

Strong organisations assign that responsibility explicitly, across technology, marketing, operations and external partners, and back it with identity and access management. WordPress supports this through its built-in roles and capabilities, and organisations can add single sign-on with their identity provider using a plugin or a platform layer such as Altis. Each person’s permissions then match their job, and administrators can revoke them centrally when that person leaves.

Security built into delivery

Security checks run on every change throughout a project. Automated scanning flags vulnerable plugins, themes and code while developers are still working on them, when an issue costs far less to fix than one found in a pre-release audit. Releases stop stalling on late reviews, and developers come to treat security as part of their own work.

Shared standards across every site

Shared standards and access control policies give multi-site organisations consistency without forcing every team into the same workflow. A central team defines the baseline: approved plugins, update windows, authentication requirements and the review process for new integrations. Regional and brand teams then build what they need on top of that baseline, and the central team can still see what’s running across the estate.

How does vendor lock-in affect WordPress security governance?

Dependence on a single vendor limits how quickly an organisation can respond when its security requirements change, and procurement teams often miss that cost.

Proprietary platforms often feel easier to govern. One contract covers the software, the infrastructure, the support process and the security controls, so the organisation knows who to call. It may have far less visibility of how the platform works internally, how the vendor handles vulnerabilities, or when a fix will ship, so its security posture rests partly on what the vendor chooses to disclose.

With WordPress, anyone can read and review the codebase. The WordPress project also works closely with some of the largest web hosts, network providers, CDNs and security research institutions, which gives it access to expertise no single vendor employs. Security teams can therefore read the code they are responsible for, follow how the project resolves issues, and make decisions from evidence.

That control becomes important when requirements change. A new regulation, an acquisition or an AI integration can each create security needs that didn’t exist when the contract was signed. On a closed platform, the organisation has to wait for the vendor’s roadmap to catch up, whereas on an open one it can change its hosting, architecture or processes on its own timetable.

The wider WordPress ecosystem helps here too. Enterprises can choose between many hosting providers, agencies, security specialists and support partners. If one relationship stops working, they can end it without replacing the platform or rebuilding their governance.

How is AI changing WordPress security governance?

AI increases the number of systems that can read an organisation’s content, knowledge and customer data, so security teams need a record of which tool connects to which system, and what it can read

Most AI tools need access to data to be useful. A content assistant draws on the editorial archive, a support agent on customer records, and a search tool on internal documentation. Information that used to stay inside one well-governed system now travels to several, and some of those systems are run by vendors the security team has never assessed.

A team might trial a tool to speed up production, find it helpful, and connect it to more systems before anyone asks what it can access. Repeat that across departments and the organisation loses track of where AI is in use and what data it touches.

Organisations should bring AI tools under the same governance as the rest of the platform, before those tools go live. For every AI tool in use, an organisation should know what information it can reach, who is accountable for it, and what risk assessment took place before anyone connected it.

WordPress gives security teams a solid basis for those answers. Its capability-based permissions model is granular and extensible, so administrators can give an AI integration exactly the access it needs and nothing more. Our WordPress AI page covers how Human Made approaches these integrations.

For a structured way to benchmark your organisation’s security maturity, download The Definitive Guide to Enterprise WordPress Security. If you’d like a second opinion on your platform and governance, talk to us about a WordPress security audit.

FAQ: Enterprise WordPress security governance

Yes. Publishers, universities, government agencies and financial services organisations run WordPress at enterprise scale. Like any CMS, its security depends on how teams host, govern and maintain it. Because its codebase is open, anyone can review it, and the WordPress Security Team publishes details of each vulnerability once it has been fixed.

The largest risks are third-party plugins and integrations, permissions that grow without review, delayed updates and unclear ownership, and AI tools with unchecked access to company data. Good WordPress security governance manages each of them.

It means the whole organisation shares ownership of security, including the teams that choose tools, commission sites, manage vendors and handle data, with clear accountability at each point. IT still runs the technical controls, while the rest of the business takes part in the decisions that create or reduce risk.

No. Anyone can review open-source code, and fixed vulnerabilities are disclosed publicly. With proprietary software, review happens mostly inside the vendor and customers rely on that vendor to disclose problems. A higher count of published vulnerabilities usually means more people are reviewing the code.

Keep a record of every AI tool in use, assign an owner to each, and assess what data it can reach before anyone connects it. Then grant each integration the minimum access it needs through the CMS’s permissions model, and review those connections as regularly as user accounts.

The post Security is a business capability, not a technical function appeared first on Human Made.

7 Steps to Bring AI Tools Under Security Governance on WordPress

30 October 2026 at 12:03

Without governance, unapproved AI tools will creep into your WordPress site over time, often through a series of small and seemingly innocuous decisions. Whether it’s an editor who wants to try a new assistant, or a developer who connects a model to the codebase, it’s natural for your team to want to adopt the tools that make their jobs easier. But it should never come at the cost of your security.

AI governance for WordPress is about giving teams clear rules to follow so they can adopt AI with confidence, and avoid sending sensitive information to unapproved tools. The seven steps below will show you how to find the AI tools already connected to your site and set limits on what each one can access.

What AI Governance for WordPress Means

AI governance for WordPress is about clarifying what AI tools can do and see on your platform covering access, data, review, and accountability.

WordPress now gives you a technical way to set some of those limits. WordPress 6.9 added the Abilities API, a standard way to register the actions a site can perform, each with an optional permission check. The API gives you the control point as your team still has to decide which abilities to expose, and to whom.

Step 1: Inventory Every AI Tool and Connection

Start by listing every AI tool that touches your WordPress environment:

  • Plugins with AI features
  • Browser extensions your editors use
  • API keys and connections to model providers
  • Agent and MCP connections to your site
  • Tools your agency or vendors use on your codebase

Watch out for any uses of shadow AI, where members of your team may have adopted tools without approval or visibility.

The goal here is to have one current register, with a named owner for every tool.

Step 2: Classify Tools by Risk and Data Sensitivity

Not every tool needs the same scrutiny. Sort each one by what data it touches and what it can do:

  • Low risk: suggests edits to public content and can’t change anything on its own.
  • Medium risk: reads unpublished or internal content.
  • High risk: publishes content, changes code or settings, or touches personal data.

The tier will dictate how much review a tool gets. For example, a low-risk writing assistant needs a quick check, but a high-risk agent with write access needs a full security review.

Step 3: Lock Down Access and Credentials

What an AI tool can reach decides how much harm it can do, so access is the first control to tighten.

  • Use least privilege. Scope each connection to specific actions rather than broad admin rights.
  • Treat AI agents as users. Give them their own accounts and roles, so you can trace and revoke their access.
  • Protect credentials. Store API keys in a secrets manager, not in code or plugin settings. Rotate them regularly and whenever staff change.
  • Remove what you don’t use. Delete dormant connections and unused keys.

Step 4: Set Rules for What Data AI Can Use

Decide in advance what information can go to a third-party model. A simple split works well:

  • Usually fine: published, public content.
  • Needs approval: unpublished drafts and internal documents.
  • Restricted: personal data, client confidential material, and anything under regulation.

Check each provider’s terms for whether they train on your data and how long they keep it. Then write the rules in plain language that editors and developers can follow.

Step 5: Keep Humans in the Approval Path

AI can play a part, but sign-off should always come from a human.

Build review into the workflow for anything high-impact:

  • Publishing content
  • Deploying code
  • Changing permissions or settings

Approval only works when the reviewer has the authority and the time to say no. A rubber-stamp step adds risk because it creates false confidence.

Done well, AI still speeds up the work, and a named person signs off on the result.

Step 6: Log and Monitor AI Activity

You can’t govern an AI tool whose activity you can’t trace. Record which tool did what, when, and under which account.

Then watch for unusual patterns:

  • Sudden spikes in requests
  • Activity at odd hours
  • Access to content a tool shouldn’t touch

Add rate limits and cost caps so a misconfigured tool can’t run up a bill or flood your platform. Keep logs long enough to support an investigation. This is the same audit-trail discipline we recommend for agencies, and it applies just as well to your internal tools.

Step 7: Assign Ownership and Review Regularly

Lack of ownership often contributes to governance failure. To avoid this, name an accountable owner, typically a senior leader in digital or security, and give them the authority to approve and retire tools.

Then put the basics in writing:

  • A short AI usage policy that staff can read in minutes
  • An incident plan covering how to revoke access, roll back changes, and notify the right people
  • A review schedule, quarterly at minimum, plus a check after any major tool update or WordPress security release

Frameworks can help you structure this. The NIST AI Risk Management Framework offers a starting point, and OWASP’s guidance on LLM application risks covers the specific threats worth planning for.

AI Governance Checklist at a Glance

StepKey actionTypical owner
1. InventoryList every AI tool, key, and connectionDigital or IT lead
2. ClassifyTier tools by data and capabilitySecurity lead
3. AccessApply least privilege and manage keysEngineering
4. Data rulesDefine what AI can and can’t useSecurity and legal
5. ApprovalRequire human sign-off on high-impact actionsEditorial and engineering
6. MonitorLog activity and alert on anomaliesEngineering and security
7. OwnershipAssign an owner and review regularlySenior leadership

Governance Makes AI Usable at Scale

A one-page register of your AI tools, with an owner against each one, is a useful first step toward seeing your real exposure. Start with Step 1 this week.

Once your register is in place, The Definitive Guide to Enterprise WordPress Security shows how AI governance fits into your wider security picture. Its self-scoring maturity assessment covers governance, access controls and AI readiness, so you can benchmark where your organisation stands and decide what to tackle next.

FAQ: AI Governance for WordPress

It can be, with the right controls. Vet each plugin carefully and limit its access. Risk depends on what the tool can read and change.

Shadow AI refers to any AI tools that staff use without approval or visibility. It’s hard to protect data or enforce rules for tools that you don’t know exist.

One accountable senior owner, usually in digital, IT, or security, supported by input from legal, editorial, and engineering.

Yes, if anyone on your team uses AI on your platform. A short, clear policy sets expectations and gives you something to point to when questions or incidents arise.

Start with an inventory, then apply least-privilege access, separate accounts for agents, and scoped permissions. Remove any connection you can’t justify, and log what remains.

The post 7 Steps to Bring AI Tools Under Security Governance on WordPress appeared first on Human Made.

Open Source vs Proprietary CMS Security: What Enterprise Teams Should Know

30 October 2026 at 12:03

Key takeaway: In the open source vs proprietary CMS security debate, open source holds up well in the enterprise space. WordPress keeps vulnerabilities private until a fix is ready, then delivers it through automatic updates by default. With either model, how your team runs the platform is what matters most.

Enterprise security teams often ask us if open source is safe enough. The short answer? Yes.

Truth be told, we’re a WordPress agency, so we’re not totally neutral but we’ll show you our reasoning so you can understand our take.

Keep reading for a full comparison on open source vs proprietary CMS security covering how each model handles vulnerabilities, and what enterprise teams do to keep either one strong.

Is Open Source Less Secure Than Proprietary Software?

No. Maintenance is the real determining factor in a platform’s security level, including how fast fixes ship and how quickly customers apply them.

With open source, your security team and independent researchers can inspect the code, and a global community of contributors reviews it continuously. That review feeds a structured process for reporting and fixing vulnerabilities, described below.

How WordPress Handles Vulnerability Reports

Researchers report most vulnerabilities privately, through the WordPress Security Team and its HackerOne program. The team verifies each report and triages it in a private workspace, separate from public development tools.

The team ships critical fixes as standalone security releases while lower-severity fixes wait for the next scheduled release.

For serious issues, major hosts and security vendors get advance notice. Protection can be in place before the fix goes public. WordPress 7.0.2, released in July 2026, shows this working. The security team worked with hosts and CDN providers to put mitigation in place across tens of millions of sites before the release went public.

Once a fix ships, the team publishes an advisory that credits the researcher. Serious issues may also receive a CVE, which lets enterprise vulnerability-management tools track them consistently. Sites with automatic background updates, the default for minor and security releases, can receive the fix within hours without anyone taking action. Our post on how a WordPress security release happens walks through each stage.

WordPress is one of the most widely used technologies on the internet, so its vulnerabilities get announced and discussed in public. That can make it appear as though WordPress has more issues than other platforms but that’s really just a side-effect of transparency. A global community of contributors and security researchers reviews the code continuously.

What Vendor-Managed Platforms Do Well

Proprietary CMS vendors offer a single accountable company and a contract that defines responsibilities. Many also manage patching for you, which suits teams with limited security capacity.

The main difference from open source is how much your team can see. With a proprietary platform, you rely on the vendor’s advisories to learn what each fix changed, and you usually can’t inspect the code to check for yourself.

Open Source vs Proprietary CMS Security: Side by Side

FactorOpen source (e.g. WordPress)Proprietary
Code visibilityYour team and independent researchers can inspect itLimited to the vendor and approved parties
Vulnerability handlingPrivate triage, then a public advisory after the fixVaries by vendor
Patch timingFixes ship quickly, and automatic updates can apply themThe vendor sets the schedule
Who applies the fixYour team or agency, or automatic updatesOften the vendor, depending on the contract
Third-party codePlugins and themes need review before launchAdd-ons and integrations need the same review
Independent verificationYour team can test and audit directlyDepends on what the vendor allows
AccountabilityShared between your team and your agency or hostConcentrated with the vendor
Exit optionsYou can change agency or host and keep the platformChanging vendor might mean replacing the platform

Four Ways Enterprise Teams Keep WordPress Protected

Open source gives you control. Enterprise teams use it in four ways.

  1. Test updates in staging before they reach production. Enterprise teams often control automatic updates so that regression testing and change control happen first.
  2. Review plugins and themes before launch, and again at each major update. WordPress plugin security starts with deciding which code you allow.
  3. Give each user and integration the minimum access it needs, and review permissions regularly.
  4. Name an owner for patching and another for incident response.

Our WordPress security page explains more about how we handle security on client platforms.

Questions to Ask Any Vendor or Agency

These questions work for open source and proprietary platforms. For more useful questions to ask when in the prospecting stage of agency selection, check out our article on questions worth asking before choosing a WordPress agency.

  • How do you handle vulnerability reports, from first report to fix?
  • How fast do you patch, and who applies the fix?
  • How do you vet third-party code?
  • What audit trails and monitoring exist?
  • Who owns incident response, and what are the response times?

How AI Is Raising the Value of Fast, Coordinated Patching

AI agents can now exploit known vulnerabilities quickly, so the time between a published fix and a protected site matters more. This is why WordPress keeps unpatched issues in a private workspace and gives hosts advance notice. It’s also why automatic updates narrow the gap.

Teams also need to know how their agency uses AI on their codebase. We cover this in how WordPress agencies use AI and what clients should ask.

Next Steps for Enterprise Security Teams

To conclude, when it comes to open source vs proprietary CMS security, both models can meet enterprise requirements. WordPress adds transparency, a mature disclosure process and exit options. Your choice depends on your team’s capacity to run the platform, or to work with an agency that does.

If you’re weighing up that decision, The Definitive Guide to Enterprise WordPress Security goes deeper into the governance and operational practices that keep a platform secure. Its self-scoring maturity assessment shows where your organisation stands today and where to improve next.

FAQ: Open Source vs Proprietary CMS Security

Yes, when the platform gets patched promptly and governed well. Open source adds public review and a mature disclosure process. Your team still decides how quickly it applies updates and who has access.

Yes. WordPress handles serious vulnerabilities privately and gives major hosts advance notice before a fix goes public. Enterprise teams add staged updates and controlled permissions on top.

Not automatically. They offer a single accountable vendor and often managed patching. You get less visibility into the code and into what each fix changed. Either model can be secure with good maintenance.

Responsibility is shared. The WordPress Security Team handles core vulnerabilities. Your agency or internal team looks after your implementation, and your host looks after the infrastructure. Name an owner for each.

Yes. No single vendor owns the platform, so you can change agency or host and keep it. Proprietary platforms often have several implementation partners too, but changing vendor means replacing the platform.

The post Open Source vs Proprietary CMS Security: What Enterprise Teams Should Know appeared first on Human Made.

WordPress Revisions: Agentic Gold?

By: Noel
23 October 2026 at 10:52

The agentic future keeps inheriting hand-me-downs from the past.

WP-CLI gives agents commands that behave the same way every time, and Query Monitor shows them exactly how a page was built.

Then there are relics only now coming to light, like post revisions. For years they bloated databases with endless copies of every edit, so plenty of sites trimmed them (cheaper hosts often cap them, while enterprise hosts keep everything). But in our opinion, that fluffy extra storage is about to become a lot more valuable.

Every revision records what changed, who changed it, and when. Together they form a log of how your organisation behaves on WordPress, and mining a log like that for patterns is what enterprises call process mining. If you’re lucky, you’ve been keeping yours since revisions arrived in 2008.

Compare each version with the one before and you can see whether edits were content or design, and where your editorial hours really went. There are gaps, because custom fields aren’t revisioned by default and WooCommerce products have no history at all, but it’s a strong starting point.

Whether you know it or not, you’ve been running manual workflows all along. Most are blurry, some are very specific, and a few are experiments.

Those can become agentic workflows, with simple scripts for the repeatable parts and AI judgement for the decisions, all modelled on how your team already works.

We’re testing this at Human Made, and the early results suggest the past and the agentic future are a promising match.

Curious what yours hold? Ask Claude or Codex to run this on a copy of your database (never production):

>_ PROMPT

Using read-only queries and scripts on this database copy, turn my post revisions into agent workflows.

Clean: revisions only, no autosaves, system accounts or no-op saves. Last one to two years, not the build or a migration.

Classify: diff each revision against the previous one and label the change: dates, numbers, links, images, sections added or removed, layout, or copy.

Group: find the same change repeated across many pages (a year rolled forward, a link swapped, a block setting changed). Each is a process, even across weeks and editors.

Deliver the top five: name, share of edits, owner, trigger and cadence, steps in order, source of new values, mechanical versus judgement steps, and a draft workflow.

Close with your blind spots: history depth, and content types with no revisions.

The exciting part isn’t doing the same work faster. It’s moving your team up to higher-value work, and finding the tasks and market edges nobody had time to look for. The old pain points go with it (and yes, we’ll find new ones; we always do). For any large WordPress site, pairing process mining with structured workflows is one of the easiest wins available right now.

How are you solving workflows? If you’d like to try our open-source agentic workflows tool when it’s released, just give us a shout.

The post WordPress Revisions: Agentic Gold? appeared first on Human Made.

How a WordPress full site editing (FSE) theme is built, and why it matters for enterprise sites

20 October 2026 at 09:48

For most of WordPress’s history, a theme was something developers changed and editors worked around. Templates lived in PHP files. As a result, a new layout, a tweak to the header or a different type scale meant a ticket, a branch and a deployment, and the queue for those changes grew with every team that published to the site. A WordPress block theme, the product of the full site editing (FSE) project, changes that arrangement.

Block themes move most of those decisions somewhere both groups can reach. Since the Site Editor arrived in WordPress 5.9 in January 2022, teams can build every part of a site from blocks, including the header, navigation and footer. Developers define colours, typography and spacing once, in a single file, and WordPress applies them everywhere. The development team still decides what is possible, while editors work within those limits without waiting for a release.

For an organisation with several publishing teams, regional sites or a brand team that needs consistency, the bigger change is where the design rules live. Because they sit in the theme rather than in individual pages, a page put together by someone who joined last week follows the same rules as one the designer built.

This guide explains how a block theme is put together, what each part is responsible for, and where projects tend to go wrong. The final section covers how we apply the same approach to enterprise platforms at Human Made.

What a block theme is, and where “FSE” fits

A block theme is a WordPress theme in which every template is made of blocks, the same units editors already use for paragraphs and images. WordPress’s documentation describes it as a theme that uses blocks for all parts of a site, with styles that apply across the whole site.

“Full site editing” was the name of the project that introduced this. WordPress now talks about block themes and the Site Editor, though “FSE theme” still turns up in agency briefs and forum threads. In other words, all three describe the same thing.

The practical difference from a classic theme comes down to who can change what, and how.

Classic themeBlock theme
TemplatesPHP filesHTML files made of blocks
Design settingsThe Customizer and hard-coded CSSOne theme.json file, plus Global Styles in the editor
Header and footerPHP includesTemplate parts, editable in the Site Editor
Who can change a layoutDevelopersDevelopers, and editors within limits the theme sets
MenusThe Menus screenThe Navigation block
Reusable layoutsCustom code or a page builderBlock patterns and synced patterns

Classic themes still work, and WordPress still supports them. Plenty of enterprise sites run on them, so moving to a block theme is a project in its own right rather than a theme swap. The case for moving is strongest when page layouts change often, or when several teams publish to the same platform.

The parts of a block theme, and who owns each one

A block theme needs only two files to run: a stylesheet that identifies the theme, and one template WordPress falls back to for every page. However, a production theme has more, and each part answers a different question about the site.

PartWhat it controlsWho usually changes it
style.cssThe theme’s name, version and minimum WordPress versionDevelopers
theme.jsonColours, type, spacing, layout widths, and which design controls editors seeDevelopers, from the design system
TemplatesThe layout for each kind of page: posts, pages, archives, search results, 404sDevelopers set the defaults; admins can adjust them in the Site Editor
Template partsShared sections such as the header, footer and navigationDevelopers build them once; the content team edits menu links
PatternsReady-made sections editors insert and fill, such as a hero or a feature gridDevelopers build them; editors use them every day
Style variationsAlternative looks for the whole theme, such as a dark mode or a sub-brandDevelopers build them; admins choose between them

In short, the last column shows the point of the whole structure. Decisions that affect every page sit with the people responsible for the platform, and decisions about individual pages sit with the people writing them.

theme.json: where the design decisions live

theme.json holds two kinds of information. Settings define the options editors can choose from: the colour palette, font sizes, spacing values and the widths content can sit at. Styles, on the other hand, define how the site looks before anyone touches it, from the body text colour to the corner radius on every button. The current version of the format, version 3, needs WordPress 6.6 or later.

Each setting becomes a preset, and WordPress turns every preset into a CSS custom property. Templates, patterns and blocks all refer to those presets rather than to fixed values. As a result, changing the primary colour in theme.json changes it in every template, every pattern and every page that uses it, without anyone opening those files.

The same file also limits what editors can do. A theme can switch off custom colours so only the brand palette appears, hide WordPress’s default font sizes, or remove design controls from specific blocks. For a regulated organisation, or one with a strict brand, this is where the organisation enforces governance. A rule set in theme.json applies to every editor on every page, with no reliance on training or memory.

Name presets by their role

How you name presets matters more than it first appears. A palette with colours called Dark Blue and Coral works until the brand changes. At that point, either the names stop matching the colours or someone has to rename every reference across the site.

Instead, name each colour by its role, such as Primary, Secondary, Base and Contrast. A palette like that survives a rebrand, because when the values change, the names still describe what each colour does. The same thinking also applies to type sizes (Small, Medium and Large rather than pixel values) and to font families (Body and Heading rather than the typeface names).

Fonts

theme.json can also register fonts bundled with the theme. Serving fonts from the site’s own domain removes the connection to a third-party font service, which saves a request on every page and keeps visitors’ IP addresses away from that service. For organisations working under GDPR, the second point is often the deciding one.

Templates and template parts: structure shared across the site

Templates set the layout for each kind of page. Block themes follow the same template hierarchy as classic themes, so WordPress looks for the most specific template available (a single post template for a blog post, say) and falls back to the general index template if none exists. Because each template is a file of blocks rather than PHP, admins can also open and adjust it in the Site Editor.

Custom templates also extend this. A theme can offer a full-width landing page or a campaign layout, and editors pick it from the page settings when they create a page.

Template parts hold the sections that templates share: the header, footer, navigation and anything else that repeats. Each one exists only once, so an edit to the footer appears on every template that includes it. On a site with thousands of pages, a change that would once have meant updating hard-coded markup in several files becomes a single edit.

Patterns: the parts editors build pages from

A pattern is a ready-made arrangement of blocks that an editor inserts as one piece and fills with their own content. A hero with a headline, an introduction and a button is a pattern. So is a three-column feature grid, a case study card or a contact section. Patterns live in the theme as files, so they go through version control and deployment with the rest of the code.

In fact, on most enterprise sites, patterns now do the job page builders used to. Developers build every pattern from core WordPress blocks, and theme.json styles it, so it matches the brand wherever it lands and updates when the brand does.

Content-only editing

Developers can also lock a pattern so editors can change its words, images and links but can’t move, delete or restyle the blocks inside it. WordPress calls this content-only editing. As a result, editors see only the places where content goes, which removes the most common way pages drift from the design: someone adjusting a layout to fit a longer headline.

Synced patterns

You edit a synced pattern in one place, and it updates everywhere it appears. It suits anything that must stay identical across the site, for example a breadcrumb bar, a legal disclaimer or a standard call to action. WordPress stores synced patterns as content rather than in the theme, so teams create and manage them in the Site Editor.

How many patterns?

Fewer than most teams expect. After all, each pattern is something editors have to find, understand and choose between, and each one adds markup and CSS the platform has to maintain. A small set, grouped into a handful of families, is quicker to learn, quicker to load and easier to keep consistent than a library of near-duplicates.

Style variations, and what a rebrand looks like

A style variation is an alternative set of theme.json values bundled with the theme, such as a dark mode, a high-contrast version or a sub-brand for one division. Admins switch between them in the Styles panel of the Site Editor.

However, variations only work cleanly when the presets have role-based names. If the default Base colour is white and Contrast is near-black, a dark variation reverses the two values and every template and pattern follows, because none of them refers to a specific colour.

Similarly, a rebrand takes the same route. New colours, typefaces and spacing values go into theme.json, and the site changes with them. Some patterns may still need rework if the new brand changes layouts as well as styles, although most of the visual change happens in one file.

The Site Editor and version control

The Site Editor lets authorised users change templates, template parts and global styles from the WordPress dashboard. WordPress saves those changes to the database, and from then on the database version overrides the theme file for that item.

For a small site run by one person, that is convenient. However, an enterprise platform with a development team, staging environments and a release process runs into a problem: the code in version control no longer matches what visitors see, and changes made in production never reach staging or the other sites on the platform.

Teams usually handle this in one of three ways:

  • Restrict the Site Editor to a small group of admins through user roles, and treat the theme files as the source of truth.
  • Use the Create Block Theme plugin, or a similar export step, to write approved Site Editor changes back into the theme and commit them.
  • Remove template editing for most users on multisite or multi-brand platforms, and route structural changes through the development team.

Whichever approach a team picks, it needs agreeing before launch. Otherwise, untangling drift afterwards means comparing every customised template against its file, one at a time.

Where block theme projects go wrong

Most of the problems we see on block theme projects trace back to decisions made in the first few weeks.

  • Designing pages before parts. When designers treat every page as a one-off, the build ends up with dozens of near-identical patterns, each with its own CSS. Designing the parts first and proving them on a small number of reference pages keeps the set lean.
  • Naming presets after how they look. The cost doesn’t show at launch. Instead, it shows at the first rebrand, when Dark Blue has to become green.
  • Building too many patterns. A library of 80 patterns sounds generous. In practice editors settle on a handful, and the rest go stale without anyone noticing.
  • No agreed rule for the Site Editor. Without one, the database and the code drift apart within weeks of launch.
  • Upgrading theme.json without checking presets. Version 3 changed how WordPress’s default font and spacing sizes interact with a theme’s own presets, so anyone upgrading a theme from version 2 should check it in the editor before release.
  • Bringing editors in at launch. Editors who first meet the system on go-live day build pages around it. By contrast, involving them during the build surfaces the gaps while there is still time to close them.

How Human Made builds block themes for enterprise clients

We build enterprise WordPress platforms on block themes, and the structure described above shapes how a project runs from the first workshop. The aim is a platform the client’s team creates pages with, so a new product, campaign or service doesn’t have to wait for a designer and a developer to catch the site up. We took the same approach for our own website redesign.

Four layers

Our design guide starts from one idea: we are building a system for making web pages. That system has four layers. Human Made designs and builds the first three, while the client’s team works in the fourth.

LayerWhat it holdsWhere it lives in WordPressOwned by
FoundationsType, colour, spacing, borders, shadows and accessibility rulestheme.json and Global StylesHuman Made
BlocksOpeners, text with media, feature grids, quotes and logos, self-filling listings, formsPatterns built from core blocksHuman Made
TemplatesStarting layouts for service pages, hubs, landing pages, articles and archivesTemplates and template partsHuman Made
PagesThe client’s content, with blocks added, swapped or reorderedThe block editorThe client’s team

We design accessibility into the foundations, so every block and template inherits it. Anything the client’s team builds in the fourth layer stays inside the brand and the performance budget, because the three layers beneath it hold.

Design the parts, then prove them

First, we agree the block set and the templates. We then design a set of the client’s pages in full, in situ. On a smaller build that means the home page and the critical pages; on a larger one, every unique layout on the site.

Those designed pages become reference pages. At the design gate, the client signs off three things: the reference pages, a block glossary showing every block in every state, and a page inventory that maps each remaining page to a template and a set of blocks. Build starts once the client approves them.

Build in sprints, with the client publishing from the start

The build runs in two-week sprints. Early sprints deliver the foundations, navigation, footer and core blocks. Later ones deliver the templates and the reference pages. Then, after each sprint review, the client’s page builders create real pages with whatever has shipped.

By the final sprint, the client’s team has already published a large part of the site, and its editors have spent weeks working in the CMS they will run after launch. Meanwhile, anything the kit can’t express comes back to the next review, where we decide together whether to adapt the content, add a block to the set, or build the exception by hand.

What creating a page looks like

Take a new service page, a few sprints into a build. One person on the client’s team has the content in a document and the reference page open in another tab.

First, they create a page from the service template. It opens with a hero, an introduction, a feature strip, a numbered process, a row of project cards, an FAQ and a contact form, already in the brand, with placeholders where the words go. Next, they drop their content in. Two full case studies tell this particular service’s story better than a row of cards, so they swap the project cards for the case study block, which arrives styled and spaced by the same foundations. Finally, they check the page against its reference page and publish. The header, footer and contact form are shared parts, so they were never in question.

The page took one person an afternoon, and no brief.

When it comes to building pages in bulk, sites that make use of a block theme can be rebuilt using scripted migration. WordPress stores blocks as ordinary HTML with a short comment marking each one, so a script can write block markup just as an editor can. It reads each existing page, matches it to a template and set of blocks from the page inventory, and imports the result. A thousand pages can go in a single run, styled by the same foundations and fully editable afterwards.

The scripted route suits pages with a predictable structure, such as articles, product pages and case studies. Pages with one-off layouts usually still need a person, so most migrations script the bulk and leave the exceptions to the content team.

Building on block themes

A block theme puts a site’s design rules in one place and gives editors a defined set of parts to build with. As a result, for organisations whose sites need to change as often as the business does, it shortens the distance between deciding to publish something and publishing it. A rebrand, a new service or a campaign landing page becomes work the content team can do, with the platform keeping it on brand.

If you’re weighing up a move to a block theme, or want to know what one would mean for your platform, tell us about your project.

FAQ: WordPress Block Themes and Full Site Editing

There isn’t one. “Full site editing” was the name of the WordPress project that introduced block themes, and “FSE theme” is the older term. WordPress’s own documentation now uses “block theme”.

The templates need rebuilding, but the content stays where it is, because WordPress stores posts and pages separately from the theme. Some organisations also move in stages: classic themes can use theme.json too, so teams can consolidate design settings first and convert the templates later.

Only as far as the theme allows. theme.json can restrict colours, sizes and design controls, developers can lock patterns to content-only editing, and user roles decide who can open the Site Editor at all.

theme.json is the configuration file at the root of a block theme. It defines the design options available to editors and the default styles for the whole site, and WordPress turns its values into CSS custom properties that every template and pattern uses.

Yes, provided the organisation agrees its governance up front. Style variations handle sub-brands, shared patterns keep sites consistent, and a clear rule for who can change templates stops individual sites drifting from the platform.

As few as the site’s content needs. In practice, developers can build most enterprise sites from a small set grouped into a handful of families. A smaller set is also quicker for editors to learn and cheaper to maintain.

The post How a WordPress full site editing (FSE) theme is built, and why it matters for enterprise sites appeared first on Human Made.

How a WordPress Security Release Happens, From Report to Patch

30 September 2026 at 19:48

Most site owners only see one part of the process that results in a new version of WordPress being released that fixes a security vulnerability: a dashboard notification that reads “An updated version of WordPress is available”. That’s intentional, the software is built to “just work”. Everything before that notification happens behind the scenes, often over days or weeks. The process might start with a report about a weakness from a security researcher, proceed through verification, fixing the bug, testing, and subsequent coordination with some of the world’s largest web hosts and service providers. All activity that stays mostly outside of public view.

The WordPress security release process runs through a consistent set of stages: report, verify, triage, patch, test, coordinate, release, and notify. A critical severity fix may ship within hours, while lower severity issues wait for the next scheduled release, but the release and deployment process handles security issues at the speed that enterprise security teams depend on.

As one of the most widely used technologies on the internet, vulnerabilities in WordPress are announced, scrutinised, and discussed publicly. While this can create the impression that WordPress experiences more security issues than alternative platforms, it also reflects one of the fundamental strengths of open-source software: transparency. Potential issues are exposed to continuous review by a global community of contributors, security researchers, agencies, hosting providers, and enterprise users. With the rise in cybersecurity capabilities of frontier AI agents, this transparency is more important than ever.

Where WordPress Vulnerability Reports Come From

Many security issues in WordPress are responsibly reported to the WordPress Security Team via its well-established vulnerability disclosure program on HackerOne. A mixture of human review and AI augmentation results in each report being prioritised and routed to the appropriate development team accordingly.

Verifying and Triaging the Report

Not every submission of a security vulnerability turns out to be exploitable. Once the team confirms an issue is real, they assess how serious it is. Some issues can wait for the next scheduled release. Others need to move immediately.

That assessment happens inside a private workspace, separate from WordPress’s public development tools. This is because tracking an unpatched vulnerability in the open would hand attackers and their AI agents the same information the security team is racing to fix.

Immediate Release or Scheduled Release? How WordPress Decides

Severity determines the release path. The team pushes a critical issue out as an immediate, standalone security release, skipping the normal cadence. The risk of waiting outweighs the disruption of an out-of-cycle update.

A minor issue waits for the next regularly scheduled release instead, bundled alongside other fixes. That’s a risk-management decision. The team weighs exploitability and real-world impact against the cost of pushing an emergency release across millions of sites.

Coordinated Disclosure With Hosts and Security Vendors

The WordPress open source project has a uniquely close relationship with some of the largest web hosts and platform providers in the world, due to its ubiquity and the many members of the WordPress community who work for those companies. WordPress operates a private discussion forum for some of these companies so they can securely discuss upcoming fixes and plan mitigations in advance.

When a more serious vulnerability occurs, the fix doesn’t move straight from ready to public. Major hosting providers, CDNs, and web application firewall vendors are given advance notice to put protective measures in place prior to a security release being made available publicly.

WordPress 7.0.2, released in July 2026, is an example of this process working as intended. The WordPress security team worked closely with web hosts and CDN providers to put mitigation in place across tens of millions of WordPress websites before the release was made publicly available, due to the severity of the issue that was fixed. With the rise of autonomous AI agents that can quickly exploit known issues, this is more important than ever.

Publishing the Advisory: The Announcement Process

Once a fix ships, the team publishes an advisory on the WordPress.org News site. It details what was fixed and how serious the issues were. A CVE – a standardised public identifier that lets security tools, scanners, and enterprise vulnerability-management systems track the issue consistently – may be published for particularly severe issues.

The advisory will also credit the researcher who reported it. Being publicly credited builds a researcher’s reputation, which incentivises them to report privately rather than go public first.

How the Fix Actually Reaches Your Site

Administrators who haven’t turned on automatic updates will see a dashboard prompt to update manually. They’ll also be given a summary screen that summarises what changed. 

For sites with automatic background updates turned on (the default for minor and security releases) the fix will be completed without any action needed. The administrator simply gets a confirmation email once it’s done. These automated updates allow a large share of the WordPress ecosystem to gain protection within a matter of hours after a fix ships, removing the need for an individual site owner to notice a notification and act on it before an attacker does.

What This Means for Enterprise WordPress Security Teams

For a single site, this automatic process is usually sufficient. However, Enterprise environments tend to need something more substantial. Staging environments, regression testing, and change-control processes have to run before anything touches production. That’s why many enterprise platforms prefer to disable or tightly control automatic updates. 

Enterprise teams need their own patch verification and rollout discipline whenever there is a new WordPress security release. However, the WordPress Security Release process itself is transparent enough about how a fix moves from a researcher’s report to a trusted release, to allow enterprise teams to manage each release with confidence and understanding. 

A reliable patching process is only one part of securing WordPress at enterprise scale. The Definitive Guide to Enterprise WordPress Security covers the governance, operational and AI-readiness questions around it, and includes a self-scoring maturity assessment to show where your organisation stands.

FAQ: WordPress Security Release Process

Mostly through responsible disclosure. Researchers report issues privately, either via WordPress’s HackerOne program or directly to the security team, instead of publishing them immediately.

It depends on severity. The team can patch and release critical issues within days as an immediate security release. Minor issues usually wait for the next regularly scheduled release.

Yes, by default, for minor and security releases. Administrators can disable automatic background updates, and many enterprise environments do this to test changes before deployment.

The team treats critical issues as serious enough to justify an immediate, standalone release outside the normal schedule. Minor issues wait for the next scheduled release alongside other fixes.

The security advisory names the researcher who responsibly disclosed the issue, reinforcing the incentive to report privately rather than publish vulnerabilities publicly.

The post How a WordPress Security Release Happens, From Report to Patch appeared first on Human Made.

Why critical thinking matters in agencies

23 September 2026 at 10:57

Critical thinking in agencies means questioning assumptions. It means weighing evidence. It means reasoning through a decision before committing to it, rather than accepting the first plausible-sounding answer just because it arrived quickly. And it matters more now than it did five years ago. Templates, automation, and AI-generated drafts increasingly shape the daily judgement calls an agency makes. It has never been easier to mistake a fluent answer for a correct one.

This article sets out why critical thinking matters. It covers what the habit looks like in day-to-day agency work, and how teams can build it back in.

This isn’t an argument against automation, templates, or AI tools. All three have a legitimate place in how agencies deliver work efficiently. It’s an argument for keeping a deliberate human check in the loop. The cost of removing that check is higher than it first appears, and it tends to surface much later than the decision that caused it.

When technology promises to think for us

The World Economic Forum’s Future of Jobs research has consistently placed critical thinking near the top of the skills employers expect to matter most. Critical thinking and problem-solving top the list of skills employers believe will grow in prominence. That ranking has held steady since the Forum’s first report in 2016.

This consistency is worth pausing on. It suggests the demand for critical thinking in agencies isn’t a passing trend tied to one technology cycle. It’s a structural response to how quickly information, tools, and expectations change.

Agencies sit in an unusual position here. Clients often pay not just for execution but for judgement, and judgement is precisely what critical thinking protects. A team can defer entirely to whatever a template, a process document, or an AI system produces. But without pausing to check that output actually fits the situation, the agency stops adding the one thing a client can’t easily get elsewhere.

What this looks like in day-to-day agency work

Critical thinking rarely announces itself dramatically. It tends to show up as small, repeatable habits in how a team reaches a decision, not a single heroic moment of insight. In client-facing agency work, it tends to include the following.

  • Asking why before how. Pause before execution to check that the underlying assumption behind a brief, a recommendation, or a plan is actually sound.
  • Separating correlation from causation. Notice when two things happened together without immediately assuming one caused the other, especially when reporting results back to a client.
  • Actively seeking disconfirming evidence. Look for the data point, the client, or the colleague’s opinion that challenges the current plan, rather than only gathering support for a conclusion already reached.
  • Distinguishing a confident answer from a correct one. Fluency and confidence, whether from a person or an AI system, are not the same thing as accuracy.
  • Applying the most scrutiny where a mistake would be most costly. Don’t spread the same shallow level of review evenly across every decision.

None of these habits are dramatic on their own. That’s exactly why they’re the first thing to slip when a team is moving fast.

AI and critical thinking: why the two now depend on each other

People often frame AI and critical thinking as opposites. Using one, the thinking goes, means giving up the other. The more accurate framing is that AI has made critical thinking a precondition for using the technology safely, not a nice-to-have alongside it.

Generative AI systems are remarkably good at producing fluent, confident-sounding output. That fluency is exactly what makes uncritical reliance on them risky. An AI system has no internal sense of when it has got something wrong. Catching that falls entirely to the human reviewing the output. When a team treats AI-generated material as a finished answer rather than a first draft worth interrogating, the habit of critical evaluation weakens from simple lack of use.

We’ve written before about how agencies use AI internally, covering quality, safeguards, and transparency. The underlying argument there is the same one this piece makes: those three things are critical thinking, applied systematically to AI output.

Avoiding cognitive bias in decision making

Avoiding cognitive bias in decision making is one of the more concrete, evidenced reasons critical thinking earns its place in agency work. Cognitive biases such as confirmation bias, anchoring, and overconfidence quietly distort judgement long before anyone notices. They affect experienced decision-makers just as much as inexperienced ones. That’s part of why they’re so persistent.

Research summarised by McKinsey on behavioural strategy found that organisations which actively work to reduce bias in major decisions tend to see meaningfully better outcomes. That work draws on behavioural economics research into the limits of rationality, and how systematically decision-makers deviate from purely rational calculations.

That evidence matters for agencies specifically. Many of the recommendations an agency makes carry real stakes, whether about a platform choice, a migration approach, or a content strategy. An unexamined bias can quietly steer a client toward the wrong outcome.

A few practical steps help counteract this. Assign someone in a review to deliberately challenge the prevailing view. Separate when a team makes a recommendation from when it needs to deliver it. Treat any option that arrived first or loudest with a little more scepticism.

The cost of skipping it

The cost of skipping critical thinking in agencies rarely announces itself at the point a team takes the shortcut. It tends to surface later, once the consequences have compounded into something harder to unpick.

A team mistakes a confident pitch for genuine substance, and a hiring or vendor decision goes ahead on that basis. A plan goes unchallenged in a meeting because no one wants to be the person who slows things down, even when several people privately have doubts. A team ships AI-generated material to a client without checking it against the underlying facts, because it read fluently. The same mistake keeps recurring across projects, simply because no one paused long enough after the first instance to ask why.

Individually, each of these looks like a minor lapse. Collectively, they tend to be the actual root cause behind the moments a team looks back on and asks how they missed something so avoidable.

Building the habit back into how teams operate

Critical thinking skills in the workplace are a practice, not a fixed personality trait. A person or a team can deliberately reintroduce them, even after they’ve slipped. A few concrete habits tend to make the most difference.

  1. Build in a pause before sign-off. Ask a single question, such as what would have to be true for this to be wrong. It costs very little time and catches a surprising number of avoidable errors.
  2. Assign a deliberate challenger. Rotate responsibility for pressure-testing a plan across a team. It normalises disagreement as routine, rather than personal.
  3. Treat AI output as a first draft, not a finished answer. Review AI-generated work the way an experienced editor reviews a junior colleague’s first pass. Keep the habit of scrutiny active, not dormant.
  4. Separate the decision from the deadline. Decouple when a team needs to decide from when the work needs to ship, wherever that’s possible. It reduces how many decisions get made under artificial time pressure.
  5. Keep an honest record of past mistakes. A simple, ongoing log, reviewed periodically rather than filed away, makes the case for slowing down concrete rather than theoretical.

How to evaluate a WordPress agency for critical thinking, not just capability

Anyone working out how to evaluate a WordPress agency tends to focus first on technical capability, delivery process, and security credentials. All three matter a great deal. But critical thinking in agencies is one of the clearest, most practical signals of whether a prospective partner will actually serve an organisation well, rather than simply agreeing with whatever brief lands on their desk.

A partner willing to push back on a flawed requirement is demonstrating exactly this. So is one who asks why before jumping straight to how, or says plainly that a proposed approach isn’t right. These are the habits this piece describes above, under real commercial pressure rather than in the abstract.

We’ve explored this in more depth in what to evaluate when choosing an agency, which sets out the four pillars we think matter most: technical capability, delivery maturity, security and governance, and strategic alignment. Critical thinking runs underneath all four. A partner can score well against every documented pillar and still fail to apply real judgement when a client’s situation doesn’t quite match the template.

Critical thinking in agencies isn’t a soft skill sitting alongside the real work. It’s the difference between a decision that happens to turn out well and one an organisation can actually rely on. The more useful question usually isn’t whether something looks right at first glance. It’s why you believe it actually is.

FAQ: Critical Thinking in Agencies

It’s the discipline of evaluating information, assumptions, and recommendations on their actual merits. It means not accepting them simply because they arrived confidently, quickly, or from an authoritative-sounding source.

Because AI and critical thinking now depend on each other, rather than sitting in opposition. Generative tools can genuinely widen the range of options a person considers. But that only holds if the human reviewing the output keeps questioning it.

Through small, repeatable habits practised consistently. Pause before sign-off. Actively seek out disconfirming evidence. Assign someone to challenge the prevailing plan. Treat both AI output and expert opinion as a starting point, not a settled conclusion.

Cognitive bias describes the specific, largely unconscious distortions, such as confirmation bias or anchoring, that quietly skew judgement. Critical thinking is the broader, deliberate practice that catches and corrects for those distortions.

Look for evidence that the agency questions a brief rather than simply executing it. Look for a team that asks why an approach is right for the specific situation, and one willing to disagree with a client when the evidence points elsewhere.

The post Why critical thinking matters in agencies appeared first on Human Made.

Claude or Codex? WordPress doesn’t care

By: Noel
17 September 2026 at 08:00

I often get asked, "Claude or Codex?"

For larger companies, this decision matters. You’ll go through procurement, approvals, and more. Yet it probably matters less than people think. Each frontier model has its edge, but that edge comes and goes.

After the billions of tokens I’ve run through, here’s my honest take: you’re fine with whatever you have.

Here’s why…

In 2009, a team published results from a surgical safety study across eight hospitals and 7,688 patients. Complications fell from 11% to 7%, deaths from 1.5% to 0.8%, with only one change. The surgeons who left on Friday were the same ones who came back on Monday. A simple checklist made difficult tasks more predictable.

You can always find capability, but reliability is something you build. In agentic work, the equivalent of a checklist is the harness: the engineering around the model that answers four questions. What the agent can see. What it can touch. What it can run. What it has to prove before a change is accepted. The model provides judgement. Everything else, the code, tests, and content, is what you put in place.

The case for a harness has real backing too. A few months back, IBM and Oxford Economics surveyed 2,000 executives across 33 countries. Two thirds of CIOs and CTOs are accountable for AI systems they don’t fully control. Those who built control into the system, rather than simply buying add-ons, ran 25% fewer incidents and deployed 16 times more agents. You’d expect the tightest controls to slow things down. Instead, the opposite happened.

Coming back to my opening question: the model is a commodity. The real moat is the harness.

WordPress is an exceptional harness candidate because it’s structured and documented enough to orchestrate genuinely predictable outcomes. Our open-source package, Block Runner, is one example teams are already using. It takes most inputs (HTML, design files, etc.) and turns them into valid native WordPress blocks, speeding up the design-to-website pipeline.

We tested this by prompting an agent to import designs into valid blocks. With OpenAI’s latest frontier model, Astra, it scored just 26 unassisted. With Luna, a much cheaper model, but with Block Runner attached, it scored 97.

WordPress design import benchmark: Astra scores 26 out of 100; Luna with Block Runner scores 97.

What you can do this week:

  1. Take an AI workflow you run repeatedly, on WordPress or elsewhere.
  2. Put a single check in front of the output. A test, schema, parser, or a human in the loop. Something that can reject the result with a reason.
  3. Run the same workflow on a much cheaper model. If it still holds up, you’re building a harness. Congratulations.

Don’t make the mistake of feeding the model more domain knowledge and hoping predictability follows. Knowledge in a prompt is advice, and the model is free to ignore it. The same knowledge written as a check that can fail the job is a binding contract, which is why a newer model release doesn’t undo the work you’ve put in.

Build the harness for WordPress and beyond, and you’ll get a higher rate of productivity downstream. It’s not something your competitors can just buy off the shelf.

The post Claude or Codex? WordPress doesn’t care appeared first on Human Made.

How WordPress Agencies Use AI — and What Clients Should Ask About It

16 September 2026 at 15:20

Most WordPress agencies now use AI somewhere in their workflow. But the real question isn’t whether an agency uses AI. It’s where, how carefully, and what still requires a human to sign off.

This matters more than it might seem. AI genuinely reduces repetitive work, but it doesn’t replace judgment. The agencies worth hiring can explain that difference clearly. Below, we break down how WordPress agencies use AI in practice, where it doesn’t belong in enterprise delivery, and the questions worth asking any agency about their approach.

Where AI Actually Shows Up in Agency Work

Code generation and scaffolding

AI coding assistants generate boilerplate, scaffold new components, and speed up repetitive implementation work. Agencies increasingly use these tools during development, particularly for well-understood, low-risk code. They don’t use them for the architectural decisions that shape how a platform holds up over time.

QA and testing

Visual regression testing and automated QA checks increasingly rely on AI to flag unexpected changes across a site. This catches issues that would otherwise require a person to manually compare screenshots page by page. It speeds up testing, but a person still has to decide whether a flagged change actually matters. The WordPress core handbook on testing sets out how testing rigor works at the platform level, AI-assisted or not.

Content migration and modeling

Migrating a large, messy legacy site into a clean content model plays to AI’s strengths: repetitive, pattern-matching work at scale. AI tools can map old content types, auto-tag content, and flag inconsistencies far faster than a person working through the same site manually.

Documentation

AI tools can draft technical documentation directly from code, which teams then review and refine. This keeps documentation from falling behind development, a common failure point on long-running platforms.

Research and internal operations

Many agencies use AI for competitive research, accessibility audits, meeting notes, and early drafts of proposals or reports. Clients rarely see any of this, and that’s generally the point. It’s productivity tooling, not a deliverable.

Where AI Doesn’t Belong in Enterprise Delivery

AI struggles with decisions that carry real consequences if they go wrong. Strong agencies draw a clear line here instead of letting AI creep into places it shouldn’t be — a distinction we cover in more depth in our Definitive Guide to Choosing an Enterprise WordPress Agency.

Architecture and technical decisions

Choosing how a platform scales, how integrations connect, or when to take on technical debt requires context AI doesn’t have: the organization’s history, its constraints, its future plans.

Governance and compliance judgment calls

Accessibility, security, and regulatory requirements involve trade-offs specific to an organization’s risk tolerance. That’s a human decision, not something to automate. The W3C’s Web Accessibility Initiative guidelines show the kind of nuanced, context-dependent standard that still needs human interpretation.

Client-facing strategic recommendations

Advice that reflects real judgment about a client’s specific situation should come from someone who understands that situation, not a generated summary.

Agencies that treat AI as a tool for reducing grunt work, rather than a replacement for expertise, tend to be the ones worth trusting with a serious platform. We describe the same pattern in our breakdown of WordPress agency red flags and green flags: confidence and specificity matter more than the tool itself.

Safeguards for Responsible AI Use

Using AI well isn’t just about where an agency applies it. It’s about what surrounds that use. A few safeguards worth looking for:

Human review before anything ships. A person should review AI-generated code, content, or documentation before it reaches production or a client, particularly for anything that touches architecture or security.

Clear data handling policies. Client data shouldn’t go to third-party AI tools without a clear understanding of what happens to it, and under what terms. This matters especially for platforms handling sensitive or regulated content.

Some form of audit trail. When AI plays a role in a decision, someone should be able to trace what it generated, what a person reviewed, and what changed.

Written internal guidelines. Agencies with a genuine AI policy, even a simple one, tend to apply it more consistently than those making it up as they go.

Questions to Ask About AI Use

A short list of questions that tend to reveal how seriously an agency takes this — and a natural extension of the broader questions worth asking before choosing a WordPress agency:

  • Where in your workflow do you currently use AI?
  • What does a person review before it reaches me?
  • Do you ever send my data to a third-party AI tool, and under what terms?
  • What would you never let AI decide on its own?
  • What’s changed about how you work because of AI, and what hasn’t?

Vague or evasive answers here are worth paying attention to. Agencies that have thought this through can usually answer quickly and specifically, because they’ve already had to define the boundaries for themselves.

Why the Best Use of AI Is Invisible

The agencies getting real value from AI tend to describe it in fairly unglamorous terms: less time on repetitive work, more time on the decisions that actually require expertise. That’s a productivity story, not a marketing one.

This lines up with how we think about agency selection more broadly. The details that actually predict a good partnership rarely make for an exciting pitch, a theme we explore further in the total cost of choosing the wrong agency. AI works the same way. If an agency’s AI story sounds more like a sales pitch than a workflow decision, take note.

Choosing an Agency With Your Eyes Open

How WordPress agencies use AI is changing fast, but it hasn’t changed what actually matters in choosing one: judgment, transparency, and a clear sense of where human expertise still needs to lead.

For a broader framework on evaluating agency partners — including questions to ask, red flags to watch for, and a full evaluation scorecard — see our Definitive Guide to Choosing an Enterprise WordPress Agency.

FAQ: How WordPress Agencies Use AI

Ideally, yes. Agencies confident in how they use AI generally have no reason to hide it, and transparency here is a reasonable proxy for how seriously they take the underlying practice.

It depends on where and how they use it. Reviewed, AI-assisted work is generally low-risk. AI making unreviewed decisions about architecture, security, or governance is a different matter, and worth asking about directly.

With AI-assisted work, a person uses AI as a tool within their own process, then reviews and takes responsibility for the result. AI-generated work implies less human involvement, and in an enterprise context, that distinction matters.

This varies. Some agencies treat AI tooling as part of their standard process, similar to any other software they use. Others may factor efficiency gains into pricing. It’s a reasonable question to ask directly during procurement.

The post How WordPress Agencies Use AI — and What Clients Should Ask About It appeared first on Human Made.

How to Evaluate an Enterprise WordPress Agency: The 4 Key Pillars

14 September 2026 at 15:09

Knowing how to evaluate an enterprise WordPress agency comes down to four things that rarely show up clearly in a pitch. Those four things are technical capability, delivery maturity, security and governance, and strategic alignment. A visually impressive site means very little if the platform becomes difficult to scale, maintain, or govern six months after launch. That’s exactly why these four areas matter more than the portfolio ever will.

Why a Pitch Alone Won’t Help You Evaluate an Enterprise WordPress Agency

Most enterprise WordPress agencies look similar on the surface. Polished case studies, recognisable client logos, and a confident timeline tend to appear in almost every proposal you’ll read. However, none of that actually tells you how an agency performs once a project gets hard. Requirements shift, timelines tighten, and the platform eventually has to hold up under real operational pressure. In fact, the cost of getting this decision wrong rarely shows up at launch. It tends to surface months or years later. That’s precisely why learning how to evaluate an enterprise WordPress agency means looking well past the sales process itself.

These four pillars exist to surface exactly that. Each one focuses on a different part of how an agency actually operates once the contract is signed and the real work begins.

Looking for a real deep dive into choosing a WordPress Agency? Check out The Definitive Guide to Choosing a WordPress Agency, complete with evaluation scorecard.

The 4 Pillars to Evaluate an Enterprise WordPress Agency

Below, we break each pillar down into what it actually covers and what you should ask about. That way, you can compare agencies on substance rather than presentation alone.

Pillar 1: Technical Capability

Technical capability describes whether an agency can explain, clearly and without unnecessary jargon, how their platform will hold up under real pressure. Traffic grows, editorial teams expand, and teams add new integrations over time.

Architecture and Scalability

Enterprise platforms need to support growth without becoming fragile. That means handling increasing traffic volumes, new integrations and workflows, regional or multisite expansion, and future migrations without requiring a rebuild each time. A strong architecture creates flexibility without introducing chaos. Look for teams that think in systems rather than individual features, and who can explain performance and long-term maintainability in practical terms instead of jargon.

Engineering Standards

Good engineering practices rarely attract attention when everything works smoothly. Their absence, however, becomes obvious very quickly once something breaks. Ask how the team reviews code, how they test releases before deployment, and what deployment workflows they rely on. Also ask how they manage technical debt as the platform grows and requirements change. Mature engineering teams maintain strong internal processes, clear coding standards, and structured QA. Importantly, they can also explain these practices clearly to non-technical stakeholders, not only to other engineers.

Integrations and Extensibility

Enterprise WordPress platforms sit inside busy digital ecosystems. CRM data, DAM assets, analytics, identity management, and marketing automation all connect in. Each connection adds real value while also introducing another point of dependency. As a result, a capable agency won’t treat integrations as a box-ticking exercise. Instead, they’ll want to understand how data actually moves, who owns it, and what happens when a service fails unexpectedly. Saying “yes, we can integrate that” is easy for almost any agency to claim. Designing an integration that stays maintainable two years later, on the other hand, takes real, hard-won experience.

Hosting and Operational Resilience

Infrastructure decisions shape a platform’s stability long after the initial launch has come and gone. So it’s worth asking how the team structures environments, how they manage releases day to day, and what monitoring and alerting they rely on. It’s also worth asking how they handle incidents and rollbacks when something goes wrong. These details can feel secondary during procurement. In reality, though, they often determine whether a platform stays reliable once it’s under genuine operational pressure. Ultimately, if an agency can only describe what they’ll build, that gap is worth noting. What matters more is whether they can explain how they’ll keep it maintainable two years from now.

Pillar 2: Delivery Maturity

Delivery maturity is about process rather than raw skill alone. Large enterprise projects rarely fail because of one single bad technical decision. Instead, they tend to break down through weak communication, unclear ownership, or planning that was unrealistic from the start.

Discovery and Planning

The quality of discovery usually determines the quality of everything that follows during delivery. Strong agencies spend real time understanding organisational structure, existing workflows, dependencies, and internal constraints before jumping to proposed solutions. They do this by asking difficult questions and identifying risks well before those risks become genuinely expensive. Admittedly, that approach can feel slower at the start of a project. In practice, though, it tends to create faster and cleaner delivery once the real work is underway. Consequently, it’s worth being cautious of agencies that move quickly toward estimates or technical recommendations without first understanding the environment they’re stepping into.

Team Structure and Accountability

One of the simplest and most important questions in enterprise delivery is also one of the most revealing: who actually owns what? Strong agencies define these responsibilities clearly from the start. That covers who leads delivery, who owns technical direction, how they maintain continuity across long projects, and what happens once scope changes partway through. Meanwhile, it’s worth paying close attention to how agencies describe their own teams during these conversations. Mature organisations tend to describe collaborative structures and shared ownership. Less mature ones, by contrast, lean heavily on individual personalities or senior leadership visibility during the sales process itself. That difference tends to become obvious fairly quickly once actual delivery begins.

Documentation, QA, and Release Workflows

It’s worth evaluating how the team tests releases, how they document decisions along the way, and how they structure governance and escalation paths. Experienced agencies introduce enough structure to keep projects moving without creating unnecessary bureaucracy. Instead, they maintain clarity and control while still keeping delivery moving at a reasonable pace.

Long-Term Support

Enterprise platforms don’t simply stop evolving once they launch. Content models expand, integrations change, and teams grow considerably over time. So it’s worth asking directly how post-launch support actually works, what SLAs exist, and how roadmap planning happens. It’s also worth asking whether support tends to be proactive or purely reactive once problems arise. Above all, the strongest agencies design for this reality from the start. They don’t treat it as an afterthought once they’ve already signed the contract.

Pillar 3: Security and Governance

Agencies can’t bolt governance onto a platform after launch. It has to be part of the platform’s design from day one if it’s going to hold up under real inspection. Enterprise platforms operate under constant scrutiny, which means security, accessibility, compliance, and permissions all need genuine consideration well before a release ever reaches production.

Ask the agency directly how they handle security reviews and what actually triggers them. Ask how they manage access and permissions across large editorial teams, and how they test and approve releases before they go live. It’s also worth asking whether compliance requirements shape delivery workflows from the start, rather than only appearing as a check at the very end.

Accessibility deserves particular attention within this pillar. Many agencies still treat accessibility as a late-stage QA task rather than a core part of design and engineering. That approach rarely scales well as a platform grows. Instead, strong partners embed accessibility directly into design systems, structured content models, and testing workflows from the very outset. They treat adherence to standards such as WCAG as an ongoing operational discipline rather than a one-off checklist exercise.

Overall, mature agencies build governance directly into the platform as a structural decision from the start. Less mature ones only address it once they’ve already built the platform and problems start appearing.

Pillar 4: Strategic Alignment

The strongest agency relationships feel genuinely collaborative rather than purely transactional. Good agencies don’t simply execute whatever requirements land on their desk. Instead, they actively help organisations make better decisions. That means challenging unrealistic timelines, identifying hidden risks early, aligning technical decisions with business goals, and helping internal teams work more effectively together over time.

Collaboration style is worth watching closely, particularly under real pressure. Some teams become defensive the moment they’re challenged. Others simply disappear into process instead of engaging directly. Strong partners, however, stay transparent, pragmatic, and solutions-focused throughout. They explain trade-offs clearly, challenge unrealistic assumptions when they see them, and stay honest about complexity and risk rather than avoiding difficult conversations.

A successful launch matters, of course. A platform that continues evolving cleanly years later matters considerably more. That outcome only happens when an agency is genuinely willing to push back, rather than simply agreeing to everything you ask for.

If you’re looking for a WordPress agency currently, we’ve got just the guide for you. Download The Definitive Guide to Choosing an Enterprise WordPress Agency, which comes complete with an evaluation scorecard to help you assess agencies against the criteria we’ve covered in this article.

How These Four Pillars Help You Evaluate an Enterprise WordPress Agency

None of these four pillars function well in isolation from one another. For instance, a technically excellent platform can still fail badly if delivery maturity is weak. Nobody clearly owns the decisions the team makes along the way. Likewise, strong governance means very little if the underlying architecture simply can’t scale to meet real demand. In short, the four pillars reinforce one another. That’s exactly why evaluating just one of them, usually technical capability since it’s the easiest to demo, tends to leave real risk completely unexamined.

PillarWhat good looks likeWhat a vague answer sounds like
Technical capabilityClear trade-offs and plain-language explanations of architecture decisions“We use best practices” with no specifics offered
Delivery maturityA documented discovery process and clear escalation paths“We’re very collaborative” with no real process detail
Security & governanceGovernance built into the design from day oneAccessibility and security framed as a late-stage QA task
Strategic alignmentA willingness to challenge timelines and underlying assumptionsAgreeing to every requirement without any pushback at all

Resources to Help You Evaluate an Enterprise WordPress Agency Further

If you’re actively evaluating agencies right now, a few other resources pair well with everything covered above:

The Bottom Line on How to Evaluate an Enterprise WordPress Agency

A visually impressive site means very little if the platform is hard to scale, govern, or maintain a year from now, regardless of how strong the original pitch was. Ultimately, learning how to evaluate an enterprise WordPress agency means weighing all four pillars together. Don’t rely on whichever single pillar happens to demo the most impressively during procurement.

Frequently Asked Questions

The best approach weighs four areas together rather than any single one in isolation. Technical capability covers whether they can explain architecture decisions clearly. Delivery maturity covers whether they run real discovery and QA processes. Security and governance covers whether they build compliance in from day one. Strategic alignment covers whether they’ll challenge unrealistic timelines rather than simply agreeing to them.

Delivery maturity refers to an agency’s process discipline. That includes how they run discovery, manage stakeholders, document decisions, and handle QA and releases throughout a project. It matters just as much as technical skill, since most enterprise project failures stem from weak process rather than any single bad technical decision.

Ask how they approach architecture and extensibility, and what their deployment and testing workflows actually look like in practice. Also ask how they manage technical debt as a platform grows over time. Strong agencies tend to answer with specifics and clear trade-offs. Weaker ones often speak in generalities or lean heavily on jargon instead.

The post How to Evaluate an Enterprise WordPress Agency: The 4 Key Pillars appeared first on Human Made.

A great pitch isn’t always a great WordPress agency

By: Noel
4 September 2026 at 08:17
Animated agency selection graphic.

Welcome to Word on the Future!

Every enterprise WordPress project starts the same way: a strong pitch, a polished proposal, a shortlist of client logos everyone recognises. It’s what happens after the contract is signed that separates the agencies who deliver from the ones who just present well.

This month, we’re digging into procurement — the questions that actually reveal an agency’s competence, the hidden costs of getting the choice wrong, and a brand new guide to help you evaluate with confidence.

Let’s get into it!

What’s inside this issue 📚

The Definitive Guide to Choosing an Enterprise WordPress Agency.

The Definitive Guide to Choosing an Enterprise WordPress Agency 📖

Most enterprise WordPress agencies look nearly identical on paper. Polished case studies. A tidy service list. A logo wall full of names you recognise.

What’s much harder to fake is a confident, specific answer to an unexpected question — and that’s exactly where this guide comes in.

We’ve pulled together everything we’ve learned from years of enterprise WordPress delivery into one practical framework, covering:

  • Why the real risk in agency selection is invisible at pitch stage, and where to actually look
  • The difference between technical capability, delivery maturity, and genuine long-term fit
  • How to evaluate whether an agency is actually AI-ready, not just AI-aware
  • A ready-to-use evaluation scorecard, so you can score agencies on evidence instead of confidence

Whether you’re running a formal RFP or just trying to sanity-check a shortlist, this guide gives you a structured way to see past the pitch and evaluate what actually matters: whether an agency has lived through the problem you’re hiring them to solve.

Download the guide →

Questions to ask before choosing a WordPress agency.

Questions to Ask When Choosing a WordPress Agency 🔍

A great pitch and a great delivery aren’t the same thing. And the gap between them usually doesn’t show up until you’re months into a project — by which point switching costs time, money, and momentum.

We’ve broken down the exact questions that separate agencies who’ve genuinely solved these problems before from those who are guessing: on technical capability, governance, and long-term support.

Weak answers stay vague. Strong ones come with trade-offs and real examples.

Read the full breakdown →

The true cost of choosing the wrong enterprise WordPress agency.

The True Cost of Choosing the Wrong Enterprise WordPress Agency 💸

The wrong agency rarely looks like a mistake at the time.

It looks like a great pitch — right up until the problems surface, months into delivery.

This piece breaks down what that cost actually looks like: not just the invoice, but the slowed roadmaps, the technical debt, and the operational drag that builds quietly until it can’t be ignored.

Find out what it really costs →

The post A great pitch isn’t always a great WordPress agency appeared first on Human Made.

Questions To Ask When Choosing A WordPress Agency

3 September 2026 at 15:49

Choosing the wrong WordPress agency rarely looks like a mistake at the time. It looks like a great pitch, a polished proposal, and a shortlist of impressive client logos. The problems don’t surface until months into delivery — and by then, switching agencies costs time, money, and momentum.

The right questions can surface most of this risk before you sign anything. Weak agencies tend to answer vaguely or pivot back to generic features and deliverables. Strong ones answer with specifics, trade-offs, and real examples, because they’ve solved these problems before.

Below, we break down the questions to ask when choosing a WordPress agency, organized by what each one actually reveals. If you want the full framework behind these questions, including a ready-to-use scorecard, check out our Definitive Guide to Choosing an Enterprise WordPress Agency.

Why the Right Questions Matter More Than the Right Proposal

Most enterprise WordPress agencies look nearly identical on paper. Anyone can polish a set of case studies, a service list, and a pricing model. What’s much harder to fake is a confident, specific answer to a question the agency didn’t expect.

That’s why we built this list of questions to ask when choosing a WordPress agency around real delivery experience rather than generic hiring advice. Each question tests whether an agency has actually lived through the problem you’re asking about, or whether they’re guessing. For a deeper look at how to weigh the answers, our post on the true cost of choosing the wrong agency explains what happens when organizations skip this step.

Questions About Technical Capability

How do you handle WordPress core and plugin updates at scale?

This question makes a good early test of technical maturity. A vague answer (“we keep things updated”) suggests the agency has no real process. A strong answer covers staging environments, pre-deployment testing, and how updates roll out across multiple sites or environments without breaking production.

What does your deployment workflow actually look like?

Ask the agency to walk you through their workflow step by step. Agencies with mature engineering practices describe this clearly and confidently, from code review through to release. If they struggle to explain it, they probably don’t run a consistent one.

How do you manage accessibility over time, not just at launch?

Many agencies treat accessibility as a late-stage QA checkbox, and that approach tends to break down within months of launch. Strong agencies build accessibility into their design systems and development workflows from day one, and they can describe exactly how they maintain it as the platform evolves.

How do you approach integrations, and what happens when one fails?

Every enterprise platform connects to other systems — CRM, DAM, analytics, marketing automation. Ask how the agency handles failure states, documents dependencies, and keeps integrations maintainable as requirements change. Saying “yes, we can integrate that” is easy. Explaining how they’ll keep it working two years from now takes real experience.

Questions That Reveal WordPress Agency Evaluation Red Flags

How do you approach governance across large editorial teams?

This question separates agencies who’ve genuinely worked at enterprise scale from those who haven’t. Governance at scale means structured permissions, clear escalation paths, and editorial workflows that hold up as teams and content volumes grow. Our breakdown of WordPress agency red flags and green flags covers this pattern in more detail.

What happens when requirements shift significantly mid-project?

Requirements always change. What matters is whether the agency runs a repeatable process for handling it, or treats every change as a renegotiation. Listen for how they discuss trade-offs and re-scoping, not just how accommodating they sound in the room.

Who owns what — delivery, technical direction, and continuity?

Ask directly: who leads delivery, who owns technical decisions, and what happens if a key team member leaves mid-project? Vague answers here often signal unclear accountability once you’re actually working together.

Questions About Long-Term Partnership and Support

How do you reduce technical debt during long-running engagements?

If an agency has never had to answer this question, they’ve probably never run a long engagement. Technical debt accumulates on every platform — the real question is whether the agency actively manages it or lets it compound.

What’s included in the retainer, and how do you manage priorities?

Post-launch support models vary enormously. Some agencies offer proactive, strategic partnerships. Others run reactive ticketing systems that create bottlenecks the moment something urgent comes up. Ask specifically what the retainer covers, how they set priorities, and what SLAs apply.

What operational issues tend to emerge after launch?

This question works as a good gut check. Agencies with real enterprise experience usually answer readily and specifically, because they’ve watched the same patterns repeat across clients. If an agency has nothing to say here, they may not have supported a platform long enough to know.

What a Weak Answer Sounds Like (vs. a Strong One)

Weak answers share a pattern: they stay vague, pivot back to generic features and deliverables, or dodge the specifics of the question entirely.

Strong answers share a different pattern: they include real trade-offs, concrete examples, and an honest acknowledgment of risk. A strong agency won’t shy away from saying “here’s where this gets difficult,” because they’ve already solved that problem before, more than once.

If you take away one thing from this list, take away this: the specificity of the answer usually matters more than the answer itself.

FAQ: Questions to Ask When Choosing a WordPress Agency

What’s the most important question to ask a WordPress agency?
There’s no single most important question, but the strongest signal usually comes from asking what happens after launch — support models, technical debt, and how the agency handles changing requirements. These answers reveal whether an agency thinks long-term or just wants to get you to go-live.

How do I know if a WordPress agency is enterprise-ready?
Look for specific, confident answers about governance, accessibility, integrations, and post-launch support, not just a portfolio of recognizable client logos. Enterprise-ready agencies can explain their processes in detail because they’ve repeated them across multiple large-scale engagements.

What are red flags when hiring a WordPress agency?
Common red flags include agreeing to every requirement without pushback, giving vague or generic answers to technical questions, offering little visibility into QA or release processes, and focusing purely on launch with no discussion of what comes after.

Should I ask these questions during an RFP or in a follow-up conversation?
Ask them in both places, ideally. A whole team can polish a written RFP response. A live conversation, where you can ask follow-up questions and probe deeper, often reveals the real differences between agencies more clearly.

Choosing With Confidence

Asking sharper questions earlier remains one of the simplest ways to avoid an expensive agency mistake later. It costs nothing, and it tends to reveal far more than any proposal will.

For a deeper framework — including a full evaluation scorecard — take a look at our Definitive Guide to Choosing an Enterprise WordPress Agency.

The post Questions To Ask When Choosing A WordPress Agency appeared first on Human Made.

The Total Cost Of Choosing The Wrong Enterprise WordPress Agency

By: Lorna Lim
2 September 2026 at 13:02

The cost of choosing the wrong WordPress agency rarely shows up at launch. It surfaces quietly, months or years later. A platform that once felt like a win starts costing more with every release. The financial cost of a bad agency choice is the easy part to calculate — it’s on the invoice. The total cost of ownership of a WordPress platform is harder to see. It’s the number that actually determines whether your organisation can keep moving at speed – and procurement almost never sees it.

The cost of choosing the wrong WordPress agency rarely lands where you’d expect it to. Here’s where that cost shows up, and why it compounds.

The invoice isn’t where the cost lives

When an enterprise WordPress project goes wrong, the instinct is to look at the budget line. Did it run over? Did the retainer balloon? Did you end up paying for a second agency to fix the first one’s work? Those numbers matter, but they’re not the real damage.

The real damage is behavioural. Once a platform becomes hard to maintain, the organisation adapts around it rather than the other way round. Editorial teams start avoiding certain templates because they’re fragile. Marketing quietly delays campaigns because releases feel risky. Engineers spend their sprints managing regressions instead of building anything new. None of that appears on an invoice. All of it is cost. It’s part of what makes the hidden cost of WordPress migration and development so easy to underestimate at the outset.

Why do Enterprise WordPress projects fail after launch, not at launch?

A rough timeline of where enterprise WordPress project failure actually surfaces:

At launch: Everything looks fine. The site is live, the demo works, the stakeholders are happy. This is the moment procurement teams use to judge success. It’s also the least informative moment in the platform’s lifespan.

Around month six: The first real cracks appear. A content model that didn’t anticipate a new use case. A plugin conflict nobody caught. An integration that sales quietly approved but nobody stress-tested. Small, individually forgivable.

By year two: The cracks have merged into a pattern. Releases take longer than they should. Every new feature request comes with a caveat about what it’ll break. The platform technically works, but nobody trusts it to change gracefully. By now, replacing the agency (or the platform) feels far more disruptive than it would have eighteen months earlier.

That lag is precisely why the cost of choosing the wrong WordPress agency is so easy to underestimate. The bill doesn’t arrive until you’re already locked in. If you’re trying to put a number on how much a failed WordPress project actually costs, look at this delayed timeline. It matters more than the original invoice.

Why “It launched successfully” is a weak signal of vendor selection risk

Enterprise buyers naturally weight the launch heavily when they judge an agency. It’s the most visible milestone in the relationship. It’s also, often, the milestone procurement scores most heavily. That’s part of why RFPs can miss the signals that actually predict long-term WordPress agency vendor selection risk.

But a successful launch tells you almost nothing about whether the agency built the platform to last. Sustainable architecture doesn’t demo well. Governance processes don’t show up in a highlight reel. You see the quality of an agency’s decision-making far more clearly under pressure than on day one. A traffic spike. A mid-project scope change. A new integration nobody planned for. That’s when the platform’s real behaviour shows.

This is also why cost and risk are so tightly linked. The platforms that launch cheapest tend to be the ones where a lot of that pressure-testing simply didn’t happen.

Is the cheapest WordPress agency worth It? The false economy of the lowest bid

Lower-cost proposals are attractive for an obvious reason. Enterprise teams scrutinise budgets, and a smaller number is easier to defend internally. But agencies rarely cut margin evenly across a project. What tends to shrink first is exactly the work that doesn’t show up in a demo. That includes discovery time, QA depth, and documentation. It also includes accessibility work and the architectural thinking that makes a platform easy to extend later. This is the cheap WordPress agency risk in practice — the corners you can’t see get cut first.

None of that absence is visible at handover. It becomes visible the first time the organisation asks the platform to do something the agency never built it for. By then, you’ve usually spent the original saving several times over — in slower releases, firefighting, and remedial work.

This is the core problem with judging an enterprise WordPress agency on launch price alone. You’re pricing the one moment that tells you the least. You’re ignoring the years that will tell you the most. It’s also the honest answer to whether the cheapest WordPress agency is worth it. Rarely — once you account for what happens after launch.

What does total cost of ownership mean for a WordPress platform?

Total cost of ownership for a WordPress platform isn’t just the build fee plus hosting and support retainers. It’s the build cost, plus every hour spent working around fragile templates. Add every delayed campaign, and every remedial project needed to fix architecture that couldn’t scale. Measured this way, the cheapest agency at procurement is frequently the most expensive one three years in.

Judge the decision on its lifespan, not its launch

The organisations that get this right tend to ask a different question during procurement. Instead of asking what this will cost to build, they ask a different question. What will it cost to operate, change, and grow over the next three years? That single reframe changes almost everything about how you evaluate a partner. A platform that’s slightly more expensive to build but genuinely easy to evolve will almost always win out financially. It beats a platform that was cheap to launch and expensive to live with.

A successful launch is a nice moment. It isn’t the test. The real test of whether you chose well is simple. Does the platform still feel adaptable and stable? Is it still worth investing in, two or three years after everyone’s stopped talking about the launch? That’s long after the true cost of choosing the wrong WordPress agency would otherwise have made itself known.

If you’re currently evaluating enterprise WordPress partners, run that three-year lens over every proposal before price becomes the deciding factor. Our Definitive Guide to Choosing an Enterprise WordPress Agency covers the full evaluation process.

The post The Total Cost Of Choosing The Wrong Enterprise WordPress Agency appeared first on Human Made.

AI is changing enterprise WordPress

By: Noel
17 July 2026 at 08:36
word on the future 1

Welcome to Word on the Future!

AI has a habit of making existing problems impossible to ignore.

Platforms that once felt flexible suddenly look rigid. Procurement processes that worked five years ago start asking the wrong questions. Cost models change. Governance changes. Even the definition of what a CMS should do is shifting beneath our feet.

This month, we’re exploring what that means for enterprise WordPress. There’s a brand new playbook, a deep dive into why WordPress is uniquely positioned for the AI era, and a look at the procurement and platform decisions that will matter long after today’s AI headlines have faded.

Let’s go!

What’s inside this issue 📚

The Enterprise WordPress Playbook Featured 1

New guide! The Enterprise WordPress Playbook 📖

Consider this your cheat code for the next CMS strategy meeting.

We’ve distilled years of enterprise WordPress experience into one practical guide, covering the questions organisations are asking right now:

– How do you prepare for AI?

– What actually drives platform costs?

– How do you scale without creating chaos?

– And why are so many enterprises rediscovering WordPress?

Whether you’re choosing a new CMS, untangling a sprawling digital estate, or wondering if your current platform is fit for what’s coming next, this playbook has your back. It’s opinionated, practical, and refreshingly free of vendor fluff.

Download the playbook →

wp hack still 2 corruption

WordPress Security and AI: The Attack Surface Is Expanding 🔐

AI is opening up exciting new possibilities. It’s also creating new ways for things to go wrong.

Every AI integration introduces another connection to manage, another permission to govern, and another potential point of failure. As organisations experiment with AI across publishing, marketing, and operations, the attack surface grows with them.

The good news? This isn’t a WordPress problem. It’s an enterprise reality. The organisations that stay secure won’t be the ones avoiding AI. They’ll be the ones putting the right governance, processes, and architecture in place from day one.

Learn how to build an AI-ready security strategy →

Why Enterprise WordPress Is Built for the AI Era

Why Enterprise WordPress Is Built for the AI Era 🤖

AI has entered the chat.

The question is whether your CMS is ready for it.

The platforms that thrive over the next few years won’t just bolt AI onto existing workflows. They’ll make it easy to integrate new models, automate repetitive tasks, connect with emerging tools, and evolve as the technology inevitably changes.

That’s exactly where WordPress shines. Open, extensible, and backed by a huge ecosystem, it’s uniquely placed to help enterprise teams experiment, adapt, and move at AI speed, without waiting for a vendor’s next roadmap update.

Read the full article →

Enterprise CMS Costs  What Total Cost of Ownership Really Means

Enterprise CMS Costs: What Total Cost of Ownership Really Means 💰

Spoiler alert: your licence fee is only the opening act.

The biggest costs of an enterprise CMS rarely show up on the procurement spreadsheet. They’re hidden in expensive integrations, inflexible architectures, mounting technical debt, and the engineering hours needed just to keep everything ticking over.

Dive in to explore why more organisations are looking beyond the sticker price and evaluating platforms based on their long-term value. Your finance team might even thank you.

Discover what TCO really means. →

Why Enterprise WordPress RFPs often miss what matters 1

Why Enterprise WordPress RFPs Often Miss What Matters 📝

Here’s a controversial take: the longer your RFP, the less likely it is to answer the questions that actually matter.

Feature checklists and lengthy requirements documents can make procurement feel thorough, but they rarely reveal how a platform will perform once it’s supporting multiple teams, markets, integrations, and years of change. That’s where the real challenges begin.

If you’re evaluating enterprise platforms, this is a fresh perspective on the questions worth asking before you sign on the dotted line.

Stop scoring features. Start evaluating platforms. →

Pride at Human Made  what we did and why it matters

Pride at Human Made: What We Did and Why It Matters 🌈

Pride Month may be over, but building an inclusive workplace isn’t something you squeeze into a few weeks each year.

From fundraising and learning sessions to community initiatives led by our brilliant Inclusivity Team, June was a chance to celebrate, reflect, and keep pushing for meaningful progress. It’s a reminder that the best teams are built by creating an environment where everyone can thrive, every day of the year.

A huge thank you to our Senior People Ops Manager Hannah Terrill, our Inclusivity Team, and everyone who helped make this year’s initiatives happen. ❤️

See how we got loud and proud this month →

The post AI is changing enterprise WordPress appeared first on Human Made.

Enterprise WordPress Security Is Really About Decision Making

30 July 2026 at 08:35

Enterprise WordPress security is often discussed in technical terms.

Keep software up to date. Strengthen authentication. Monitor vulnerabilities. Choose secure infrastructure. Follow security best practices.

They’re all sensible recommendations.

The difficulty is that very few enterprise platforms become more or less secure because of a single technical decision. They change gradually as the organisation around them changes.

A new supplier joins a project. Marketing adopts another platform. A regional office needs its own publishing workflow. A business acquisition introduces another website. An AI tool is connected to editorial processes. Someone needs temporary access to production for a launch weekend.

None of these decisions appear particularly significant. They’re simply part of running a large organisation.

Taken together, they shape the security of the platform far more than many people realise.

In practice, enterprise WordPress security is heavily influenced by how organisations make decisions over time.

Enterprise WordPress security involves every team

One of the defining characteristics of enterprise organisations is that nobody sees the whole picture.

Editorial teams see publishing workflows. Developers see code and infrastructure. Marketing sees campaigns and customer journeys. Procurement sees contracts. Security teams see policies and risk. Regional teams see the systems they rely on every day.

Each perspective is valid. Each team is solving genuine business problems.

The challenge is that every decision made within those individual contexts also affects the wider platform.

A new integration might improve a marketing workflow while introducing another dependency that engineering needs to maintain. An AI service might reduce editorial effort while creating a new relationship with organisational data. A supplier might solve an immediate delivery challenge while increasing the number of people with access to production systems.

None of those outcomes necessarily make the platform less secure. They do illustrate why enterprise WordPress security extends well beyond the CMS itself. The platform becomes the point where hundreds of independent decisions intersect.

Enterprise WordPress platforms remember decisions long after projects end

Enterprise platforms have long memories.

Projects finish. Teams change. Agencies move on. Priorities shift. The platform remains.

Several years after launch, it’s common to find systems that nobody uses anymore, integrations whose original owners have left the organisation, or workflows that continue simply because they’ve never been revisited.

Sometimes those decisions still make sense. Sometimes the business has changed so much that nobody remembers why they were made in the first place.

This isn’t unusual. It’s how successful enterprise platforms evolve.

The organisations that manage this complexity well don’t rely on institutional memory. They create processes that make it easier to understand why decisions were made, who owns them today, and when they should be reviewed.

That’s an operational discipline as much as a security one, and it’s an important part of maintaining enterprise WordPress security over the lifetime of a platform.

AI is reshaping enterprise WordPress security

AI is becoming an increasingly important part of enterprise WordPress security discussions.

Teams that might previously have evaluated one or two new technologies each year are now assessing new AI capabilities every month. Editorial teams want content assistants. Developers are experimenting with coding agents. Marketing wants personalisation. Customer service teams are exploring conversational interfaces.

Each opportunity brings another decision.

Which provider should we use? What content should it access? Which teams can use it? How will it integrate with existing systems? Who remains accountable for the output? What happens if the organisation wants to adopt a different model next year?

These questions rarely have purely technical answers.

They require organisations to make consistent decisions across technology, operations, legal, procurement, marketing, and security. The faster AI evolves, the more valuable that consistency becomes.

What does enterprise WordPress security actually involve?

When people think about enterprise WordPress security, they often picture software updates, infrastructure, or vulnerability management.

Those are all essential, but they’re only part of the picture.

A mature approach to enterprise WordPress security also includes:

  • Governance and decision-making
  • Identity and access management
  • Integration and supplier management
  • Operational processes
  • AI governance
  • Change management
  • Clear ownership and accountability

Together, these practices help organisations maintain confidence as platforms evolve, technologies change, and digital estates become more complex.

Governance exists to improve decisions

Governance often sounds administrative.

Policies. Documentation. Approval processes. Standards.

Viewed that way, it’s easy to see governance as something that slows organisations down.

Enterprise organisations experience it differently.

Good governance reduces uncertainty. Teams understand how new technologies are evaluated. Suppliers know what’s expected of them. Decisions follow consistent principles rather than depending on who happens to be involved in a particular project. Similar problems are solved in similar ways, even when different teams are responsible for delivery.

That consistency becomes increasingly valuable as organisations grow because the volume of decisions continues to increase while the number of people making them grows alongside it.

Strong enterprise WordPress security depends on organisations making consistent decisions over many years.

Ultimately, enterprise WordPress security reflects how an organisation operates

Every enterprise platform tells a story about the organisation behind it.

Some platforms reveal years of carefully considered evolution, where new technologies have been introduced deliberately and operational practices have matured alongside the business.

Others reveal the opposite. Different teams have solved similar problems in different ways. Ownership has become unclear. Temporary decisions have quietly become permanent. Complexity has accumulated faster than understanding.

The technology may look similar in both cases.

The difference lies in how decisions have been made.

This is why enterprise WordPress security shouldn’t be viewed solely as a technical capability. It reflects how an organisation introduces change, manages complexity, and creates confidence that today’s decisions will still make sense several years from now.

The post Enterprise WordPress Security Is Really About Decision Making appeared first on Human Made.

WordPress Security and AI: the Attack Surface Is Expanding

By: Jon Ang
14 July 2026 at 13:25

Every month, enterprise organisations connect more AI systems to their digital estate.

For organisations running WordPress at enterprise scale, these new services are changing the security landscape. AI assistants, content generation tools, developer agents, search experiences, and workflow automations increasingly interact with WordPress content, APIs, and business systems. Each new integration creates opportunities for innovation alongside new security considerations that platform and security teams need to understand.

The attack surface is no longer defined solely by websites, applications, or infrastructure. It increasingly includes every AI service that can access, process, or generate information on behalf of the organisation.

This shift is changing the questions enterprises need to ask about WordPress security and AI. As AI becomes more deeply embedded in enterprise publishing, development, and operational workflows, organisations need to understand how these technologies influence security, governance, and risk.

WordPress security and AI start with understanding data access

Every AI tool depends on access to information.

In enterprise WordPress environments, that information often includes editorial content, media libraries, customer data, product information, internal documentation, and the wider business systems connected to the platform. AI tools derive their value by accessing, analysing, or generating content from these sources.

Each connection creates a new relationship between enterprise data and a third-party service.

On its own, an individual integration may present relatively little risk. Over time, however, organisations can accumulate dozens or even hundreds of AI-powered services across different departments, each with its own permissions, governance requirements, and security considerations.

Marketing teams may use AI to generate campaign content. Editorial teams may rely on AI for summarisation or tagging. Developers increasingly use AI assistants to write and review code. Customer service teams are deploying AI-powered support tools, while business teams connect AI to internal knowledge and operational data.

The result is a growing network of systems with access to valuable organisational information.

Understanding how those systems interact with WordPress and the wider digital estate is becoming an increasingly important part of enterprise security.

Visibility is becoming harder to maintain

Many enterprise security programmes were designed around relatively stable technology estates.

Applications were centrally approved. Infrastructure evolved gradually. New software typically followed established procurement and governance processes.

AI adoption often follows a different path.

Teams can begin experimenting with new tools in minutes. Individual departments may adopt different providers to solve similar problems. New capabilities appear faster than many organisations can evaluate them.

Innovation accelerates. Visibility can diminish just as quickly.

For organisations running WordPress, maintaining visibility means understanding where AI is being used, what information those systems can access, and how data moves between WordPress and the wider digital estate. Without that visibility, it becomes increasingly difficult to assess risk, maintain compliance, or respond confidently as the technology landscape evolves.

Data governance is becoming a WordPress security priority

As organisations adopt more AI services, governance becomes increasingly important.

Questions that once focused primarily on infrastructure now extend to AI itself.

  • Which AI tools are approved?
  • What information can employees share with AI systems?
  • Which WordPress content and business systems can AI access?
  • Who is responsible for reviewing new AI services?
  • How are permissions, data flows, and usage monitored over time?

These questions sit at the intersection of technology, governance, and WordPress security.

The organisations making the greatest progress with AI are often those that establish clear policies early, allowing teams to innovate within well-understood boundaries rather than introducing controls after widespread adoption.

WordPress provides the flexibility to adopt AI securely

The AI landscape continues to evolve at extraordinary speed.

New models emerge regularly. Existing providers introduce new capabilities. Organisations are discovering new use cases while reassessing others. Few enterprises expect to be using exactly the same AI technologies five years from now.

This places greater importance on the flexibility of the platforms that sit at the centre of the digital estate.

WordPress is well suited to this environment because it was designed to integrate with other systems. Its mature API ecosystem, open architecture, and flexibility allow organisations to introduce new AI services while maintaining control over infrastructure, governance, and data flows.

That flexibility also supports long-term resilience. Enterprises can evaluate new AI providers, replace existing services, or introduce new capabilities without being constrained by proprietary platform limitations or tightly coupled technology stacks. As AI continues to evolve, retaining that freedom of choice becomes an increasingly important aspect of enterprise WordPress security.

Good WordPress security has always been about governance

Discussions about WordPress security and AI often focus on technology. In practice, successful enterprise programmes are built on governance, operational discipline, visibility, and the ability to adapt as the organisation evolves.

AI reinforces something enterprise security teams have understood for years.

Strong WordPress security is rarely determined by a single technology choice. It emerges from governance, operational discipline, visibility, and the ability to adapt as the organisation evolves.

The introduction of AI doesn’t change these principles. It extends them across a larger and more complex technology landscape.

Organisations that establish clear ownership, understand how information flows between systems, and maintain visibility across their digital estate will be better placed to adopt AI confidently while protecting their platforms, users, and data.

As enterprise AI adoption continues to accelerate, the organisations achieving the strongest security outcomes are unlikely to be those that slow innovation. They will be the ones that build the governance, operational maturity, and platform flexibility needed to evolve securely over time.

The post WordPress Security and AI: the Attack Surface Is Expanding appeared first on Human Made.

Why Enterprise WordPress Is Built for the AI Era

9 July 2026 at 11:49

Artificial intelligence is rapidly becoming part of enterprise operations, and enterprise WordPress is no exception.

Marketing teams are using AI to accelerate content production. Editorial teams are experimenting with summarisation, tagging, and content enrichment. Customer experience teams are exploring personalisation and recommendation engines. Internal teams are using AI to improve search, knowledge management, and workflow automation.

As organisations adopt these technologies, a new question is emerging: does the underlying digital platform support this evolution, or create friction around it?

For enterprise organisations, AI is not simply another technology trend to accommodate. It represents a new layer across the digital estate, touching content, data, workflows, governance, and customer experiences. Platforms that were selected primarily for publishing content are now being asked to support entirely new ways of working.

This shift is bringing renewed attention to the characteristics that make a platform adaptable at enterprise scale.

AI is increasing the value of open architecture

One of the defining characteristics of the current AI landscape is how quickly it changes.

New models emerge regularly. Existing providers introduce new capabilities at a rapid pace. Organisations are experimenting with multiple services simultaneously, often combining proprietary data with different AI platforms depending on the use case.

Few enterprises want to commit their long-term AI strategy to a single vendor.

This is where WordPress’ open architecture becomes particularly valuable.

WordPress was built around extensibility. APIs, plugins, custom development, and integration frameworks allow organisations to connect new services without fundamentally changing the platform itself. AI providers can be introduced, replaced, or expanded as requirements evolve.

This flexibility matters because enterprise AI strategies are still taking shape. The organisations creating the most value from AI are often those that retain the freedom to experiment and adapt as technologies mature.

Enterprise AI depends on integration

The most impactful AI use cases rarely exist in isolation.

A content generation tool is only useful if it fits within editorial workflows. Personalisation systems depend on audience data. AI-powered search relies on access to structured content. Workflow automation requires connections between multiple business systems.

Success depends on integration.

Enterprise WordPress has long operated as part of larger digital ecosystems. It commonly integrates with customer data platforms, analytics services, DAM systems, ecommerce platforms, CRM tools, identity providers, and marketing technology stacks.

That interoperability becomes increasingly important as AI capabilities are introduced across the organisation. Rather than requiring teams to centralise everything within a single vendor ecosystem, WordPress allows AI services to become part of an existing technology landscape.

This supports a more pragmatic approach to adoption, where organisations can introduce AI where it delivers value while maintaining established workflows and governance models.

Content becomes more valuable when it is structured

AI systems depend on content.

They generate it, analyse it, categorise it, enrich it, and use it to power search, recommendations, and automation. The quality of those outputs is heavily influenced by the quality and structure of the underlying content.

This is an area where mature enterprise WordPress implementations have a significant advantage.

Organisations that invest in structured content models, consistent taxonomies, reusable content components, and robust governance frameworks create content assets that are easier for both humans and machines to work with.

As AI adoption grows, content is increasingly becoming an organisational asset rather than simply a publishing output. Structured content can be reused across channels, surfaced through AI-powered experiences, and enriched through automation in ways that are difficult to achieve when content exists in disconnected or poorly governed systems.

For enterprises managing large volumes of content across brands, regions, and channels, these foundations become increasingly important.

Governance becomes more important, not less

The excitement surrounding AI often focuses on speed and automation.

Enterprise adoption introduces a different set of concerns.

Teams need confidence in how AI is being used. They need oversight of content workflows. They need auditability, permissions, approval processes, and clear governance frameworks. Legal, compliance, security, and brand considerations all remain important regardless of how sophisticated AI becomes.

WordPress is already designed around governance at scale.

Role-based permissions, editorial workflows, approval processes, and extensible governance models allow organisations to introduce AI capabilities while maintaining appropriate oversight. AI can become part of existing workflows rather than operating outside them.

This distinction is important because enterprise AI adoption is rarely a technology challenge alone. It is often an organisational challenge that requires balancing innovation with accountability.

A global ecosystem creates resilience

The pace of AI innovation makes ecosystem strength increasingly valuable.

Organisations benefit from access to implementation expertise, proven patterns, emerging integrations, and a community that is actively exploring new possibilities.

WordPress benefits from one of the largest ecosystems in the digital industry. Thousands of organisations, developers, agencies, and technology providers contribute to its evolution. As AI capabilities become more deeply integrated into digital platforms, this ecosystem helps accelerate adoption and reduce risk.

Enterprises are not solving problems in isolation. They are drawing on a large body of shared knowledge and practical experience.

This becomes particularly important when technologies are evolving as quickly as AI.

Why WordPress continues to scale with enterprise ambition

The enterprise conversation around AI often focuses on tools.

The more significant question concerns the foundations those tools depend on.

Organisations need platforms that can integrate new technologies, support evolving workflows, govern increasingly complex operations, and accommodate future requirements that may not yet be fully understood. They need flexibility without sacrificing control, and innovation without creating fragmentation.

These are challenges that enterprise organisations have been addressing for years. AI changes the context, but many of the underlying requirements remain the same.

WordPress continues to scale because its core strengths align closely with those needs. Open architecture, interoperability, extensibility, governance, and ecosystem depth provide enterprises with a platform that can evolve alongside changing technologies rather than being constrained by them.

As AI becomes embedded across the enterprise, those characteristics are becoming increasingly valuable.

Animal, Bee, Insect
Advertisement, Poster, Animal

Download The Enterprise WordPress Playbook to explore how leading organisations are using WordPress to build scalable, adaptable, and future-ready digital platforms.

The post Why Enterprise WordPress Is Built for the AI Era appeared first on Human Made.

❌
❌