Open hmgl opened 2 years ago
Your question is unclear and you failed to follow the instructions on the issue template when opening your issue.
I'll take a guess though:
Are you wanting to see the list of One-Click-Apps assigned tags and made sortable by those tags in the user interface? Some apps fit more than one category, so I am thinking tags would be better suited if this is what you are asking.
tags are fine. For instance, wordpress should be tagged as blogging. Joplin should be tagged as note-taking
The inherent problem is who gets to design the nomenclature for the software? This really should be in the hands of the developers who write software, not so much the lists that include such software.
For example, you might immediately wan to assign "blogging" to what WordPress themselves refer to their software as a "content management system". As a developer of a content management system myself, I can say that calling my software a "blogging" platform would absolutely undermine any marketing I am doing to promote the software. And technically speaking, my software doesn't fit the category of a content management system exactly, because there is no user interface. Therefore, it should be called something else. If I tagged my software only as "content management", people would probably and rightly so assume that there is a user-interface. This is one problem with labeling software.
The term "blogging" is very use-case specific. WordPress, being a full content management system that go so far beyond "blogging", including acting as the software base to run entire e-commerce websites or even as a customer relation management portal.
With that in mind, we could assume we could provide tags for "content management" and "blogging" but then does that mean we would also add tags for all the other possible use-cases for the software such as "CRM" or "E-Commerce"? This would not make sense.
While on the surface, this feature request does seem like a practical improvement to Caprover but ultimately, I think this takes away from what Caprover is intended to solve. There is a certain amount of work that is required to code and maintain such as feature that I don't feel would be worth the trouble.
I like this idea. The list of one-click apps is only going to get bigger and having some sort of filtering/categorisation would be great. I like to click through the list every now and then to see if there's anything interesting out there and having even broad categorisation would make this much easier.
If someone disagrees with how something has been tagged/categorised then a simple pull request on the one-click repo would sort that out.
I definitely understand that this can be complex, and many apps would fit into more than one category. For example, Oodo, performs so many tasks as an ERP. I think that it would require something like tagging where there would be the option of providing multiple tags. However, If we get to that level, then there likely would be almost as many tags as there are applications. I would think that if this gets implemented it would be helpful to allow the system admin to either add additional tags, or overwrite the tags based on their systems needs and designs.
I propose the following:
Tagging all the apps with the appropriate tags and then having a simple interface that lets you pick and choose the tags that are grouped based on things like "Communication", "Productivity", "Administration", etc.
This of course is a lot of work. At the end of the day, most people know what they are looking for when they go to install an app.
Please read CapRover goals and scope before posting a new feature request.
Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like A clear and concise description of what you want to happen.
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.
Additional context Add any other context or screenshots about the feature request here.