Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/fluid-project/eleventy-plugin-fluid
Eleventy plugin which provides common filters, shortcodes and transforms for Fluid Project websites.
https://github.com/fluid-project/eleventy-plugin-fluid
eleventy-filter eleventy-plugin eleventy-shortcode eleventy-transform
Last synced: 3 months ago
JSON representation
Eleventy plugin which provides common filters, shortcodes and transforms for Fluid Project websites.
- Host: GitHub
- URL: https://github.com/fluid-project/eleventy-plugin-fluid
- Owner: fluid-project
- License: bsd-3-clause
- Created: 2020-09-29T20:01:46.000Z (about 4 years ago)
- Default Branch: main
- Last Pushed: 2024-08-06T16:23:43.000Z (3 months ago)
- Last Synced: 2024-08-07T03:28:33.529Z (3 months ago)
- Topics: eleventy-filter, eleventy-plugin, eleventy-shortcode, eleventy-transform
- Language: JavaScript
- Homepage:
- Size: 1.34 MB
- Stars: 1
- Watchers: 8
- Forks: 3
- Open Issues: 4
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE.md
- Authors: AUTHORS.md
Awesome Lists containing this project
- awesome-starred - fluid-project/eleventy-plugin-fluid - Eleventy plugin which provides common filters, shortcodes and transforms for Fluid Project websites. (others)
README
# eleventy-plugin-fluid
[](https://github.com/fluid-project/eleventy-plugin-fluid/blob/main/LICENSE.md)
[](https://github.com/fluid-project/eleventy-plugin-fluid/releases/latest/)
[](http://npmjs.com/package/eleventy-plugin-fluid)
[](https://codecov.io/gh/fluid-project/eleventy-plugin-fluid)
Eleventy plugin which provides common filters, shortcodes and transforms for [Fluid Project](https://fluidproject.org) websites.
## Requirements
- Node >= 18
- Eleventy >= 2.0.1
- Infusion >= 4.6.0
## Installation
Add `eleventy-plugin-fluid` to your Eleventy-based static site by running:
```bash
npx install-peerdeps eleventy-plugin-fluid
```
(You can also run `npm install --save eleventy-plugin-fluid`, but you'll then need to install the specified [`infusion`](https://www.npmjs.com/package/infusion)
peer dependency in your project as well; the [`install-peerdeps`](https://www.npmjs.com/package/install-peerdeps)
command handles both at the same time.)
Then, in your Eleventy configuration file (usually `eleventy.config.js`), load the plugin as follows:
```js
const fluidPlugin = require("eleventy-plugin-fluid");
module.exports = function (config) {
config.addPlugin(fluidPlugin);
};
```
## Usage
For any options passed to `eleventy-plugin-fluid` in the configurations described below, you can override the default
rather than merging with it by passing the option with `override:` as a prefix to the key. For example, to override the
default options for the `css` configuration block, you could do the following:
```diff
const fluidPlugin = require("eleventy-plugin-fluid");
module.exports = function (config) {
- config.addPlugin(fluidPlugin);
+ config.addPlugin(fluidPlugin, {
+ "override:css": {
+ // Your options here.
+ }
+ });
};
```
Note that if you don't override required defaults when using this method, your configuration will not be valid, so
proceed with caution if you are using this technique.
### Asset Handling
`eleventy-plugin-fluid` includes configuration for processing and bundling Sass and CSS files using [Sass](https://sass-lang.com)
and [LightningCSS](https://lightningcss.dev/), and JavaScript files using [esbuild](https://esbuild.github.io).
#### CSS
By default, any CSS files found in the `./src/assets/styles/` directory or its children will be processed _unless the
filename begins with an underscore (`_`)_. For this reason, if you are using CSS partials via the [`@import`](https://lightningcss.dev/bundling.html#%40import)
rule, you should name them according to the pattern `_partial.css` to prevent them from being transformed as standalone
files (this convention will be familiar to those who have worked with Sass and Sass partials).
Options for LightningCSS may be modified by passing values to the `css` option when registering `eleventy-plugin-fluid`
in your config:
```diff
const fluidPlugin = require("eleventy-plugin-fluid");
module.exports = function (config) {
- config.addPlugin(fluidPlugin);
+ config.addPlugin(fluidPlugin, {
+ css: {
+ cssModules: true,
+ }
+ });
};
```
Default values are as follows:
```js
let options = {
/* Where should Eleventy look for CSS files to process? */
basePath: `./${eleventyConfig.dir.input || "src"}/assets/styles`,
/* Should CSS files be processed? */
enabled: true,
/* See: https://lightningcss.dev/minification.html */
minify: true,
/* Not yet supported, see https://github.com/fluid-project/eleventy-plugin-fluid/issues/170 */
sourceMap: false,
/* See: https://lightningcss.dev/transpilation.html#draft-syntax */
drafts: {
nesting: true
},
/* A Browserslist configuration string (see: https://browsersl.ist) */
browserslist: "> 1%"
};
```
If you wish to disable CSS processing altogether, set the `enabled` key of the `options.css` object to `false`.
If you wish to disable Browserslist altogether, you can pass an empty array (`[]`) to the `browserslist` key.
For more options, see the [LightningCSS docs](https://lightningcss.dev/docs.html).
#### Sass
Sass processing is disabled by default. When enabled, any Sass files with the `.scss` extension found in the
`./src/assets/styles/` directory or its children will be processed _unless the filename begins with an underscore (`_`)_.
To enable Sass and disable CSS, add the following configuration when registering `eleventy-plugin-fluid` in your config:
```diff
const fluidPlugin = require("eleventy-plugin-fluid");
module.exports = function (config) {
- config.addPlugin(fluidPlugin);
+ config.addPlugin(fluidPlugin, {
+ css: {
+ enabled: false
+ },
+ sass: {
+ enabled: true
+ }
+ });
};
```
Options for Sass may be modified by passing values to the `sass` option when registering `eleventy-plugin-fluid`
in your config:
```diff
const fluidPlugin = require("eleventy-plugin-fluid");
module.exports = function (config) {
- config.addPlugin(fluidPlugin);
+ config.addPlugin(fluidPlugin, {
+ css: {
+ enabled: false
+ },
+ sass: {
+ browserslist: '> 1.5%',
+ enabled: true
+ }
+ });
};
```
Default values are as follows:
```js
let options = {
/* Where should Eleventy look for Sass files to process? */
basePath: `./${eleventyConfig.dir.input || "src"}/assets/styles`,
/* Should Sass files be processed? */
enabled: false,
/* See: https://lightningcss.dev/minification.html */
minify: true,
/* Not yet supported, see https://github.com/fluid-project/eleventy-plugin-fluid/issues/170 */
sourceMap: false,
/* See: https://lightningcss.dev/transpilation.html#draft-syntax */
drafts: {
nesting: true
},
/* A Browserslist configuration string (see: https://browsersl.ist) */
browserslist: "> 1%"
};
```
Note that all of these will be passed to LightningCSS, not Sass, with the exception of `basePath`, `enabled`, and `sourceMap`.
If you wish to disable Sass processing altogether, set the `enabled` key of the `options.sass` object to `false`.
If you wish to disable Browserslist altogether, you can pass an empty array (`[]`) to the `browserslist` key.
For more options, see the [Sass](https://sass-lang.com/documentation/) and [LightningCSS docs](https://lightningcss.dev/docs.html).
#### JavaScript
By default, any JavaScript files with the `.js` extension found in the `./src/assets/scripts/` directory or its children
will be processed with [esbuild](https://esbuild.github.io) _unless the filename begins with an underscore (`_`)_.
Options for esbuild may be modified by passing values to the `js` option when registering `eleventy-plugin-fluid`
in your config:
```diff
const fluidPlugin = require("eleventy-plugin-fluid");
module.exports = function (config) {
- config.addPlugin(fluidPlugin);
+ config.addPlugin(fluidPlugin, {
+ js: {
+ target: "esnext"
+ }
+ });
};
```
Default values are as follows:
```js
let options = {
/* Where should Eleventy look for JavaScript files to process? */
basePath: `./${eleventyConfig.dir.input || "src"}/assets/scripts`,
/* Should JavaScript files be processed? */
enabled: true,
/* See: https://esbuild.github.io/api/#minify */
minify: true,
/* See: https://esbuild.github.io/content-types/#javascript */
target: "es2020",
basePath: `./${eleventyConfig.dir.output || "_site"}/assets/styles`
};
```
If you wish to disable JavaScript processing altogether, set the `enabled` key of the `options.js` object to `false`.
### Localization
`eleventy-plugin-fluid` adds support for localization using Eleventy's [i18n plugin](https://11ty.dev/docs/plugins/i18n/)
and [`eleventy-plugin-i18n-gettext`](https://github.com/sgissinger/eleventy-plugin-i18n-gettext) for string translation.
By default, the following languages are configured:
- `en`
- `en-CA`
- `en-US`
- `es`
- `fa`
- `fr`
- `pt-br`
You can add support for additional languages by passing values to the `supportedLanguages` option when registering
`eleventy-plugin-fluid` in your config:
```diff
const fluidPlugin = require("eleventy-plugin-fluid");
module.exports = function (config) {
- config.addPlugin(fluidPlugin);
+ config.addPlugin(fluidPlugin, {
+ supportedLanguages: {
+ de: {
+ // The slug which will be used in URLs to content in this language.
+ slug: "de",
+ // The slug which will be used to localize UIO (see: https://docs.fluidproject.org/infusion/development/localizationinthepreferencesframework#specifying-a-localization)
+ uioSlug: "de",
+ // The direction of the language.
+ dir: "ltr",
+ // The endonym of the language.
+ name: "Deutsch"
+ }
+ }
+ });
};
```
`eleventy-plugin-fluid` provides the following [global data](https://www.11ty.dev/docs/data-global-custom/):
```json
{
"defaultLanguage": "en",
"defaultLanguageDir": "ltr",
"supportedLanguages": {
"en": {
"slug": "en",
"uioSlug": "en",
"dir": "ltr",
"name": "English"
},
"en-CA": {
"slug": "en-ca",
"uioSlug": "en_CA",
"dir": "ltr",
"name": "English (Canada)"
},
"en-US": {
"slug": "en-us",
"uioSlug": "en_US",
"dir": "ltr",
"name": "English (United States)"
},
"es": {
"slug": "es",
"uioSlug": "es",
"dir": "ltr",
"name": "Español"
},
"fa": {
"slug": "fa",
"uioSlug": "fa",
"dir": "rtl",
"name": "فارسی"
},
"fr": {
"slug": "fr",
"uioSlug": "fr",
"dir": "ltr",
"name": "Français"
},
"pt-BR": {
"slug": "pt-br",
"uioSlug": "pt_BR",
"dir": "ltr",
"name": "Português (Brasil)"
}
}
}
```
The `defaultLanguage` can be overridden by passing a new value to the `defaultLanguage` options key when registering
`eleventy-plugin-fluid`.
By default, `eleventy-plugin-fluid` also configures a [`localesDirectory`](https://github.com/sgissinger/eleventy-plugin-i18n-gettext#localesdirectory)
for `eleventy-plugin-i18n-getttext` as `./src/_locales`. This can be overridden by passing a new value to the
`localesDirectory` options key when registering `eleventy-plugin-fluid`.
`eleventy-plugin-fluid` also provides two localization-related helpers:
#### `generatePermalink`
[`generatePermalink`](src/utils/generate-permalink.js) is used to generate localized permalinks for a collection type,
with full support for [pagination](https://www.11ty.dev/docs/pagination/). Here's an example, as used in an `11tydata.js`
file:
```js
const { EleventyI18nPlugin } = require("@11ty/eleventy");
const { generatePermalink } = require("eleventy-plugin-fluid");
const { _ } = require("eleventy-plugin-i18n-gettext");
module.exports = {
layout: "layouts/base.njk",
eleventyComputed: {
lang: data => EleventyI18nPlugin.LangUtils.getLanguageCodeFromInputPath(data.page.inputPath),
langDir: data => data.supportedLanguages[data.lang].dir,
locale: data => data.lang,
permalink: data => {
const locale = data.locale;
return generatePermalink(data, "pages", _(locale, "pages"), _(locale, "page"));
}
}
};
```
In this example, [`eleventy-plugin-i18n-gettext`](https://github.com/sgissinger/eleventy-plugin-i18n-gettext) is used
to localize the URL path for the collection. The `_()` method provided by `eleventy-plugin-i18n-gettext` requires a
variable called `locale` as its first parameter (see [this issue](https://github.com/sgissinger/eleventy-plugin-i18n-gettext/issues/22)).
#### `localizeData`
[`localizeData`](src/utils/localize-data.js) is used to localize [directory data](https://www.11ty.dev/docs/data-template-dir/)
for a directory of content in a specific language (where the directory name is the language code). Here's an example,
as used in an `11tydata.js` file:
```js
const { localizeData } = require("eleventy-plugin-fluid");
module.exports = () => {
return localizeData({}, __dirname);
};
```
This helper is a wrapper for [`i18n.enhance11tydata`](https://github.com/sgissinger/eleventy-plugin-i18n-gettext#i18nenhance11tydataobj-locale-dir).
#### Disabling String Translation
If you don't need string translation features in your project, you can disable string translation by setting the `i18n`
option to false when registering `eleventy-plugin-fluid` in your config:
```diff
const fluidPlugin = require("eleventy-plugin-fluid");
module.exports = function (config) {
- config.addPlugin(fluidPlugin);
+ config.addPlugin(fluidPlugin, {
+ i18n: false
+ });
};
```
Note that if you do this, you will need to remove any uses of the `localizeData` helper or
[`eleventy-plugin-i18n-gettext` functions](https://github.com/sgissinger/eleventy-plugin-i18n-gettext#api) in your
project.
#### Additional Reference
For additional information on setting up localization/internationalization, see:
- [Eleventy Internationalization plugin](https://www.11ty.dev/docs/plugins/i18n/)
- [`eleventy-plugin-i18n-gettext`](https://github.com/sgissinger/eleventy-plugin-i18n-gettext)
- [Trivet](https://github.com/fluid-project/trivet/#internationalization)
### Markdown Configuration
`eleventy-plugin-fluid` amends Eleventy's [default Markdown configuration](https://www.11ty.dev/docs/languages/markdown/#default-options)
as follows (for more information see [markdown-it](https://github.com/markdown-it/markdown-it#init-with-presets-and-options)):
```json
{
"html": true,
"linkify": true,
"typographer": true
}
```
Options for Markdown may be modified by passing values to the `markdown` option when registering `eleventy-plugin-fluid`
in your config:
```diff
const fluidPlugin = require("eleventy-plugin-fluid");
module.exports = function (config) {
- config.addPlugin(fluidPlugin);
+ config.addPlugin(fluidPlugin, {
+ markdown: {
+ options: {
+ breaks: "true"
+ }
+ }
+ });
};
```
You can also enable [`markdown-it` plugins](https://www.npmjs.com/search?q=keywords:markdown-it-plugin) when
registering `eleventy-plugin-fluid` as follows:
```diff
const fluidPlugin = require("eleventy-plugin-fluid");
module.exports = function (config) {
- config.addPlugin(fluidPlugin);
+ config.addPlugin(fluidPlugin, {
+ markdown: {
+ plugins: [
+ // The npm package name of the plugin, which must be installed in your project.
+ "markdown-it-emoji",
+ // The npm package name of the plugin, which must be installed in your project, and an options object for the plugin.
+ ["markdown-it-anchor", {}]
+ ]
+ }
+ });
};
```
### Filters
All examples use the [Nunjucks](https://mozilla.github.io/nunjucks/) template language. Eleventy supports a number of
other template languages; see Eleventy's [documentation on filters](https://www.11ty.dev/docs/filters/) for usage with
different template languages.
#### formatDate
Formats a date string.
```nunjucks
{{ "Sun Jun 21 2020 18:00:00 GMT-0300 (Atlantic Daylight Time)" | formatDate }}
```
Output: `June 21st, 2020`
Optionally, a [`locale` parameter](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl#locale_identification_and_negotiation)
can be supplied to format a date in a locale other than English.
```nunjucks
{{ "Sun Jun 21 2020 18:00:00 GMT-0300 (Atlantic Daylight Time)" | formatDate('fr') }}
```
Output: `21 juin 2020`
#### isoDate
Formats a date string to [ISO 8601](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toISOString)
format.
```nunjucks
{{ "Sun Jun 21 2020 18:00:00 GMT-0300 (Atlantic Daylight Time)") | isoDate }}
```
Output: `2020-06-21T21:00:00.000Z`
#### limit
Trims an array to the specified length.
```nunjucks
{{ ["a", "b", "c"] | limit(2) | dump }}
```
Output: `["a", "b"]`
#### markdown
Processes an input string using [Markdown](https://www.11ty.dev/docs/languages/markdown/).
```nunjucks
{{ "A paragraph with some _emphasis_." | markdown | safe }}
```
Output: `
A paragraph with some emphasis.
\n`
#### slug (deprecated)
Processes an input string by lowercasing it, replacing whitespace with hyphens, and stripping special characters to
create a URL-safe version.
**NOTE: This filter is deprecated and the `slug-filter.js` file has been removed as of eleventy-plugin-fluid 1.0.
Instead, use Eleventy's new [`slugify`](https://www.11ty.dev/docs/filters/slugify/) filter.**
#### split
Splits an input string into an array based on a provided delimiter.
```nunjucks
{{ "a,b,c" | split(",") | dump }}
```
Output: `["a", "b", "c"]`
### Shortcodes
All examples use the [Nunjucks](https://mozilla.github.io/nunjucks/) template language. Eleventy supports a number of
other template languages; see Eleventy's [documentation on shortcodes](https://www.11ty.dev/docs/shortcodes/) for usage with
different template languages.
#### figure
Outputs a `` element with a ``. The first and second parameters in the opening tag of the shortcode
are the image URL and alternative text respectively. Caption content, which can use Markdown, goes in between the
opening and closing shortcode tags.
```nunjucks
{% figure "/assets/image.png", "A description of this image." %}
An illustration of something, found [here](https://example.com).
{% endfigure %}
```
Output:
```html
An illustration of something, found here.
```
#### renderString
Renders a string with a supported [template engine](https://www.11ty.dev/docs/languages/) using the Eleventy [Render plugin](https://www.11ty.dev/docs/plugins/render/).
This can be particularly useful when front matter data from a template needs to be processed using Markdown.
```md
---
title: About
subtitle: Learn about our [mission](/about/mission/), [vision](/about/vision/), and [values](/about/values/).
---
This is what we do.
```
```nunjucks
{{ title }}
{% renderString subtitle, "md" %}
{{ content | safe }}
```
Result:
```html
About
This is what we do.
```
By default, the following template formats are supported:
- [HTML (`html`)](https://11ty.dev/docs/languages/html/)
- [Markdown (`md`)](https://11ty.dev/docs/languages/markdown/)
- [WebC (`webc`)](https://11ty.dev/docs/languages/webc/)
- [JavaScript (`11ty.js`)](https://11ty.dev/docs/languages/javascript/)
- [Liquid (`liquid`)](https://11ty.dev/docs/languages/liquid/)
- [Nunjucks (`njk`)](https://11ty.dev/docs/languages/nunjucks/)
- [Handlebars (`hbs`)](https://11ty.dev/docs/languages/handlebars/)
- [Mustache (`mustache`)](https://11ty.dev/docs/languages/mustache/)
- [EJS (`ejs`)](https://11ty.dev/docs/languages/ejs/)
- [Haml (`haml`)](https://11ty.dev/docs/languages/haml/)
- [Pug (`pug`)](https://11ty.dev/docs/languages/pug/)
For example, you could enable [Vue](https://github.com/11ty/eleventy-plugin-vue) support when registering
`eleventy-plugin-fluid` as follows:
```diff
const fluidPlugin = require("eleventy-plugin-fluid");
+ const eleventyVue = require("@11ty/eleventy-plugin-vue");
module.exports = function (config) {
+ config.addPlugin(eleventyVue);
- config.addPlugin(fluidPlugin);
+ config.addPlugin(fluidPlugin, {
+ templateFormats: [
+ "vue"
+ ]
+ });
};
```
#### uioStyles
Outputs links to the required CSS assets for an instance of [Infusion User Interface Options][1]. Use this when you want
the out-of-the-box/drop-in experience with UI Options styles overriding the site styles. This is the quickest way to
start, but harder to customize and fit with your site's own styling.
```nunjucks
{% uioStyles %}
```
Result:
```html
```
#### uioStyleProps
Outputs links to the required CSS assets for an instance of [Infusion User Interface Options][1]. This only includes the
related CSS Custom Properties. Use this when you want to have control over how the enactor styles are applied.
See: [Integrating UI Options Styling Preferences](https://docs.fluidproject.org/infusion/development/tutorial-userinterfaceoptions/integratinguioptionsstylingpreferences)
```nunjucks
{% uioStyleProps %}
```
Result:
```html
```
#### uioScripts
Outputs links to the required JavaScript assets for an instance of [Infusion User Interface Options][1].
```nunjucks
{% uioScripts %}
```
Result:
```html
```
#### uioTemplate
Outputs the required HTML template markup for an instance of [Infusion User Interface Options][1]. This should used
directly after the opening `` tag.
```nunjucks
{% uioTemplate %}
```
Result:
```html
```
If you want to use a custom integration of User Interface Options, you can insert the required markup directly into your
[base template](https://github.com/fluid-project/fluidic-11ty/blob/main/src/_includes/layouts/base.njk).
#### uioInit
Outputs the required JavaScript to initialize an instance of [Infusion User Interface Options][1]. This should used
directly before the closing `` tag.
```nunjucks
{% uioInit %}
```
Result:
```html
fluid.uiOptions.multilingual(".flc-prefsEditor-separatedPanel", {
"auxiliarySchema": {
"terms": {
"templatePrefix": "/lib/infusion/src/framework/preferences/html",
"messagePrefix": "/lib/infusion/src/framework/preferences/messages"
},
"fluid.prefs.tableOfContents": {
"enactor": {
"tocTemplate": "/lib/infusion/src/components/tableOfContents/html/TableOfContents.html",
"tocMessage": "/lib/infusion/src/framework/preferences/messages/tableOfContents-enactor.json",
"ignoreForToC": {
"ignoreClass": ".flc-toc-ignore"
}
}
}
},
"prefsEditorLoader": {
"lazyLoad": true
}
});
```
Optionally, to support localization, you can pass in locale and direction arguments.
```nunjucks
{% uioInit "fa", "rtl" %}
```
Result:
```html
fluid.uiOptions.multilingual(".flc-prefsEditor-separatedPanel", {
"auxiliarySchema": {
"terms": {
"templatePrefix": "/lib/infusion/src/framework/preferences/html",
"messagePrefix": "/lib/infusion/src/framework/preferences/messages"
},
"fluid.prefs.tableOfContents": {
"enactor": {
"tocTemplate": "/lib/infusion/src/components/tableOfContents/html/TableOfContents.html",
"tocMessage": "/lib/infusion/src/framework/preferences/messages/tableOfContents-enactor.json",
"ignoreForToC": {
"ignoreClass": ".flc-toc-ignore"
}
}
}
},
"prefsEditorLoader": {
"lazyLoad": true
},
"locale": "fa",
"direction": "rtl"
});
```
If you want to use a custom integration of User Interface Options, you can insert the required script tag directly into your
[base template](https://github.com/fluid-project/fluidic-11ty/blob/main/src/_includes/layouts/base.njk).
### Template Languages
#### WebC
`eleventy-plugin-fluid` adds the [Eleventy WebC plugin](https://www.11ty.dev/docs/languages/webc/) for WebC support. By
default, the plugin will look for WebC components in `./src/_components/**/*.webc`. This, and [other options](https://www.11ty.dev/docs/languages/webc/#installation),
can be modified when registering `eleventy-plugin-fluid`:
```diff
const fluidPlugin = require("eleventy-plugin-fluid");
module.exports = function (config) {
- config.addPlugin(fluidPlugin);
+ config.addPlugin(fluidPlugin, {
+ webc: {
+ components: "./src/_includes/**/*.webc"
+ }
+ });
};
```
### Transforms
#### HTML Minify
`eleventy-plugin-fluid` adds an HTML minify transform to output files with a `.html` extension which minifies them
using [`html-minifier`](https://www.npmjs.com/package/html-minifier).
## Passthrough Copy
By default, `eleventy-plugin-fluid` copies the [required assets](src/config/uio-assets.json) for an instance of
[Infusion User Interface Options][1] into the `lib/infusion` directory of the build directory.
[1]: https://docs.fluidproject.org/infusion/development/tutorial-userInterfaceOptions/UserInterfaceOptions.html
## Development
### Releasing
This package uses [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/), enforced with
[commitlint](https://commitlint.js.org/). This facilitates releasing new versions of the package via [Release Please](https://github.com/googleapis/release-please).
To cut a release, merge the current [release pull request](https://github.com/google-github-actions/release-please-action#whats-a-release-pr).
This will tag an appropriate [semantic version](https://semver.org) based on the nature of the recent commits to the
project and update [the changelog](CHANGELOG.md).
You will then need to publish the updated version to the [npm registry](http://npmjs.com). This requires an npm account
with appropriate maintainer permissions. To publish the package, run:
```bash
npm publish
```
For more information on publishing to npm, see the [npm publish documentation](https://docs.npmjs.com/cli/publish).
## Third Party Software in `eleventy-plugin-fluid`
`eleventy-plugin-fluid` is based on other publicly available software, categorized by license:
### ISC License
- [eleventy-plugin-lightningcss](https://github.com/5t3ph/eleventy-plugin-lightningcss)
- [eleventy-plugin-sass-lightningcss](https://github.com/5t3ph/eleventy-plugin-sass-lightningcss)
### MIT License
- [deepMerge.js](https://vanillajstoolkit.com/helpers/deepmerge/)