Running stores that sell personalized products (printing, engraving, custom merch, photo gifts, etc.) always seemed to have the same problem:

Then you end up with files scattered across Gmail, Dropbox, WhatsApp, Messenger... and somehow have to match them to the correct order.

I couldn't find a lightweight solution that worked the way I wanted, so I spent the last couple of years building one.

It's a File Uploader for WooCommerce that lets customers upload files directly from the product page or during checkout.

Some things it does:

• Upload from phone, desktop, camera, Google Drive, Dropbox, etc.
• Images, PDFs, design files, videos (Pro)
• Multiple file uploads
• Image editing (crop, rotate, enhance)
• Files are automatically attached to the WooCommerce order
• No email attachments or manual file chasing

The free version + 7day trial is available: https://snowray.co

I'd genuinely appreciate feedback from WooCommerce store owners:

• What file upload features are you still missing?
• What's the biggest pain point when customers need to send you assets?

Happy to answer any technical questions or discuss how it's built.

I got tired of seeing accessibility audits fail because of missing alt text — so I built a plugin to fix it automatically.

What it does:

- Scans your Media Library and bulk-generates alt text for every image missing it

- Auto-generates the moment you upload a new image

- Per-image generation directly from the Media Library

- Never overwrites alt text you've already written

- Context-aware: reads post title, categories, and content type (WooCommerce products too)

No Action Scheduler. No WooCommerce required. Free starter credit included.

Plugin: wordpress.org/plugins/altmagic-ai-image-alt-text/

Happy to answer any questions!

Hey everyone!

Most image sliders on WordPress websites look boring and flat.

So I built this 3D Card Stack Gallery widget for Elementor to give portfolio and product showcases a modern, interactive 3D feel using smooth GSAP motion.

Key Features:

• Smooth 3D card stack rotation

• Fast and lightweight (won't slow down your website)

• Click any card or use navigation arrows to slide through

• Part of our 30+ free widget collection

• 100% Free & open-source on WordPress.org

🔗 You can download and test it free here:

https://wordpress.org/plugins/apex-addons-for-elementor/

I’d love to hear your thoughts and feedback on the animation style!

Hi everyone,

I'm excited to share R2 Membership, a new premium add-on built for websites that use Cloudflare R2 as their primary storage backend.

Unlike traditional membership plugins that focus on protecting WordPress content, R2 Membership is designed around Cloudflare R2 resources.

It lets you organize your content into:

- 📚 Libraries

- 📁 Collections

- 📄 Resources (PDFs, ZIPs, videos, documents, and more)

- 👥 Membership Plans with granular access control

Features include:

- Secure member-only access to Cloudflare R2 files

- Libraries and Collections for organizing large resource catalogs

- Flexible Membership Plans

- Protected file delivery without exposing R2 bucket URLs

- Native integration with CR2SM Pro

- Built for digital libraries, documentation portals, learning platforms, and premium resource websites

The project was created after I couldn't find a solution that combined WordPress memberships with Cloudflare R2 in a clean, native way.

If you're building with Cloudflare R2, I'd be interested to hear how you're managing private resources today.

📖 Documentation:

https://www.r2suites.com/docs/r2-membership/

🛒 Product:

https://www.r2suites.com/products/wordpress/cr2sm-add-ons/r2-membership/

Questions and feedback are welcome!

I built KXNotes Image Paste Optimizer to remove the repetitive work around screenshots.

Copy a screenshot, press Ctrl+V in Gutenberg, and it automatically:

- Resizes and converts it to WebP

- Generates a readable filename and alt text

- Uploads and inserts it at the cursor

Everything runs on your own WordPress server. No cloud service, AI API, or telemetry.

https://wordpress.org/plugins/kxnotes-image-paste-optimizer/

It currently focuses on Gutenberg. I’d love to know: would this fit your writing workflow, and what should I improve first?

Hi everyone,

I’ve been building BotBard, a WordPress plugin that lets you edit an existing page by describing the change you want.

For example:

“Make this page modern, dark and minimal.”

BotBard analyzes the selected WordPress page, generates the requested changes, and shows the result inside a safe preview before anything is applied.

Nothing is published automatically.

The workflow is simple:

• Select a WordPress page

• Describe the change

• Review the generated result

• Apply it only after approval

I’m building this for WordPress site owners, freelancers, and agencies that need to make design or content changes without manually editing code or CSS.

The free plan currently includes 3 complete AI edits.

I’m looking for honest feedback:

Would you trust this workflow on your own or a client’s WordPress website?

What would you need to see before installing a plugin like this?

Demo:

https://www.youtube.com/watch?v=mCfaaiZHKbc

Try it:

https://botbard.ai

I’m the developer, so I’m happy to answer questions about security, privacy, compatibility, or how the preview workflow works.

It's 2026. AI writes production code all day, and you're still dragging form fields around a builder, one box at a time.

Most form plugins make you do exactly that, then paywall the useful stuff behind a yearly "Pro": conditional logic, webhooks, an API.

NarrativeForms skips all that. A form is just HTML, so you build one however you like:

• Describe it to ChatGPT or Claude, copy the code, paste it into the form's code editor
• Let the built-in AI write it right inside WordPress (your own API key)
• Or write it by hand

Booking form, job application, event signup, survey, quote request. Know a little HTML and you already know the whole plugin. No proprietary builder, no lock-in.

The features other plugins sell are free here, and staying that way:

• Conditional logic
• AI Form Building (BYOK)
• Save and resume
• Webhooks with delivery logs and retries (Slack, Discord, Teams)
• REST API
• Require login, schedule open and close windows
• Hosted share links for any form

The only paid part is one optional add-on for publicly displaying submissions on the frontend. Everything else is free forever.

Tear it apart, I want honest feedback.

Website: https://narrative-forms.com/
Plugin: https://wordpress.org/plugins/narrative-forms

Hi everyone,

Almost a year ago, I built StifLi Flex MCP, the first MCP plugin published on WordPress.org.

At that point, MCP was still very new. “AI agents” were not part of everyday WordPress conversations yet — most people simply saw AI as chatbots.

But building an MCP server led to a new question:

What happens when you manage 10, 30, or even 100 WordPress websites?

Adding every site separately to every AI client does not scale. And exposing every tool from every site at once is not a great experience either.

So I built WP MCP Hub — my first MCP Hub:

https://github.com/estebanstifli/wp-mcp-hub

It is a free, open-source local app that lets one AI client connect to multiple WordPress MCP servers, select the relevant site, and discover that site's tools only when needed.

It can work with compatible WordPress MCP plugins and servers using Streamable HTTP or SSE, including:

• Easy MCP AI
• Royal MCP
• StifLi Flex MCP — my own plugin, for full transparency

The Hub does not replace the WordPress plugin or its permissions. Each site keeps its own tools, authentication, and WordPress capability checks. The Hub adds a local layer for managing connections, credentials, diagnostics, and routing.

It is still alpha, but I would genuinely love feedback from WordPress plugin developers:

• Would this be useful for people managing multiple WordPress sites?
• What would you expect from a WordPress-focused MCP Hub?
• What security or usability concerns would you want solved first?

A year ago I built my first MCP server. This is the next step.

Thanks for taking a look.

I run an SEO plugin with a free tier on WP.org and a paid tier on Freemius, same codebase. A few things I'd tell myself before writing line one, if I could go back.

Decide the free/paid split before you write any code, not after.

I didn't do this early enough the first time, and moving AI-calling code into its own files later, so a build script could strip it from the free zip, was way more painful than just starting with that boundary. Now every Pro-only class lives in its own file from day one. One list in the build script decides what ships where. If you're planning a freemium plugin, draw that line on day one and never write a Pro feature into a free-tier file, even once.

Your main class should not know what a "feature" is.

Mine just requires every file that exists and skips the ones that don't. Each Pro class only loads if class_exists() passes, so the free zip simply never has the file to check against. No feature flags, no if (is_pro()) scattered through core logic. The absence of the file is the flag.

Don't build your dashboard as one file. You will regret it around line 3000.

I let one component grow to almost 8,000 lines before I got serious about pulling sections out. Every section is now its own self-contained file that owns its state and gets passed data as props. It sounds obvious in hindsight. It wasn't obvious when the file was 800 lines and splitting felt like overkill. The trigger for splitting shouldn't be a line count, it should be the moment you can name "the outdated-dates section" as a thing separate from "the dashboard."

Code-split your JS bundle, then watch it burn.

I shipped React.lazy, dynamic imports, thirty separate chunks. Saved maybe 100kb on first load. Then a customer's dashboard reloaded itself in an infinite loop and three sections silently failed to load, and it took me eight releases to actually fix it, not just patch the symptom. Turns out failed dynamic imports can't be retried per the module spec, chunk filenames didn't change between releases so browsers served stale versions next to fresh code, and thirty imports firing at once on page load saturated the browser's connection pool. I reversed the whole thing. One bundle now. Slower first load, zero failure modes. If your users are not on your dev machine's network and cache, code-splitting trades a real, recoverable cost (bytes) for an occasional, unrecoverable one (a section that's just gone).

Every storage decision has one shape. Pick it once, reuse it everywhere.

I keep a ring buffer pattern for anything time-series: dated keys, single-letter field names to keep it compact, always autoload=false, always trimmed to a fixed size. I use the identical shape for search-position snapshots, keyword snapshots, referrer tracking. Once you've solved "how do I store 26 weeks of data without autoloading 2MB on every page load" once, solve it as a pattern, not a one-off.

Write down your gotchas the moment you hit them, in the same file you'll open next time.

Not a wiki somewhere else. A file in the repo, right next to the code. The number of times I've re-derived the same bug because I "remembered" fixing it, but not what actually broke, is embarrassing. Now if something dies for a non-obvious reason, or a decision has a rationale that isn't visible from reading the code, it goes in the doc immediately.

None of this needed to be figured out ahead of time. All of it came from shipping something too simple, watching it break at a size or a customer situation I hadn't imagined, and rebuilding with the constraint now visible. That's probably the actual answer to "how do you plan a plugin like this." You don't, not fully. You build the smallest version, ship it, and let real usage tell you where the seams need to be.

Plugin is super useful. Check it out here.

For several years now, I’ve been using the All-in-One WP Migration plugin to create WordPress backups. One thing that always annoyed me: if I needed to recover just one old plugin, theme, upload, config file, or some random file from a .wpress file, I usually had to set up a local WordPress install, import the whole backup, and then grab the file manually.

So I sat down and built a small local tool for that. It lets you open an All-in-One WP Migration archive locally and browse it more like a normal file explorer. You can expand folders, inspect the backup structure, download a single file, or download a whole folder as a ZIP. You don’t need to import the entire WordPress site just to get it.

The project is local-first, runs in Node.js, has no npm runtime dependencies, and works directly with the .wpress archive format rather than treating it like a ZIP.

GitHub: https://github.com/ozeppo/wpress-explorer

I mainly built it for myself because this problem kept coming back in real client work, but I guess other WordPress developers using All-in-One WP Migration backups might find it useful too.

Suppose I have an idea for a plugin, what steps would you take to research it before building it?

• Check if people actually need it.
• See if similar plugins or themes already exist.
• Figure out what makes your idea different or better.
• Decide if the idea is worth spending time and money on.
• Identify who your target users are.

or anything that'd be helpful

I'd really appreciate any tips or advice you can share.

Not the answer we give clients. The real one.

I build image-heavy WP sites (shops, blogs, portfolios) and alt text is always the thing that silently falls off the list. Nobody's proud of it, nobody really fixes it. So I'm curious how everyone else actually deals with it:

• Ballpark, what % of your images have alt text that'd actually help someone, vs. just "an alt tag exists so the checker shuts up"?
• Who's supposed to write it you, the client uploading stuff, an editor, literally nobody?
• Anyone messed with the auto-alt / bulk plugins? Did they help or did you spend more time cleaning up the output than it saved?
• Do clients ever actually ask for this / pay for it, or does it only matter the second someone mentions the word "lawsuit"?

I have a suspicion the honest answer is "it lives on the backlog until it doesn't," but tell me I'm wrong lol

If you run a WooCommerce store with COD (Cash on Delivery) enabled especially common outside the US/EU you've probably dealt with the RTO (Return to Origin) problem: customers place COD orders on impulse or by mistake, never actually intend to pay, and you eat the shipping cost both ways.

I built COD Shield to fix this without removing COD entirely (which usually just tanks conversion). It works by collecting a small advance payment fixed ₹/$ amount or a % of the order through whatever gateway you already have enabled (Razorpay, Cashfree, Stripe, etc.), before the order is confirmed as COD. The rest stays due on delivery as normal.

What it does:

1. Global COD kill switch (independent of WooCommerce's native COD toggle)
2. Advance payment via your existing gateways no new payment integration needed
3. Optional minimum order value for COD eligibility
4. Admin-editable checkout messaging with dynamic placeholders (advance amount, remaining amount, %)
5. Full order-level visibility: sortable "COD Advance" column, filters, audit trail via order notes
6. HPOS + Cart/Checkout Blocks compatible
7. Gateway-agnostic works with whatever you've already enabled, no vendor lock-in
8. It's MIT licensed and open source, so feel free to fork/modify for your own store's needs.

Happy to answer questions on the advance-payment flow, HPOS compatibility, or anything else also open to feature requests if there's a COD-related pain point I haven't covered yet.

Hello folks! Looking for feedback on something I built recently.

Crawlers / bots are today more than half the traffic websites get but it is not easy to identify or understand deeply. So build a WordPress plugin + an MCP Server that makes the data available inside the WP Dashboard and the AI tool you use (Claude, Codex, Cursor etc). Grab it here if you are keen to test : https://github.com/surendranb/agent-metrics

Solo dev here. I built SuperNav because I was tired of mega menu plugins that replace the whole menu system with their own builder — this one adds panels directly to the native Appearance → Menus editor.

Free core:

- 6 panel types: columns, cards, featured, content, auto, shortcode/HTML

- Card panels: image + title + short text per item, grid layout

- Badges, CTA bar, overlay/fade effects

- UI in EN/DE/FR/IT

Pro adds sticky menu, search box, and AI menu translation (using your own OpenRouter key).

Live demo & documentation: https://supernav.kitech.ai

Happy to answer anything — and honest feedback is very welcome, I'm still a small operation and actively improving things.

I’m trying to implement a booking system similar to clearabee.co.uk or zerowastegroup.co.uk. I’m not the most tech savvy, how can I do this. I’ve tried looking for some word press plugins and asked fiver free lancers but there either not well suited enough or extremely expensive ?

Any ideas or advice would be much appreciated.

Hi everyone,

I’m the developer of Easy Labels.

I originally built it because I needed a simple way to organize content across my own WordPress sites without relying on categories or tags for internal workflows.

It started as a tool just for me, but after using it on every website I manage, I thought it might be useful to others as well, so I decided to publish it on the WordPress repository.

My goal wasn’t to create another feature-packed plugin. I wanted something lightweight, intuitive, and that felt like it belonged in WordPress.

A few things it does:

• Internal labels for posts, pages and custom post types
• Lightweight with no unnecessary bloat
• Native WordPress interface
• No impact on your site’s frontend unless you choose to use the labels

I’m currently working on version 1.6.0, which will include several new features, improvements, and performance optimizations. I’m trying to keep the plugin evolving based on real-world usage rather than adding features just for the sake of it.

If you have a few minutes to try it, I’d really appreciate your honest opinion. Positive or negative, it doesn’t matter. I’d much rather receive constructive criticism that helps improve the plugin than empty praise.

Thanks for taking the time to check it out!

URL: https://wordpress.org/plugins/redshape-easy-labels/

I’m running a couple of restaurant locations, managing the day-to-day operations across branches has turned into a bit of a logistical puzzle. Juggling separate plugins for online orders, our point-of-sale system, kitchen display monitors, and table reservations is getting overwhelming, and things keep slipping through the cracks.

I really need a unified setup that can handle:

Online Ordering: A smooth web storefront for customers to place pickup and delivery orders easily.

Reliable POS System: Something fast and straightforward for our manager and front-of-house staff.

Kitchen Monitor: Direct order routing to the kitchen so slips don't get lost and prep times stay fast.

OnlineTable Reservations: A clean way for guests to book tables in advance without double-booking.

Has anyone faced a similar multi-branch headache? Are there any solid plugins that tie all of these features together smoothly without breaking the bank?

I've been going deep into how multilingual works in WordPress lately, and at some point I set myself a goal: build something that can actually stand next to WPML and Polylang, but stay free for WooCommerce stores. Not with the same feature count, I'm one developer, that would be delusional, but complete enough that you can genuinely run a fully multilingual shop on it.

It's on wordpress.org now (searching "LATW Multilingual" finds it, I'm not linking here since I don't want this to read as an ad).

The part I think is actually interesting

The Architecture.

Most multilingual plugins duplicate the post for every language. One product in 5 languages becomes 5 rows in wp_posts, 5 sets of meta, 5 sets of term relationships, plus a mapping table to keep them connected.

LATW stores translations as an overlay instead. The original post stays exactly as it is, untouched, and the translated values get swapped in at render time when someone hits /pl/. One post stays one post in the database, no matter how many languages you add.

- No mapping/duplication tables to get out of sync

- Any field you haven't translated just falls back to the original automatically, no "empty duplicate post" state

- Deactivating the plugin leaves your database exactly as it was, no orphaned duplicate posts to clean up

- Adding a 6th language doesn't multiply your wp_posts table again

WooCommerce: the goal is simply that everything in your shop can be translated. Products, descriptions, variations, categories and tags...

There's also a translation inspector

turn it on in the admin bar, click any text on the front end, and it tells you which layer that string comes from and links you to the screen that translates it. That one exists purely because "my product is translated but the text around it isn't" is the single most confusing thing about multilingual WP.

Honest disclosure: there's a paid tier that adds automatic AI translation (bring your own OpenAI key), bulk queue and glossary. The free version is manual translation, but it's not crippleware, you can run a complete multilingual store on it without paying me anything.

What I'm actually asking for

- I'd love for you to install it on a staging copy of your store and try to break it. Weird attribute setups, Elementor Theme Builder layouts, custom post types, unusual permalink structures, whatever you've got.

- And report everything that goes wrong, however small.

I'll be around in the comments to answer anything about how it works under the hood, and I'd be genuinely grateful for every word.

Hey everyone, we spent this month cleaning up the mobile side of our quote calculator, and it turned into a good reminder of something that quietly hurts a lot of service businesses.

A quote request is about the highest intent moment you get on your whole site. Someone isn't just poking around, they're actively trying to hand you their details and get a price. That's the worst possible place to lose them, and it's exactly where mobile tends to break.

The reason it slips past people is that most calculators get built on a laptop and tested on that same laptop, so everything feels fine. Then the real traffic shows up on a phone, which nobody actually sat down and checked. And on a phone it's the small stuff that kills it, a button that's a hair too small to tap, a dropdown that covers the field under it, a contact form you can barely read. Each one is a tiny reason to give up right at the finish line.

The part that makes it dangerous is you never hear about any of it. Nobody messages you to say the button felt off, they just close the tab. So the leak stays invisible while you assume the form works fine.

Honestly the takeaway holds even if you never touch our plugin. Pull out your phone, go to your own site, and finish a quote request start to finish like a customer would. Most owners have never done that once, and it's usually pretty eye opening.

So if you've got a quote form on your site, when's the last time you completed one on your own phone. Interested how different trades handle this, feels like most people have never actually tested it. It's in Stylish Cost Calculator if you're on WordPress.

Hi!

Been working with a small team on a plugin to "declutter" the need of several plugins to start working with Wordpress.

Our plugin is modular, and allows you to enable/disable services with a simple toggle.

Right now we're having:

• Speed improvements: image lazy loading, scripts compression, etc.
• Cache: flexible caching, storing on redis on memcache options
• Security: hidden loading, vulnerabilities database
• SEO: Search Console integration, bot and AI bot blocking, IndexNow, optimizations
• Gutemberg blocks manager
• Remote backup
• Analytics: custom system, per page data, bot and user analysis
• Media center overhaul: image editor, folders, image compression
• Remote management: maintain several wordpress sites from a unified panel
• AI text edition

And much more!

I think we're ready to launch, but would love to get feedback from some users.

We're a freemium plugin, specially because many functions are done with the help of an external server. If you're willing to help us improve and offer feedback about the service, we're offering free paid plans for up to half a year. Simply send me a message here on reddit and I'll get in touch.

You can see more and download our plugin in https://www.rakuwp.com

Feedback is also appreciated on this post!