The Frontity Framework is not under active development anymore. We have shared more details about this decision in this blog post.
This means that pull requests and issues are not being actively reviewed and bugs are not guaranteed to be fixed. There has been some interest from the community in continuing the project so if you are interested in becoming a maintainer and continuing the development of the framework please do let us know in this thread!
Thanks!
Hi Michal, two friends of mine and I want to start using Frontity for our projects and we are thinking about contributing to the project, how could we get started?
I think the best first step would be to actually use the framework for a project and get a bit more familiar with it!
We don’t have a clear process for nominating new maintainers at this point but in general we’re looking for people who have some familiarity with the codebase as well as an incentive in seeing Frontity continue.
If you are looking to be a contributor rather than a maintainer, I’m afraid nobody is actively working reviewing pull requests right now so it’s a bit difficult to contribute until someone can step forward to take over the maintenance.
I understand, before this I was talking with my friends and we see that there are many things optimized to work with React and WordPress with Frontity and therefore we would like to be maintainers regarding updates with React and how to work, we see this as a great contribution to the projects that are already done with Frontity and for us to be aware of updates and improvements that have in React and WordPress. We will use the framework in a first project and study it in depth to understand more about the code and be able to maintain it over time.
What a big F… you to all the people and companies that built on this framework.
The end of an era…
Frontity was built on the open-source guarantee:
Open source software guarantees the right to access and modify the source code, and to use, reuse and redistribute the software, all with no royalty or other costs.
That means that all the time and effort we put into it is yours, free of charge, and forever.
If you like the project and want to see it go on, please start contributing yourself, convince your company to contribute or search for sponsorships so others can contribute 
@orballo has been contributing lately to the framework with important features. I’m still reviewing, merging and releasing features for people willing to contribute:
Finally, if you want to understand why we decided to start working on Gutenberg itself, I invite you to see Pablo’s talk at the last WordCamp Europe to understand our vision, even if you don’t agree with it.
I want to be part of the development and maintenance of this wonderful framework.
The solution that I would sugget to maintain this Framework is as follows:
I know that Frontity team will now work with Automatic to build Gutenberg features, but we cant let this Frontity framework die.
This is an Open Source project and if development to this fraemwork is not done then many people will loose trust in Open Source, coz they will think every framework will not be maintained after few time.
Anyone who agrees with me and wants to work on this project then mail me: appevolver2022@gmail.com
The problem with Frontity is, it should really just be a custom hook useWordpress() no need for it to be a Framework. That way it would be more successfully and people can integrate WordPress as a backend in any React Framework they want like (next, remix, vite/cra, astro, gatsby).
This doesnt make sense.
There are people who want to use Wordpress as headless CMS. What those people will do?
Wordpress as CMS is feature packed and having Headless CMS allows to use much better use of Wordpress API’s.
I know we can directly setup next, react, gatsby and start with development, but this will be time consuming process.
Advantage of headless CMS is that we get SPA (Single Page Application) which is much faster and you cannot get this functionality with Wordpress as Wordpress is built on PHP.
Any1 interested in starting Frontity development with me then have discussion with me on Google Chat. Email: appevolver2022@gmail.com
We can contribute on this project or we can built new framework built on Frontity
The Custom Hook should be the alternative solution I am looking for. I will try it based on Twenty Twenty-Three theme. Do you have more suggestion? Thanks!
Was there ever a discussion to have Automattic take this over? I recall attending a WordCampUS a few years back where Matt Mullenweg really pushed WordPress theme devs to learn JavaScript…It seems like that need has been disregarded, and I still await (hope) for an official theme release to resemble what Frontity accomplished.
My understanding is it is more efficient to let any JaveScript/Next/Gatsby developers to do this job. Right now, I try to develop a Jamstack solution for WordPress Twenty Twenty-Three Theme based on Gatsby WordPress Starter. If I success, I will publish it in my GitHub. Then people can provide comments, I will improve my code, so we can continue the advantages of Frontity. If this way works smoothly, more developers can convert more WordPress themes into JavaScript solution, and more theme developer can use them
Hi @mmczaplinski and all,
I’m interested in working actively with that framework as well. we can create a slack/WhatsApp group for active discussion. There, we will build an active team to monitor all personnel of the other contributors.
I want to join
Hello,
I’ve just been reviewing projects I had to abandon during the pandemic (including unfinished experiments with Frontity).
The blog announcement was a bit vague but from looking at the community activity, and the fact no maintainers have been appointed, I’m assuming the Automattic acquisition killed off the framework and it’s now dead in the water?
I should look at porting any code to a more mature framework like Ionic (for a single x-platform codebase) or look at the WordPress Interactivity API, which will be PWA capable but is in early development?
