Version 1.0 - Tasks to accomplish and Problems to solve

jeremyzahner commented 8 years ago

This issue should serve as a roadmap to version 1.0.

Functionality

TBD

Problems

TBD

Documentation

[ ] New - #115 - Publishing to the wordpress.org plugin directory (Related: #116 / #99 / #80 )

renaudham commented 8 years ago

Hi. What is the staus for the V1.0

it seems nobody is working on it anymore. Anyway it seems relatively stable to be used for real life projects, from all my test.

Is there a milestones plan for evolutions/fix to do in case my team would want to contribute?

Thanks

jeremyzahner commented 8 years ago

@renaudham You are most welcome on making proposals on what we should add/include to a possible first stable release.

renaudham commented 8 years ago

Hi Jeremy

Great. Thanks

I'm currenlty working on a big complex plugin using Herbert. Just started for a Setting and an API Ajax page.. I will show more later, going slowly, when we have free time.

How can I add a list of ideas/Suggestions here, where is the best place to avoid to overload this current page? Or a Google Doc link...?

Some quick notes, and in the future I will propose a real list... 👍

I already see some things missing and I'm adding some myself (with my team also)to Herbert, but currenlty of course now not in the Core folder but in the app/ressources folders,

like for example: -some class that can directly add/update/edit WP options, with simple methods.. (my current code is not very clean for this.. I can show in future, not sure its the best solution for this at all) -A class about Users manipulation shortcuts, like for example directly adding a simple method to check if a user is authorized to aces to a method in an API Front endpoint called by Ajax..

and many others, some related to simplifying interaction with WP core environment, some about extending the part fully out of WP, more around some kinds of common elements that are relatively base, and exist in Laravel/Symfony.

I will not list more now but I think Herbert is a VERY good basis and that it deserve to be increased. And from now on we stop our past 2 years way to add Laravel in WP and we will focus to set up more elments aroud GetHerbeet for our projects.

just FYI, An example of a project we started 2 years ago, mixing Laravel and WP, it was working but really not merged as you do, both are fully separated and independant except Users management. Far from as integrated as you did.. http://english.carticipe.com/

getherbert / herbert