@ryangorley I use ProcessWire as my go-to CMS, it‘s pretty flexible (I think there are some similarities to kirby) and it really shines when paired with a paid addon called ProFields (License of this one is not FOSS though). Let me know if you have any questions!
@ryangorley As much as it initially sounds like trolling, just go ahead with a plain HTML+CSS for portfolio site. And something common like jekyll, hugo or zola for blogs. github/gitlab allow to deploy the site using CI and all you worry about is a domain. Might be a bit tedious to get off the ground, but it's super convenient long term.
@jimmac For my own stuff, this totally works. For clients, they generally feel like they have to have some kind of CMS to make changes (even though 80% will never log in and use it).
It is Not for the feint of heart, and the plugin code is the Unix Way, not the drunken frat party that is WordPress plugins. To pull a phrase: $foo Is User Friendly Just Very Picky Who It's Friends Are
Drupal is a pain in the ass, and migrating plugins you best speak PHP well. Migration is actually easy with some good tools to assist but hand edit to be sure. I have five ports and was going to port Bootstrap{3-4... yeah I know}, but that project is likely a loss. (Bootstrap was Twitter's UI, guessing it's not internally maintained anymore).
@ryangorley have you seen @classicpress? It's WordPress without Gutenberg/FSE. You should feel right at home. You could pair it with Astro following the same instructions as WordPress. But the content management experience would be simpler.
@ryangorley@getkirby I‘m of course biased here as a member of the Kirby team, so I can‘t directly answer your question.
However you can rest assured that the only reason for our license is to ensure the continued development and support of Kirby. We are now in our 12th year since the Kirby 1 launch and our license model allows us to be sustainable. If we were still to go out of business for whatever reason, I‘m pretty sure we would open source Kirby.
@lukasbestle@getkirby Thanks for responding, Lukas. What you're saying aligns with what I've observed and I believe it.
It's not my place to tell anyone what they should give away. So this is only a suggestion. What if you freely licensed the versions of Kirby that have reached EOL? The newest & best Kirby could remain as is, but people would have insurance against the "bus factor" or an unsavory buy-out. Community could patch old versions for those who can't upgrade.
@ryangorley@lukasbestle@getkirby That's an interesting thought. We would need to discuss the consequences for us. If it would really mean that old versions get more community patches, that'd be great. But if it turns out that we get a lot more issues and PRs for very old code, it would be a problem for us.
I was wondering if we could actually write down that open-source exit promise that Lukas mentioned though. It sounds like a fair insurance policy for the community to me.
@ryangorley@getkirby personally, i would avoid proprietary software as much as i can. If you were searching for a niche software, i would expect limited options. For web publishing? Not so much, there are plenty to choose from: https://staticsitegenerators.net/
@pohokolius Yeah, that's how I like to work. Thanks for the link. There are some really neat SSG's out there. The problem is the headless CMS layer I would need to add for clients to keep up a blog or whatever. The setup is complex, and the most user-friendly options are proprietary. 🤦
I have looked into @astro which is an exciting #FOSS static site generator, but it would need to be paired with a headless CMS and those are almost universally proprietary (and expensive). It's hard to hand that kind of mixed setup off to a client too.
Grav would be the closest FOSS alternative to Kirby, but it's not as polished and development has slowed down a lot. I don't think I would be handing off a 5 year solution.
There are others. But yeah, I've spent a lot of time looking.
@ryangorley@astro I was really frustrated by the headless CMS landscape, so I built my own. It's called @mattrbld and I am planning on fully open sourcing it once I've had the chance to clean up the code a bit more (which unfortunately is taking longer than expected...).
Maybe it's worth for you to keep an eye on nonetheless. 😊
It's a FOSS CMS, built on top of Django. Really great content managment, verry good admin UI. And I lake that after install, it's minimal and then you add only what you need.
@ryangorley@postroutine@wagtail@doctormo I regularly teach Django to people who only know beginner Python. As long as you can understand Python syntax, you can clone Django Python code that uses advanced Python features that you might not have covered yet. Investing in a Python-based platform gives you more Python experience. Investing in more PHP is a losing proposition.
@_KevinTrainor@ryangorley@postroutine@doctormo Compared to WordPress, Wagtail’s strength will be how flexible it is, and in particular being able to have a solid ecosystem (Django + packages) for parts of the sites / pages that might not need any CMS features at all. There’s less "batteries included" though, it’s meant for devs keen to do quite a bit of coding with Django’s ORM. https://docs.wagtail.org/en/stable/getting_started/the_zen_of_wagtail.html is a good read if you want to consider it further.
Add comment