You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -40,7 +40,7 @@ Do you already have an existing feed someplace other than `/feed.xml`, but are o
40
40
41
41
```yml
42
42
feed:
43
-
path: atom.xml
43
+
path: /blog/feed.atom
44
44
```
45
45
46
46
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.
@@ -62,13 +62,15 @@ Additionally, the plugin will use the following values, if present in a post's Y
62
62
63
63
* `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).
64
64
65
+
* `description` - A short description of the post.
66
+
65
67
### Author information
66
68
67
69
*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.*
68
70
69
71
There are several ways to convey author-specific information. Author information is found in the following order of priority:
70
72
71
-
1. An `author` object, in the documents's front matter, e.g.:
73
+
1. An `author` object, in the document's front matter, e.g.:
72
74
73
75
```yml
74
76
author:
@@ -176,16 +178,16 @@ By default, collection feeds will be outputted to `/feed/<COLLECTION>.xml`. If y
176
178
feed:
177
179
collections:
178
180
changes:
179
-
path: "/changes.xml"
181
+
path: "/changes.atom"
180
182
```
181
183
182
-
Finally, collections can also have category feeds which are outputted as `/feed/<COLLECTION>/<CATEGORY>.xml`. Specify categories like so:
184
+
Finally, collections can also have category feeds that are outputted as `/feed/<COLLECTION>/<CATEGORY>.xml`. Specify categories like so:
183
185
184
186
```yml
185
187
feed:
186
188
collections:
187
189
changes:
188
-
path: "/changes.xml"
190
+
path: "/changes.atom"
189
191
categories:
190
192
- news
191
193
- updates
@@ -195,15 +197,15 @@ feed:
195
197
196
198
Optional flag `excerpt_only` allows you to exclude post content from the Atom feed. Default value is `false` for backward compatibility.
197
199
198
-
When in `config.yml` is `true` than all posts in feed will be without `<content>` tags.
200
+
When in `config.yml` is `true` then all posts in feed will be without `<content>` tags.
199
201
200
202
```yml
201
203
feed:
202
204
excerpt_only: true
203
205
```
204
206
205
-
The same flag can be used directly in post file. It will be disable `<content>` tag for selected post.
206
-
Settings in post file has higher priority than in config file.
207
+
The same flag can be used directly in post file. It will disable `<content>` tag for selected post.
208
+
Settings in post file have higher priority than in config file.
207
209
208
210
## Tags
209
211
@@ -244,6 +246,16 @@ feed:
244
246
245
247
Note that if you include a tag that is excluded a feed will not be generated for it.
246
248
249
+
## Skip development
250
+
251
+
Use `disable_in_development: true` if you want to turn off feed generation when `jekyll.environment == "development"`,
252
+
but don't want to remove the plugin (so you don't accidentally commit the removal). Default value is `false`.
253
+
254
+
```yml
255
+
feed:
256
+
disable_in_development: true
257
+
```
258
+
247
259
## Contributing
248
260
249
261
1. Fork it (https://github.com/jekyll/jekyll-feed/fork)
0 commit comments