127704ad17
Prior to the change backticks were used in an attempt to create a code block. The problem is that inside block level HTML tags Markdown is not supported. I have replaced the backticks with a combination of HTML tags in order to approximately simulate the appearance of a code block. The docs suggest possible use of span tags in place of the surrounding div tags as a solution to getting the Markdown to render. I tried this but no success. This change improves the readers understanding of the information, because the reader doesn't have to make sense of raw markdown. |
||
|---|---|---|
| .github | ||
| benchmark | ||
| docs | ||
| exe | ||
| features | ||
| lib | ||
| rake | ||
| script | ||
| test | ||
| .codeclimate.yml | ||
| .editorconfig | ||
| .gitignore | ||
| .jrubyrc | ||
| .rubocop.yml | ||
| .travis.yml | ||
| CONDUCT.markdown | ||
| Gemfile | ||
| History.markdown | ||
| LICENSE | ||
| README.markdown | ||
| Rakefile | ||
| appveyor.yml | ||
| jekyll.gemspec | ||
README.markdown
Jekyll
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.
Having trouble with OS X El Capitan?
See: https://jekyllrb.com/docs/troubleshooting/#jekyll-amp-mac-os-x-1011
Getting Started
- Install the gem
- Read up about its Usage and Configuration
- Take a gander at some existing Sites
- Fork and Contribute your own modifications
- Have questions? Check out our official forum community Jekyll Talk or
#jekyllon irc.freenode.net
Code of Conduct
In order to have a more open and welcoming community, Jekyll adheres to a code of conduct adapted from the Ruby on Rails code of conduct.
Please adhere to this code of conduct in any interactions you have in the Jekyll community. It is strictly enforced on all official Jekyll repositories, websites, and resources. If you encounter someone violating these terms, please let a maintainer (@parkr, @envygeeks, or @mattr-) know and we will address it as soon as possible.
Diving In
- Migrate from your previous system
- Learn how the YAML Front Matter works
- Put information on your site with Variables
- Customize the Permalinks your posts are generated with
- Use the built-in Liquid Extensions to make your life easier
- Use custom Plugins to generate content specific to your site
License
See the LICENSE file.