Replies: 5 comments 5 replies
-
Comments on the Workbench from Shoaib Sufi, community lead at the Software Sustainability Institute:
|
Beta Was this translation helpful? Give feedback.
-
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 |
Beta Was this translation helpful? Give feedback.
-
A suggestion: wonder is capitalising/titlecasing headings should be done automatically and via a configuration parameter? |
Beta Was this translation helpful? Give feedback.
-
I'm going to add a comment here, as I am not sure where is appropriate, but the Overview box at the start of a lesson is very compressed. If the side bar is not collapsed, the text is very compacted so that "Questions" is limited to 2 / 3 words per line harming readability. |
Beta Was this translation helpful? Give feedback.
-
Looks like point 8. on including examples of fenced divs is at: https://carpentries.github.io/sandpaper-docs/component-guide.html#top under 'More' menu - this could perhaps be made more prominent under '1. Introduction to The Carpentries Workbench' section. Just noting it here - we could link to the transition guide here too: https://carpentries.github.io/workbench/transition-guide.html (this is possibly already done). |
Beta Was this translation helpful? Give feedback.
-
This is an issue to collect some feedback on the use of Workbench:
Beta Was this translation helpful? Give feedback.
All reactions