2 ms·
>The solution is to use design language that people are familiar with. Then all you end up with are clones of the same platform. Not much better imo. >For exa
by Sir_Cmpwn 7y ago
>The solution is to use design language that people are familiar with.
Then all you end up with are clones of the same platform. Not much better imo.
>For example, why can't I find the issues/todos from the main repository page?
Because unlike Github, the repository is not the main home of the project. This is true even of many projects hosted on Github. The git repo is often one of many, or the wrong place to file issues, or isn't where the docs live. A centralized idea of a "project" with links backwards and forwards is a blocking planned feature of the Sourcehut beta. But if you're comfortable using a beta-quality UI library then you can live with using a beta-quality project host.
- olah_1 7y agoThanks for the reply! >Then all you end up with are clones of the same platform. There are ways to use familiar design language while at the same time innovating. Like I said before, I just don't want to feel stupid. >Because unlike Github, the repository is not the main home of the project. I don't think your UI is terrible btw. I think I'm just primarily confused about this point. >A centralized idea of a "project" with links backwards and forwards is a blocking planned feature of the Sourcehut beta. I think this would be so helpful. If I can't see a link to Todos.sr.ht from Git.sr.ht, then how would I know that I have to change the subdomain in order to get there? For what it's worth, Gitlab is a UI nightmare compared to Sourcehut. So I very much value your emphasis on the clean and simple.