Would the awesome-tuis community and maintainers be interested in a web page for the applications?
The page could dynamically pull information directly from the README.md, so no changes would be required there. New submissions could be added just as before, without altering the workflow.
If there’s enough interest, I’d be happy to start development (no promises though xD).
Originally created by @Nqtural on GitHub (Jan 15, 2026).
Original GitHub issue: https://github.com/rothgar/awesome-tuis/issues/498
Would the awesome-tuis community and maintainers be interested in a web page for the applications?
The page could dynamically pull information directly from the README.md, so no changes would be required there. New submissions could be added just as before, without altering the workflow.
If there’s enough interest, I’d be happy to start development (no promises though xD).
I would love something that had screenshots or videos of each tool in action. I've actually thought about making that a prerequisite for being on the list because it's really hard to figure out how some of these tools work and if they're TUIs at all.
The reason I recorded my own video was partially because it's really hard to see what the tools do.
<!-- gh-comment-id:3844710222 -->
@rothgar commented on GitHub (Feb 4, 2026):
I would love something that had screenshots or videos of each tool in action. I've actually thought about making that a prerequisite for being on the list because it's really hard to figure out how some of these tools work and if they're TUIs at all.
The reason I recorded my own video was partially because it's really hard to see what the tools do.
gifs would be too big if you put them all on a single page. You can embed ascii cinema but that would mean people need to have recordings available.
<!-- gh-comment-id:3850958829 -->
@rothgar commented on GitHub (Feb 5, 2026):
gifs would be too big if you put them all on a single page. You can embed ascii cinema but that would mean people need to have recordings available.
I have started development; the current state of the page can be found here. Keep in mind that this is not intended to be the finished product: thus far it is a MVP.
The goal of the site is to be an alternative way to view the Markdown contents, not a replacement. I want to keep the project maintenance the same as before. The way I have accomplished that thus far is:
All data is parsed from the existing Markdown file using regular expression. This makes updating the list identical to how it was before.
The code is automatically compiled on branch updates using a GitHub Actions workflow: as long as GitHub pages is set up to host from gh-pages branch, maintainers do not have to update the gh-pages branch or compile the website code.
As for videos/GIFs, I have an idea that could be implemented gradually. Basically, select a program and then you can see info about it, link to the source code and if there is a GIF for that program (something like assets/gif/programname.gif) it is displayed.
<!-- gh-comment-id:3854042643 -->
@Nqtural commented on GitHub (Feb 5, 2026):
I have started development; the current state of the page can be found [here](https://nqtural.github.io/awesome-tuis/). Keep in mind that this is not intended to be the finished product: thus far it is a MVP.
The goal of the site is to be an alternative way to view the Markdown contents, not a replacement. I want to keep the project maintenance the same as before. The way I have accomplished that thus far is:
- All data is parsed from the existing Markdown file using regular expression. This makes updating the list identical to how it was before.
- The code is automatically compiled on branch updates using a GitHub Actions workflow: as long as GitHub pages is set up to host from `gh-pages` branch, maintainers do not have to update the `gh-pages` branch or compile the website code.
As for videos/GIFs, I have an idea that could be implemented gradually. Basically, select a program and then you can see info about it, link to the source code and if there is a GIF for that program (something like `assets/gif/programname.gif`) it is displayed.
A little more polishing work has been done, although no GIFs/images. How does it look to you @rothgar?
<!-- gh-comment-id:3980596988 -->
@Nqtural commented on GitHub (Mar 1, 2026):
A little more polishing work has been done, although no GIFs/images. How does it look to you @rothgar?
I love how snappy it is even with lots of items to list. I'm sure screenshots would slow it down but also improve it a lot. I wish there was an easy way to get screenshots from all the tools.
<!-- gh-comment-id:3995899323 -->
@rothgar commented on GitHub (Mar 4, 2026):
I love how snappy it is even with lots of items to list. I'm sure screenshots would slow it down but also improve it a lot. I wish there was an easy way to get screenshots from all the tools.
It is fast due to loading content asynchronously and is techically one page due to how Vue Router's WebHashHistory works.
I'm working on a way to load images from the repo or compiled static page, making sure images are optional so it can be implemented gradually.
One idea for gathering the images could be to rely on the community, encouraging users to submit an image through a pull request if no image is found.
<!-- gh-comment-id:3998823885 -->
@Nqtural commented on GitHub (Mar 4, 2026):
It is fast due to loading content asynchronously and is techically one page due to how Vue Router's WebHashHistory works.
I'm working on a way to load images from the repo or compiled static page, making sure images are optional so it can be implemented gradually.
One idea for gathering the images could be to rely on the community, encouraging users to submit an image through a pull request if no image is found.
Images are here! Although the only one I have added for is Dashboards > AdGuardian-Term so I could test it. There are also instructions for how submitting images would work.
Adding images this way is quite complicated, nothing the average user would care to do. I'm open for ideas and suggestions how to to make this process easier.
Let me know your thoughts, feedback greatly appreciated.
<!-- gh-comment-id:4013807550 -->
@Nqtural commented on GitHub (Mar 6, 2026):
Images are here! Although the only one I have added for is Dashboards > AdGuardian-Term so I could test it. There are also instructions for how submitting images would work.
Adding images this way is quite complicated, nothing the average user would care to do. I'm open for ideas and suggestions how to to make this process easier.
Let me know your thoughts, feedback greatly appreciated.
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.
Originally created by @Nqtural on GitHub (Jan 15, 2026).
Original GitHub issue: https://github.com/rothgar/awesome-tuis/issues/498
Would the awesome-tuis community and maintainers be interested in a web page for the applications?
The page could dynamically pull information directly from the README.md, so no changes would be required there. New submissions could be added just as before, without altering the workflow.
If there’s enough interest, I’d be happy to start development (no promises though xD).
@rothgar commented on GitHub (Feb 4, 2026):
I would love something that had screenshots or videos of each tool in action. I've actually thought about making that a prerequisite for being on the list because it's really hard to figure out how some of these tools work and if they're TUIs at all.
The reason I recorded my own video was partially because it's really hard to see what the tools do.
@zen0bit commented on GitHub (Feb 4, 2026):
gif?
@rothgar commented on GitHub (Feb 5, 2026):
gifs would be too big if you put them all on a single page. You can embed ascii cinema but that would mean people need to have recordings available.
@Nqtural commented on GitHub (Feb 5, 2026):
I have started development; the current state of the page can be found here. Keep in mind that this is not intended to be the finished product: thus far it is a MVP.
The goal of the site is to be an alternative way to view the Markdown contents, not a replacement. I want to keep the project maintenance the same as before. The way I have accomplished that thus far is:
gh-pagesbranch, maintainers do not have to update thegh-pagesbranch or compile the website code.As for videos/GIFs, I have an idea that could be implemented gradually. Basically, select a program and then you can see info about it, link to the source code and if there is a GIF for that program (something like
assets/gif/programname.gif) it is displayed.@Nqtural commented on GitHub (Mar 1, 2026):
A little more polishing work has been done, although no GIFs/images. How does it look to you @rothgar?
@rothgar commented on GitHub (Mar 4, 2026):
I love how snappy it is even with lots of items to list. I'm sure screenshots would slow it down but also improve it a lot. I wish there was an easy way to get screenshots from all the tools.
@Nqtural commented on GitHub (Mar 4, 2026):
It is fast due to loading content asynchronously and is techically one page due to how Vue Router's WebHashHistory works.
I'm working on a way to load images from the repo or compiled static page, making sure images are optional so it can be implemented gradually.
One idea for gathering the images could be to rely on the community, encouraging users to submit an image through a pull request if no image is found.
@Nqtural commented on GitHub (Mar 6, 2026):
Images are here! Although the only one I have added for is Dashboards > AdGuardian-Term so I could test it. There are also instructions for how submitting images would work.
Adding images this way is quite complicated, nothing the average user would care to do. I'm open for ideas and suggestions how to to make this process easier.
Let me know your thoughts, feedback greatly appreciated.