-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix layout/text issues in Community screen #5732
Comments
Couple more items:
Can the main links at the top be symbols? Maybe "settings" could be turned into a cog and community could get its own icon too. Otherwise yeah I agree the top menu is kind of crowded as-is. Matrix link seems to work for me. |
|
@xyzmaker123 I would not continue on fixing that screen but rather work on an alternative approach. |
@chimp1984 Please don't put too much blame on me. I agree I did a few stupid mistakes, but I thought general idea of this tab was already accepted on issue - including top menu placement, irregular columns and messages. If it was not accepted - with whom I should talk before start working on an issue? |
The #4904 (comment) has a grid for the items below the first row with same width. Anyway, we don't need to discuss that further.... |
I close that here as I think the solution should be reconsidered and best discussed in the issue. |
The new community screen has some layout as well as small text issues.
Text:
Layout:
I am not sure the copy URL link is needed as the link will only open a browser if the user has agreed to that at first time opening a URL. So the protection to not open a webbrowser if not wanted is already built in in the generic URL handling.
Beside all that I am not sure if the added value justifies an additional main menu item. The menu gets more overloaded and I think the content could be added to support as well. A dropdown menu for support with the most important links might be another option. Bisq is already very content and text heavy, adding more does not add value IMO.
As it is now, I would recommend to revert the merge and consider more though on UX first how to add the content best.
The text was updated successfully, but these errors were encountered: