docs: add Web/UI Design RFC - #698
Open
behinddwalls wants to merge 1 commit into
Open
Conversation
## Summary ### Why? Operators have no browser UI. The first surface is queue-scoped list, summary, history, and poll — the same as CLI watch. A Node BFF and overlay repo are heavier than that, and they do not follow the Go library/host split already used in production. ### What? Adds `doc/rfc/web.md`: operator UI as a `templ`+HTMX Go library (`submitqueue/web`) with example `service/` and production Go hosts, YARPC to the gateway, zap/tally. Documents Next.js as the alternative and what that choice gives up. Indexes it from `doc/rfc/index.md`. Co-authored-by: Cursor <cursoragent@cursor.com>
behinddwalls
force-pushed
the
preetam/sq-web
branch
from
September 8, 2026 14:39
6f83378 to
7fb60ad
Compare
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
1 participant
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.
Summary
Why?
Operators have no browser UI. The first surface is queue-scoped list, summary, history, and poll — the same as CLI watch. A Node BFF and overlay repo are heavier than that, and they do not follow the Go library/host split already used in production.
What?
Adds
doc/rfc/web.md: operator UI as atempl+HTMX Go library (submitqueue/web) with exampleservice/and production Go hosts, YARPC to the gateway, zap/tally. Documents Next.js as the alternative and what that choice gives up. Indexes it fromdoc/rfc/index.md.