Skip to content

Review Visible Copy For Admin, JSON, And API-Like Wording #75

Description

@TheSilkky

Review Visible Copy For Admin, JSON, And API-Like Wording

Priority

High

Type

Copy audit / frontend hardening

Labels

backlog, frontend, design, documentation, security, testing

Branch Scope

Created from docs/end-user-product-design at d2c32a3.

Background

The current app is still close to a technical prototype. Several routes expose API-like concepts, including technical metadata, sharing grants, contact public-key records, and key-delivery details. The design document says normal user copy should use plain product language while preserving precise terminology in advanced or reviewer contexts.

A cross-route copy audit can keep later product-design work coherent.

Proposed Scope

  • Inventory visible copy across routes, empty states, error states, form labels, and action labels.
  • Replace admin, JSON, API, grant, token, metadata, chunk, stream, and key-delivery wording where it appears in normal user flows.
  • Preserve precise technical terms in advanced panels, debug/developer contexts, API documentation, and security-review text.
  • Confirm emergency, experimental-status, and responsibility wording remains clear.
  • Update tests and docs references where user-visible copy changes.

Acceptance Criteria

  • Normal user flows avoid admin-console and API-first language.
  • Technical terms remain available only where they are useful and clearly framed.
  • The copy does not overpromise production status, emergency response, notification delivery, capture reliability, or decryption behavior.
  • Error and empty states are covered, not just page headings.
  • Tests that assert copy are updated.

Out Of Scope

  • Backend behavior changes.
  • Hiding security-relevant status from reviewers.
  • Browser decryption, key escrow, raw key handling, recording, capture, emergency dispatch, or notifications.
  • Rewriting server docs from the web-client repository unless a separate docs issue scopes that work.

Suggested Validation

  • Product copy review
  • Security boundary review
  • npm run typecheck
  • npm run lint
  • npm run test
  • npm run build
  • npm run test:e2e
  • git diff --check

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions