In T9360#146722, @chad wrote:

DocumentPro is way better than Oblivious

For Home I expect 90%-98% of people to not be blog post authors, so visiting /phame/ would be best served getting content to them from whatever Blogs they want to follow. I am partial to providing to quicker access to posting new posts though, so I want to think about that some more (and EditEngine might be the actual answer).

DocumentPro is way better than Oblivious

Yeah, let me dig into that a bit and come up with some options. I have to go look at what the skin code is doing.

Oblivious skin is terrible and we should just get rid of it. The internal skin is a million times better.

I don't think it costs us very much to keep it around, and it does make some stuff nicer/easier. For example, we'd have no way to link to the live blog or live post if we don't know what domain it's on, and I like checking the live post after publishing something.

Do you see any point to doing "Custom Domain" stuff? That is, with EditEngine and Conduit, should that use case just be on the end user?

Some thoughts from banging on this, not sure how much you want to deal with:

I think this is done enough.

Yeah, consistency and like "attacker gets into your account and deletes all your stuff and it's gone forever and you are so very sad" and such.

Any reason to remove the delete functionality then? Just for app consistency?

We could probably just do unpublished for now and wait until we have a stronger use case for a real "archive".

How should archiving posts work? Or is hidden/unpublished enough?

Yep, it was the Apache restart. Sorry for poor testing, thanks for fixing the incidentally discovered bug, and hopefully the other part of my comment was less useless :)

I did find D14574 in testing this, so there was at least 1 bug.

These errors point to being behind HEAD and/or not restarting Apache/PHP-FPM. rP2a063a for example resolved the constant issue.

master as of yesterday (Tue) approx. 2 pm PST. When I get home I'll check if the logs match up, but I took care to pull all three repos and ran a storage upgrade.

Are you at HEAD?

Not opening another bug report since Phame is not out of beta yet, but I thought I should still let you know that I stumbled upon an exception yesterday after updating from before the comments revamp:

• When viewing a Blog page (not a post itself): (Unable to resolve method 'isArchived'.)
• When submitting a New Blog form: >>> UNRECOVERABLE FATAL ERROR <<< Undefined class constant &#039;TYPE_STATUS&#039;

Phame should be "mostly reasonable" to test as an internal blog platform. There is more polish to come, but feel free to send feedback along here.

Works for me!

There won't be any configuration for comments.

For reference, I think this is an excellent plan and I'm stoked to see internal comments being considered. (If I already have to get my users to sign up for a Phabricator account, it's good if they don't have to also log into Disqus.)

I'll yank it in one diff, so it's easy to resurrect.

I could see some future where you maybe want a split blog view (employees can comment privately, public comments publicly), but it's also hard for me to envision large corporation trusting Phabricator over Wordpress is they have super serious needs.

Yeah, I'm onboard with that plan.

My plan is to get all the "clean up" done, then re-design the landing page and the blog page. It's definitely not easy to get around or discover anything.

Maybe there can be a way to enable it as a menu item, but being disabled by default. Your call! Thanks for getting back to me despite the beta label (forgot that you don't take bug reports / features on it yet).

Only the most common actions are there, otherwise we'd have over 50 items. Personal customization offers better flexibility to individual workflows.

In our community, for regular members (not involved in board/admin tasks), I expect it to be the one most commonly used action (the other common action being commenting on other people's posts). Either way, I can work with providing a separate link in a dashboard box. However, for a global menu I would find it confusing to not find "Create" actions in the "Create New" menu.

How often do you expect everyone to write a blog post? Mostly this will just clutter the quick create menu. We expect T8994 to cover these edge cases.

https://secure.phabricator.com/book/phabricator/article/prototypes/

https://secure.phabricator.com/book/phabricator/article/prototypes/