This is live on Write.as and merged into WriteFreely for the v0.13 release.

Taking this; related to existing work to eliminate references to "static pages" in user-facing docs, etc., in favor of "pinned pages". I should have something to show for this (in terms of changes) next week.

Will finish this up and get it merged. Because of how widely this feature is needed, I think we can get it in without the fediverse deletion functionality for now.

One issue: images aren't automatically resized, as they are when uploaded through Snap.as. Instead of doing client-side image resizing here, we should rely on the server: {T851}.

This is live on Write.as now (Classic editor v2)

Currently, this only uploads to a user's personal Snap.as storage space -- which likely isn't the desired behavior for users writing a post on a team / Organizations blog.

That last issue is fixed and deployed on Write.as. Final WriteFreely pull request: #356

WriteFreely PR #444.

WriteFreely PR: #442

@heyakyra This task has a broader scope / works on a higher level, for managing all users on a WriteFreely instance. We can address Team suspensions in another task.

This is deployed on Write.as, and will be in the next version of WriteFreely (see #439)!

Would this be helpful to leverage?

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.

Is Write.as served by Nginx, Apache, or something like that? I noticed that testmysite.io reports that HTTP2 is not enabled, but should be a one-line fix in Nginx config or there's the more bleeding-edge approach https://h2o.examp1e.net/ 😉

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

Awesome, that sounds easy enough then. Thank you!

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.

We should provide a dedicated space for editing navigation items.

No problem, we can teach editors to adapt in the meantime! Combined with T520, will there at least be a way to copy image embeds from Snap.as into the WYSIWYG editor without having to copy markdown and switch to markdown mode (assuming that will still be an option)?

@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!

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