rams-jekyll-feed 0.13.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 7f3cb511770a28bcfbbecf77ca8b578c914c4be693557caff990828efb6b2e19
+  data.tar.gz: 1589e07490b1b5045ef3a12a239c227dfc6a8ed87b6226cc67cd29e48ccd5704
+SHA512:
+  metadata.gz: b6481cef834d7fb704efaf0a5088def0228d316f2d972fe22c41c5ed61b33284d99874afcbe59d18f9b40e64f839e4229a0b4bd818e07026af3e8b4a17720216
+  data.tar.gz: 8fa2a552cd1d1d3af2e26085a68feaba99d6553abe9496acc17f6281b5ba12a68e3e6bc2593772f3aa0da3d17cb9d3ed3ecccc7986dd6fa403f999dc3adc5244

data/.gitignore

@@ -0,0 +1,21 @@
+/vendor
+/.bundle/
+/.yardoc
+/Gemfile.lock
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+/spec/reports/
+/tmp/
+*.bundle
+*.so
+*.o
+*.a
+mkmf.log
+*.gem
+Gemfile.lock
+spec/dest
+.bundle
+spec/fixtures/.jekyll-metadata
+spec/fixtures/.jekyll-cache

data/.rspec

@@ -0,0 +1,2 @@
+--color
+--format progress

data/.rubocop.yml

@@ -0,0 +1,27 @@
+require: rubocop-jekyll
+
+inherit_gem:
+  rubocop-jekyll: .rubocop.yml
+
+AllCops:
+  TargetRubyVersion: 2.3
+  Include:
+    - lib/**/*.rb
+
+  Exclude:
+    - .gitignore
+    - .rspec
+    - .rubocop.yml
+    - .travis.yml
+
+    - Gemfile.lock
+    - History.markdown
+    - LICENSE.txt
+    - README.md
+
+    - script/**/*
+    - vendor/**/*
+
+Naming/MemoizedInstanceVariableName:
+  Exclude:
+    - lib/jekyll-feed/page-without-a-file.rb

data/.travis.yml

@@ -0,0 +1,32 @@
+language: ruby
+cache: bundler
+rvm:
+  - &latest_ruby 2.6
+  - 2.4
+  - 2.3
+env:
+  global:
+    - NOKOGIRI_USE_SYSTEM_LIBRARIES=true
+  matrix:
+    - JEKYLL_VERSION="~> 3.8"
+matrix:
+  include:
+    - rvm: *latest_ruby
+      env: JEKYLL_VERSION="~> 3.7.4"
+    - rvm: *latest_ruby
+      env: JEKYLL_VERSION=">= 4.0.0.pre.alpha1"
+before_install:
+- gem update --system
+- gem install bundler
+before_script: bundle update
+script: script/cibuild
+notifications:
+  email: false
+deploy:
+  provider: rubygems
+  api_key:
+    secure: qz0q6ur0kGo03jjLdoAak6WcEAwxX2r9LG3DVrhOrcfoFipkuW+uwR0et4tpK8uFrz0P9y7eTIKOb0XCXeIsIXWj6R5benpRGr2U8m9A+tE/jxviBFUaxaokte0lqWiX1fEyhRmW3zvcdLQ47Vd2EwTNaq6ZmPulmEe9gS0rBQghyclakGlZ17LI7oGgiNL9SQ335Yqa1qJklTHYHbodWQ3Z07v7VN2jxqi3WH6NacT5gUGp5iCNCLLa8+jpKr4uONNIoy6/geAWdqtvgGUE8oTjIWDoJarrknJpqfx9Rd0KLDzkyneAigHDYPW60QtrE6GGpK/+TF1pF4DzdK2EgTWqGFnZf8ehfnxmtHVl2Xq/DPr6hS8Q/f+ut4ioMzBQxPD0hfh8/EOMYKsO8mOuOlYTiZXC7iuGyvFUOl2hnBgWA99t+I0NNB06qFp3ZxIjolEc3zjzc9f1a5HUXlEut5V8nqvCwbctNiTVpT8ZEWlsQlyRUnr9cIMUTEfLgQ+v6DnvAJBMO1EILq6liB5qfutjNhzhlREt7P/ZdppGsAzWpgt0q2PafqVoPe62WR3+/8Lj2ErMr034xSSqZVNcBS0mbdvW6k3jaABo1VJ4XuHm6/yDuemWzWb7kdG9/14+IIJMW1VuaWcmnCnB6gxjkCW3Dm2ftYiN7Rfn3AUz/nU=
+  gem: jekyll-feed
+  on:
+    tags: true
+    repo: jekyll/jekyll-feed

data/Gemfile

@@ -0,0 +1,11 @@
+# frozen_string_literal: true
+
+source "https://rubygems.org"
+gemspec
+
+gem "jekyll", ENV["JEKYLL_VERSION"] if ENV["JEKYLL_VERSION"]
+
+install_if -> { Gem.win_platform? } do
+  gem "tzinfo", "~> 1.2"
+  gem "tzinfo-data"
+end

data/History.markdown

@@ -0,0 +1,165 @@
+## 0.13.0 / 2019-11-13
+
+### Minor Enhancements
+
+  * Excerpt only flag (#287)
+  * Add media:content tag (#290)
+
+### Development Fixes
+
+  * test: use categories in post (#249)
+
+## 0.12.1 / 2019-03-23
+
+### Bug Fixes
+
+  * Re-introduce Ruby 2.3 support and test Jekyll 3.7+ (#272)
+
+## 0.12.0 / 2019-03-21
+
+  * Allow Jekyll v4 (still alpha)
+
+### Development Fixes
+
+  * style: fix offenses in specs (#248)
+  * dev: update CI and style settings (#258)
+  * Enable testing for Windows platform (#265)
+
+## 0.11.0 / 2018-09-09
+
+### Development Fixes
+
+  * Require Ruby 2.3 (#222)
+  * Refactor to remove redundant calls and variables (#240)
+
+### Minor Enhancements
+
+  * Categories and collections (#228)
+  * Remove check for older version of Jekyll (#234)
+
+## 0.10.0 / 2018-06-04
+
+### Bug Fixes
+
+  * Escape image URL (#209)
+
+### Development Fixes
+
+  * Rubocop 0.55 (#223)
+  * Bump Rubocop (#230)
+
+### Minor Enhancements
+
+  * Support Typhoeus 1.0 (#232)
+
+## 0.9.3 / 2018-02-04
+
+  * Define path with __dir (#187)
+  * Bump Ruby for Travis (#188)
+
+### Documentation
+
+  * Fix: Add note about using plugins instead of gems key (#197)
+  * Add documentation for disabling smartify filter (#205)
+  * Use `https` in more places. (#165)
+
+### Development Fixes
+
+  * Rubocop: Target Ruby 2.2 (#195)
+  * Test feeds that have a `site.lang` (#164)
+  * Test against Ruby 2.5 (#201)
+
+### Minor Enhancements
+
+  * fix <entry> template for posts with post.lang defined (#168)
+
+## 0.9.3 / 2017-03-28
+
+## 0.9.1 / 2017-02-17
+
+### Minor Enhancements
+
+  * Update feed.xml (#162)
+
+## 0.9.0 / 2017-02-16
+
+### Minor Enhancements
+
+  * Use absolute_url to generate the feed_meta url (#150)
+  * Make feed stylesheet optional (#149)
+  * Use new `normalize_whitespace` filter (#143)
+  * Feed entries must contain <author> (#152)
+  * Remove trailing slash from feed ID (#159)
+
+### Development Fixes
+
+  * Simplify minify regular expression (#141)
+  * Namespace as JekyllFeed (#151)
+  * rubocop -a (#160)
+
+### Bug Fixes
+
+  * Filter out drafts before limit (#154)
+
+## 0.8.0 / 2016-10-06
+
+  * Use filters to clean up Liquid template (#134)
+
+### Minor Enhancements
+
+  * Don't set @site.config["time"] on feed generation (#138)
+
+### pedantry
+
+  * Appease Rubocop (#139)
+
+## 0.7.2 / 2016-10-06
+
+  * Support `image.path` when `post.image` is an object (#137)
+
+## 0.7.1 / 2016-09-26
+
+  * Assign `url_base` before first usage (#133)
+
+## 0.7.0 / 2016-09-06
+
+  * Use type="html" to skirt around double escaping problem (#127)
+
+## 0.6.0 / 2016-07-08
+
+  * Cleanup `post_author` logic (#113)
+  * Add XML stylesheet example with XSLT (#119)
+  * DRY up and add more doc (#120)
+  * Use smartify filter (#117)
+
+## 0.5.1 / 2016-04-18
+
+  * Fix mangling of whitespace when `site.lang` is set (#110)
+
+## 0.5.0 / 2016-04-13
+
+  * Consolidate regexps for stripping whitespace (#82)
+  * Only test against Jekyll 3 (#99)
+  * Think about how i18n might work (#75)
+  * Find author by reference (#106)
+  * Drop support for Jekyll 2 (#105)
+  * Add support for post image (#104)
+
+### Minor Enhancements
+
+  * Use Module#method_defined? (#83)
+  * Use site.title for meta tag if available (#100)
+
+### Development Fixes
+
+  * Do not require [**jekyll-last-modified-at**](https://github.com/gjtorikian/jekyll-last-modified-at) in tests (#87)
+  * Add Rubocop (#81)
+  * Correct typo in tests (#102)
+  * Simplify testing feed_meta tag (#101)
+  * Quiet known warnings in tests (#103)
+
+## 0.4.0 / 2015-12-30
+
+  * Feed uses `site.title`, or `site.name` if `title` doesn't exist (#72)
+  * Replace newlines with spaces in `title` and `summary` elements (#67)
+  * Properly render post content with Jekyll (#73)

data/LICENSE.txt

@@ -0,0 +1,22 @@
+Copyright (c) 2015-present Ben Balter and jekyll-feed contributors
+
+MIT License
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -0,0 +1,206 @@
+# Jekyll Feed plugin
+
+A Jekyll plugin to generate an Atom (RSS-like) feed of your Jekyll posts
+
+[![Build Status](https://travis-ci.org/jekyll/jekyll-feed.svg)](https://travis-ci.org/jekyll/jekyll-feed) [![Gem Version](https://badge.fury.io/rb/jekyll-feed.svg)](https://badge.fury.io/rb/jekyll-feed)
+
+## Installation
+
+Add this line to your site's Gemfile:
+
+```ruby
+gem 'jekyll-feed'
+```
+
+And then add this line to your site's `_config.yml`:
+
+```yml
+plugins:
+  - jekyll-feed
+```
+
+:warning: If you are using Jekyll < 3.5.0 use the `gems` key instead of `plugins`.
+
+## Usage
+
+The plugin will automatically generate an Atom feed at `/feed.xml`.
+
+### Optional configuration options
+
+The plugin will automatically use any of the following configuration variables, if they are present in your site's `_config.yml` file.
+
+* `title` or `name` - The title of the site, e.g., "My awesome site"
+* `description` - A longer description of what your site is about, e.g., "Where I blog about Jekyll and other awesome things"
+* `url` - The URL to your site, e.g., `https://example.com`. If none is provided, the plugin will try to use `site.github.url`.
+* `author` - Global author information (see below)
+
+### Already have a feed path?
+
+Do you already have an existing feed someplace other than `/feed.xml`, but are on a host like GitHub Pages that doesn't support machine-friendly redirects? If you simply swap out `jekyll-feed` for your existing template, your existing subscribers won't continue to get updates. Instead, you can specify a non-default path via your site's config.
+
+```yml
+feed:
+  path: atom.xml
+```
+
+To note, you shouldn't have to do this unless you already have a feed you're using, and you can't or wish not to redirect existing subscribers.
+
+### Optional front matter
+
+The plugin will use the following post metadata, automatically generated by Jekyll, which you can override via a post's YAML front matter:
+
+* `date`
+* `title`
+* `excerpt`
+* `id`
+* `category`
+* `tags`
+
+Additionally, the plugin will use the following values, if present in a post's YAML front matter:
+
+* `image` - URL of an image that is representative of the post (can also be passed as `image.path`)
+
+* `author` - The author of the post, e.g., "Dr. Jekyll". If none is given, feed readers will look to the feed author as defined in `_config.yml`. Like the feed author, this can also be an object or a reference to an author in `_data/authors.yml` (see below).
+
+### Author information
+
+*TL;DR: In most cases, put `author: [your name]` in the document's front matter, for sites with multiple authors. If you need something more complicated, read on.*
+
+There are several ways to convey author-specific information. Author information is found in the following order of priority:
+
+1. An `author` object, in the documents's front matter, e.g.:
+
+  ```yml
+  author:
+    twitter: benbalter
+  ```
+
+2. An `author` object, in the site's `_config.yml`, e.g.:
+
+  ```yml
+  author:
+    twitter: benbalter
+  ```
+
+3. `site.data.authors[author]`, if an author is specified in the document's front matter, and a corresponding key exists in `site.data.authors`. E.g., you have the following in the document's front matter:
+
+  ```yml
+  author: benbalter
+  ```
+
+  And you have the following in `_data/authors.yml`:
+
+  ```yml
+  benbalter:
+    picture: /img/benbalter.png
+    twitter: jekyllrb
+
+  potus:
+    picture: /img/potus.png
+    twitter: whitehouse
+  ```
+
+  In the above example, the author `benbalter`'s Twitter handle will be resolved to `@jekyllrb`. This allows you to centralize author information in a single `_data/authors` file for site with many authors that require more than just the author's username.
+
+  *Pro-tip: If `authors` is present in the document's front matter as an array (and `author` is not), the plugin will use the first author listed.*
+
+4. An author in the document's front matter (the simplest way), e.g.:
+
+  ```yml
+  author: benbalter
+  ```
+
+5. An author in the site's `_config.yml`, e.g.:
+
+  ```yml
+  author: benbalter
+  ```
+
+### Meta tags
+
+The plugin exposes a helper tag to expose the appropriate meta tags to support automated discovery of your feed. Simply place `{% feed_meta %}` someplace in your template's `<head>` section, to output the necessary metadata.
+
+### SmartyPants
+
+The plugin uses [Jekyll's `smartify` filter](https://jekyllrb.com/docs/templates/) for processing the site title and post titles. This will translate plain ASCII punctuation into "smart" typographic punctuation. This will not render or strip any Markdown you may be using in a title.
+
+Jekyll's `smartify` filter uses [kramdown](https://kramdown.gettalong.org/options.html) as a processor.  Accordingly, if you do not want "smart" typographic punctuation, disabling them in kramdown in your `_config.yml` will disable them in your feed. For example:
+
+   ```yml
+   kramdown:
+     smart_quotes:               apos,apos,quot,quot
+     typographic_symbols:        {hellip: ...}
+   ```
+
+### Custom styling
+
+Want to style what your feed looks like in the browser? Simply add an XSLT at `/feed.xslt.xml` and Jekyll Feed will link to the stylesheet.
+
+## Why Atom, and not RSS?
+
+Great question. In short, Atom is a better format. Think of it like RSS 3.0. For more information, see [this discussion on why we chose Atom over RSS 2.0](https://github.com/jekyll/jekyll-rss-feed/issues/2).
+
+## Categories
+
+Jekyll Feed can generate feeds for each category. Simply define which categories you'd like feeds for in your config:
+
+```yml
+feed:
+  categories:
+    - news
+    - updates
+```
+
+## Collections
+
+Jekyll Feed can generate feeds for collections other than the Posts collection. This works best for chronological collections (e.g., collections with dates in the filenames). Simply define which collections you'd like feeds for in your config:
+
+```yml
+feed:
+  collections:
+    - changes
+```
+
+By default, collection feeds will be outputted to `/feed/<COLLECTION>.xml`. If you'd like to customize the output path, specify a collection's custom path as follows:
+
+```yml
+feed:
+  collections:
+    changes:
+      path: "/changes.xml"
+```
+
+Finally, collections can also have category feeds which are outputted as `/feed/<COLLECTION>/<CATEGORY>.xml`. Specify categories like so:
+
+```yml
+feed:
+  collections:
+    changes:
+      path: "/changes.xml"
+      categories:
+        - news
+        - updates
+```
+
+## Excerpt Only flag
+
+Optional flag `excerpt_only` allows you to exclude post content from the Atom feed. Default value is `false` for backward compatibility.
+
+When in `config.yml` is `true` than all posts in feed will be without `<content>` tags.
+
+```yml
+feed:
+  excerpt_only: true
+```
+
+The same flag can be used directly in post file. It will be disable `<content>` tag for selected post.
+Settings in post file has higher priority than in config file.
+
+
+## Contributing
+
+1. Fork it (https://github.com/jekyll/jekyll-feed/fork)
+2. Create your feature branch (`git checkout -b my-new-feature`)
+3. Commit your changes (`git commit -am 'Add some feature'`)
+4. Push to the branch (`git push origin my-new-feature`)
+5. Create a new Pull Request