Co-founder of Motif here. We're building Motif because we think that ultimately, there is no difference between a document and a full-blown website. The tool needed to author such docs should be at the intersection between a coding environment and a word processor, and leverage open web technologies. The goal is that, by building a platform geared for content creation, with a rich set of tools and helpers (think drag and drop, asset management, WYSIWYG editing, shared components, instant publishing...), we can make software development accessible to more people than just developers, and improve collaboration between teams that have been siloed apart in different tools.<p>Today, Motif is a collaborative text editor (based on Monaco + Yjs + Replicache) that runs entirely in the browser (thanks to esbuild, no local Node dev environment required). It also syncs with the file system so that you can use your tools of choice (we posted about this last week [1]). It supports MDX [2], Markdoc [3], React/JS/JSX, Tailwind CSS, and ES module imports. It features instant publishing (as a Next.js application hosted on Vercel).<p>Why MDX and Markdoc? While we do think that MDX provides the most versatile format and the most powerful API (with the Unified.js ecosystem, which we will soon support), we want to give optionality to experiment and choose what is best for a given situation. Other formats, like AsciiDoc, might also be supported down the line.<p>Would love your feedback! Our Discord is: <a href="https://discord.gg/MBMh4apz6X" rel="nofollow">https://discord.gg/MBMh4apz6X</a>.<p>[1] <a href="https://motif.land/blog/syncing-text-files-using-yjs-and-the-file-system-access-api" rel="nofollow">https://motif.land/blog/syncing-text-files-using-yjs-and-the...</a><p>[2] <a href="https://motif.land/docs/basics/mdx" rel="nofollow">https://motif.land/docs/basics/mdx</a><p>[3] <a href="https://motif.land/docs/basics/markdoc" rel="nofollow">https://motif.land/docs/basics/markdoc</a>