Update decisions.md - #765
Open
jjjssswww wants to merge 1 commit into
Open
Conversation
docs(design): add Aug 5 decisions (tenant naming, login CSS) + open questions
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the design decision log to capture outcomes from the Aug 5 projects/tenants sync, clarifying terminology (tenant/team/project), UI behavior for tenants/projects/schemas, and the login UI styling approach.
Changes:
- Adds new decisions D16–D21 (tenant naming + data model mapping, tenant UI, schema nested-attribute behavior, login UI CSS approach).
- Refreshes and reorders the “Open questions” list, replacing individual names with role ownership.
- Reaffirms/extends prior decisions where applicable (e.g., projects MVP details).
Suppressed comments (2)
docs/design/decisions.md:6
- The phrase “the real thing in the mechanic” is unclear/incorrect wording; “mechanism” (or similar) reads correctly here.
- [ ] **Glossary + data model** — the team wants a vocabulary table (term → the real thing in the mechanic) plus an ER / data-model diagram, ideally generated from the DB once it's settled. Needed to keep the tenant/team/project terminology unambiguous. *(owner: eng / design)*
docs/design/decisions.md:25
- Same wording issue as above: “term → real mechanic” reads like the wrong word choice; “mechanism” is clearer.
Same backend JSON model as today — only the words change. Hierarchy: a project (the instance, e.g. "River") contains one or more tenants (organizations, e.g. "Acme"); the account "team" (the Zitadel cloud account, shown bottom-left, holding account users / billing) sits above. "Multi-tenancy" = a project is multi-tenant-capable; tenants live within a project. → The team wants a glossary (term → real mechanic) and an ER / data-model diagram generated from the DB once it's settled (see open questions).
|
|
||
| - [ ] **Project & multi-project access** — parked on the permissions foundations (Livio, Sylvana); not needed for MVP. Once ready, the project selector removed in D6 comes back in the role-assignment UI. *(owner: eng)* | ||
| - [ ] **Login vs. console visual alignment** — whether to fully restyle the login flow to match the console (CTA height, labels, button styles differ today) or keep it slightly different for MVP. Parked; revisit once light/dark tokens land. *(owner: design / eng)* | ||
| - [ ] **Applications** — no owner identified and no backend mention yet. Design to ask around for who owns applications. *(owner: design)* |
| ## Decisions | ||
|
|
||
| ### D21 · Login UI: pure CSS on own tokens, not shadcn/ui — 2026-08-05 · [standing] | ||
| The login app has to run inside many different frameworks and is built as web/lit components, so it can't use the shadcn/ui React library or Tailwind. Rebuild it with pure CSS that maps the design tokens to our own CSS classes (the original "legacy" / `zl-`-prefixed token approach), not shadcn or Tailwind classes. Reuse the same token styles for visual consistency, but add a prominent note in Figma and in code: *"don't use shadcn — the CSS is done manually."* There is no light theme in these variables today. → Design provides light + dark mode values and applies them to the correct color tokens; whether to fully align the login look with the console is a separate open question. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
docs(design): add Aug 5 decisions (tenant naming, login CSS) + open questions
Summary
Records the decisions from the Aug 5 projects/tenants sync in docs/design/decisions.md:
Also refreshes the open-questions list and replaces people names with roles. Docs only — no code or shipped behavior changes.
Validation
Docs-only change; no build or tests to run. Checked the rendered Markdown in Preview.
Release notes / changeset
No changeset required — no shipped behavior changed (documentation only).
Notes
Terminology (tenant vs. team) is intentionally called out for review; a glossary + data-model diagram is tracked as an open question.