A card theme for Jekyll made awesome using Bulma.
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
src
.bowerrc
.gitignore
.ruby-version
.travis.yml
CONTRIBUTING.md
Gemfile
Gemfile.lock
README.md
_config.yml
bower.json
screenshot.png

README.md

Build Status

Jekyll Cards Boilerplate

A card theme for Jekyll made awesome using Bulma.

jekyll-cards-boilerplate

In the wild

Features

Dependencies

  1. Install bundler gem install bundler
  2. Install bower npm install -g bower

Getting Started

$ bundle install
$ bower install
$ jekyll serve

Cards

Cards should be saved as a yaml file in the src/_data folder (ex: src/_data/films.yml).

Feel free to add whatever metadata applies to your card. If present, the description field will be shown below your metadata.

Title
  - meta1: 1
  - meta2: two
  - description: "A short description"

Configure cards in _config.yml.

cards:
  data: films         # yaml file in _data (without .yml)
  comments: true      # toggle global comments on pages
  group_by:
    name: decade      # field in yaml to group by
    caption: decades  # name of category (ex: industries)  
    fa-icon: folder-open
    fa-style: far     # valid: fas (solid), far (regular), fal (light), fab (brand)
  meta:
    - name: year        # field in yaml to map
      caption: year
      fa-icon: calendar
      fa-style: far
    - name: url
      caption: www
      fa-icon: globe
      fa-style: fas

A page for each card will be automatically generated at /<cards.data>/<card.name>.html (ex: /films/the-room.html)

When you use the group_by section (currently required), all cards will be grouped into category pages located at /<cards.categories.name>/<value>.html (ex: /decades/1930s.html)

If you wish to override the comment configuration on a specific card, you may add a comments field to your cards entry (ex: comments: false)

Deploy to Github Pages from Travis CI

With the help of Travis, pushing to master will trigger a deploy to Github Pages automatically.

  1. Point Travis to repository
  2. Configure Travis
  3. Generate a Personal Access Token from Github
  • The only scope needed is repo:public_repo
  1. Set GITHUB_API=<token> on Travis
  • Make sure Display value in build log toggle is set to Off!
  1. Update src/CNAME