NgDocPage

The page category

Any custom data that you can provide for the page and use on it via NgDocPage.data

The page demo components should be on object where key it's the component's class name and value it's class constructor

By default, the child routes of a page are shown in a fullscreen dialog. Set disableFullscreenRoutes to false to handle them yourself with a . It can be used for example in a demo that requires to show nested routes. Be careful however, only 1 router-outlet is allowed level, that can lead to collisions if multiple demos on the same page require nested routes.

If true the page will be hidden from the sidebar

Import Angular dependencies for the page. If you are using standalone components for demos and playgrounds, you don't need to import anything.

Path to the page markdown file

Render the page only for specific build configuration

Order is using for sorting entities in the sidebar

The page playgrounds should be on object where key it's the playground's name and value its playground configuration

List of providers for the page they will be available for all components on the page

The route of the entity (current sourceFileFolder name by default)

The entity title