https://github.com/agarthetiger/jekyll-pages
GitHub Pages site using Jekyll
https://github.com/agarthetiger/jekyll-pages
github-pages jekyll rakefile
Last synced: about 2 months ago
JSON representation
GitHub Pages site using Jekyll
- Host: GitHub
- URL: https://github.com/agarthetiger/jekyll-pages
- Owner: agarthetiger
- License: gpl-3.0
- Created: 2019-03-03T09:32:54.000Z (over 7 years ago)
- Default Branch: master
- Last Pushed: 2020-09-01T16:36:26.000Z (almost 6 years ago)
- Last Synced: 2025-01-12T06:24:47.901Z (over 1 year ago)
- Topics: github-pages, jekyll, rakefile
- Language: Ruby
- Homepage: https://agarthetiger.github.io/jekyll-pages/
- Size: 27.3 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE.txt
Awesome Lists containing this project
README
# GitHub Pages with Jekyll and TravisCI
[](https://travis-ci.org/agarthetiger/jekyll-pages)
## Overview
This is a simple repo demonstrating auto-generation of documentation using Jekyll, hosted on GitHub Pages. Often there is more to a repository than just a Jekyll website, so the Jekyll site source is under a docs folder. GitHub Pages will take care of the [publishing](https://help.github.com/en/articles/about-github-pages-and-jekyll#jekylls-build-process) of Jekyll websites, and the repository is configured to use the docs folder on the master branch as the Pages source. There is no build process required to publish the website, so Travis CI is used purely to ensure the site will build correctly and run some basic checks with [html-proofer](https://github.com/gjtorikian/html-proofer).
## Local Jekyll site testing
As with code, all changes should be tested prior to raising a PR to the integration branch. This can be doen automatically on the CI server with a branch builder or run locally. Putting aside any discussions of pros and cons of each, ensure you have Ruby installed, run `bundle install` to install all dependencies then run `bundle exec rake test` to run the tests locally.