Go to file
Leonard 2db01b9651 Added my site for learning purposes
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?
2015-08-16 20:59:06 +02:00
benchmark Add benchmark for end_with? vs regexp 2015-02-25 11:57:49 -08:00
bin Merge branch 'master' of https://github.com/jekyll/jekyll into _includes 2015-08-09 16:22:33 +01:00
features Merge branch 'fniephaus-_includes' into 'master' 2015-08-16 13:30:45 -04:00
lib Merge branch 'fniephaus-_includes' into 'master' 2015-08-16 13:30:45 -04:00
script Updated the scripts shebang for portability 2015-07-18 22:23:56 -04:00
site Added my site for learning purposes 2015-08-16 20:59:06 +02:00
test Merge branch 'master' of https://github.com/jekyll/jekyll into _includes 2015-08-09 16:22:33 +01:00
.gitignore DRY up the StaticFile tests a bit. #3633. 2015-04-10 16:24:45 -04:00
.jrubyrc Add support for JRuby, it was easier than assumed. 2015-05-15 07:10:22 -05:00
.travis.yml Update to JRuby 9K 2015-07-24 23:43:55 -05:00
CONTRIBUTING.markdown update contributing documentation to reflect workflow updates 2015-08-05 14:30:35 -07:00
Gemfile Try to organize dependencies into dev and test groups. 2015-07-16 16:31:30 -05:00
History.markdown Update history to reflect merge of #3782 2015-08-16 13:32:18 -04:00
LICENSE Update LICENSE to 2015. 2015-02-17 22:17:25 +01:00
README.markdown Jekyll Talk instead of plain URL + "official" 2015-05-12 14:24:40 +02:00
Rakefile Release jekyllrb.com as a locally-compiled site. 2015-02-07 22:09:43 -08:00
jekyll.gemspec Move previous runtime dependencies to development dependencies. 2015-01-31 13:53:17 -08:00

README.markdown

Jekyll

Gem Version Build Status Code Climate Dependency Status Security

By Tom Preston-Werner, Nick Quaranto, Parker Moore, and many awesome contributors!

Jekyll is a simple, blog-aware, static site generator perfect for personal, project, or organization sites. Think of it like a file-based CMS, without all the complexity. Jekyll takes your content, renders Markdown and Liquid templates, and spits out a complete, static website ready to be served by Apache, Nginx or another web server. Jekyll is the engine behind GitHub Pages, which you can use to host sites right from your GitHub repositories.

Philosophy

Jekyll does what you tell it to do — no more, no less. It doesn't try to outsmart users by making bold assumptions, nor does it burden them with needless complexity and configuration. Put simply, Jekyll gets out of your way and allows you to concentrate on what truly matters: your content.

Getting Started

Diving In

License

See LICENSE.