Kuma: U - Create Designs for Optimize Breadcrumbs, header and footer for mobile

[chinikes]

User Story

As an MDN user on a mobile device, I want a clean header so I can get to the content I'm really interested in

Acceptance criteria

• [x] Breadcrumbs are optimized for mobile
• [x] Header is optimized for mobile
• [x] Footer is optimized for mobile
• [x] Engineering sign off on designs

Tasks

1. 
   
   • [x] Create project doc
   
   
2. 
   
   • [x] Add UI for breadcrumbs in Design System Sketch file
   
   
   • 
     
     
     • [x] Test usability via short UserZoom clickable prototype
     
     
     
   
   
3. 
   
   • [x] Add UI for header in Design System Sketch file
   
   
4. 
   
   • [x] Add UI for footer in Design System Sketch file
   
   
5. 
   
   • [x] Schedule sync with Engineering team to discuss proposed system/UI
   
   
6. 
   
   • [x] Finalize assets/collections for Engineering team
   
   

[malqinneh]

Mobile breadcrumb
Just wrapped up MDN mobile breadcrumbs (finished a UserZoom study). Link the solution we're proposing to move forward with for mobile. Also worth noting that this solution was already shared with the engineering team.

[malqinneh]

Mobile header
Link to mobile designs
Link to tablet designs

[malqinneh]

Mobile footer
Link to mobile designs
Link to tablet designs
Link to desktop designs

[malqinneh]

Hey @tobinmori - anyone in particular I should loop in with regarding this issue? I added comments with links to designs. Also, @schalkneethling has already seen some of the proposed solutions.

[schalkneethling]

@malqinneh Had a preliminary look over the designs. They look good to me. What is the proposed timeline to implement these?

[malqinneh]

@schalkneethling I don't think we had set implementation timeline yet. Should be decided on by the team whenever it makes it to the Dev sprint (as an engineering story). cc @petercpg

[tobinmori]

@malqinneh - I looked these over and they're good with me. Sorry for the delay!

[schalkneethling]

Agreed. I would recommend the next step be that we create tasks for each component and then dig deeper into each component respectively in the relevant issue. As we think through and mouth code these things we will most likely find some edge cases and questions.

It would be good to have those discussions confined to each component individually. Thoughts @malqinneh @tobinmori @mindy

[malqinneh]

Makes sense @schalkneethling. In the future, we should separate issues such as this into multiple issues for each deliverable. Who wants to do that for this issue before it's closed?

[schalkneethling]

Makes sense @schalkneethling. In the future, we should separate issues such as this into multiple issues for each deliverable. Who wants to do that for this issue before it's closed?

I am happy to break these out into individual items.

[chinikes]

Hi @malqinneh - With all ACs marked as done, can this story be deemed as done? @atopal

[malqinneh]

It can, assuming Schalk created separate issues for each component.

On Mon, Mar 16, 2020 at 11:40 AM Peter Chinaka [e-mail]
wrote:

Hi @malqinneh https://github.com/malqinneh - With all ACs marked as
done, can this story be deemed as done? @atopal
https://github.com/atopal

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mdn/kuma/issues/6539#issuecomment-599605854, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABEYXQUHSVUXP36RCNOZMR3RHZB5FANCNFSM4KX7QGRA
.

[schalkneethling]

Hi @malqinneh - With all ACs marked as done, can this story be deemed as done? @atopal

It can, assuming Schalk created separate issues for each component.
…
On Mon, Mar 16, 2020 at 11:40 AM Peter Chinaka @.*> wrote: Hi @malqinneh https://github.com/malqinneh - With all ACs marked as done, can this story be deemed as done? @atopal https://github.com/atopal — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#6539 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABEYXQUHSVUXP36RCNOZMR3RHZB5FANCNFSM4KX7QGRA .

On my todo list for tomorrow :) I will be sure to close this one once I am done.

[schalkneethling]

Separate issues created. See links above ^ #6687, #6689, #6711