-
Notifications
You must be signed in to change notification settings - Fork 24
1.2. Why Should I Care
If you've used GitHub Wiki's before, you know that they are flexible, but at the same time limited.
Flexible in the sense that you can organize them however you want, this is good, but at the same time bad, since it makes you think on what's a good scalable way to organize your content. You should only focus on the content you want to write.
Also, it's limited. Did you know that you can't have two files with the same name on a GitHub Wiki? They're going to get the same slug. Even if you store them in two different directories.
These good practices aim to take all the burden out of writing good and organised Docs.
Important: The Tables of Content are generated. Any change will be overridden on the next update.
For more information: GitHub Wikifier