We're off to the races with new releases, new features, bug fixes and more. It's been an incredibly productive two weeks for the Faust.js team and we're just getting started!

Our first sprint of 2023 is complete and, as I write this, we're preparing a new release of Faust.js with new hooks for TypeScript and an initial, experimental, approach to support Gutenberg Blocks.

Hello 2023!

It's been a quiet 2 weeks for the Faust team as most of us took time to be with our families for the holidays. As a result we spent the last two weeks looking at a few minor bugs and hope to have a fresh release out soon.

Sprint 25 was a really productive one for the Faust.js team. We took a break from direct work on the codebase and made it a Faust.js hackathon with an emphasis on exploring features for the future of Faust.

The last two weeks have been all about cleanup and improvements to existing Faust features. We started the sprint with 11 different issues in mind and managed to close 16 and release one new version of the Faust cli package. It was a very successful sprint.

Progress is iterative, and that has definitely been the theme of our past two weeks as we build Faust. Rather than pushing forward on a host of new features we're not sure if you even need we've been stepping back and using our support as part of WP Engine to meet with agency partners already building on Atlas and headless in general. We've also been polishing what we have since our public release of new Faust and planning what we'll be working on in 2023.

With the end of Sprint 22, our team is proud to officially announce the re-release of Faust.js, WP Engine’s framework for building headless WordPress sites!

During this sprint, we launched the rewritten Faust documentation to work with the new version of Faust, which includes a handy getting started guide, as well as updated references and examples. We are so excited for folks to go check out new docs and really dig into these new features, and plan to roll out several new documents in the coming weeks.

Documentation, documentation, documentation.

The theme of our last sprint was documentation and it showed. We're super close to launching new documentation for new Faust. You'll see the updates on https://faustjs.org in the coming weeks.

It's alive!

After a lot of work we're happy to announce that the new code for Faust is available on npm. You can find the core package here and our new CLI package here.

This week the team finished Sprint 19, our latest 2 weeks of work, which was focused on polishing the new version of Faust and preparing to release it to you. We've been focusing on what to call the project, how to make sure those of you using existing Faust can continue to do so while needed as well as preparing plans for post-launch features and work that we want to focus on all while taking some time off and dodging hurricanes (you're reading this late as we're a fully-remote team and I am based in Sarasota, FL which was just hit by Hurricane Ian this week).

What we accomplished​

Most of our work was spent deciding how to best handle a new library that is vastly different than Faust has been built in the past. The syntax and other uses of moving from GQty to Apollo alone make things quite differently than it had been before. As a result we're working on solutions to ensure the new version is a separate install than what you've used in the past. This ensures, with a 4th quarter launch before the holidays, that your existing projects are safe and supported going forward. If you have, for example, "*" in your package.json for Faust (not a solution we recommend but, we realize, something a lot of people do), if we weren't careful that could break what you have. That won't be the case with the new version. Instead we're working on migration guides, package organization and more to ensure existing users are safe and supported and can migrate to the new library as needed.

What's next​

Sprint 20 is focused on preparing that new release. We want to have the new Faust into your hands in the next couple of weeks and that is what we're currently working on. This includes setting up new packages, finishing testing, prepping documentation and more. We've also cleaned up our backlog and will be working on filling out future epics to ensure work on new features, such as full support for Gutenberg and the Block Editor that go beyond anything you've seen yet in headless WordPress, can kick off in the coming weeks.

Next week, on 1 October to be specific, we're also happy to announce we have an official lead developer on the team that builds Faust. If you're interacted with our support on Discord or elsewhere you've probably come across Blake Wilson. He's one of the original Faust developers and was instrumental both in the current version and the new version we're about to release. I'm happy to announce he's been promoted to Senior Software Engineer here at WP Engine and will officially be taking over the team lead spot for Faust as well.

It's an exciting time for Faust and the team building it. Personally it took me a long time to understand the value of headless WordPress. Once I came to Atlas I could see the value but the tools were still too immature to really unlock its full potential. With the new version of Faust the rocket has lifted off and I am super excited that we're finally bringing you a full framework that can grow with your projects and with WordPress itself all while making headless WordPress development as easy and powerful as WordPress heavyweights like Genesis have done for the WordPress framework over the past decade.

Let's do this!