As suggested by one Pro user, a more minimally viable solution would be to include a "Reply-To" header with an email that the author chooses. If they fill out this field, replies will go there; otherwise they'll go nowhere as they do today. I think we'll go that route first.

Working on this now. Some implementation details thus far:

Docs are updated and WF pull request is open: #436.

This is already supported on Write.as and the Go API library, added in the attached commits. Will add it to WriteFreely and our API docs next.

So far, unfortunately we've only localized reader-facing UI elements (email subscription form, "Read more" links, etc.). Would definitely like to localize the editing UI as well in the future! Thanks for sharing that tool, I haven't heard of it.

No this task actually refers to more granular permissions just for Write.as (versus Submit.as).

There will be a toolbar button in the WYSIWYG editor to add an image, which will let editors paste in the Snap.as image URL. We may need to make this easier, like by just showing the image URL in Snap.as instead of the full Markdown. Will investigate that.

iOS app was released on October 20, 2020.

We should provide a dedicated space for editing navigation items.

@heyakyra In the short term, unfortunately uploads still happen in a separate place (Snap.as). But we'll work toward adding uploads into this editor!