https://github.com/foliant-docs/foliantcontrib.anchors
Arbitrary anchors for Foliant
https://github.com/foliant-docs/foliantcontrib.anchors
Last synced: 5 months ago
JSON representation
Arbitrary anchors for Foliant
- Host: GitHub
- URL: https://github.com/foliant-docs/foliantcontrib.anchors
- Owner: foliant-docs
- License: mit
- Created: 2019-03-21T13:53:37.000Z (about 7 years ago)
- Default Branch: master
- Last Pushed: 2021-07-20T09:53:13.000Z (almost 5 years ago)
- Last Synced: 2025-11-02T14:14:35.279Z (7 months ago)
- Language: Python
- Size: 25.4 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Changelog: changelog.md
- License: LICENSE
Awesome Lists containing this project
README
[](https://pypi.org/project/foliantcontrib.anchors/) [](https://github.com/foliant-docs/foliantcontrib.anchors)
# Anchors
Preprocessor which allows to use arbitrary anchors in Foliant documents.
## Installation
```bash
$ pip install foliantcontrib.anchors
```
## Config
To enable the preprocessor, add anchors to preprocessors section in the project config:
```yaml
preprocessors:
- anchors
```
The preprocessor has some options, but most probably you won't need any of them:
```yaml
preprocessors:
- anchors:
element: ''
tex: False
anchors: True
custom_ids: False
```
`element`
: Template of an HTML-element which will be placed instead of the `` tag. In this template `{anchor}` will be replaced with the tag contents. Ignored when tex is `True`. Default: `''`
`tex`
: If this option is `True`, preprocessor will try to use TeX-language anchors: `\hypertarget{anchor}{}`. Default: `False`
> Notice, this option will work only with `pdf` target. For all other targets it is set to `False`.
`anchors`
: If this options is `True`, anchors tag will be processed. Turn off if you only want to process custom IDs. Default: `True`
`custom_ids`
: Since version 1.0.5 preprocessor Anchors can also process Pandoc-style custom IDs. Set this option to `True` to do that. Default: `False`.
## Usage
**anchors**
Just add an `anchor` tag to some place and then use an ordinary Markdown-link to this anchor:
```html
...
limitation
Some important notice about system limitation.
...
Don't forget about [limitation](#limitation)!
```
You can also place anchors in the middle of paragraph:
```html
Lorem ipsum dolor sit amet, consectetur adipisicing elit.middle Molestiae illum iusto, sequi magnam consequatur porro iste facere at fugiat est corrupti dolorum quidem sapiente pariatur rem, alias unde! Iste, aliquam.
[Go to the middle of the paragraph](#middle)
```
You can place anchors inside tables:
```html
Name | Age | Weight
---- | --- | ------
Max | 17 | 60
Jane | 98 | 12
John | 10 | 40
Katy | 54 | 54
Mike Mike| 22 | 299
Cinty| 25 | 42
...
Something's wrong with Mike, [look](#Mike)!
```
**custom IDs**
Since version 1.0.5 preprocessor Anchors can also process [Pandoc-style custom heading identifiers](https://pandoc.org/MANUAL.html#heading-identifiers) (previously you had to use [CustomIDs preprocessor](https://foliant-docs.github.io/docs/preprocessors/customids/) for that purpose). To use this function, turn on the `custom_ids` option in your foliant.yml:
```yaml
preprocessors:
anchors:
...
custom_ids: True
```
Then add custom identifiers to your headings:
```
# My heading {#foo}
Lorem ipsum, dolor sit amet consectetur adipisicing elit. Omnis non vitae placeat sapiente reprehenderit officia.
```
After processing your text will be look like this:
```
# My heading
Lorem ipsum, dolor sit amet consectetur adipisicing elit. Omnis non vitae placeat sapiente reprehenderit officia.
```
## Additional info
**1. Anchors are case sensitive**
`Markdown` and `MarkDown` are two different anchors.
**2. Anchors should be unique**
You can't use two anchors with the same name in one document.
If preprocessor notices repeating anchors in one md-file it will throw you a warning. If you are building a flat document (e.g. PDF or docx with Pandoc), you will receive the warning even if anchor repeats in different md-files.
**3. Anchors may conflict with headers**
Headers are usually assigned anchors of their own. Be careful, your anchors may conflict with them.
Preprocessor will try to detect if you are using anchor which is already taken by the header and warn you in console.
**4. Some symbols are restricted**
You can't use these symbols in anchors:
```
[]<>\"
```
Also you can't use space.
**5. But a lot of other symbols are available**
All these are valid anchors:
```
!important!
_anchor_
section(1)
section/1/
anchor$1$
about:info
test'1';
якорь
👀
```
## Notice for Mkdocs
In many Mkdocs themes the top menu lays over the text with absolute position. In this situation all anchors will be hidden by the menu.
Possible solution is to change the `element` option for your anchors to have a vertical offset. Example config:
```yaml
preprocessors:
- anchors:
element: ''
```
Or, even better, you can assign your anchor a class in `element` and add these rules to your custom mkdocs styles.