You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Created by: Øyvind Nordhagen ([email protected]) on 2015/07/01 12:23:09 +0000
Votes at time of UserVoice import: 7
Sometimes properly naming a section is not enough to give our clients directions on how to use the CMS we've set up for them. I wish I could provide a description that would display over the list of entries when the section is selected in the entries interface and perhaps also in the sidebar of the entry editor.
A typical example would be a section that contains reusable content blocks like generic info, promos, teasers etc. that don't have their own URLS that the client might need to insert into other entries.
Actually this would be really useful for other stuff too, like globals, assets and users. That way I might not need to provide a separate manual on how to use the CMS. For users I know are power users maybe I could choose to disable these instructions.
This discussion was converted from issue #960 on July 13, 2021 03:55.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Sometimes properly naming a section is not enough to give our clients directions on how to use the CMS we've set up for them. I wish I could provide a description that would display over the list of entries when the section is selected in the entries interface and perhaps also in the sidebar of the entry editor.
A typical example would be a section that contains reusable content blocks like generic info, promos, teasers etc. that don't have their own URLS that the client might need to insert into other entries.
Actually this would be really useful for other stuff too, like globals, assets and users. That way I might not need to provide a separate manual on how to use the CMS. For users I know are power users maybe I could choose to disable these instructions.
Beta Was this translation helpful? Give feedback.
All reactions