Skip to content
This repository was archived by the owner on Nov 3, 2021. It is now read-only.
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file added assets/image/ListPage.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added assets/image/ListWithDefaultFilter.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
3 changes: 1 addition & 2 deletions docs/ContentPage.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,6 @@ Settings pages or feature pages are considered as content page

Content page should use `Page` with `content` as `layoutType`

![page layout type](./image/Page.png)
![content page](./image/ContentPage.png)

### Breadcrumb Group
Expand Down Expand Up @@ -31,7 +30,7 @@ A description is **required for all settings/ feature front pages** to provide c
<br />

### Page Action
Use `Inline` for page action and pass into `titleAction` on Page component for page action
Use [Inline](/#/Composition/Inline) for page action and pass into `titleAction` on Page component for page action
```jsx
import { FontAwesomeIcon } from '@Domain/Icons';
import { TooltipPopover } from '@Domain/Popovers';
Expand Down
1 change: 0 additions & 1 deletion docs/FormPage.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,6 @@ Pages with form or forms (wizard) are considered as form page

Form page should use `Page` with `form` as `layoutType`

![page layout type](./image/Page.png)
![form page](./image/FormPage.png)

### Breadcrumb Group
Expand Down
Loading