These are chat archives for jescalan/roots

11th
Feb 2016
Jeff Escalante
@jescalan
Feb 11 2016 04:53
would love to support prismic. the only reason I haven't investigated it further is because they don't have a write API
so for us at carrot that makes it fairly unsafe for use
meaning any content in prismic needs to be manually added via their web interface, there's no way to programmatically add content
this means probably I won't be putting a lot of time into building an extension for it myself
especially bc there's so much on my plate at the moment
but I'd be happy to help out with and/or review if someone else wanted to work on it!
David Eglin
@djeglin
Feb 11 2016 10:25
Yeah, that makes sense. Upon looking at it there are a couple of things it just doesn't deal with that would be dealbreakers for me, too - Such as markdown.
Shame, because the writing environment and the flexibility afforded with "slice" fields looks amazing.
Contentful it is, then :)
Jeff Escalante
@jescalan
Feb 11 2016 15:29
@djeglin it is sad though I agree. I spend a lot of time looking over contentful alternatives, because honestly I am not a fan of contentful's pricing model. but haven't found anything yet
David Eglin
@djeglin
Feb 11 2016 15:32
Yeah - To be honest, Contentful is great for some people, but for a lot of potential clients I think that the writing and actual content management experience might be less-than-ideal, too.
David Eglin
@djeglin
Feb 11 2016 15:47
@jenius How do you go about setting the basedir in roots? When I've used jade separately in the past I've just set it as a jade option, but it seems here I need to set it in locals. It looks like I need to do some kind of string interpolation along the lines of #{__dirname}/views, but that itself doesnt work
David Eglin
@djeglin
Feb 11 2016 16:10
Nevermind - Managed to sort it in the end.
Noel Quiles
@EnMod
Feb 11 2016 17:02
@jenius would Cockpit CMS be a decent self-hosted alternative to Contentful?
Eli Williamson
@eliwilliamson
Feb 11 2016 17:10
so i searched this room and implemented the scss support via node-sass installation and requiring in app.coffee as well as updating the css_pipeline to accomodate scss file extensions. idk what i could have missed but roots just stays stuck "compiling" forever here is my app.coffee
This message was deleted
David Eglin
@djeglin
Feb 11 2016 17:13
FWIW, @EnMod , I've used Cockpit before and it seems like a really well put together little system. You would, as I understand it, end up using it with roots-records to parse the json spat out by Cockpit. Can't comment specifically on implementing it with Roots, but when I've worked with it in a relatively standalone sense it has been a breeze
Eli Williamson
@eliwilliamson
Feb 11 2016 17:15
i tried running roots watch -v but still no outbut to help me debug :/
Eli Williamson
@eliwilliamson
Feb 11 2016 17:29
nm - roots was outdated. just updated and all is working swell!
http://i.imgur.com/j6ZBj.gif?noredirect
Noel Quiles
@EnMod
Feb 11 2016 20:39
@djeglin Hmm...I might try using roots-records and Cockpit in that case then, to see how it works for me. Thanks for the insight! Sounds like this might be a good idea for you too, @jenius