(That was my attempt at a different, less eye staring into your soul, logo).

That isn't the logo we're planning to use. We haven't settled on a final logo (we had external designers come up with new ideas). Still testing stuff locally.

(Though I really like the sidebar menu with projects / repositories / create new)

FYI the logo in the design / mock doesn't really look like an eye - it makes me think of a gear not an eye with a gear.

There isn't a wordmark in the redesign, it will just be a text hyperlink (which you can customize).

For the very little it is worth, my coworkers consistently refer to our instance as Phab, matching the subdomain we gave it, and currently have a mark like

I think you're free to fiddle -- there are some more adjustments and things, but nothing too significant. I think the only other really CSS-ish thing is that if you search for events in a specific range (July 5-7) on a calendar view, I'd like to make it clear which days your query covers.

land what you got and I can start fiddling? or did you have more?

In T11034#186209, @epriestley wrote:

The dialog can be resized by dragging the lower right corner.

What about show only active projects in "Browse projects" window?

Hello! What about show only active projects in "Browse projects" window?

We've just been inching our way through this bit-by-bit to address specific use cases and improvements. That approach seems to be working pretty well and we have no plans to turn the whole mail into some fancy graphic thing, so I don't anticipate doing a specific whole-mail HTML redesign. We'll continue making improvements to specific sections.

I spent pretty much the whole afternoon yesterday getting "All Day" events working properly without getting a result I was happy with (some of this was untangling date controls, which will probably come upstream eventually).

I'll have my laptop with me next week, should be easy for me to clean up CSS stuff on the road.

Visually, I have a hard time picking out the current day/week.

Use of link color to convey state is weird?

I'll CSS in the event details later, but wanted this to go full width if possible.

My test data is pretty sketchy:

got a full screenshot?

Ah, fair enough. Two options it is, then.

I would want to on admin.phacility.com

I poked at it a little bit but only got this far:

We can just replace ui.custom-header with two separate options I guess and put deprecation guidance in the old option.

I'll get you an update month view here this afternoon, I've been mulling it over.

@epriestley I think my rough plan here is:

After D16226, panels no longer support tagging.

Upshot: I think renderValue($string) on ModularTransactionType is totally reasonable. We can fiddle with how it looks later.

make it blink

I think it's generally reasonable to show values with style instead of quotes in the web UI, although maybe a style other than bold would be best.

Projects are PHUIHandleView, so we could theoretically teach the handle to render them with tags.

There was a longer discussion in enriching timelines in D15442.

I'd like these to be extendable actually, and not just dark links. So for instance, if you tag a project, we could render the actual project tag:

Tagged this with Design, because this is mostly UI question...

You are right, it does not specifically describe or refer to an import button anywhere.

Okay, but the docs don't actually describe or refer to an import button anywhere -- there's no text like "click the import button" that I missed when updating things?

In T11278#184475, @epriestley wrote:

Another issue is that when following the user docs, the docs still points towards having the import button on the creation of project.

I can't find where we say this in the documentation. Can you point me at what you're seeing?

Another issue is that when following the user docs, the docs still points towards having the import button on the creation of project.

I'm leaning toward just adding a big "Clippy" element to this UI:

I think if you haven't activated the repository and visit URIs, we can show an "Import" type note and call it a day for now.

Yeah, I think it goes away after you push "activate"

Is that text already present and I just missed it?

We can probably start with a text hint on this view:

Another issue is that when following the user docs, the docs still points towards having the import button on the creation of project. I was pretty confused as it clearly wasn't that. Perhaps the page after clicking the 'Create Repository' could have an option of importing, which presets the values to observe a repo.

I was confused at first - from previous workflow I thought I took a wrong step when setting up the repository and landed on a "completed" repository page which I didn't expect without selecting host vs. mirror. I deleted the repository and started again and finally got it after hours of turmoil (maybe more like a minute of prodding).

yeah doesn't import ssh from what I see and they just say to use the command-line importer if you can't use the web tool

Here's what I see -- step 1:

I get this screen:

GitHub's import doesn't seem to work with any repositories that require credentials?

Oh, I was looking at this:

GitHub make this reasonably obvious.

People keep getting stuck on this, so we should look at fixing the UI so we don't have to post the documentation over and over.

The UI stuff seems to be figured out so I'm going to call this done this continue work in T4788.