Input form

Depending on your environment you'll want to use render or include. As a rule of thumb: server-side use include, precompiled browser use render. If you're using vf-eleventy you should use include.

Using include

You'll need to pass a context object from your code or Yaml file (example), as well as the path to the Nunjucks template. Nunjucks' include is an abstraction of render and provides some additional portability.

{% set context fromYourYamlFile %}
- or -
{% set context = {
  "component-type": "form"
}
 %}
{% include "../path_to/vf-form__input/vf-form__input.njk" %}
                

Using render

This approach is best for bare-bones Nunjucks environments, such as precompiled templates with the Nunjucks slim runtime where include is not be available.

{% render '@vf-form__input', {
  "component-type": "form"
} %}
                

<div class="vf-form__item">
  <label class="vf-form__label" for="text">Text</label>
  <input type="text" id="text" class="vf-form__input">
</div>
              

Depending on your environment you'll want to use render or include. As a rule of thumb: server-side use include, precompiled browser use render. If you're using vf-eleventy you should use include.

Using include

You'll need to pass a context object from your code or Yaml file (example), as well as the path to the Nunjucks template. Nunjucks' include is an abstraction of render and provides some additional portability.

{% set context fromYourYamlFile %}
- or -
{% set context = {
  "component-type": "form",
  "search_placeholder": "Search all of EMBL.org"
}
 %}
{% include "../path_to/vf-form__input/vf-form__input.njk" %}
                

Using render

This approach is best for bare-bones Nunjucks environments, such as precompiled templates with the Nunjucks slim runtime where include is not be available.

{% render '@vf-form__input', {
  "component-type": "form",
  "search_placeholder": "Search all of EMBL.org"
} %}
                

<div class="vf-form__item">
  <label class="vf-form__label" for="search">Search</label>
  <input type="search" id="search" class="vf-form__input" placeholder="Search all of EMBL.org">
</div>
              

Depending on your environment you'll want to use render or include. As a rule of thumb: server-side use include, precompiled browser use render. If you're using vf-eleventy you should use include.

Using include

You'll need to pass a context object from your code or Yaml file (example), as well as the path to the Nunjucks template. Nunjucks' include is an abstraction of render and provides some additional portability.

{% set context fromYourYamlFile %}
- or -
{% set context = {
  "component-type": "form",
  "search_placeholder": "Search this book"
}
 %}
{% include "../path_to/vf-form__input/vf-form__input.njk" %}
                

Using render

This approach is best for bare-bones Nunjucks environments, such as precompiled templates with the Nunjucks slim runtime where include is not be available.

{% render '@vf-form__input', {
  "component-type": "form",
  "search_placeholder": "Search this book"
} %}
                

<div class="vf-form__item">
  <label class="vf-form__label | vf-u-sr-only" for="search">Search</label>
  <input type="search" id="search" class="vf-form__input vf-form__input--filter" placeholder="Search this book">
</div>
              

Depending on your environment you'll want to use render or include. As a rule of thumb: server-side use include, precompiled browser use render. If you're using vf-eleventy you should use include.

Using include

You'll need to pass a context object from your code or Yaml file (example), as well as the path to the Nunjucks template. Nunjucks' include is an abstraction of render and provides some additional portability.

{% set context fromYourYamlFile %}
- or -
{% set context = {
  "component-type": "form",
  "invalid": true
}
 %}
{% include "../path_to/vf-form__input/vf-form__input.njk" %}
                

Using render

This approach is best for bare-bones Nunjucks environments, such as precompiled templates with the Nunjucks slim runtime where include is not be available.

{% render '@vf-form__input', {
  "component-type": "form",
  "invalid": true
} %}
                

<div class="vf-form__item">
  <label class="vf-form__label" for="text">Text</label>
  <input type="text" id="text" class="vf-form__input vf-form__input--invalid">
</div>
              

Depending on your environment you'll want to use render or include. As a rule of thumb: server-side use include, precompiled browser use render. If you're using vf-eleventy you should use include.

Using include

You'll need to pass a context object from your code or Yaml file (example), as well as the path to the Nunjucks template. Nunjucks' include is an abstraction of render and provides some additional portability.

{% set context fromYourYamlFile %}
- or -
{% set context = {
  "component-type": "form"
}
 %}
{% include "../path_to/vf-form__input/vf-form__input.njk" %}
                

Using render

This approach is best for bare-bones Nunjucks environments, such as precompiled templates with the Nunjucks slim runtime where include is not be available.

{% render '@vf-form__input', {
  "component-type": "form"
} %}
                

<div class="vf-form__item">
  <label class="vf-form__label" for="email">Disabled email</label>
  <input type="email" id="email" class="vf-form__input" disabled>
</div>
              

Depending on your environment you'll want to use render or include. As a rule of thumb: server-side use include, precompiled browser use render. If you're using vf-eleventy you should use include.

Using include

You'll need to pass a context object from your code or Yaml file (example), as well as the path to the Nunjucks template. Nunjucks' include is an abstraction of render and provides some additional portability.

{% set context fromYourYamlFile %}
- or -
{% set context = {
  "component-type": "form"
}
 %}
{% include "../path_to/vf-form__input/vf-form__input.njk" %}
                

Using render

This approach is best for bare-bones Nunjucks environments, such as precompiled templates with the Nunjucks slim runtime where include is not be available.

{% render '@vf-form__input', {
  "component-type": "form"
} %}
                

<div class="vf-form__item">
  <label class="vf-form__label" for="password">Password</label>
  <input type="password" id="password" class="vf-form__input">
</div>