Why not use github Pages and scrape the github repository for necessary data? It's all harmless recipe stuff anyway. Non-github users could be asked to use e-mail to place recipes, and can be informed that they can use markdown. Or even present a web form that sends an encrypted e-mail for them, employing that wicked JS textarea enhancer we saw the other day, for markdown syntax or even allow haml.
The github haml pages can have links station'd at the top or bottom to pre-fetch categories, previous, and next pages. The github Page Index can include a JS that builds the UI of the site via DOM manipulation, based on a lightweight Web app hosted elsewhere and called in via ajax.
Why not use github Pages and scrape the github repository for necessary data? It's all harmless recipe stuff anyway. Non-github users could be asked to use e-mail to place recipes, and can be informed that they can use markdown. Or even present a web form that sends an encrypted e-mail for them, employing that wicked JS textarea enhancer we saw the other day, for markdown syntax or even allow haml.
The github haml pages can have links station'd at the top or bottom to pre-fetch categories, previous, and next pages. The github Page Index can include a JS that builds the UI of the site via DOM manipulation, based on a lightweight Web app hosted elsewhere and called in via ajax.Summary: Total MVR (minimum viable repository).