Skip to content
This repository has been archived by the owner on Oct 28, 2024. It is now read-only.

Channel centric UI #133

Merged
merged 14 commits into from
Jul 13, 2021
Merged

Channel centric UI #133

merged 14 commits into from
Jul 13, 2021

Conversation

flynnduism
Copy link
Member

@flynnduism flynnduism commented Jul 10, 2021

This PR updates the UI with new layouts and styles. This replaces #105.

Main changes:

  • app view is split to a channel/revision two column layout, implementing a new IA model as outlined here
  • use a tabbed approach to switch between environment views
  • forms for creating / editing channels are reorganized into a series of choices

Views updated:

  • Account/Login
  • Account/register
  • App/Details
  • App/New
  • App/Delete
  • App/NewChannel
  • App/EditChannel

Missing Pieces

There are some additional parts of this that aren't working properly, and I will be seeking help to 🍐 get them functional:

  • Adding cleanup and rendering more data for Revisions in the left-hand timeline section (ties into Event history #134)
  • App/Edit routing is breaking
  • App/EditChannel form isn't submitting correctly
  • App/NewChannel form isn't submitting correctly

Some Screenshots

Screen Shot 2021-07-09 at 4 54 01 PM

Screen Shot 2021-07-09 at 4 54 20 PM

Screen Shot 2021-07-09 at 4 53 53 PM

Copy link
Contributor

@bacongobbler bacongobbler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great. Deployed locally and everything seems to work. Really like the work done with the radio buttons for using a range revision rule vs a specific revision, too.

Let me know if you'd like to spend some time pairing on the issues you listed in the OP. I'm free most this week (asides Wednesday/Thursday - I'll be OoO on those days).

<div class="columns">
<div class="column">
<ul class="rev-list">
@foreach (var revision in Model.Revisions.OrderByDescending(r => r.OrderKey())) {
Copy link
Contributor

@bacongobbler bacongobbler Jul 12, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

would you mind adding a TODO note to tie in #134 here?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What you have here is more like the "revisions" table in the existing UI, which tells the user what revisions are registered and where they are active. I would definitely not describe this as "recent activity" - e.g. there might be recent changes to a legacy deployment whose version number might be quite old. Correspondingly, I would describe this as "is currently active on" rather than "was pushed to" - we are not observing the push event here, only the current deployment state.

We can choose whether to have the 'all revisions' list, the 'recent activity' feed or both - I'm just saying we need to label them appropriately.

(Another idea for the revisions list, if we want one, would be to have an 'active revisions' list on the main app page but keep the 'all revisions' list off on a linked page or behind a 'see all' toggle button.)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @itowlson I am going to rework this section (and the terminology therein) in a follow up PR

@flynnduism flynnduism self-assigned this Jul 12, 2021
Copy link
Contributor

@itowlson itowlson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks amazing. One minor comment on wording where we are conflating two different things. Otherwise eager to get this in as soon as you've addressed the bits you said are currently not working.

<div class="columns">
<div class="column">
<ul class="rev-list">
@foreach (var revision in Model.Revisions.OrderByDescending(r => r.OrderKey())) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What you have here is more like the "revisions" table in the existing UI, which tells the user what revisions are registered and where they are active. I would definitely not describe this as "recent activity" - e.g. there might be recent changes to a legacy deployment whose version number might be quite old. Correspondingly, I would describe this as "is currently active on" rather than "was pushed to" - we are not observing the push event here, only the current deployment state.

We can choose whether to have the 'all revisions' list, the 'recent activity' feed or both - I'm just saying we need to label them appropriately.

(Another idea for the revisions list, if we want one, would be to have an 'active revisions' list on the main app page but keep the 'all revisions' list off on a linked page or behind a 'see all' toggle button.)

@bacongobbler
Copy link
Contributor

Would you mind rebasing when you get the chance? Thanks!

Signed-off-by: flynnduism <dev@ronan.design>
Signed-off-by: flynnduism <dev@ronan.design>
* fixes directory casing mismatch issue (Hippo > hippo)
* includes fix for the App/EditChannel and App/NewChannel forms
* fixes controller issue for App/New

Signed-off-by: flynnduism <dev@ronan.design>
Signed-off-by: flynnduism <dev@ronan.design>
Signed-off-by: flynnduism <dev@ronan.design>
@flynnduism flynnduism force-pushed the channel-centric-ui branch from 64d81d0 to 41068ba Compare July 13, 2021 18:41
Signed-off-by: flynnduism <dev@ronan.design>
Signed-off-by: flynnduism <dev@ronan.design>

<div class="tabs">
<ul>
<!-- an initial/default environment, auto-generate when creating an app -->
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

delete this

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

removed

@Html.DisplayFor(modelItem => item.Name)
</p>
</a>
<a class="env-url" target="_blank">
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we make this clickable?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's now clickable

@bacongobbler
Copy link
Contributor

I've been putting this PR through its paces today, and it looks like it's ready to go!

Signed-off-by: flynnduism <dev@ronan.design>
Signed-off-by: flynnduism <dev@ronan.design>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants