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.

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!

Will this make it possible to upload and caption photos from the same place as posts are written?

Found a resource for adding the CMD + K binding for adding links: https://discuss.prosemirror.net/t/binding-command-k-to-open-insert-link-prompt/1354

I'm going to try to wrap this up.

Looking into this today

This will be supported as an alternative WriteFreely editor -- see T727: WYSIWYG Editor.

To add to this list:

sub task status:

This is looking really good so far! Have been using it myself lately and it's been great.

Noting here re: icons

progress so far

As mentioned in this forum post, we should start with a browser extension.

In the interim, this will be an extension

On mobile the split should be horizontal, with the preview up top. It should also scroll with the editor content.

Idea 2:

This hasn't been an issue, but would make the web app consistent with the mobile apps.

Maybe this should be more of a "preview" button, instead.

In T234#6480, @matt wrote:

Growing Paste.as isn't in line with our current larger vision for our products anymore, especially for becoming financially sustainable. Creating a Tor hidden pastebin service isn't where we want to go or spend our time.

This was feedback from only one person (when I created this task), but we haven't heard of anyone else having this problem. So closing for now.

This doesn't match the product vision and would add unnecessary complexity. Might be better for another product.

For some of the same reasons we need {T360}, we should have offline support. The same user that requested T360 lives in New Zealand where internet is "slow and expensive." Our native clients support offline usage, and since this would be a really nice differentiator that fits in line with our product goals, we should support this soon.

Came across this video; after traveling to Europe and not having documents written on Write.as available on the plane, thinking again this would be hugely useful.

See the MDN article on it, or a tutorial from Google.

Actually occurs before publishing. But this is finished.

As we're moving towards accounts and this is a relatively technical task, I think we'll leave it to the CLI and revisit again in the future if this service-level privacy becomes important.

Should also enable switching between light and dark mode.

Would be cool, but might be too much. In the meantime, users can write raw markdown for formatting with T207: Support Markdown