@lpriestley hit this and also wasn't sure if the animation was intentional or not.

oh, fixed!

In T7418#99197, @chad wrote:

M1421 for record has discussion on this feature.

Should we just merge this to T5558? The discussion there was around making Project homes be "Dashboards", so you'd install a Global or specific set on a per project basis or just design a super-awesome-dashboard by default.

I also think T3670 and T5558 also play into this. Specifically, if we rocked those tasks, then that could essentially complete this task, as in the value of "details" rises significantly enough that the switcher is a toss up. M1421 for record has discussion on this feature.

Ok, for what is worth this is my own experience:

Yeah, I want to clean up T7410 first, at a minimum, before looking at this. As a heavy Phabricator user on this install (where we haven't had anyone clicking workboard buttons randomly), my experience since we implemented this is that the workboard rule always takes me to the correct page (and that page is usually the workboard).

I don't feel consistent is the correct path here, specifically because each project "container" serves vastly different purposes and your reason for visiting those pages vary wildly. The point of auto-switching is to adhere to the fundamental design principle of being an efficient tool for power users. It solves the core issue of taking the user in the majority of cases, to their correct destination. If the role and feature set of Projects continues as it has, a consistent landing experience will often be the less efficient for productivity.

Pretty sure D11904 fixed this.

Rainbow logo was pretty fabulous.

Been thinking if we go back to the rainbow logo, no one will want to change it maybe?

Yeah, we specifically plan to make changes in this vein eventually:

This process isn't user friendly, and I don't think we'll close this out until it really is. Feel free to leave feedback here.

One issue with this as it stands today is that it's hard to get the file to be marked as cacheable. Some discussion in T6007. Without the flag, the logo will reload/flicker on every page load.

Okay, no worries about making it simpler. Its not really that fancy anyway; I just made this config a "custom" type, wrote the pertinent class, and have reasonable error-checking logic in there for my guess at the spec. Good to know the retina stuff doesn't really matter; I thought I had to emulate the CSS properties as they exist now for e.g. whatever Apple magic happens when you switch from portrait to landscape mode.

(In the Phacility case, the 1x is about 2KB and the 2x is about 3KB. Clearly not worth special casing to save 1KB, once, on non-retina displays.)

We should be able to use one image and just background-size-x/y it to the right dimensions. On retina it will have 2x resolution properly, on normal displays it will be "too big", but that's fine (they won't be much bigger, and they'll get cached).

The image I checked in is the same size as the standard logo.

The zip here is void. What I checked into rSERVICES is what's been properly tested.

Did a bunch of work on this and I just realized that I'll need to add some code to when we render the header to add a full on style section. I think this is necessary to support retina or whatever you want to call the 1x vs 2x versions. :/

I guess you'd probably need to override background-image-position-x/y and such too if it's currently using a sprite.

I think regenerating the map is really bad in the long run. Particularly, it means the sprite map and resource map will be dirty in the working copy, so git pull will fail the next time we update them and we'll get a bunch of instances that can't upgrade. Another issue is that Phacility users could not customize their instance headers, because they all share a single map. And they need optipng installed. And the daemons need write access to the source code itself if we're going to do this in the background.

scripts/celerity/generate_sprites.php

How does one generate the sprite map? I'm finding things to be hard to figure out... e.g. the CeleritySpriteGenerator class feels like its important, but I have no idea how it gets invoked?

I think 2-3 concentric circles of eldritch runes should appear and rotate in alternating directions. As they gain speed, the browser should emit a bass hum and begin to shake. This will help users understand the interaction better.

I'm all for @aik099 suggestion - zoom while centered instead of jump.

Maybe the hover effect should be changed to zoom while keeping icon position centred.

I am (so far) not a fan of it, on the otherhand, if they had faces on the icons and those changed when you moused over then... that would be epic :D

This is designed and checked in.

The design is a little experimental, so we'll monitor feedback for a while and see if changes need to be made.

Ah, then ok. Thought this was a mistake, because nothing else jumps on hover.

The transition is intentional.

Sounds like we're all kind of weakly in favor of not branding instances.

Added the 1x and 2x logos, not sure where to drop them or how they look in practice. haha.

This is "working as intended" on mobile. We should maybe mark XHPAST as developer/prototype or something.

In T4984#57937, @chad wrote:

I'd imagine we'd want to group them by Application.

Maniphest
W12 Unbreak Now Tasks
Display: ObjectList · Columns: 1, 2, 3
...

Given a bit of thought to this, and a lot of research into competing products. In essence I think T4100 is the correct path, but with a slightly more expanded role - basically go all in.

T7251 is a suggestion of a UI I particularly like - the Product Studio (Microsoft's internal bug tracker) / "query builder" interface.

Are you considering to interpret #alias in quicksearch box as "in project #alias"? For example, to query a string within the tasks associated to one project only. Right now this is usually a two-step process, first searching for the string, then narrowing to the project.

Also if you press 'Custom Policy' for visibility below the title of things like Pastes, it doesn't provide a very useful message.

Not likely worth spending resources on .

D11402 re-jiggers the email such that its comment -> inline comments -> the rest of the stuff.

Just adding my vote to increase the priority for this feature.

Thanks for the feedback, but have no plans to pursue this in the upstream at this time. See T4213 for customizing Phabricator's design if that interests you.