Why is this important or useful?

Its come up in two cases:
(a) I want to have a template page per team or group that users shouldn't edit, but should be able to copy to make their own
(b) someone else made something interesting and complicated such using using dot {{{}}} and I want to see how they did so to be able to make something else.

the example above uses logged out users, but the same would apply to logged in users who just couldn't edit that specific page.

This isn't a good fit in the upstream for me.

a) Should be solved by your install. You can either provide the template in the text of the document or just leave it editable if they really really need the source. Is it being abused that much? You could even link to an editable copy that people can use if it must be pristine.

b) This is a theoretical use case, and one I don't think needs solved. Public installs with dot installed and you can't login to seems exceedingly edge case. Remarkup in general isn't particularly difficult to learn and is reasonably documented.

Adding Actions for me is as slippery a slope as adding config options. They just cost a lot to build/maintain/document/design, as well as reduce the overall effectiveness of a menu and increase the clutter of options around the site. Basically they make Phabricator harder to understand, so the benefit needs to be significant.

@chad I won't object to closing as Wontfix but to be clear: this use case is not limited to public installs or nor to installs with dot installed. I was just giving an example of a 'complicated' remarkup example.

This is why we ask people to file tasks about the problems they are having with Phabricator. This task focuses on a feature thats wanted, and then defended with reasons instead of allowing us to discern the core issue and group with similar needs.

This consumes developer time, in that we have to provide reasoned responses why that feature isn't a fit instead of just saying 'hey, these other users need a similar feature here, let's add your use case'.