PatternFly Elements - Home PatternFly Elements v2 prerelease v1

Get started

Quick start

If you'd like to start exploring PatternFly Elements right away, checkout our Quick start demo page.

Install PatternFly Elements

Depending on the tool you use to manage dependencies (npm, Yarn, etc.) use the command line to install the components you’d like as a dependency of your project like this:

npm install --save @patternfly/pfe-card
npm install --save @patternfly/pfe-cta

This will install not only the pfe-card and pfe-cta, but also the base element, pfelement, and will save it to your package-lock.json. Depending on which browsers you support, you may also need to load the custom-elements and webcomponentsjs polyfills.

npm install --save @webcomponents/custom-elements
npm install --save @webcomponents/webcomponentsjs

Include PatternFly Elements JavaScript

There are a few options for including PatternFly Elements into your site or app.


If your site does not need to support older browser such as IE11, you may load the JavaScript via: script type="module". List out all the components you may include on your page, and the browser will fetch the dependencies dynamically on load. Learn more about JavaScript modules.

<script type="module" src="PATH/pfe-card.min.js"></script>
<script type="module" src="PATH/pfe-cta.min.js"></script>

In an app

Include the PatternFly Element web component and its dependencies within the app.

import '@patternfly/pfe-card/dist/pfe-card.min.js';
import '@patternfly/pfe-cta/dist/pfe-cta.min.js';

With require.js

Use require.js, a JavaScript file and module loader.

<!-- polyfills and require.js -->
<script src=""></script>
<script src=""></script>
<script src=""></script>


Load the scripts individually (not recommended)

Load individual PatternFly Element scripts, but bundle the polyfills with the base pfelement.js file. The order in which the scripts are loaded matters in this scenario. The pfelement.js base class needs to be loaded before any other component.

<script src="@patternfly/pfelement/dist/pfelement.umd.min.js">
<script src="@patternfly/pfe-card/dist/pfe-card.umd.min.js">
<script src="@patternfly/pfe-cta/dist/pfe-cta.umd.min.js">

Bundle everything

Bundle all of the scripts together into one rollup and include that.

Add PatternFly Elements markup

Add a call-to-action component.

  <a href="">PatternFly Elements</a>
PatternFly Elements

Add a card component.

  <h3 slot="pfe-card--header">Card header</h3>
  <p>This is the pfe-card body.</p>
  <div slot="pfe-card--footer">
    <p>This is the footer</p>

Card header

This is the pfe-card body.

This is the footer

Add attributes

Attributes can be used to adjust a theme, a palette color, a priority, set default values, etc. Be sure to check out the "Attributes" section for each component to see which attributes are available.

Change the priority of a call-to-action component using the priority attribute.

<pfe-cta priority="primary">
  <a href="">PatternFly Elements</a>
PatternFly Elements

Change the color value of a card component to change its appearance using the color attribute.

<pfe-card color="accent">
  <h3 slot="pfe-card--header">Card header</h3>
  <p>This is the pfe-card body.</p>
  <div slot="pfe-card--footer">
    <p>This is the footer</p>

Card header

This is the pfe-card body.

This is the footer

Use CSS variables to customize or theme your components

CSS variables are subject to the normal cascade, so consider where you want these overrides to propogate.

Page-level CSS, theme variables

Theme variables will impact all components on the page where this CSS is loaded.

// your-page.css
:root {
  --pfe-theme--color--ui-accent: green;
  --pfe-theme--color--surface--darker: navy;

Note: overriding local variables (i.e., –pfe-cta–foo) will not work at this level. Those overrides can only be done on the component via tag name, class, or ID.

Page-level CSS, component variables

/* your-page.css */
pfe-cta {
  --pfe-cta--BackgroundColor: pink;
  --pfe-cta--Color: black;

pfe-band {
  --pfe-band--Padding--vertical: 34px;
  --pfe-band--BackgroundColor: green;
  --theme: saturated;

Component-level inline CSS

As a last resort, you may choose to override variables with inline styles. This could be desirable if you only need one component to deviate from the design system. Note that this incurs some level of risk, especially related to colors, as you are opting out of the color combinations in the system.

<pfe-cta style="--pfe-cta--BackgroundColor: pink">
  <a href="">PatternFly Elements</a>

Avoiding the flash of unstyled content (FOUC)

PatternFly Elements provides a stylesheet that causes the body[unresolved] attribute to avoid the flash of unstyled content (FOUC). Adding the unresolved attribute to the body tag will hide the entire page until all elements have upgraded or 2 seconds have passed, whichever happens first. By including the pfelement--noscript.css file (wrapped in a noscript tag), all content will be revealed immediately for pages without JavaScript turned on. To customize the wait time, update the value of the --pfe-reveal-delay variable (default 2 second delay) and the --pfe-reveal-duration variable (how long the reveal animation takes, default 0.1618 seconds).

<!DOCTYPE html>
<html lang="en">
  <meta charset="UTF-8">
  <meta name="viewport" content="width=device-width, initial-scale=1.0">
  <title>PatternFly Elements - Avoiding the FOUC</title>
    Add pfelement--noscript.min.css to reveal the content 
    immediately in case JavaScript is turned off 
      <link href="PATH/@patternfly/pfelement/dist/pfelement--noscript.min.css" rel="stylesheet">
  <!-- Add pfelement.min.css to the head -->
  <link rel="stylesheet" href="PATH/@patternfly/pfelement/dist/pfelement.min.css">
<!-- Add the unresolved attribute to the body tag -->
  The pfelement.js base class and pfelement.min.css file handle 
  the removal of the unresolved attribute 
<body unresolved>