The WordPress community recently announced the Zeel Thakkar Memorial Scholarship, created to support women from India and Nepal who want to attend the major WordPress event in their area: WordCamp Asia.
The scholarship honors the memory of Zeel Thakkar, a WordPress contributor who passed away last year at a young age. Zeel contributed across several major WordPress releases, participated in local and regional events, and was known in the community for her enthusiasm, kindness, and commitment to open source.
I had the opportunity to cross paths with Zeel during work on past WordPress release squads. I remember seeing her contributing during release parties that I was coordinating for WordPress 6.7 and 6.8. Moments like those are where many contributors first find their rhythm in the project. Hopefully the props she received during those efforts helped encourage her continued interest in contributing to WordPress. Her participation and growth as a contributor are a good reminder of how welcoming entry points into the project can help nurture the next generation of community leaders.
Programs like the Zeel Thakkar Memorial Scholarship matter not just because they honor a valued contributor, but because they strengthen the future of the project itself.
Many long-time WordPress contributors can trace their deeper involvement back to attending a WordCamp. Meeting other contributors in person, participating in Contributor Day, and seeing how the project operates behind the scenes often becomes the moment when someone moves from casual user to active contributor. Those contributors go on to help lead release squads, maintain components, organize local communities, and guide the direction of the WordPress project.
Travel and conference costs can be a real barrier for contributors, especially in regions where the WordPress community is growing quickly but resources are limited. Scholarships like this help remove those barriers and open the door for new contributors to participate in the global WordPress community.
In that way, this effort isn’t only about remembering Zeel. It’s also about making sure more people have the same opportunity to step into the community, build relationships, and find their place contributing to WordPress.
I’ve made a donation today and hope that you consider doing so as well.
If you’re able, please consider contributing to the scholarship fund. Contributions of any size help expand the opportunity for future contributors to attend events like WordCamp Asia, connect with the community, and continue the work Zeel cared deeply about.
Open source communities thrive because people show up for one another. Supporting initiatives like this is one small way we can honor Zeel’s memory while helping the next generation of contributors find their way into the project.
I recently had the chance to join the Crossword podcast for a conversation about open source, WordPress, and what meaningful contribution really looks like beyond writing code.
On this episode of Crossword.fm, we talked about how I got involved in the WordPress project, why non-technical contributors play such a critical role in open source, and what I’ve learned from spending nearly a decade working at the intersection of product, community, and engineering within the open web.
A few of the themes we explored include the value of organizers and facilitators in large open source projects, how text-first and asynchronous collaboration (meaning Slack-based meetings and regular meeting summaries and decision documenting via WordPress.org posts) helps WordPress scale globally, what sponsored contribution looks like inside agencies, and how to think about the future of WordPress in a way that brings people along rather than leaving them behind.
As with most good conversations, there were a few things I wanted to expand on but simply ran out of time during the recording.
One important example worth calling out is the continued leadership coming from Human Made, particularly through the work of John Blackbourn. During the episode we touched on agencies noticeably contributing to the project and I would be remiss without plugging John’s work. Their sustained investment in leading and supporting the WordPress Security Team is a strong example of what high-impact, long-term contribution looks like when a company aligns its expertise with a critical need in the project.
We also touched briefly on the question of how to get companies to agree to contribute to open source. In practice, the most realistic path forward usually starts with business alignment. What improvements to WordPress would directly support a company’s products, services, or clients? Advocating for and contributing toward those outcomes is often the clearest way to earn leadership buy-in. That contribution may not always be in core, and that’s completely fine. Sustainable participation tends to start where incentives overlap.
Finally, a quick clarification on a phrase used during the conversation. When Luke referenced “skating to where the puck is going to be,” that’s a sports reference that means anticipating demand rather than reacting to it. For folks like my dear friend Weston Ruter and others who do not live in the world of sportsball, that was what Luke meant.
If you’re interested in contributing to WordPress, supporting open source from inside an organization, or just want a grounded look at how large community-driven projects actually function, I think you’ll enjoy the conversation.
Open source software powers critical digital infrastructure, but funding rarely reaches the people maintaining it. Dries Buytaert’s post on digital sovereignty makes a strong case for changing how governments and organizations invest in open source. Recent sustainability challenges in projects like Tailwind show this isn’t theoretical. If organizations rely on open source, contributing back (including funding) should be treated as a baseline responsibility, not optional goodwill.
This post is not a summary or a critique. It’s an agreement and an attempt to extend the argument into the broader open source ecosystem, especially WordPress.
Dries articulates a problem that’s been hiding in plain sight for years. Open source software underpins much of our digital world, yet the people and projects responsible for building and maintaining that software are routinely bypassed when funding decisions are made.
Dries frames this through government procurement and digital sovereignty, but the issue is broader and structural. We see the same dynamics play out across the private sector and across ecosystems of every size.
I’ve been thinking about this recently in the context of projects like Tailwind CSS. Tailwind has enormous adoption, deep influence on modern web development, and a thriving ecosystem built around it. And yet, like many widely used open source projects, it has struggled at times to turn that success into stable, long-term funding for maintenance and stewardship.
That’s the paradox: popularity is often mistaken for sustainability. In reality, widespread usage can increase the maintenance burden faster than funding models evolve to support it.
In many ways, this starts to resemble a modern version of the tragedy of the commons. Open source is a shared resource that everyone benefits from, but when responsibility for sustaining it is diffuse, the rational short-term behavior is to underinvest and hope someone else picks up the slack. The result isn’t sudden failure, but slow erosion through burnout, deferred maintenance, and growing risk.
This is not a Tailwind-specific problem. It’s a pattern.
The same tension exists in the WordPress ecosystem.
WordPress powers businesses, governments, nonprofits, publishers, and educational institutions worldwide. Entire industries are built on top of it. Economic value flows through hosting companies, agencies, SaaS platforms, and integrators, while upstream projects and maintainers often rely on voluntary contribution or a relatively small pool of sponsors.
Programs like Five for the Future have helped normalize contribution as part of doing business, and WordPress has benefited enormously from sponsored contributors who show up across multiple release cycles. But even here, the gap between value extracted and value reinvested remains real. When budgets tighten, open source contributions are often treated as optional, despite supporting mission-critical systems.
What resonates most in Dries’ post is the framing of open source as shared infrastructure.
We already accept this model elsewhere. Roads, utilities, and public services are funded because society depends on them. Open source software plays a similar role in the digital world. If organizations rely on it to operate, scale, and serve people, contributing back (including funding) should be a baseline responsibility, not an act of goodwill. If contribution is a responsibility rather than charity, it’s worth being clear about what responsible, sustainable support actually looks like.
So what does sustainable support actually look like?
We already have working examples:
Red Hat has shown how commercial success can directly fund upstream Linux development over decades.
WordPress has demonstrated the impact of sustained, sponsored contributor programs tied to releases, security, and long-term maintenance.
Government-backed efforts like the Sovereign Tech Fund recognize open source as critical infrastructure worthy of direct public investment.
These approaches differ, but they share a common trait: funding the people and projects doing the upstream work, not just the layers built on top of them.
Dries’ suggestion that procurement and vendor selection should explicitly account for upstream open source contributions is especially compelling. It aligns incentives toward long-term sustainability instead of short-term delivery. It also rewards organizations that treat open source stewardship as part of their operating model, not a marketing line item.
Whether we’re talking about government digital services, enterprise platforms, or widely adopted frameworks like Tailwind, the lesson is the same: popularity is not a funding model.
If we care about digital sovereignty, resilience, and innovation, we can’t assume open source will take care of itself. It won’t. It’s built and maintained by people, and those people need consistent, institutional support to do this work well.
So here’s the question I think every organization should be asking itself:
If your business, platform, or public service depends on open source, how are you directly funding and sustaining the projects and people you rely on?
Dries’ post is an important signal in that direction, and I hope it pushes more organizations to answer that question honestly. If that answer is unclear or uncomfortable, that’s probably the point.
There is a moment every year when the lights dim, the livestream timer counts down, and the room settles into that familiar mix of quiet and anticipation. This year, State of the Word left me with a feeling I have not had in a long time. It felt like all the threads of AI work happening across WordPress finally came together.
If you have not watched the replay, it is worth it.
Before I dig into the part I had the privilege of contributing to, here is a quick sense of how the event landed for me.
The WordPress AI panel and the shift happening in real time
One of the highlights of my year was joining the AI panel hosted by Mary Hubbard, alongside Matt Mullenweg, Felix Arntz, and James LePage. Sitting on that panel, hearing how each of us approached AI from different angles, I realized we were not just discussing features. We were describing a shift in how people will build and maintain sites in the coming years.
This is where the “obvious and surprising things” came up. These were ideas I shared during the panel, because they reflect what I have seen across Fueled (and 10up) client work, ClassifAI development, and now the AI Experiments plugin.
The obvious things
These are the patterns everyone expected to see, and they are becoming mainstream faster than many predicted.
Chat-based search showing up as a natural extension of site discovery
Local and in-browser models that run privately, offline, and at very low cost
AI-driven brand visibility (aka “GEO” or Generative Engine Optimization)
Content distribution and translation workflows that used to require entire engineering teams now becoming almost trivial
These trends feel obvious only because the groundwork has been quietly laid for years.
The surprising things
The twist this year came from watching how people are starting to use the new Notes feature in WordPress 6.9.
I mentioned this on the panel because it caught me off guard when I saw it bubbling up within the community during the 6.9 release cycle. People are already experimenting with AI-driven content review inside Notes. Imagine WordPress calling out accessibility issues, shifts in tone, or sections where your writing reads differently than you intended. These are editorial tools that used to require specialized software. Now they are emerging directly inside WordPress.
That is when it hit me. The AI conversation in WordPress is no longer about novelty. It is about workflow, quality, and confidence.
A journey that started long before this State of the Word
For me, this work did not start with the AI Experiments plugin. It started in 2018 when the 10up team built the first version of ClassifAI for a client who needed content classification at scale. We open-sourced it in 2019 and kept evolving it as real publishers and agencies pushed its limits.
Those years shaped everything I know about AI inside WordPress. They taught me how AI fits into editorial workflows, when AI should require human review versus full automation, how permissions and provider selection affect trust, and how failure states must be designed with care. Those lessons are now embedded in the AI Experiments plugin.
ClassifAI will continue serving enterprise use cases with deep configurability. It will adopt the Abilities API, MCP adapter, and WP AI Client as those stabilize in the ecosystem.
The AI Experiments plugin takes a different path. It offers simple, approachable example AI experiments for non-technical users, while also serving as a reference for developers, agencies, and hosts who want to build AI powered features for their customers.
Each of these experiments helps us learn how people want to use AI inside their workflows, and which features could grow into stable tools inside core one day.
Looking ahead
This year’s State of the Word left me excited about something simple.
We are not racing toward AI.
We are shaping AI so it fits naturally into the way people already work in WordPress.
We are building an ecosystem where:
open tools remain the default (I’m specifically passionate about open source, local LLMs)
user choice stays central
and AI enhances creativity instead of replacing it
If you want to explore the AI Experiments plugin or get involved, you can follow everything in the open: https://github.com/WordPress/ai. And if you have ideas or want to push the boundaries of what is possible, I would love to hear them.
I had the privilege of speakingtwice at WordCamp Canada (“WCEH”; as in WordCamp, eh?)this year but had to leave before Matt Mullenweg’s town hall because of a family emergency. After catching up later through his recap post, I was struck by how much ground he covered, from personal publishing tools and encrypted journaling to AI, open media, and the future of the web itself.
His remarks touched on several themes that feel central to WordPress’s next chapter: helping people reclaim their online identities beyond centralized platforms, and navigating the tension between openness and authenticity as AI reshapes how we create and trust content.
I wanted to ask Matt two questions that build on those ideas about the role WordPress can play in making “publish once, syndicate everywhere” a reality, and how it might help rebuild trust in what’s real online.
Let me give a little update on what I’ve been up to. My life’s mission is to democratize publishing, commerce, and messaging.
On the social side of publishing, I have Tumblr, which is a microblogging social network, but right now it’s on a different technical stack. I need to switch it over to WordPress, but it’s a big lift. It’s over 500 million blogs, actually, and as a business, it’s costing so much more to run than it generates in revenue. We’ve had to prioritize other projects to make it sustainable. It’s probably my biggest failure or missed opportunity right now, but we’re still working on it.
Day One is a fully encrypted, shared, and synchronized blogging and journaling app that runs on every device and on the web. You can also have shared encrypted journals with others. It uses the same encryption as one password. It’s the first place I go to draft an idea—for example, to write this talk. Its editor is not as good as Gutenberg yet, but it’s pretty decent at allowing multimodal input—which means you can record voice notes, draw things, etc.—and capturing it all. It’s mostly replaced Evernote, Simplenote, and even private P2s for me. It has some fun features, like when you make a new entry it records, the location, what music you’re listening to on Apple Music, how many steps you’ve taken, the weather. Honestly, some features that would be nice to get into WordPress, at least as a plugin.
So WordPress.com Studio is built on an open source project called Playground that we created to allow you to spin up WordPress in a WASM container in about 30 seconds, right inside your browser.
So my first question to Matt is this: WordPress powers much of the open web, but most people still publish primarily on centralized social platforms. There were some good talks at WCEH on the open web, the social web, and the indie web, shared by Dave Winer and Evan Prodromou this week and by Tantek Çelik at WCUS 2019. What role do you see WordPress, either in core or through plugins, playing to help people reclaim their online identity and make ‘publish once, syndicate everywhere’ a mainstream reality?
However, when AI creates a face, there’s no such restrictions there. So something that we could actually start to do, because right now I think we have some anti-AI rules in the photo directory, I think we should probably start to look at evolving that. So, for example, you can take a picture of me right now, change my face with AI to a face that has never existed, and that could be CC0-licensed and anyone in the world could use it. So I think there’s some possibilities there.
I also think there’s some opportunities to use AI analysis of all the photos to give a better semantic understanding and a better search that we currently offer, which right now is typically monollingual, I don’t think it translates well into the, you know, 60-plus languages that WordPress supports, and it’s manual tagging. So there might be things to do, like a more automated understanding, which, of course, gets better over time.
You know, we started to incorporate some of the AI models like Gemini and other things on WordPress.org to make us way more efficient on things like plug-in submissions and some code scanning. I actually think we’re very much in chapter one of where this is going to be.
So first I will say, I don’t want to say that there’s bad actors. I think there might be bad actions sometimes, and just temporarily bad actors who hopefully will be good in the future. You know, every saint has a past, every sinner has a future. I never want to define any company or any person as permanently good or bad. Let’s talk about actions.
Which leads to my second question for Matt: As AI makes it harder to tell what’s real online, trust in content is slipping. The Breaking News episode of RadioLab in 2019 showed how deepfakes blur the line between truth and fiction. How can WordPress and the open web help rebuild that trust? For example, could it support initiatives like the Content Authenticity Initiative that use open tools to verify the source and history of digital media?
I’m thrilled to share how the Shipping WordPress Without Shipping Code talk went at WordCamp Canada 2025 (aka “WCEH”; get it WC, eh?). For folks who couldn’t attend, here’s a summary of what we covered, insights from the audience, and next steps you can try yourself.
If you’d rather watch than read, here’s the full WordCamp Canada 2025 talk:
In the talk I walked my own path, from helper to release deputy to AI team lead, all without ever having commit access. Along the way I shared how non-developer roles often get overlooked, practical patterns I’ve used to keep releases moving, and encouragement for designers, strategists, writers, or project leads who want to jump into this space. Here’s how the session unfolded, with some highlights and sample quotes.
Opening & Framing
I started by confronting the myth that only engineers lead in open source. My aim was to shift perspectives: YOU can lead, even if your strengths lie outside code.
The Historical Gap
We talked about how WordPress projects have historically lacked project and product management support, and how that gap creates friction. I quoted from the WordPress release handbook:
“The main focus of the release team is to lead the release from its beginning through to launch … to act as connectors and facilitators.”
It resonated: many in the audience nodded when I called out that non-developer contributions are often invisible or undervalued.
My Journey
I shared my own timeline: involvement in WordPress 4.7, then 4.8, 4.9, 5.8, 6.1, and 6.8. I also noted that WordPress 4.7 had 482 contributors, including 205 first-timers, to emphasize how major release cycles need more scaffolding than code alone in order to support that many new contributors.
What “Glue Work” Looks Like
This was a core section of my talk. We broke down how “glue work” such as triage, alignment, decision logging, and volunteer motivation is the connective tissue in a release. I used the quote:
“Triage is the practice of reviewing existing issues to be sure they are relevant and actionable.”
And I referenced how Apache PMC members and Kubernetes maintain non-coding roles, showing that this isn’t just WordPress-specific but a pattern in mature open source communities.
Tools, Patterns, & Gotchas
Here, the audience got actionable advice. Some highlights:
Use GitHub issues and projects with clear labels (needs-decision, punt, etc.)
Maintain decision logs so the same debates don’t repeat
Establish scope gates (feature freeze, RC readiness) to protect the release timeline (go/no go decisions)
Beware burnout and invisible labor
I referenced Karl Fogel’s Producing Open Source Software from my notes in a recent WordPress Book Club hosted by Aaron Jorbin roughly as ~“If it’s not written down, it didn’t happen.” And Nadia Eghbal’s note that “Maintainers simply don’t have the energy to onboard every person who shows passing interest.”
From Contributor to Leader
We laid out a three-step path:
Start small: take notes, triage, run a meeting agenda.
Own a lane: coordinate docs, dev notes, or release notes.
Lead a release: coordinate across teams, make decisions, facilitate.
I also referenced the Kubernetes “leads and shadows” model as something WordPress could use to mentor future contributors.
Practical Playbook
Seven habits you can take into your own contributor journey:
Write the agenda, end on time
Keep a decision log
Guard scope with labels
Close stale issues
Default to public and async
Give credit often
Leave breadcrumbs
I urged the audience to pick one habit and try it immediately.
Takeaways and Q&A
I wrapped up by reinforcing that leadership lives outside the repo and glue work makes shipping possible. I invited folks to pick a lane, join a triage session, or help curate the next release.
The question period surfaced great stories: people surprised they could participate in release work without code, and others asking how to balance contributions with full-time jobs.
What I Learned from the Room
Many talented people hesitate because they don’t see non-developers in core.
The “playbook” habits resonated; people wrote them down quickly.
There’s appetite for more structured mentorship paths for project contributors.
Some folks suggested pairing systems (non-developer lead and developer lead) to onboard new contributors.
Next Moves You Can Try
Join the next WordPress core triage or bug scrub session.
Volunteer to take notes for a devchat.
Pick one of the seven playbook habits and try it in your own project or team.
Consider how your current job or project might adopt glue roles, like coordinating features, managing scope, or writing decisions.
Final Thoughts & Thanks
Before wrapping up, I have to say how special it was to experience WordCamp Canada in Ottawa. The Carleton University campus was absolutely stunning, with crisp fall air, the leaves just starting to turn, and Richcraft Hall overlooking the canal and nearby lake creating an incredible setting.
Ottawa itself is a beautiful mix of history and energy, with old architecture and monuments along the Ottawa River that show how much care the city puts into preserving its character.
And of course, none of this would have been possible without the amazing organizers, volunteers, and sponsors who made WordCamp Canada feel every bit like the flagship event it is becoming. The warmth and generosity of the Canadian WordPress community really stood out, from hallway conversations to contributor day collaborations.
Running this talk in Canada felt meaningful. It’s part of a larger conversation: WordPress needs more voices who see beyond code, people who connect, facilitate, and help the system work. I can’t wait to see what happens when more contributors realize they are leaders already.
If you were in the session, thank you. If we met, thanks again. If not, I hope you’ll drop me a line, try one small piece of this playbook, and remember that leadership doesn’t always look like a commit; sometimes it’s the work no one sees, but everyone depends on.
AI is becoming standard in content workflows—but too often, it comes at the cost of data privacy, long-term ownership, and open standards. What if WordPress could help you do AI differently?
In this workshop, we’ll go hands-on with ClassifAI and local LLMs to explore how AI features can be built ethically and scalably—from alt text generation to semantic classification to content summarization. You’ll learn how to configure ClassifAI with a local model via Ollama or any compatible runner, using the new AI Services plugin developed by the WordPress Core AI Team.
We’ll walk through real-world use cases and show how teams can reduce third-party dependencies while speeding up editorial flow—especially useful for enterprise content teams, agencies, and hosts. You’ll leave with a working configuration (or clear path to one), plus a roadmap of how these tools are evolving across the WordPress ecosystem.
Bring your laptop and a local or staging WordPress site if you’d like to follow along. Whether you’re building for one site or 10,000, this workshop will help you make AI work for you—not the other way around.
If you missed the workshop or had troubles following along (sorry!), then below are my slides as well as a reference to the prerequisite setup steps to be prepared for the workshop.
With WordCamp US just around the corner, one might about any new Wapuu designs on company swag in Portland. A couple weeks ago on vacation with my family, I was walking the beach boardwalk with our kids and saw several Labubus being swung around or otherwise attached to kids’ slingbacks. My brain immediately went to “what would a mashup of a Wapuu and a Labubu look like?” and just as quickly started prompting ChatGPT with image generation requests to get an answer.
The 4o model did a pretty great job from my initial, simple boardwalk-based prompt of “Can you design a mashup of a Labubu and a Wapuu?” even nailing the mashup name of “Wabubu”:
Absolutely — just to clarify first: are you imagining this mashup as a character illustration, a 3D model, or something else (e.g. plush, toy concept, sticker art)?
Assuming you’re looking for a character design mashup between Labubu (the mischievous, spiky-toothed character from The Monsters series by POP MART) and Wapuu (the cuddly WordPress mascot), here’s an idea for the concept:
Labubu × Wapuu Mashup Design Concept
Name: Wabubu
Core Traits Blended:
Wapuu body shape: round, simple, chibi proportions, friendly pose
Labubu face: mischievous wide smile, prominent buck teeth, large ears, and wild hair
Wapuu accessories: hugging the WordPress logo (or an alternate WP-related item like a laptop, Gutenberg block, or code bracket)
Wapuu’s round face but with Labubu’s wide, toothy grin and pronounced front teeth
Big mischievous Labubu-style eyes (slightly tilted, giving a prankster vibe)
Fluffy tufts of Labubu’s wild hair, slightly unkempt, poking out behind ears
Long pointed ears, one flopped down playfully
Body:
Retain Wapuu’s soft, rounded body and paws holding the WordPress logo
Covered in soft fur with Labubu’s tiger-like stripes subtly hinted in the texture
Small tail – could be a hybrid of Wapuu’s squirrel-style and Labubu’s wilder brush tail
Color Palette:
Golden yellow fur base (like Wapuu), but with darker brown/orange accents from Labubu
Blue-and-white WordPress logo contrasts nicely for emphasis
Pose Ideas:
Cheeky grin, clutching the WordPress logo sideways like it just stole it
One paw giving a “peace” sign or tiny devil horns
Sitting on a stack of code books or on top of a WordPress admin dashboard
Would you like me to generate an image of this version of Wabubu for you? If you want it to look more cute or more punk/mischievous, I can adjust the balance accordingly. Just let me know!
The first two generated images, however, missed the mark:
Even asking ChatGPT to show me what it thought was a Wapuu and a Labubu in a basic “a plus b equals c” sort of image was a struggle to get the entire image within the output:
At that point it was obvious that ChatGPT wasn’t super clear on what a Labubu looked like and needed a lot more coaching to create a landscape image of the mashup creation. So I shared an image of the first Wapuu and Labubu image from a quick web search to better define the image generation request and that immediately yielded better results:
From there it was much better at hitting what I was looking for in the Wabubu mashup both in a friendlier Wapuu version and a mischievous Labubu version:
At this point I felt it had nailed the general concept and started asking it to create different image style variants based on quick prompt variations:
Wabubu 3D plush Labubu styleWabubu 3D plush Wapupu styleWabubu full character sheet for animations or merchWabubu Studio Gibli versionWabubu Japanese anime versionWabubu Bob Ross painting versionWabubu 80s hair band plus neon imagery styleWabubu spider verse style animationWabubu origami paper animal versionWabubu studio laika claymation styleWabubu black and white coloring book styleWabubu Tim Burton gothic styleWabubu pixel art / 16-but sprite sheetWabubu kawaii bento box styleWabubu y2k vaporware aestheticWabubu chibi styleWabubu low-poly 3D renderWabubu embroidery patch style
Ironically with all the fun I had peppering ChatGPT with image generation variations I hit the cap of my monthly plan limit of image generations (yes, there are some variants and generations that I didn’t include here because they were just _bad_).
So at this point, ahead of WCUS, I’m curious… which of these are your favorite Wabubu variant? Which would you want physical merch of? What other image variants would you create? Do you prefer the more friendly Wapuu or the more mischievous Labubu variants? Which style do you think would make an epic enamel pin, plush toy, or swag giveaway at WordCamp US? Let me know your pick, or suggest a new mashup idea!
As my friendly competition with Jonathan Desrosiers and Jeff Golenski in contributing photos to the WordPress Photo Directory in 2024 came to a wrap, I’ll note that I didn’t manage to get a recap post out monthly and my photo submissions definitely ebbed and flowed but overall I’m pleased to see a grand total of 136 photos contributed!
Following on from my August & September post, let’s take a look at my October, November, and December contributions to the Photo Directory. Before October, I had 113 photos accepted and as the month of September wrapped up that number has increased by 23 to 136 photos in the directory.
P.S. – this post’s featured image comes from Openverse in searching for “October November December” and is “Banksia recurvistylis” by Jean and Fred is licensed under CC BY 2.0.
Following on from my May, June, & July post, let’s take a look at my August and September contributions to the WordPress Photo Directory. Before August, I had 105 photos accepted and as the month of September wrapped up that number has increased by 8 (sigh, a couple slow months) to 113 photos in the directory.
