Here's the code
Http://gihub.com/evanplaice/evanplaice.com
I haven't fleshed out the journal section yet but the majority of the rest of the site is all markdown driven with a clean separation between application. It's also hosted on S3.
In theory, I could change the content directly to be loaded on Dropbox, although it would be preferable to provide inline caching of requests. For example use AWS lambda to frequently check for updates.
Eventually, when it's ready, I plan to extract the journaling portion and release it as a server-less journaling platform.
What about a 3rd option?
Use a web application that can asynchronously fetch markdown files and render them client-side.
That's basically how my site I've been working functions.
http://evanplaice.com
Here's the code Http://gihub.com/evanplaice/evanplaice.com
I haven't fleshed out the journal section yet but the majority of the rest of the site is all markdown driven with a clean separation between application. It's also hosted on S3.
In theory, I could change the content directly to be loaded on Dropbox, although it would be preferable to provide inline caching of requests. For example use AWS lambda to frequently check for updates.
Eventually, when it's ready, I plan to extract the journaling portion and release it as a server-less journaling platform.