Hacker News Reader

Comment by geraldbauer | Hacker News Reader

Great news. Congratulations. If anyone is interested in learning more about Jekyll I've put together a link collection called Awesome Jekyll @ Planet Jekyll [1] - it also includes a section on the history (evolution) of GitHub Pages. Cheers. [1] https://github.com/planetjekyll/awesome-jekyll

View on HN

Why are you using a README to display this list instead of GitHub Pages?

It's a tradition. That's how awesome lists work. See the mother of all awesome lists -> https://github.com/sindresorhus/awesome for more examples. The idea is to keep it as simple as possible e.g. just a single README page. That's all.

Yeah I’m aware of that, but why? You can use GitHub pages with one markdown file; it would be the same contribution workflow but with a nicer end-user interface IMO.

Good point. Thanks. The first version was actually a links.yml Datafile with rendered with GitHub pages. The Dr Jekyll's Themes Directory [1] or the The Jekyll Showcase [2] still use this contribution workflow. Cheers.

[1] https://github.com/drjekyllthemes/themes [2] https://github.com/planetjekyll/showcase

You can't easily do pull requests on a GitHub Pages static file. (You'd have to edit the source.)

They work just like any other Markdown file, and you can include a link in the rendered site to edit. See http://ben.balter.com/2015/09/13/github-pages-edit-button/.

Ah, I am referring to the use case where the site is rendered clientside via Jekyll, then uploaded to the x.github.io repo. (which lets you use plugins, among other things, which is why I thought that was the more frequent use case). Not the loading-markdown-directly workflow.

Can you use Travis to build and modify the repo for you?

Reply on news.ycombinator.com