cms VS Wagtail

Statamic is one of the best flat-file CMSs. It’s built with Laravel and can be used as a headless Git-based CMS as well. The paid professional version allows you to use REST APIs and GraphQL APIs for content management and offers a GitHub integration for content storage and editorial workflows.

Aah, that's always a controversial question, on one hand, some universal rules of usability do exist, but on the other hand, everyone's habits, taste and use cases are very different.

The most neutral definition of a "well designed" website, without any further context, could be "created in a way that helps users achieve intended goals efficiently, while keeping max number of users happy about its look".

Again, different audiences will have very different answers. Here at HN, sites like https://www.mcmaster.com/ and https://www.craigslist.org win – because HN users appreciate old look and how efficient these sites are.

https://www.apple.com/ is an industry standard of a marketing site for consumer tech. It's not universally "well designed".

Other examples of well done marketing pages: https://www.sketch.com/ ; https://statamic.com/ ; https://linear.app/ got its share of hype recently.

Other times, a website is well designed because its content is awesome and is easy to consume. See https://ciechanow.ski/ and https://www.joshwcomeau.com/

Is https://github.com/ well designed? As an amateur developers, I'd say yes.

Is https://htmx.org/ well designed? Hmm, at a glance, there's no design at all. Is no design also design? That's a rabbit hole.

P.S. I often hear my website is well-designed :-)

Local CMSs are the ones that are mostly file-based (like Statamic or Astro). This means that you can edit everything locally and deploy the data. This way, our CMS is more secure, but on the downside, you have to have a local server working, and you might experience more conflicts, especially when two people will work on the same article (although Git might save you from many of those). It also means that there is a higher learning curve. A remote CMS works somewhere on a server, and most users don't care how.

I use Statamic, the free version will do everything your looking for and it can be as simple or as complex as you need it to be. It's flat file based (by default) too so deployment / version control is super easy.

Statamic (PHP / Laravel)

I'm not in the market for a CMS but if I were I'd likely go with https://statamic.com/ if I needed to build something from scratch.

If you're looking for a great CMS and were bitten by WordPress back in the day, you should take a look at Statamic (https://statamic.com)

It's a Laravel package and it's the best CMS I've ever used (from a dev perspective). v4 just dropped the other day

https://statamic.com free for personal. Your welcome.

If you like Python 🐍 then check out this project. Wagtail is a popular CMS, combining Django’s powerful customization capabilities with a slick user interface. The newest update brings Django 5.0 support, a new searchable and filterable listing UI, the accessibility checker built into the admin interface, and a brand new 10-step tutorial for developers. This release marks Wagtail's 10th birthday 🎂. Happy birthday to the team and all the best for the next ten years and beyond 🥳.

Repo : https://github.com/wagtail/wagtail

- The discussion thread we use to track all public feedback: https://github.com/wagtail/wagtail/discussions/9553. Comments very welcome.

Not so long ago, I submitted a Pull Request in wagtail to improve the admin performance, especially for non-superusers. Basically, it caches all the user's permissions on first access. However, I was pretty sure that this would load a lot of model fields that we never need but there isn't a tool that gives us that type of report. Therefore, I started building an app that keeps track of all fields accessed so you can easily know which ones haven't been used and apply the only/defer optimisation for Django querysets.

Wagtail would be a good example https://github.com/wagtail/wagtail/tree/main/wagtail/tests

Paarth moving from no contributions to the 21st most contributions - https://github.com/wagtail/wagtail/graphs/contributors.

Over the last few years, I have had the incredible opportunity to be a core team member of the Wagtail project. In that time, I have reviewed many new pull requests, and I’ve also had the chance to submit many of my own across Wagtail and many other projects.

Wagtail 2.15 is the most recent LTS (Long Term Support) release, so it’s not a bad release to stick to at all, at least until February 2023.