Nextblock Update: 5 NPM Libs, `npm create nextblock`, and What's Next

Hey dev community!

Sorry I've been a bit quiet on here. I've been deep in the trenches on Nextblock, and I'll be honest—getting the monorepo architecture just right was much harder and took way longer than I originally anticipated.

But that grind has finally paid off, and I'm stoked to share some massive updates.

The Milestones

The foundation for Nextblock is now set, and it's built to scale.

1. NX Monorepo with 5 Libraries: The project is now fully contained in an NX monorepo. This was a huge lift, but it means we can properly manage shared code, UI, utils, and more. The structure is now broken down into 5 core libraries.
2. All Libs are on NPM: All 5 of these new libraries have been successfully published to npm, making them available to the public.
3. We Got the Name! This is the one I'm most excited about. We've officially secured the npm create nextblock command! This is a huge step for making onboarding easy and establishing the brand.

What's Next: DX and Adoption

With the core architecture solid, my focus is now shifting 100% to developer experience (DX) and getting this into the hands of early adopters.

Here's the immediate roadmap:

• Optimize npm create nextblock: Right now, the command is a placeholder. My next task is to build it out to be a proper scaffolding tool. It will gather setup information (project name, etc.) and provide clear guidelines on how to install.
• Create a Starter Template: I'll be creating the first official "early adopter" template. This is the key to letting you all finally try Nextblock and see what I mean by "2025 ultrafast website speeds."

The goal has never changed: No compromise. This framework will be the end of WordPress.

Thanks for following the journey. The really fun stuff starts now.