+ [2015-07-29T07:00:28Z] pontiki here's how i'm thinking of doing it:
+ [2015-07-29T07:01:57Z] pontiki use a collection of http response codes, text meanings, descriptions, and/or other error page content. Use that collection to build the set of static pages under /error, and wire up the nginx conf to point at them.
+ [2015-07-29T12:44:23Z] gynter pontiki: i have all error pages generated by hand
+ [2015-07-29T12:44:33Z] gynter but that collections solution would do fine
+ [2015-07-29T12:56:52Z] jaybe pontiki, nod; that's how i go about it. nginx.org/r/error_page

message no. 105605

Posted by pontiki in #jekyll at 2015-07-29T07:01:57Z

use a collection of http response codes, text meanings, descriptions, and/or other error page content. Use that collection to build the set of static pages under /error, and wire up the nginx conf to point at them.
+ [2015-07-30T01:37:27Z] jaybe no need to ask to ask; just ask your question ;)
+ [2015-07-30T01:52:30Z] happy_dev haha alright jaybe
+ [2015-07-30T01:52:50Z] happy_dev I wanted to redo my website, and was hoping to add a blog to it. It's currently being hosted on DigitalOcean. Would Jekyll be a good thing to use for this? I'm fairly decent with HTML/CSS/JS, but don't really know much about backend yet