• rebase

• fix rebase

• rebase?

• rebase?

• double check diff by hand

• Add back crumbs, icons

Will update with crumbs and icons.

This is the search thing in Discourse and it works super well. As a first time admin, I used it like 50 times to find all the stuff I wanted to change without feeling overwhelmed by 500 options. I thinkkkkkk I could build a typeahead datasource and do this?

Icons: I can add back icons, I'm sort of on the fence of how useful they are.

I definitely understand that thinking and if we were building a new product today, do that. At least, I think we generally do that? Renaming applications comes with legacy baggage, and I'm not convinced the cost of the baggage plus the engineering cost outweigh a basic solution that could easily be rolled back. When you have very limited resources, how do you budget changes that are "correct, but highly expensive" vs "incorrect, but very cheap". Outside of an engineering organization, do you make that same decision? I gave serious consideration to renaming them this weekend, and that path seemed in the 1-2 month range for me, even if you agreed to it. I can't in good conscience allocate that much time to a single point of polish.

I strongly dislike this change and think it solves a non-problem that only a few users experience and which we've already given them tools to deal with.

• update two separate panels

• remove unused var

I'd probably lean towards just increasing the padding under the text to make sure the field is clearly separate from the one below it.

• back out phui-info-view tweaks

• move header css change
• back out setup issue CSS

• add todo for crumbs

• finished first pass

@mna Please follow our bug reporting guidelines if you feel you've encountered a bug. This task is several years old and not relevant.

• fix scope of CSS rule in ApplicationSearch

• remove history specific code no longer needed

• simpler

I believe this is the right path forward, though the road may be bumpy.