Text element

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" : "element",
"text" : "This text is extra large",
"type" : 1,
 }
%}
{% include "../path_to/vf-text/vf-text.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-text', {
  "component-type" : "element",
  "text" : "This text is extra large",
  "type" : 1,}
%}
                

 <p class="vf-text-body vf-text-body--1">This text is extra large</p>
              

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" : "element",
"text" : "This text is large",
"type" : 2,
 }
%}
{% include "../path_to/vf-text/vf-text.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-text', {
  "component-type" : "element",
  "text" : "This text is large",
  "type" : 2,}
%}
                

 <p class="vf-text-body vf-text-body--2">This text is large</p>
              

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" : "element",
"text" : "This text is regular",
"type" : 3,
 }
%}
{% include "../path_to/vf-text/vf-text.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-text', {
  "component-type" : "element",
  "text" : "This text is regular",
  "type" : 3,}
%}
                

 <p class="vf-text-body vf-text-body--3">This text is regular</p>
              

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" : "element",
"text" : "This text is small",
"type" : 4,
 }
%}
{% include "../path_to/vf-text/vf-text.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-text', {
  "component-type" : "element",
  "text" : "This text is small",
  "type" : 4,}
%}
                

 <p class="vf-text-body vf-text-body--4">This text is small</p>
              

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" : "element",
"text" : "This text is extra small",
"type" : 5,
 }
%}
{% include "../path_to/vf-text/vf-text.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-text', {
  "component-type" : "element",
  "text" : "This text is extra small",
  "type" : 5,}
%}
                

 <p class="vf-text-body vf-text-body--5">This text is extra small</p>