You can add to this if you wish, or hide it by clicking the down-arrow symbol in the upper right hand corner of the site. This is where you go to start creating things like pages, events, articles, etc. If you click on this, you should get a page similar to the one shown in the picture below, where everything you have on your site is listed. These are organized in a table format, with the title found on the right, followed horizontally by the type of content event, person, slideshow image, etc.
You will be able to see all of the SiteNow apps, including background image, articles, events, featured slider, people, and SiteNow SEO search engine optimization. Here you can do things like disabling demo content and looking at the details of each type of app. These details can be helpful for learning what an app looks like, what it does, and what it can be used for. You can add another HawkID user to the site on this page, and you can also transfer site ownership.
When you view an administration page, the page will be displayed normally in the full content area of the website and the Back to site button will appear in the top left corner of the website in the administration toolbar. The Windows Fax and Scan toolbar has few commands, so the better version labels the most important ones. Place the most frequently used groups first. Within a group, put the commands in their logical order. Overall, the commands should have a logical flow to make them easy to find, while still having the most frequently used commands appear first.
Doing so is most efficient, especially if there is overflow. Use group dividers only if the commands across groups are weakly coupled.
Doing so makes the groupings obvious and the commands easier to find. Avoid placing destructive commands next to frequently used commands.
Use either order or grouping to get separation. Also, consider not placing destructive commands in the toolbar, but only in the menu bar or context menus instead. Use the overflow chevron to indicate that not all commands can be displayed. But use overflow only if there isn't sufficient room to display all the commands. The overflow chevron indicates that not all commands are displayed, but more of them could be with a better layout.
Make sure that the most frequently used commands are directly accessible from the toolbar that is, not in overflow in small window sizes. If necessary, reorder the commands, move less frequently used commands to menu buttons or split buttons, or even remove them completely from the toolbar.
If this remains a problem, reconsider your choice of toolbar style. Generally, toolbars work great together with menu bars because having both allows each to focus on their strengths without compromise.
On hover, display the button affordance to indicate that the icon is clickable. After the tooltip timeout, display the tooltip or infotip. For mode buttons, display the control to reflect the currently selected mode. If the mode affects the behavior of mouse interaction, also change the pointer. For property buttons and drop-down lists, display the control to reflect the state of the currently selected objects, if any.
On interaction, update the control's state and apply the change to the selected objects. If nothing is selected, do nothing. Exception: On rare occasions, a toolbar command can be used more efficiently modally. In such cases, use double-click to toggle the mode. In this example, double-clicking the Format painter command enters a mode where all subsequent clicks apply the format. Users can leave the mode by left single-clicking. Exception: Windows 7-style toolbars use icons only for commands whose icons are well known; otherwise they use text labels without icons.
Doing so improves the clarity of the labels, but requires more space. Make sure toolbar icons are clearly visible against the toolbar background color.
Always evaluate toolbar icons in context and in high-contrast mode. Choose icon designs that clearly communicate their purpose, especially for the most frequently used commands. Well-designed toolbars need icons that are self-explanatory because users can't find commands efficiently using their tooltips. However, toolbars still work well if icons for a few less frequently used commands aren't self-explanatory.
Choose icons that are recognizable and distinguishable, especially for the most frequently used commands. Make sure the icons have distinctive shapes and colors. Doing so helps users find the commands quickly even if they don't remember the icon symbol. For more information and examples, see Icons. If you are using menu buttons and split buttons in a toolbar, try to use the following standard menu structures and their relevant commands whenever possible.
Unlike menu bars, toolbar commands don't take access keys. These commands mirror the commands found in standard menu bars, so they should be used only for primary toolbars. This list shows the button labels and type with their order and separators, shortcut keys, and ellipses.
Note that the command for displaying and hiding the menu bar is in the View menu. These commands supplement standard menu bars. Note that the command for displaying and hiding the menu bar is in the Tools menu. The supplemental toolbar category names differ from the standard menu category names because they need to be more encompassing.
For example, the Organize category is used instead of Edit because it contains commands that aren't related to editing. To maintain consistency between menu bars and toolbars, use the standard menu category names if doing so wouldn't be misleading.
In this example, the toolbar should use Edit instead of Organize for consistency because it has the standard Edit menu commands. Palette windows use shorter title bars to minimize their screen space. Put a Close button on the title bar. Provide a context menu for window management commands. Display this context menu when users right-click on the title bar.
When possible and useful, make palette windows resizable. Indicate that the window is resizable, using resize pointers when over the window frame. When a palette window is redisplayed, display it using the same state as last accessed. When closing, save the window size and location.
When redisplaying, restore the saved window size and location. Also, consider making these attributes persistent across program instances on a per user basis.
Provide customization for toolbars consisting of two or more rows. Only the unlabeled icons style needs customization. Simple toolbars with few commands don't need customization. Provide a good default configuration. Users shouldn't have to customize their toolbars for common scenarios. Don't depend upon users customizing their way out of a bad initial configuration. Assume that most users won't customize their toolbars.
For the Customize command, display an options dialog box that provides the ability to choose which toolbars are displayed and the commands on each toolbar. Provide a Reset command to return to the original toolbar configuration in the Customize options dialog box.
Provide the ability to customize the toolbars using drag-and-drop in the following ways:. While toolbar commands are used for immediate actions, sometimes more information is needed to perform the action. For example, a formatting toolbar in Microsoft Excel gives you access to things like making text bold or changing text alignment with other common buttons. In an Internet browser , toolbars add functionality that may not come pre-installed.
For example, with the Google toolbar, you can get access to exclusive Google features. If you are missing an application's toolbar, try pressing Alt on the keyboard, as some programs hide the toolbar until Alt is pressed. In Windows 8 and Windows 10, some programs and apps may only show a hidden toolbar if the mouse cursor is positioned at top of the window.
0コメント