fidzu : WordPress

The WordPress Foundation is pleased to announce the return of the Kim Parsell Memorial Scholarship for WordCamp US 2025. Applications are being accepted until July 25, 2025.

Remembering Kim Parsell

Kim Parsell was a dedicated contributor and a beloved member of the WordPress community. Her passion for open source and her welcoming spirit inspired many, both online and in person. Each year at WordCamp US, the WordPress Foundation celebrates Kim's legacy by supporting contributors who share her commitment and enthusiasm. The Kim Parsell Memorial Scholarship aims to make it easier for deserving community members to attend WordCamp US, reflecting Kim's belief in making WordPress accessible and inclusive for all.

If you're unfamiliar with Kim's story or her invaluable role in the community, we encourage you to read these heartfelt tributes collected from friends and colleagues.

Scholarship Eligibility

This year, a single scholarship will be awarded. To qualify, applicants must:

• Identify as a woman
• Be actively involved as a contributor to WordPress
• Have never attended WordCamp US before
• Demonstrate a need for financial support to attend the event

If you meet these qualifications, we invite you to apply before the July 25 deadline. All applicants will be notified of the decision by August 7, 2025.

For additional information, visit the Kim Parsell Memorial Scholarship page hosted by the WordPress Foundation.

Join the Celebration

• Tickets for WordCamp US 2025 are now available-secure yours soon!
• Volunteer applications are open until July 11, 2025
• Interested in supporting the event? Explore our sponsorship opportunities

Help us spread the word about this opportunity and make WordCamp US 2025 even more special.

14 Jul 2025 6:57pm GMT

In the evolving digital commerce landscape, successful funding requires strong founder-investor relationships, clear problem-solving focus, and ethical considerations, emphasizing collaborative growth and effective product strategies.

14 Jul 2025 9:38am GMT

You know that moment when you breeze into a new app by clicking "Sign in with Google"? That's not magic. It's federated identity management (FIM).

It lets you hop between apps and services using just one login, no password juggling required.

You've likely got usernames and passwords scattered across what feels like half the internet. It's a mess for users, and an even bigger migraine for developers trying to build secure login systems from scratch.

FIM solves this core problem of digital identity management by creating trusted links between different platforms. So instead of managing dozens of accounts, you just maintain one primary identity that does the heavy lifting across multiple services.

In this article, we'll unpack:

• How identity providers and service providers team up to make login friction-free.
• The protocols behind the magic - SAML, OAuth, OpenID Connect.
• Why FIM systems are more secure and more user-friendly than the old-school alternatives.
• How tools like Gravatar bring federated identity to the everyday user, not just the enterprise crowd.

So, let's dig into how federated identity is rewriting the rules of online access.

What is federated identity management?

Federated identity management lets users log into multiple services with just one set of credentials - even if those services belong to entirely different organizations or live in separate security realms.

In short: One login, many doors.

The clever part? While users enjoy the simplicity of a single sign-in, each organization still keeps tight control over its own systems and data. Everyone wins - convenience for users, boundaries for businesses.

At its heart, FIM solves a very modern dilemma: Too many passwords, not enough patience. By reducing login clutter whilst safeguarding security, it keeps systems streamlined and users sane.

For example:

• A university student signs into their campus portal with their regular uni login.
• From there, they can hop into a Google Workspace to submit assignments, dive into academic databases, or access publishing platforms with no additional accounts.
• Their university identity just… goes with them.

This all works thanks to behind-the-scenes handshake deals called federated identity agreements. The university acts as the identity provider, backing the student's identity. Services like Google Workspace act as service providers, trusting that endorsement and granting access accordingly.

It all works through carefully coordinated authentication protocols working behind the scenes. These standards let systems talk to each other securely. Only the essentials get shared, passwords never stray from their home base, and users keep control of their data.

Now, let's dig into how those protocols do their thing.

Key protocols and standards: SAML, OAuth, and OpenID Connect

Federated identity might sound like something dreamt up in a sci-fi novel, but it's really just about helping different services trust each other enough to vouch for you.

That way, you're not logging in twelve times before breakfast. Instead, a handful of protocols quietly do the work to keep things smooth, secure, and repeat-login free.

Here are the big three making that happen:

SAML (Security Assertion Markup Language)

SAML is basically the corporate go-to when it comes to easy sign-ins. It's what lets employees hop between internal tools (HR systems, dashboards, intranets etc.) without juggling five passwords and a daily identity crisis.

Here's the gist:

• You try to access a service (say, the company HR portal).
• You're bounced over to the company's identity provider.
• You log in with your usual details.
• The service gets a SAML assertion - a signed digital nod that says, "Yep, this person checks out".

It's especially handy in enterprise and B2B settings, where you need airtight security and rich user data. If you're into technical deep dives, the OASIS SAML Technical Committee has the specs.

OAuth 2.0

OAuth isn't really about proving who you are; it's about saying what an app can do on your behalf.

That moment when you "Sign in with Google", OAuth is just passing a temporary access token that tells the app, "This person's cool with you looking at their calendar (but hands off their emails)." It's identity permission management, not identity confirmation.

It's like handing out a key that only opens one room in the house, and only for a short time. You can learn more about it on the OAuth 2.0 site.

OpenID Connect

OpenID Connect builds on OAuth 2.0 by enabling proper ID verification. It's what makes one-click logins like "Sign in with Apple" or "Sign in with Google" actually log you in, not just hand out permissions.

It works by adding an identity token that securely shares who you are with the service. So now, it's not just "this person said yes," it's "this person is Alice, email verified, and here's the proof."

Want to build with it? The OpenID Connect specs are the go-to guide for implementation.

Identity providers vs. service providers: Roles in the FIM ecosystem

In federated identity management (FIM), two main players run the show: The identity provider (IdP) and the service provider (SP). Knowing what each does is key to understanding how FIM works.

Identity providers handle the login. They verify who you are; whether that's Google, Microsoft, your university, or your company's system. The IdP stores your credentials and confirms your identity to other services.

Service providers are the apps and platforms you want to access using that login, like Zoom, Dropbox, or academic databases.

Here's what happens when you click "Sign in with Google":

• Google (the IdP) checks your credentials.
• It tells the service provider you're authenticated.
• The service provider grants access without ever seeing your password.

This split keeps things secure. Your passwords stay with trusted IdPs, so you're not juggling new logins for every service. And if a service provider is breached, your credentials are still safe.

For organizations, it simplifies access control. IT teams can grant or revoke access from the IdP side, managing all connected services in one go when people join or leave.

FIM vs. single sign-on: Key differences explained

Single sign-on (SSO) is the big crowd-pleaser: One login, and you're in. Email, HR tools, task boards, wiki rabbit holes - it's all yours, no repeated password dance required.

The catch is it all lives within the borders of your organization. Handy, yes. But fenced in.

Federated identity management (FIM) takes things a step further. Same single login magic, but this time the credentials can travel. Across platforms. Across orgs. Across ecosystems. It's SSO with a passport.

Here's how that plays out:

• With SSO, a university student signs in once and gets access to campus email, class materials, and the meal plan portal.
  
• With FIM, that same login gets them into external research libraries, academic collaboration tools, and third-party cloud drives, all run by different providers.

Both SSO and FIM save you from juggling five logins and twenty browser tabs. Both boost security by keeping authentication centralised. The difference? FIM doesn't stop at the edge of your organization, it builds trust between systems that aren't under the same roof.

To make this work, FIM needs a little extra backend choreography. To work smoothly across domains, it relies on protocols like SAML, OAuth, or OpenID Connect (the same ones we unpacked earlier).

SSO inside a single org skips the extra tech since everything's already playing on the same team.

So: SSO keeps things simple within your four walls. FIM gets you past the gates.

Gravatar's profiles-as-a-service: A simplified approach to federated identity

Gravatar makes federated identity feel less like an enterprise buzzword and more like something regular people can actually use. It takes the big, often baffling ideas behind FIM and packages them into something simple, familiar, and weirdly elegant.

Let's start with the magic trick: Update once, sync everywhere.

Change your photo or bio on Gravatar and - ta-da - it updates across every platform that supports it, from WordPress comment sections to your GitHub commits. No faff. No repeat uploads. Just instant consistency, quietly flexing the whole "federated identity" concept in real life.

What really makes it click, though, is how Gravatar ties your identity to your email address instead of your name. That lets you switch gears effortlessly:

• One email for your work persona.
• Another for hobby projects.
• A third for your incognito forum life.

Each one becomes its own lightweight identity provider. And because Gravatar plays nicely with WordPress, GitHub, Slack, OpenAI (and plenty more), your profile travels with you like a loyal companion.

Gravatar skips the corporate complexity in favor of something far more accessible, especially for solo operators and smaller teams.

Best of all? It's free. And since it's backed by Automattic, Gravatar takes ideas that used to live inside enterprise IT departments and hands them over to the rest of us.

How developers can leverage Gravatar's API for cross-domain identity

If you're a developer staring down the barrel of yet another user profile system, take a breath. Gravatar's got your back. Our API is basically a plug-and-play shortcut to "profiles-as-a-service," and integrating it is almost suspiciously easy.

Instead of wrestling with databases, uploads, and custom logic, you can hook into Gravatar's infrastructure with just a few lines of code. Here's what you get:

• Avatars in all the sizes you'll need.
• Verified social links.
• User bios and display names.
• Professional details, neatly packaged.

It's a clean fix for the mess of cross-domain identity. One Gravatar profile works across every platform that supports the API. No more begging users to upload the same photo (again). No more duplicated effort.

And here's what makes things even better: the docs are actually helpful. Whether you're calling our REST API or grabbing an SDK, our Gravatar tutorials walk you through everything from basic avatar fetching to pulling in full profiles.

Building your own profile system could eat up weeks or months. With Gravatar, you'll be done before your coffee goes cold. Plus, you skip the long-term headaches: Maintenance, security patches, user complaints - all gone.

If you're working on a comment thread, a full-blown app, or anything in between, Gravatar delivers a clean, federated identity solution minus the enterprise bloat.

Create your digital passport today

Gravatar makes federated identity simple and available to everyone, whether you're a solo creator or a full-stack developer.

One profile, thousands of platforms: WordPress, GitHub, Slack, OpenAI… all covered.

You simply update your profile once, and it syncs everywhere. No more hunting down forgotten logins just to swap out a profile pic or tweak a bio.

For developers, it's a breeze: Just a few lines of code, and your users get a polished, cross-platform experience without the headache of building your own identity infrastructure.

Gravatar's been trusted by millions for over a decade, and it's backed by Automattic, the same folks behind WordPress.com and a whole suite of web heavyweights.

It's free, privacy-conscious, and puts you firmly in control.

Ready to streamline your online presence? Set up your free Gravatar and make profile chaos a thing of the past.

11 Jul 2025 6:30pm GMT

I'm so glad Tammie was (partially) inspired to reflect on the beginning of her contribution journey after reading my 12 year first contribution anniversary post. I love reading these stories! They really ignite a meditative mindset.

I'm currently up in the White Mountains on a family vacation. I read her post with my morning coffee before my wife and I set out to hike Mount Willard as part of our attempt to tackle the 52 With A View. I know, I should be better about disconnecting, but her reflections had me thinking on the trail.

Everyone is just "figuring it out" (whatever that means)

It's interesting how the contributors you looked up to when getting started that you assumed were well established were actually still finding their way.

Tammie is a great example of this. I remember looking at comments she made and thinking they were insightful and based on lots of experience. They were and still are, but her experience was not what I had assumed. Her experience at the time was just not yet from contributing to WordPress. She too was wandering around looking for the path that looked just right at the same time as me.

"Figuring it out" also means something different to everyone. And "it" can also change over time. The best path today will likely not be a good fit in 10 years, 5 years, or even 6 months.

Activating Observers

"A simple code review or "great job" can be the difference between a one-time contributor and a future maintainer. You never know what someone needs to hear, so be generous with feedback."

This is something I included in my essay for the Maintaine.rs book. In Tammie's post, she interestingly had a sentence that struck me as the exact opposite of that statement.

"Our projects are full of the ghosts of contributors we never activated, and that fuels me to see potential in every person who gives up their time."

What happens when we don't put our best forward, if it wasn't enough, or wasn't what someone needed to hear? Obviously we can't (and shouldn't) attract or keep everyone who passes by the communities we care for to join in our efforts. But what about those who were good fits but just weren't engaged with in the right way?

Maybe documentation was lacking. Maybe expectations were unclear. Or maybe they sensed a maintainer was being territorial towards an area of the project they look after. This excerpt from Producing Open Source Software is relevant here:

Watch out for participants who try to stake out exclusive ownership of certain areas of the project, and who seem to want to do all the work in those areas, to the extent of aggressively taking over work that others start. Such behavior may even seem healthy at first. After all, on the surface it looks like the person is taking on more responsibility, and showing increased activity within a given area. But in the long run, it is destructive. When people sense a "no trespassing" sign, they stay away. This results in reduced review in that area, and greater fragility, because the lone developer becomes a single point of failure. Worse, it fractures the cooperative, egalitarian spirit of the project.

Karl Fogel. Producing Open Source Software. Chapter 8: Preventing Territoriality

Sometimes letting people find their way means not engaging at all. Not every contributor requires an eager welcome or hand-holding. Over-engaging can also be a bad thing. Knowing how to gauge the appropriate level of interaction is a skill that comes with time.

Different Paths For Different People

On our hike, I noticed that the route my wife took was almost never the same as the one I took on the same exact path. I wasn't intentionally avoiding her footprints, I was just subconsciously choosing what looked best to me.

The same is true in a large community. Instead of rigid groupings with strict criteria that must be met, establish decision-making frameworks that encourage flexibility guided in foundational principles.

I sometimes observe new contributors trying to make sense of activity by forcing everything into specific categories, paths, or types. While it makes a lot of sense as a first step, that can quickly lead to frustration and burn out because it just doesn't work like that at scale.

Paths also manifest to individuals differently. Sometimes they're rocky and sometimes not. Sometimes it's rocky but one giant smooth rock instead of many little ones, and occasionally the surface is just a little slippery. Everyone proceeds at their own pace. If you believe in the mission and have purpose, continue on despite the form the path takes in front of you.

Avoid Congregating At The Top

Two Summers ago while also in New Hampshire, we took the Mount Washington Auto Road to the top of the 6,288 foot highest point in New England. When we reached the summit, the weather was drastically different (30-40MPH gusts, cloudy, and 35°F) than at the base (high 80°s F, calm, clear and sunny).

Besides the weather, something else stood out. There was a line ~100 people long waiting for a chance to take a photo in front of the summit sign.

When everyone crowds toward the "top," we risk losing the balance and continuity that healthy communities need. It's not about reaching the summit. Rather, it's about ensuring the entire path is well-traveled, well-marked, and connected.

Don't Meet At The Top

We never truly make it to the "top" because it's not a static thing. This is especially true in technology where everything is constantly changing and evolving. Thus, "getting to the top" is the wrong goal. Instead, our goal should be to connect with as many people as we can at the many points paths intersect along the way. Put differently, we should be building connections between as many paths as possible.

Those Who Predate Us

There was a very old stone wall covered in moss on the hike and I found myself thinking: how many others had used the same path before me? How many people lived on this mountain before the trail existed? There's no true way to know, especially if everyone is respecting the carry in, carry out mindset. Instead, the signs will be very subtle and require an astute eye.

Footprints, paths worn down from traffic, and in more obvious cases, others actually passing you on your way. While each path is unique, where your path takes you is rarely untraveled. Learn to spot the differences and adjust accordingly.

Many Small Trickles Fill A Basin

When you drink from the fire hose of a large Open Source project like WordPress, it's easy to lose sight of the cumulative efforts that are required to create such a strong and steady flow. But like basins and streams, it takes many small trickles to fill them.

Our work isn't measured only by the splash of large contributions, but by the steady trickle of small acts that feed a thriving ecosystem. If we want future contributors to drink from the same basin, we need to show them how every small drop matters.

Judging Effectiveness By Noise

As we got close to the end of the hike, we started hearing cars on the highway again. The trail we took was an out and back loop. In this situation, it meant we were in the right place. But when we started the hike, the opposite was true.

When participating in a community, the level of "noise" can be used to gauge whether your work is on target.

When beginning to work on a foundational task that only a few people can advise on, that often means you're in the right space. But once you've shared that idea with the wider community, silence could mean you've missed the mark.

Still, silence isn't always failure. Sometimes it's just the sound of others listening, considering, and preparing to walk their own part of the trail that you've created.

Featured image credit: CC0 licensed photo by soycelycruz from the WordPress Photo Directory.

The post The Ghosts of Unactivated Contributors appeared first on Jonathan Desrosiers.

11 Jul 2025 1:55am GMT

The WordPress Foundation is proud to launch WordPress Credits, a contribution-focused internship program that brings university students into the heart of the WordPress open source project. While WordPress thrives on contributions from a global volunteer community, many students and newcomers face barriers to entry, such as a lack of structured guidance or real-world experience in open source projects. This new program is designed to bridge that gap, nurturing future contributors and ensuring WordPress remains innovative, inclusive, and sustainable for years to come.

The pilot program, developed in partnership with the University of Pisa, was announced on stage at WordCamp Europe 2025 by Matt Mullenweg and Mary Hubbard. Since then, it has attracted interest from students across various fields of study, including humanities, computer science, and communication. Companies in the WordPress ecosystem have also expressed support and interest in contributing to the project. In response to the growing interest from both community members and academic institutions, we are now inviting more universities to join the initiative.

Open to students from all fields of study, the program blends structured onboarding with a personalized contribution project. Activities are adapted to each student's degree program and familiarity with WordPress, aiming to develop transferable skills, academic-related competencies, and active participation in the WordPress community. Internship durations may vary depending on the university or educational institution. Some may align with academic semesters (typically 3-4 months), while others, like the University of Pisa, allow students to sign up year-round with a requirement to complete a set number of contribution hours (e.g. 150 hours). Flexible arrangements can be discussed to meet the specific requirements of each institution.

Foundational Training includes:

• An introduction to open source principles and the WordPress Foundation
• Getting familiar with community tools (Slack, Make blogs, Learn platform, GitHub)
• Setting up a personal WordPress site and publishing content

Each student will choose a contribution area and design their own personal project within that area. Examples of possible projects include:

• Translating interfaces or documentation
• Creating multilingual subtitles for educational videos
• Contributing code or performing testing
• Supporting product development or design
• Writing or editing content
• Assisting with community event organization
• Developing training materials for Learn WordPress
• Creating open source tools
• And much more…
  

Interns are guided by an experienced mentor specific to their chosen area and supported by a dedicated WordPress Foundation contact person throughout the program. All student contributions, whether code, translations, documentation, or educational materials, will be publicly visible and integrated into official WordPress projects and resources, directly benefiting the wider community.

Interested universities and educational institutions interested in participating can reach out by filling the interest form.

We also invite companies in the WordPress ecosystem to support this initiative by sponsoring mentors who will guide and empower the next generation of contributors, or by providing tools and resources that help students succeed in their contribution journey.

If your company is interested in getting involved, please visit the Company Guide to learn more and fill out the form to join the program.

By welcoming students, mentors, sponsors, and volunteers into this initiative, we are building a stronger and more connected WordPress community. Each person who takes part, whether they guide a student, share their experiences, provide sponsorship, or simply help spread the word, helps ensure that open source remains vibrant and accessible for all. Together, we are not just supporting individual contributors; we are shaping the future of WordPress and open source itself.

10 Jul 2025 4:56pm GMT

In this episode of Dev Pulse, hosts chat with Jason Cosper about the challenges and humor in infrastructure, consulting rates, communication, and the evolving role of AI in tech work and workflows.

10 Jul 2025 10:54am GMT

This post was inspired by the awesome posts from Jonathan Desrosiers and Felix Arntz, who celebrated their contribution anniversaries with reflection. It made me muse on how critical those first points, the initial steps in a contribution journey, are. I began reflecting on my own 'firsts' and the people who helped me achieve them.

Reflecting

I am never one to celebrate anniversaries in general, and as a result, I admit I let my slide, both personally and professionally. That isn't a pattern I suggest anyone should follow, though; it's essential to acknowledge where you have been and who helped you get there.

In open source, those who have been involved in the project for a longer time may have always known what they are doing. This is far from the truth. Those who enabled my first props also had their own. Often, though, the first prop isn't the first entrance into the project. It can be an incredible moment that empowers someone, though, by recognising their work. Often, props can come after a few stages in a contribution journey, and we might forget that. That path was one I followed, taking time to explore adjacent spaces before even finding my way around the space.

My first props

I admit I don't recall ever looking up my first props before and I found mine this time but it took a bit. It was a nice moment that aligned with my contribution story to see my props split across core and BuddyPress. It also reflected how I took time before props to get settled in.

My first appearance in this space was in core, and then I rapidly ended up in adjacent areas, such as the theme review team and BuddyPress. On reflection, this could have been a different story. It could have been one of the contributor who pivoted out, never finding their space. So, I am grateful for finding a space and to those contributors who caught me.

My first BuddyPress props was by Paul Gibbs, and it was on 11/12/2010. My first core props came a few years later, and it was by Helen Hou-Sandi on 03/01/2013. By each of these props, I was already settled into those spaces as a contributor. Props might come later because you're working on other things or the role you're contributing.

A welcome

I had the pleasure of being asked to share my thoughts on contributing to maintaine.rs, along with other open source contributors, including the ever-awesome Jonathan Desrosiers. This is an incredible project telling stories across open source, and I encourage checking it out. In it, I was asked about welcoming contributors and how to see value.

If you want contributions, be sure to show how and where they are wanted. It's one thing to say 'all contributions are welcome', but that's open-source theatre because honestly, it's likely not all are in every area as welcome as others. There are always more areas needed than some. Highlight these and make sure someone gets off to a contribution success from the start.

My journey could have been very different if I hadn't found a place to contribute. Empowered by those people, I was led to the props and supported in my first tickets. Our projects are full of the ghosts of contributors we never activated, and that fuels me to see potential in every person who gives up their time.

When I arrived at the project, I wasn't sponsored; I was giving my own time because this project was providing me with a blog and client work. My journey in open source began before WordPress, starting with Linux. When I joined the project, I already understood the concept of contribution and came to it with that in mind, looking to find a way to balance what I was gaining.

I wasn't aware of all the options to contribute to the project; there were fewer than there are today. I had to be shown my options, where I could be helpful. My path was one so many have followed. I ended up staying here for so long because of the people who caught up with me along the way and helped empower me as a contributor, so thank you.

Props is just one of the firsts

Whilst these are 'first', they are just the public ones. There are so many firsts in a contribution journey. I was in these projects before my props. My first experience with core was that it was too overwhelming, which is why my first props is in BuddyPress. My first solo theme review was also pivotal to my journey 14 years ago.

Every conversation, particularly in the first few stages, was pivotal to my journey as it set the tone for where I ended up adventuring. They could also have been points that led me to leave the project because I couldn't find a way to contribute. I hold onto this point when interacting with others, as each contribution is so significant. You never know what someone will do in a project if they are given the opportunity, and it starts with them knowing they can do things. It's essential always to acknowledge and recognise everyone who contributed. You never know whose first props those might be and what impact each of us might have on someone's journey of contribution.

Someone might also travel this project and never get props, because perhaps of the contribution area they are in or the work they are doing. That's a key thing to consider, and actually, my own journey has public and non-public recognition due to different roles. As a project, WordPress needs to be better at recognising and measuring all types of contributions so the pride we all feel in props can be given to anyone contributing significantly.

If open source contribution works, it's a journey. This point is demonstrated by the adventures I have travelled and those of others within these projects. We have grown up, changed jobs, and moved locations, but we stayed with the project and our contributions. You do that because you want to, because you are getting something from doing it, as contribution has to be a two-way street to become a part of someone's life. Props and other recognition are a boost to help you on that journey. It works because it acknowledges the work being done, and in its simplest form, it is a way of saying thank you.

10 Jul 2025 9:14am GMT

As AI advances, WordPress must choose between cloud-based tools or local agent workflows. Emerging protocols allow dynamic communication, influencing automation, privacy, and the future control of web content management.

10 Jul 2025 9:01am GMT

In 2004, I was at home with one baby, having just left a career that I loved. Being at home with a baby full-time was shriveling up my brain. Before WordPress I tried gardening, sewing, painting, preserving and cooking. I was desperate to fill the void left by my career.

My husband at the time, was a tech genius and had heard of a new get rich quick scheme: "blogging".

I didn't know what that meant - I had to research what the internet was! But I was desperate and the evening news was featuring these "mommy bloggers" who were making small fortunes!

"If they can do it", I thought, "So can I!"

I made a whole $0.82 that year.

I am not easily dissuaded though. I decided that a new theme would get me more revenue.

To build themes circa 2007, you had to learn the template system, the file structure, and the hooks baked into WordPress.

It was like a giant puzzle and I was so excited to be using my brain - I jumped in.

Learning to Swim

I read every single page in the WordPress.org docs. I spent 10-20 hours a week in the support forums, mostly asking for help - not giving much!

I learned to code by fixing real problems - it was challenging and the internet was full of quality resources.

I made big mistakes - I crashed countless sites! And in doing so, I learned what not to do.

I was in heaven.

Except for those all-nighters trying to fix something that I broke on a client's site.

I learned from the best in the community - because back then, they were in the forums with me. I learned from friends and other bloggers. I learned from online articles (pre-YouTube days).

Along the way, I met a fellow mommy blogger who had a side business called Desperately Seeking WordPress. (Her blog was Desperately Seeking Sanity and she has the best sense of humour!) She needed help. I was available.

At the time, our offer was simple: we would install WordPress, a theme, and a few plugins - and make it look nice - for $20.

Eventually, she stepped back, and I got to take the reins.

That's when I realized I hadn't the foggiest idea how to run a real business. I started reading books like *E-Myth*, *Duct Tape Marketing*, and *Purple Cow*. I had no MBA, no startup capital. Just the desire to help other mommy bloggers not get ripped off by tech 'gurus'.

Building a Business While Falling Apart

I've struggled with depression for my entire adult life. By 2006, I had three young children. By 2012, I was divorced. The work that had been a fun puzzle, now had to pay the bills.

I couldn't disappear on bad days - my fledgling company had to be reliable! The clients needed stuff. So I hired my first contractor. She made more than I did most months.

But I needed to know someone would be there for my clients when I couldn't be. That was the first step toward building a team that would be better than any of us could have imagined.

The behind-the-scenes work we do stays the same whether it is for celebrities or tiny fledgeling bloggers. And when we were kind, didn't talk down to them, and were honestly helpful, they talked about us. And we became 100% referral-based.

So how do YOU get referrals?

I can't tell you that - but - I know what works for us: radical honesty (even when it hurts our bottom line), genuine kindness and respect, and being the best at what we do. I believe with all my heart that our clients are in good hands.

And that honesty requires owning my mistakes. I wish I could say I don't make them anymore but… radical honesty!

We always do what's in the client's best interest, even when it costs us money.

The Invisible Work

After about seven years, I made an intentional decision to hire women. I grew up in West Africa, and I've seen firsthand how empowering women lifts entire families and communities.

So we began funding microloans for women entrepreneurs in developing countries. The research shows that supporting women has a multiplier effect - and I've always had a soft spot for hard-working entrepreneurial free spirits.

From the very beginning, we were a remote team. I've never been on my own - being reliable is a non-negotiable - I need the team.

One of those teammates is Diane. I met her 14 years ago, just after she got married. She's quiet, steady, avoids the spotlight - and she's been one of the most important people in my life. We've built a business together through births, illness, life transitions - and I trust her completely.

That trust, that stability, is part of what we offer our clients. And it's rooted in one simple idea: be kind. Treat everyone with dignity. Respect whatever expertise they bring, even if it's not technical. Our job is to help their business succeed - not to impress them with ours.

Burnout, Boundaries, and Pricing with Purpose

In 2014, I burned out - hard. I had thrown myself into social media marketing. I spent $1000's on courses and really tried to implement the suggestions. Guest post twice a month? Check. Two hours connecting on Facebook every day? Check. Write three posts a week? Check.

I did all the things. 'Cause they told me to.

I think it only took me three months to crash and burn. I got so sick, my body was done. I spent two full weeks in bed.

That's when I learned my limits. And it's when I learned to stay focused.

Today, all decisions go through a, "What does this do to the bottom line?" framework. And by bottom line - I mean money, of course, but without sacrificing service, honesty or the trust of our clients.

Part of our growth meant making pricing decisions that felt terrifying.

We raised prices from $20/setup to $40/hour. We lost 20% of our clients - and I expected to lose more. But the ones who stayed? They valued us. They paid happily. They referred us to others.

Later, we raised it again - to $75/hour. I braced for another drop. It never came.

Instead, I got emails thanking me! Clients said they were glad we were finally charging what we were worth! I'm still shocked about it. Who knew I'd have warm fuzzy stories on the day we raised our prices?

Eventually, we raised it to $89/hour. Still below the $110-$120 that custom coders charge. Because we're not "true coders." We're *practical coders.* We solve real problems, fast, for people who trust us.

And that trust is priceless.

On Staying True in a Shifting World

Through all of this - the growth, the pivots, the grief and healing - this little WordPress agency has offered me survival.

The ability to work from home. To be present for my kids. To build something real while living with depression. To build a team based on trust, not hustle.

I can only recommend something that I truly believe is the best option for my clients. That's why WordPress matters to me. It's extensible, open-source, secure, supported, owned and portable. Currently it is the best option for my clients. And I can stand behind that.

A sign sits on my desk. It reads: "Who can I serve today?"

That's the constant. That's the compass.

Today, I volunteer in the WordPress support forums - the same ones I learned from. I volunteer in the community to give back. I'm sharing my story, not to teach anyone how to succeed, but to say: it's okay to build slow. To price based on value, not hype. To grow into leadership without chasing fortune.

There are still chapters unfolding in my story. Some endings haven't revealed themselves yet. But I know this much:

I stayed.

And through WordPress, I learned that staying - quietly, kindly, steadily - can be its own kind of success.

Cathy's Work Environment

We asked Cathy for a view into her development life and this is what she sent!

HeroPress would like to thank Draw Attention for their donation of the plugin to make this interactive image!

The post The Remote Team Who Raised Me appeared first on HeroPress.

09 Jul 2025 3:00pm GMT

On the podcast today we have Héctor de Prada.

Héctor is one of the founders of Modular DS, a tool for managing multiple WordPress websites, but his contributions to the WordPress community go far beyond his day job. Based in Spain, he's been involved in creating and developing websites for years, and has immersed himself in the WordPress community, attending numerous WordCamps and Meetups in various cities. More recently, he's been co-organising the WordPress Meetup in León, a city in the north of Spain, which has seen impressive growth and engagement since its revival after the pandemic.

Héctor shares why he volunteers his free time to organise these community events, and the impact Meetups can have, not only for individual learning, but for revitalising local tech ecosystems.

We discuss what makes a successful Meetup, how his team approaches event planning, rotating roles so nobody feels the pressure to attend every time, and how sponsors and local venues help make it all happen.

Héctor explains how their Meetup group draws diverse attendees, from students and marketers to business owners and agencies, and how they've experimented with differing formats and topics to keep things fresh and inclusive. Whether it's inviting guest speakers from digital businesses, running panel forums, or focusing on networking opportunities for job seekers and entrepreneurs, he highlights the power of community in building connections that extend beyond WordPress.

We cover everything from the practicalities of finding venues and sponsors, to managing team workflows and keeping the events welcoming and approachable.

If you've ever thought about starting a WordPress Meetup in your city, or want to bring new energy to an existing group, this episode is for you.

Useful links

Héctor's presentation at WordCamp Europe 2025: Tips for hosting a successful WP meetup in your city

WordPress León meetup

Héctor on LinkedIn

Héctor on wordpress.org

09 Jul 2025 2:00pm GMT

As described by longtime contributor Tammie Lister in a recent episode of Open Talk on Open Channels, fractional sponsorship is when a contributor is sponsored part-time by multiple organizations (or individuals). Rather than being fully funded by one company or acting as a purely unpaid volunteer, fractional contributors assemble support from several interested parties. As […]

09 Jul 2025 10:46am GMT

Twelve years ago today, I received my very first props for contributing to WordPress Core. I had no idea at the time, but it turned out to be a transformative milestone in my career.

In WordPress, community participants receive credit for contributing to a given change or deliverable by receiving "props."

Props should be given to all those who contributed to the final commit, whether through patches, refreshed patches, code suggested otherwise, design, writing, user testing, or other significant investments of time and effort. Usernames are parsed for the credits list and WordPress.org profiles.

WordPress Core Handbook

Before each release, the names of all contributors to that version are collected and added to the Credits API, which powers the Credits page in the WordPress dashboard. I'm proud to have been listed on that page for 22 consecutive releases starting with 4.7, and 27 of the 33 releases overall since my first credited contribution in WordPress 3.7 "Basie," alongside 210 other contributors.

To celebrate my ten year anniversary, I started publishing a blog post each year. In past editions, I've focused a bit on my WordPress origin story and looking at some "props" related data.

This year, I'm excited to commemorate the day by announcing something new!

From Stage to Essay

At the end of May, Nick Vidal from the Open Source Initiative reached out to me. To celebrate GitHub's Maintainer Month, he had been working to compile a collection of contributor stories for a book about the maintainers behind Open Source projects. He asked me if I'd be willing to submit something.

I was honored! I read through the dozen or so questions he sent and wrote answers for a handful that resonated with me. The next day I flew out to attend WordCamp Europe. Between the whirlwind of travel, attending sessions, and preparing to give my talk, I completely forgot about it.

A few days after speaking, I received another email from Nick.

While doing some research about you, I fell in love with your recent talk at WordCamp Europe.

He had seen the recording of my talk and asked me to incorporate the subject matter with the answers I had already sent over for the book. My speaker notes captured the core ideas, but they needed a lot of refinement and proper citations before they could stand alone as a publishable essay. I also included some thoughts from my recent post about the impact of maintaining Open Source projects.

I'm excited to share that thanks to the many hours Nick put into the project, the maintaine.rs website showcasing this project is live. You can read my essay on the website, or download the full book in PDF or EPUB format.

Building On The Ideas Of Others

My good friend and fellow Core Committer Felix Arntz celebrated the 10 year anniversary of his first contribution to WordPress late last month. He wrote about 10 things he's learned in 10 years of contributing.

As far as I know, Felix hadn't seen my WCEU talk or heard about the Maintainers project. Despite that, we ended up exploring many of the same themes and principles.

While the ideas I explore in my talk and essay aren't novel, they're rooted in lessons I've learned from others and foundational Open Source concepts. A key part of participating in any Open Source community is learning from your predecessors. How should we conduct ourselves? How should we structure our communities? How should we make decisions? You can earn the respect of your peers by demonstrating that you thoughtfully consider these questions through your day to day actions.

Submit Your Own Story

I'm grateful to be included in the book among many other amazing maintainers, but I was also glad to find out I was not the only maintainer representing the WordPress project: Tammie Lister also submitted her maintainer story.

While it's good to see WordPress represented in the book, the project is maintained by many people, not just two.

On the landing page for the project is a call out to "Share Your Story" for consideration in future editions. The HeroPress site does an amazing job of surfacing the stories behind members of the WordPress community. But there's value in sharing those stories with the broader Open Source community too. If you help maintain WordPress in some way, I hope you'll consider sharing your story for a future edition of the book, they all deserve to be heard.

Closing Thoughts

Over the past 12 years, I've done my best to contribute in ways that don't just solve problems, but make the project more approachable, more sustainable, and more human.

I recently received this DM from someone.

"Watched your talk on my way home. You did a fantastic job explaining core and the committer role. Reminded me why I'm still around and invigorated to do more. Thanks!"

It came from someone I deeply respect, someone I've learned a great deal from over the years.

It's easy to underestimate the impact even our most routine contributions can have on others, especially in Open Source, where so much of the work happens asynchronously and behind a screen.

Messages like this remind me why I do this work. I hope others have found value or inspiration in what I've shared. And if my story, my talk, or my essay helps even a few people feel more connected or inspired to stay involved, then it's all been worth it.

Here's to year 13 and beyond.

"Props" Anniversaries: Ten, Eleven.

Commit-iversaries: Two, Five, Six.

Featured image credit: "A couple of bookshelves with colorful books on a stone wall" by mdburnette/ CC0 1.0

The post 12 Years Contributing to WordPress appeared first on Jonathan Desrosiers.

08 Jul 2025 11:52am GMT

In this Media Playbook episode, Rae Morey and Adam Weeks discuss effective pitching for WordPress stories, covering what makes a story newsworthy, and providing practical advice for successful media outreach.

08 Jul 2025 8:27am GMT

When a business first starts creating content, it often looks chaotic. There's not always a strategy. You try a few blog posts, maybe some tutorials or listicles, toss in a few keywords you think matter, and hope something sticks. And that's okay. In fact, that messy start is what helps shape your future strategy. The […]

08 Jul 2025 7:17am GMT

Before I begin this post, I am writing it not expecting change, but rather sharing my opinion. It is the opinion of someone who has themes both default and working with them from agencies to exploration, threaded through their life. I say this with a passion for what themes were, are, and I see evolving into. I am also focusing on a pause, not a stop or hard point. This is a suggestion, a thought I am working through myself.

The past

The default themes worked for us as a project in WordPress. They were both a call to unify in work, and also allowed us something to focus on testing the features of the year. They were also a way to close out the year; historically, many switched to them to showcase.

Another thing the default themes have done well is showcase different aspects of WordPress. One could argue that having a theme focus is key for everyone. Similarly, many writers use it as a basis for their content, drawing on it as fuel. It was an end to the year for many, although I would self-reflect, as the years have gone by, this has waned. Again, this is a personal reflection.

Today

For a long time, whether we like to admit it or not, the default theme process has been more complex and disjointed. It hasn't been as much about testing features as many weren't theme visible.

Each default theme currently incurs a high maintenance cost. This goes over the code in support. I am reluctant to recommend anything in core that adds to the bundled theme debt at this time, considering there is still a backlog. To be clear, I want to see significant product benefits before recommending it as a course of action.

Themes have changed

Themes are a sliding scale of complexity, ranging from the quick brew weekend, a few hours of JSON for a personal site, to the large-scale enterprise theme founded on a complex design system, an extensive pattern library, and variations. Themes today are different, and anyone who is creating them knows this. Anyone not creating them also knows this, which is where the next bit comes in.

The education piece

One of the loudest comments in favour of having a default theme is that it brings education. Whilst this is true, education once a year isn't useful. We need to consider the themes that are relevant today, and to do that, we need to examine all the pieces and their respective use cases. How are different people making themes? How are individuals experimenting? How are agencies scaling? How are people using themes today, and where are they stuck?

What a theme is needs to be reconsidered

The strongest point for pausing this year is to take a moment as a project and consider what a theme is today. What design tools are missing that we need first? What pieces do we have, and how do they go together? Where do they not go together and need to? Fix those flows first, then build amazing 'themes' or whatever we settle on.

The future of a theme might be a 'kit' where you have a style you share. It might be something else. We haven't paused long enough to think about it, and it's not the same format we keep reworking in default themes.

What else could we do instead?

Here are a few things that could be done with all the people and effort a theme release typically takes. It's worth noting that they require a lot, which is why these are in much greater demand at this time.

• Education: Many people still don't understand or haven't fully explored the potential of block themes. Taking time for this collectively could be a powerful experience. It also helps the ecosystem, agencies and products.
• Improve the design tools for themes: By adding features such as adaptive controls and other missing pieces, redirecting the effort that would have gone into the default theme into the core editor itself. This benefits everyone and all themes.
• Rejuvenate the community theme project: This moves it beyond being a one-time event and could include various types of experiments. Allow exploration of what a theme is.
• Identify the areas where the themes are not working out: Improve this with tools and also within the core itself. This goes beyond the design tools and into the system of themes themselves.

A pause is not a stop

I chose this title because I am suggesting a pause, although I struggle to see 'when' we would need them, but of course, things change. As a project, WordPress should also release more experiments on what a theme should be today. That's been the issue, and as a result, the default theme has become such a hot topic for people.

This is just my thought, though. If a default theme were to happen, it would be amazing and welcome. I also know it will be done incredibly well. I often reflect on the logistics and the limited resources required for incredible contributions. I always want to put them in the space where they will be most effective and move the project forward. I also think that, as a product, it makes sense to have focus, and I can't see a default theme that fits right now. I'm open to evidence, as always, to counter that. For that, it's up to the project to decide, not me.

06 Jul 2025 4:57pm GMT

Another month has passed and what a month this was, it started with WordCamp Europe and ended with a new sponsor.

Areas of contribution

My focus continued in the areas it had before, but I also began trying to work more product work into this. I also attended the contribution day at WordCamp Europe, as well as the event itself. I had many great conversations that fueled me throughout the month.

Some stats this month (it's worth noting I also did a lot of commenting, feedback and other activities outside of ticket numbers but they are good to refer to):

• Commits: 4
• Closed tickets: 44
• Gave indepth feedback: 32 (this is worth calling out as often requires time around product and design).

I have also been exploring how to optimise flows, such as rapid note-taking, and speed up more triage processes.

• Backlog: My focus was on closing tickets and also on the ancient list which is to clear down.
  • Another focus on the Gutenberg repo and clearing up the 'needs design' to be a true reflection of that state.
• Extensibility: Reviewing and verifying if issues are still valid, while also engaging in conversations about next steps.
• Bundled themes: Cleared out things for potentially including in next release.

I also explored limits with dataViews and other areas of the editor, and as a result, encountered issues. This is always beneficial to do, as I learn each time where the boundary problems lie.

Sharing the journey

This month saw the opportunity to share my journey in contribution in a conversation with Marcel Bootsman at WCEU for Kinsta. I also got to be on the OpenChannels.fm talking about the evolving landscape of core contribution and company sponsorship, with Tim and Zach from BigScoots with the amazing Adam Weeks joining us.

I continued to reflect on the learnings from the work I am doing. I wrote about 'Defining Roadmaps in the Open' and 'Optimising Triage and Review Processes in WordPress using AI'.

Upcoming plans for contribution

I am allowing July to take shape as it unfolds, but to start with, this work will form the foundation. I also want to explore how I can incorporate some of my outside product management experience a bit more.

• Backlog:
  • Focus on ancient and inactive trac log.
• Core editor:
  • Continue on making sure 'needs design' label is a true indicator.
  • Move on to the triage of the components label.
  • Components: see where can help with documentation - for example how can things be surfaced on make easier.

Sponsors this month

06 Jul 2025 3:37pm GMT