Shopify's Open Source page is built with Jekyll and Sass and hosted on GitHub Pages.
All of the data comes from Jekyll. Any change in index.html (including whitespace commits - e.g.) will trigger a rebuild and update all of the numbers.
To include a repo in the list, add it to optInRepos in javascripts/custom-repos.js. The repo must be owned by Shopify. To include non-Shopify repos, use customRepos. Set a defined project language or custom avatar in the same file.
- Clone this branch or download the zip and navigate to the folder in terminal
- Install Jekyll:
gem install jekyll - Install Sass:
gem install sass- Use
sass -vto make sure it worked
- Use
- Install Compass:
gem install compass - Make sure everything is setup with
bundle install - Run
bundle exec jekyll serve - In another terminal window, run
compass watch - Access the page at
http://localhost:4000
- Use Ruby 3.3 or newer for the current bundle.
Gemfilesets minimum patched versions for ActiveSupport, Nokogiri, and rubyzip; keep these floors when updating dependencies. - WEBrick 1.9.2 remains affected by CVE-2026-38969, with no patched release available as of November 12, 2026. It is used by the local Jekyll preview server, not served to visitors of the static site. Until a fix is available, keep previews bound to loopback (
bundle exec jekyll serve --host 127.0.0.1); do not expose them to untrusted traffic or place them behind a public reverse proxy. Usebundle exec jekyll buildwhen no preview server is needed.
bundle exec jekyll servewill compile the Jekyll and Sass files into static assets in the _site folder each time a file is saved. That folder is excluded from the repo.compass watchwill update ie.css and main.css.- Use
rake buildto manually parse SCSS files. - Your local build will be nearly empty because:
- The page uses Jekyll's
site.github.public_repositoriesobject to get the repo data. This data is only available when live. - Custom repo data is generated by Github's JS API, so it will show up locally.
- The page uses Jekyll's
- The content for each project comes from the GitHub Pages for that repo.
This can be from a
gh-pagesbranch, or from the/docsdirectory, based on the GitHub Pages settings. Using the/docsdirectory is preferred as it's less confusing for contributors.