Hacker News new | past | comments | ask | show | jobs | submit login

What would be the advantages of using this over static site generators?



The UX isn't an utterly terrible developer workflow?

I write code all day. Git is awesome, and you can pry Vim from my cold dead hands. But Jekyll is fiddly and doesn't really match my preferred writing workflow.

Ghost workflow: Visit URL, mash password manager (occasionally), click "new post" and start writing. Change the title whenever I feel like it. A live preview of the post appears on the left, and I click publish when I'm done. Click a little button in the UI to view the finished post on my site.

Jekyll workflow: Open a terminal. Create a new file named with the current date and the post stub. Half the time I don't know what either of those are off the top of my head. Open Vim. Type out the post metadata block. Inevitably get something wrong. Type post. Tab to the terminal and start Jekyll's server. Navigate to local server URL in browser. Alt tab back and forth between browser and editor, hitting F5 every time I want a new preview. Rename file with new stub (optional). Git add, commit, and push. Navigate to my public site in browser to make sure everything came out OK. Mash F5 a few times because Github Sites hasn't compiled it yet. Delete the "We compiled your site!" email from my inbox.

Note that Ghost requires much less prep; the majority of my time in Ghost is just editing my post's text. Jekyll has a larger lead in time to editing, and while editing I have to switch back and forth between my editor and the browser for a preview. Jekyll requires more effort doing busywork that isn't writing. I found my output dropped way off after I switched from Wordpress because the barrier to starting a post was higher.


If you host your jekyll blog on github, then creating a new blog post is as simple as logging into github and going straight to your blog repo. You can create a new file and edit straight from there. The blog is rebuilt on each commit.


Oh, nice. iirc, I tried it when online editing first appeared on Github, and it was a bit finicky about rebuilding the page afterwards. Good to hear it works now.

I used prose.io for a while, but ran into a few cases where the preview didn't match what Github generated. It looks like there's a whole new interface since the last time I used Prose, so perhaps that's not an issue anymore. It supports image uploads now, too.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: