mirror of
https://github.com/anomalyco/opentui.git
synced 2026-04-25 04:55:58 +03:00
[GH-ISSUE #254] [DISCUSSION] should opentui.com be a website? #835
Labels
No labels
bug
core
documentation
feature
good first issue
help wanted
pull-request
question
react
solid
tmux
windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/opentui#835
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Vicentesan on GitHub (Nov 2, 2025).
Original GitHub issue: https://github.com/anomalyco/opentui/issues/254
this issue aims to understand why the current domain opentui.com redirects to the gh repo instead of an website. looking at the repo, it doesn't seem like we have a website. for that reason, i would rephrase the question: is it on the opentui roadmap to create a website? if so, i would like to help build it
@0xjuanma commented on GitHub (Dec 11, 2025):
Even a minimal landing page could be fine for now, with links to gh, etc if needed.
@kommander commented on GitHub (Jan 18, 2026):
This is up for grabs now.
We'd like to align design with www.opencode.ai, opentui will get its own proper logo. The website and documentation should live as packages in this repo and be built and deployed from there.
As soon as we have something to publish, a target to deploy to will be provided.
@remorses commented on GitHub (Jan 18, 2026):
I have been working on a npm package that can render opentui TUIs to the browser via websocket, would you like to use it for the website? I can prepare a quick demo to show you how it looks like. We could even let users play with the core examples script directly in the browser
@Vicentesan commented on GitHub (Jan 18, 2026):
i will try to design something as well in the coming days
@kommander commented on GitHub (Jan 18, 2026):
Cool
@remorses I would like to keep it simple and pretty much static for now to get going, but I am open to trying things going forward.
@remorses commented on GitHub (Jan 18, 2026):
Here is an experimental website created using opentui and deployed to Fly. Each request is a WebSocket connection to the server, TUI output is returned as json over WebSocket. It can handle a lot of concurrent users because it does not spawn a new process per connection.
https://opentui.fly.dev/
Code is here
@kommander commented on GitHub (Jan 18, 2026):
@remorses it's very laggy and the 3D stuff doesn't seem to work? But it tries to render 200-1200fps somehow. I think it just crashed and restarted.
@simonklee commented on GitHub (Jan 18, 2026):
the live TUI rendering is interesting and could work well as a playground feature down the line.
I think the priority is a landing page that explains what OpenTUI is, shows it in action (terminal recordings would be fine), and gets people to an install command. The docs in packages/core/docs/ are a starting point but need structure (getting started, core concepts etc).The examples in the repo are great but would benefit from some curation and explanation.
Astro makes sense for consistency with opencode.ai, if that's a priority.
Mainly keep it at a level where it's not too much a of a maintenance burden, because then it will just drift out of sync and cause confusion instead of helping.
@remorses commented on GitHub (Jan 20, 2026):
@kommander yeah the website was just an experiment, each interaction is a websocket round trip so there is latency. Some of the examples were breaking the server and restarting the server sorry about that, I am using the test renderer so fps calculation may be wrong there
@simonklee commented on GitHub (Jan 27, 2026):
https://opentui.com/