9. Workflows and documentation operations
The Editorial Workflow and Content Integrity project summarizes the problem. The sections here retain the review path, stale-editor scenario, proposed safeguards, and reporting context behind it.
9.1 Editorial ownership in Umbraco
In May 2026, I reviewed initial Umbraco workflow requirements and reframed them into two clearer scenarios: content authored by a Technical Writer/Senior Technical Writer, and content authored by an approved Technical Support agent. My version distinguished formal reviewers from general commenters and clarified drafting, SME validation, peer review, ownership, permissions, and publication to dev.
The workflow was forwarded as the current documentation-production workflow to be replicated in the Umbraco Workflow plugin. Production publication remained a separate Web-team responsibility. That boundary matters: publication to dev within the editorial workflow is not the same as authority to deploy the production website.
9.2 Stale editor overwrite prevention
Testing in June exposed a content-integrity problem involving two writers opening the same topic. One could enter Workflow Drafting while the other retained an older browser copy, creating a possible later overwrite. I documented the scenario and proposed a claim/unclaim safeguard independent of workflow stages.
I proposed safeguards covering editorial ownership, save-time checks on the server, workflow integration, and permissions for overriding or reassigning a lock. A server-side check would address stale browser sessions before they could overwrite newer changes.
After discussing the behavior with the Web team, I submitted a workflow-plugin bug report describing the overwrite risk and the proposed save-time safeguards.
9.3 Process documentation and communication
My contributions span the writing process: scoping requests, checking product facts, documenting release-note procedures, recording migration problems, and clarifying editorial ownership.
I explored clearer documentation-status notifications for Product Managers who were missing updates among other Jira messages. I proposed a Power Automate approach and discussed its suitability with IT.
9.4 Reporting and measurement
I generate and analyze monthly departmental metrics to support workload tracking and process improvement. I also worked on a knowledge-article reporting page that connects support cases with article attachments and identified enhancements for further review before publication.
I checked issue labels and release queues to improve reporting consistency, and analyzed repository activity to understand documentation changes and review patterns.