wagtail / guide

A website to teach Wagtail CMS to content editors, moderators and administrators.
https://guide.wagtail.org
BSD 3-Clause "New" or "Revised" License
32 stars 26 forks source link

Browser-level UI settings (Accessibility features documentation) #333

Closed ginandze closed 1 year ago

ginandze commented 1 year ago

Browser-level UI settings

ginandze commented 1 year ago

Browser-level UI settings Sidebar expanded/collapsed By default, the sidebar is expanded. You may want to collapse it, in order to have more space to work on the Dashboard.

image

To collapse it, simply click on the white arrow button at the top-right of the sidebar.

Rich text toolbar pinned/unpinned While on the edit screen, you may need to pin the rich text toolbar for easy access. To do this, highlight a piece of the text you are typing. The rich text toolbar will appear.

image Click on the pin at the top-right of this toolbar to pin it at the top of the text area.

Minimap opened/closed In the edit screen, Wagtail has a minimap feature which gives you a high-level overview of your page. It is useful for quick navigation to the various parts of the page you are working on. The minimap is shown on the right side of the editor screen. You can click on the various tabs to quickly jump to different sections of your page. The editor screen minimap is opened by default. To close it, click on the white arrow button at the top-right of the minimap.

image

Currently-open side panel While on the edit screen, you can access the currently-open side panel by clicking on any of the items on the top-right taskbar menu, such as Status, Comments, Preview or History. To close the side panel, click on the toggle button at the top of the side panel. image

thibaudcolas commented 1 year ago

@ginandze I think this should be done at the same time as #329. Please be mindful that screenshots are a lot of work to maintain. It’s not really sustainable for us to have as many as you suggest here.

ginandze commented 1 year ago

@ginandze I think this should be done at the same time as #329. Please be mindful that screenshots are a lot of work to maintain. It’s not really sustainable for us to have as many as you suggest here.

Understood @thibaudcolas I'll work on this, thanks.