Front End Development for Triggers UI

[kimholmes]

This issue provides front end development specifications to build the Triggers UI of the dashboard. These designs are based on UX iterations between the design and development teams and are based on previous design specs located under this Epic:

#675
The design contact is @ carrenelloyd

[carrenelloyd]

Please ping me on Slack with any questions.
Slack: @carrie

[kimholmes]

@carlos-logro @AlanGreene

[ncskier]

I just noticed that the Triggers | YAML toggle menu should probably be a Triggers header. Instead, the toggle button should be at the top of the page, and it should read Details | YAML to match the toggles we have in the rest of the pages:

The current layout will look weird when switching to the YAML view, because the entire page becomes YAML:

[kimholmes]

@ncskier Just had a conversation with Carrie, the viz designer and she reminded me that we did decide to move those tabs down. The reasoning behind it was that, if we have a Details tab up top, it will be very sparse. So, we decided we didn't need a Details tab and that resulted in moving the tabs below the Details content.

[carrenelloyd]

1. Added Details subheader below Tabs
2. $productive-heading-02
3. 24 spacing token above and below the Details text

[tekton-robot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[tekton-robot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

[tekton-robot]

@tekton-robot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Send feedback to tektoncd/plumbing.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[AlanGreene]

/remove-lifecycle rotten
/reopen

[tekton-robot]

@AlanGreene: Reopened this issue.

In response to this:

/remove-lifecycle rotten
/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[AlanGreene]

/remove-lifecycle stale

[AlanGreene]

We should also consider how a user will navigate between Triggers resources and the resulting Pipelines resources.
This has come up a number of times, most recently in https://tektoncd.slack.com/archives/CHTHGRQBC/p1602508229019000. Although that question was initially focused on the Pipeline visualisation it makes sense to consider how it would affect navigation and the presentation of the Triggers resources too.

[tekton-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

[AlanGreene]

/lifecycle frozen