Standard Reader

Why We Chose Offprint Instead of Building Our Own Editor

There is a version of Kevara that has a built-in long-form writing tool. We decided not to build it. Here is why that decision was right.

Kevara | Digital Embassy
Jun 3, 2026 · 31 min read

arly in building Kevara, the question came up: should we include a writing editor?

The case for it seemed obvious. Professionals write. Thought leadership, case studies, project retrospectives, opinion pieces. Long-form content is part of a serious professional presence. If Kevara is the "front door" of your digital identity, it seemed logical to let you write from inside it.

We decided not to. And then we found something better.

The Problem With Building an Editor

An editor is not a feature. It is a product.

Building a good writing tool, one that handles formatting, drafts, publishing, media embeds, and a reading experience worth anyone's time, is a substantial engineering investment. And if we built it, we would be storing your writing in Kevara's infrastructure. Which violates the foundational principle we built everything else on.

Kevara is a display layer. We read from your Personal Data Server. We write records back to your PDS. We do not hold your content. The moment we build a writing tool, we become the host of your words, and your long-form work becomes exactly the kind of centralised, platform-dependent content we were designed to replace.

We would have been solving the wrong problem.

What the AT Protocol Already Solved

The AT Protocol is not just a social microblogging standard. It is a broader framework for structured, portable data. And the long-form writing ecosystem on the protocol already exists.

Offprint, Leaflet, and pckt.blog are all AT Protocol-native writing platforms. When you publish on Offprint, your article is stored as a site.standard.document record linked to your DID. It lives in the open social web. It is attached to your cryptographic identity. It is readable by any app in the atmosphere that chooses to surface it.

This is the "write once, syndicate everywhere" model that Kevara is built for. You write on Offprint. Kevara reads your published work from the protocol and surfaces it directly on your professional profile, alongside your career history, your skills, and your verified credentials. No copy-pasting. No manual links. Your body of work, assembled from open records.

The Smarter Move: Be a Surface, Not a Silo

If we had built our own editor, Kevara would have become another place your content lives. Another silo to manage. Another platform to trust with your writing.

By integrating with Offprint and the Standard.site framework instead, we get to do what we are actually good at: presenting your professional identity in its best form, pulling data from wherever it legitimately lives, without claiming ownership of any of it.

Your Kevara profile is the editorial front end of your whole digital presence. The writing lives on Offprint. The career records live on your PDS. The verification comes from our Ozone labeler. We assemble the picture. We do not manufacture the parts.

What This Means for You

If you are a professional who writes and you are not already publishing on Offprint, it is worth setting up. The platform is clean, thoughtfully designed, and takes long-form writing seriously. Your articles publish to the AT Protocol atmosphere, which means they are surfaced anywhere the protocol is read, including Kevara.

Once your Offprint publications are connected to the same AT Protocol handle as your Kevara profile, they appear automatically in your My Articles section. You can pin your best pieces, set the display format, and feature up to six articles in your public profile layout.

The writing is yours. It lives on the open web. Kevara just makes sure people see it.

The Broader Principle

Kevara is not trying to own every function of your professional life online. We are trying to present it. There is a meaningful difference between being a hub that aggregates your sovereign data and being a platform that holds it all.

The decision not to build a writing editor was actually a decision about what kind of company we want to be. We want to be the display layer, the trust engine, and the professional presentation tool. We do not want to be another place your words are locked in.

Choosing to work with Offprint instead of competing with it was the right call. And the more we work within the AT Protocol ecosystem rather than trying to rebuild it inside our own walls, the better Kevara gets.


Kevara surfaces your Offprint articles directly on your professional profile alongside your career history and verified credentials. Connect your AT Protocol handle at kevara.app to get started.

Kevara | Digital Embassy
Kevara | Digital Embassy
@kevara.app
BlueskyDiscussion

No discussion yet.