-
Notifications
You must be signed in to change notification settings - Fork 190
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
Ensure screenshots use uniform naming conventions across components #2815
Comments
I'm going to adjust the description of this issue to accommodate the names we use across all documentation screenshots. Even if we can't automate screenshots right now, we can at least make these more minor tweaks for consistency. It doesn't seem like teams care much about who we name the demo users/screenshots, so just need to make a decision and work with each team to ensure these are updated. |
This is very similar to this issue. I'm going to close out that one, and update this one to include uniform naming across all components, regardless of the screenshot automation mechanism. |
I am going to ensure usernames are "My Organization" -- I'll take a look at each of the following components and their screenshots next week:
I did not find any instances across SM, so this will be SaaS-focused. Of course, anyone is welcomed to create a backlog issue if we would like to incorporate a unified sandbox environment/different user personas automated in the docs screenshots. This issue solely aims to ensure all org names are the same across the screenshots to begin with. |
Updating in Modeler this week, and then this can be closed out 👍 |
Identity screenshots include user "Bark Barkins." This should be aligned with our other screenshots and test/demo users.
Additional note: I thought we had documentation on what to include or not include in screenshots, but I can't find it on this page. FYI @christinaausley
(Edit by Christina below)
Need to:
Tasks
The text was updated successfully, but these errors were encountered: