Steve McDougall asked us a  great question on Twitter about our redesign and relaunch of Laravel News on Statamic:

I’d love to read a write up by someone on the @laravelnews team about how they’ve adapted to @statamic and what made them choose this as a CMS system. Would be really interesting to see how they may have had to adapt, and any unforseen benefits they may have found.

The answers to these questions will not fit in a Tweet, so I wanted to go through each point and share a little behind the scenes on how this all came about.

Why we chose Statamic

I’ve had my eye on  Statamic since it first launched. Looking at my Statamic purchase history, I’ve been a customer since v1 but never felt the time was right to make the jump from my old system. That all changed when they launched v3 last year and moved it to a more Laravel package-style setup.

With v3, you can install it with any Laravel app, which meant I could keep a lot of the existing secondary code that runs Laravel News. These are things like the links section, the automated daily newsletter, the account management, etc. Knowing I could keep all that and gain a new control panel to write and publish posts was a big win.

#news #laravel

Reader Question: Why did you choose Statamic for Laravel News?
1.20 GEEK