Introducing Typemark

I've set up documentation for products more times than I'd like to admit.

Every time, the same ritual. Pick a framework, fight the config, wrangle MDX plugins that break on every update. Deploy to some static host only to realize the search doesn't work and the CSS that looked fine locally falls apart on mobile. Repeat.

The docs are supposed to be the easy part. You've already done the hard work, building the actual product. Writing about it shouldn't require its own infrastructure team.

So we built Typemark

Typemark is a documentation platform for dev and product teams. You sign up, name your project, and you're editing a live documentation site. Not "in a few minutes after the build finishes." Right now. The site is live before you finish your first paragraph.

Here's what that actually looks like:

1. Sign up
2. Type a project name
3. You're in the editor, and the docs are already published

That's it. No GitHub repo required, no config to set up, no deploy step. You just write.

Writing, not wrestling

The editor has two modes. Visual mode is a proper WYSIWYG. Not a markdown preview pane pretending to be one. You write in something that looks and feels like the published page. Headings, callouts, code blocks, tabs, all editable right there.

When you need more control, flip to source mode and you're looking at raw MDX with syntax highlighting and autocomplete. Same file, same content, no conversion weirdness.

Your content is standard MDX, not a proprietary format, not locked into our database. If you ever decide to leave, you take your files and go. That's how it should be.

Git under the hood

Every save is a Git commit. We're not storing your docs in some opaque database. There's a real Git repository behind every project. You get commit history, you can see what changed and when.

Want to connect your own GitHub repo? Go ahead. Push from VS Code, and your docs update. Edit on Typemark, and it pushes to GitHub. It works both ways.

But you don't have to use GitHub. Start writing immediately with our managed hosting and connect a repo later if you need to. Or don't. Your call.

For the whole team

The visual editor means PMs can update the changelog. Support can fix that FAQ entry that's been wrong for two months. Marketing can polish the getting started guide. Nobody needs to learn MDX or open a pull request.

Developers still get their source mode, their config-as-code, their GitHub workflow. Everyone gets to work the way they want.

What's in the box

Beautiful defaults out of the gate. Dark mode, AI-powered search, custom domains, responsive design, SEO, syntax highlighting with Shiki. Callouts, tabs, code groups, cards, steps, accordions, OpenAPI auto-generation from a spec file.

Everything I wished I had every time I started a docs project from scratch.

Where we're going

Typemark is live and you can start using it today. But honestly, what's shipping next is what keeps me up at night in the best way.

We're building content intelligence directly into the platform. Not a chatbot bolted onto a search bar, but AI that understands your entire documentation surface and tells you which pages are outdated, which guides have gaps, and which API docs drifted from your actual endpoints. AI that helps you write better docs, not just find them.

Documentation has been a static artifact for too long. We want it to be a living system that actively helps your team keep it accurate, complete, and useful.

There's a lot more I want to share about this, and I will soon. The foundation is solid and what's coming next is genuinely exciting.

If you've ever spent a weekend fighting a docs framework when you should have been writing actual documentation, give Typemark a try.

We'd love to hear what you think.