Hey everyone! WPBones v2.0 just dropped the biggest release since the framework launched. Here s the short version:
The old build pipeline is gone. No more Gulp, no more run-s, no more per-plugin build scripts that drift over time. v2 replaces everything with a single webpack.config.js that auto-discovers your entries from resources/assets/. Drop a .tsx file, webpack picks it up. That s it.
Lately I ve been thinking about how different design challenges look depending on the product you re building.
In theory, design processes often look clean and structured. But in reality, every product comes with its own constraints unclear requirements, edge cases, technical limitations, or simply trying to balance user needs with business goals.
This release brings you 2 core features: official Cloud Services and Strategy Engine, fully enhancing the out-of-the-box AI experience and convenient automated task processing capabilities. In addition, this update covers up to 19 new features, 27 improvements, and 15 bug fixes, dedicated to creating a smoother, smarter, and more stable user experience.
Trophy is now powering over 24M streaks which is kind of crazy to think about considering we only launched 1.0 here in January this year. One of the parts I find most interesting about building horizontal infrastructure is that as you scale and power more and more products you get to see insights that most teams building in isolation will only see a part of, and you can use those insights to make the the infrastructure better for everyone. For example, because we power streaks for so many users, Trophy can tell that 25% of all streaks are lost on a Friday, closely followed by Saturday (19%) and then Wednesday (18%).
We launched here back in 2024, which gave us a real platform to kickstart our journey, and the feedback from this community has genuinely shaped how we built Inr .
Hey all, BIG announcement! We just crossed 2 million users on Scrimba This marks a massive step towards our goal to be the place to learn and build with code. If you haven't already tried Scrimba, come on in! We still have many completely free courses from frontend, fullstack, backend and AI as well as a lively discord of friendly folks all around the world who help inspire, support and motivate one-another every.single.day.
I've been building my app for 8 months now, and i ended up having 5 repositories
nextjs app
databases
customer facing API
node-sdk that wraps the api
react-sdk, for both reusing shared component and customer facing components
So i thought, it's gonna be great if i create a mono repo with submodules. But it was terrible. I realized that turborepo does not like external packages, and as i tried to reuse my own customer facing libs, the DX became terrible. It was very time consuming to ship a feature. Even when i wanted to use Codex or Cursor 3, it was not able to show git diff properly, also i was not able to use Cursor's cloud agents properly to ship complex features.
