Copytext of Stories, News, Events mentioning dates in the future is not properly transformed after the event date. How to improve the workflows.

[acsr]

Reading stories while the wording is not matchiung the actual current state is not only confusing but also not nice to suggest professional content management.

Take the view of the reader and of a search engine. If you cannot trust if the text you read is actually true, you maybe are not trusting the other facts as well.

Solutions

1. Manually edit pages after the event (cumbersome)
2. Prepare 3 versions: in advance of the event, during the event, after the event and set publication state and publishing date accordingly. Caveeat: make sure to have proper redirections of the orginal URL to the followup pages. or edit the short URL by hand.

If you are using versions, you can prepare the later versions and save them as working copies and then restore to the initial version, while keeping the others. Then restoring the upcoming versions under the same URL can be done by a non editor/author but a site manager.

[acsr]

I updated today the text of the pages mentioning the Beethoven Sprint 2024 accordingly. But addeed no significant further facts. I would suggest to activate working copy support to make editing in multiple steps more errorprone in a team. Need to lookup the current state of the install.

I can confirm that Versioning is activated on regular pages and working. Working Copy Support package is available for install but is not installed yet.

Versioning / History is hidden under the ellipsis "more" icon "…" under the edit pencil when not in editing mode.
Instead of the workflow state change, an option to add a "change note" for content changes save is not obvious for me in the current Volto VLT UI.

Using proper "change note" is like proper git commit messages especially useful for editing in a team to get the purpose of changes, if you are not the only author. We should act more professional here.

Statements on this welcome here. Should be then distributet to new tickets if we change something in the setup.

[tisto]

@acsr Albert had a more prominent place in mind for the changelog entry. However, we never implemented what was specified in Pastanaga UI. Feel free to create an issue in Volto putting this on the table. I agree with you that this is a feature that we should have.

[acsr]

@tisto wrote:

@acsr Albert had a more prominent place in mind for the changelog entry
I completely agree.
I agree with you that this is a feature that we should have.
@tisto We have it! Its just hidden by CSS without need.

The ChangeNote feature is crucial for the CMS workflow on the client side, if you want to seriously keep track of changes.

Developers may miss this, but it also puts a strange light on those who never missed to recognize this. Therefore a more prominent place of the ChangeNote Input is a strong feature. But no input is even worse.
Even forcing a ChangeNote or a default option to choose "minor edit", "typo", "same as before, continued session" would be good as a policy for organisations and their editors teams to increase quality.

General Volto issue?

I already wrote a ticket in Plone.de solely on this issue but limited to Plone.de and VLT.
#66
I needed further research to figure out where the screws are: VLT or Volto
@tisto can you confirm this is a general Volto issue?

The Prominent place for me would be to pop up the input form for the note when you are on the save action. Yes it maybe is one hop more, but can lead to more productivity at the end.

Creating a changeNote suggestion from the changes Diff as an AI assistant

This is by the way one of the most useful usecases where an AI assistant can suggest a commit message or summary of the changes. Ebven as postprocessing this could improve editors workflows and even for users tracking changes as well.

[tisto]

@acsr I can confirm that this is a Plone core / Volto issue.