I build mdedit.io — a no-account Markdown editor with live preview, collaboration and AI assistance I’m looking for feedback on the public beta of mdedit.io: https://mdedit.io Repository: https://github.com/MatthiasHertel21/mdedit mdedit.io is a browser-based Markdown editor focused on writing, structuring, previewing, sharing and exporting longer Markdown documents. It does not require an accou
The drift problem Every project that ships a translated README has the same lifecycle: Someone writes README.md in English. A contributor opens a PR with README.zh.md. Great. Three months later, English has six new sections. Chinese has the original. A second translator opens README.es.md. Spanish gets translated from… which version? The current README.md? Or README.zh.md, by accident, because t
§0 — Hook The work-pool schema that runs the paragraf project names three work types: spec, package, and issue-bucket. Only two of the three have a defined The first article introduced a methodology that produced a working library — Two parallel improvements happened in the one week that followed. The first was The second improvement was a sprint. Two new color-related packages shipped under The
The previous three posts covered how events flow from the SDK to the UI, how the timeline renders, and how tool cards visualize. This final post looks at SwiftWork's infrastructure — how data is stored, how state is restored, how Markdown is rendered, how code is highlighted, and how API keys are managed. These components are independent, but all essential to making the app usable. SwiftWork uses
Every AI app I've shipped recently rewrote the same plumbing. The OAuth dance for Slack. Encrypted storage for an API key. Refresh-token logic that finally fails on the 3rd call after an hour. Wiring up an MCP client to a server behind a bearer token someone pasted into a Notion page.