Is this right for me?
Last updated
Last updated
Not every tool is right for every person or team. This template is built on the following major assumptions:
Using a text/code editor (not a GUI editor) to author content in Markdown.
Using Git and repositories to store and change your code and content.
Using GitHub Pages for hosting your website.
Using Jekyll as a static site generator.
If you're not comfortable with or at least familiar with the above, this template may not be right for you. If you want to learn more, see this crash course on the tech used in this template.
The GitHub Pages hosting service is free, but only for public repos. If you want the source code of your website to be private, you'll have to pay for it.
There are other tools available to make your lab website. Here are some of them to investigate:
✔️ Pros of GUI-based | ❌ Cons GUI-based |
---|---|
The main benefit of this template is its automatic citations from just simple identifiers. Other academic templates allow you to enter in a full bibliography manually, but this template is unique in that it uses Manubot to fill in as many details as possible automatically. You can provide just a publication id. You can even enter in an author id and get a list of publications. If you only need a few citations, this isn't a big deal, but if you have hundreds, it can be an enormous time saver.
There are things that other academic templates have that are not included in this template, but we are constantly assessing these differences and looking for ways we can improve. Ideally, the template will eventually be able to do most or everything that the other templates do, and more.
Notably we are working to make sure site layout, theming/styling, components, and interactive features are all comprehensive and flexible.
If you feel something is missing from the template, please don't hesitate to ask for it. We are very receptive to feature requests and other community feedback!
✔️ Pros of code-based | ❌ Cons of code-based |
---|---|
Easy to learn. No special knowledge needed.
Customizable, but only to an extent. No bespoke functionality, like automatic citations!
Quick and convenient to edit. WYSIWYG in-browser editors.
Usually not free.
Integrated services like domain names and customer support.
Harder to track revisions, authorship, reviews, collaboration, issues, etc.
Offer 100% control and flexibility, with coding knowledge.
Harder to learn. Special knowledge required.
Git and GitHub benefits. Easily track revisions, authorship, reviews, collaboration, issues, etc.
Less convenient to edit. Need to make changes in a text/code-based way. Feedback less immediate/direct.
Open source and free. Maintainers more receptive to changes and new features.
Harder to setup and troubleshoot.