| The major problem is having me visualise what is going to come out of the process Every markdown-like language has some underlining and bullet points. I can handle that. Once we get into using graphviz / some other tool for drawing charts and graphs I simply lose it. It is in the end much easier to knock up something in PowerPoint / Visio / paint tool than be clever with graphviz. The only arguments against this are 1. Maintenance - and yes it’s a good argument. Changing the name of one box should be easy - but it is with some paint tool too. 2. Graphviz etc are much more “programmable”. Slapping together 6 boxes for your network diagram is easy. 150 is what graphviz is for. The problem is that you stopped using markdown the minute you went “oh, 150 boxes with edges between them.” At that point you have to use “some other tool”. Maybe that tool is taipy, or graphviz or he’ll LaTeX is great for this - but you need to master the tool then you get great results. So things like this should be “If you are already fluent with graph production in LaTeX, use this tool
That links latex to markdown” Otherwise spending a large chunk of your undergraduate thesis learning how to use the tool might not work so good. Summary: Just use dead simple plotly graphs in your sphinx docs. Something like “total number of words bar chart”. Then it’s there and you can expand it as much as you can before you hit the complexity limit that is just simpler to grab a visual drawing tools and store a binary. |