At Laracon US we announced we're working on a new course at Spatie: Full Stack Artisan.
In Full Stack Artisan, we'll dive into building Laravel applications with Inertia, React, TypeScript, view models, our Laravel Data package, and more.
Last week I took a break from working on course content to set up branding and a landing page.
Last week, we launched a redesigned for Flare, our Laravel error tracker.
I contributed to the app UI, but most of the work was done by Digital With You, who provided us with the design, and the team that implemented it: Alex, Freek, Rias, Ruben, and Sam.
Check it out for yourself! Or read our launch post for all the nitty gritty details.
I created the original Spatie guidelines site three years ago. Last month, we consolidated a few of our subsites to our main spatie.be site, including the guidelines.
I'm not going to dive into implementation details. I'm going to talk about why we decided on this stack and go in-depth on the structure of the application code, bundle sizes, and choosing external dependencies.
Some time last year, we released the latest iteration of the Spatie.be website.
There's a succinct description of what we're about, followed by a peculiar little block, dubbed "Latest insights from the team".
Unlike other agencies, we don't have a company blog. We encourage everyone to write on their own blog and put their latest articles in the spotlight.
Everyone keeps ownership of their content.
There's nothing fancy backing this feature, blog entries are synced via RSS. If you're interested in implementing something similar in PHP, our source code is available on GitHub.
We just open sourced our company guidelines site! We previously kept the contents in a private wiki on GitHub, but I'm glad we finally put the time in giving the contents a real home.
Like our docs site, the content is stored in markdown files, which can directly be edited on GitHub. The site deploys whenever something's pushed to the master branch.
As for why we decided to open source it all...
This site contains a set of guidelines we use to bring our projects to a good end. We decided to document our workflow because consistency is one of the most valuable traits of maintainable software.
The contents of this site exist for ourselves—more importantly, our future selves—and for giving future collegues a reference to our way of doing things and their quirks. The guidelines cover workflow, code style, and other little things we consider worth documenting.
The guidelines are available on guidelines.spatie.be.