Our content team often moves articles around, de-prioritizing them by setting their publication date in the past, so they appear deep in the pagination rather than on the first or second pages.
Previously when we used Wordpress, they would simply do it by setting the publication date in the past. In Dato this is unfortunately not possible.
I see this feature has been asked about at least a couple of times already:
The answer, in each case was that the publication date was a read-only object representing internal state, but that doesn’t seem to be the full picture, because you can set a publication date in the future!
As advised in the above threads, we have created an additional field per model that has a configurable datetime for publication, but that has made the UX for the content editors even more confusing. If they want to use a publication date of now or in the future, they can use the standard “publish” button, but if they want to set one in the past, they have to use this other field, further down in the model.
If Dato wants to keep immutable records of creation, publication, etc. it would be great if it did this in a separate object, and allowed the publication date that is used by the big, main “publish” button to be set in the past as well as the future, and bring it in line with other CMS publication functionality.
I feel this would not only greatly improve the experience migrating from an old, established Wordpress site, but also fulfil an expected publishing behavior in the editor.