npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@visual-framework/vf-heading

v1.1.1

Published

vf-heading component

Downloads

2,073

Readme

Heading component

npm version

About

For basic heading formatting and sizes.

Usage

EMBL’s primary corporate typeface is IBM Plex Sans. Subdomains should use the same font except for cases where they have a different brand guideline.

The vf-heading component leverages the design token typography sizes.

Use heading tags, such as <h1> and <h2> to define the structure of a page. Apply tokens, such as vf-text-heading--1 to define the size and other stylistic elements of the heading. 

To establish a consistent content organisation throughout your site, style headings consistently. However, a heading level such as <h1> does not always need to correspond with the same token such as vf-text-heading--1. You can change the token if the page requires so but it is advisable to ensure the pages have a consistent heading structure whenever possible.

This component provides utility-like functionality and you'll rarely need to directly use this component. When coding a component's Sass, it will typically be better to use the mixins (@include set-type(text-heading--1);) than these vf-heading classes.

How to use

  • Every page should have at least one heading (typically a h1).
  • All text that looks like a heading should be marked up as a heading.
  • All text that is marked up as a heading should be a conceptual section heading.
  • The heading hierarchy should be meaningful, e.g: <h1>Recruitment: What to expect</h1> <h2>Our recruitment process</h2> <h3>Step 1: Application</h3>

Headings should be written in sentence case.

How not to use

  • Do not skip heading levels (e.g. from <h1> to <h3> without a <h4> on a page) as this causes issues to users of screen readers and other assistive technologies.
  • Do not use headings to style text that is not meant to be a heading element. Use a different vf-text style instead of a heading level for this type of text.

Related documentation

For more information on headings please consult the following documents:

Install

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

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

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-heading/index.scss";

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

Help