Hi Romain,
Without sounding like a douche myself, I feel that you need to take some time to understand the use of Beans, as well as have a fundemental understanding of the WordPress theme structure.
Beans does not (necessarily) change the way you create templates for various aspects of WordPress (page templates, pages, taxonomies, post types etc). It also does not pose limitations and does not enforce a "beans" approach, it merely gives you the tools to use shoudl you WANT the power of Beans.
Once you understand tha basic markup functions and actions / hooks (read the Beans docs) you will quickly see that using Beans becomes exceptionally easy and flexible.
I am all for helping you, but I feel you need to put more effort into reading and applying core Beans concepts.
What particular aspect of Beans do you feel that you need more guidance on?
Simon
Mmmh okay, currently I use the bones theme so I'm not really familiar with framework and child themes.
So the beans framework theme is like a "super theme" wich every themes should implements ? Should I extends it ? Or duplicate it and add my own template ? And after my child themes could implement it ?
Or all I have to do is develope like I did before but just using beans_open/close_markup instead of html tag, so I could use beans_*_action on it in child themes ?
I have read the 3 child themes code but they only modify beans theme, it's not really instructive for building a theme as there is not new templates.
I will continue to learn about it cause I like the way all markup can be hooked and not just some action defined by the framework (I hope I use the good terms^^)
Romain
Edit : ok I guess I get it 🙂
Edit 2 : I had just misunderstood this sentence in template doc : In Beans, overwriting page templates isn’t typically necessary since it can be done directly in the child theme functions.php.
I thought we had not to create new template :/