Link github location npm version


Variants


A text link A text link with :hover A text link with :visited A text link that is disabled

This is an example of using inline links when you are using the .vf-content container.

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 (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",
  "link_href": "JavaScript:Void(0);",
  "buttonType": "default"
}
 %}
{% include "../path_to/vf-link/vf-link.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-link', {
  "component-type": "element",
  "link_href": "JavaScript:Void(0);",
  "buttonType": "default"
} %}
                
HTML
<div class="vf-stack vf-stack--400">
  <!-- Primary -->
  <a href="JavaScript:Void(0);" class="vf-link">A text link</a>
  <!-- Primary Hover -->
  <a href="JavaScript:Void(0);" class="vf-link vf-link--hover">A text link with :hover</a>
  <!-- Primary Visited -->
  <a href="JavaScript:Void(0);" class="vf-link vf-link--visited">A text link with :visited</a>
  <!-- Primary Disabled -->
  <a href="JavaScript:Void(0);" class="vf-link" disabled>A text link that is disabled</a>

  <p class="vf-u-margin__bottom--0 vf-text-body vf-text-body--2">This is an example of using <a href="JavaScript:Void(0);">inline links</a> when you are using the <code>.vf-content</code> container.</p>
</div>
              
Installation info

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

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

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-link/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.1.2

  • Implements updated vf-search markup.
  • Changes a few pages on how it works with nunjucks and markdown.

1.1.0

  • updates Design Tokens homepage.
  • adds neutral colour tokens
  • adds 'status banners' for components in the documentation page.
  • Adds the form options as their own set of components in the list.
  • https://github.com/visual-framework/vf-core/pull/1390/files
  • Updates to use 11ty 0.12.1
  • https://github.com/visual-framework/vf-core/pull/1435

1.0.24

  • changes the vf-intro so it's a white background, removes the padding.
  • changes the links in vf-intro to be the 'correct' buttons.

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-link

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