Now that you know how to add quick memos on Nots.io, it’s time to get more from these notes you’re adding. We made them suitable for any kind of developers’ workflow: they could be just a short piece of text with a note to future self. Or an even bigger piece of well-formatted text for making specs and RFCs.
Once the project created, it’s now time to start adding documentation. As we mentioned in the previous posts, the major idea of Nots is to tie your docs to the source code. To make it easy to discover documentation from what every developer operate on an everyday basis — from the source code. Here’s how you can do it.
In terms of Nots, a single piece of knowledge, that added to the system, is represented as a note. A note could be a short text message, like a yellow sticky note on a whiteboard. Or a bigger article with rich-formatted text, links, attached images, and PDFs. Here’s a brief overview of the notion of notes.
Project is the central concept of Nots. This is the place where all the work happen. In this detailed guide we show you how to set up your first project, what options do you have and how to invite your teammates right away.
