Hello,
I have recently started using typolight and quite pleased by the way the application addresses common features such as user's UI custmisation, templates and plug-ins management, etc.. It is meeting 99% of my needs.
However, there is 1 thing that I think anyone can expect from a CMS: publishing workflow.
All the changes you currently make on the site go live as soon as you save the page. If you change the type of the article through the dropdown, it submit the changes automatically, and publish the page without even having to save the page.
This makes it challenging to sell to clients who need to make regular changes to the site, but would obviosuly need to preview the changes before pushing them live. And when there is more than one person responsible for the site, they would also like the ability to set up 2 types of profiles:
- the copy writer: can carry out changes to pages, but cannot publish them (only save them to make them available for preview)
- the publisher: responsible for reviewing the changes, and publish them live.
I am not sure this logic can be "plugged in" as such, and I would think that this is rather a core development.
Searching for "workflow" didn't return any result. Is any work related to this type of features has been considered yet?
Note: the change we are considering as a workaround at the moment is to use a "staging site" on which typolight is sitting. And create a plug-in which would simply copy the staging database onto the live database.
=> changes carried out in typolight only impact the staging site.
Not very clean though, as synch between staging and live needs to be carried out carefully:
1) We need to install typolight twice (staging + live)
2) We need to be careful not copying data created by users (example contact form submitted through the site and stored in the database) from staging to live
3) We need to also transfer/delete any files such as images uploaded/delete on staging..
4) etc..
So before planning starting developing the "publish" plug-in, would be interested to check that such a core feature is not likely to be release within the next weeks or so..
Emmanuel
Bookmarks