@tgr can we get confirmation on the browser, please?

@chad, it looks like we're just using the browser's default outline for buttons.

Yeah, I tend to agree. I don't really see any approaches we can take here that don't make things a little worse for experienced users who already know what they're looking for, and I'm not sure there's too much of a use case left for less-experienced users.

The main concern for me would be typeaheads are for knowing what you're looking for already, and making that faster / easier. Browse interfaces are for discovery.

This is sort of what I was thinking about for the "Search Description" / "Usage Hint" (descriptions / projects are random examples):

(You could write some similar rules if you want to try something in that vein, although it's a pretty big pain to fork JS/CSS right now.)

I should make a Herald rule to auto-resign.

Okay well @chad resigned from D16893 as soon as he saw animation in a CSS file so I don't think that one's going anywhere.

Alright, I'm going to try this:

+1 to what 20after4 wrote. The approach is definitely helpful, and to make this look less cluttered and inconsistent ("are projects with longer descriptions which take up more vertical space somehow more important?"), cutting off project descriptions seems like a good compromise.

It would be cool if in Phabricator will be implemented a Pre-Build Dark theme.

In T11034#199653, @epriestley wrote:

---

Now that this has been deployed for a while, I'm curious if there's any feedback about it? Specifically:

• Does this approach generally seem like it's a reasonable solution to the problem (if not in its current form, in some similar form which handles these issues more gracefully)? Or are we not really in the right ballpark?

I suppose an alternate path is to enable Dashboards on Project homepages, and you can embed your project wiki or text panel for a really cool long description and information.

Would you fill out at least, like, 5 of them?

Hovercards, Search, Browse, etc. It could get used.

We could call it "Search Description" so it feels clear that it only displays in some UIs.

Yeah, I think it's pretty reasonable if people would actually fill it out. We could surface it in a few other places too (e.g., /projects/) without fallback. It just seems like there's a decent chance no one will ever fill it out and it will sort of just be cluttering up the UI. But the cost on our side is pretty small, so if some people claim that they'd probably want to fill it out I'm happy to move forward with it.

Provide an alternate, text-only field for "Project summary in typehaead results." which users only enter text into, so we don't have to worry about remarkup.

For reference, here's the current state of "discovery" downstream:

• • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • •
• Sorry, I've dropped my bag of Doritos™ brand perfect circles • • • • •
• • • • • • • • • • • • • • • • • • • • • • • • • •• • • •• • • • • • • •

I got 12 quest points. Level up!

Here's what I'm planning to do for imports:

Design atrocity incoming for T10747.

Rough overall state of the world is that "all the hard stuff" is mostly "done" but it's probably fairly buggy, so I'm going to push on exports and some UI stuff for a bit and try to catch all those bugs while I do. Also imports are probably hard but I'm going to imagine that they aren't for now.

Yeah, agreed.

Nice idea! Also would be good to flip Description / Invitees boxes on the view page.

I think I'm going to move the recurrence controls to a separate screen, so you'll make a recurring event in two parts:

You can today, just extend PhabricatorGuideModule and drop it in src/extensions. It should just show up.

Maybe it might be a good idea to allow people to create own Guides? Could be helpful for recuring setup stuff for newusers for example, like we got it at our instance.

Though I guess a "fake" dashboard is not as performant as actual dashboards. But equivalent to current hardcoded homepage?

Yeah, I think scope-wise this could get out of hand quickly and consume a month on both design and engineering. I think I can propose something here that will not take your time and maybe 1-2 days of mine.

I think we're on fairly firm technical footing on some specific changes, which I can probably lay the groundwork for and hand off to you to populate:

I have 7 panels for new Phacility Admin, trying to think of one last action panel..... .... .... memes?!? Good idea or great idea?

It's not 100% reliable but we can use that to make a pretty good guess.

We know if someone has set up arcanist, correct? They ran arc install-certificate?

In the general (Phabricator, rather than Phacility) case we could also suppress that warning while "NUX Mode" is active, for whatever "NUX Mode" means. Presumably, it's not important to fix until you get through whatever NUX flow we end up with. This would indirectly reduce the annoyance for Phacility instances, although sync is still better.

I'll file something just to keep separate.

We definitely should sync it, and probably at least some other stuff, like language and pronoun, which may not be relevant now but is likely to be relevant in the future.

So first thing I notice when starting a new test instance... Phabricator wants to set my Timezone, so OK fine, click save, get redirected to settings. Is there any means of pre-populating that before the user first logs in from admin maybe?

But if you can easily work around, great!

It's a one time cost, and cheaper than a sprite, is it not?

When you think of it, it's also a waste of bandwidth to even transfer FontAwesome when I have a working copy in my system's fonts folder.

My concern is that I can't tell Firefox which fonts from which sites with which checksums it shall trust, so I block all of them and rely on my locally installed fonts.

We only serve a local trusted copy, is that your main concern?

Hopefully I can use this to repair the broken icons while still blocking foreign font files. At first I thought I had to create a custom mapping from CSS class names to Unicode characters, or even icon sprites in cases where I can't find a nice Unicode character for the meaning.