Vrite VS DocFX

These reasons (and many others) are why I decided to create Vrite - an open-source developer content platform. - Source: dev.to / 2 months ago

However, writing Markdown files is a very different experience compared to the WYSIWYG approach. It can be challenging for beginners or less technical users, while also getting increasingly difficult to manage as the content base grows. My latest project — Vrite — is meant to solve this problem. - Source: dev.to / 7 months ago

So, I've been building Vrite as an open-source project for a while now, and I'm happy to finally share it here - with v0.2.0 now having official self-hosting support. Source: 8 months ago

Hi everyone, So, I've been building Vrite as an open-source project for a while now, but only now - with v0.2.0 - I'm happy to finally provide official self-hosting support. The best way to describe Vrite is a "developer content platform" - something between a CMS and a knowledge base - a versatile tool to create, manage, and publish your technical content. You can use it in various ways: - as a headless CMS for... - Source: Hacker News / 8 months ago

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/windows/javadoc.html 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... - Source: Hacker News / 5 months ago

Actually, we use it for OptiTune, it's called "docfx" https://dotnet.github.io/docfx/. Source: over 2 years ago

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. Source: over 2 years ago

I use docfx from microsoft to generate documentation for all my oss libraries. Source: over 2 years ago

My best guess would be that there's a CI/CD pipeline in GitHub that utilizes DocFX to convert the Markdown files to HTML. The constructed HTML files are then placed in an Azure Storage account that configured for Static Website Hosting combined with Azure CDN. Source: over 2 years ago