Store markdown: Every view = conversion Every edit = no processing Store html Every view = no processing Every edit = convert to markdown and back Store both Every view = no processing Every edit = convert to html after edit You have to weigh up your processing costs vs. your storage cost.
What I've seen is indeed to store the compiled HTML in a seperate row in the database. Just have one row 'content' and another 'content_html', and save the compiled HTML in the 'content_html' row. (Surely you have some kind of save method that you can override to do this?).
I'm currently using Markdown with PHP. I store the markdown-source in the database, and I display the Converted Version upon request. I have no performance issues, and am very happy with this setup.
You should definetly store original Textile/Markdown markup and use either standard HTTP caching stuff (Last-modified, Expires-At, ETag) to cache rendered pages or just cache the result of processing markup.
I've put up a little survey to see what people prefer for markup here: luciddesign.co.nz/2009/2/9/textile-vs-ma....
It's just a picture of the survey and no results. – stesch Jun 18 at 8:42.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.