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
We Rewrote Our Angular 18 App in React 20 and Increased Developer Velocity by 40% Last quarter, our engineering team made the bold call to rewrite our 3-year-old Angular 18 production application in React 20. After 6 months of development, we cut over to the new stack with zero downtime, and the results have exceeded our expectations: we’ve measured a 40% increase in developer velocity, alongsid
White labeling is more common than you might think. When developing software, you often need to deploy the same application for multiple clients, each requiring their own customization: unique color palettes, logos, or specific variants for a link. Without a proper strategy, you might be tempted to simply clone the existing repository and implement client-specific changes on demand. However, this
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
TL;DR: ng-prism lets you showcase Angular components by adding a single decorator to the component class itself. No story files, no parallel file tree, no framework mismatch. Just Angular. If you've ever maintained a Storybook setup for an Angular component library, you know the drill: for every component you write, you also write a .stories.ts file. Then you keep both in sync. Then so