A mdbook preprocessor that allows the re-usability of template files with dynamic arguments
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
Go to file
sgoudham 0a7e6fd504
[v0.1.0] - Separate all links logic into links.rs
3 years ago
.github [v0.1.0] - Add deploy.yml script 3 years ago
src [v0.1.0] - Separate all links logic into links.rs 3 years ago
.gitignore Add /.idea to .gitignore 3 years ago
CONTRIBUTING.md Add CONTRIBUTING.md 3 years ago
Cargo.toml Remove unused dependencies & add aho-corasick to substitute strings 3 years ago
LICENSE Initial commit 3 years ago
README.md [v0.1.0] - Add ##Format & ##Example sections 3 years ago

README.md

mdbook-template

build crate.io downloads license

A mdbook preprocessor that allows the re-usability of template files with variable arguments

Table of Contents

TODO

Author Notes

I'm still a beginner in terms of my Rust skills, so I'm definitely... probably sure that there are edge cases within this preprocessor.

Installation

Install Through Cargo

$ cargo install mdbook-template

Add the following line into your book.toml

[preprocessor.template]

You're good to go :D Continue building your mdbook normally!

$ mdbook build

About

Given the following directory structure

book.toml
src
├── one.md
├── two.md
├── two
│   └── three.md
├── images
│   ├── ferris.png
│   └── corro.png
└── SUMMARY.md

If we wanted to include the images ferris.png and corro.png within all the files through a footer, we'd have to copy the same piece of markdown/code in every file and set a unique path back to the images/ directory.

This is where mdbook-template can help.

Being based on the {{#include ... }} feature of mdbook, mdbook-template allows you to use familiar syntax to include files while passing in arguments to allow for dynamic generation of text.

Format

The format is as follows

        1             2           3
    {{#template     <file>      <args>}}
  1. The identifier that this text should be replaced
  2. The relative path to the template file
  3. Any arguments that should be substituted within the template file. Arguments should be seperated by whitespace and should be in the key=value format.

Arguments to be replaced within the template files should be wrapped in {}

Example

Given the following directory

book.toml
src
├── one.md
├── two.md
├── two
│   └── three.md
├── images
│   ├── ferris.png
│   └── corro.png
├── templates
│   └── footer.md
└── SUMMARY.md

and the following content

templates/footer.md

- - - - 
Designed By Goudham
![ferris]({path}/ferris.png)
![ferris]({path}/corro.png)

one.md

# One
Some Content...

{{#template templates/footer.md path=images}}

two.md

# Two
Some Content...

{{#template templates/footer.md path=images}}

two/three.md

# Three
Some Content...

{{#template templates/footer.md path=../images}}

After running mdbook build with the mdbook-template preprocessor enabled, the files will have dynamic paths to the images

one.md

# One
Some Content...

- - - - 
Designed By Goudham
![ferris](images/ferris.png)
![ferris](images/corro.png)

two.md

# Two
Some Content...

- - - - 
Designed By Goudham
![ferris](images/ferris.png)
![ferris](images/corro.png)

two/three.md

# Three
Some Content...

- - - - 
Designed By Goudham
![ferris](../images/ferris.png)
![ferris](../images/corro.png)

Further examples are included within the section which demonstrate a variety of usages.

License

MIT

Contributing

First, thanks for your interest in contributing to this project! Please read the CONTRIBUTING.md before contributing!

Acknowledgement

This preprocessor is heavily based off the links.rs file within mdbook itself. I definitely wouldn't have been able to mock up something like this without the strong foundations that mdbook already implemented.