new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

GitHub Primer · all subjects

page-header

13 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Page header purpose and usage

Page header determines the top-level headings of a UI. It arranges elements that apply context and provide navigation for the current page. The elements within page header are rearranged and displayed accordingly depending on the viewport size and context of the page.

Page header anatomy and components

Page header can include a context bar, title bar, description, and contextual navigation pertaining to the current page. By default, the context bar is visible on narrow viewports only, the title bar is visible on all viewports, and the leading action and trailing action are visible on regular viewports.

Context bar purpose and visibility

The context bar is intended to set context for the user on smaller viewports and provide any actions that fit within the context bar. By default, the context bar including its actions is only visible on narrow viewports.

Context bar parent link

The parent link is the default way to let users navigate up in the hierarchy on narrow viewports.

Context bar as generic slot

The context bar is a generic slot for any component above the title region. Use it for custom breadcrumbs and other navigation elements instead of parent link.

Title bar contents

The title bar can include a static page title, actions, and leading and trailing visuals.

Default title variant usage

Default title variant is the most common page title size. Use for static titles in most situations.

Large title variant usage

Use large title variant for user-generated content such as issues, pull requests, or discussions.

Subtitle variant usage

Use subtitle variant when a title is already present in the page, such as in a Split page layout.

Leading visual in title bar

Leading visuals are optional and appear at the start of the title. They can be octicons, avatars, and other custom visuals that fit a small area. Leading visuals remain visible on all viewports.

Trailing visual in title bar

Trailing visual and trailing text can display auxiliary information. They're placed at the right of the item, and can denote status, privacy details, etc. Trailing visuals remain visible on all viewports.

Leading action in title bar

A back button can be used as a leading action for local navigation. On narrow viewports, use parent link instead.

Trailing action in title bar

Trailing action can display subtler actions aligned directly next to the title. On narrow viewports, replace the trailing action with an item in an overflow button.

Give your agent this brain