adoro
adoro copied to clipboard
Which are the most popular CMS and why?
http://awards.cmscritic.com/past-winners/ of these I've used:
- Drupal
- Joomla
- Magento (e-commerce)
- Wordpress
- Magnolia
- Ghost
Why would anyone want to build another CMS given there are _so many_ ("good" ones) already...?
I'm going to be adding some notes on a lightweight, open source and secure CMS that I am looking for. My other need is for it to be relatively friendly suitable for non technical people to use.
My understanding so far is that Drupal and Wordpress don't fall into the lightweight category. Using the list above as a starting point I'm going to look into them in a bit more detail.
Joomla
- [x] Open source
- [ ] Lightweight/ secure
- PHP, MySQL
- User friendly? Seems so. Doesn't require markdown etc.
- Need to know our hosting plan as a starting point for installation.
Magento
- [x] Open source
- [ ] Lightweight/ secure
- PHP
- User friendly?
Magnolia - digital business platform
- [x] Open source
- [ ] Lightweight/ secure
- Java
- User friendly?
Wagtail
- [x] Open source
- [x] Lightweight/ secure
- Python
- User friendly? yes
Elixir CMS - not suitable
Lyn
DEVELOPMENT IS IN PROGRESS.
Changelog
Should I fork this and use it as a platform?
Probably not. We won't stop you from doing it, but we don't advise it. This is not a general purpose podcasting CMS. It is a CMS that is specific to Changelog and our needs. From the design and layout to the data structures and file hosting, we built this for us. An example of just how custom it is — we literally have our podcast slugs hardcoded in areas of the code. Yuck.
Thesis - BETA Quality
- React User Interface
- 'Not a full featured CMS'
- Not a full featured WYSIWYG editor
- Not an authentication or permission system
Contento - WIP
Node Shortlist
Ghost - publishing platform
- [x] Open source
- [x] Lightweight/ secure
- AMP integration
- Authors, Editors, Administrator permissions
- Has JQuery built in
- Node, MySQL, Ember, Express, Handlebars
- CONS: html written in markdown but there is a realtime live preview so you can see what the changes you're making look like, 'publishing platform' will be interesting to see how easily it can build our features, has a 'Pro' paid for version with more features, Ubuntu 16.04 is the only officially supported OS
Ghost is designed beautifully for blogging purposes but lacks the flexibility when comes to building the website. https://uditgoenka.com/blog/ghost-vs-wordpress/
- CRM Integration? Ghost and Zoho CRM or Wealthbox CRM ($35pm) listed on Zapier
2016 Article: If you need just a blog, I highly recommend using Ghost, but if you want to run a website or launch a web app with a blog, Keystone.js is a way to go. https://modernweb.com/building-blog-keystone-cms-node-js/
Enduro
- Handlebars, Sass, Gulp, Bootstrap, Angularjs, Browsersync, Express, Jasmine, Git, Npm and Heroku
- CONS: build failing, C grade for maintenance, is no db a problem?
- No db just flat files?
- Deploy by git
Apostrophe
- Node, MongoDB, Nunjucks (templating), Express, Less
- Definitely has blog module
- Used by well known orgs
- Nice content management UI
Keystone
- For database driven websites
- 'More like a CMF than a CMS'
- Used by well known orgs
- Node, MongoDB, Express, Handlebars/Jade/ NunJucks/ Swig
- Can do email management
- Doesn't have different admin roles built in out of the box
- Upkeep:
We haven't actually abandoned Keystone, just done a terrible job of communicating what's going on and empowering others to be involved. So we're fixing that, starting today.
As has been pointed out, v4 should have been out of "beta" ages ago and, functionally, has been for a year. It needs to be cleaned up and published so we can move forward.
We'd like to bring in new admins and maintainers from the community to help organise and do the work of finalising v4, and continue maintaining it into the future.
Buckets - Deprecated
The focus/emphasis of the question should have been on the Why part. Most people default to using an existing CMS because they don't want to think about how the CMS user-experience or "workflow" can be improved. The reason we ended up using "Wagtail" for client projects was because I didn't want to waste my time explaining to "stakeholders" why it's suboptimal.
There are always "trade-offs" and no single CMS has all the features I would like to have "out-of-the-box" (or through extensions/modules/plugins). WordPress comes close in terms of SEO, Content Editing Experience and Plugin Availability, but it falls short on Security, Version Control and "Workflow".
Any CMS that we end up using must do things quantifiably better than the "status quo". otherwise we are a "me too" with nothing to differentiate ourselves from all the other agencies which build "Skins" on existing CMSes ...
Here are a selection of questions I would ask:
- [ ] Is the content version-controlled by default (how can I roll-back to a previous version?)
- [ ] Is there a user "hierarchy" (admin, editor, commenter, guest, etc) so content creation /editing/approval permissions are clear.
- [ ] What is the Content Creation/Editing/Approval UX?
- [ ] Is the Content Editor "WYSIWYG" or does the creator need to know HTML/Markdown?
- [ ] Are content changes done through an approval/review workflow (where appropriate)? (like GitHub PRs but for non-technical people)
- [ ] Are pages rendered as AMP by default (i.e. mobile-first/friendly and cached by Google)?
- [ ] Are static pages/assets served from a CDN with well-defined headers for faster loading?
- [ ] Are real-time analytics built-in by default so data is easily viewable.
- [ ] does track http refers and show custom content for users from a specific platform.
- [ ] Is full-text-search built-in? Or is the search UX terrible?
- [ ] Is SEO done well by default or will Google never find / index the content?
- [ ] Are links automatically-indexed so they can be periodically checked to avoid
404
errors? - [ ] How are "media" (images/videos) uploaded and managed? (are they stored on CDN by default?)
- [ ] Can a user create "Draft" content which is hidden and not published until approved.
- [ ] Can content be scheduled so that it goes out at an "Embargo" date/time e.g: an "announcement"?
- [ ] Can content have an "end time" so that it gets "unpublished" at a certain time e.g: "Black Friday Promo".
- [ ] Does the CMS have a real-time commenting system which promotes engagement?
- [ ] Is SPAM Protection built-in or an "after thought"?
- [ ] How much additional configuration is required in order to send emails?
(e.g. to send an update on a comment they posted)
- [ ] how are users confirmed? (do we send them an email with a link they need to click?)
- [ ] Can Users authenticate with their existing "Social" account? e.g: Facebook or Google?
- [ ] Can (registered) Users suggest edits to content (e.g: fix a typo).
- [ ] Are "short URLs" enabled by default so content can easily be shared e.g:
dwyl.co/45dx
- [ ] Is tagging automatic or manual? does the platform suggest tags based on content? can (registered) readers of the content suggest new tags?
- [ ] is RSS available out-of-the-box or is an "add-on" required?
👍 We are definitely using this as a learning experience on the above rather than a decision on 'what to use'.
To the list above, I would add:
- [ ] is there image uploading functionality built in (with good documentation on how to set up hosting for the image)?
- [ ] is there image resizing functionality built in?