We will use this icon to mark check points.
A check point is a way for you to check how you are doing.
For most of the steps in this tutorial we will
provide the code as it should look after the task. It is tempting, we
know, but please, please, do not go for the “copy&paste” way.
We will use this icon to challenge you
with additional code-related tasks so you can go further at your own
pace. No inline answer will be provide for those challenges but we will
give you some guidelines and tips. By the way, within the instructions
we will use an italic font to refer to variables and pieces of code.
We will use this icon to ask you some questions related to the task your are working on.
Additional info and resources - this is not essential to complete the tutorial, but very interesting.
Tips that might help you on this task.
If you are following this tutorial as part of a workshop, do not hesitate to
raise your hand and share any questions or comments you may have.
If you are doing it by your own, you still can raise your hand in our
mailing list, just join our Google Group.
Purposes of this tutorial series
- Learn basic concepts of BioJS
- Get hands on dependency management in BioJS 2.0
- Master the workflow for publishing a package on npm and the BioJS 2.0 registry
Getting help
Our education portal is a work in progress. So if you encounter a logical inconsistency or just want to ask a question - don’t hesitate to contact us.
We also maintain a public Github wiki.
For technical queries (questions, suggestions, proposals or bug reports) Gitlab issues are preferred.
If you find a typo or want to help us to make this tutorial even better, you are invited to click on “Improve this page”.
Concepts in this tutorial
- Data separation and modularity
- Versioning (via npm)
- Minimal rules -> conventions and gold standards
