brandonkelly

Most scaling issues come from overly complex content models. The overall volume of content isn’t much of a concern.

Thanks dude <3

Not yet. We’ll share some thoughts when we make our decision, I’m sure.

Yeah we’re starting to investigate which route we’ll take (Yii 3, Laravel, or Symfony).

These days everything is so componentized it’s becoming less and less important, though. Craft has always pulled in a various Symfony components, and v4 adds Laravel Collections.

Interesting scoop from the other side—thanks Daniel!

From the outside, there were some weird vibes coming out of EL back then – they’d taken a bit of an adversarial tone with the community, which had us wondering whether it was a good idea to have all our eggs in the EE basket. Then an EL designer publicly ranted about P&T, calling us a “direct competitor”, on the EE Podcast, when Craft was just a twinkle in our eye. Which ironically, was the exact moment we decided to really commit to building a CMS. Self-fulfilling rant I guess :)

The instructions assume you have a whole PHP dev environment setup-- very frustrating, after some time googling the various errors I kept hitting I just quit.

Sorry you had trouble. Craft definitely has stricter requirements than WP. v4 requires PHP 8, a handful of PHP extensions, and MySQL 5.7.8+/MariaDB 10.2.7+/PostgreSQL 10.0+.

Most modern local dev environments will have everything it needs – DDEV (https://ddev.com/), Lando (https://lando.dev/), our own Craft Nitro (https://getnitro.sh/), even MAMP, etc. –, but I realize these come with a learning curve. We do our best to ease you into it without making too many assumptions in our tutorial, so you might want to try giving it another go with that: https://craftcms.com/docs/getting-started-tutorial/

If you’re a Mac user, you’re going to need to start moving in this direction even to get WordPress running, as built-in PHP support has been deprecated and Apple plans to stop shipping it in future versions of macOS.

This has been my issue with most Wordpress alternatives-- they assume you are a professional PHP developer, rather than someone who just wants to try a CMS

No argument there. WP is built for the masses; Craft is a developer tool. It doesn’t assume PHP knowledge (the built-in templating system is powered by Twig), but you will need a strong understanding of web standards and basic logical concepts. Or you can get your content out using the built-in GraphQL API, to hook it into a decoupled front-end like Next.js or Gatsby.

1. They're not dropping out when the product becomes less profitable...if some drop out, others take over

I mentioned we’re open to moving to FOSS if we can create a business model that supports it. I should also say that, if worst comes to worst and we have to shut off the lights, one of two things will happen: either we will sell Craft to one of the thousands of companies with a vested interest in the product, whom we strongly feel is capable of continuing to move it forward, or we’d give Craft a GPL or MIT license, making it FOSS. There is no scenario where we would just drop it and pretend it never existed. Even if we wanted to do that, it would ruin our professional careers and probably result in a few lawsuits, so no thanks! :)

2. There are many people looking at the code and fixing bugs.

We recommend that plugin developers familiarize themselves with Craft’s codebase, because it’s the best place to find examples of how to do things when developing plugins. As a result, we’ve received hundreds of bug fixes from the community (including suggested code fixes). So this is definitely not an exclusive benefit to FOSS software.

CraftCMS seems more fitting to our needs because it's flexible and lean; we're impressed with what we've seen so far but are concerned that it's not open-source and that it's so new.

Hi, I’m the Founder & CEO of Pixel & Tonic, the team behind Craft CMS. I’m obviously biased, but if your only concerns with Craft are that it is proprietary and relatively new, I’d like to attempt to ease those concerns :)

Yes the actual Craft application logic is proprietary, but all of the code is “open source” in that it’s not obfuscated in any way, and the majority of the code is in fact FOSS, including Yii, Twig, Guzzle, jQuery, and several smaller scripts. We contribute to many of them, and if we can create a business model that supports it, someday we’d even like to make Craft itself FOSS.

Which brings me to a second point, which is that unlike most CMS projects (and open source projects in general), Craft is made by a dedicated team of developers. We’re funded entirely from Craft CMS (and Craft Commerce) sales, with no VC/angel funding. So we’re highly incentivized to keep making Craft better every day, and keep offering great support. Our business is stable, we’re profitable, and revenue is rising steadily. We’ll still be around in 10 years :)

And as to it being new, well, it’s not really that new anymore. 1.0 came out in early 2013, it’s had over 240 updates (see the changelog – https://craftcms.com/changelog), and it’s generally considered to be one of the most bug-free CMSes out there. And it is being used by thousands of companies and organizations, from small boutiques to global brands like The Associated Press, Netflix, Oakley, Mixmag, and Wired. You can read about a few of those projects here: https://craftcms.com/news/case-studies

That’s my spiel, but feel free to AMA if you have any questions :)

Haha, definitely agree with this. I took some time to override much of the Kama skin's CSS (including the dialogs) for Wygwam. Ended up with something much more clean: http://brandon-kelly.com/fieldframe/showcase