This repository builds a plugin for Remarkable markdown parser that allows embedding external contents, e.g. videos, to Markdown documents.
The plugin provides a custom Markdown syntax that can be used in Markdown document to embed external contents using a URL, like embedding an image. It expects external contents to be available from the provided URL following the oEmbed specs.
Add remarkable-oembed
to your project using a package manager. For example:
Using yarn
:
yarn add @elasticpath/remarkable-oembed --dev
Using npm
:
npm install @elasticpath/remarkable-oembed --save-dev
Enable the remarkable-oembed
plugin and let Remarkable parse the markdown content:
const { Remarkable } = require('remarkable')
const remarkableOembed = require('@elasticpath/remarkable-oembed')
let md = new Remarkable().use(remarkableOembed)
md.render('!oembed[](https://www.youtube.com/watch?v=7ALwNmwYxBg)')
Above markdown content will be parsed and give you following html:
<div class="oembed oembed-video"><iframe src="https://www.youtube.com/embed/7ALwNmwYxBg?feature=oembed" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen="" width="200" height="113" frameborder="0"></iframe></div>
See the next section for more details on the syntax.
-
With an alternative text and title:
!oembed[alternative text](source url "title") !oembed[A Youtube video about Elastic Path Commerce Cloud](https://www.youtube.com/watch?v=7ALwNmwYxBg "What is Elastic Path Commerce Cloud")
-
With an alternative text only:
!oembed[alternative text](source url) !oembed[A Youtube video about Elastic Path Commerce Cloud](https://www.youtube.com/watch?v=7ALwNmwYxBg)
Note: Please make sure that there is no space between your source URL and the closing bracket.
!oembed[A Youtube video about Elastic Path Commerce Cloud](https://www.youtube.com/watch?v=7ALwNmwYxBg )
The Markdown above will not work.
-
With a title only:
!oembed[](source url "title") !oembed[](https://www.youtube.com/watch?v=7ALwNmwYxBg "What is Explains Elastic Path Commerce Cloud")
-
With no alternative text or title:
!oembed[](source url) !oembed[](https://www.youtube.com/watch?v=7ALwNmwYxBg)
You can add extra configuration to the oEmbed URL by adding extra query parameters to the end of the source url.
For instance, maxwidth
and maxheight
are two valid request parameters for rich
and video
type according to section 2.3.4.2. The video type and 2.3.4.4. The rich type from oembed. You can specify the width and height by adding &maxwidth=
and &maxheight=
to the end of the source url:
!oembed[](https://www.youtube.com/watch?v=7ALwNmwYxBg&maxwidth=100&maxheight=500)
There are also custom options implemented by each provider, e.g. theme
option for codesandbox. According to its documentation, you could trigger the light theme by adding ?theme=light
to the end of the source url:
!oembed[](https://codesandbox.io/s/react-new?theme=light)
Git is required if you would like to work with this repository on your local machine or would like to contribute changes to this repository.
This repository is also configured with "EditorConfig" to make sure everyone's favourite editor is configured the same way, such as: using spaces for indentation, new line at the end of file, etc. Some editors have built-in support for EditorConfig. Please download and install EditorConfig plugin for your Editor, if you're using one of the editors that does not have this support out of the box.
Below are some useful commands that can be executed from the root of this repository in your terminal.
-
./gradlew clean
: Removesbuild
directory so that you have a fresh build result. -
./gradlew rollup
: Bundles the.js
files for NPM release. -
./gradlew unit_test
: Runs the mocha unit tests for the source files insrc
directory. Generates reports inbuild/test-report
andbuild/coverage-report
directories as well as your terminal. -
./gradlew lint
: Runs the eslint for all.js
files. Generates reports inbuild/lint-report
directory as well as your terminal. -
./gradlew test
: Runs all test related gradle tasks, includingunit_test
andlint
.
Publishing to NPM and releasing in GitHub is automated by the CI/CD pipeline in this repo, and uses Semantic Release, commit messages must follow the format described in the documentation for a release to be triggered.