Block Shortcuts style shouts with UPPERCASE ALL THE THINGS

[stevepiercy]

Describe the bug

When a block is active, and the user clicks Block on the right-hand side, the content is mostly uppercase, which is rude and shouty.

Expected behavior

It would be nice to have sentence case friendly text. Also some text needs to be updated and added.

Screenshots

ANGRY BLOCK TEXT

Friendly block text

Proposal

This could be resolved by removing this transformation. I don't know how that would affect other parts of the UI.

.ui.secondary.attached.segment {
    text-transform: uppercase;
}

Also I would suggest other text updates:

Change block type: / to bring up a menu of block types. Use up/down arrow keys and Enter, or tap or click, to select a block type.

Strong/Bold: mod+b
Emphasis/Italic: mod+i
Underline: mod+u
Strikethrough: mod+s

The modifier key (mod) on Windows is Ctrl, and on macOS it is ⌘ or command.

Software (please complete the following information):

https://6.demo.plone.org/edit

[davisagli]

Probably we could detect whether the current OS is Mac or not, so that we can show the correct modifier key rather than making the reader put the pieces together.

[tiberiuichim]

The sidebar for the Slate text is mostly an experiment that was never finished.

When we've started to use Volto, the feedback from our users was that it was confusing to have the sidebar automatically switch between the Document and the Block tab (when focusing a Title or Text block, it switches to Document, otherwise it sticks to the Block panel). With draft, when you activated the Block tab panel, there was an empty panel with a big "forbidden" icon. So with volto-slate we've tried to provide "something" for the sidebar. We had the idea that we want volto-slate extensions, and we need to provide a space for them to render, so we've decided just to show the shortcuts, as a sort of placeholder for some future, more relevant content. So the whole "shortcuts + markdown help" can be considered an experiment that can be removed or improved.

[stevepiercy]

I got another idea. What if we had end-user Editor documentation for Volto? And then in the UI, we could place the universal help icon (❔) that links to the relevant Volto Editor page in the docs, based on the context. This would keep the UI clean and leave space for future development. PyCharm does that for its UI, and it is super helpful to me.

Additionally this would create something for directionless newbies to work on that is relatively easy. These docs would be perfect for newbies. We could tag an issue with "33 needs: docs" and "41: lvl easy" to give a good entry point for them.

[ksuess]

I got another idea. What if we had end-user Editor documentation for Volto? And then in the UI, we could place the universal help icon (❔) that links to the relevant Volto Editor page in the docs, based on the context. This would keep the UI clean and leave space for future development. PyCharm does that for its UI, and it is super helpful to me.

Additionally this would create something for directionless newbies to work on that is relatively easy. These docs would be perfect for newbies. We could tag an issue with "33 needs: docs" and "41: lvl easy" to give a good entry point for them.

If I get you right, you are suggesting to replace "shortcuts" section and "markdown help" section by a universal help icon (❔) that links to the end user instructions in 6.docs? This would be a great solution. Editors using the UI seldom have always up to date instructions at their fingertips. Additional fields of schema enhancers are not hidden below the "shortcuts" section and "markdown help".

[stevepiercy]

Yup, you got it! Of course, we have to have that documentation available to link to. 😉

We were talking about how to make a GSoC project that focuses on documentation more interesting. I think this feature would qualify.