onenote-md-exporter VS DocFX

The situation isn’t as bad as it would be for a cloud only service though. As long as you have backups, you can open the “.one” files with OneNote even if you have no access to OneDrive or sync. You can also use an external tool like the OneNote markdown exporter (https://github.com/alxnbl/onenote-md-exporter) to get a copy that at least has the basic content accessible outside of OneNote.

looks like it was this one: https://github.com/alxnbl/onenote-md-exporter

Are you on Windows? I used this to migrate to Joplin before I started using Obsidian. It's a quick way to get your notes into markdown. Did a great job for mine.

By the way, I developed a tool to export OneNote notebook into Joplin export format or markdown format. Maybe it can help you to evaluate the different alternatives : https://github.com/alxnbl/onenote-md-exporter

For OneNote users wanting to evaluate or migrate to Obsidian, you can give a try to the exporting tool that I have developed. It is available on GitHub : https://github.com/alxnbl/onenote-md-exporter . If you encounter any issue or missing feature, you can open an issue on GitHub. Hope it can help some people.

I have just published the 1.0 version which is pretty stable and complete. It is available here: https://github.com/alxnbl/onenote-md-exporter

Not answering any of your questions but If you are looking for a way to migrate your onenote notebooks into Joplin, you may be interested by this tool that I have developed : https://github.com/alxnbl/onenote-md-exporter .

This is a better looking version of what Java and C# have had for a long time (kudos to the author for that!), is that the inspiration for this tool?

https://docs.oracle.com/javase/8/docs/technotes/tools/window...

https://dotnet.github.io/docfx/

I saw the author mentioned in another comment that they found themselves peeping inside type declaration files "too often". While I do often use sites generated by the above tools to discover new API's that suit my needs, diving into the actual code using a good decompiler is still my first move, as it is often cheaper than seeking out the documentation online, and it will show me the actual implementation as well. So in my opinion there is no shame in looking inside the declaration files!

Tools like DocFx provide the ability to display the programmable functions in HTML pages. They are used with the following commands in the docfx folder:

AFAIK they use https://github.com/dotnet/docfx which can be too heavy for your case. We use mdBook for internal documentation (plain .md with mermaid plugin) and then serve it at docs.yourdevenv.com.

DocFX is a nice solution.

It uses DocFX

Some of the standard and well-maintained Tools for Comments are JSDoc for Javascript, DocFx for .NET, and JavaDoc for Java.

Actually, we use it for OptiTune, it's called "docfx" https://dotnet.github.io/docfx/

We would really prefer to use a somewhat generic pre-made tool for this (such as DocFX) compared to rolling our own solution. We can roll our own solution... But would prefer not to so that we can minimize development and maintenance overhead.