- HTML 100%
| content/assets/images | ||
| includes | ||
| package | ||
| .gitignore | ||
| package-list.json | ||
| README.md | ||
fhir-ig-template
VWS look-and-feel in FHIR IG build template (e.g. icon, colors, header, footer).
Package id: nl.generiekefuncties.igtemplate — a child template of
fhir2.base.template.
Layout
| Path | Purpose |
|---|---|
package/package.json |
Template manifest; declares the base template and its version |
package-list.json |
Published version history of this template |
includes/ |
Liquid fragments that replace the base template's versions |
content/ |
Static files copied to the IG output (content/assets/images/x.svg → assets/images/x.svg) |
A file that does not exist in the base template is added; a file that does exist
replaces the base version. A file named _append.<name> is appended to <name>
from the base instead of replacing it.
Using it from an IG
In the IG's ig.ini, set template to
template = nl.generiekefuncties.igtemplate#<version>.
Constraints
nl.generiekefuncties.igtemplate is not on the IG Publisher's list of templates allowed
to execute scripts, so this template must stay passive: no script or targets
in a config.json, and only file types from the publisher's safe list
(.html, .css, .svg, .json, .xml, .md, .woff2, …).
includes/fragment-pagebegin.html is a full copy of the base template's file, so
it must be re-synced whenever fhir2.base.template changes that fragment.