search

Getbeans / Beans

Beans WordPress Theme Framework. The default branch is set to development, please switch to the master branch for production.
https://www.getbeans.io
Other
391 stars 61 forks source link

Consider WordPress.org Submission #61

Open hellofromtonya opened 6 years ago

hellofromtonya commented 6 years ago

Should we submit to WordPress.org? @ThierryA did submit previously, see ticket #30094.

I'm opening this issue as a discussion thread, i.e. to consider, discuss, and, if we agree to re-submit, plan the approach.

bphippen commented 6 years ago

First of all thanks Tonya, for helping out on Beans, it is by FAR my favorite theme framework and it would've been a shame to let it die a slow death...

Anyways after reading the ticket, it seems like the reviewers don't quite see it as a "finished" theme and would require things like the Compiler to be a separate plugin.

In my opinion, Beans is built for devs and the only benefit to being in WP.org, to me, are auto-updates. But that can be handled outside .org anyways.

I think with some TLC, Beans could become the next Genesis and they have done fine without .org

So my vote is no, it's probably not worth the effort.

hellofromtonya commented 6 years ago

@bphippen Excited to be here and help Beans grow.

I thank you for your insights and vote!!

I think the issue primary issue with submitting to WordPress.org is the review team and how they approach the review process. The scope is very narrow. A framework, especially a smart, advanced, and innovative framework, just doesn't fit within their criteria.

There has been talk about pulling the API out of the theme as a separate plugin. It's something we are thinking about and analyzing. If that happened, then maybe submitting would be beneficial.

Submission comes with risks and overhead. For example, we then have support in 2 places. That can be a burden on the team.

There are benefits to be there such as the updater, protecting the Beans brand (so no one else submits a theme with the name "Beans" which not Beans-powered), marketing, exposure, etc.

The key for us to weighing out pros and cons. As Beans is today, it would not be accepted.

That's why we opened this issue, i.e. to ensure it stays in front of us for discussion.

bphippen commented 6 years ago

Great points! If it were up to me, I would focus on making Beans the ultimate theme framework for WordPress Devs, and I'm not sure WP.org would be the best place for a theme like that. Beans main competition is Underscores, Genesis Framework, and Roots. So my thinking is: How can Beans become the de facto starter framework for WordPress devs?

Either way though, I'm on board and dedicated to being an ambassador for Beans!

christophherr commented 6 years ago

@hellofromtonya I'm not sure how this applies to a "parent theme / framework" but there is a new-ish "rule" that wp.org will not accept theme names that would have a certain amount of active installs from the get go (to prevent gaming the featured theme system) .