Dashboard: Dashboard doesnt look like its part of Tekton

[CarolynMabbott]

Expected behavior

Dashboard should look like part of Tekton

Actual behavior

The dashboard doesn't look part of tekton

Steps to reproduce the problem

1.
2.
3.

Environment

• Kubernetes Platform:
  

• Tekton Pipelines version:
  

• Tekton Triggers version:
  

• Tekton Dashboard version:
  

Additional Info

Add the colourful Tekton cat back so we look part of Tekton
Our colour scheme looks nothing like its related to tekton

[a-roberts]

So specifically I can only think of a reversion to the coloured cat image as well, is there anything else in particular you have in mind @CarolynMabbott? Any suggested colour scheme?

@kimholmes @AlanGreene @carrenelloyd what are your thoughts on this too?

[carrenelloyd]

@a-roberts @CarolynMabbott Can you please post a screengrab of what you are referring to exactly?

[kimholmes]

@CarolynMabbott It would be helpful to understand what the Tekton color scheme is. I wasn't aware of one. I know the cat logo had colors, but beyond that, I'm not aware of a color scheme.

[CarolynMabbott]

https://tekton.dev/ - What the cat should look like

Currently what the cat looks like on the dashboard

[kimholmes]

FYI - that site is currently under construction. It's being replaced by this:
https://tekton-website-258208.firebaseapp.com/

[AlanGreene]

Screenshot of the current content of that link for comparison, this is the current state of the new website design:

If we're going to make changes to the dashboard to match the Tekton website we should probably wait for it to land or get confirmation from those working on it that this is in fact the (current) final design.

[kimholmes]

Thanks @AlanGreene Yes. My point was that we should keep the dashboard neutral. And the Carbon design system does a good job of that.

[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]

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]

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]

@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.