Vrite as a whole can be referred to as a headless CMS, though it’s different compared to other tools in this category.

Essentially it’s a toolkit intended primarily for technical content (like programming blogs or docs), with multiple features in one:

- WYSIWYG editor focused on good UI/UX (including good support for code), and collaboration;

- Kanban dashboard (and other views in the future) for managing the content and its production process; Especially useful for larger teams;

- The “headless CMS” part for hosting and delivering content and related assets; This includes API and Extension system; (in the future planned additions are asset optimization and Git integration)

So, tl;dr; it’s a lot more than the mention tools and I’m still looking for a way to categorize it clearly.

Thanks for detailing this. Does it support math(Jax)/latex/katex ?

Not yet. That’s in the pipeline.