-
Notifications
You must be signed in to change notification settings - Fork 6
Description
What do you thin about organizing the documentation according to divio documentation system?
This structure could improve navigation and help new users and developers to find what they want.
Also, it could be easier to spot missing/doublicated/outdated articles...
The draft version could be like this (feel free to change):
Tutorials
https://yaq.fyi/blog/installing-yaq/
https://yaq.fyi/blog/ne1000/ (need also a text version)
https://yaq.fyi/blog/yaqc/
https://control.yaq.fyi/
How to guides
https://yaq.fyi/blog/happi/
https://yaq.fyi/blog/yaqc-cmds/
https://yaq.fyi/blog/record-simply-script/
https://yaq.fyi/blog/bat/
https://yaq.fyi/blog/labview1/
Explanations
https://yaq.fyi/introduction/
https://yaq.fyi/licensing/
https://yaq.fyi/alternatives/
References
https://traits.yaq.fyi/
https://yaq.fyi/traits/
https://yaq.fyi/daemons/
https://yaq.fyi/hardware/
https://yaq.fyi/packages/
https://yeps.yaq.fyi/000/
https://github.com/yaq-project
https://doi.org/10.1063/5.0135255
https://www.youtube.com/@yaq-project