81–90 of 208 posts
Is there an open source CMS that people would recommended for use with a static website generator for large websites? Netlify CMS is interesting for example and I love how content changes are versioned in Git. I like static website generation but don't want to get locked into a proprietary CMS platform.
So while talking during the entire article about being firm supporter of open source software, they choose a proprietary CMS. I'm disappointed by the W3C.
I'm technical director of an agency that builds websites solely in WordPress, and I can say with feeling that Gutenberg has (so far) been a disaster not just in terms of accessibility but in terms of clarity of the development process. It's been a moving target since day one, with us constantly scrambling to keep up with large changes in each release. We held off for a while, and have only built three sites with it,…
But more importantly, it should not be in core. Full stop. Once WP became REST-driven the push should have been to lighten core. That is to decouple as muxh as possible. Core is that _core_. Then you configure your needs from there. Core should be the basics, as light and as lean as possible.
But instead, more and more unnecessary bloat. More and more features with less and less benefit.
Yes, I'm looking at CraftCMS and others as well. WP has jumped the shark. It's not going away. But I'm tired of having to shower after everytime I work with it.
Is there an open source CMS that people would recommended for use with a static website generator for large websites? Netlify CMS is interesting for example and I love how content changes are versioned in Git. I like static website generation but don't want to get locked into a proprietary CMS platform.
Glad they realized the issues of Wordpress but a shame they went with proprietary nonsense with a faux license. A php based platform has a lot of negatives for scalability. Using a cms to generate static content is much more simple, scalable and cheaper. Keep it simple.
> The use of React complicates front-end build. We have very talented front-end developers, however, they are not React experts - nor should they need to be. > I believe front-end should be built as standards-compliant HTML/CSS with JavaScript used to enrich functionality where necessary and appropriate. This is what worries me about React (and with other front end frameworks in general). I'm writing this as someone…
I use Wordpress extensively and I find the whole Gutenberg switch to be absolutely atrocious. From the design to the technical implementation. And it is also received as such. The classic editor has been downloaded millions of times. What worries me most is that the developers haven’t responded one bit to these issues (if I read the relevant issues) and it solves no problems. It feels a lot like the technology du jou…
Is there an open source CMS that people would recommended for use with a static website generator for large websites? Netlify CMS is interesting for example and I love how content changes are versioned in Git. I like static website generation but don't want to get locked into a proprietary CMS platform.
I belive that with GatsbyJS you can your a repo + markdown as a "backend".
I also don't understand the hype. I think it's just good marketing, people don't know the alternatives, and it uses React.
I usually side with Hugo because it's so fast and simple to get running. I don't love the template language but the majority of sites don't need complex template logic anyway.
Earlier quoted context omitted.
I belive that with GatsbyJS you can your a repo + markdown as a "backend".
Does Gatsby build fast enough for a large site though? I find their business model strange if I'm understanding it correctly - faster builds are a paid feature. I also don't understand the hype. I think it's just good marketing, people don't know the alternatives, and it uses React. I usually side with Hugo because it's so fast and simple to get running. I don't love the template language but the majority of sites do…