Earlier quoted context omitted.
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/ .
GitHub pages is now running Jekyll 3
11–20 of 119 posts
Re: GitHub pages is now running Jekyll 3
#12Re: GitHub pages is now running Jekyll 3
#13I was a little surprised to see that GitHub is essentially playing favorites with Markdown rendering engines. Is there a discussion somewhere that outlines some of the reasoning behind this pick?
Re: GitHub pages is now running Jekyll 3
#14Re: GitHub pages is now running Jekyll 3
#15I was a little surprised to see that GitHub is essentially playing favorites with Markdown rendering engines. Is there a discussion somewhere that outlines some of the reasoning behind this pick?
Yes. The decisions was actually made on the open source GitHub Pages Gem repo, based on both user feedback and actual usage stats: https://github.com/github/pages-gem/issues/179.
Re: GitHub pages is now running Jekyll 3
#16Re: GitHub pages is now running Jekyll 3
#17Also it's a bit unfortunate there's still no easy way to do site translation in Jekyll.
Anyway, well done on the upgrade. Love jekyll.
Re: GitHub pages is now running Jekyll 3
#18[1]: https://www.staticwebsitemanager.com
Are there any features the community would love to see offered in a Jekyll-based CMS?
Re: GitHub pages is now running Jekyll 3
#19Re: GitHub pages is now running Jekyll 3
#20We are in private beta and are looking for people to try it out and give us feedback. We think it's great and are looking for early adopters who want an awesome static hosting experience.