Summary

Description

Support smart search with meta-tagging system in-

1. Asset Browser
2. Script Canvas
3. Entity outliner
4. Viewport
5. Inspector
6. Example: searching for player

As a team working on O3DE rev the engine test, we have come across several inconsistent and incorrect tool-tips messages in the editor.

Tooltip are located in many locations throughout the editor this includes; the animation system, asset browser, UI editor, outliner, inspector, main header, global settings, PhysX global settings, etc.

Fixing individual tooltips messages seems not like the best use of our time based on the number of issues we are seeing. This is because all tooltips text are stored inline and not centralized and thought about holistically. The AC for this project is as followed.

• We would like for all of the tooltips in the editor to be combined into a centralized location for easy update.
• This could be a TXT, XML, Excel or some kind of easily readable file(s). Developer needs to research best method.
• We should include some rules about how we should be speaking to the customer. This should be reflected as comments in the beginning of this new document so as developers add to the document, they can read the rules before updating the text.
• Rules needing to be confirmed by docs. William Hayward and Doug Erickson please give your thoughts to help confirm standards to reflect most recent writing practices.
• We do not use camel case.
• We only capitalize proper names, example, "Script Canvas."
• First letter should always be capitalized.
• periods should be used.
• Text should be written in future tense. Not past tense.
• Tooltip text should reflect what we are looking and how to accomplish that task.
• Length of text should never exceed 1 paragraph of text. If text is longer than 1 paragraph we should be redirecting a customer to a secondary page to get more information. No specific standard set on where customer must go.
• We should prepare this text to be localized into multiple languages.
• This means we should be careful about terminology that could be misunderstood in different languages.
• This task will also include pulling out all the tooltip text throughout the editor and replace it with some kind of common global variable.
• We will also need docs to do a pass on all the tooltip text once it has been centralized into a file(s).

Meeting Details

• Date/Time: 09/22/2021 @ 11:00am PT
• Location: Discord SIG-UI-UX Voice Room
• Moderator: UI/UX SIG Committee
• Note Taker UI/UX SIG Committee

This meeting is for the SIG UI-UX Office Hours. For details of the office hours, please visit here.

To sign up the Office Hours, please the comments below with following information:

• Topic
• Type: [request approval/request review/brainstorm ideas/submit research or design request/others]
• Background or links to the related docs
• Possible length of discussion: 30 mins or 1 hour

UI-UX SIG Meeting — today's content for 03-16-2022

Hi O3DE Community,
We want to invite you to our conversation about today's newest content, design specifications, and program update.

This weeks conversation: we will continue building our multiplayer game with Gene Walters ( @AMZN-Gene ). As we all know building a multiplayer game requires a good understanding of all the foundational parts of O3DE. This includes networking, game logic, and scripting. Understanding how all these parts come together properly is the key in making it work. Come take part in our conversation as we discover what's working, what's not working, and what it takes to build a multiplayer game in O3DE.

In our previous meeting we hosted Gene Walters part one of setting up multiplayer. So if you missed part one don't fret. We are working on re-broadcasting it on YouTube in a new community channel called "O3DE Community Spotlight" which our new community Manager - @aFinchy is working on now. We will post an update to the group as soon as we have a link available.

Schedule

• Date/Time: 03/16/2022 @ 10:00am PT
• Location: Discord SIG-UI-UX Voice Room
• Moderator: UI/UX SIG Committee
• Note Taker UI/UX SIG Committee

Meeting Details

We want to invite you to our Sig UX UI bi-weekly meeting*.* This is a bi-weekly meeting and we will cover the following items from the UX team.

• New and interesting topics that O3DE has hot of the press. Because these items are so new we are likely to find bugs and new feedback from the community. This is kind of the point. As we let you observe and talk to us we can make adjustments to the workflows before it goes out to the masses.
• RTE program updates and new details. Any new findings, results, or feedback.
• Check in with designer about problems they are facing regarding tickets and if any help is required
• Feedback from any research previously done regarding tickets.
• Assign designers or UI-UX SIG members UX work. This includes deadlines and expectations of work completed.
• In some cases a show and tell may be required to talk through a pending issue or new feature. However we we’ll try to hold these for design critiques for every other Wednesday.
• Request for research and or conduct live research.

The SIG-UI-UX Meetings repo contains the history past calls, including a link to the agenda, recording, notes, and resources.

To sign up for a topic in the SIG-UI-UX Bi-weekly meeting.

• Please add a comment to this ticket with following information:
• Discord name:
• Topic of conversation:
• How much time you might need:
• Any UX resource you have already been working with and if their attendance is required.
• ** Any resource to help explain your issue **

How can I use the Bi-weekly meeting?

• Please add any specific agenda items you would like to talk about to the ticket.
• We will address any agenda items first. These items should be related to outstanding tickets.
• This meeting is not about creating new tickets but reviewing and fixing outstanding tickets.
• If you have speciality such as research, design, or a unique understanding of game development. Let us know so we can help facilitate where we can use your help the most.
• Offer to be a note taker. We always need some help here. Facilitating a meeting and being a note taker can be tough, so any one willing to help will be appreciated.
• Offer to be a person willing to help put together agenda items and or review agenda items from previous meetings.

What should I bring to the bi-weekly meeting?

• Nothing is required but the following items would be helpful
o A list of ticket you are interested in addressing
o An update on tickets you have been working on
o Some prepared questions about the tickets you own

Cut-off time / cancellation

• For the UI/UX bi-weekly meeting the UI-UX SIG team will check the GitHub Agenda item ticket 24 hours before the scheduled meeting, if no one signs up in the session, we will lock down the agenda of that day.
• If you are unable to attend after signing up, Please just reach out in discord or on the ticket to let us know about the change.

Meeting Details

• Date/Time: June 24, 2021 @ 18:00pm UTC / 2:00pm ET / 11:00am PT
• Location: Discord SIG-UI-UX Voice Room
• Moderator: Josh / Liv
• Note Taker Josh / Liv

The SIG-UI-UX Meetings repo contains the history past calls, including a link to the agenda, recording, notes, and resources.

Meeting Agenda

• Introductions - tell us about yourself and your interest in the UI/UX SIG!
• Feedback mechanisms for the charter, other documents
• Rev the Engine introduction
• Meeting frequency

Action Items

TBD

Open Discussion Items

List any additional items you'd like to address in the comments below

I think it will be nice if a user can right click the GameFolder: <project path> for an option to open the file explorer at the project's location

Meeting Details

• Date/Time: 09/01/2021 @ 11:00am PT
• Location: Discord SIG-UI-UX Voice Room
• Moderator: UI/UX SIG Committee
• Note Taker UI/UX SIG Committee

This meeting is for the SIG UI-UX Office Hours. For details of the office hours, please visit here.

To sign up the Office Hours, please the comments below with following information:

• Topic
• Type: [request approval/request review/brainstorm ideas/submit research or design request/others]
• Background or links to the related docs
• Possible length of discussion: 30 mins or 1 hour

Meeting Details

• Date/Time: 09/08/2021 @ 11:00am PT
• Location: Discord SIG-UI-UX Voice Room
• Moderator: UI/UX SIG Committee
• Note Taker UI/UX SIG Committee

This meeting is for the SIG UI-UX Office Hours. For details of the office hours, please visit here.

To sign up the Office Hours, please the comments below with following information:

• Topic
• Type: [request approval/request review/brainstorm ideas/submit research or design request/others]
• Background or links to the related docs
• Possible length of discussion: 30 mins or 1 hour

SIG-UI-UX Office Hours for 02-23-2022

Hi O3DE Community,
We want to invite you to our UX UI design review and office hours.

• Date/Time: 02-23-2022 @ 10:00am PT
• Location: Discord SIG-UI-UX Voice Room
• Moderator: UI/UX SIG Committee
• Note Taker UI/UX SIG Committee

The SIG-UI-UX Meetings repo contains the history past calls, including a link to the agenda, recording, notes, and resources.

To sign up the Office Hours.
Please add a comment to this ticket with following information:

• Discord username:
• Topic of conversation:
• How much time you might need:
• Any UX resource you have already been working with and if their attendance is required.

This is a bi-weekly meeting will cover the following items.

• UI-UX SIG team will show some of the O3DE workflows that are currently in-progress.
• UI-UX SIG will provide feedback to other UX designers about their O3DE designs.
• UI-UX SIG will provide feedback to the community about O3DE work they are working on.
• Will have open conversations about UX/UI related problems coming down the pipeline.
• Discuss UX tickets

Schedule

• The Sig UX-UI meeting (Triage and UX updates) will be on every other Wednesday at 10-11pm PST
• The design review/Office hours will be on the opposite weeks.
• This means every Wednesday we have something fun for UX going on.

How do I sign up get feedback?

• You can sign up by going to https://github.com/o3de/sig-ui-ux/issues
• Find the specific event you are interested in attending and getting feedback on.
  • In the comment section of that ticket place the details you would like to talk about.
  • Please include your name and/or Discord Name
  • The area of topic you would like to cover
  • The amount of time you might need to review this topic
  • Any individuals you have been already working
  • Any specific people you would like to attend this session for help.

How can I use office hours:

• Request a "sign-off" on your project from the UI-UX SIG.
• Usability/UX review of your designs/mock-ups.
• Discuss certain customer pain points or UX related topics.
• Brainstorm ideas or solutions to a user problem or feature.
• Submit user research or UX design requests.
  What should I bring to the office hour:
• Nothing is required but the following items would be helpful
  • A brief project overview or documentation, This should include the following
  • A simple user problem statement. As a user I want to solve this problem...
  • Who is your audience? Who are the users/user groups affected by the change?
  • What is your vision behind this change or update?
  • What is your UX issue related to: user interface, usability testing, learnability, documentation etc?
  • Materials/Workflows of the existing product. Sketches or wire-frames of ideas. PR/FAQ are also help.

Cut-off time / cancellation

• The UI-UX SIG Office Hours is sign-up based. We will check the topics 24 hours before the scheduled office hour, if no one signs up in the session, we will lock down the agenda of that day.
• If you are unable to attend after signing up, Please just reach out in discord or on the ticket to let us know about the change.

SIG-UI-UX Office Hours for 05-05-2022

Hi O3DE Community,
We want to invite you to our UX UI design review and office hours.

• Date/Time: 04-27-2022 @ 10:00am PT
• Location: Discord SIG-UI-UX Voice Room
• Moderator: UI/UX SIG Committee
• Note Taker UI/UX SIG Committee

The SIG-UI-UX Meetings repo contains the history past calls, including a link to the agenda, recording, notes, and resources.

To sign up the Office Hours.
Please add a comment to this ticket with following information:

• Discord username:
• Topic of conversation:
• How much time you might need:
• Any UX resource you have already been working with and if their attendance is required.

This is a bi-weekly meeting will cover the following items.

• UI-UX SIG team will show some of the O3DE workflows that are currently in-progress.
• UI-UX SIG will provide feedback to other UX designers about their O3DE designs.
• UI-UX SIG will provide feedback to the community about O3DE work they are working on.
• Will have open conversations about UX/UI related problems coming down the pipeline.
• Discuss UX tickets

Schedule

• The Sig UX-UI meeting (Triage and UX updates) will be on every other Wednesday at 10-11pm PST
• The design review/Office hours will be on the opposite weeks.
• This means every Wednesday we have something fun for UX going on.

How do I sign up get feedback?

• You can sign up by going to https://github.com/o3de/sig-ui-ux/issues
• Find the specific event you are interested in attending and getting feedback on.
  • In the comment section of that ticket place the details you would like to talk about.
  • Please include your name and/or Discord Name
  • The area of topic you would like to cover
  • The amount of time you might need to review this topic
  • Any individuals you have been already working
  • Any specific people you would like to attend this session for help.

How can I use office hours:

• Request a "sign-off" on your project from the UI-UX SIG.
• Usability/UX review of your designs/mock-ups.
• Discuss certain customer pain points or UX related topics.
• Brainstorm ideas or solutions to a user problem or feature.
• Submit user research or UX design requests.
  What should I bring to the office hour:
• Nothing is required but the following items would be helpful
  • A brief project overview or documentation, This should include the following
  • A simple user problem statement. As a user I want to solve this problem...
  • Who is your audience? Who are the users/user groups affected by the change?
  • What is your vision behind this change or update?
  • What is your UX issue related to: user interface, usability testing, learnability, documentation etc?
  • Materials/Workflows of the existing product. Sketches or wire-frames of ideas. PR/FAQ are also help.

Cut-off time / cancellation

• The UI-UX SIG Office Hours is sign-up based. We will check the topics 24 hours before the scheduled office hour, if no one signs up in the session, we will lock down the agenda of that day.
• If you are unable to attend after signing up, Please just reach out in discord or on the ticket to let us know about the change.

Meeting Details

• Date/Time: 09/29/2021 @ 11:00am PT
• Location: Discord SIG-UI-UX Voice Room
• Moderator: UI/UX SIG Committee
• Note Taker UI/UX SIG Committee

This meeting is for the SIG UI-UX Office Hours. For details of the office hours, please visit here.

To sign up the Office Hours, please the comments below with following information:

• Topic
• Type: [request approval/request review/brainstorm ideas/submit research or design request/others]
• Background or links to the related docs
• Possible length of discussion: 30 mins or 1 hour

UI-UX SIG Meeting — todays content for 03-02-2022

Hi O3DE Community,
We want to invite you to our meeting program feedback, RTE updates, triage, and design specific conversations.

The purpose of this meeting is to retest the Multiplayer workflow from several months ago when the documentation wasn't complete. We will be testing if the new documentation provided changes the status of this workflow from fail to pass. @AMZN-Gene will drive this process for us and the community can see how this process works. Come and join us for all the fun.

Schedule

• Date/Time: 03/02/2022 @ 10:00am PT
• Location: Discord SIG-UI-UX Voice Room
• Moderator: UI/UX SIG Committee
• Note Taker UI/UX SIG Committee

Additional details we might cover

•RTE program updates and new details. Any new findings, results, or feedback.
• Check in with designer about problems they are facing regarding tickets and if any help is required
• Feedback from any research previously done regarding tickets.
• Assign designers or UI-UX SIG members UX work. This includes deadlines and expectations of work completed.
• In some cases a show and tell may be required to talk through a pending issue or new feature. However we we’ll try to hold these for design critiques for every other Wednesday.
• Request for research and or conduct live research.
• Close out tickets if completed.

The SIG-UI-UX Meetings repo contains the history past calls, including a link to the agenda, recording, notes, and resources.

To sign up for a topic in the SIG-UI-UX Bi-weekly meeting.

• Please add a comment to this ticket with following information:
• Discord name:
• Topic of conversation:
• How much time you might need:
• Any UX resource you have already been working with and if their attendance is required.
• ** Any resource to help explain your issue **

How can I use the Bi-weekly meeting?

• Please add any specific agenda items you would like to talk about to the ticket.
• We will address any agenda items first. These items should be related to outstanding tickets.
• This meeting is not about creating new tickets but reviewing and fixing outstanding tickets.
• If you have speciality such as research, design, or a unique understanding of game development. Let us know so we can help facilitate where we can use your help the most.
• Offer to be a note taker. We always need some help here. Facilitating a meeting and being a note taker can be tough, so any one willing to help will be appreciated.
• Offer to be a person willing to help put together agenda items and or review agenda items from previous meetings.

What should I bring to the bi-weekly meeting?

• Nothing is required but the following items would be helpful
o A list of ticket you are interested in addressing
o An update on tickets you have been working on
o Some prepared questions about the tickets you own

Cut-off time / cancellation

• For the UI/UX bi-weekly meeting the UI-UX SIG team will check the GitHub Agenda item ticket 24 hours before the scheduled meeting, if no one signs up in the session, we will lock down the agenda of that day.
• If you are unable to attend after signing up, Please just reach out in discord or on the ticket to let us know about the change.

UI-UX SIG Meeting — todays content for 02-02-2022

Hi O3DE Community,
We want to invite you to our meeting program feedback, RTE updates, triage, and design specific conversations.

This weeks meeting will focus on our upcoming Sig UX initiative for 2022. Including our community engagement in SIG UI-UX. We will go through the program details including some of the following:

• Expert interviews lineup for the next 6 months.
• Gamification process - need feedback
• Roadmap visibility
• Community leadership

It should be lots of fun and I'm looking forward to the conversation.

Schedule

• Date/Time: 02/02/2022 @ 10:00am PT
• Location: Discord SIG-UI-UX Voice Room
• Moderator: UI/UX SIG Committee
• Note Taker UI/UX SIG Committee

Other meeting details we may review.

• Review outstanding ticket assigned previously.
• RTE program updates and new details. Any new findings, results, or feedback.
• Check in with designer about problems they are facing regarding tickets and if any help is required
• Feedback from any research previously done regarding tickets.
• Assign designers or UI-UX SIG members UX work. This includes deadlines and expectations of work completed.
• In some cases a show and tell may be required to talk through a pending issue or new feature. However we we’ll try to hold these for design critiques for every other Wednesday.
• Request for research and or conduct live research.
• Close out tickets if completed.

The SIG-UI-UX Meetings repo contains the history past calls, including a link to the agenda, recording, notes, and resources.

To sign up for a topic in the SIG-UI-UX Bi-weekly meeting.

• Please add a comment to this ticket with following information:
• Discord name:
• Topic of conversation:
• How much time you might need:
• Any UX resource you have already been working with and if their attendance is required.
• ** Any resource to help explain your issue **

How can I use the Bi-weekly meeting?

• Please add any specific agenda items you would like to talk about to the ticket.
• We will address any agenda items first. These items should be related to outstanding tickets.
• This meeting is not about creating new tickets but reviewing and fixing outstanding tickets.
• If you have speciality such as research, design, or a unique understanding of game development. Let us know so we can help facilitate where we can use your help the most.
• Offer to be a note taker. We always need some help here. Facilitating a meeting and being a note taker can be tough, so any one willing to help will be appreciated.
• Offer to be a person willing to help put together agenda items and or review agenda items from previous meetings.

What should I bring to the bi-weekly meeting?

• Nothing is required but the following items would be helpful
o A list of ticket you are interested in addressing
o An update on tickets you have been working on
o Some prepared questions about the tickets you own

Cut-off time / cancellation

• For the UI/UX bi-weekly meeting the UI-UX SIG team will check the GitHub Agenda item ticket 24 hours before the scheduled meeting, if no one signs up in the session, we will lock down the agenda of that day.
• If you are unable to attend after signing up, Please just reach out in discord or on the ticket to let us know about the change.

Meeting Details

• Date/Time: 08/04/2021 @ 11:00am PT
• Location: Discord SIG-UI-UX Voice Room
• Moderator: UI/UX SIG Committee
• Note Taker UI/UX SIG Committee

This meeting is for the SIG UI-UX Office Hours. For details of the office hours, please visit here.

To sign up the Office Hours, please the comments below with following information:

• Topic
• Type: [request approval/request review/brainstorm ideas/submit research or design request/others]
• Background or links to the related docs
• Possible length of discussion: 30 mins or 1 hour

Meeting Details

• Date/Time: 08/11/2021 @ 11:00am PT
• Location: Discord SIG-UI-UX Voice Room
• Moderator: UI/UX SIG Committee
• Note Taker UI/UX SIG Committee

This meeting is for the SIG UI-UX Office Hours. For details of the office hours, please visit here.

To sign up the Office Hours, please the comments below with following information:

• Topic
• Type: [request approval/request review/brainstorm ideas/submit research or design request/others]
• Background or links to the related docs
• Possible length of discussion: 30 mins or 1 hour

Meeting Details

This meeting is for the SIG-UI-UX Bi-weekly meeting.

• Date/Time: 10/27/2021 @ 11:00am PT
• Location: Discord SIG-UI-UX Voice Room
• Moderator: UI/UX SIG Committee
• Note Taker UI/UX SIG Committee

The SIG-UI-UX Meetings repo contains the history past calls, including a link to the agenda, recording, notes, and resources.

To sign up for a topic in the SIG-UI-UX Bi-weekly meeting.

• Please add a comment to this ticket with following information:
  • Discord name:
  • Topic of conversation:
  • How much time you might need:
  • Any UX resource you have already been working with and if their attendance is required.
  • ** Any resource to help explain your issue **

What will we be covering?

• Ticket triage - We will go through our ticket backlog and do prioritization and sorting
• Review outstanding ticket assigned previously.
• Check in with designer about problems they are facing regarding tickets and if any help is required
• Feedback from any research previously done regarding tickets.
• Assign designers or UI-UX SIG members UX tickets. This includes deadlines and expectations of work completed.
• In some cases a show and tell may be required to talk through a pending issue or new feature. However we we’ll try to hold these for design critiques for every other Wednesday.
• We will review status of Rev the engine. Any new findings, results, or feedback.
• Close out tickets if completed.

How can I use the Bi-weekly meeting?

• Please add any specific agenda items you would like to talk about to the ticket.
• We will address any agenda items first. These items should be related to outstanding tickets.
• This meeting is not about creating new tickets but reviewing and fixing outstanding tickets.
• If you have speciality such as research, design, or a unique understanding of game development. Let us know so we can help facilitate where we can use your help the most.
• Offer to be a note taker. We always need some help here. Facilitating a meeting and being a note taker can be tough, so any one willing to help will be appreciated.
• Offer to be a person willing to help put together agenda items and or review agenda items from previous meetings.

What should I bring to the bi-weekly meeting?

• Nothing is required but the following items would be helpful
o A list of ticket you are interested in addressing
o An update on tickets you have been working on
o Some prepared questions about the tickets you own

Cut-off time / cancellation

• For the UI/UX bi-weekly meeting the UI-UX SIG team will check the GitHub Agenda item ticket 24 hours before the scheduled meeting, if no one signs up in the session, we will lock down the agenda of that day.
• If you are unable to attend after signing up, Please just reach out in discord or on the ticket to let us know about the change.

Summary:

Single paragraph explanation of the feature

What is the relevance of this feature?

Why is this important? What are the use cases? What will it do once completed?

Feature design description:

What are non-entity assets, where do we use them, why do we need them?

Do we really even need the Asset Editor - is there a better solution?

Asset Editor was initially created as a short-term solution to solve some technical problems, and we've never got the chance to delve deep to Asset Editor to improve its ease of use. is currently used by many features, such as input, physics, etc. However, the linkage between these components and the Asset Editor is obscure. The Asset Editor is divorced from the natural flow of the components, tools and system that utilize the defined assets. The experience to create and manage different assets on the Asset Editor is also unintuitive and hard to use.

Technical design description:

• Explain the technical portion of the work in enough detail that members can implement the feature.

• Explain any API or process changes required to implement this feature

• This section should relate to the feature design description by reference and explain in greater detail how it makes the feature design examples work.

• This should also provide detailed information on compatibility with different hardware platforms.

What are the advantages of the feature?

• Explain the advantages for someone to use this feature

What are the disadvantages of the feature?

• Explain any disadvantages for someone to use this feature

How will this be implemented or integrated into the O3DE environment?

• Explain how a developer will integrate this into the codebase of O3DE and provide any specific library or technical stack requirements.

Are there any alternatives to this feature?

• Provide any other designs that have been considered. Explain what the impact might be of not doing this.
• If there is any prior art or approaches with other frameworks in the same domain, explain how they may have solved this problem or implemented this feature.

How will users learn this feature?

• Detail how it can be best presented and how it is used as an extension or a standalone tool used with O3DE.
• Explain if and how it may change how individuals would use the platform and if any documentation must be changed or reorganized.
• Explain how it would be taught to new and existing O3DE users.

Are there any open questions?

• What are some of the open questions and potential scenarios that should be considered?

Meeting Details

• Date/Time: Sept 2th, 2021 @ 18:00pm UTC / 2:00pm ET / 11:00am PT
• Location: Discord SIG-UI-UX Voice Room
• Moderator: @yuyihsu, @AMZN-Liv
• Note Taker @amzn-leenguy

The SIG-UI-UX Meetings repo contains the history past calls, including a link to the agenda, recording, notes, and resources.

Overview

Hi Sig-UX-UI O3DE community,
It's time for our Sig UX meeting. It will take place via Discord in our SIG voice channel.

Here's our current agenda items for this meeting:

• UI/UX review processes - Will review update to the UX triage process. Talking about new tags and some of our plans in the next few weeks
• UI/UX triage - We have accumulated a number of tickets that we would like to review with the community and see how we should
• Rev the Engine program - Give further updates about ticket and process for RTE program.
• @jt [SCB_GameDesigner] would like to talk about:
  " A Native particle system. a particle system usually needs tweaking of the design patterns to get a good UI so the UX doesn't get wedged between a rock and a hard place. - PM: Owner - @ausrobis to be a part of this conversation

Here's a concrete example from other communities. Since the UI is at first usually just a front end by the programmers for the code that is written it suffers from the usual suspects. IMO one of the biggest and ugliest suspects from a UX standpoint frequently ends up being that the particle system redraws with every single UI setting change, even minor ones and viewport interactions.

This is infuriating to a user/designer and ends up in outright frustration between them and the programmers because aspects of the UX like that are addressed way too late in the programming/algorithm choices so they keep getting sidelined by labeling them a feature request. So just a heads up to help make the particle system one of the aspects that attracts peeps instead of repels them away from the platform. o3de/o3de#2889"_

If you’d like to propose additional topics, please leave comments in the GitHub thread for this meeting’s agenda.
We’ll make adjustments to the agenda items. With the increase number of individuals joining the O3DE community we will leave time in the beginning to allow for any new individuals to introduce themselves. Looking forward to connecting with you all!

Meeting History

The SIG-UI-UX Meetings repo contains the history past calls, including a link to the agenda, recording, notes, and resources. Please see specified folders. These folder structures may be rearranged in the next couple weeks.

In our last meeting we...

• UX/UI Sig Triage process - what we think this will look like.
• This includes tags and how often we should have this conversation
• Where we are at with Rev the Engine.
• What dose it mean to be a contributing member of UX /UI and how you level up.
  • Beginner level - 0 to 5 tickets (5 tickets)
  • Green level - 6 to 16 tickets (10 tickets)
  • Mid level - 17 to 32 tickets (15 tickets)
  • Advanced 33 to 53 tickets (20 tickets)
  • Staff 54 and above tickets (Free Swag)
• We are now using Zenhub to track tickets. Working on new swim lanes.
• Reminder - Joshua will be OOO on the next meeting. Yuyi and Lee will help drive this meeting in my absence

Summary:

The Sig UX-Ui team has been working on our ticket triage process. We've defined some of the new rules around how and what actions should be taken. We have worked with @forhalle, @yuyihsu, @AMZN-Liv, and @mcphedar to establish the best rules we can based on the most current process we have in place. Please note that anything added can be changed at a later point, but these will act as guiding principles until we know better.

What is the motivation for this suggestion?

Why is this important?
We already have three Sig Ux Ui documents that captures some of our rules, but these documents don't define the ticket triage process. We want to keep these documents up to date with the latest perspective.

What are the use cases for this suggestion?
I as a Sig Ux Ui member want to understand the rules of triage and how its performed. How would I learn about these rules?

What should the outcome be if this suggestion is implemented?
We will post this RFC for one week to receive feedback and address any open concerns about the process. If there are no major objections. We will add our content to the following governance charter documentation.

What is the strategy for adoption?

Yuyi and myself will be test driving the process within the next couple of weeks to make sure we haven't incorrectly defined any details and making any minor adjustments as we encounter new use cases. We will append those details to this document if any are encountered.

+ ------------------------------------------------------------------------ 

O3DE Sig UX/UI - process, guidelines and quality standard

In May 2021 we began working on our goal “Build a UX charter with scalable process and guidelines to support community autonomy”. The definition of this goal is; establish the UX process, guidelines and quality standard to enable the community to build consistent and quality user experience in O3DE.” The definition define below is not the finish line for us but a baseline we intend to continue to work on and refine. We are currently testing for a broad number of contributors and learning styles in the community to improve on this model.

If you're curious about our other Sig Ux UI charter documents, you can read them here.
UX charter, Interacting with UX Sig, Patterns for O3DE UX /UI

So what does the Sig UX-UI charter already have defined?

• Roles and responsibilities of the Sig UX-UI group.
• How do we handle disagreements.
• Define our cross-cutting activities and how do we process them.
• How the Sig UX-UI patterns can be changed or added to by community contributions.
• How do developers submit new UX content that doesn’t require Sig UX UI oversite.
• A bi-weekly meeting office hours and design review.
• A bi-weekly Sig-UX-UI Charter meeting (Review open tickets, RTE improvements, answer open questions from community).
• Promote design engagement with the O3DE community by openly doing our own internal design review externally.
• On-call UX rotation (Used for discord responses)
• Create a customer engagement model.
• Maintaining the Sig email channel for updates and feedback.
• Maintaining Sig calendar to keep track of meetings and times
• Established patterns for meeting notes and documentation for GitHub.
• Rules for reviewing content (office hours / design review) + document guidelines.

Sig UX-UI charter items still in progress:

• Creating a plan on how we will handle new RFC incoming to the Sig UX-UI.
• Begin publishing our UX pattern (BlueJay design system) so the community can have the same knowledge that we do as UX designers.

New items we are adding below.

• How do we process GitHub tickets?
• New "tags" for the GitHub ticket triage process.
• Established new rules on how to evaluate and processing tickets.
• How to promote community contributions.

Mission Statement (the why):

As the Sig UX UI group. Our job is to be the voice of the customer and actively improve the vision, workflows, and patterns of O3DE. This is accomplished by reviewing and improving user reported problems through different forms of UX methodologies. We are here to promote our UX foundational guidelines and give expert feedback. The Sig-ui-ux team is an active contributors/owner of new features or services being added to O3DE. Unlike most other Sig’s UX-UI is a cross cutting team and that means we need the ability to review tickets and potentially request for additional changes, change direction, or reject work. Each of these kinds of decision would be done in close collaboration with PM or SDM to verify stakeholder agreement.

How are we processing tickets?

We have now established some ground rules about how ticket triage will work. These are the steps until we learn better.

• A Sig-UI-UX Maintainer will drive our Bi-weekly Wednesday Sig Triage calls on tickets. As well as attend the #Sig-Release O3DE Issue Triage on Monday and Wednesday. During these meetings in conjunction with the Sig UI-UX Reviewer community we will apply our tags and status
  • A reviewer will have the ability to add remove tags in open conversation with the community. During that time the reviewer (Sig UI-UX representative) will be able to drive the conversation around what labels should be added and removed. Long term, I would expect that specific reviewer members who earn the label "Sig UX UI staff" would earn these same abilities and could step in to drive these conversations. Please see more about leveling up below.

Search queries:

• Ready for triage list:
  • https://github.com/o3de/o3de/issues?q=is%3Aopen+label%3Asig%2Fui-ux+-label%3Aneeds-ux-action%2C+-label%3Aneeds-ux-info%2C+-label%3Astatus%2Fneeds-ux-approval%2C+-label%3Aui-ux%2Fin-design%2C+-label%3Astatus%2Fux-approved
• Needs UX action but doesn’t currently have a UX owner.
  • Global search (top left of page) is:open label:sig/ui-ux, label:needs-ux-action -assignee:bhanuja-s -assignee:rainbj -assignee:amzn-leenguy -assignee:yuyihsu
  • https://github.com/o3de/o3de/search?q=is%3Aopen+label%3Asig%2Fui-ux%2C+label%3Aneeds-ux-action+-assignee%3Abhanuja-s+-assignee%3Arainbj+-assignee%3Aamzn-leenguy+-assignee%3Ayuyihsu&type=issues
• Tickets that are assigned to “sig/ui-ux” and needs triaged
  • Blocker/Critical bugs: https://github.com/o3de/o3de/issues?q=is%3Aopen+is%3Aissue+label%3Asig%2Fui-ux+label%3Akind%2Fbug+label%3Apriority%2Fcritical%2Cpriority%2Fblocker+-label%3Aneeds-ux-action%2Cstatus%2Fneeds-ux-approval%2Cui-ux%2Fin-design+
  • Pull requests: https://github.com/o3de/o3de/pulls?q=is%3Apr+is%3Aopen+label%3Asig%2Fui-ux+-label%3Astatus%2Fneeds-ux-approval%2Cneeds-ux-action%2Cstatus%2Fux-approved
  • Bugs without priority: https://github.com/o3de/o3de/issues?q=is%3Aopen+is%3Aissue+label%3Asig%2Fui-ux+label%3Akind%2Fbug+-label%3Apriority%2Fcritical%2Cpriority%2Fblocker%2Cpriority%2Fmajor%2Cpriority%2Fminor+-label%3Aneeds-ux-action%2Cstatus%2Fneeds-ux-approval%2Cui-ux%2Fin-design+
  • Major bugs: https://github.com/o3de/o3de/issues?q=is%3Aopen+is%3Aissue+label%3Asig%2Fui-ux+label%3Akind%2Fbug+label%3Apriority%2Fmajor+-label%3Aneeds-ux-action%2Cstatus%2Fneeds-ux-approval%2Cui-ux%2Fin-design+
  • Minor bugs: https://github.com/o3de/o3de/issues?q=is%3Aopen+is%3Aissue+label%3Asig%2Fui-ux+label%3Akind%2Fbug+label%3Apriority%2Fminor+-label%3Aneeds-ux-action%2Cstatus%2Fneeds-ux-approval%2Cui-ux%2Fin-design+
• Tickets that are assigned to “sig/ui-ux” and have been triaged
  • Needs-ux-action: https://github.com/o3de/o3de/issues?q=is%3Aopen+is%3Aissue+label%3Aneeds-ux-action
  • Ui-ux/in-design: https://github.com/o3de/o3de/issues?q=is%3Aopen+is%3Aissue+label%3Aui-ux%2Fin-design
• Tickets that need UX approval:
  • https://github.com/o3de/o3de/issues?q=is%3Aopen+is%3Aissue+label%3Astatus%2Fneeds-ux-approval

Tags

• During this triage session this representative needs to make a few calls. Does the ticket we are looking at have a UX workflow that will affect the user’s visual understanding of O3DE in any way. If it does, one or more of the following tags should be applied. An additional tag beside Sig/ui-ux should be added to every ticket we process during triage.
  • Sig/ui-ux: This indicates there is some unspecified amount of work needed to be review by the UX team. This tag doesn’t give any specific details about complexity, approval needs or any specificity about time. This is a mere indicator that UX involvement is needed to some degree. This tag should only be removed by someone representing our UX group.
  • needs-ux-info: This tag is to be used when a ticket requires more information from a developer or the ticket creator to be able to make a call on what our next steps should be. At this point the UX representative is unable to determine next steps.
  • needs-ux-action: We would add this tag in addition to the previous tags. So, someone has identified that this ticket cannot proceed without action being taken from the UX team. This will need a specific UX owner. Time for assigning owners will be allotted in the Sig-UI-UX triage session for this. However, owners can be added by anyone. This tag should only be removed by someone representing our UX group.
  • status/needs-ux-approval: This tag will be added to a ticket where there is some unspecified amount of changes that impact the workflow and or UI and it requires UX eyes before it can be delivered to production. This tag doesn’t mean UX is required to deliver mock or graphics for this ticket. However, it does require a UX person to give a sign off on the ticket that it doesn’t conflict with any known design patterns, upcoming work, or breaks any foundational patterns we have already established. This tag should only be removed by someone representing our UX group.
  • ui-ux/in-design: After a ticket has been assigned to a designer. The ticket should be marked ui-ux/in-design“ indicating this ticket is active and In progress by a design resource. This tag would be removed if the task is resolved or if the ticket is being moved out of the UX workstream. This ticket tag can be added and removed as many times as needed.
  • status/ux-approved: This tag is added to ticket who have UX final sign off for a ticket. This should not be added to a ticket until all UX actions are completed including, design, research, feedback. This ticket does not mean sign off is good from PM or SDM. This means from the UX point of view all task related to UX have hit the quality and clarity bar that we are ok with proceeding with this solution. This tag should only be added by the UX designer who owns this work. When marking approved on a ticket the user should also re-assign the ticket back to the developer or SDM who owns the workstream (if one is not already included).
• Sometime it will be obvious and we can assign a feature label if known.
• if it needs UX action we need to go through the list a second time and assign specific owners to items that need action. If no UX owner this mean the item is pending triage ownership.
• If UX reviews a ticket and determine that ux is not needed we will remove our tag but also add a comment specifying please follow ux patterns, ok to proceed without ux.
• When processing UX tickets either in Sig-UX-UI or Sig-Release meeting please keep in mind the following use cases that don’t get resolved by a tag.

How would development and UX share a single ticket?

From an ownership perspective GitHub allows for more than one owner of a ticket. This means the ticket that have UX should have two assigned contributors. UX owners will not remove development resources. We will try to keep most details in the ticket comments. However, some documentation might be linked outside GitHub Including Figma designs or Qualtrics research data.

Which team should own this ticket: Development or UX?

UX can be assigned as a co-owner from a team perspective. No single threaded ownership is required anymore. You can assign two teams.

How is a ticket marked as “rejected” or “please fix“ if it’s just UX rejected?

If a ticket is rejected or asked for additional updates, we will change the status of the ticket to match its current state regardless of split deliverables. This means a ticket can be set as rejected with qualifiers but still be good from a code point of view. We imagine this might change as we learn more.

When should we be removing any of the labels?

The primary time when we can remove label is when the ticket is marked “Status/ux-approved”. At that point you can remove “need-ux-action” and “ui-ux/in design”

During our bi-weekly Sig-ui-ux charter meeting we will do the following actions:

• Review all the tickets labeled Sig/ui-ux ** that have not already been processed. (Open tickets only)
• Review any tickets we have recently closed that would be useful for the group to understand any major changes to the workflow.
• Identify any new patterns / icons that need to be added to our library or BlueJay design system documentation.
• Help unblock designers if they need clarification on next step or resources to reach out to.
• Add team and specific UX owners to the tickets for processing.
• Assign which UX contact should be looked at the ticket (if one is known).
• Try to categorize the tickets into different buckets during triage. Completed, in-progress, not started, and backlog / rejected.

What's our plan for more community contribution?

• We have externalized all of our major design related activities so that the public can attend. This includes ticket triage, UX design review, Rev the engine updates, Blue Jay Design system reviews, and open office hours.
• The Sig-ui-ux team holds two standing meetings. This meeting meets every Wednesday but alternates discussion points based on week.
• These meetings are communicated on the O3DE calendar, O3DE UX mailing list, GitHub issues (mtg-agenda), and on discord before every meeting.
• For these meeting we will look for creative ideas of topic name to peak user interest (Example from JT: UX smacking. Test-drive Tuesday, etc.)
• Get the community involved in the conversation (if possible).
• Lurkers can often be our next best customer. So help them feel included but don’t be forceful with the conversations or topic. Let them lurk and join the conversation when ready.
• Don’t ghost the community.
• Make sure after a decision has been made in the public that you don’t forget to relay the outcome to the group.
• Do our best to answer question posted in the group as soon as possible. A lack of response can chase people away.
• We will help prioritize use case or problems effecting the expert. Then secondarily hobbyist and influencers.
• Expert discussions: as we are working on specific topics of conversation, we plan on reaching out to different members of different game teams directly to give different demos or test a specific workflow. In these situations we might provide gift cards as a thank you for your time and energy. More details about the specific contribution will be made available as we have them.

How do we make sure that community contribution is rewarded?

• First and foremost. Not all good ideas come from just us. So, we want to make sure we acknowledge the people who contribute good ideas. This is either in conversation amongst the group or writing shared amongst Sig-ui-UX group. Please note that this Sig-ui-ux group doesn’t have the power to make announcement on behalf of O3DE, but related to UX when we are given the floor, we intend to recognize your contribution.
• Individual contributors have the option of earning different status among the UX team including Git privileges.
• An assigned UX designer on a ticket will note on that ticket any external contributions which helped. Based on the number of tickets this individual has been helpful in accomplishing he will be assigned a badge level. Badge level will indicate your status.
  • Beginner-level - 0 to 5 tickets (5 tickets)
  • Green-level - 6 to 16 tickets (10 tickets)
  • Mid-Level - 17 - 32 tickets (15 tickets)
  • Advanced-level - 33 to 53 tickets (20 tickets)
  • Staff - 54 and above

Other ideas to raise customer engagement: (Thanks JT for your contribution)

• As a system we should work in close collaboration with 3rd party tools. These contributors will bring with them a ton of their own developers and users. So, supporting the smaller ecosystem will help make community contribution higher.
• When working on issues, try not refer to a “unspecific task name/number” instead refer to the customer problem we are looking at when announcing topics of conversation for meetings. This will attract people to very specific conversations that interest them.
• Consider using some kind of voting system to allow people to participate who might not have the time to be vocal in their contributions.
• Use a system called “Graphic-all” which allows user to download experimental builds with maybe two alternative UX workflows. People become invested in seeing their option do well.
• Pay attention to YouTube comments specific to UX and follow up with individuals that have something to say but maybe are not active contributors.
• Beware and have strict rules around people who want to get leadership abilities by paying for their badge system. The badges should be earned not paid for.
• Help promote learning tutorial videos and ask to be a contributor and or ask them to promote Sig-ux-ui group.
• Go into all the social media and engage in the conversation on these other platforms.

Please fill any info related to the below for the 11/30 release notes: Note this has a due date of Friday Nov 12th, 2021

• Features

  • Onboarding experience (covered in sig-content)

    • Remote gems
    • bug fixes in project manager

  • Gameplay development experience

    • Improve prefabs editing in the viewport with the prefab editing focus mode (covered in sig-content)
    • Improve the searching experience in asset browser, users can now see the search results shown in a flat view without the folder structure, it makes it easier for users to find the files they are searching for faster (not covered in sig-content)
    • PhysX Joint related components adopt the new component editing mode in the viewport. Now users can edit the PhysX joints directly in the viewport using the manipulators. (covered in the sig-core)

  • Look development experience

    • Improved the speed of iteration between Maya/Blender and O3DE with the hot reload feature (covered in sig-graphics-audio)

  • Team collaboration experience

    • We are still evaluating this. will update more later.

  • Editor extension experience

    • We introduced several things to improve the implementation efficiency for engine builders to extend O3DE with their own tools and workflows.
      • Sample gems to extend the UIs
      • Documentations to support users to extend the engine (should covered in sig-doc)

  • Packaging and deployment experience

    • User can now easily package their project and share with their friends for them to play (not covered in sig build)

• Bug fixes (GHI list if possible)

• Deprecations

• Known issues

UI-UX SIG Meeting — Today's content for - PENDING

Hi O3DE Community,
We want to invite you to our conversation about today's newest content, design specifications, and program update.

This weeks conversation: we'll deep dive with Pip @lmbr-pip into online Gems for O3DE. What are they, how do they work, and how do users create them. Gems are at the heart of O3DE, so being able to create your own functionality and share them with others is a powerful tool for extending the engine. Pip will give us some basic examples about how to get up and running and some of the cool new innovations, and different ways users are publishing their own Gems. Come join our conversations and ask your questions live!

In our previous meeting: We spoke about Game building with Prefab focus modes. Please keep an eye on this ticket in the future for a link to see the previous rebroadcast link

Schedule

• Date/Time: PENDING
• Location: Discord SIG-UI-UX Voice Room
• Host: Joshua Rainbolt @rainbj
• Note Taker UI/UX SIG Committee

Meeting Details

We want to invite you to our Sig UX UI expert interviews, global updates, Roadmap visibility, and design review. This meeting is bi-weekly and we will cover the following items:

• New and interesting topics that O3DE has hot of the press. Because these items are so new we are likely to find bugs and new feedback from the community. This is kind of the point. As we let you observe and talk to us we can make adjustments to the workflows before it goes out to the masses.
• RTE program updates and new details. Any new findings, results, or feedback.
• Check in with designer about problems they are facing regarding tickets and if any help is required.
• Feedback from any research previously done.
• Assign designers or UI-UX SIG members UX work.
• Conduct live research.
• Create any ticket or close tickets based on our conversation.

Past meetings, including a link to the agenda, recording, notes, and resources.

https://github.com/o3de/sig-ui-ux/issues?q=is%3Aissue+is%3Aclosed+todays+in%3Atitle

To sign up for a topic in the Today's topic Bi-weekly meeting.

• Please add a comment to this ticket with following information
  • Discord name.
  • Topic of conversation.
  • How much time you might need.
  • Any UX resource you have already been working with and if their attendance is required.
  • Any resource to help explain your issue.

How can I get UX help on an issue?

We generally use the alternative weeks open office hours meeting to have conversations like this. Please look for the next meeting here and include a request in the comments. As long as time is open, we will address your agenda right away. Please give us 24 hours notice before the meeting to have a UX expert in that area join the meeting.
https://github.com/o3de/sig-ui-ux/issues?q=is%3Aissue+is%3Aopen+Office+in%3Atitle+

How can I Help?

• Great question. If you have a speciality such as research, design, or a unique understanding of game development. Let us know so we can help facilitate conversation on how best to contribute.
• Offer to be a note taker. We always need some help here. Facilitating a meeting and being a note taker can be tough, so any one willing to help will be appreciated.
• Offer to be a person willing to help put together agenda items and or review agenda items from previous meetings.

What should I bring to the bi-weekly meeting?

• Nothing, unless your a presenter, your attendance and great conversation is enough

Cut-off time / cancellation

• For the UI/UX bi-weekly meeting the UI-UX SIG team will check the GitHub Agenda item ticket 24 hours before the scheduled meeting, if no one signs up in the session, we will lock down the agenda for that day.
• If you are unable to attend after signing up, please just reach out in discord or on the ticket to let us know about the change.

Summary:

Unify the viewport interaction model and experience to optimize the consistency and learnability

What is the relevance of this feature?

Why is this important? What are the use cases? What will it do once completed?

Feature design description:

• Scope

• Improve the component editing mode with cluster UI and switcher
• Grid System / Snapping / Alignment
• Unify across tools/editors, editor, material editor, LyShine, etc
• Brush system

• User benefits:

• Context based communication for users providing visual guidance on what operations can be used and when.
• Context based input boxes provide immediate and precise input adjustments as needed
• Hotkeys are bound per button instead of per feature and easily re-used for different tools.

Technical design description:

• Explain the technical portion of the work in enough detail that members can implement the feature.

• Explain any API or process changes required to implement this feature

• This section should relate to the feature design description by reference and explain in greater detail how it makes the feature design examples work.

• This should also provide detailed information on compatibility with different hardware platforms.

What are the advantages of the feature?

• Explain the advantages for someone to use this feature

What are the disadvantages of the feature?

• Explain any disadvantages for someone to use this feature

How will this be implemented or integrated into the O3DE environment?

• Explain how a developer will integrate this into the codebase of O3DE and provide any specific library or technical stack requirements.

Are there any alternatives to this feature?

• Provide any other designs that have been considered. Explain what the impact might be of not doing this.
• If there is any prior art or approaches with other frameworks in the same domain, explain how they may have solved this problem or implemented this feature.

How will users learn this feature?

• Detail how it can be best presented and how it is used as an extension or a standalone tool used with O3DE.
• Explain if and how it may change how individuals would use the platform and if any documentation must be changed or reorganized.
• Explain how it would be taught to new and existing O3DE users.

Are there any open questions?

• What are some of the open questions and potential scenarios that should be considered?

SIG-UI-UX Office Hours for XX-XX-XXXX

Hi O3DE Community,
We want to invite you to our UX UI design review and office hours.

• Date/Time: XX/XX/XXXX @ 10:00am PT
• Location: Discord SIG-UI-UX Voice Room
• Moderator: UI/UX SIG Committee
• Note Taker UI/UX SIG Committee

The SIG-UI-UX Meetings repo contains the history past calls, including a link to the agenda, recording, notes, and resources.

To sign up the Office Hours.
Please add a comment to this ticket with following information:

• Discord username:
• Topic of conversation:
• How much time you might need:
• Any UX resource you have already been working with and if their attendance is required.

This is a bi-weekly meeting will cover the following items.

• UI-UX SIG team will show some of the O3DE workflows that are currently in-progress.
• UI-UX SIG will provide feedback to other UX designers about their O3DE designs.
• UI-UX SIG will provide feedback to the community about O3DE work they are working on.
• Will have open conversations about UX/UI related problems coming down the pipeline.
• Discuss UX tickets

Schedule

• The Sig UX-UI meeting (Triage and UX updates) will be on every other Wednesday at 10-11pm PST
• The design review/Office hours will be on the opposite weeks.
• This means every Wednesday we have something fun for UX going on.

How do I sign up get feedback?

• You can sign up by going to https://github.com/o3de/sig-ui-ux/issues
• Find the specific event you are interested in attending and getting feedback on.
  • In the comment section of that ticket place the details you would like to talk about.
  • Please include your name and/or Discord Name
  • The area of topic you would like to cover
  • The amount of time you might need to review this topic
  • Any individuals you have been already working
  • Any specific people you would like to attend this session for help.

How can I use office hours:

• Request a "sign-off" on your project from the UI-UX SIG.
• Usability/UX review of your designs/mock-ups.
• Discuss certain customer pain points or UX related topics.
• Brainstorm ideas or solutions to a user problem or feature.
• Submit user research or UX design requests.
  What should I bring to the office hour:
• Nothing is required but the following items would be helpful
  • A brief project overview or documentation, This should include the following
  • A simple user problem statement. As a user I want to solve this problem...
  • Who is your audience? Who are the users/user groups affected by the change?
  • What is your vision behind this change or update?
  • What is your UX issue related to: user interface, usability testing, learnability, documentation etc?
  • Materials/Workflows of the existing product. Sketches or wire-frames of ideas. PR/FAQ are also help.

Cut-off time / cancellation

• The UI-UX SIG Office Hours is sign-up based. We will check the topics 24 hours before the scheduled office hour, if no one signs up in the session, we will lock down the agenda of that day.
• If you are unable to attend after signing up, Please just reach out in discord or on the ticket to let us know about the change.

Meeting Details

Hi O3DE Community,
We want to invite you to our UX design review and office hours.

• Date/Time: 11/17/2021 @ 11:00am PT
• Location: Discord SIG-UI-UX Voice Room
• Moderator: UI/UX SIG Committee
• Note Taker UI/UX SIG Committee

The SIG-UI-UX Meetings repo contains the history past calls, including a link to the agenda, recording, notes, and resources.

To sign up the Office Hours.
Please add a comment to this ticket with following information:

• Discord username:
• Topic of conversation:
• How much time you might need:
• Any UX resource you have already been working with and if their attendance is required.

This is a bi-weekly meeting will cover the following items.

• UI-UX SIG team will show some of the O3DE workflows that are currently in-progress.
• UI-UX SIG will provide feedback to other UX designers about their O3DE designs.
• UI-UX SIG will provide feedback to the community about O3DE work they are working on.
• Will have open conversations about UX/UI related problems coming down the pipeline.
• Discuss UX tickets

Schedule

• The Sig UX-UI meeting (Triage and UX updates) will be on every other Wednesday at 10-11pm PST
• The design review/Office hours will be on the opposite weeks.
• This means every Wednesday we have something fun for UX going on.

How do I sign up get feedback?

• You can sign up by going to https://github.com/o3de/sig-ui-ux/issues
• Find the specific event you are interested in attending and getting feedback on.
  • In the comment section of that ticket place the details you would like to talk about.
  • Please include your name and/or Discord Name
  • The area of topic you would like to cover
  • The amount of time you might need to review this topic
  • Any individuals you have been already working
  • Any specific people you would like to attend this session for help.

How can I use office hours:

• Request a "sign-off" on your project from the UI-UX SIG.
• Usability/UX review of your designs/mock-ups.
• Discuss certain customer pain points or UX related topics.
• Brainstorm ideas or solutions to a user problem or feature.
• Submit user research or UX design requests.
  What should I bring to the office hour:
• Nothing is required but the following items would be helpful
  • A brief project overview or documentation, This should include the following
  • A simple user problem statement. As a user I want to solve this problem...
  • Who is your audience? Who are the users/user groups affected by the change?
  • What is your vision behind this change or update?
  • What is your UX issue related to: user interface, usability testing, learnability, documentation etc?
  • Materials/Workflows of the existing product. Sketches or wire-frames of ideas. PR/FAQ are also help.

Cut-off time / cancellation

• The UI-UX SIG Office Hours is sign-up based. We will check the topics 24 hours before the scheduled office hour, if no one signs up in the session, we will lock down the agenda of that day.
• If you are unable to attend after signing up, Please just reach out in discord or on the ticket to let us know about the change.

Meeting Details

• Date/Time: 12/01/2021 @ 10:00am PT
• Location: Discord SIG-UI-UX Voice Room
• Moderator: UI/UX SIG Committee
• Note Taker UI/UX SIG Committee

This meeting is for the SIG UI-UX Office Hours. For details of the office hours, please visit here.

To sign up the Office Hours, please the comments below with following information:

• Topic
• Type: [request approval/request review/brainstorm ideas/submit research or design request/others]
• Background or links to the related docs
• Possible length of discussion: 30 mins or 1 hour

Meeting Details

• Date/Time: 09/15/2021 @ 11:00am PT
• Location: Discord SIG-UI-UX Voice Room
• Moderator: UI/UX SIG Committee
• Note Taker UI/UX SIG Committee

This meeting is for the SIG UI-UX Office Hours. For details of the office hours, please visit here.

To sign up the Office Hours, please the comments below with following information:

• Topic
• Type: [request approval/request review/brainstorm ideas/submit research or design request/others]
• Background or links to the related docs
• Possible length of discussion: 30 mins or 1 hour

UI-UX SIG Meeting — todays content for 04-13-2022

Hi O3DE Community,
We want to invite you to our conversation about today's newest content, design specifications, and program update.

This weeks conversation:
We have some time off from our normal conversation. Today we will review program updates from the Rev the engine program. Updates regarding UX team status and outstanding projects being worked on

In our previous meeting:
We finished out Multiplayer Game setup guide that can now be found on YouTube.

https://www.youtube.com/watch?v=pY4DDsIBOJY&list=LLw4ld6P3z0uovKZbgR0wQbg
https://www.youtube.com/watch?v=EYP8ejNCMCw

Schedule

• Date/Time: 04/13/2022 @ 10:00am Pacific Time (PT)
• Location: Discord SIG-UI-UX Voice Room
• Moderator: UI/UX SIG Committee
• Note Taker UI/UX SIG Committee

Meeting Details

We want to invite you to our Sig UX UI expert interviews, global updates, Roadmap visibility, and design review. This meeting is bi-weekly and we will cover the following items:

• New and interesting topics that O3DE has hot of the press. Because these items are so new we are likely to find bugs and new feedback from the community. This is kind of the point. As we let you observe and talk to us we can make adjustments to the workflows before it goes out to the masses.
• RTE program updates and new details. Any new findings, results, or feedback.
• Check in with designer about problems they are facing regarding tickets and if any help is required.
• Feedback from any research previously done.
• Assign designers or UI-UX SIG members UX work.
• Conduct live research.
• Create any ticket or close tickets based on our conversation.

Past meetings, including a link to the agenda, recording, notes, and resources.

https://github.com/o3de/sig-ui-ux/issues?q=is%3Aissue+is%3Aclosed+todays+in%3Atitle

To sign up for a topic in the Todays topic Bi-weekly meeting.

• Please add a comment to this ticket with following information
  • Discord name.
  • Topic of conversation.
  • How much time you might need.
  • Any UX resource you have already been working with and if their attendance is required.
  • Any resource to help explain your issue.

How can I get UX help on an issue?

We generally use the alternative weeks open office hours meeting to have conversations like this. Please look for the next meeting here and include a request in the comments. As long as time is open we will address your agenda right away. Please give us 24 hours notice before the meeting to have a UX expert in that area join the meeting.
https://github.com/o3de/sig-ui-ux/issues?q=is%3Aissue+is%3Aopen+Office+in%3Atitle+

How can I Help?

• Great question. If you have speciality such as research, design, or a unique understanding of game development. Let us know so we can help facilitate conversation on how best to contribute.
• Offer to be a note taker. We always need some help here. Facilitating a meeting and being a note taker can be tough, so any one willing to help will be appreciated.
• Offer to be a person willing to help put together agenda items and or review agenda items from previous meetings.

What should I bring to the bi-weekly meeting?

• Nothing, unless your a presenter, your attenance and great conversation is enough

Cut-off time / cancellation

• For the UI/UX bi-weekly meeting the UI-UX SIG team will check the GitHub Agenda item ticket 24 hours before the scheduled meeting, if no one signs up in the session, we will lock down the agenda of that day.
• If you are unable to attend after signing up, Please just reach out in discord or on the ticket to let us know about the change.

Meeting Details

• Date/Time: 08/25/2021 @ 11:00am PT
• Location: Discord SIG-UI-UX Voice Room
• Moderator: UI/UX SIG Committee
• Note Taker UI/UX SIG Committee

This meeting is for the SIG UI-UX Office Hours. For details of the office hours, please visit here.

To sign up the Office Hours, please the comments below with following information:

• Topic
• Type: [request approval/request review/brainstorm ideas/submit research or design request/others]
• Background or links to the related docs
• Possible length of discussion: 30 mins or 1 hour

Meeting Details

• Date/Time: 10/19, 2021 @ 11:00am PST
• Location: Discord SIG-UI-UX Voice Room

Meeting agenda:

We will be going through the UI-UX SIG issues on GitHub (https://github.com/o3de/o3de/issues?q=is%3Aopen+is%3Aissue+label%3Asig%2Fui-ux), and assign the tickets to the right owner and status.

UI-UX SIG Meeting — todays content for 05-12-2022

Hi O3DE Community,
We want to invite you to our conversation about today's newest content, design specifications, and program update.

This weeks conversation:

In our previous meeting:

Schedule

• Date/Time: 05-12-2022 @ 10:00am Pacific Time (PT)
• Location: Discord SIG-UI-UX Voice Room
• Moderator: UI/UX SIG Committee
• Note Taker UI/UX SIG Committee

Meeting Details

We want to invite you to our Sig UX UI expert interviews, global updates, Roadmap visibility, and design review. This meeting is bi-weekly and we will cover the following items:

• RTE program updates and new details. Any new findings, results, or feedback.
• Check in with designer about problems they are facing regarding tickets and if any help is required.
• Feedback from any research previously done.
• Assign designers or UI-UX SIG members UX work.
• Conduct live research.
• Create any ticket or close tickets based on our conversation.

Past meetings, including a link to the agenda, recording, notes, and resources.

https://github.com/o3de/sig-ui-ux/issues?q=is%3Aissue+is%3Aclosed+todays+in%3Atitle

To sign up for a topic in the Todays topic Bi-weekly meeting.

• Please add a comment to this ticket with following information
  • Discord name.
  • Topic of conversation.
  • How much time you might need.
  • Any UX resource you have already been working with and if their attendance is required.
  • Any resource to help explain your issue.

How can I get UX help on an issue?

We generally use the alternative weeks open office hours meeting to have conversations like this. Please look for the next meeting here and include a request in the comments. As long as time is open we will address your agenda right away. Please give us 24 hours notice before the meeting to have a UX expert in that area join the meeting.
https://github.com/o3de/sig-ui-ux/issues?q=is%3Aissue+is%3Aopen+Office+in%3Atitle+

How can I Help?

• Great question. If you have specialty such as research, design, or a unique understanding of game development. Let us know so we can help facilitate conversation on how best to contribute.
• Offer to be a note taker. We always need some help here. Facilitating a meeting and being a note taker can be tough, so any one willing to help will be appreciated.
• Offer to be a person willing to help put together agenda items and or review agenda items from previous meetings.

What should I bring to the bi-weekly meeting?

• Nothing, unless your a presenter, your attendance and great conversation is enough

Cut-off time / cancellation

• For the UI/UX bi-weekly meeting the UI-UX SIG team will check the GitHub Agenda item ticket 24 hours before the scheduled meeting, if no one signs up in the session, we will lock down the agenda of that day.
• If you are unable to attend after signing up, Please just reach out in discord or on the ticket to let us know about the change.

Meeting Details

• Date/Time: Aug 19th, 2021 @ 18:00pm UTC / 2:00pm ET / 11:00am PT
• Location: Discord SIG-UI-UX Voice Room
• Moderator: Josh / Liv / Yuyi
• Note Taker Josh / Yuyi / Liv

Overview

Hi Sig-UX-UI O3DE community,
It's time for our Sig UX meeting. It will take place via Discord in our SIG voice channel. Please double click on the attached meeting invite to add it to your calendar. It will be Aug 19th.

Here's our current agenda items for his meeting:

• UI/UX review processes- We are going to talk about the processes to maintain a consistent and high-quality user experience in O3DE by collaborating with the community.
• Rev the Engine program- We will share how we want to use the Rev the Engine program to continue engaging the community to improve the user experience in O3DE with us.
• UX roadmap- We will review the high-level items in the UX roadmap.

For more details of the meeting agenda, you can view it here: If you’d like to propose additional topics, please leave comments in the GitHub thread for this meeting’s agenda. We’ll make adjustments to the agenda items. With the increase number of individuals joining the O3DE community we will leave time in the beginning to allow for any new individuals to introduce themselves (if you would like to say hi). Looking forward to connecting with you all!

Meeting History

The SIG-UI-UX Meetings repo contains the history past calls, including a link to the agenda, recording, notes, and resources. Please see specified folders. These folder structures may be rearranged in the next couple weeks.

In our last meeting we

• Did introductions and topic reviews.
• We got updates from Rev the engine and where that program is at.
• UX Roadmap.
• We spoke about process the Gem submission process.
• We got an introduction to BlueJay design system.
• We talked about the ticket approval process and out thoughts about how we should handle this process.

Meeting Agenda

(@rainbj)

• Ticket migration to get everything into Git
• Take a look at our ticket backlog and get some ideas on how we should handle this process
• Talk about tags, prioritization, and how we should review the tickets?

(@forhalle)

• Give an update about the current triage process and how UX will work within this.

(@yuyihsu)

• Update the community about where we are at with Rev the engine.
• Review major roadmap items. What is UX working on.

Meeting Details

• Date/Time: 07 22, 2021 @ XX:XXpm UTC / XX:XXpm ET
• Location: Discord SIG-UI-UX Voice Room
• Moderator: TBA
• Note Taker Person

The SIG-UI-UX Meetings repo contains the history past calls, including a link to the agenda, recording, notes, and resources.

SIG Updates

What happened since the last meeting?

Meeting Agenda

Discuss agenda from proposed topics

Outcomes from Discussion topics

Discuss outcomes from agenda

Action Items

Create actionable items from proposed topics

Open Discussion Items

List any additional items below!

UI-UX SIG Meeting — todays content for 02-16-2022

Hi O3DE Community,
We want to invite you to our meeting program feedback, RTE updates, triage, and design specific conversations.

The purpose of this conversation is to have Suzanne Leibrick review the game Genre document with the Sig UX team and community to understand where our heads are at about direction of customers what this all means. We need to understand this first to really understand the type of customer we really want to appeal to for the next major release. This will help define some of our main customers pain points we will be tackling in the next several month

Schedule

• Date/Time: 02/16/2022 @ 10:00am PT
• Location: Discord SIG-UI-UX Voice Room
• Moderator: UI/UX SIG Committee
• Note Taker UI/UX SIG Committee

Additional details we may cover

•RTE program updates and new details. Any new findings, results, or feedback.
• Check in with designer about problems they are facing regarding tickets and if any help is required
• Feedback from any research previously done regarding tickets.
• Assign designers or UI-UX SIG members UX work. This includes deadlines and expectations of work completed.
• In some cases a show and tell may be required to talk through a pending issue or new feature. However we we’ll try to hold these for design critiques for every other Wednesday.
• Request for research and or conduct live research.
• Close out tickets if completed.

The SIG-UI-UX Meetings repo contains the history past calls, including a link to the agenda, recording, notes, and resources.

To sign up for a topic in the SIG-UI-UX Bi-weekly meeting.

• Please add a comment to this ticket with following information:
• Discord name:
• Topic of conversation:
• How much time you might need:
• Any UX resource you have already been working with and if their attendance is required.
• ** Any resource to help explain your issue **

How can I use the Bi-weekly meeting?

• Please add any specific agenda items you would like to talk about to the ticket.
• We will address any agenda items first. These items should be related to outstanding tickets.
• This meeting is not about creating new tickets but reviewing and fixing outstanding tickets.
• If you have speciality such as research, design, or a unique understanding of game development. Let us know so we can help facilitate where we can use your help the most.
• Offer to be a note taker. We always need some help here. Facilitating a meeting and being a note taker can be tough, so any one willing to help will be appreciated.
• Offer to be a person willing to help put together agenda items and or review agenda items from previous meetings.

What should I bring to the bi-weekly meeting?

• Nothing is required but the following items would be helpful
o A list of ticket you are interested in addressing
o An update on tickets you have been working on
o Some prepared questions about the tickets you own

Cut-off time / cancellation

• For the UI/UX bi-weekly meeting the UI-UX SIG team will check the GitHub Agenda item ticket 24 hours before the scheduled meeting, if no one signs up in the session, we will lock down the agenda of that day.
• If you are unable to attend after signing up, Please just reach out in discord or on the ticket to let us know about the change.

SIG-UI-UX Office Hours for 02-09-2022

Hi O3DE Community,
We want to invite you to our UX UI design review and office hours.

• Date/Time: 02-09-2022 @ 10:00am PT
• Location: Discord SIG-UI-UX Voice Room
• Moderator: UI/UX SIG Committee
• Note Taker UI/UX SIG Committee

The SIG-UI-UX Meetings repo contains the history past calls, including a link to the agenda, recording, notes, and resources.

To sign up the Office Hours.
Please add a comment to this ticket with following information:

• Discord username:
• Topic of conversation:
• How much time you might need:
• Any UX resource you have already been working with and if their attendance is required.

This is a bi-weekly meeting will cover the following items.

• UI-UX SIG team will show some of the O3DE workflows that are currently in-progress.
• UI-UX SIG will provide feedback to other UX designers about their O3DE designs.
• UI-UX SIG will provide feedback to the community about O3DE work they are working on.
• Will have open conversations about UX/UI related problems coming down the pipeline.
• Discuss UX tickets

Schedule

• The Sig UX-UI meeting (Triage and UX updates) will be on every other Wednesday at 10-11pm PST
• The design review/Office hours will be on the opposite weeks.
• This means every Wednesday we have something fun for UX going on.

How do I sign up get feedback?

• You can sign up by going to https://github.com/o3de/sig-ui-ux/issues
• Find the specific event you are interested in attending and getting feedback on.
  • In the comment section of that ticket place the details you would like to talk about.
  • Please include your name and/or Discord Name
  • The area of topic you would like to cover
  • The amount of time you might need to review this topic
  • Any individuals you have been already working
  • Any specific people you would like to attend this session for help.

How can I use office hours:

• Request a "sign-off" on your project from the UI-UX SIG.
• Usability/UX review of your designs/mock-ups.
• Discuss certain customer pain points or UX related topics.
• Brainstorm ideas or solutions to a user problem or feature.
• Submit user research or UX design requests.
  What should I bring to the office hour:
• Nothing is required but the following items would be helpful
  • A brief project overview or documentation, This should include the following
  • A simple user problem statement. As a user I want to solve this problem...
  • Who is your audience? Who are the users/user groups affected by the change?
  • What is your vision behind this change or update?
  • What is your UX issue related to: user interface, usability testing, learnability, documentation etc?
  • Materials/Workflows of the existing product. Sketches or wire-frames of ideas. PR/FAQ are also help.

Cut-off time / cancellation

• The UI-UX SIG Office Hours is sign-up based. We will check the topics 24 hours before the scheduled office hour, if no one signs up in the session, we will lock down the agenda of that day.
• If you are unable to attend after signing up, Please just reach out in discord or on the ticket to let us know about the change.

Meeting Details

• Date/Time: July 29th, 2021 @ 18:00pm UTC / 2:00pm ET / 11:00am PT
• Location: Discord SIG-UI-UX Voice Room
• Moderator: Josh / Liv
• Note Taker Josh / Liv

##Email for Meeting
Hi Sig-UX-UI O3DE community,

It's time for our 2nd Sig meeting. It will take place via Discord in our SIG voice channel. Please double click on the attached meeting invite to add it to your calendar. It will be July 29th at 11am PST.

Many of you might have setup O3DE and started building something in the engine. We'd love to hear from you what you think about the overall user experience (from set up the engine, create the project, to build content in the Editor) so far! Anything that we should consider improving in the upcoming release?

Here's our current agenda for the meeting-

• UI/UX review processes- We are going to talk about the processes to maintain a consistent and high-quality user experience in O3DE by collaborating with the community.
• Rev the Engine program- We will share how we want to use the Rev the Engine program to continue engaging the community to improve the user experience in O3DE with us.
• UX roadmap- We will review the high-level items in the UX roadmap.
• BlueJay Design System- We will talk about what is BlueJay design system and how do we plan to use it to drive a consistent user experience in O3DE.
• Other topics from the community- we've collected the following topics from the community
  • How should we handle the logic for icons being displayed in the viewport that represent an entity. Currently, it's not showing the most relevant component icon.
  • What telemetry data should we look for in the Editor that can help us improve the user experience?

For more details of the meeting agenda, you can view it here: #22 If you’d like to propose additional topics, please leave comments in the GitHub thread for this meeting’s agenda. We’ll make adjustments to the agenda items.

With the increase number of individuals joining the O3DE community we will leave time in the beginning to allow for any new individuals to introduce themselves (if you would like to say hi).

Looking forward to connecting with you all!

Thanks,

Josh

SIG Meeting History

The SIG-UI-UX Meetings repo contains the history past calls, including a link to the agenda, recording, notes, and resources. Please see specified folders. These folder structures may be rearranged in the next couple weeks.

SIG Updates

In our last meeting we did introductions and reviewed: Where does the sig documentation live, what is the current status of the UX work, what is our overall UX vision, and some of the existing programs we are trying to get up and running. Please see last weeks meeting notes in GitHub for more details.

After our last meeting we worked on pushing forward some of the next steps for O3DE including the BlueJay design system for O3DE, rev the engine, and some critical UX bugs for GA.

Meeting Agenda

(@rainbj )

• How do we prevent UX features that are submitted by the community from going out without UX review? Any ideas on how work on this process.
• We should give updates on this topic, plus what is going on with icons in general.
• We should talk about ticket approval process?
• We need to make some kind of on-call rotation for Sig. Find opportunity in other Sigs to help organize our UX sig.
• Talk about the bot that Yuyi's son is writing for us about tracking down conversations in other Sig's related to UX/UI. It should ping them letting them know there is another location they should involve too.

(@yuyihsu )

• Update the community about where we are at with Rev the engine.
• Can people from the community attend these meetings? How can we get help from our community with this project?
• Review major roadmap items. What is UX working on.

(@amzn-leenguy )

• Top level topic for the BlueJay design system. Where we are and next time.

(@bhanuja-s )

• Gem submission process. How users can collaborate and submit content to O3DE.

(discord threads to discuss)

• How should we handle the logic for icons being displayed in the viewport that represent an entity. Currently, it's not showing the most relevant component icon.
• What telemetry data should we look for in the Editor that can help us improve the user experience?

Summary:

Single paragraph explanation of the feature

What is the relevance of this feature?

Why is this important? What are the use cases? What will it do once completed?

Feature design description:

• Scope

• Unify the hotkeys across the editor
• Hotkey editor, nested/hierarchical (can even redefine mapping for various component modes)

• User benefits:

• User definable Hot keys for editor and tools
• Industry standardized controls as a default experience making it easier to switch from others game engines or DCC tools to LY.
• Ability to provide alternative pre-sets of controls and/or let users share via a configuration file.

• Engineering / Developer benefits:

• Consolidation of keybinding out of C++ and into data, allowing new tools and keys to be developed for modes with less overhead.
• Established binding pattern and when combined with modes makes it easier for new tools to follow a standard.

Technical design description:

• Explain the technical portion of the work in enough detail that members can implement the feature.

• Explain any API or process changes required to implement this feature

• This section should relate to the feature design description by reference and explain in greater detail how it makes the feature design examples work.

• This should also provide detailed information on compatibility with different hardware platforms.

What are the advantages of the feature?

• Explain the advantages for someone to use this feature

What are the disadvantages of the feature?

• Explain any disadvantages for someone to use this feature

How will this be implemented or integrated into the O3DE environment?

• Explain how a developer will integrate this into the codebase of O3DE and provide any specific library or technical stack requirements.

Are there any alternatives to this feature?

• Provide any other designs that have been considered. Explain what the impact might be of not doing this.
• If there is any prior art or approaches with other frameworks in the same domain, explain how they may have solved this problem or implemented this feature.

How will users learn this feature?

• Detail how it can be best presented and how it is used as an extension or a standalone tool used with O3DE.
• Explain if and how it may change how individuals would use the platform and if any documentation must be changed or reorganized.
• Explain how it would be taught to new and existing O3DE users.

Are there any open questions?

• What are some of the open questions and potential scenarios that should be considered?

What is the relevance of this feature?

To many new customers, there's a high barrier to entry when they first learn how to use O3DE to build their project. Many have expressed the need to learn from examples. With the new prefab system, we can build a template system that contains a variety of samples that come with the gems and users can drag and drop these samples to their game to prototype their idea quickly. With these sample templates, users can also learn how to use the functions easily.

Feature design description:

1. Template container(s)
2. Template workset(s) (collections)
3. Template workset palette (gui, collection as visual thmbnails)
4. Which systems, tools, workflows utilize Templates and Worksets?

Technical design description:

• Explain the technical portion of the work in enough detail that members can implement the feature.

• Explain any API or process changes required to implement this feature

• This section should relate to the feature design description by reference and explain in greater detail how it makes the feature design examples work.

• This should also provide detailed information on compatibility with different hardware platforms.

What are the advantages of the feature?

• Explain the advantages for someone to use this feature

What are the disadvantages of the feature?

• Explain any disadvantages for someone to use this feature

How will this be implemented or integrated into the O3DE environment?

• Explain how a developer will integrate this into the codebase of O3DE and provide any specific library or technical stack requirements.

Are there any alternatives to this feature?

• Provide any other designs that have been considered. Explain what the impact might be of not doing this.
• If there is any prior art or approaches with other frameworks in the same domain, explain how they may have solved this problem or implemented this feature.

How will users learn this feature?

• Detail how it can be best presented and how it is used as an extension or a standalone tool used with O3DE.
• Explain if and how it may change how individuals would use the platform and if any documentation must be changed or reorganized.
• Explain how it would be taught to new and existing O3DE users.

Are there any open questions?

• What are some of the open questions and potential scenarios that should be considered?

Meeting Details

• Date/Time: 10/7, 2021 @ 18:00pm UTC / 2:00pm ET / 11:00am PT
• Location: Discord SIG-UI-UX Voice Room
• Moderator: @rainbj
• Note Taker @amzn-leenguy

The SIG-UI-UX Meetings repo contains the history past calls, including a link to the agenda, recording, notes, and resources.

Meeting Agenda

Here's what we have so far, please propose any open discussion items that you'd like to cover in this meeting-

• Rev the Engine program update and collaboration with the O3DE Game Jam
• UI-UX issue management process review
• BlueJay Design System update
• Open discussion topics: TBD

Meeting Details

This meeting is for the SIG-UI-UX Bi-weekly meeting.

• Date/Time: 01/05/2022 @ 11:00am PT
• Location: Discord SIG-UI-UX Voice Room
• Moderator: UI/UX SIG Committee
• Note Taker UI/UX SIG Committee

The SIG-UI-UX Meetings repo contains the history past calls, including a link to the agenda, recording, notes, and resources.

To sign up for a topic in the SIG-UI-UX Bi-weekly meeting.

• Please add a comment to this ticket with following information:
  • Discord name:
  • Topic of conversation:
  • How much time you might need:
  • Any UX resource you have already been working with and if their attendance is required.
  • ** Any resource to help explain your issue **

What will we be covering?

• Ticket triage - We will go through our ticket backlog and do prioritization and sorting
• Review outstanding ticket assigned previously.
• Check in with designer about problems they are facing regarding tickets and if any help is required
• Feedback from any research previously done regarding tickets.
• Assign designers or UI-UX SIG members UX tickets. This includes deadlines and expectations of work completed.
• In some cases a show and tell may be required to talk through a pending issue or new feature. However we we’ll try to hold these for design critiques for every other Wednesday.
• We will review status of Rev the engine. Any new findings, results, or feedback.
• Close out tickets if completed.

How can I use the Bi-weekly meeting?

• Please add any specific agenda items you would like to talk about to the ticket.
• We will address any agenda items first. These items should be related to outstanding tickets.
• This meeting is not about creating new tickets but reviewing and fixing outstanding tickets.
• If you have speciality such as research, design, or a unique understanding of game development. Let us know so we can help facilitate where we can use your help the most.
• Offer to be a note taker. We always need some help here. Facilitating a meeting and being a note taker can be tough, so any one willing to help will be appreciated.
• Offer to be a person willing to help put together agenda items and or review agenda items from previous meetings.

What should I bring to the bi-weekly meeting?

• Nothing is required but the following items would be helpful
o A list of ticket you are interested in addressing
o An update on tickets you have been working on
o Some prepared questions about the tickets you own

Cut-off time / cancellation

• For the UI/UX bi-weekly meeting the UI-UX SIG team will check the GitHub Agenda item ticket 24 hours before the scheduled meeting, if no one signs up in the session, we will lock down the agenda of that day.
• If you are unable to attend after signing up, Please just reach out in discord or on the ticket to let us know about the change.

As a team working on O3DE rev the engine test, we have come across several inconsistent and incorrect error messaging and warning message throughout the editor.

These locations include Asset browser, console window, Asset Processor, IMGUI, etc

Fixing individual error messaging and warning message seems not like the best use of our time based on the number of issues we are seeing. This is because all error messaging and warning message text are stored inline and not centralized and thought about holistically. The AC for this project is as followed.

• We would like for all of the error messaging and warning message in the editor to be combined into a centralized location for easy update.
• This could be a TXT, XML, Excel or some kind of easily readable file(s). Developer needs to research best method.
• We should include some rules about how we should be speaking to the customer. This should be reflected as comments in the beginning of this new document so as developers add to the document they can read the rules before updating the text.
• Rules needing to be confirmed by docs. William Hayward and Doug Erickson please give your thoughts to help confirm standards to reflect most recent writing practices.
• Errors and warning messages should be clear and actionable
• We should include a consistent format about message
• Example [ warning: type of error: location : what can be done to fix it]
• We do not use camel case.
• We only capitalize proper names, example, "Script Canvas."
• First letter should always be capitalized.
• periods should be used.
• Text should be written in future tense. Not past tense.
• Text should reflect the language about next steps.
• Length of text – We can set a standard after we see the most complex text use case
• We should prepare this text to be localized into multiple languages.
• This means we should be careful about terminology that could be misunderstood in different languages.
• This task will also include pulling out all the error /warning text throughout the editor and replace it with some kind of common global variable.
• We will also need docs to do a pass on all the error /warning once it has been centralized into a file(s).

UI-UX SIG Meeting — today's content for 01-19-2022

Hi O3DE Community,
We want to invite you to our meeting program feedback, RTE updates, triage, and design specific conversations. The purpose is to discuss the UX gap with the community and the team. Talk about the plan and what needs to change and create a direction for us to help best resolve these issues.

Schedule:

• Date/Time: 01-19-2022 @ 10:00am PT
• Location: Discord SIG-UI-UX Voice Room
• Moderator: UI/UX SIG Committee
• Note Taker UI/UX SIG Committee

Meeting Details:

We want to invite you to our Sig UX UI bi-weekly meeting*.* This is a bi-weekly meeting and we will cover the following items from the UX team.

Agenda items:

1. UI-UX SIG meeting format update
2. Update on the Rev the Engine Program.
3. Update on the BlueJay Design System roadmap.
4. Customer insight learning @finchy [Amazon, Finch Studio] will share their feedback on the material editing workflow.

Let us know if there's other topic you'd like to talk about in our meeting tomorrow by adding a comment to this ticket

Other items covered in this meeting.

• Ticket triage - We will go through our ticket backlog and do prioritization and sorting
• Review outstanding ticket assigned previously.
•RTE program updates and new details. Any new findings, results, or feedback.
• Check in with designer about problems they are facing regarding tickets and if any help is required
• Feedback from any research previously done regarding tickets.
• Assign designers or UI-UX SIG members UX work. This includes deadlines and expectations of work completed.
• In some cases a show and tell may be required to talk through a pending issue or new feature. However we we’ll try to hold these for design critiques for every other Wednesday.
• Request for research and or conduct live research.
• Close out tickets if completed.

The SIG-UI-UX Meetings repo contains the history past calls, including a link to the agenda, recording, notes, and resources.

To sign up for a topic in the SIG-UI-UX Bi-weekly meeting.

• Please add a comment to this ticket with following information:
• Discord name:
• Topic of conversation:
• How much time you might need:
• Any UX resource you have already been working with and if their attendance is required.
• ** Any resource to help explain your issue **

How can I use the Bi-weekly meeting?

• Please add any specific agenda items you would like to talk about to the ticket.
• We will address any agenda items first. These items should be related to outstanding tickets.
• This meeting is not about creating new tickets but reviewing and fixing outstanding tickets.
• If you have speciality such as research, design, or a unique understanding of game development. Let us know so we can help facilitate where we can use your help the most.
• Offer to be a note taker. We always need some help here. Facilitating a meeting and being a note taker can be tough, so any one willing to help will be appreciated.
• Offer to be a person willing to help put together agenda items and or review agenda items from previous meetings.

What should I bring to the bi-weekly meeting?

• Nothing is required but the following items would be helpful
o A list of ticket you are interested in addressing
o An update on tickets you have been working on
o Some prepared questions about the tickets you own

Cut-off time / cancellation

• For the UI/UX bi-weekly meeting the UI-UX SIG team will check the GitHub Agenda item ticket 24 hours before the scheduled meeting, if no one signs up in the session, we will lock down the agenda of that day.
• If you are unable to attend after signing up, Please just reach out in discord or on the ticket to let us know about the change.

UI-UX SIG Meeting - todays content for XX-XX-XXXX

Hi O3DE Community,
We want to invite you to our meeting program feedback, RTE updates, triage, and design specific conversations. The purpose is to discuss the UX gap with the community and the team. Talk about the plan and what needs to change and create a direction for us to help best resolve these issues.

Schedule

• Date/Time: XX/XX/XXXX @ 10:00am PT
• Location: Discord SIG-UI-UX Voice Room
• Moderator: UI/UX SIG Committee
• Note Taker UI/UX SIG Committee

Meeting Details

We want to invite you to our Sig UX UI bi-weekly meeting*.* This is a bi-weekly meeting and we will cover the following items from the UX team.

• Ticket triage - We will go through our ticket backlog and do prioritization and sorting
• Review outstanding ticket assigned previously.
•RTE program updates and new details. Any new findings, results, or feedback.
• Check in with designer about problems they are facing regarding tickets and if any help is required
• Feedback from any research previously done regarding tickets.
• Assign designers or UI-UX SIG members UX work. This includes deadlines and expectations of work completed.
• In some cases a show and tell may be required to talk through a pending issue or new feature. However we we’ll try to hold these for design critiques for every other Wednesday.
• Request for research and or conduct live research.
• Close out tickets if completed.

The SIG-UI-UX Meetings repo contains the history past calls, including a link to the agenda, recording, notes, and resources.

To sign up for a topic in the SIG-UI-UX Bi-weekly meeting.

• Please add a comment to this ticket with following information:
• Discord name:
• Topic of conversation:
• How much time you might need:
• Any UX resource you have already been working with and if their attendance is required.
• ** Any resource to help explain your issue **

How can I use the Bi-weekly meeting?

• Please add any specific agenda items you would like to talk about to the ticket.
• We will address any agenda items first. These items should be related to outstanding tickets.
• This meeting is not about creating new tickets but reviewing and fixing outstanding tickets.
• If you have speciality such as research, design, or a unique understanding of game development. Let us know so we can help facilitate where we can use your help the most.
• Offer to be a note taker. We always need some help here. Facilitating a meeting and being a note taker can be tough, so any one willing to help will be appreciated.
• Offer to be a person willing to help put together agenda items and or review agenda items from previous meetings.

What should I bring to the bi-weekly meeting?

• Nothing is required but the following items would be helpful
o A list of ticket you are interested in addressing
o An update on tickets you have been working on
o Some prepared questions about the tickets you own

Cut-off time / cancellation

• For the UI/UX bi-weekly meeting the UI-UX SIG team will check the GitHub Agenda item ticket 24 hours before the scheduled meeting, if no one signs up in the session, we will lock down the agenda of that day.
• If you are unable to attend after signing up, Please just reach out in discord or on the ticket to let us know about the change.

Meeting Details

• Date/Time: 08/18/2021 @ 11:00am PT
• Location: Discord SIG-UI-UX Voice Room
• Moderator: UI/UX SIG Committee
• Note Taker UI/UX SIG Committee

This meeting is for the SIG UI-UX Office Hours. For details of the office hours, please visit here.

To sign up the Office Hours, please the comments below with following information:

• Topic
• Type: [request approval/request review/brainstorm ideas/submit research or design request/others]
• Background or links to the related docs
• Possible length of discussion: 30 mins or 1 hour

SIG chair / co-chair elections for 2022

Since the inception of O3DE, each SIG chair has been staffed as an interim position. It's time to hold some official elections, following some of the proposed guidance but with our own process due to the holiday season and in order to expedite the elections into next year.

The chair / co-chair roles

The chair and co-chair serve equivalent roles in the governance of the SIG and are only differentiated by title in that the highest vote-getter is the chair and the second-highest is the co-chair. The chair and co-chair are expected to govern together in an effective way and split their responsibilities to make sure that the SIG operates smoothly and has the availability of a chairperson at any time.

Unless distinctly required, the term "chairperson" refers to either/both of the chair and co-chair. If a chair or co-chair is required to perform a specific responsibility for the SIG they will always be addressed by their official role title.

In particular, if both chairpersons would be unavailable during a period of time, the chair is considered to be an on-call position during this period. As the higher vote-getter they theoretically represent more of the community and should perform in that capacity under extenuating circumstances. This means that if there is an emergency requiring immediate action from the SIG, the chair will be called to perform a responsibility.

Responsibilities

• Schedule and proctor regular SIG meetings on a cadence to be determined by the SIG.
• Serve as a source of authority (and ideally wisdom) with regards to O3DE SIG area of discipline. Chairpersons are the ultimate arbiters of many standards, processes, and practices.
• Participate in the SIG Discord channel and on the GitHub Discussion forums.
• Serve as a representative of the broader O3DE community to all other SIGs, partners, the governing board, and the Linux Foundation.
• Represent the SIG to O3DE partners, the governing board, and the Linux Foundation.
• Coordinate with partners and the Linux Foundation regarding official community events.
• Represent (or select/elect representatives) to maintain relationships with all other SIGs as well as the marketing committee.
• Serve as an arbiter in SIG-related disputes.
• Coordinate releases with SIG Release.
• Assist contributors in finding resources and setting up official project or task infrastructure monitored/conducted by the SIG.
• Long-term planning and strategy for the course of the SIG area of discipline for O3DE.
• Maintain a release roadmap for the O3DE SIG area of discipline.

Additionally, at this stage of the project, the SIG chairpersons are expected to act in the Maintainer role for review and merge purposes only, due to the lack of infrastructure and available reviewer/maintainer pool.

... And potentially more. Again, this is an early stage of the project and chair responsibilities have been determined more or less ad-hoc as new requirements and situations arise. In particular the community half of this SIG has been very lacking due to no infrastructural support, and a chairperson will ideally bring some of these skills.

Nomination

Nomination may either be by a community member or self-nomination. A nominee may withdraw from the election at any time for any reason until the election starts on 12/3.

Nomination requirements

For this election, nominees are required to have at minimum two merged submissions to http://github.com/o3de/o3de (must be accepted by 2022-01-31). This is to justify any temporary promotion to Maintainer as required by this term as chairperson. Submissions may be in-flight as of the nomination deadline (2021-12-08 12PM PT), but the nominee must meet the 2-merge requirement by the end of the election or they will be removed from the results.

Any elected chairperson who does not currently meet the Maintainer status will be required to work with contributors from the SIG to produce an appropriate number of accepted submissions by January 31, 2022 or they will be removed and another election will be held.

The only other nomination requirement is that the nominee agrees to be able to perform their required duties and has the availability to do so, taking into account the fact that another chairperson will always be available as a point of contact.

How to nominate

Nominations will be accepted for 1 week from 2021-12-01 12:00PM PT to 2021-12-08 12:00PM PT.
Nominate somebody (including yourself) by responding to this issue with:

• A statement that the nominee should be nominated for a chair position in the specific SIG holding its election. Nominees are required to provide a statement that they understand the responsibilities and requirements of the role, and promise to faithfully fulfill them and follow all contributor requirements for O3DE.
• The name under which the nominee should be addressed. Nominees are allowed to contact the election proctor to have this name changed.
• The GitHub username of the nominee (self-nominations need not include this; it's on your post.)
• Nominee's Discord username (sorry, but you must be an active Discord user if you are a chairperson.)

Election process

The election will be conducted for one week from 2021-12-08 12:00PM PT and 2021-12-15 12:00PM PT and held through an online poll. Votes will be anonymous and anyone invested in the direction of O3DE and the SIG holding the election may vote. If you choose to vote, we ask that you be familiar with the nominees.

If there is a current interim chair, they will announce the results in the Discord sig channel as well as the SIG O3DE mailing list no later than 2021-12-17 1:00PM PT. If there is no interim chair, the executive director will announce the results utilizing the same communication channels. At that time if there is a dispute over the result or concern over vote tampering, voting information will be made public to the extent that it can be exported from the polling system and the SIG will conduct an independent audit under the guidance of a higher governing body in the foundation.

The elected chairpersons will begin serving their term on 2022-01-01 at 12AM PT. Tentatively SIG chairs will be elected on a yearly basis. If you have concerns about wanting to replace chairs earlier, please discuss in the request for feedback on Governance.

Meeting Details

This meeting is for the SIG-UI-UX Bi-weekly meeting.

• Date/Time: 11/10/2021 @ 11:00am PT
• Location: Discord SIG-UI-UX Voice Room
• Moderator: UI/UX SIG Committee
• Note Taker UI/UX SIG Committee

The SIG-UI-UX Meetings repo contains the history past calls, including a link to the agenda, recording, notes, and resources.

To sign up for a topic in the SIG-UI-UX Bi-weekly meeting.

• Please add a comment to this ticket with following information:
  • Discord name:
  • Topic of conversation:
  • How much time you might need:
  • Any UX resource you have already been working with and if their attendance is required.
  • ** Any resource to help explain your issue **

What will we be covering?

• Ticket triage - We will go through our ticket backlog and do prioritization and sorting
• Review outstanding ticket assigned previously.
• Check in with designer about problems they are facing regarding tickets and if any help is required
• Feedback from any research previously done regarding tickets.
• Assign designers or UI-UX SIG members UX tickets. This includes deadlines and expectations of work completed.
• In some cases a show and tell may be required to talk through a pending issue or new feature. However we we’ll try to hold these for design critiques for every other Wednesday.
• We will review status of Rev the engine. Any new findings, results, or feedback.
• Close out tickets if completed.

How can I use the Bi-weekly meeting?

• Please add any specific agenda items you would like to talk about to the ticket.
• We will address any agenda items first. These items should be related to outstanding tickets.
• This meeting is not about creating new tickets but reviewing and fixing outstanding tickets.
• If you have speciality such as research, design, or a unique understanding of game development. Let us know so we can help facilitate where we can use your help the most.
• Offer to be a note taker. We always need some help here. Facilitating a meeting and being a note taker can be tough, so any one willing to help will be appreciated.
• Offer to be a person willing to help put together agenda items and or review agenda items from previous meetings.

What should I bring to the bi-weekly meeting?

• Nothing is required but the following items would be helpful
o A list of ticket you are interested in addressing
o An update on tickets you have been working on
o Some prepared questions about the tickets you own

Cut-off time / cancellation

• For the UI/UX bi-weekly meeting the UI-UX SIG team will check the GitHub Agenda item ticket 24 hours before the scheduled meeting, if no one signs up in the session, we will lock down the agenda of that day.
• If you are unable to attend after signing up, Please just reach out in discord or on the ticket to let us know about the change.

Meeting Details

Hi O3DE Community,
We want to invite you to our UX design review and office hours.

• Date/Time: 11/03/2021 @ 11:00am PT
• Location: Discord SIG-UI-UX Voice Room
• Moderator: UI/UX SIG Committee
• Note Taker UI/UX SIG Committee

The SIG-UI-UX Meetings repo contains the history past calls, including a link to the agenda, recording, notes, and resources.

To sign up the Office Hours.
Please add a comment to this ticket with following information:

• Discord username:
• Topic of conversation:
• How much time you might need:
• Any UX resource you have already been working with and if their attendance is required.

This is a bi-weekly meeting will cover the following items.

• UI-UX SIG team will show some of the O3DE workflows that are currently in-progress.
• UI-UX SIG will provide feedback to other UX designers about their O3DE designs.
• UI-UX SIG will provide feedback to the community about O3DE work they are working on.
• Will have open conversations about UX/UI related problems coming down the pipeline.
• Discuss UX tickets

Schedule

• The Sig UX-UI meeting (Triage and UX updates) will be on every other Wednesday at 10-11pm PST
• The design review/Office hours will be on the opposite weeks.
• This means every Wednesday we have something fun for UX going on.

How do I sign up get feedback?

• You can sign up by going to https://github.com/o3de/sig-ui-ux/issues
• Find the specific event you are interested in attending and getting feedback on.
  • In the comment section of that ticket place the details you would like to talk about.
  • Please include your name and/or Discord Name
  • The area of topic you would like to cover
  • The amount of time you might need to review this topic
  • Any individuals you have been already working
  • Any specific people you would like to attend this session for help.

How can I use office hours:

• Request a "sign-off" on your project from the UI-UX SIG.
• Usability/UX review of your designs/mock-ups.
• Discuss certain customer pain points or UX related topics.
• Brainstorm ideas or solutions to a user problem or feature.
• Submit user research or UX design requests.
  What should I bring to the office hour:
• Nothing is required but the following items would be helpful
  • A brief project overview or documentation, This should include the following
  • A simple user problem statement. As a user I want to solve this problem...
  • Who is your audience? Who are the users/user groups affected by the change?
  • What is your vision behind this change or update?
  • What is your UX issue related to: user interface, usability testing, learnability, documentation etc?
  • Materials/Workflows of the existing product. Sketches or wire-frames of ideas. PR/FAQ are also help.

Cut-off time / cancellation

• The UI-UX SIG Office Hours is sign-up based. We will check the topics 24 hours before the scheduled office hour, if no one signs up in the session, we will lock down the agenda of that day.
• If you are unable to attend after signing up, Please just reach out in discord or on the ticket to let us know about the change.

UI-UX SIG Meeting — Today's content for 04-28-2022

Hi O3DE Community,
We want to invite you to our conversation about today's newest content, design specifications, and program update.

This weeks conversation I'll be enjoying a conversation with Danilo @AMZN-daimini, John @jonawals and myself Joshua Rainbolt @rainbj about how prefab editing experience is going to be changing. Will look at some of the new updates which we call focus mode and how this will impact the user experience. We'll be giving a demo for a couple different examples of how user might experience this new world of editing. This will give users some insight on new experiences coming including in the outliner, the viewport, and the inspector. Come join us and let us know what you think about our experience and how we can make it better.

In our previous meeting we concluded our multiplayer demo and set up with Gene Walters. If you would like to watch these videos on re-broadcast please look out for our link in the next few weeks.

Schedule

• Date/Time: 03/30/2022 @ 10:00am Pacific Time (PT)
• Location: Discord SIG-UI-UX Voice Room
• Moderator: UI/UX SIG Committee
• Note Taker UI/UX SIG Committee

Meeting Details

We want to invite you to our Sig UX UI expert interviews, global updates, Roadmap visibility, and design review. This meeting is bi-weekly and we will cover the following items:

• New and interesting topics that O3DE has hot of the press. Because these items are so new we are likely to find bugs and new feedback from the community. This is kind of the point. As we let you observe and talk to us we can make adjustments to the workflows before it goes out to the masses.
• RTE program updates and new details. Any new findings, results, or feedback.
• Check in with designer about problems they are facing regarding tickets and if any help is required.
• Feedback from any research previously done.
• Assign designers or UI-UX SIG members UX work.
• Conduct live research.
• Create any ticket or close tickets based on our conversation.

Past meetings, including a link to the agenda, recording, notes, and resources.

https://github.com/o3de/sig-ui-ux/issues?q=is%3Aissue+is%3Aclosed+todays+in%3Atitle

To sign up for a topic in the Todays topic Bi-weekly meeting.

• Please add a comment to this ticket with following information
  • Discord name.
  • Topic of conversation.
  • How much time you might need.
  • Any UX resource you have already been working with and if their attendance is required.
  • Any resource to help explain your issue.

How can I get UX help on an issue?

We generally use the alternative weeks open office hours meeting to have conversations like this. Please look for the next meeting here and include a request in the comments. As long as time is open we will address your agenda right away. Please give us 24 hours notice before the meeting to have a UX expert in that area join the meeting.
https://github.com/o3de/sig-ui-ux/issues?q=is%3Aissue+is%3Aopen+Office+in%3Atitle+

How can I Help?

• Great question. If you have speciality such as research, design, or a unique understanding of game development. Let us know so we can help facilitate conversation on how best to contribute.
• Offer to be a note taker. We always need some help here. Facilitating a meeting and being a note taker can be tough, so any one willing to help will be appreciated.
• Offer to be a person willing to help put together agenda items and or review agenda items from previous meetings.

What should I bring to the bi-weekly meeting?

• Nothing, unless your a presenter, your attenance and great conversation is enough

Cut-off time / cancellation

• For the UI/UX bi-weekly meeting the UI-UX SIG team will check the GitHub Agenda item ticket 24 hours before the scheduled meeting, if no one signs up in the session, we will lock down the agenda of that day.
• If you are unable to attend after signing up, Please just reach out in discord or on the ticket to let us know about the change.

SIG-UI-UX Office Hours for 03-09-2022

Hi O3DE Community,
We want to invite you to our UX UI design review and office hours.

• Date/Time: 03-09-2022 @ 10:00am PT
• Location: Discord SIG-UI-UX Voice Room
• Moderator: UI/UX SIG Committee
• Note Taker UI/UX SIG Committee

The SIG-UI-UX Meetings repo contains the history past calls, including a link to the agenda, recording, notes, and resources.

To sign up the Office Hours.
Please add a comment to this ticket with following information:

• Discord username:
• Topic of conversation:
• How much time you might need:
• Any UX resource you have already been working with and if their attendance is required.

This is a bi-weekly meeting will cover the following items.

• UI-UX SIG team will show some of the O3DE workflows that are currently in-progress.
• UI-UX SIG will provide feedback to other UX designers about their O3DE designs.
• UI-UX SIG will provide feedback to the community about O3DE work they are working on.
• Will have open conversations about UX/UI related problems coming down the pipeline.
• Discuss UX tickets

Schedule

• The Sig UX-UI meeting (Triage and UX updates) will be on every other Wednesday at 10-11pm PST
• The design review/Office hours will be on the opposite weeks.
• This means every Wednesday we have something fun for UX going on.

How do I sign up get feedback?

• You can sign up by going to https://github.com/o3de/sig-ui-ux/issues
• Find the specific event you are interested in attending and getting feedback on.
  • In the comment section of that ticket place the details you would like to talk about.
  • Please include your name and/or Discord Name
  • The area of topic you would like to cover
  • The amount of time you might need to review this topic
  • Any individuals you have been already working
  • Any specific people you would like to attend this session for help.

How can I use office hours:

• Request a "sign-off" on your project from the UI-UX SIG.
• Usability/UX review of your designs/mock-ups.
• Discuss certain customer pain points or UX related topics.
• Brainstorm ideas or solutions to a user problem or feature.
• Submit user research or UX design requests.
  What should I bring to the office hour:
• Nothing is required but the following items would be helpful
  • A brief project overview or documentation, This should include the following
  • A simple user problem statement. As a user I want to solve this problem...
  • Who is your audience? Who are the users/user groups affected by the change?
  • What is your vision behind this change or update?
  • What is your UX issue related to: user interface, usability testing, learnability, documentation etc?
  • Materials/Workflows of the existing product. Sketches or wire-frames of ideas. PR/FAQ are also help.

Cut-off time / cancellation

• The UI-UX SIG Office Hours is sign-up based. We will check the topics 24 hours before the scheduled office hour, if no one signs up in the session, we will lock down the agenda of that day.
• If you are unable to attend after signing up, Please just reach out in discord or on the ticket to let us know about the change.

Summary

Allow users to define the data, and make the system to use the metadata to talk with each other.

Example, if user create a tag using the tag component, but when entity searching doesn't know the tag. and in SC, users have to manually type in the tag.

Description

Meeting Details

Date/Time: 10/06/2021 @ 11:00am PT
Location: Discord SIG-UI-UX Voice Room
Moderator: UI/UX SIG Committee (Joshua)
Note Taker UI/UX SIG Committee

This meeting is for the SIG UI-UX Office Hours. For details of the office hours, please visit here.
To sign up the Office Hours, please the comments below with following information:

The SIG-UI-UX Meetings repo contains the history past calls, including a link to the agenda, recording, notes, and resources.

SIG Updates

What happened since the last meeting?

Meeting Agenda

• Type: [request approval/request review/brainstorm ideas/submit research or design request/others]
• Background or links to the related docs
• Possible length of discussion: 30 mins or 1 hour

Outcomes from Discussion topics

Discuss outcomes from agenda

Items from our open Discussion

• JT - He would like to see us using these meeting to show details about how consistency of showing new items to inspire new updates and changes. Understanding patterns.
• We need to speak with the other Sig charters because they are not knowing exactly when to apply UX-UI labels. We might left to their tickets so just remove. @forhalle
• We should have a larger conversation about patterns overrides. When is new patterns override. It appears they are
• PhysX might be overriding the patterns.

Please List any additional items below!