Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/loup-brun/hugo-cite

πŸ“ Easily manage your bibliography and in-text citations with Hugo, the popular static-site generator.
https://github.com/loup-brun/hugo-cite

bibliography citations csl-json hugo shortcode static-site-generator

Last synced: 8 days ago
JSON representation

πŸ“ Easily manage your bibliography and in-text citations with Hugo, the popular static-site generator.

Awesome Lists containing this project

README

        

# Hugo Cite

πŸ“ Easily manage your bibliography and in-text citations with [Hugo](https://gohugo.io), the popular static-site generator.

[**Documentation site + demo β†’**](https://labs.loupbrun.ca/hugo-cite/)

---

⚠️ **Important note: APA is the only citation style currently available, and you must be aware that it does not match the entire APA spec.**
More styles may be added eventually (contributions welcome!), but given that they are extremely verbose to implement, this is unlikely to happen in a near future.

---

## Install

### 1. Download

Download Hugo Cite in the `themes/hugo-cite` directory, either by [cloning with Git](https://github.com/loup-brun/hugo-cite) (the preferred method) or by [downloading as a ZIP file](https://github.com/alex-shpak/hugo-book/archive/master.zip).

The Git way:

```bash
git submodule add https://github.com/loup-brun/hugo-cite.git themes/hugo-cite
```

Your project directory should then look like this:

```bash
# Your Hugo project directory
β”œβ”€β”€ config.yml
└── themes
└── hugo-cite
```

### 2. Configure

Edit the `theme` parameter in your Hugo config file and add `hugo-cite` after your theme.

```yaml
# config.yml
theme:
-
- hugo-cite
```

### 3. Add CSS

Reference the CSS somewhere in your HTML templates:

```html

```

## Usage

You must first provide a **[CSL-JSON](https://citeproc-js.readthedocs.io/en/latest/csl-json/markup.html) bibliography file**.
(Other formats, such as BiBTeX, are _not_ supported.)
In Zotero for instance, this can be accomplished by selecting the CSL-JSON format when exporting a collection.
Just include `bib` in the filename (such as `bibliography.json`,`oh-my-bib.json`, or simply `bib.json`) and save it inside your Hugo project directory.

Here is an example:

```bash
# Your Hugo project directory
β”œβ”€β”€ content
β”‚ β”œβ”€β”€ article1
β”‚ β”‚ β”œβ”€β”€ bib.json
β”‚ β”‚ └── index.md
β”‚ β”œβ”€β”€ article2
β”‚ β”‚ β”œβ”€β”€ image.jpg
β”‚ β”‚ β”œβ”€β”€ index.md
β”‚ β”‚ └── mr-bib.json
β”‚ └── article3
β”‚ β”œβ”€β”€ index.md
β”‚ └── oh-my-bib.json
└── path
└── to
└── bib.json
```

### Shortcodes

There are two shortcodes you can use in your content:

- **`{{< bibliography >}}`**: display a list of works.
- **`{{< cite >}}`**: render an in-text citation.

### Display a bibliography

#### Basic Example

By default, the `{{< bibliography >}}` shortcode will render all entries from a `bib.json` included in a [leaf bundle](https://gohugo.io/content-management/page-bundles/#leaf-bundles) (see directory example above).

```markdown

{{< bibliography >}}
```

#### Cited Works

You can restrict the list only to works cited on the page (with the use of in-text citations, see below):

```markdown

{{< bibliography cited >}}
```

#### File Defined in Front Matter

You can specify the path to a JSON file located *inside* the Hugo project directory in the content page’s **front matter** using the `bibFile` parameter.
This is especially useful when working with `cited` entries:

```markdown
---
title: My Article
bibFile: path/to/bib.json # path relative to project root
---

## Bibliography

{{< bibliography >}}
```

#### File Defined in Shortcode

Alternatively, you can specify the path to the CSL-JSON file at the shortcode level:

```markdown

{{< bibliography "path/to/bib.json" >}}
```

#### Combine Options

You can also **combine both options** (the path to the JSON file must come first):

```markdown

{{< bibliography "path/to/bib.json" cited >}}
```

**Note**: if you are working with a `cited` bibliography, you’ll have to specify the path to the JSON file in the front matter for in-text citations to access the same file.

#### Named Params

You can chose to use **named params** for clarity (the order does not matter here):

```markdown

{{< bibliography src="path/to/bib.json" cited="true" >}}
```

#### File From a URL

Thanks to Hugo’s [`getJSON`](https://gohugo.io/templates/data-templates/#data-driven-content) function, the path can also be a **URL**.
*Note however that this method may have some drawbacks if you are [reloading often](https://gohugo.io/templates/data-templates/#livereload-with-data-files), see the Hugo docs regarding potential issues.*

```markdown

{{< bibliography "http://example.com/my/bib.json" >}}
```

### Render in-text citations

Use the `{{< cite >}}` shortcode to render rich in-text citations.

Example:

```markdown

{{< cite "Lessig 2002" >}}
```

The citation key (in the above example, `Lessig 2002`) must match the `id` field of a reference in your CSL-JSON file.
You can make it look like an author-date format, or anything else.

Here’s an excerpt of a CSL-JSON file:

```json
[
{
"id": "Lessig 2002",
"author": [
{
"family": "Lessig",
"given": "Lawrence"
}
]
}
]
```

Using the citation key defined in the CSL-JSON, you can reference your entry in content files:

```markdown

Our generation has a philosopher.
He is not an artist, or a professional writer.
He is a programmer. {{< cite "Lessig 2002" >}}
```

#### Suppress Author

For an abbreviated in-text citation form, you can add a **dash** (`-`) at the beginning of your citation key:

```markdown

{{< cite "-Lessig 2002" >}}
```

The above would render `(2002)` rather than `(Lessig, 2002)`.

#### Cite a Page

You can also provide a **page** as the second positional parameter:

```markdown

{{< cite "Lessig 2002" 5 >}}
```

The example above will render `(Lessig, 2002, p. 5)` (note the `p.` was added by hugo-cite; you need not to add it).

#### Cite a Page Range

You can instead specify a **range of pages** using a **dash** `-`, which will output `pp.` before the page range (ensure there is no space between the page numbers):

```markdown

{{< cite "Lessig 2002" 5-6 >}}
```

The example above will render `(Lessig, 2002, pp. 5-6)`.

#### Combine Multiple Citations

You can combine **multiple citations** in a single block, using the **semi-colon** (`;`) separator (no spaces around the semi-colon):

```markdown

{{< cite "Lessig2002;Nussbaum2011;Dewey1938" >}}
```

The above would render `(Lessig, 2002; Nussbaum, 2011; Dewey, 1938)`.

Works with pagination too, **in the matching order** of the citation keys:

```markdown

{{< cite "Lessig2002;Nussbaum2011;Dewey1938" "5-6;;25" >}}
```

The above would render `(Lessig, 2002, pp. 5-6; Nussbaum, 2011; Dewey, 1938, p. 25)`.

## Cited Works

```markdown

{{< bibliography cited >}}
```

## Demo

Check out a working [online demo β†’](https://labs.loupbrun.ca/hugo-cite/demo/)

[![Screenshot featuring Hugo Cite](https://user-images.githubusercontent.com/9596476/79130193-88061600-7d74-11ea-9654-0dc8b3d5bd2d.png)](https://labs.loupbrun.ca/hugo-cite/demo/)

## License

[WTFPL](LICENSE)