Would this be helpful to leverage?

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.

Dropping for future reference, in case you ever want to drop PHP dependencies 😀

• https://plausible.io/
• https://usefathom.com/

Ah cool no worries. Yes Project Fluent is great, we've started using it where I work. It addresses the shortcomings of GNU Gettext (you can actually have variations of the same translation when different languages don't have a one-to-one conversion for some phrases) and Mozilla has also created a nice web app to collaborate on translations: https://github.com/mozilla/pontoon/

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.

Is the write.as web UI available in other languages (maybe through https://projectfluent.org/)? It isn't an short-term need, but may be nice to have some day for editors who's first language is Spanish. I didn't see a setting in my account preferences, but maybe it's somewhere else

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

Does the lack of this mean that all users of Write.as Teams are effectively admins? Not a blocker, just checking

We should provide a dedicated space for editing navigation items.

@heyakyra This is addressed in T812. Basically, that'll be possible with a new custom template system.

This is improved and superseded by T810: Blog post management section.

A long-time Pro user just asked if there's a way to do this.