Mocks for navigation and UX that scales for all K8s resources

[bryk]

• this will be used later in a design doc proposal
• also renamed old mocks folder to tell more than just date

See: #584

---

This change is

[bryk]

@olekzabl Can you review?

[codecov-io]

Current coverage is 86.89%

Merging #585 into master will not affect coverage as of 04bace2

@@            master    #585   diff @@
======================================
  Files          102     102       
  Stmts          870     870       
  Branches         0       0       
  Methods          0       0       
======================================
  Hit            756     756       
  Partial          0       0       
  Missed         114     114       

Review entire Coverage Diff as of 04bace2

Powered by Codecov. Updated on successful CI builds.

[olekzabl]

A few issues:

• navigation.png: "togheder" -> "together"
• manu-extended.png: "manu" -> "menu" (in the file name)
• rc-details-page-events.png: tooltips disagree with pic! section
  "Properties of the object" does not exist
• some inconsistencies between details pages:
  • "Properties in structurized form" in {pod,rc}-details-page-overview.png
    look different (no "State" on the latter)
  • Headers of link sections are named by object types in
    {pod,rc}-d-p-o.png while by roles in details-page-template.png
    (ideally, the header should perhaps combine the role and the target
    object type)

On Tue, Mar 29, 2016 at 12:13 PM, Piotr Bryk [email protected]
wrote:

@olekzabl https://github.com/olekzabl Can you review?

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#585 (comment)

[floreks]

• rc-details-page-events.png: tooltips disagree with pic! section

Ops, I will fix that.

• some inconsistencies between details pages:
  • "Properties in structurized form" in {pod,rc}-details-page-overview.png
    look different (no "State" on the latter)

This is just a proposal. Should we actually group properties by some common purpose? Tell me which one you like better and I'll adjust other.

• Headers of link sections are named by object types in
  {pod,rc}-d-p-o.png while by roles in details-page-template.png
  (ideally, the header should perhaps combine the role and the target
  object type)

I'm not sure I know what you mean. Are you referring to the Pod > <name> section on top near action buttons? Is it wrong? On the template we've got Resource 1 > foo instance which I believe is correct. Could you elaborate?

[floreks]

Please find updated rc - events mock here

[bryk]

Please find update rc - events mock here

Can you post the source?

[floreks]

Here is the link to balsamiq project

[bryk]

All addressed. PTAL.

@floreks You can delete the links you've posted.

[bryk]

I'll merge to base design doc on this. Any comments can be addressed in follow up PRs.