Markdown collaboration without losing plain text

Markdown earns trust because it stays understandable outside the tool that created it. A useful collaboration layer should preserve that property instead of turning a simple document into a format that only one product can interpret.

Zelares starts from that constraint: the document remains Markdown while collaboration lives around it.

The format stays boring on purpose

Plain text is a strong long-term boundary. It is easy to diff, export, version, search, and move between tools. That means the collaboration product can evolve without asking people to surrender the underlying knowledge they wrote.

The useful layers sit beside the source:

Need	Zelares layer
Organize work	Workspaces and projects
Control access	Workspace and project permissions
Write together	Real-time collaboration
Connect knowledge	Links, tags, properties, and graph views
Take content elsewhere	Markdown-first import and export workflows

None of those require inventing a private replacement for Markdown.

Collaboration should add context, not ownership

Teams need more than a text area. They need a shared place to decide who can see a project, who can edit it, and how related documents fit together. Those concerns matter, but they do not need to become part of the file format itself.

Keeping those responsibilities separate gives a team a clearer contract:

• Markdown remains readable plain text.
• Collaboration can be real time.
• Permissions can be enforced around projects and workspaces.
• The product can add richer navigation without hiding the source.

Portability changes the product incentive

When the source remains portable, a product has to keep earning its place. Better collaboration, clearer organization, dependable publishing, and useful team controls become the reasons to stay—not the cost of escaping a proprietary format.

That is the direction we want for Zelares: make Markdown more useful for groups while keeping the knowledge itself easy to understand and carry forward.