It can't hurt to have a mock available, but it's unlikely that I can implement logos for merchants in less than an hour (because of T6670, this may actually be a day or more of work).

I promise to keep the design to under an hour's work. Mostly, I don't want them looking like "Phabricator" emails, and just a plain logo, address, and table.

We can make these look different from other transactional email (but still general to Phortune) with a moderate amount of time, work, and ongoing maintenance cost.

Can these be one offs (HTML) or do you see them going through the normal pipeline. Basically, how much freedom do I have. I'm not looking for fancy, just need to know if I can fork from normal HTML.

For reference, here's what they look like today:

I actually have some design studies on this in general, so it has begun on the explorative side of the house.

• Users can disable instances, which is the same thing as canceling a subscription from a user perspective.
• All this other stuff we don't care about for a long time.

This is resolved for Phacility because we disabled Dashboards.

We should probably also disable the dashboards application on Phacility since the plan is for Instances to replace it anyway (T7143).

Very true ;)

I didn't close it. ;-)

Yea, I asked Evan in IRC if he wanted reports on it and he said yes.

Phortune is a prototype application. https://secure.phabricator.com/book/phabricator/article/prototypes/

This happens on Phortune Orders and Subscriptions as well.

I'm going to push this further out now since I believe we have all the must-have launch features. Notable core feature omissions:

We've successfully processed payments with Phortune so I think the era of this task has drawn to a close. I'll file more narrow stuff for future development.

Specifically, projects can be added via hashtags (#) for Remarkup purposes.

Closed by commit rPed0b23cb4d41.