Skip to content
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

stopipv/web (the source code for the website)

How to edit the site Build Status

  1. You can edit files directly on GitHub -- no cloning or other installation necessary! Note that images won't render in preview mode when you're editing on GitHub, this is normal, the file path is purposely set up under static/images/ for Hugo, the site's compilation tool. When you're done editing content, save your commit(s) and the website will be updated within a couple minutes. Click on this build badge Build Status to see the site's automated deployment process with Travis CI.
  2. OR, if you want to edit locally (benefit: see the final website rendered on your browser in real time before saving commits and publishing), install Hugo on your machine. Mac OS: brew install hugo. Windows: choco install hugo -confirm. Linux: snap install hugo. Then, install make (generally available on macOS with XCode installed, and on Linux by default).
  3. Refer to general Hugo tips/documentation as needed to orient yourself to the tool. You have plenty of fancy static compiler customizations/templating/site variables available to make the site even more awesome.
  4. To see the website as you're editing locally (automatically rebuilds when you change project files), run make develop. Navigate to localhost:1313 in a browser to see what the site looks like rendered as you're editing it.

Where to edit the site (directory/file structure)

  1. For the homepage, edit /layouts/_default/index.html (in plain HTML). For all other content, edit the files in /content/posts/*.md (in Markdown). You'll see the server rebuild the site whenever you save changes to a file. The config.toml file has special parameters used throughout the site that you can modify.
  2. For quick CSS modifications, edit static/css/style.css. It's best to do this locally since you can see the changes before pushing to GitHub.
  3. When you're ready to push your changes, either commit directly on GitHub, or locally stop the server and run make publish (or, just push the commits on your own). This will commit the source code to, and trigger an automatic build/deploy cycle on Travis CI. Check the site after a few minutes for the update (you can view the build progress live by clicking the green badge at the top of this README).
  4. To make a new page, run hugo new post/ Be sure to set draft: false in the file before publishing!

Need help?

Email or reach me on Cornell's slack (username @sam). I'm happy to help with site development or answer questions.

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.