The latest Beans framework update was in the fall of 2018. There is no lead person and support in guiding Beans forward.
I would suggest that you find another speedy framework to go with instead. Please add suggestions to another framework as well as reasons why you would use it.
NB! Another option would be to let us know that you would like to contribute to the forward movement of Beans.
actualy there sud be a video tutorial for beans for starters. I am ready work on it but conufusing on making index of Topics to cover.
That sounds good Tasz! I have lots of tutorials here: https://wpbeansframework.com/ You can look through and get an idea of various topics that would be good to cover.
Btw these days with Gutenberg it would be good to experiment with how to improve Beans to work better with Gutenberg.
No more updates?? o_O Is this the end of Beans? 🙁
i have experimented a new way better then gutenberg. I mixed Yootheme premium theme Features in beans theme. and its page builder was working perfectly in beans. You can see how it works. https://yootheme.com/blog/2016/10/05/yootheme-pro-page-builder
But there was some conflict on uikit 2 and uikit 3. I think Let me first develop a child theme which support uikit 3
I think I switch to Astra
@christian_weller: The original project leads for the Beans Framework have moved onto other work and are no longer available to lead the project. No one with their skill set has stepped forward to assume leadership. One co-maintainer, Tonya Mork is working with the Genesis Framework, which is now owned and supported by WordPress host WP Engine. Look for elements of the Beans Framework to be incorporated into Genesis.
An update was made by Thierry Muller in the #general channel on Slack.
Thierry Muller [3:46 PM] Saturday 27th of April. Hi @channel, first of all I would like to thank everybody for creating a small but amazing community around Beans. Over the year, other frameworks have stepped up massively, specifically the very promising upcoming 3.0 version of Genesis. While Beans has been waaayyyy ahead of the game for many years, even more so as Genesis was heavily loosing momentum at the time it was created, I believe it is no longer justified to have two similar frameworks growing on their side and trust that Genesis will have a long life now that it has been acquired by WP Engine. After giving it a lot of thoughts, I think it is time for Beans to RIP. So what is next?
- Creating a landing page on Beans site to make it official (with a link to the old site initially)
- Making it official on the Github repo (keep it available though)
- Advising Beans users to move on to Genesis (my preferred choice) You really can’t live without it? Beans will remain available for Download
More information at https://getbeans.slack.com
Thank you Robert and Paal... but this is really bad news!
Beans was the only reason for me to jump on Wordpress. I simply love the Beans particularity concept with Beans IDs. I love it to delete, replace or move any element with a single line of update safe php code. I love the modular integration of uikit, the LESS integration, the consolidation of all assets in one file, the image API and all those nice other little, sophisticated code ingredients that helps me building websites with the main foucus on SEO. Google Pagespeed is one of the most important indicators for quality code. And Beans has alway given me quality code out of the box with no efforts and it's fast as a shark wihtout any caching plugins!
The last days I have checked a lot of Genesis themes and I havent found a single one that has even come close to what I expect codewise!
https://www.studiopress.com/ is proclaiming a SEO friendly framework...with a mobile google-pagespeed of 23?!? Seriously? Are you kidding me??? This is why I'm not even inclined to have a closer look to Genesis so far! I really don't want to work with a framework that lets me drag and drop design elements but has to be pimped with tons of plugins (amp plugin!?).
When will Genesis 3 be published? Which Beans elements will be incorporated? I wouldn't hesitate a second to pay for a framework, that incorporates the Beans concept.
Beans is now being maintained. I'll be working on fixes for the 1.6 branch - focusing on submitted issues listed in github and Gutenberg.
Please feel free to discuss anythinig with me via Slack, this message board. I am open to suggestions and any help.
I was lucky enough to discover Beans a year ago.
Has made me an "WordPress Expert", because it covers almost any part of WordPress like Fields, Customizer, Post Meta, Term Meta, Options, Markup, Hooks, Compiler, Images etc...
It's sad to hear other frameworks that does not offer as half as Beans offers to have more users base. I made a list of what I think could improve on Beans to be ahead of other frameworks:
- Support Gutenberg
- Support other Page builders
- Maybe new fields like font list
- Pre made sanitization methods
- Sanitization for default fields
- Options values to be saved together in Database
- Use Uikit to design, not metaboxes in Option Page
- Upgrade to UiKit 3, Modern, lightweight, and most important no jQuery
- Less heavy Widgets API, there is a way to achieve what this does using build-in hooks.
- Less heavy Actions API there is a way to achieve what most this does using filters.
- Put API on Classes, calling
Beans_Markup::open()is better than
beans_open_markup()as i know that the method that i am calling is from Markup API
- Maybe change a little the structure and how templates are rendered
- Maybe Compiler API is not necessary as new HTTP/2 may change things
- Image API to regenerate images on backend or maybe removed completely
Hey Joseph B,
I agree - finding beans has helped my development as well.
I'm close to finishing the simple Gutenberg related issues and hope to push them to the repo ASAP. Should you find any issues related to Gutenberg not mentioned in the issues kindly add them.
The "Pre made sanitization methods" - do you have any specific suggestions here?