How to Build a Static CMS with Roots, Contentful, and Netlify
1–9 of 9 posts
Re: How to Build a Static CMS with Roots, Contentful, and Netlify
#2This seems really complicated and expensive (if you're not using the free tier of each of the services) for something that could be really simple.
Re: How to Build a Static CMS with Roots, Contentful, and Netlify
#3This seems really complicated and expensive (if you're not using the free tier of each of the services) for something that could be really simple.
The free tiers for both are quite extensive actually, so we easily fit in, even with a very large amount of content.
Re: How to Build a Static CMS with Roots, Contentful, and Netlify
#4This seems really complicated and expensive (if you're not using the free tier of each of the services) for something that could be really simple.
I'm curious, by really simple are you referring to using a traditional out of the box CMS like Wordpress?
This works great for us as a digital agency because we usually have multiple projects going on at once that need to perform at scale immediately (traffic from large brand media buys and sharing on social platforms), so we needed tools to be able to manage static content.
If you have different ideas on how to allow non-developers to manage a static site (without having to edit our code repo), I'd love to chat :-).
Re: How to Build a Static CMS with Roots, Contentful, and Netlify
#5This seems really complicated and expensive (if you're not using the free tier of each of the services) for something that could be really simple.
+1, paying 99/month for the first non-free layer of contentful is defintely not cheap, and the free tier won't get you too far.
Ideally what I'd like to see for a small team is to run a $5 digital ocean instance that does at least a mediocre job of managing assets in a database and triggering the static export of the site. Unfortunately I haven't found anything that a non-savvy user would consider as useful. Any idea for that (or alternative for contentful)?
Re: How to Build a Static CMS with Roots, Contentful, and Netlify
#6This seems really complicated and expensive (if you're not using the free tier of each of the services) for something that could be really simple.
Maybe Cockpit CMS could be used? Self hosted CaaS style CMS and seems to have a REST interface. I wonder if it could be used with static generators? http://getcockpit.com/. I Have been thinking about this for a while and would love to see it work with metalsmith.io, Assemble.io or maybe even my favourite harp.js.
Re: How to Build a Static CMS with Roots, Contentful, and Netlify
#7This seems really complicated and expensive (if you're not using the free tier of each of the services) for something that could be really simple.
Maybe Cockpit CMS could be used? Self hosted CaaS style CMS and seems to have a REST interface. I wonder if it could be used with static generators? http://getcockpit.com/ . I Have been thinking about this for a while and would love to see it work with metalsmith.io, Assemble.io or maybe even my favourite harp.js.
Thanks for mentioning Cockpit CMS, it looks great!
Re: How to Build a Static CMS with Roots, Contentful, and Netlify
#8This seems really complicated and expensive (if you're not using the free tier of each of the services) for something that could be really simple.
+1, paying 99/month for the first non-free layer of contentful is defintely not cheap, and the free tier won't get you too far. Ideally what I'd like to see for a small team is to run a $5 digital ocean instance that does at least a mediocre job of managing assets in a database and triggering the static export of the site. Unfortunately I haven't found anything that a non-savvy user would consider as useful. Any idea…
This discussion got me thinking and I started working on a side project to do exactly that. Let me know if you'd like to be notified when it's ready for beta. My e-mail is in my profile if you're interested
Re: How to Build a Static CMS with Roots, Contentful, and Netlify
#9This seems really complicated and expensive (if you're not using the free tier of each of the services) for something that could be really simple.
I'm curious, by really simple are you referring to using a traditional out of the box CMS like Wordpress? This works great for us as a digital agency because we usually have multiple projects going on at once that need to perform at scale immediately (traffic from large brand media buys and sharing on social platforms), so we needed tools to be able to manage static content. If you have different ideas on how to allo…
This discussion got me thinking and I started working on a side project to do exactly that. Let me know if you'd like to be notified when it's ready for beta. My e-mail is in my profile if you're interested