docpad

I am pretty confused with the architecture behind how data is persisted in Docpad. From blogs and forums, I got to know in-memory (and/or out directory) is used for generated contents. But one of the selling points of Docpad is "completely file based". From the sound of it, hosting it on Heroku or any ephemeral file system doesn't seem logical. Can anyone give some explanation/clarification? DocPad is pitched as a next generation web architecture. This mindmap showcases why we call it that perfectly: DocPad Architecture Vision http://d.pr/i/jmmZ+ The workflow being like so: Importers bring

DocPad is described as being comparable to other static site generators, but it is also described as being "not limited to static site generation". I've been browsing the DocPad website and other documentation and haven't yet been able to find anything that seems to explain how to incorporate dynamic content, and what types of limitations may be involved? As a relative beginner, I am wondering if anyone can help me better understand the methodology whereby dynamic content would be incorporated into DocPad...? e.g. AJAX, and dynamic server-side scripts for doing things like dynamically loading

I would like to minify HTML, CSS and JavaScript files when I hit docpad generate , how can I do that? There are a few ways you can go about this. The most prominent and most immediate way is to modify your docpad configuration file to trigger an external tool like grunt to minify your assets via the grunt minify task . Here is a gist that showcases this. Alternatively, there is also Cloudflare which is an amazing website DNS server that also acts as a CDN for your website's content, and minifies your assets automatically post-deployment. Read more here. Also, while it isn't minify related, you

I've created a Docpad site using the Twitter Bootstrap skeleton. I cannot get either Bootstrap's tabbable tabs or drop-down menus to work. They render, but do not function. From research on Stackoverflow it appears that additional jquery needs to be included for these Bootstrap functions. I've tried to add it in to Docpad but have been unsuccessful. Has anyone gotten these Bootstrap functions to work in Docpad? for Boostrap, to run drop-down menu i know its need this code in a page to work: $('.dropdown-toggle').dropdown(); this call a bootstrap plugin. the sequence call for js files is:

This should be really obvious but I just cant get my head around it How do I add extra routes in Docpad?? Im looking for the Docpad equivalent to express.js's app.post("*", function(res,req,next){ //Do stuff } As far as I can understand I need to create a plugin module for this? How do I tell Docpad to use my routes? Im guessing it has something to do with the extend-server event, do I put that as parameter in docpad.coffee? How do I pass the req object to my route handler? can I force docpad to always consider my routing first? kinda like middleware? can I pass a (processed) url back to

I need show only partial blog post... with a "Read more" link to full blog post. HOME: List last 5 partial/intro posts with Read More. This is possible in Docpad? Thanks.. May by getCuttedContent: (content) -> i = content.search('<!-- Read more -->') if i >= 0 content[0..i-1] else content hasReadMore: (content) -> content.search('<!-- Read more -->') >= 0 more and <% posts = @getCollection('posts') %> <% for i in [@document.page.startIdx...@document.page.endIdx]: %> <% document = posts.at(i).toJSON() %> <article class="post"> <h3><span class="posts_date"><%= @formatDate(document.date) %></span