A simple, easy lab notebook website
- Note: Consider integrating your HackMD or Obsidian with your GitHub account. This could make formatting each of your markdown files a simpler task. Check out Issue #1 for more detailed information.
To automatically update a simple website with your markdown documents!
That's it.... Thanks?
To create your own website!
- Fork this repo as
lab-notesWhen forking you have the option of renaming the fork. Rename your fork to remove
_templatesfrom its name for a simpler URL. - Click
Settings>Pages - In the
Sourcedropdown, selectDeploy from a branch - In the
Branchdropdown, selectmainthen clickSave - There is now a
Your site is live atfollowed by a URL!Note: You may need to refresh the page.
- Head back to
<> Code, in the upper right hand corner there is anAboutsection- Click the
Settings(Actually looks like this -> ⚙️) - Toggle the checkbox under
Websitethat saysUse your GitHub Pages website
- Click the
- Update the title yaml header in the
index.mdfile with your name i. Something like<YourName>'s Lab Notebook(e.g.Brenda's Lab Notebook)
The idea was a straight-forward one when I thought this up. Each markdown document added to the docs directory will become a link on your website. Each link will take you to the rendered markdown document on a new nested website. The trick was to automate this! (For those interested in Github Actions as an automation tool, check out the .github/workflows/update_index.yaml file!)
- Consider removing the
notes-template.mdfile in thedocsdirectory... or don't and just keep it and update it in to a template that works for you. - Add any number of your own markdown documents to the
docsdirectory- The document file name must not contain any whitespaces and must end in
.md- Whitespaces in filename will not work! (eg.
whitespaces in file names.md) - Filename must contain
.mdat the end! (eg.must-contain-.-md-at-the-end) - Name the files similar to this ->
2024-week-1.md.
- Whitespaces in filename will not work! (eg.
- The document file name must not contain any whitespaces and must end in
- The contents of the document will be rendered as markdown.
- If you want to have unique titles for each document, include a yaml header with
title:. See the template below.
---
title: Year Week number
---
# Goals
In this section I will list the weekly, quarterly, and yearly goals I hope to achieve or have completed this week.
**Weekly:**
- [x] Create a lab notebook repo
- [ ] Read the docs
**Quarterly:**
- [ ] Present my work to the lab
- [ ] Write some python code
- [ ] Write some snakemake files
**Yearly:**
- [ ] Have a well documented project in github that is functional (if not perfect)
# Results
In this section write the verbatim results (eg. copy the code chunks, error reports, plots) that relate to the goals you have achieved this week.
example:
This week I created a lab notebook repo using this method (include the cli arguments and the process below)
# Discussion
In this section explain your results and how they relate to you goals
example:
I am applying for credit this quarter. Therefore, I chose to create a lab notebook repo in github to continue practicing git and github as it is an important tool for biotech/bioinformatics.
# Journal
In this section add anything else you may wish to include.
example:
Nothing additional to comment this week. Work has been taken allot of my time this week. It's finals, I was not able to complete the goals I thought I would. I got a new hamster and it is very fluffy.