Recent posts
#en#product
You can now list, read, compare, and name a note's versions through the HackMD API. Here is what the five endpoints do, what they deliberately do not do, and how to try them.The HackMD Versions API is now live
#en#education
Teams are building more internal tooling than ever, and nearly all of it depends on a knowledge layer that has to be addressable, versioned and permissioned. A walk through HackMD's REST API and MCP server, from ETag delta syncs to the versions endpoints that make agent write-back reviewable.The Infrastructure Layer: how teams are building and the tools that are powering them
#en#company
Two days at AmericasMart, one badge, and a through-line nobody planned. Justin Samuels, Robin Bender Ginn, Claudio Wunder, and Ethan Arrowood on stage; MCP and SKILL.md files in every hallway between them.Road to Render ATL: How the South brought together markdown, AI, and passionate engineers
#en#education
Every agent you use starts from zero. This post walks through a real workflow where one LLM writes a spec into a HackMD folder, a different LLM pulls that same spec into its context, and both work from the same source of truth.Context Switching: Keeping your LLMs in sync
#en#product
Your public notes have always been shareable. Now they're discoverable. HackMD Community turns published notes into a shared space where you can explore what others are building, learn from real work, and connect with the people behind it.Introducing Community: A New Way to Share and Collaborate on HackMD
#en#education
Most of us now work across several LLMs and agents in a single afternoon, and each one forgets everything the moment we close the tab. Markdown layer can become the memory that your team, your individual work, and your agents all read from and write back to.