Styleguide
-
Molecules
-
Components
- Auth Modal
- Banner
- Category Filter Menu
- Comparison Table
- Countdown Timer
- Expandable List
- Featured Event
- Flex Cols Img
- Flex Cols
- Form Contact Default
- Hall of Fame List
- Hero
- Ico Three Col
- Ico Two Col
- Info Bullets
- Logo Card Grid
- Logos XS
- Multi Ico List
- One Col
- Resource Thumbnail
- Security Details
- Stepline
- Subnav
- Two Col
-
Styles
Stepline
Description
The stepline component renders a specialized "stepline" based on data housed in the stepline yaml file (see: `src/_data/stepline`). It takes few inputs, relying on the data file to generate most of it's content.
Default Stepline
Rendered
This is a header
This is a subheader
Start by familiarizing yourself with the new file format. Watch this video, or check out the docs.
Use this script to see which projects are building on CircleCI 1.0. Stop building any inactive projects you don’t plan to migrate.
You can get your projects building on CircleCI 2.0 without impacting your team. Create a new branch for testing so your team can keep building while you get things set up.
The configuration translation endpoint will help you get started with your config file. You will want to tweak the output, but it should help you get started.
You can use the command line interface to validate your config changes with a pre-commit Git hook. This will help you avoid running a bunch of failed builds while you are fine-tuning your syntax. Read how in the docs or watch this video.
Options
classes
:string
tag
:string
- Defines the tag name to apply as a filter to the stepline data. This input is required.
Default Stepline
Code
{% include components/stepline.html
header="This is a header"
subheader="This is a subheader"
tag="eol" %}
Rendered
This is a header
This is a subheader
Start by familiarizing yourself with the new file format. Watch this video, or check out the docs.
Use this script to see which projects are building on CircleCI 1.0. Stop building any inactive projects you don’t plan to migrate.
You can get your projects building on CircleCI 2.0 without impacting your team. Create a new branch for testing so your team can keep building while you get things set up.
The configuration translation endpoint will help you get started with your config file. You will want to tweak the output, but it should help you get started.
You can use the command line interface to validate your config changes with a pre-commit Git hook. This will help you avoid running a bunch of failed builds while you are fine-tuning your syntax. Read how in the docs or watch this video.