A week ago, I asked @parkr via email if he could add my site here (mostly because I thought it's too cheeky to just propose a file-change). But now he told me that it's better to just do it here: I'm asking because I spend a huge amount of time and effort on making it great and usefully structured for people who're just getting started with Jekyll. Therefore it's also great as a forked starting-point, if you ask me. Besides keeping the code clean, I also spend much time on making the site as fast as possible. There's not much CSS in use, the HTML output is minified and images are directly served from the repo (and therefore GitHub's CDN) instead of from third-party services. There's also a lot of "include"-thinking happening for things like embedded Tweets, images or iFrames - which most people just inline in each post. When making a significant change, I also always make sure to write a few paragraphs about why I exactly did it as a commit message. And when it comes to really big updates, I write entire posts too (explaining all improvements and their benefits to the site's performance/look). Here's an recent example: http://leo.github.io/notes/v2/ I'm definitely sure that many people could get something out of it. Don't you think so too? |
||
---|---|---|
.. | ||
_data | ||
_docs | ||
_includes | ||
_layouts | ||
_posts | ||
_sass | ||
css | ||
fonts | ||
help | ||
img | ||
js | ||
news | ||
.gitignore | ||
CNAME | ||
README.md | ||
_config.yml | ||
favicon.ico | ||
feed.xml | ||
freenode.txt | ||
index.html | ||
latest_version.txt |
README.md
Jekyll docs site
This directory contains the code for the Jekyll docs site, jekyllrb.com.
Contributing
For information about contributing, see the Contributing page.
Running locally
You can preview your contributions before opening a pull request by running from within the directory:
bundle install
bundle exec rake site:preview
It's just a jekyll site, afterall! 😉