WordPress is easy to underestimate.
For many people, it is simply the software behind a blog, company website, online store, or portfolio. But WordPress has been around for more than two decades, survived several major shifts in how the web works, and grown from a small blogging project into the foundation for a huge part of the internet.
Its history also includes some unusual details: jazz-inspired release names, an almost legendary default plugin, an open-source licensing model, and architectural decisions made more than 20 years ago that still influence WordPress today.
Here are some of the most interesting facts about WordPress and why they matter.
1. WordPress Started as a Fork of Another Blogging Platform
WordPress was not created entirely from scratch.
Its origins go back to a blogging platform called b2/cafelog, developed by Michel Valdrighi. When development of b2 slowed down, Matt Mullenweg wrote a blog post in January 2003 suggesting that the project could be forked and continued.
Developer Mike Little responded to the idea.
That collaboration eventually became WordPress.
The first public version, WordPress 0.7, was released on May 27, 2003.
This origin matters because WordPress demonstrates one of the core advantages of open-source software. A project did not have to disappear simply because its original development slowed down. Developers could legally build on it, improve it, and take it in a new direction.
More than two decades later, that fork became one of the most widely used publishing platforms on the internet.
2. The Name “WordPress” Was Suggested by Christine Tremoulet
Matt Mullenweg and Mike Little created the software, but neither of them came up with the name WordPress.
The name was reportedly suggested by Christine Tremoulet, a friend of Matt Mullenweg.
It turned out to be an unusually durable brand name.
“Word” connects naturally with publishing and writing, while “Press” reflects traditional publishing terminology. That combination worked well when WordPress was primarily a blogging platform and continued to make sense as the software evolved into a full content management system.
The capitalization is also intentional:
WordPress
Not WordPress, Word Press, or wordpress.
The capital P has become part of the project’s branding.
3. WordPress Is Older Than Many Platforms We Now Consider Part of the Modern Internet
WordPress launched in 2003.
To put that into perspective:
Facebook launched in 2004.
YouTube launched in 2005.
Twitter, now X, launched in 2006.
The first iPhone arrived in 2007.
Instagram launched in 2010.
TikTok came much later.
WordPress existed before social media became the dominant force it is today and before smartphones became the primary way many people access the internet.
That longevity is significant because web technologies change quickly. Many platforms that were popular in the early 2000s either disappeared or became irrelevant.
WordPress instead kept evolving.
It moved from classic blogging layouts to full websites, custom post types, ecommerce, REST APIs, block-based editing, full-site editing, and increasingly modern development workflows.
4. WordPress Powers More Than 40% of the Web
One of the most remarkable WordPress statistics is its overall market presence.
WordPress is used by more than 40% of websites across the web.
The exact percentage changes over time depending on the measurement source, but WordPress has maintained an unusually large lead among content management systems.
That scale becomes easier to understand when you consider the range of websites that use it.
WordPress can power:
- Personal blogs
- News publications
- Corporate websites
- University websites
- Membership platforms
- Online communities
- Course websites
- Portfolio sites
- Ecommerce stores
- Documentation sites
- Marketing websites
Few software platforms operate across such a broad range of use cases.
WordPress is not dominant because every WordPress website looks or behaves the same. It is dominant partly because developers can make WordPress behave very differently depending on the project.
5. Plugins Changed the Future of WordPress
The WordPress plugin architecture arrived with WordPress 1.2 in 2004.
That was one of the most important technical decisions in WordPress history.
Instead of trying to add every feature directly into WordPress Core, developers could extend WordPress through plugins.
Need SEO features?
Install a plugin.
Need ecommerce?
Install WooCommerce.
Need forms?
There are plugins for that.
Need membership functionality, multilingual content, backups, caching, security, invoices, product recommendations, analytics, LMS functionality, or custom fields?
Plugins can add those capabilities without requiring modifications to WordPress Core.
This architecture helped create an entire commercial ecosystem around WordPress.
Thousands of companies now build businesses around WordPress plugins, themes, hosting, development services, agencies, education, and consulting.
The plugin system did more than make WordPress customizable. It helped create an economy around the platform.
6. Hello Dolly Became the Most Famous Useless Plugin in WordPress
One of the strangest pieces of WordPress history is the Hello Dolly plugin.
It was created by Matt Mullenweg and included with WordPress installations for years.
When activated, Hello Dolly displays random lyrics from Louis Armstrong’s song “Hello, Dolly!” in the WordPress administration interface.
That is essentially all it does.
It does not improve SEO.
It does not make WordPress faster.
It does not add security.
It simply displays lyrics.
Despite its limited practical purpose, Hello Dolly became one of the most recognizable plugins in WordPress history because millions of WordPress users encountered it inside their dashboards.
It also served as a very simple demonstration of how the WordPress plugin system works.
7. WordPress Releases Are Named After Jazz Musicians
Major WordPress releases traditionally receive names honoring jazz musicians.
The tradition reflects Matt Mullenweg’s interest in jazz.
Over the years, WordPress releases have been named after musicians including:
- Miles Davis
- Charles Mingus
- Billy Strayhorn
- Duke Ellington
- Ella Fitzgerald
- Count Basie
- Thelonious Monk
- John Coltrane
- Dinah Washington
- Billie Holiday
- Louis Armstrong
- Mary Lou Williams
For example, WordPress 1.0 was called Davis, after Miles Davis.
WordPress 1.2 was Mingus, after Charles Mingus.
More recent versions have continued the same tradition.
These names are not product editions in the traditional software sense. Users still refer to releases primarily by version number.
But the jazz naming tradition has become part of WordPress culture.
8. WordPress Did Not Originally Have a Modern Theme System
Today, themes are one of the fundamental concepts in WordPress.
That was not always the case.
The proper WordPress theme system arrived with WordPress 1.5 in 2005.
That release introduced much more structured separation between website content and presentation.
This was an important milestone.
A website owner could change the visual presentation of a WordPress site without replacing all of the site’s content.
Themes eventually developed into a massive ecosystem of their own.
For years, traditional WordPress themes relied heavily on PHP template files. More recently, WordPress has moved toward block themes, theme.json, the Site Editor, patterns, and block-based templates.
The technology has changed significantly, but the core idea remains the same: website content and website presentation should be manageable separately.
9. WordPress Is Open Source
WordPress is released under the GNU General Public License, commonly known as the GPL.
That means WordPress is not simply free in the sense of costing zero dollars.
Users have important freedoms around the software.
They can use it.
They can study it.
They can modify it.
They can redistribute it under the terms of the license.
This licensing model has strongly influenced WordPress culture and its ecosystem.
A developer can download WordPress Core, inspect the code, build something on top of it, contribute improvements, or create commercial products that interact with it.
No single vendor controls what you can build with a self-hosted WordPress installation in the way a closed SaaS platform might.
That freedom is one of the reasons WordPress became so widely adopted by developers, agencies, businesses, and hosting companies.
10. WordPress.org and WordPress.com Are Not the Same Thing
This remains one of the most common sources of confusion among new WordPress users.
WordPress.org is associated with the open-source WordPress software and community project.
You can download WordPress, install it on a compatible hosting server, use plugins and themes, and control the website yourself.
WordPress.com is a hosted website platform operated by Automattic.
It uses WordPress technology but provides hosting and services around it.
The distinction matters because discussions about WordPress frequently use the same word to describe two different things.
When developers talk about WordPress Core, plugins, themes, hooks, the plugin repository, or self-hosted WordPress, they are generally talking about the WordPress.org ecosystem.
11. WooCommerce Is Built on Top of WordPress
WordPress was originally created as publishing software.
Today, it is also the foundation of a major ecommerce ecosystem because of WooCommerce.
WooCommerce works as a WordPress plugin.
Once installed, it adds ecommerce concepts such as:
- Products
- Shopping carts
- Checkout
- Orders
- Coupons
- Payment integrations
- Shipping
- Taxes
- Customer accounts
Other plugins can then extend WooCommerce further with subscriptions, recommendations, invoices, bookings, memberships, advanced checkout tools, product bundles, marketing automation, and many other features.
This is an important example of why WordPress’s plugin architecture matters.
WordPress Core itself does not need to become an ecommerce application. A plugin can build an entire commerce platform on top of it.
12. WordPress Has Maintained a Strong Commitment to Backward Compatibility
WordPress developers place significant importance on backward compatibility.
This means older plugins, themes, APIs, and development patterns often continue working across multiple generations of WordPress.
There are limits, of course. Twenty-year-old code cannot be expected to run perfectly forever.
But WordPress generally tries to avoid breaking existing websites unnecessarily.
That philosophy has advantages and disadvantages.
The advantage is stability.
A business may operate a WordPress site for many years while gradually updating WordPress, PHP, themes, and plugins.
The disadvantage is technical complexity.
Maintaining compatibility with old behavior can make it harder to redesign APIs or remove legacy architecture.
This tension between modernization and backward compatibility is one of the central technical challenges WordPress Core developers continuously manage.
13. WordPress Still Contains DNA From Software Built More Than Two Decades Ago
Because WordPress began as a fork of b2/cafelog, some of its history reaches back even further than 2003.
Certain concepts and architectural decisions evolved gradually rather than being redesigned from scratch every few years.
That helps explain some characteristics experienced WordPress developers recognize immediately:
the database structure,
the procedural APIs,
the global functions,
hooks,
filters,
template hierarchy,
and the emphasis on backward compatibility.
Modern WordPress development now includes JavaScript, React-based interfaces, REST APIs, block development, Node tooling, and modern PHP practices.
But underneath those newer layers sits a platform that evolved continuously rather than being repeatedly replaced.
That evolutionary development model is unusual for software operating at WordPress’s scale.
14. The “Five-Minute Install” Became Part of WordPress’s Identity
For years, WordPress promoted its famous five-minute installation.
The concept was simple: installing publishing software should not require advanced server administration skills.
Users typically needed a database, database credentials, a web server, and the WordPress files.
WordPress would handle much of the remaining setup.
Modern managed WordPress hosts have taken this even further. Many now install WordPress automatically with a single click or create it when a new hosting account is provisioned.
But the original five-minute install reflected an important design philosophy.
WordPress wanted publishing on the web to be accessible to people who were not professional developers.
That principle helped the platform spread far beyond the technical community.
15. WordPress Is Developed by a Global Community
WordPress does not operate like a traditional software product built entirely by employees inside one company.
Development involves contributors from around the world.
People contribute to areas such as:
- Core development
- Design
- Accessibility
- Documentation
- Translation
- Testing
- Themes
- Plugins
- Performance
- Security
- Community events
- Training
Companies in the WordPress ecosystem also sponsor contributors to work on the project.
This distributed development model can sometimes make decision-making slower or more complicated than it would be inside a single company.
At the same time, it allows a large group of people and organizations to participate in the future of the platform.
16. WordPress Has Its Own Global Event Ecosystem
WordPress communities organize events known as WordCamps.
These events bring together developers, designers, marketers, agencies, hosting companies, product businesses, freelancers, and users.
Major events such as WordCamp Europe, WordCamp US, and WordCamp Asia can attract participants from around the world.
There are also smaller local WordCamps and WordPress meetups.
These events are important because WordPress is not only software.
It is also an ecosystem of businesses, contributors, communities, and professionals who depend on or contribute to the platform.
17. WordPress Has Changed Its Editor More Dramatically Than Almost Any Other Part of the Platform
For many years, editing WordPress content meant using the classic editor.
That changed with WordPress 5.0 in 2018, when WordPress introduced the block editor, commonly associated with the Gutenberg project.
Instead of treating the page as one large content field, WordPress began treating content as individual blocks.
A paragraph is a block.
An image is a block.
A heading is a block.
A gallery is a block.
Buttons, columns, navigation, templates, and many other interface elements can also function as blocks.
The block system eventually expanded beyond post content into site editing.
WordPress can now use blocks to control areas such as headers, footers, templates, and navigation.
The transition has been controversial at times, but it represents one of the largest architectural changes in WordPress history.
18. WordPress Has Survived Multiple Generations of Web Technology
WordPress has existed through several major web eras.
It survived the transition from desktop-focused websites to responsive design.
It adapted as mobile traffic became dominant.
It remained relevant during the rise of social networks.
It competed with website builders and SaaS publishing platforms.
It incorporated REST APIs as headless architectures became more common.
It moved toward JavaScript-heavy interfaces and block-based editing.
It now exists in an environment increasingly influenced by artificial intelligence and automation.
WordPress has not always adapted quickly, and not every change has been universally accepted.
But its ability to evolve without abandoning millions of existing websites is one of the main reasons it remains relevant after more than 20 years.
Why WordPress Is Still Interesting After More Than Two Decades
The most interesting thing about WordPress is not any single statistic.
It is the fact that a small blogging fork released in 2003 became infrastructure for a significant portion of the web.
Its plugin architecture created an enormous extension ecosystem.
Its GPL license allowed developers and companies to build freely around it.
WooCommerce turned it into an ecommerce platform.
Its theme system made design extensible.
Its contributor model created an international development community.
And its commitment to backward compatibility allowed websites and businesses to remain on the platform through years of technological change.
WordPress has plenty of technical debt, long-running debates, competing priorities, and architectural quirks.
That is partly what makes its history interesting.
It was not designed in 2003 with a 20-year roadmap for powering millions of websites, online stores, membership platforms, publications, and enterprise projects.
It evolved into that role.
And more than two decades after its first public release, that evolution is still continuing.
