2 ms·
so the documentation get's parsed by a program which detect hook parts , set them up and look for any trigger then update that part of documentation to show tha
by dvrj101 2y ago
so the documentation get's parsed by a program which detect hook parts , set them up and look for any trigger then update that part of documentation to show that particular node is active?
edit- or the hooks are already set the program just link them to which part of documentation get's update. Like a tag system?
- d--b 2y agoThanks for the feedback. I was thinking much more freeform. In the code, you'd send events to the backend using something like: `post_to_aerial("task_X","some args")` In Aerial, you would then match "task_X" to some icon or some part of your documentation. The way I envision it is that Aerial is very visual, so it's mostly diagrams. In a way, if you start by drawing the diagram the way you envision things to run, you could setup the monitoring before the code itself, in a sort of "monitoring-driven-development".