Our lab’s site was cloned from the Fraser labs site! See below for their post about creating your own lab website:
If you are starting a new lab or want an easy (democratized) way to run your lab website - please: Clone this website!
The Fraser lab website was built by Ben Barad 6 years ago using Github Pages. Since then, it has been improved upon by many members of the lab, and has been updated over 1000 times by James.
We love our lab website because it is so easy to use and update. Updates are done in markdown, which is very easy to learn. As part of on-boarding, new members add their own bio and picture. This also serves to teach people git and to get comfortable with the idea of modifying, breaking, and fixing the website! The publications page is particularly powerful with easy formatting based on IDs for Pubmed, the Protein Data Bank, BioRxiv etc. Similarly the members page makes it easy to add accounts for Twitter, github, and other services. We keep adding more features. For example, Jen will be adding alumni links for lab websites or LinkedIn pages in the near future!
In keeping with our lab principles on sharing, we decided from the beginning to share it with a permissive open source license, so that others in the community are able to copy and modify it to make their own lab websites. We’re glad they have!
Have you made a website using the Fraser lab or one of these sites as a template? We’d love to add yours to our list!
Recently, our lab website has gone through some significant ugprades. These include moving to collections for most things instead of using the _data
folder, moving to a CDN to load large files, and support for structure loading with UglyMol. This guide predates these, and while it is relatively easy to copy the website still, for this guide we recommend taking a copy of one of the releases we made before incorporating these edits: https://github.com/fraser-lab/fraser-lab.github.io/releases
organization_name.github.io
- right away, you’ll start seeing a website appear at that URL! Optionally, download the site, and try building it using the instructions in the readme so you can edit locally. Either way, delete the current CNAME
file, which points to https://fraserlab.com. Once you’ve done this, the website will start showing up automatically at https://organization_name.github.io - no further hosting or configuration required.external
folder)config.yml
and news.xml
files to be your lab’s name!_includes/header.html
and _includes/footer.html
for your website! In particular, change the university brand image and link in the header, and the link in the footer.static
folder, and put in member photos, key images/PDFs for papers, and any extra images that you want to use on your site._posts
folder and write one or two of your own!_data
, _includes
, _layouts
, _drafts
,_posts
, publications
, research
, members
, static
, and maybe news
and join
.index.md
to change the homepage! You can change the image in _layouts/home.html
. Change the sidebar on the homepage at _includes/sidebar.html
_data
and do the following:
members.yml
and alumni.yml
with your own members and alumni!sep.yml
and visitors.yml
based on your needs - do you have visiting scientists or undergrads/high school students to list?navlinks.yml
based on your needs - this controls what is in the navbar at the top of each page.publications.yml
with your own publications._layouts/members.html
. Update the members page sidebar by editing _includes/alumni_sidebar.html
.research/index.md
. Similarly update any other specific pages by editing the index.md
or index.html
file in each folder._includes/disqus.html
, or remove it at _layouts/post.html
if you don’t like comments on your posts.sitemap.xml
and optionally make another one of your own.favicon.ico
with one of your own!static.css
and _layouts
and _includes
to customize the site to your heart’s content!For a new publication, just upload a photo and PDF, then update the _data/publications.yml
file. Similarly, for a new member, just update _data/members.yml
. New blog posts can be made by adding a new markdown file in _posts