Figure github location npm version

The vf-figure component can be used to display and caption diagrams, illustrations, photos, etc. This is to be used as a 'single' item of content that if it was removed from the page or have its position moved in the DOM it would not affect the pages other content.

Variants


hello alt text
Version, 1982, Adenovirus with 217 dots
Nunjucks syntax

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 (exampe), 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": "Version, 1982, Adenovirus with 217 dots",
  "alttext": "hello alt text",
  "imageUrl": "../../assets/vf-figure/assets/figure-example.png"
}
 %}
{% include "../path_to/vf-figure/vf-figure.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-figure', {
  "component-type": "element",
  "text": "Version, 1982, Adenovirus with 217 dots",
  "alttext": "hello alt text",
  "imageUrl": "../../assets/vf-figure/assets/figure-example.png"
} %}
                
HTML
<figure class="vf-figure">

  <img class="vf-figure__image" src="../../assets/vf-figure/assets/figure-example.png" alt="hello alt text" loading="lazy">

  <figcaption class="vf-figure__caption">Version, 1982, Adenovirus with 217 dots</figcaption>

</figure>
              
hello alt text
Version, 1982, Adenovirus with 217 dots
Nunjucks syntax

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 (exampe), 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": "Version, 1982, Adenovirus with 217 dots",
  "alttext": "hello alt text",
  "imageUrl": "../../assets/vf-figure/assets/figure-example.png",
  "vf_figure__align_inline_start": true
}
 %}
{% include "../path_to/vf-figure/vf-figure.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-figure', {
  "component-type": "element",
  "text": "Version, 1982, Adenovirus with 217 dots",
  "alttext": "hello alt text",
  "imageUrl": "../../assets/vf-figure/assets/figure-example.png",
  "vf_figure__align_inline_start": true
} %}
                
HTML
<figure class="vf-figure vf-figure--align vf-figure--align-inline-start">

  <img class="vf-figure__image" src="../../assets/vf-figure/assets/figure-example.png" alt="hello alt text" loading="lazy">

  <figcaption class="vf-figure__caption">Version, 1982, Adenovirus with 217 dots</figcaption>

</figure>
              
hello alt text
Version, 1982, Adenovirus with 217 dots
Nunjucks syntax

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 (exampe), 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": "Version, 1982, Adenovirus with 217 dots",
  "alttext": "hello alt text",
  "imageUrl": "../../assets/vf-figure/assets/figure-example.png",
  "vf_figure__align_inline_end": true
}
 %}
{% include "../path_to/vf-figure/vf-figure.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-figure', {
  "component-type": "element",
  "text": "Version, 1982, Adenovirus with 217 dots",
  "alttext": "hello alt text",
  "imageUrl": "../../assets/vf-figure/assets/figure-example.png",
  "vf_figure__align_inline_end": true
} %}
                
HTML
<figure class="vf-figure vf-figure--align vf-figure--align-inline-end">

  <img class="vf-figure__image" src="../../assets/vf-figure/assets/figure-example.png" alt="hello alt text" loading="lazy">

  <figcaption class="vf-figure__caption">Version, 1982, Adenovirus with 217 dots</figcaption>

</figure>
              
hello alt text
Version, 1982, Adenovirus with 217 dots
Nunjucks syntax

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 (exampe), 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": "Version, 1982, Adenovirus with 217 dots",
  "alttext": "hello alt text",
  "imageUrl": "../../assets/vf-figure/assets/figure-example.png",
  "vf_figure__align_centered": true
}
 %}
{% include "../path_to/vf-figure/vf-figure.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-figure', {
  "component-type": "element",
  "text": "Version, 1982, Adenovirus with 217 dots",
  "alttext": "hello alt text",
  "imageUrl": "../../assets/vf-figure/assets/figure-example.png",
  "vf_figure__align_centered": true
} %}
                
HTML
<figure class="vf-figure vf-figure--align vf-figure--align-centered">

  <img class="vf-figure__image" src="../../assets/vf-figure/assets/figure-example.png" alt="hello alt text" loading="lazy">

  <figcaption class="vf-figure__caption">Version, 1982, Adenovirus with 217 dots</figcaption>

</figure>
              

Usage

The vf-figure component can be used within any existing Visual Framework layout component. The size of the vf-figure is dictated by the size of the image rather and responds to the browser viewport if the viewport is smaller. The vf-figure component also has some alignment class selectors available which can float or centre the component in and around the other content on the page.

Class Selectors

Nunjucks Props

To avoid any mistyping, forgetfulness, and to aid in future proofing the component. We are using 'pseudo props' in nunjucks to determine which CSS selectors to use. All props do nothing unless included in your data for the component.

Props available

Installation info

This component is distributed with npm. After installing npm, you can install the vf-figure with this command.

$ yarn add --dev @visual-framework/vf-figure

Sass/CSS

The source files included are written in Sass(scss). You can point your Sass include-path at your node_modules directory and import it like this.

@import "@visual-framework/vf-figure/index.scss";

Make sure you import Sass requirements along with the modules. You can use a project boilerplate or the vf-sass-starter

Changelog

Changelog

1.0.23

  • small change to cards on homepage

1.0.18

  • dependency bump

1.0.17

  • dependency bump

1.0.16

  • dependency bump

1.0.13

  • dependency bump
  • adds roamap and consultation docs

1.0.12

  • design token documenation now lives in the component libary

1.0.7

  • adds updates blog

1.0.6

  • begin to make more pattern/boilerplate guidance
  • minor templating updates

1.0.5

  • dependency bump

1.0.4

  • uses vf-favicon
  • adds meta attributes

1.0.3

  • run vf-component-assets:everything on local dev
  • remove reference to removed /css/app.css

1.0.2

  • Add 404
  • Fix component CSS generation

1.0.1

  • Also generate per-component CSS with vf-css:generate-component-css

1.0.0

  • Initial release to be used with vf-core 2.2.0

Assets



File system location: components/vf-figure

Find an issue on this page? Propose a change or discuss it.