-
-
Notifications
You must be signed in to change notification settings - Fork 7
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
Collection of comments on the Workbench #9
Comments
Comments on the Workbench from Shoaib Sufi, community lead at the Software Sustainability Institute:
|
Thank you for collecting this feedback, @anenadic! I've transferred this issue to the workbench repository so that it's clear that this is feedback about the workbench in general as opposed to the documentation, specifically.
In general, you can open a link in a separate tab/window by using ctrl on Windows/Linux or cmd on Mac and clicking the link. There is a good reason why we do not have links open in new tabs/windows by default: it takes away user autonomy. While it's possible for users to hold a special key (e.g. ctrl on Windows/Linux or cmd on Mac) and click on the link to open it in a new tab/window if the link uses the default setting, if a link always opens in a new tab, it's not possible to have the behaviour open in the same tab/window. More reasons can be found in https://css-tricks.com/use-target_blank/
See #8
I agree with this. This is one reason why we de-emphasized the presence of the schedule on the landing page (e.g. you need to visit the instructor landing page in order to view it). Ultimately, though, this is an issue for individual lessons and maintainers.
This is a good point. I believe I might be able to use browser cache to handle this, but it will require some investigation. I will open an issue in {varnish} and address it once we are nearing the end of the beta phase.
I believe this was implemented with accessibility in mind, but will be exploring ways to allow custom CSS to be added (though official lessons should not deviate from the styling).
Thank you for this feedback! I'll have to go back to the Figma files and make sure our CSS matches the spec.
We have a component guide linked in the callout blocks section of the documentation |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
This is an issue to collect some feedback on the use of Workbench:
The text was updated successfully, but these errors were encountered: