Cool. @cmullins70 it also doesn’t hurt if you leave them relative paths… if you like to live dangerously (i.e., it will actually resolve correctly upon merge).
Oh hey! I figured out:
Solves all our problems, I think. @madgrizzle I can sort out converting the absolute-to-relative paths. It should just be a search-and-replace through the markdown files. I’ll coordinate with the folks working on the CI tooling.
1 Like
I’ll coordinate with the folks working on the CI tooling.
My ears are buzzing… Just add a script in tools/ and it’ll be easily called in the CI build. Bonus point is that you can test it locally.
Perfect, thank you. I’ll include that in a PR.
@madgrizzle I still can’t seem to pull notes from the repo correctly. Would you mind importing the rest of the markdown files? Then I’ll tag them and start updating them. https://hackmd.io/c/tutorials/%2Fs%2Flink-with-github
@cmullins70 and anyone else. If you have a Maslow 4 and are still interested in Documentation I have been working on a draft of a comphrensive user manual that would gather a lot of info from the formus as well as some libaries where people can gather useful information. It is all in the Maslow4 main repo. I liked cmullins70’s flowchart of documentation topics. It feels like it has a lot of common features with the table of contents that I have started sketching out. All the docs are here, I would welcome any help. Maslow_4/docs at Maslow-Main · MaslowCNC/Maslow_4 · GitHub
2 Likes