Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refactor(pie-docs): DSW-2324 update the tag overview docs #2067

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

raoufswe
Copy link
Member

@raoufswe raoufswe commented Nov 15, 2024

Describe your changes (can list changeset entries if preferable)

  • updates the tag component docs to latest designs

Author Checklist (complete before requesting a review)

  • I have performed a self-review of my code
  • I have added thorough tests where applicable (unit / component / visual)
  • I have reviewed the Docs site preview
  • If there are visual test updates, I have reviewed them properly before approving

Reviewer checklists (complete before approving)

Reviewer 1

  • I have reviewed the Docs site preview
  • If new links have been added, I have tested them in the preview
  • If there are visual test updates, I have reviewed them

Reviewer 2

  • I have reviewed the Docs site preview
  • If new links have been added, I have tested them in the preview
  • If there are visual test updates, I have reviewed them

Copy link

changeset-bot bot commented Nov 15, 2024

🦋 Changeset detected

Latest commit: 32ea1ac

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
pie-docs Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@raoufswe raoufswe force-pushed the dsw-2324-update-overview-docs branch from 0ab86dc to 99e9dfc Compare November 15, 2024 15:40
@raoufswe raoufswe marked this pull request as ready for review November 15, 2024 15:41
@raoufswe raoufswe requested review from a team as code owners November 15, 2024 15:41
@pie-design-system-bot
Copy link
Contributor

pie-design-system-bot commented Nov 15, 2024


Fails
🚫 You currently have an unchecked checklist item in your PR description.

Please confirm this check has been carried out – if it's not relevant to your PR, delete this line from the PR checklist.

Generated by 🚫 dangerJS against 32ea1ac

@raoufswe raoufswe changed the title Dsw 2324 update overview docs refactor(pie-docs): DSW-2324 update the tag overview docs Nov 15, 2024
} %}

{% list {
type: listTypes.ordered,
items: [
"**Icon (Optional):** Visually supports the label.",
"**Label:** Provides information about the content or purpose of the tag.",
"**Container**: Background container that organises the information."
"**Label:** Provides informative information to the user.",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can feel Xander disapproving of this wording across the planet - I think "informative information" might be redundant. Could we remove "informative" please?

Suggested change
"**Label:** Provides informative information to the user.",
"**Label:** Provides information to the user.",

"**Label:** Provides information about the content or purpose of the tag.",
"**Container**: Background container that organises the information."
"**Label:** Provides informative information to the user.",
"**Trailing icon (Optional):** Indicates additional actions or further interactions."
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just to check we haven't missed a requirement here - does the trailing icon emit a different event to the leading?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

both leading and trailing icons don't emit any event, they are pure visuals.


Tag can use colour for visual categorisation.
The non-interactive variation should be used by default, and should be used when the tag doesn’t require any interactive features tied to the instance.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The non-interactive variation should be used by default, and should be used when the tag doesn’t require any interactive features tied to the instance.
The non-interactive variation should be used by default, and should be used when the tag doesn’t require any interactivity.

siggerzz
siggerzz previously approved these changes Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants