carpentries / workbench

Repository for Discussions and Materials about The Carpentries Workbench
https://carpentries.github.io/workbench/
Creative Commons Attribution 4.0 International
17 stars 7 forks source link

Collection of comments on the Workbench #9

Closed anenadic closed 2 years ago

anenadic commented 2 years ago

This is an issue to collect some feedback on the use of Workbench:

anenadic commented 2 years ago

Comments on the Workbench from Shoaib Sufi, community lead at the Software Sustainability Institute:

" Really liking the new template! Makes it even easier to promote the Carpentries way! Looking around more - it’s actually beautiful - in the same way Read the Docs format is - actually I might prefer the Carpentries one - is it custom or built off of an existing template? "

"Loving the responsive design also - well done to the team who put this together! Back to the content - some really fantastic stuff here. "

zkamvar commented 2 years ago

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.

open external links in a separate tab by default actually, is there a way to control how individual links are opened in general (in the same tab or a separate one)?

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/

Search button only seems to search within the page and not within the site

See #8

This is not a criticism of the Workbench itself as this is how the old lesson template was designed as well - but I wonder if we should be mixing in workshop operations things into the lesson content - for example we have "episodes" for breaks and when reading the lesson, this adds an extra click for the person. I think these breaks are part of a suggested workshop schedule on how the course can be delivered but should be separated out from the lesson content. Even more so as people may not make breaks at the same time as suggested - I often have this with instructor training which suggests one 15 min break per half fay of teaching as we normally break two times. The old lesson template also implies that IT will be delivered over 2 days as we have seen during pandemic that is not always the case. The new Workbench does not have this issue but I'd still consider separating the schedule of delivery out of the content (i.e. the breaks).

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.

navigation menu on the left does not stay 'collapsed' between page refreshes or navigating between pages - it should stay 'collapsed' or 'expanded' until that is changed

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.

too big top padding on headings - as this is a matter of personal preference, can this be controlled by a lesson designer?

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).

Section headings - feels like there is little difference between heading3/4 etc. - need to review this myself to be sure - again a matter of personal preference but still putting it here

Thank you for this feedback! I'll have to go back to the Figma files and make sure our CSS matches the spec.

Add examples of all types of fenced divs in the Workbench documentation

We have a component guide linked in the callout blocks section of the documentation