In T4207#55409, @qgil wrote:

Original request: http://fab.wmflabs.org/T162

(also, if you have examples from other sites you feel do this well, feel free to drop inspiration here).

Sure.

Is this yoinkable for a Design direction? I can easily bang out a few mocks this week of various ideas. Short-term, I think we're wasting a lot of space. Long term, I want to make sure the experience is simple for new users, and powerful for people who have to sit in it all day.

Remaining work here is:

Doesn't look as bad here either:

Ok, thank you! Something is something and this might be enough. I will report back if there is anything relevant.

Looks good in Debian / Chrome...

I think this is specific to the global typeahead; tokenizers behave as expected:

Looks completely different on my Mac (not that it looks great). Wonder what changed.

I think we've resolved this as far as we're going to for the short-term. Additionally this week we've increased the fonts in the header and subheader (status - policy) as well as now uniformly use indigo to indicate closed in the status and on the timeline. These make it easier to spot and associate closed objects where previously the color for closed was a rather non-special black.

We'll want to use the background colors for tags, and maybe with the checkered tag just use a simple grey background.

Projects currently have a small "typeahead/tokenizer" icon (which appears in typeaheads) and a larger "profile picture".

Closed by commit rP725e1e198868.

Closed by commit rP800b3b030f1c.

Nuked.

Need to nuke #d3net too. Keep finding stragglers.

After D11126, you can test this by doing something like this:

I assume this task just covers visibility policy?

In T6802#88402, @chad wrote:

We don't have access to said task, feel free to reproduce here (or use screenshots).

Thanks!

Awesome! Do you have any left?

Thank you immensely, for these rapid changes!
Feel free to close this bug, now that the most pressing issues have been resolved.

We don't have any plans for that in vanilla Phabricator. T4863 covers customizing workboards, T418 covers customizing everything else. In general though T3820 is how we think installs should deal with mixed levels of permissions in a single install.

also, could have similar differentiation in search results, workboards,
task lists on projects, feeds (i.e. side of front page), pages for
individual users with tasks changed by that user

Introducing pure red text in the header could be a useful first step, yes. We would need to think of a solution that doesn't conflict with other plans to put more emphasis in task resolutions i.e. T6500: Duplicated tasks should be marked more visibly as duplicates.

As a first pass, we could either go with something simple like text:

About the footer, it is worth noting that Wikimedia's instance has a footer, while here you don't, and most existing instances don't have one because it is a relatively recent feature. The fact that the site with a footer gets this feedback has some relevance.

In T6792#88135, @epriestley wrote:

It would be easier for us to motivate changes like this if specific users weighed in and said "I personally have difficulty reading text X, and it would be helpful if it was higher-contrast", versus "text X does not conform to standard Y".

It would be easier for us to motivate changes like this if specific users weighed in and said "I personally have difficulty reading text X, and it would be helpful if it was higher-contrast", versus "text X does not conform to standard Y".

I don't know how long the current design of Phabricator will last. It's already deviated from the .org screenshots and those went up only maybe 4-6 weeks ago. In general, we prefer to move quickly and improve Phabricator every week.

Some other general thoughts:

Sorry, no idea when I'll get to this.

In T4214#83351, @qgil wrote:

we will wait patiently for this one.

Basically, we clip (actually we use ellipsis if you're at HEAD) overly long titles. If you make a dashboard and put content heavy items in a the narrow column on a very narrow screen, this is what can happen. We have alternate displays for tablet and mobile widths.

Closed by commit rP7aedb3c04e06.

Closed by commit rPe872f79f6147.

I have installed P1094 on our installation and it's more or less exactly what I want. The only major improvement for me would be to have something similar in the project/tag-view. Showing the same dependience-tree for all tickets in that tag. Not sure if that's doable. The untill-then-fix is to have a "mother-of-all-tickets"-ticket per tag which has all other tickets as childtickets.

This task is about offering a better control (e.g., one that lets you visually click a picture of what the layout looks like, instead of selecting it from a dropdown). However, there are two related tasks in this vein; I'm going to merge them together.

We have a dashboard selector. Is this task about offering more options?

Sadly does not repro on Chrome 41.

Yeah it might just be something like setFooterLink which we provide a base footer, and links can be tacked on.

Closed by commit rPe7b6d332e9af.

Ordered more shirts, in Official Indigo!