4 ms·

Did you forget the part where the the template snippets become bootstrap html? Granted, it's not something I wrote. I just saw a potential use of a great librar

Did you forget the part where the the template snippets become bootstrap html? Granted, it's not something I wrote. I just saw a potential use of a great library that could be achieved by building a simple server over it. Anyone could do it, but I was the one who did it this time, at this place, for a genuine need I had. If you're going to call a Show HN menial because it doesn't live up to your standards of how complex a show HN would be, your opinion is duly noted. But from "complete lack of functionality" to "menial", that's quite a stretch.

stephenr 12y ago
I apologise for my tone in earlier comments. Let me try again: My point is that the goals of this project seem to introduce more problems than it solves. It re-creates the same HTML header/footer for every request, but then doesn't do the actual markdown conversion, and it doesn't even serve the associated JS, CSS, etc files that are required to make it work. A simple Markdown to styled page(s) tool is a great idea, I wrote one myself a few years ago, before moving onto things like Gollum. Having a read-only tool like this is a great alternative to the extra weight of something like Gollum, but this just doesn't really solve the problem very well right now, IMO. Given that it runs on Node, you could quite easily add a few features to make it a more complete solution: * Serve all assets - in this way, this can be used standalone, behind a caching proxy like varnish, or as an origin server for a CDN service like Akamai or similar. The specific JS and CSS that it requires could be bundled outside the document root and handled as a special case in the url router. * Handle markdown conversion in the server. The client-side code can probably run with little if any modification in Node, and would reduce the number of resources and processing time required on the client device

stephenr 12y ago

I apologise for my tone in earlier comments. Let me try again: My point is that the goals of this project seem to introduce more problems than it solves. It re-creates the same HTML header/footer for every request, but then doesn't do the actual markdown conversion, and it doesn't even serve the associated JS, CSS, etc files that are required to make it work. A simple Markdown to styled page(s) tool is a great idea, I wrote one myself a few years ago, before moving onto things like Gollum. Having a read-only tool like this is a great alternative to the extra weight of something like Gollum, but this just doesn't really solve the problem very well right now, IMO. Given that it runs on Node, you could quite easily add a few features to make it a more complete solution: * Serve all assets - in this way, this can be used standalone, behind a caching proxy like varnish, or as an origin server for a CDN service like Akamai or similar. The specific JS and CSS that it requires could be bundled outside the document root and handled as a special case in the url router. * Handle markdown conversion in the server. The client-side code can probably run with little if any modification in Node, and would reduce the number of resources and processing time required on the client device