Citations & Bibliography for 11ty
npm install eleventy-plugin-citationsThis plugin parses Pandoc-style citations ([@id1; @id2]) in any input files and replaces them with formatted references.
It also stores the references in data that can be used to display a bibliography however and wherever you want.
1. Why another plugin?
1. Feature: Bibliography based on what is actually used in the output file, not how you structure your input files
2. Feature: Full templating customization
3. Feature: Multiple citation sequences that can be linked up correctly
4. Feature: Linkbacks from bibliography reference to citations in the text
2. Installation
3. Usage
1. Linking to bibliography files
2. Rendering citations in the text
3. Rendering the bibliography
4. Citation syntax
5. Confuguration Options
6. CSL Styles and Locales
1. Styles
2. Locales
7. Limitations \& Known issues
1. 11ty watch mode
2. Citation syntax
3. No support for 11ty \<= 2
4. Relative paths are resolved relative to the project root
5. Bibliography cannot come before the last citation
6. Low priority things
I developed this plugin over the course of writing my PhD thesis, while being on a pretty tight schedule.
Trust me, I really did not want to write yet another plugin for this unless I absolutely had to.
However, after carefully reviewing all the other plugins I could find, I decided that none of them were suitable for my needs.
Your needs may be different, so I suggest you check them out too:
| Package | Repo | Citation parser | Bbliography parser | Reference formatter |
| ------- | ---- | --------------- | ------------- | ------------- |
eleventy-plugin-citations (this plugin) | leaverou/eleventy-plugin-citations | _(Custom)_ | biblatex-csl-converter | citeproc + Custom + Your template! |
@arothuis/markdown-it-biblatex | arothuis/markdown-it-biblatex | _(Custom)_ | biblatex-csl-converter | citeproc |
eleventy-plugin-citeproc | Myllaume/eleventy-plugin-citeproc | @zettlr/citr | N/A _(Only supports JSON)_ | citeproc |
eleventy-plugin-bibtex | Savjee/eleventy-plugin-bibtex | N/A _(No citation support)_ | citation-js | citation-js |
markdown-it-bibliography | DerDrodt/markdown-it-bibliography | _(Custom)_ | biblatex-csl-converter-ts | citeproc |
markdown-it-cite | studyathome-internationally/markdown-it-plugins | _(Custom)_ | biblatex-csl-converter | _(Custom)_ |
I wanted to be able to break content down into multiple pages and templates and still have a single bibliography at the end.
I.e. a single bibliography for the whole thesis, and a separate, different one for each standalone chapter.
Most plugins were extending markdown-it, and thus were unaware of the broader context they were being used in, so they had to be atomic: all citations had to be in the same Markdown file.
Now, you could probably do some weird gymnastics to compile a Markdown file with all your content that you then feed back into eleventy
(thanks @DmitrySharabin for the idea!), but that sounded quite contorted.
The way this plugin works, collected references are keyed by page.url so you can have separate bibliographies
for separate files, based on what is actually used on each file.
This also means you can call it as many times as you want on the same content and it will not distort the output.
Most plugins were generating the HTML for the citations and references in JS, providing varying levels of customization.
I wanted to have the references as part of the data cascade and use actual templates for displaying them which provides unparalleled flexibility.
A lot of my content was Markdown converted from LaTeX with pandoc.
I had several citation sequences (e.g. [@foo; @bar]), which many plugins did not support or had limited support (e.g. only the first was linked).
This is due to how citeproc works that is at the core of all but one of them:
it returns a single string with all the citations in it and no metadata about what is what.
This plugin does a lot of work to reverse engineer citeproc’s output to figure this out.
Yes, even sequence ranges (e.g. [1, 3–5, 18, 34–60]) are correctly linked up!
You can set up your template so that not only citations link to their bibliography entries, but bibliography entries link back to citations!
First, install with npm:
``sh`
npm install eleventy-plugin-citations --save-dev
Then add it to your .eleventy.js config file:
`js`
import citations from 'eleventy-plugin-citations';
Then in your config function:
`js`
eleventyConfig.addPlugin(citations);
You can also provide options (described below) to customize the plugin behavior, e.g.:
`js`
eleventyConfig.addPlugin(citations, {
citationTemplate: "_includes/partials/_citations.njk",
bibliography: "references.bib",
style: "acm-sigchi.csl",
});
You either use the bibliography plugin config option or bibliography as a data key
(which could be global data, directory data, or even page data, you know the drill).
E.g. you can have a bibliography.json global data file like this:
`json`
[
"references.bib",
"references2.bib"
]
or you can specify it in your frontmatter like this:
`yaml`
bibliography: [references.bib, references2.bib]
Specifying values lower down the hierarchy does not override values higher up, the result is merged, i.e. uses all specified bib files.
Strings are also supported, but are not recommended as they override their ancestor values.
Arrays are also compatible with Pandoc Citer
though keep in mind that relative links are resolved differently.
The plugin adds the following:
- A citations filtercitations
- A paired shortcode
You use whichever of the two is convenient to pick up & format citations in your content.
See below for the citation syntax.
These do double duty: they pick up references for bibliography, and they format the citations in the text.
this means that only text that has gone through one of the two will be collected for the bibliography.
For the filter, you need to also add | safe after it so that the HTML it returns can be rendered.
`njk`
{{ "See [@doe99; @smith2000]" | citations | safe }}
You can provide your own template for rendering the citation via the citationTemplate option,citationRender
or a function that takes the citation info and returns the text of the formatted citation via the option.
By default, the plugin will use its internal citation template for this, which looks like this:
`njk`
{%- for part in parts -%}
{%- if part.citation -%}
{{ part.text }}
{%- else -%}
{{ part | safe }}
{%- endif -%}
{%- endfor -%}
The plugin adds the following:
- A references computed data property that resolves to the page’s own referencesreferencesByPage
- A global data object that contains references for all pages. You can get another page’s references by using referencesByPage.get(otherPage) or referencesByPage.get(otherPageURL).bibliography_citation
- A filter that takes an id as input and returns a formatted citation for use in the bibliography.bibliography_entry
- A filter that takes an id as input and returns a formatted reference for use in the bibliography.doi_link
It can optionally take an options parameter.
Currently the only option is which will linkify any DOI links"id"
(use value for the link text to be the id, "url" to just linkify the URL, or provide your own template).
You can use these however you want to generate the bibliography or just use the demo _references.njk if you’re looking for something quick.
This is an example of a very bare-bones bibliography,
similar to what LaTeX would generate:
`njkBibliography
You can check out the demo reference template (and its CSS) for a more complex example
including backlinks, highlighting of missing entries, nicer DOI links, and more.
Citation syntax
The citation syntax supported is a subset of the Pandoc citation syntax.
Basically ids only, without any locator information.
We also parse the same citation flags from
but don’t yet do anything with them.| Example | Description | Parsed? | Supported? |
| ------- | ----------- | ------- | ---------- |
|
[@doe99] | Single citation | ✅ | ✅ |
| [@doe99; @smith2000] | Multiple citations separated by semicolons | ✅ | ✅ |
| [-@doe99] | Suppress author | ✅ | 🚫 |
| [!@doe99] | Author-only | ✅ | 🚫 |
| [~@doe99] | Inline | ✅ | 🚫 |
| @doe99 | Citation without brackets | 🚫 | 🚫 |
| [@{https://example.com/bib?name=foobar&date=2000}, p. 33] | URLs as keys | 🚫 | 🚫 |
| [see @doe99] | Prefix | 🚫 | 🚫 |
| [@doe99, and passim] | Suffix | 🚫 | 🚫 |Confuguration Options
| Name | Type | Default | Description |
| ---- | ---- | ------- | ----------- |
|
citationTemplate | string | - | The path to the Nunjucks template that will be used to format the citations. |
| citationRender | function | _(See prose)_ | A function that takes info about a citation sequence and returns an HTML string |
| style | string or object | style-vancouver | The CSL style to use for formatting the references, either as an object or a path to a CSL XML file. |
| locale | string or object | locale-en-us | The locale to use for formatting the references, either as an object or a path to a locale CSL XML file. |
| bibliography | string or string[] | - | One or more global BiBTeX files. In case of duplicate keys, later wins. These will be merged with any BiBTeX files provided via the data cascade and will have lower priority. |CSL Styles and Locales
CSL is an XML-based standard to describe citation styles.
Several popular locales and styles are available as NPM packages.
$3
This plugin has been tested and verified to work with the most popular styles, and a few others.
| Style | Tested? | Text citation | Bibliography citation |
| ----- | ------- | ------------- | --------------------- |
| Vancouver | ✅ (default) | (1) | 1. |
| Nature | ✅ | 1 | [1] |
| APA | ✅ | (Doe et al., 1999) | [doe99] |
| Chicago | ✅ | (Doe et al., 1999) | [doe99] |
| MLA | ✅ | (Doe et al., 1999) | [doe99] |
| RSC | ✅ | 1 | 1 |
Note: Nature, APA, and Chicago use the same overall citation style and appear to only differ in terms of how they format bibliography entries.
$3
| Locale | Tested? |
| ------ | ------- |
| en-US | ✅ (default) |
| en-GB | 🚫 |
| fr-FR | 🚫 |
| de-DE | 🚫 |
| es-ES | 🚫 |
Limitations & Known issues
$3
Editing bibliography files will not trigger a rebuild.
$3
While you provide CSL files for the style, the plugin had to make certain assumptions to afford the templating flexibility it provides,
since citeproc provides chunks of text or HTML, with no granularity for the different parts of the citation.
Locators are currently not supported in the citation syntax.
They are mostly parsed, but not output.
$3
I _may_ be open in merging PRs to support Eleventy v2 if the changes are minimal,
but I’m not interested in making extensive changes to the codebase to cater to the past.
Just migrate to 11ty 3, it’s the future!
$3
Yes, it would be _much_ better if bibliography paths specified in a specific Markdown file resolved relative to that file,
and is what Pandoc Citer expects too.
However, given how the data cascade works in 11ty, this is not possible, as we don’t know where each entry is coming from so we can resolve it based on the file that defined it, and we definitely don’t want to be resolving global bibliography files relative to each file that uses them!
$3
The
citations filter and {% citations %} shortcode do double duty: they format the citations AND collect them so they can print out references.
This means that when you print out page.references`, you are only printing out references that have been collected by then.There are certain things I did not need, and thus are deprioritized (see wrt tight deadline above):
- No support for Liquid templates. The plugin imports Nunjucks directly.
That said, as long as your citation template is a Nunjucks template, you should probably be fine.
- The citation template cannot use any of your other 11ty data or any custom filters etc.
This is because it imports Nunjucks directly and does not have access to the 11ty environment.
Happy to merge PRs on these, I just don’t have the time to do them myself.