> The primary use-case is dev marketing (right now) and general documentation like usage guides, explainations, etc., where the content is primarly text with ad

> The primary use-case is dev marketing (right now) and general documentation like usage guides, explainations, etc., where the content is primarly text with addition of code ... Looking back, labeling Vrite as a "CMS for technical/developer marketing" might have made it more clear what the product's goals are. I think that's the way to go. There's a lot of opportunity there for a tool that's better suited to this work than blog-focused CMSs and Google Docs, but with the same sphere of pick-up-and-go accessibility ("so easy, even a product manager could use it!") without sacrificing the technical hooks to integrate that content with disparate things like LMSs, in-app help, or product docs. Runbook docs might even be a good fit depending on how well Vrite can integrate with the tools being deployed, and would be the right audience for the kinds of people who'd likely write and maintain extensions for it. Product education teams that are allergic to the weight and complexity of LMSs would probably enjoy it too, especially if a mature extension or frontend pops up that can take one pile of content nodes and conditionally present them as blog posts, presentation slides, and paginated workbooks. But man... the product docs space is like a 12-armed bear. I'd stay far away from even implicitly raising the possibility of Vrite being a fit for "documentation" from a product point of view. Product docs teams often have the most, and most specific, feature needs ("can you conditionalize my content based on non-Boolean feature flags while outputting to both raw and formatted HTML, PDF, and DOCX, and also linting all the content for style, reading level, and sensitivity, oh and also we need to be able to publish shared content across 36 versions of 7 product lines in 12 languages, including British localization. Also it can't fail any accessibility tests. Also can you make the logo on the output 6.5 pixels bigger, use this font I got off dafont, and match these Pantone color values from our branding"), and also the fewest technical resources to write or maintain things like extensions, and smallest budgets to pull the whole thing off — so they're also always looking at any tool that might even tangentially help them do more with less.