- Go to the
_posts
folder - Create a new markdown document called YYYY-mm-dd-some-name.md. The name must contain the date of the post and a short description of what its about.
- Put a yaml header in the top of the document. The header should contain:
-
layout: post
-title: [your title goes here]
-date: [date of post in format YYYY-mm-dd hh:mm:sss]
-categories: [a category of your choice]
. This can be useful later for categorizing news posts when we have a whole bunch. - Write a markdown news post. A good length is one to two sentences. This post can contain photos and links, lists, quotes, etc.
- Save the markdown file.
- Run
jekyll build
- Commit your changes.
- Go to the
_people
folder. - Create a new markdown document called [personName].md.
- Go to the
img/bio_img
folder. Put an image of the person here, calledpersonName.jpg
. Any photo format is accepted. - Write a YAML header for the document. It should contain:
-
name: The person's name
-biography: A description of the person's interests and position.
-role: The role in the lab.
Accepted values are "Professor", "Postdoc", "Graduate Student", "Undergraduate". Sorry Simon, Research Scientist isn't an accepted value. Currently, the role is only used for sorting and partitioning on the page. -linkedin: Link to linked in profile
-twitter: Link to twitter profile
-email: Email address
-orcid: Link to ORCID profile
-photo: "name of photo in bio_img folder".
This should exactly match the name of the image you put in theimg/bio_img
-seniority: A number representing how to sort.
Categories (role
s) will be partitioned and then sorted byseniority
. - No markdown needs to be written in this file. All bio information should go into
biography
key in YAML. - Save the file.
- Run
jekyll build
- Commit your changes.
- Create a new markdown file in the root (top level) directory.
- Put a YAML header. Make sure it contains the line
layout: page
- Write your page in markdown.
- Run
jekyll build
- Commit your changes.
When linking to top-level pages, make sure you link to href="{{site.baseurl}}/NameOfPage/
. This tells the link to go to the root of the website, then look for your page name. If you don't include {{site.baseurl}}
, you may encounter problems with relative paths. If you include the file extension if the NameOfPage, you may find that the name is unknown. For this reason, don't include the file extension (e.g., .html
), instead, put a trailing slash (e.g., /
). This can be done in the nav.html
document to put a new link in the navigation bar. To link to pages within markdown, you can just use markdown links.