A connected application cannot show anything inside the console #173

New Issue

2026-10-06T18:11:55Z

cgalo5758 commented

2026-10-06 18:11:55 +00:00

What a person cannot do today

See or act on a connected application's state from inside the console. An integration that ships in the console renders its own pages from Go templates; an application outside the console has no way to show a status, a list, a settings form or a setup step to a member or an operator.

What they should be able to do

The console renders a closed set of region types from data a connector declares: a status card, a list with row actions, a settings form, a setup flow, an action, a validation, notices, a link out, and data shown on console pages. A link out can sign the person in.
Read-only regions render from stored data; only actions and validations call the connector while the page waits, within three seconds.
Recorded facts about contact with the application may be shown; claims of health that nothing backs may not.
A page shows each connection's delivery lag and restore events.

Why it matters

Members and operators work in one console. A closed set of region types means a need it does not cover arrives as a request for a new type, rather than being worked around in raw HTML without anyone hearing about it; the documentation says where to make that request.

Where

internal/server (a region renderer), the connection pages, the design system. Notices need the part #167 decides; notifications (#168) and the attention section (#78) are related.

Done when

A connector declares regions and the console renders each type at both widths with the copy rules enforced at render time; a link out signs the person in; lag and restore events are visible per connection; the documentation names where to request a region type.

Order

Comes after #172.

## What a person cannot do today See or act on a connected application's state from inside the console. An integration that ships in the console renders its own pages from Go templates; an application outside the console has no way to show a status, a list, a settings form or a setup step to a member or an operator. ## What they should be able to do - The console renders a closed set of region types from data a connector declares: a status card, a list with row actions, a settings form, a setup flow, an action, a validation, notices, a link out, and data shown on console pages. A link out can sign the person in. - Read-only regions render from stored data; only actions and validations call the connector while the page waits, within three seconds. - Recorded facts about contact with the application may be shown; claims of health that nothing backs may not. - A page shows each connection's delivery lag and restore events. ## Why it matters Members and operators work in one console. A closed set of region types means a need it does not cover arrives as a request for a new type, rather than being worked around in raw HTML without anyone hearing about it; the documentation says where to make that request. ## Where `internal/server` (a region renderer), the connection pages, the design system. Notices need the part #167 decides; notifications (#168) and the attention section (#78) are related. ## Done when A connector declares regions and the console renders each type at both widths with the copy rules enforced at render time; a link out signs the person in; lag and restore events are visible per connection; the documentation names where to request a region type. ## Order Comes after #172.

cgalo5758 added this to the Public launch milestone 2026-10-06 18:11:55 +00:00

cgalo5758 added the

kind

enhancement

area/integrations area/operator-ui area/member-ui labels 2026-10-06 18:11:55 +00:00

cgalo5758 referenced this issue

2026-10-06 18:12:03 +00:00

FedWiki and Discourse are built into the console instead of connecting through the published contract #174

cgalo5758 referenced this issue

2026-10-06 18:12:16 +00:00

An application outside the console cannot connect to it: there is no published protocol #171

cgalo5758 referenced this issue