On today's menu: refactor one of the base parts of Hiker, our upcoming Laravel package. Quite proud of these 5-year-old lines of code as they proved our idea was feasible, performing and promising. Now, let's take them to the next level 💪

Hey Laravel devs, a question! 👋

For big projects containing a presentation website + app + ..., do you go full monolith or do you create separate Laravel repos for each part (and if so, how do you deal with repeated models, jobs, etc.)?

That's one of the main reasons I was thinking about in favor of the monolith. However, working as a team, separate repos could maybe offer less compatibility issues or maintenance overhead, allowing to upgrade each part at its own pace.

Typographic rules! Every language has them and sometimes they can get annoying to implement (french, I'm looking at you 😠).

I decided to tackle this problematic with a simple package, first to scratch my own itch but now that it's out there, give it a try!

It doesn't only add non-breaking spaces as you're free to register any custom language-specific rule.

github.com/whitecube/laravel-string-typography

GitHub - whitecube/laravel-string-typography: A set of simple Str & Stringable macros helping to implement typographic rules

From: github.com

So Pinkary is running on SQLite? Let's get some people here and demonstrate how it scales! 📈✅