The console has no notifications #168
Open
opened 2026-10-06 08:12:34 +00:00 by cgalo5758
·
2 comments
Labels
Clear labels
accessibility
area/billing
area/catalog
area/discourse
area/domains
area/entitlements
area/fedwiki
area/identity
area/integrations
area/licensing
area/member-ui
area/meta
area/operator-ui
area/ops
area/testing
duplicate
good-first-issue
invalid
privacy
security
upstream
wontfix
A barrier for people using assistive technology or a keyboard alone.
The Stripe mirror, checkout, subscriptions, invoices, fulfillment.
Products, prices, plan ladders, purchasability.
The Discourse integration.
The domains registry, claims, placements, the certificate ask.
Entitlement sets, rules, grants, pools, provisioning.
The Federated Wiki integration and farm sync.
Sign-in, sessions, persons, organizations, workspaces, roles.
The provider registry, outbox and webhooks in general.
Licenses, the contributor agreement, SPDX headers.
Member pages.
The repository itself, its contributing guide, CI, the tracker and the workflow.
Operator pages, forms, lists, the design system.
Deployment, configuration, migrations, workflows, instance settings.
The test stack, screens, lint, walkthroughs.
Closed because another issue already covers it.
Small, self-contained, and explained enough to be a first contribution.
Closed because it is not a ticket for this repository.
Touches what a person's data reveals.
Touches authentication, authorization, secrets or data exposure.
Waits on another repository or project before it can move.
Closed because it will not be done, with the reason in the last comment.
kind
bug
The software does something other than what it promises; closed when it again does what it promises.
kind
debt
Code, tests or tooling to clean up with nothing visible changing; closed when they are cleaner.
kind
design
A question to settle before work can be defined; closed when the decision is written down.
kind
docs
Documentation that is wrong or missing; closed when it says the right thing.
kind
enhancement
Something the software does not do yet; closed when it does.
priority
critical
Blocks the active milestone or harms members now.
priority
high
Next in line inside the active milestone.
priority
low
Inside the active milestone, when nothing else is left.
priority
medium
Inside the active milestone, after the high ones.
Milestone
No items
No Milestone
Projects
Clear projects
No projects
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: wiki-cafe/member-console#168
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The question
The console tells a person something only on the page where it happened, and only while they are looking. None of these reach anyone:
Most platforms keep notifications behind a control in the top bar, with read and unread state. What does the console notify about, whom, and where are notifications read?
What depends on the answer
Options known so far
Decided when
The kinds of event that notify, who receives each, and where notifications are read are written down, and #78 and #167 say how they relate.
The notice part (#167) keeps no record of closed notices. A notice's close button posts to whoever owns the fact, and the owner records it on its own row.
One of today's two closable notices belongs here. A declined or failed site request's outcome on the FedWiki sites card is closed by setting
acknowledged_aton the lifecycle request (AcknowledgeLifecycleRequestininternal/integration/lifecycle.go). By this issue's own rule that outcome is a notification, because the member may have left the page before it finished. When notifications have their store, closing the outcome becomes marking it read there, and that read state replacesacknowledged_at.One difference to settle here:
acknowledged_atis kept per workspace, so one member closing the outcome closes it for everyone in the workspace, while a notification's read state is per person.Toasts are a third way the console tells a person something, beside notices (#167) and notifications, and this issue has to place them too. Today there are two:
internal/embeds/static/error-handler.jswhen a request fails;internal/embeds/static/success-toast.jsfrom anHX-Triggerheader (showSuccessToast) or rendered into a page that loads after a create.Both reach only the person on the page, at that moment, and they leave no record. The notice part keeps them a separate part: one shared template for their markup in every layout, and the error toast staying until it is closed.
Questions this issue has to answer about them: