dan
/
jekyll
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
5,999 Commits 2 Branches 2 Tags 21 MiB
Ruby 70.6%
Gherkin 23.1%
JavaScript 3.8%
HTML 1.2%
Shell 0.8%
Other 0.4%
Go to file
Kevin Locke bb9462f12f Whole-post excerpts should match the post content 
When a post does not contain an excerpt_separator, meaning the excerpt
includes the entire post, the excerpt should contain exactly the post
content.

This is desirable both from a correctness standpoint, that the excerpt
should not introduce any new content, and more practically to allow fast
and easy detection of whole-post excerpts in Liquid templates using
`post.excerpt == post.content`.  A common use-case is deciding whether
to render "Read More" links on a page containing post excerpts.

This commit does exactly that.  It avoids adding additional newlines to
the excerpt content when the excerpt includes the whole post and adds
tests to ensure that this behavior is correct and preserved going
forward.

Signed-off-by: Kevin Locke <kevin@kevinlocke.name>
 		2015-10-01 13:58:00 -07: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 Whole-post excerpts should match the post content 2015-10-01 13:58:00 -07:00
lib Whole-post excerpts should match the post content 2015-10-01 13:58:00 -07:00
script add script to vendor mime types 2015-08-24 16:21:50 -04:00
site Notes for Homebrew, advanced installs, and cleanup 2015-09-30 12:57:09 -04:00
test Whole-post excerpts should match the post content 2015-10-01 13:58:00 -07: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
CONDUCT.md Add a Code of Conduct. 2015-08-20 10:17:37 -07:00
CONTRIBUTING.markdown update contributing documentation to reflect workflow updates 2015-08-05 14:30:35 -07:00
Gemfile Lock Cucumber to 2.0 because 2.1 is broken. 2015-09-11 15:03:07 -05:00
History.markdown Update history to reflect merge of #3999 2015-09-30 21:23:41 -07:00
LICENSE Update LICENSE to 2015. 2015-02-17 22:17:25 +01:00
README.markdown Add a Code of Conduct. 2015-08-20 10:17:37 -07: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

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

License

See LICENSE.