[GH-ISSUE #219] Feedback + contributing guideline #55

New issue

Closed

opened 2026-03-02 23:44:11 +03:00 by kerem · 2 comments

kerem commented

2026-03-02 23:44:11 +03:00

Owner

Originally created by @hanpham32 on GitHub (Oct 20, 2025).
Original GitHub issue: https://github.com/anomalyco/opentui/issues/219

Since learning about OpenTUI from Opencode, I'm beginning to use OpenTUI to build new TUI apps. It's been a fun experience using TS to put together a UI in the terminal. I can see OpenTUI be a powerful framework for future TUI app developments. I would love to contribute to this open source project, however, there isn't a standard guideline for that. Would also love to see an official OpenTUI API documentation. I understand this is an on-going development framework so there will be many breaking changes.

Originally created by @hanpham32 on GitHub (Oct 20, 2025). Original GitHub issue: https://github.com/anomalyco/opentui/issues/219 Since learning about OpenTUI from Opencode, I'm beginning to use OpenTUI to build new TUI apps. It's been a fun experience using TS to put together a UI in the terminal. I can see OpenTUI be a powerful framework for future TUI app developments. I would love to contribute to this open source project, however, there isn't a standard guideline for that. Would also love to see an official OpenTUI API documentation. I understand this is an on-going development framework so there will be many breaking changes.

kerem closed this issue

2026-03-02 23:44:11 +03:00

kerem commented

2026-03-02 23:44:12 +03:00

Author

Owner

@kommander commented on GitHub (Oct 20, 2025):

Cool, want to write a guideline? :) Bug fixes are always welcome, feature suggestions, also in the form of a PR as well. Features are subject to discussion though and I cannot guarantee anything. Support/binding packages like react/solid/vue are handled by their respective maintainers, where I am also trying to look after solid, as that is what is used in opencode. Should add tests and must pass in the pipeline. Otherwise I am open to suggestions on what the guidelines could be.

@kommander commented on GitHub (Oct 20, 2025): Cool, want to write a guideline? :) Bug fixes are always welcome, feature suggestions, also in the form of a PR as well. Features are subject to discussion though and I cannot guarantee anything. Support/binding packages like react/solid/vue are handled by their respective maintainers, where I am also trying to look after solid, as that is what is used in opencode. Should add tests and must pass in the pipeline. Otherwise I am open to suggestions on what the guidelines could be.

kerem commented

2026-03-02 23:44:12 +03:00

Author

Owner

@hanpham32 commented on GitHub (Oct 21, 2025):

Yes, happy to work on this :)

@hanpham32 commented on GitHub (Oct 21, 2025): Yes, happy to work on this :)

kerem referenced this issue

2026-03-02 23:45:38 +03:00

[PR #55] Entrepeneur4lyf/api docs #255

kerem referenced this issue

2026-03-14 09:14:51 +03:00