https://github.com/djm/remark-shortcodes
A custom Markdown syntax parser for remark that adds support for shortcodes.
https://github.com/djm/remark-shortcodes
Last synced: about 1 month ago
JSON representation
A custom Markdown syntax parser for remark that adds support for shortcodes.
- Host: GitHub
- URL: https://github.com/djm/remark-shortcodes
- Owner: djm
- License: mit
- Created: 2017-09-08T12:52:26.000Z (over 7 years ago)
- Default Branch: master
- Last Pushed: 2022-06-22T04:20:54.000Z (almost 3 years ago)
- Last Synced: 2025-04-02T17:48:32.650Z (about 2 months ago)
- Language: JavaScript
- Homepage:
- Size: 380 KB
- Stars: 45
- Watchers: 1
- Forks: 7
- Open Issues: 5
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# remark-shortcodes [![NPM Package][npm-package-badge]][npm-package] [![Coverage Status][codecov-badge]][codecov]
A custom Markdown syntax parser for [**remark**][remark] that adds support for shortcodes.
## Update, January 2021
This package does not work with Remark v13+ due to its parser changes:
* If you would like to fix that, please [see this issue](https://github.com/djm/remark-shortcodes/issues/19).
* If you would like similiar functionality but with a different syntax - see the core-maintained [`remark-directive`](https://github.com/remarkjs/remark-directive) project.
## Summary
**_What are shortcodes?_** They are a way to provide hooks for macros and/or
template partials inside a markdown file. They consist of start & end blocks,
in between which the shortcode has a name defined and an optional set of
key:value attributes in HTML style. They can look like this:
```md
The example below uses the default start & end blocks that
this parser ships with:
[[ MailchimpForm id="chfk2" ]]
But they are configurable, so if you're coming from Hugo say,
you can set them as such:
{{< MailchimpForm id="chfk2" >}}
```
**_Why use them?_** Because sometimes you'd like to insert content inline
without copy pasting raw HTML in to your Markdown file. The copy paste
approach means that hard-to-modify code is littered throughout your
content and is therefore very hard to maintain; whereas the shortcode
approach can result in a partial being updated in only one place.
Both [Wordpress][wordpress-shortcodes] & [Hugo][hugo-shortcodes] have
support for shortcodes; this parser's implementation is much closer
to Wordpress's, as it does not support inner content or nested shortcodes
like Hugo does - but can actually be used for the simpler partials. It
was made for my use, but if you'd like to extend it to support more cases,
please feel free! Everyone is welcome.
## AST Block: `Shortcode`
`Shortcode` ([`Node`][node]) is a simple node that has an identifier and an
optional object with string values, respresenting the attributes parsed.
```idl
interface Shortcode <: Node {
type: "shortcode";
identifier: string;
attributes: { key: string, ...}
}
```
For example, the following markdown:
```md
[[ MailchimpForm id="chfk2" ]]
```
Yields:
```json
{
"type": "shortcode",
"identifier": "MailchimpForm",
"attributes": { "id": "chfk2" }
}
```
## Installation
[npm][npm]:
```bash
npm install --save remark-shortcodes
```
## Usage
Say `example.js` looks as follows:
```javascript
var unified = require('unified');
var parse = require('remark-parse');
var shortcodes = require('remark-shortcodes');
var markdown = 'Example paragraph\n\n{{> MailchimpForm id="chfk2" <}}'
var tree = unified()
.use(parse)
// Plugin inserted below, with custom options for start/end blocks.
.use(shortcodes, {startBlock: "{{>", endBlock: "<}}"})
// Turn off position output for legibility below.
.data('settings', {position: false})
.parse(markdown);
console.dir(tree, {depth: null});
```
Running `node example` yields:
```json
{
"type": "root",
"children": [
{
"type": "paragraph",
"children": [{ "type": "text", "value": "Example paragraph" }]
},
{
"type": "shortcode",
"identifier": "MailchimpForm",
"attributes": { "id": "chfk2" }
}
]
}
```
Say `example2.js` looks as follows:
```javascript
var unified = require('unified');
var parse = require('remark-parse');
var shortcodes = require('remark-shortcodes');
var ast = {
"type": "root",
"children": [
{
"type": "paragraph",
"children": [{ "type": "text", "value": "Example paragraph" }]
},
{
"type": "shortcode",
"identifier": "MailchimpForm",
"attributes": { "id": "chfk2" }
}
]
};
var tree = unified()
.use(parse)
// Plugin inserted below, with custom options for start/end blocks.
.use(shortcodes, {startBlock: "{{>", endBlock: "<}}"})
.stringify(ast);
console.log(tree);
```
Running `node example2` yields:
```markdown
Example paragraph\n\n{{> MailchimpForm id="chfk2" <}}
```
Say `example3.js` looks as follows:
```javascript
var unified = require('unified');
var parse = require('remark-parse');
var shortcodes = require('remark-shortcodes');
var markdown = 'Example paragraph {{> MailchimpForm id="chfk2" <}}'
var tree = unified()
.use(parse)
// Plugin inserted below, with custom options for start/end blocks.
.use(shortcodes, {startBlock: "{{>", endBlock: "<}}", inlineMode: true})
// Turn off position output for legibility below.
.data('settings', {position: false})
.parse(markdown);
console.dir(tree, {depth: null});
```
Running `node example3` yields:
```json
{
"type": "root",
"children": [
{
"type": "paragraph",
"children": [
{
"type": "text",
"value": "Example paragraph "
},
{
"type": "shortcode",
"identifier": "MailchimpForm",
"attributes": { "id": "chfk2" }
}
]
}
]
}
```
## API
### `remark.use(shortcodes, {options})`
Where options support the keys:
- `startBlock`: the start block to look for. Default: `[[`.
- `endBlock`: the end block to look for. Default: `]]`.
- `inlineMode`: shortcodes will be parsed inline rather than in block mode. Default: `false`.
NB: Be careful when using custom start/end blocks, your choices
may clash with other markdown syntax and/or other remark plugins.
## Testing
To run the tests, run:
npm run test-code
To run build, tests & coverage, run:
npm run test
CI is set up on push via a Github Action, see [workflows/nodejs.yml](https://github.com/djm/remark-shortcodes/blob/master/.github/workflows/nodejs.yml).
## Releasing
Prepare the commits:
- Bump all version numbers.
- Tag the commit: `git tag -a v0.1.x -m v0.1.x`
- Push tag to Github: `git push --tags`
Publish to npm:
- Ensure tag is checked-out: `git checkout tags/v0.1.x`
- Login to NPM via the CLI: `npm login`
- Publish the package: `npm publish`
## License
[MIT](LICENSE) © [Darian Moody](http://djm.org.uk)
With thanks to [woorm][woorm] et. al for [**remark**][remark].
[npm-package-badge]: https://img.shields.io/npm/v/remark-shortcodes.svg
[npm-package]: https://www.npmjs.org/package/remark-shortcodes
[codecov-badge]: https://img.shields.io/codecov/c/github/djm/remark-shortcodes.svg
[codecov]: https://codecov.io/github/djm/remark-shortcodes
[wordpress-shortcodes]: https://codex.wordpress.org/shortcode
[hugo-shortcodes]: https://gohugo.io/content-management/shortcodes/
[gatsby-remark-shortcodes]: https://gitub.com/djm/gatsby-remark-shortcodes
[npm]: https://docs.npmjs.com/cli/install
[node]: https://github.com/syntax-tree/unist#node
[remark]: https://github.com/wooorm/remark
[woorm]: https://github.com/wooorm