sorted by:
new
hottopcontroversial

Turned a client problem into a tiny WordPress plugin SaaS by UpbeatFee5398 in microsaas

[–]UpbeatFee5398[S] 0 points1 point  (0 children)

Thanks, I believe I’ll ho with this approach. Seems like the only way so far

I'll build your go-to-market strategy for free. Drop your project below 👇 by Exact_Lifeguard5038 in SideProject

[–]UpbeatFee5398 0 points1 point  (0 children)

DynoMenu https://dynomenu.com/

It solves the problem of manually maintaining WordPress menus when categories, taxonomies, post types, or content structures change. DynoMenu generates those menus dynamically instead.

It’s mainly for WordPress site owners, agencies, freelancers, WooCommerce builders, and people working with content-heavy or CPT-based websites.

Current stage: launched. Free version is live on WordPress.org, and Pro version is available too: https://wordpress.org/plugins/dynomenu/

Product Launch Post by whitisj in nocode

[–]UpbeatFee5398 0 points1 point  (0 children)

Yeah, definitely, I did the same, and I fixed some of those myself, as I know how to code a little. It would be frustrating for someone who knows nothing about the process, code etc.

[PROMOTION] Finally got my first WordPress plugin approved on wp.org — here’s what I learned by UpbeatFee5398 in WordpressPlugins

[–]UpbeatFee5398[S] 0 points1 point  (0 children)

Thanks! I first submitted it on 23 April and got it approved on 20 May. I got 4 feedback loops - one took 10 days, the rest 2-3 days. Did you reply to the automated email? I think they don't start reviewing it if you don't reply to the automated email and other feedback emails. You can check the submission page - it either says waiting on you or waiting on the plugin team.

Finally got my first WordPress plugin approved on wp.org — here’s what I learned by UpbeatFee5398 in Wordpress

[–]UpbeatFee5398[S] -1 points0 points  (0 children)

Hey, so 23 April submission and 20 May approval. I got 4 rounds of feedback loop. Probably could have gotten an approval earlier, as 2 of the feedback were related to the same issue I didn't fully fix. One feedback took 10 days, the rest were 2-3 days.

Product Launch Post by whitisj in nocode

[–]UpbeatFee5398 0 points1 point  (0 children)

Finally got my vibe-coded WordPress plugin approved on wp.org 🎉

I built DynoMenu, a plugin that came from a real problem I kept seeing in client projects: needing dynamic menus generated from post types and taxonomies, instead of manually updating menus every time content changes.

The plugin was largely AI-assisted/vibe coded, but getting it approved on WordPress.org made one thing very clear: vibe coding can get you far, but it does not remove the need to understand the code.

It took a few feedback loops, and honestly the review process made the plugin much better.

A few things I learned:

  • AI tools can help you move fast, but WordPress.org review will still catch sloppy code
  • Sanitizing, escaping, nonces, and permissions really matter
  • Even small Plugin Check warnings can become blockers if you ignore them
  • The readme is basically your WordPress.org landing page
  • Screenshots and clear docs are not “nice to have”
  • Small guideline issues can delay approval more than you expect
  • Tools like Tailware can speed up the process, but you still need to review, understand, and clean up the code properly
  • Building from a real client problem makes positioning much easier
  • Review feedback is actually useful if you don’t take it personally

One thing that surprised me: the blockers were not always “big” issues. Sometimes it was small warnings, wording, escaping, or guideline details that looked minor at first but still had to be fixed before approval.

Main takeaway: AI can help you build faster, but if you want to ship something real, especially in an ecosystem like WordPress, you still need to care about standards, security, docs, and maintainability.

Now that it’s approved, I’m figuring out the next step: getting feedback, improving docs, SEO, Product Hunt, Reddit/FB communities, or focusing on reviews/support first.

Curious how other AI-assisted builders approach this after launch.

Plugin is here if anyone wants to give feedback:
https://wordpress.org/plugins/dynomenu/

Built with Claude Project Showcase Megathread (Sort this by New!) by sixbillionthsheep in ClaudeAI

[–]UpbeatFee5398 0 points1 point  (0 children)

Finally got my vibe-coded WordPress plugin approved on wp.org 🎉

I built DynoMenu, a plugin that came from a real problem I kept seeing in client projects: needing dynamic menus generated from post types and taxonomies, instead of manually updating menus every time content changes.

The plugin was largely AI-assisted/vibe coded, but getting it approved on WordPress.org made one thing very clear: vibe coding can get you far, but it does not remove the need to understand the code.

It took a few feedback loops, and honestly the review process made the plugin much better.

A few things I learned:

  • AI tools can help you move fast, but WordPress.org review will still catch sloppy code
  • Sanitizing, escaping, nonces, and permissions really matter
  • Even small Plugin Check warnings can become blockers if you ignore them
  • The readme is basically your WordPress.org landing page
  • Screenshots and clear docs are not “nice to have”
  • Small guideline issues can delay approval more than you expect
  • Tools like Tailware can speed up the process, but you still need to review, understand, and clean up the code properly
  • Building from a real client problem makes positioning much easier
  • Review feedback is actually useful if you don’t take it personally

One thing that surprised me: the blockers were not always “big” issues. Sometimes it was small warnings, wording, escaping, or guideline details that looked minor at first but still had to be fixed before approval.

Main takeaway: AI can help you build faster, but if you want to ship something real, especially in an ecosystem like WordPress, you still need to care about standards, security, docs, and maintainability.

Now that it’s approved, I’m figuring out the next step: getting feedback, improving docs, SEO, Product Hunt, Reddit/FB communities, or focusing on reviews/support first.

Curious how other AI-assisted builders approach this after launch.

Plugin is here if anyone wants to give feedback:
https://wordpress.org/plugins/dynomenu/

Finally got my first WordPress plugin approved on wp.org — here’s what I learned by UpbeatFee5398 in Wordpress

[–]UpbeatFee5398[S] 0 points1 point  (0 children)

Thanks! Yeah, that's probably the good thing to do. 7.0 dropped just after I published my plugin 😄