Home Page

Responsive application home layouts with an app bar, navigation, content, and footer

Home Page

The home page layout composes an app bar with flexible navigation, a full-width main region, focused content, and a footer. Its navigation adapts to the page container, which makes the layout suitable for full pages, previews, and embedded application shells.

Application Home

Product Home Page

Primary navigation gives way to a native app-bar menu when the container becomes compact.

Release confidence, built in

Ship software with a quieter control room.

DuskMoon brings deployments, service health, and team decisions into one legible workspace.

Production

Service health

All systems operational

API latency

84 ms

Deployments

18

Availability

99.99%

Designed for momentum

Everything important, nothing noisy.

Observe

A shared operating picture

See releases and incidents in the context your whole team understands.

Decide

Clear paths to action

Move from signal to owner without searching across disconnected tools.

Deliver

Release with confidence

Keep every rollout visible from first commit through production health.

Anatomy

Class Role
.home-page Container-query root and page surface
.home-page-frame Full page frame
.home-page-header App-bar header slot
.home-page-nav Primary wide-container navigation
.home-page-actions Optional wide-container app-bar actions
.home-page-menu-trigger Compact-container navigation trigger
.home-page-mobile-menu Compact-container navigation surface
.home-page-main Main landmark and flexible content region
.home-page-content Centered readable content width
.home-page-hero One-column hero that becomes a two-column composition in wide containers
.home-page-footer Footer region

Include both .home-page-nav and .home-page-menu-trigger. Container queries choose the appropriate control for the available width. The compact menu can use the native Popover API, which provides light dismissal and Escape-key handling without application state.

Keep identical destinations in both navigation surfaces, and use aria-current="page" for the active destination.

Accessibility

  • Give every navigation landmark a distinct label.
  • Preserve a single page-level h1; feature sections should begin with h2.
  • Use links for destinations and buttons only for actions or menu disclosure.
  • Ensure the menu remains reachable and operable at 200% zoom, where the compact container state may activate.