-
Notifications
You must be signed in to change notification settings - Fork 8
Description
Description
Following issue #1238
in the demo app
Right now the content used in the demo app is the one from the "definition" section of the "guideline" tab, but it is the long version of the definition and we want to use the short version instead.
Instead, the definition to use is the one under the title of the component at the top of the page.
We are missing the generic chip definition from @CyriaqueBillard , but all the other are ok.
in the dev documentation
- the OUDSChipPicker has a definition that is cut and not finished
- is it possible when you add complementary information to the definition to put it in separate paragraph:
ie: for OUDSLink
Link is a UI element that allows to navigate from one location to another, either within the same page or across different pages in the same resource, or to an external resource. Link’s primary function is navigation and it communicates its interactive nature visually and semantically. The OUDSLink proposes layout with text only or text with icon. It also proposes layout to navigate forward or backward. The link can be displayed in small or default size.
should read:
Link is a UI element that allows to navigate from one location to another, either within the same page or across different pages in the same resource, or to an external resource. Link’s primary function is navigation and it communicates its interactive nature visually and semantically.
The OUDSLink proposes layout with text only or text with icon. It also proposes layout to navigate forward or backward. The link can be displayed in small or default size.
Checklist for Core Team
- Tokens have been updated (if needed)
- Documentations have been updated (if needed)
- Unit tests have been updated and still pass
- UI tests have been updated and still pass
- Retrocompatibility has been checked, or broken API have been flagged as deprecated with a workaround
Metadata
Metadata
Assignees
Labels
Type
Projects
Status