author | tags |
---|---|
Emmanuel Château-Dutier |
cms, api |
https://css-tricks.com/api-based-cms-approach/#article-header-id-1
https://www.contentful.com/r/knowledgebase/headless-and-decoupled-cms/
https://pantheon.io/decoupled-cms
https://pantheon.io/blog/headless-websites-whats-big-deal-decoupled-architecture
http://gadgetopia.com/post/7206
http://gadgetopia.com/post/8244
https://medium.com/@davide.borsatto/the-death-of-the-cms-cec078a0d1b9#.d7kr6v4mh
http://symfony-cms.net/decoupling-headless-cms
https://medium.getsymphony.com
http://www.dtelepathy.com/blog/philosophy/do-you-really-need-a-cms
http://blog.varunarora.com/why-we-stopped-using-drupal-for-our-platform/
https://www.sitepoint.com/modx-the-best-cms-youve-never-used/
https://developer.wordpress.com/docs/api/
-
Easy file and image upload It should be very easy to add a download or to insert images. The system should even creates automatic thumbnails. Use CSS and Java Script to resize and crop it to the correct size.
-
user management Comes with a basic structure for user roles. You can assigned some team to certain ContentTypes that they’re allowed to edit. Some actions could be reserved for administrators, and developer can access to more configuration.
-
light interface
-
The Stack
-
Just editing ?
-
Taxonomie et flexibilité
-
Recherche