dependency_order | example_app | repo | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
GitHub License:
Parity-6.0.0
Buy a license for use in closed source
You should use this if all of the below are true:
you've got an existing Jekyll site written using liquid templates
you want to use some of the hot new tools from the JS ecosystem
but you don't want to completely rewrite your build process.
If you're going to process your HTML with some tool that runs in Node.js (webpack, rollup, parcel, gulp, or anything else), that tool likely has its own asset map implementation.
Copy the [_includes/asset_map
directory]({{ page.repo }}/_includes) into your own _includes
directory.
{% for title in page.dependency_order %} {% assign content = site.api | where: "title", title %} {% include docs/api.md name=title content=content %} {% endfor %}
Example app to compile
{% for i in page.example_app %} {% capture f %}
// example/{{ i }}.js
{% include_relative assets/src/example/{{ i }}.js %}
{% endcapture %} {{ f | markdownify }} {% endfor%}