Summary
Two judgement-call items grouped together because they're about information architecture, not missing content.
1. ZeroKMS naming buried under `cipherstash/kms/`
In the old docs, ZeroKMS had its own top-level: platform/zerokms/. In the new docs the section lives at content/stack/cipherstash/kms/ with index.mdx titled around the KMS function rather than the product name.
The content is all there (regions, keysets, access keys, clients, CTS, disaster-recovery, AWS-KMS comparison) — the question is brand-surface visibility. ZeroKMS is a differentiator and prospects/users searching for "ZeroKMS" land on a URL that doesn't say it.
Options:
- Leave as-is, accept the IA decision
- Rename the section folder to
cipherstash/zerokms/ and update internal links + redirects
- Keep the URL but make the index page title "ZeroKMS" explicitly and bump it in the sidebar
Worth a deliberate call rather than drift.
2. No "Discovery session" / sales-adjacent entry page
The old docs had getting-started/discovery-session — an onboarding-style page that walked enterprise prospects through what to bring to a discovery call (current data security posture, regulated data inventory, target outcomes).
The new reference/planning-guide.mdx covers similar substantive ground, but:
- It's filed under
reference/, not getting-started
- It's pitched as a self-serve planning document, not a "what to expect from a CipherStash discovery session"
If discovery sessions are still part of the sales motion, an entry point in the IA is missing. If they're not, planning-guide is the right replacement and this can be closed.
Suggested resolution
Decide each independently:
- ZeroKMS naming — engineering/marketing call, then a small docs PR + redirects
- Discovery session — sales call; if yes, add
content/stack/getting-started.mdx or similar with a CTA; if no, close
Reference material
Old pages in cipherstash-js-suite git history (commit 1c3d40ed^):
apps/docs/src/app/(articles)/platform/zerokms/page.md
apps/docs/src/app/(articles)/getting-started/discovery-session/page.md
Summary
Two judgement-call items grouped together because they're about information architecture, not missing content.
1. ZeroKMS naming buried under `cipherstash/kms/`
In the old docs, ZeroKMS had its own top-level:
platform/zerokms/. In the new docs the section lives atcontent/stack/cipherstash/kms/withindex.mdxtitled around the KMS function rather than the product name.The content is all there (regions, keysets, access keys, clients, CTS, disaster-recovery, AWS-KMS comparison) — the question is brand-surface visibility. ZeroKMS is a differentiator and prospects/users searching for "ZeroKMS" land on a URL that doesn't say it.
Options:
cipherstash/zerokms/and update internal links + redirectsWorth a deliberate call rather than drift.
2. No "Discovery session" / sales-adjacent entry page
The old docs had
getting-started/discovery-session— an onboarding-style page that walked enterprise prospects through what to bring to a discovery call (current data security posture, regulated data inventory, target outcomes).The new
reference/planning-guide.mdxcovers similar substantive ground, but:reference/, not getting-startedIf discovery sessions are still part of the sales motion, an entry point in the IA is missing. If they're not, planning-guide is the right replacement and this can be closed.
Suggested resolution
Decide each independently:
content/stack/getting-started.mdxor similar with a CTA; if no, closeReference material
Old pages in
cipherstash-js-suitegit history (commit1c3d40ed^):apps/docs/src/app/(articles)/platform/zerokms/page.mdapps/docs/src/app/(articles)/getting-started/discovery-session/page.md