Offered at RPI, Fall 2020
This page contains technical documentation useful for developing your project site.
If you have questions or are experiencing difficulties, please contact Sam: stoufs2 at rpi dot edu or Shruthi: chari at rpi dot edu
When you are trying to add to the website template that you have setup for your individual projects, please follow these steps:
Also, the navigation bar of your project page is filled out by us, and if you want to edit this (e.g.:, to add options), please consult with course TA, Shruthi: firstname.lastname@example.org or Sam Stouffer, email@example.com Finally, should you have any questions: please check the course instructions page at: https://master–rpi-ontology-engineering.netlify.app/.
We have further instructions, on the technical implementation of this infrastructure below. Additionally, some page specific notes can be found on the individual website pages. Please read through for your understanding.
The primary course site is hosted on GitHub Pages and is automatically built from the master branch. The projects, however, cannot be hosted on GitHub Pages, which only allows hosting of a single branch. Because of this, we will be hosting the branches using Netlify, a free cloud hosting service.
All branches of the GitHub repository will be built and hosted on Netlify at a url dependent upon the branch name.
The url for your branch will be https://branch-name–rpi-ontology-engineering.netlify.app/ where branch-name is the name of your branch.
Netlify will rebuild the site from your branch whenever you push new commits to the GitHub repo. Allow several minutes for Netlify to rebuild the site from your changes. The status of your Netlify build will be reported on GitHub as a commit status. You can also view the status of the latest builds on the Netlify deploy dashboard. (This requires registration to see more than the last two builds.)
Optionally, you can preview changes to your branch site without the hassle of pushing up a commit and waiting for Netlify by building and serving the site on your own machine.
Follow the quick start instructions in the Jekyll documentation.
Skip the steps where you create a new site and change directory (just make sure you are in the
ontology-engineering root directory when executing commands.)
Follow the instructions to embed files on the docs publishing support page.