Generates your Github projects in HTML for your (static) website to use from a predefined template.
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.

Github Cards

Github Cards is a Jekyll plugin to create an easy-to-reference and stylable GitHub Card using a custom Liquid tag.

Here's an example of what it does, in context: example usage


In the past, there was a 1-liner (well, two, really) that would generate a nice looking github card. You would call it like so:

<div class="github-card" data-github="edward-shen/MMM-MBTA" data-width="400" data-height="157" data-theme="default"></div>

And place this line at the bottom of your website.

<script src="//"></script>

This is nice, except for a few things:

  1. Generates an iframe. This is dangerous, because you now rely on an external webserver to not serve malware.
  2. Relatively computationally complex for the client. Why require the user to generate HTML when it can simply served from the server?
  3. Difficult to style. You're kinda forced to follow the styling provided by the author of that script.

To be fair, it does have its uses, especially in forums that allow users to post raw HTML (But that in itself should be questioned), or if you're generating your websites manually.

Github Cards adapts this idea for use with Jekyll, with provides the following benefits.

  1. Safe. No need for iframes or external sources.
  2. Static. For the user, it's as lightweight as text -- the rendered output is pure HTML.
  3. Customizable. Don't like my style? Don't worry. You can customize it to any degree you want. Every major section has either a css class or semantic tag -- in some cases, both!


This is still an in-progress work.

First, make a folder (if one doesn't exist) in your site root called _plugins. This folder should be on the same level as _site. Then, drag github-cards.rb into the plugins.

In your jekyll Gemfile add the gem graphql-client to the Jekyll plugins group:

group :jekyll_plugins do


   gem "graphql-client"

Additionally, you'll need to create a Github Personal Access Token. Fear not, you don't need any permissions other than the default scope.

See this Github article on how to create your own.

Remember, you don't need any permissions other than the default scope.

Once you got one, add it to your _config.yml:

    github_access_token: "abc123"

Then, re-run bundle install.

You may realize that the cards won't update when someone else stars or forks the repo. This is an inherit consequence of generating static HTML. To resolve this, I've included a JS file that does the following:

  1. Checks if there's a cached version of the repo data, and if so, load it.
  2. If the cached version is newer than one day, replace the star and fork count with the cached version
  3. If the cached version is non-existent or older than one hour, fetch the data using Github APIv3.
  4. Replace the star and fork count with the newly fetched version.
  5. Cache the new data.

We chose one day because honestly, it doesn't matter how many stars or forks a repo has. If it has thousands, 20 more don't really matter; if you have 2 stars, 1 more isn't really a big deal.

Plus, the static stats are updated everytime you rebuild the website, so if you really want to have your website update, you could just rerun Jekyll.

The cached data is stored locally per client, so one client may see one set of stats while another may see another. This is a side-effect of the server not keeping any data.

To add this javascript file, simply include it in your <head>. For, example, if the file is located in assets/ghcards-update.js, you'd added like so:

<script src="{{ "/assets/ghcards-update.js" | relative_url }}" type = "text/javascript"></script>

Note that this isn't a regression: In fact, the other implementation faces the same issue with live updating. However, what this plugin benefits from is that this will still show a copy of the repo card when you are rate-blocked, rather than disappearing entirely or erroring out.


By default, Github Cards only shows HTML. This is intentional, as the user can then style it themselves. However, I have provided two files as a template: style.css and _github-cards.scss.

They both provide the same functionality. Note that you may need to increase specificity if your other CSS/Sass overrides these styles.

To include these styles, simply add @import "github-cards"; or @import "style.css";.

To list all your repos, add the following liquid tag:

{% ghcards %}

This will produce cards for the first 30 most recently created repos. This is useful for listing out your repos for a projects page.

Configuration Options

Option Description Type Default Value
show_language Render HTML for the repo's primary language Boolean true
show_license Render HTML for the repo's license Boolean true
show_user_icon Render img HTML for the repo owner Boolean true
show_forks Render HTML for the repo's forks Boolean true
show_stars Render HTML for the repo's stars Boolean true

Listing multiple repos

To show the first n (up to 30) of your repos:

{% ghcards n %}

To show the first n (up to 30) of somebody's repos:

{% ghcards username n %}

Listing single repos

To show a single repo of your own:

{% ghcards repo %}

To show a single repo, add the following liquid tag:

{% ghcards username repo %}

For example, if you wanted to show only this repo, you'd use:

{% ghcards edward-shen github-cards %}


Q: WTF I tried added it and it's all huge and not formatted nicely like it should be!

A: You didn't install any stylesheets. Either include one of the templates or style it yourself.

Planned features

  • Specify single card
  • Implement get n cards from your repo
  • Implement infinite repos
  • Clean up codebase
  • Bug fixes
  • Add small js to update stars and forks on load