This instruction is specific to the slate theme but should translate well to other themes. You can change default variables in your website build by making changes in your _config.yml
file:
title: [The title of your site]
description: [A short description of your site's purpose]
Additionally, you may choose to set the following optional variables:
show_downloads: ["true" or "false" to indicate whether to provide a download URL]
google_analytics: [Your Google Analytics tracking ID]
You can take a look at the _config.yml
file in this repository to see how to type in the title and description.
You can see this cheatsheet to work with Markdown language for adding features into this website. This includes how to add headers, organization (e.g., bullets or lists), tables, and images. It also includes how to add code to a website.
*Note that for images, you will need to place the image file in a place that it can be referenced and called. I would suggest the github repo might be a good solution. Often, I make an images folder and can call the raw images file.
See example here. You can see the raw code also.
To create links to other pages, you can read this article: https://github.blog/2016-12-05-relative-links-for-github-pages/. Note that these pages should by default direct to the same local folder/directory the index file is. In this case, my README.md file is my index. If the files are in a different folder, one should specifiy the path for that folder.
You can use a website to host notebooks. First, you'll want to get the "raw" url from Github where your notebook is stored. Then, navigate to https://nbviewer.jupyter.org and paste that URL. The result will be a new generated URL that hosts your notebook. This can be a link in your website.
What is the scientitifc goal? What would you do if you had all the data? What do you want to predict or estimate? Why is this relevant to ABE researchers or the field? Provide some background on the rationale and relevance.
What kind of data is avialble? How is your data collected? Are there any concerns about the data? Which data is the most relevant? Is the data easy to acccess? Will the data change over time? What needs to be done to the data to get it ready for any downstream analysis?
Demonstrate what you would do to describe the data and if it has any patterns or anomolies. Make some plots.
Build a model, fit the model, validate the model.
What did you learn and do the results make sense? Revisit your initial question and answer it. H
In each project, I'd like to see a homework assignment that the class can do/evaluate to learn more about your data. This should be a reproducible notebook that allows them to learn one or more aspects of your data workflow. It is also an opportunity to share your research with your colleagues.
Here is an example of a fantastic project website:
https://stephenslab.github.io/ipynb-website/
If you'd like to add your own custom styles:
- Create a file called
/assets/css/style.scss
in your site - Add the following content to the top of the file, exactly as shown:
--- --- @import "{{ site.theme }}";
- Add any custom CSS (or Sass, including imports) you'd like immediately after the
@import
line
Note: If you'd like to change the theme's Sass variables, you must set new values before the @import
line in your stylesheet.
If you'd like to change the theme's HTML layout:
- Copy the original template from the theme's repository
(Pro-tip: click "raw" to make copying easier) - Create a file called
/_layouts/default.html
in your site - Paste the default layout content copied in the first step
- Customize the layout as you'd like
Templates often rely on URLs supplied by GitHub such as links to your repository or links to download your project. If you'd like to override one or more default URLs:
- Look at the template source to determine the name of the variable. It will be in the form of
{{ site.github.zip_url }}
. - Specify the URL that you'd like the template to use in your site's
_config.yml
. For example, if the variable wassite.github.url
, you'd add the following:github: zip_url: http://example.com/download.zip another_url: another value
- When your site is built, Jekyll will use the URL you specified, rather than the default one provided by GitHub.
Note: You must remove the site.
prefix, and each variable name (after the github.
) should be indent with two space below github:
.
For more information, see the Jekyll variables documentation.
Interested in contributing to Slate? We'd love your help. Slate is an open source project, built one contribution at a time by users like you. See the CONTRIBUTING file for instructions on how to contribute.
If you'd like to preview the theme locally (for example, in the process of proposing a change):
- Clone down the theme's repository (
git clone https://github.com/pages-themes/slate
) cd
into the theme's directory- Run
script/bootstrap
to install the necessary dependencies - Run
bundle exec jekyll serve
to start the preview server - Visit
localhost:4000
in your browser to preview the theme
The theme contains a minimal test suite, to ensure a site with the theme would build successfully. To run the tests, simply run script/cibuild
. You'll need to run script/bootstrap
one before the test script will work.