A user guide on nectenda.com #87

New issue

Closed

opened 2026-09-22 15:47:59 +01:00 by cruelacid · 1 comment

cruelacid commented

2026-09-22 15:47:59 +01:00

Owner

Why

The site explains what the product is and what the server cannot see. It does
not explain how to use it. /security is 3,165 words and the most
differentiated thing we have; there is nothing comparable for someone who has
just installed the plugin and shared their first folder.

This is also the gap that costs search impressions. A guide page matches what
people type — "obsidian share folder with someone", "obsidian collaborative
editing offline" — in a way a product page never does.

What to do

One page per real question, not one long page:

Sharing a folder — invite, accept, what the other person sees.
What the server can and cannot see. Links to /security rather than
restating it; bound by docs/positioning.md — never "audited", never "zero
knowledge", never "we store no metadata".
Offline editing and conflicts — what happens to work made offline, where
conflict copies land, and what .nectenda-backups/ is for. Governed by the
central principle: when two versions conflict, both are kept.
Device limits and what happens at the boundary.
Self-hosting — currently withheld; say what is true today.
Verifying the build — the sha256(main.js) in each release against the
published source. This is the trust anchor and deserves a page of its own.

Constraints

Each page needs a description inside 100-160 characters (the guard in
page() throws otherwise), a unique <title> containing "Obsidian", and an
entry in SITEMAP, rewriteLinks() and deploy-site.yml's paths:.

## Why The site explains what the product is and what the server cannot see. It does not explain how to *use* it. `/security` is 3,165 words and the most differentiated thing we have; there is nothing comparable for someone who has just installed the plugin and shared their first folder. This is also the gap that costs search impressions. A guide page matches what people type — "obsidian share folder with someone", "obsidian collaborative editing offline" — in a way a product page never does. ## What to do One page per real question, not one long page: - **Sharing a folder** — invite, accept, what the other person sees. - **What the server can and cannot see.** Links to `/security` rather than restating it; bound by `docs/positioning.md` — never "audited", never "zero knowledge", never "we store no metadata". - **Offline editing and conflicts** — what happens to work made offline, where conflict copies land, and what `.nectenda-backups/` is for. Governed by the central principle: when two versions conflict, both are kept. - **Device limits** and what happens at the boundary. - **Self-hosting** — currently withheld; say what is true today. - **Verifying the build** — the `sha256(main.js)` in each release against the published source. This is the trust anchor and deserves a page of its own. ## Constraints Each page needs a description inside **100-160 characters** (the guard in `page()` throws otherwise), a unique `<title>` containing "Obsidian", and an entry in `SITEMAP`, `rewriteLinks()` and `deploy-site.yml`'s `paths:`.

cruelacid added this to the Backlog - unscheduled milestone

2026-09-22 15:47:59 +01:00

cruelacid added the

area:docs

usability

labels

2026-09-22 15:47:59 +01:00

cruelacid added this to the User Experience project

2026-09-22 16:08:51 +01:00

cruelacid commented

2026-09-23 18:55:52 +01:00

Author