-
Notifications
You must be signed in to change notification settings - Fork 794
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
[UI Content Design Guild] Notification component topic is missing content #4165
Comments
Related to #4127 |
@sstrubberg @laurenmrice @aagonzales We're also wondering about the error, warning, info, success statuses. We're sure why that's mentioned in the |
@sstrubberg Hey, Scott. How does this look? #4238 |
@sstrubberg @alina-jacob I was told to hold off on making content changes to the Notification component topic because it was under construction. May I proceed now, please? |
@lesnider The new content for Notification is still currently in a couple different PRs and has not merged into our live website yet, so I would still hold off on making any new changes to the content until those PRs are merged. We will reach out to you once Notification can be worked on. Thanks! |
@lesnider The PRs on our side are merged and the Notifications Usage tab is up to date on the website. This is available to be worked on now. I also noticed there is another issue open with this same name here: #4238. Do these need to be separate issues, or can we combine them into one? |
@laurenmrice Thanks! I will start working on Notifications this week. I closed 4238 as a duplicate. No idea how that happened. :) |
@laurenmrice I know why there was a duplicate (#4238). @sstrubberg asked me to use a new template (#4165 (comment)) and so I did. Should we reopen 4328 and close this one instead? I have only a few days before vacation, but perhaps I can work on this topic before I leave or as soon as I return. @sstrubberg What do you think? Should I use this issue or reopen #4238 to open PRs? |
https://carbondesignsystem.com/components/notification/usage/
Need explicit guidance for creating content for messages (error, information, warning).
The text was updated successfully, but these errors were encountered: