The latest articles on DEV Community by Reymond Godoy (@e2e2a). https://dev.to/e2e2a https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3912156%2F5ff0861e-5993-458f-a24c-07ba03dd7f83.jpg https://dev.to/e2e2a en Reymond Godoy Mon, 04 May 2026 13:29:27 +0000 https://dev.to/e2e2a/project-stria-5937 https://dev.to/e2e2a/project-stria-5937 <p>I’ve been working on a web-based Markdown editor inspired by tools like Obsidian, focused on structured documentation workflows.</p> <p>The idea is to explore a browser-based writing environment for:</p> <ul> <li>documentation</li> <li>knowledge bases</li> <li>structured Markdown content</li> <li>RAG-ready text pipelines</li> </ul> <h2> What it includes: </h2> <ul> <li>Live Markdown preview</li> <li>Callouts and Mermaid diagrams</li> <li>Link-based structured notes</li> <li>Obsidian-like writing experience in the browser</li> <li>API-first design (docs/api.md for backend integration)</li> </ul> <h2> Current status: </h2> <ul> <li>Frontend-only prototype (no database yet)</li> <li>No persistence — just live editing/testing in the browser</li> </ul> <h2> What I’m trying to validate: </h2> <ul> <li>Is this type of browser-based Markdown editor actually useful?</li> <li>Would you use something like this?</li> <li>What’s missing for real-world adoption?</li> </ul> <p>Live demo: <a href="https://stria-nine.vercel.app/" rel="noopener noreferrer">https://stria-nine.vercel.app/</a><br> Source code: <a href="https://github.com/e2e2a/stria" rel="noopener noreferrer">https://github.com/e2e2a/stria</a></p> <p>Any feedback is appreciated, especially brutally honest takes.</p> webdev nextjs programming react