-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Fix Links + UI improvements #2182
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
Comments
Thanks for opening this issue!
|
I think we should remove all these links:
|
Agree, it goes against a few UI design principles, it's simply uncommon and takes too much brain power to decipher. |
Agree 100% with you |
Ok, to conclude, the changes are:
I would recommend to create 2 separate issues with 2 separate PRs for this. |
New Issue Checklist
Issue Description
The link in the ••• > Deployment/Maintenance at the bottom of the parse Dashboard points to
http://serverfault.com/tags/parse
instead of https://serverfault.com/questions/tagged/parse-server
The link in the ••• > Code-Level Questions points to
http://stackoverflow.com/questions/tagged/parse.com
instead of https://stackoverflow.com/questions/tagged/parse-server
Remove the "Server-Questions??" looks like the tag parse-server in stack overflow include "all stuff related to parse"?
Change the link http://docs.parseplatform.org/ to https://docs.parseplatform.org/ (to point to the secure version)
Change the link http://parseplatform.org/ to https://parseplatform.org/ (to point to the secure version) in the Open Source Hub (I personal will change the Open Source Hub label to something more "normal?" Web, Official Web, or something..)
Fix the "Show All" label in the Manage Columns Menu (See Pic)

The "Cancel" button in the dialogs is labeled as "Never mind, don't." I personally feel it very weird.. 🤔
Some of this "issues" are personal opinions...
Steps to reproduce
Click on the links, etc
Actual Outcome
Shows zero questions in server fault
Expected Outcome
Show the 66 questions in server fault and ~2000 in StackOverflow using the tag parse-server
Environment
Any
Dashboard
4.1
all
any
Server
5
any
any
Database
Postgres
14
local
Logs
The text was updated successfully, but these errors were encountered: