-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Platform UI Refresh #205
Comments
I am going to recommend that we don't bother with critiques until we can see how our atoms and molecules start reacting with one another at the organism phase. |
Just amended point 3. to include "by at least one designer and other staff member (at organism level)" |
|
Yes, the idea is to work from the littelest things to the more complex things, adjusting the foundational, atom elements in the process.
It represents assessing them and designing them, but not implementation in the PL/Client. |
Thats useful thanks. I might be too hopeful here. But if possible, it'd help to have a best guess - with thoughts from @Angamanga and @middle8media - whether the scope of design changes is likely push us towards just updating things in the PL or to rebuilding some/all of them from scratch. |
@rjmackay @middle8media @justinscherer @Erioldoesdesign I think update or rebuild depends on how big the design-changes are. We could for example restructure and use the atoms->pages concept more strictly and rebuild components where necessary. |
I think let's just wait for us to make some progress on these tickets and we'll have another conversation about impact on React rollout in a couple weeks. |
@justinscherer @Erioldoesdesign do you know what issues from the UI refresh epic will be / should be worked on during cycle 6? (for the design team) @Angamanga do you have any specific priorities in mind/ things we need for the migration and are blockers? cc @jrtricafort please jump in if this was discussed already or you know the answer :) |
@rowasc @justinscherer We talked about this in the Design implementation - Process sync call just now but just so it's documented here too. Me and Justin will take a look tomorrow when we sync up to prioritise for the remainder of the week he is OOO. We'll be moving design tickets into cycle 6 as part of that sync up :) |
@Erioldoesdesign excellent thankk you ! |
@rowasc I don't know the answer. @justinscherer and @Erioldoesdesign can you provide your input here? |
@jrtricafort We moved a few design tickets into cycle 6 :) when Justin is back on Monday. There may be more we can tackle but there's a good amount in there for now 👍 |
Thanks @Erioldoesdesign and @justinscherer ! |
Summary
Refactor the Platform UI from the bottom up using Brad Frost's Atomic Design Methodology
The methodology has us start with the most basic, fundamental components of the UI, the atoms, and cascade those designs into more and more complex components(atoms --> molecules --> organisms --> templates) until we arrive at new page templates.
This work is intended to coincide with the frontend javascript framework re-platform into React.
Acceptance criteria
Every piece of work must:
For reference, there is an existing list of UX debt to be addressed in this epic
The text was updated successfully, but these errors were encountered: