Feature Requests
Complete

Content editor

Currently, there is no option to edit the generated content, which sometimes requires a very small manual correction before it is sent to WordPress or passed further along.

A content editor feature would be useful, as it would allow users to make these small changes, such as content corrections, adding links, or adding an image.

Points I would pay attention to:

Should the content editor be available at all times, or only until the content is "sent" to WordPress?

If the client approves the content, should the content editor still remain available?

These are logistical topics worth considering, but I think the best solution would be for the content editor to remain available at all times.

I would also consider the option of uploading images to the client's WordPress, so they are not hotlinked. As long as the image is hosted on our CDN, that is fine, but when we add an image from a local drive or another location, it should be uploaded to the client's website.

The simplest approach would be to upload all images, unless the URL comes from the client's domain. In that case, we should not upload it again in order to avoid duplicates.

Once again, why this content editor is needed:

After content is generated, it is often proofread. Internal linking, brand voice, content quality, and other elements are checked. When the content requires corrections, it is moved to Google Docs. Having an editor in this tool would eliminate the need for Google Docs, allow corrections to be made directly in the tool, and shorten the path from production to publication.

Also:
Since a content approval system for clients is planned, this editor could also be useful in that context, especially if the requested changes require human input and cannot be handled by the agent.

4 Comments

Sign in to comment

Rad PaluszakPinned·about 1 month ago

This is now live 👏

Posting anonymously

Rad Paluszak·about 1 month ago

Content editor is 100% a part of the planned approval system.

The simplest approach would be to upload all images, unless the URL comes from the client's domain. In that case, we should not upload it again in order to avoid duplicates.

The editor will only allow you to insert images via link, so if you want the image to be from the client's WordPress (or other CMS) library, you'll have to upload it there first. We do not foresee any image upload functionality at this time.

Should the content editor be available at all times, or only until the content is "sent" to WordPress?
No, the editor will no longer be available. You can edit the content in WordPress directly.

If the client approves the content, should the content editor still remain available?
No, in this case, also, the editor is going to disappear. Once approved, the content is read-only.

We're planning to have an option to see the content version as generated by Zeni and then the version as saved and edited by the user. Meaning, you have the very first text from Zeni and the very last saved in the editor for comparison. At this time we're not planning to include any other version or snapshot control.

Posting anonymously

Kiler·about 2 months ago

For WordPress, I would also consider supporting shortcodes. If we add [custom_shortcode] in the editor, will it be handled correctly after publishing or sending the content to WordPress?

Posting anonymously

Rad Paluszak·about 1 month ago

If you're going to use shortcodes in the editor, after publishing to WordPress, the CMS will handle them in a standard way:
1. If the shortcode exists, it's going to be processed automatically by WordPress
2. If the shortcode does not exist, it will be displayed verbatim.

It's not really something we can control with Zeni, it's the standard WordPress behaviour.

Posting anonymously