Core dna's New Content Workflow
With the release of the new content workflow, Core dna's CMS users will have access to
Improved Content Governance: Workflows allow users to define and enforce content approval processes, ensuring content goes through the necessary review steps before publishing.
Visibility and Transparency: Workflows make the content review and approval process more visible, so users can track the status of content as it moves through the different stages.
Collaboration and Coordination: Workflows facilitate better collaboration between content creators, reviewers, and approvers by routing content through the appropriate steps.
Version Control and Auditing: Workflows create a documented history of content changes and approvals, allowing for better version control and auditing.
What is the impact of content workflow on content creation?
Streamlined Content Editing: Users can create content branches and add comments to facilitate the review process, rather than relying on external communication.
Reduced Publishing Errors: Workflows help catch issues earlier in the content lifecycle, reducing the risk of publishing errors or unapproved content.
Faster Turnaround Times: Automated routing of content through the workflow can speed up the overall review and approval process.
Clearer Responsibilities: Workflows define the roles and responsibilities for each step, making it clearer who needs to take action.
Overall, the workflow capabilities provide Core dna users with more structure, visibility, and control over their content management processes - leading to improved governance, collaboration, and efficiency. The key is ensuring the workflows are intuitive and flexible enough to meet each customer's unique needs.
Release 2024.8 - Workflows, versioning, forms
With this release, we are bringing advanced workflows along with version branching to Core dna. We additionally launch the first phase of our forms improvements, allowing further customize your forms.
- Version branching
- Ever wondered what has changed in a previous content version, or when a certain change was introduced? With branches, we now give you the power to structure your content versions by grouping them together into named branches, making it much easier to navigate through previous content versions.
- Content drafts
- During content editing, our system automatically saves drafts of your progress. In the past, it was not that obvious that you were editing a draft, and this draft can potentially have been created by other editors without you noticing. Now, drafts are user specific, and you will only automatically get to see the draft of a page if you have created it. Draft ownership is also made more obvious in the version history. Additionally, we now make it much more obvious that a draft version is being edited by showing a banner at the top.
- Version updating
- In the past, content versions could only be created, but never altered after their creation. Editor would this either create a lot of versions, making them hard to navigate, or would have to stick to the draft which could be overwritten by somebody else. Now, we support updating content versions. For all content that is not shown on the page yet (as active revision), existing versions can be updated by the user that created them.
- Explicit active revisions
- Following the new possibility to update content versions, we additionally made it more obvious to users when content will be shown to visitors. The save button for versioned content now allows you to explicitly choose between different actions: You can either Save and activate a version, displaying it to visitors, or just choose Save new version to keep working on your content before making the changes visible.
Forms improvements
- Support for layout areas for forms, allowing you to add any type of content to your form, and including custom entities
- Every input field now supports custom CSS classes, further allowing you to customize the look and feel of your forms
- Possibility to re-order options of select fields through drag and drop
- Richtext editors in forms will now use the same configuration as other richtext editors, allowing you to sanitize content, use custom lists and styles and more
- Placeholders can now be specified for select fields as well
- Hidden input fields can now also be validated
- The Date/Time input fields have received an update to allow specifying a minimum and maximum date, which will get validated on form submission
Other improvements and bug fixes
- Fixed an issue with certain hooks actions being moved to the wrong position after saving
- Prevented additional updated hooks entity events being trigger on new records for certain entities
- Added additional validation to admin menu elements to prevent issues of accessing the admin panel on custom admin menu elements