JSPM

  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 3109
  • Score
    100M100P100Q129299F
  • License EUPL-1.2

Page component for the Municipality of Utrecht based on the NL Design System architecture

Package Exports

  • @utrecht/page-css
  • @utrecht/page-css/dist/index.css
  • @utrecht/page-css/dist/index.mjs

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@utrecht/page-css) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Page component

Component that centers the page. The page maximizes the width of the content for large viewports, to keep the line length of texts readable and avoid large horizontal distances between related components.

Typically the contents of the page component are:

  • Page Header component
  • Page Content component
    • Main content
    • Complimentary content
  • Page Footer component

API

  • CSS class name: utrecht-page
  • Web component: <utrecht-page>
  • Angular/React/Vue.js component: UtrechtPage

CSS implementation

Margin

To create some transparent space around the page, margin-inline CSS variables are provided. However, to automatically horizontally center the page margin-inline: auto needs to be used.

Achieving both goals is made possible by implementing the margin-inline as padding-inline on a transparent container element. The only downside to this approach is that margin collapsing won't work anymore, but that doesn't seem like anyone would ever need for a component that realistically is only used once per document.

Padding

Padding is not applied directly in the page component itself, but in the child components such as Page Header, Page Content and Page Footer.

Relevante WCAG regels

  • WCAG eis 2.4.1: gebruik de skip link zodat gebruikers direct naar de main page content kunnen gaan.
  • WCAG eis 2.4.2: de pagina moet een duidelijke titel hebben