Content Editor for the front-end

[AGaiki]

I think that a useful feature, especially if Retype is being used in a setting where content needs to be edited continuously, would be for the end-user to be able to add articles and edit existing articles from the website itself. With that being said, are there plans for ways to authenticate users, thus limiting access to who can access the site?

[AndreyChechel]

Hi @AGaiki

Yes, there're certainly plans for supporting content editing - this feature is being worked on for a while already. We feel that content editing brings user experience on the next level, so Retype will become even more user-friendly and will help to focus on content editing rather on technical stuff.

We're doing our best to deliver it as soon as possible and I hope it'll be rolled out in one of the upcoming releases.

As for user authentication - that'd require repurpose of the Retype Server used in retype watch workflow to become a production-ready server, whereas currently it's meant to be used for content development only. This is something we'd love to work on, but because of a lot of other features being in progress, it has lower priority for now.

[geoffreymcgill]

Our first goal is implement a feature within the page for content creators to edit the page content without leaving the context of the page. For instance, not having to use a secondary text editor such as VS Code.

This initial functionality will still require running retype watch locally and will not be an online service, but we plan on exploring Retype as a service as well.