5 ms·
Very similar to a tool I created a while back: https://github.com/ashleyw/convey https://github.com/ashleyw/convey It's <100 lines of code, and really quite pr
by ashleyw 15y ago
Very similar to a tool I created a while back: https://github.com/ashleyw/convey https://github.com/ashleyw/convey
It's <100 lines of code, and really quite primitive; if you request hello.css, and that file exists, it serves that. If it doesn't exist, but hello.sass does, it'll compile and serve that instead. Same goes for .haml and .coffee files requested with .html and .js respectively. No configuration, no required file structure — just prototype as you would with just HTML/CSS…except using the compiled templates you love!
- stdbrouw 15y agoWord. Convey may be easier to get running for some people, as it's Ruby instead of node.js. Thanks for sharing. Three things draughtsman adds on top of Convey: * No need for projects: works in any directory. * The ability to use JSON / YAML to populate templates; especially useful if you already have some JSON sample data you can use. * Offline resources: makes jQuery and underscore.js available at the root, regardless of whether they're actually in that directory. The one thing it misses that Convey has: * The ability to save the compiled files to a directory.
- ashleyw 15y agoConvey works in any directory too, you just run `convey` within it. The `init` command just creates a skeleton file structure to get you started. Like the idea of using JSON to populate templates though, that's neat!