HackMD

09/04/2026

You found the perfect link for your doc.

Now you just need it to look like it belongs there.

With Link Preview in HackMD, paste your URL and choose how you want to share it.

Keep the original URL.

Turn it into a clean reference.

Or give your readers more context with a preview card.

It’s one small part of writing, but one less thing to stop and format manually. 💜

09/03/2026

Your team is probably building more internal software than it used to.

Onboarding assistants. Coding agents. Internal search. Architecture digests. Tools that pull context together before work starts.

But all of them depend on the same thing:

A knowledge layer they can actually trust.

That means stable addresses for your docs, cheap ways to detect what changed, a clear record of who changed what, and permissions your tools can inherit instead of rebuilding from scratch.

In our latest blog, we break down how you can use HackMD’s REST API, version history, and hosted MCP server as that infrastructure layer.

Because the model is rarely the hard part.

Read the full post below. 👇

https://buff.ly/BeHD4fe

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.

08/31/2026

You have a problem.

Your agent skills are becoming more valuable, but they are also getting scattered across repos, terminals, local files, and individual workflows.

We think that knowledge should be easier to share.

With HackMD, you can create, share, and collaborate on skills from your workspace, your terminal, or wherever your agent lives.

That means the instructions that shape how your agents work do not have to remain trapped in one person’s setup.

Your team can build them together, improve them over time, and keep the knowledge behind your agentic workflows in one collaborative place. 💜

Your skills are knowledge.

Give them a home your whole team can use.

08/28/2026

Your agent can do a lot.

But it still needs somewhere to put the knowledge it creates.

That’s why we’ve opened up the official HackMD Skills repo. 💜

You can plug ready-to-use skills into Claude Code, Cursor, Codex, and compatible agent workflows to help your agents:

→ keep an ongoing work log across sessions
→ publish plans, Markdown, HTML, and files directly to HackMD
→ turn plans and trade-offs into visualizations your team can actually share

Instead of letting valuable context disappear inside individual agent sessions, you can bring that knowledge back into a collaborative space your whole team can work from.

Give your agents some superpowers 👇

https://buff.ly/GUsPBRX

Get HackMD superpowers. Contribute to hackmdio/hackmd-skills development by creating an account on GitHub.

08/21/2026

We came to for the people, the open source conversations, and, of course, a little Markdown. 💜

What we left with was a much bigger question about where AI agents are heading.

MCP is making it easier for your agents to connect to the tools your team uses, but they still need to understand how your team actually works.

That context increasingly lives in Markdown.

Your runbooks, architecture decisions, agent instructions, skill files, and documentation are becoming part of the infrastructure that helps AI understand your team.

We pulled together what we learned from RenderATL 2026, including conversations about Node.js, open-source sustainability, AI infrastructure, and the people building it all.

Give our full recap a read below 👇

https://buff.ly/HCxQsHB

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.

08/20/2026

Your team’s knowledge should not be scattered across local .md files.

Drag and drop Markdown files into your workspace to bring documentation, ideas, and project context into one collaborative place.

What starts as a local file becomes shared knowledge your entire team can build on.

Think of it as a living knowledge brain for your team 💜

08/17/2026

Building the future of robotics takes more than great hardware

It takes research, shared knowledge, and a team that can stay aligned while moving quickly

Menlo Research is building Asimov, an open robotics platform designed to give more developers the tools to experiment with, learn from, and build the next generation of humanoid robots

HackMD supports that journey by giving their team a collaborative space to document ideas, share technical knowledge, and keep important context moving alongside the work

https://buff.ly/qDoSy8S

HackMD gives you a real-time Markdown editor for collaborative work. Working with Markdown files in HackMD is simple, straightforward, and fun.

08/14/2026

Day Two of Renderatl - Render-Atlanta is a wrap!

Brian Muenzenmeyer and Claudio Wunder took us inside the future of Node.js documentation, showing how doc-kit is rethinking a documentation system that has supported the ecosystem for years

What stood out to us was the role Markdown continues to play as knowledge becomes useful not only to developers but also to search systems and AI tools

Later, Ethan Arrowood from Harper and the OpenJS Foundation community brought that same spirit to life through Node.js Code & Learn, helping developers move from learning about open source to actually contributing to it

Better documentation helps people understand; great communities give them somewhere to contribute

Till next year, RenderATL 💜

08/12/2026

Day One at Renderatl - Render-Atlanta has given us plenty to think about

Robin Bender Ginn of the OpenJS Foundation took a deeper look at an important question in the AI era: if AI is generating more code, who is maintaining the Node.js runtime, packages, and open source infrastructure that code ultimately depends on?

Justin E. Samuels, CEO of Render, joined a conversation about the engineer’s evolution from coder to producer, where the value increasingly comes from guiding AI output, shaping systems, and applying the human judgment needed to ship reliable software

Two different conversations with a common thread: technology may be moving faster, but people, community, and shared knowledge still sit at the center of what gets built

A great start to RenderATL 2026 🔥

08/11/2026

Great collaboration means giving everyone room to edit without worrying about losing what came before

With version history, teams can follow how documentation evolves, understand past changes, and restore an earlier version when needed

That means more confidence when collaborating, clearer context for distributed teams, and less hesitation when it is time to improve the doc