Workflows  [[3. Resources/Readwise/Full Document Contents/Articles/Workflows|Full Document Contents]] ## Document Notes --- tags: - #wordpress - #gutenberg - #workflows Author: Make WordPress Core Source: Make WordPress (Core blog) Reference: https://make.wordpress.org/core/2023/07/04/workflows/ date created: 2025-08-22 00:00 --- # Title: WordPress Phase 3 Workflows: Collaboration, Review, and Publishing Flow ## Table of Contents: - [[#🧭 Introduction]] - [[#🎯 Scope Overview]] - [[#💬 Inline Comments & Review States]] - [[#🧩 Tasks in the Publish Flow]] - [[#🔗 Sharing Drafts, Previews, and Design Changes]] - [[#🧱 Extension Points for In‑App Previews]] - [[#🗂️ Multi-Entity Saving, Scheduling, and Snapshots]] - [[#🔧 Version Control Hook Points]] - [[#🔐 Granular Permissions for Patterns & Templates]] - [[#👥 Multi-Author Representation]] - [[#🤝 Get Involved]] - [[#📝 Summary:]] - [[#📖 Main Content:]] - [[#🗒️ Notes]] - [[#📖 References]] - [[#🗣️ Paraphrase]] - [[#📰 Newsletter]] - [[#✅ Action Items]] - [[#🧪 Hypotheses]] - [[#📊 Methodology]] - [[#❓ Questions]] - [[#🔮 Future Research]] - [[#💡 Implications]] - [[#🧠 Learning Styles Assessment]] - [[#📊 Accessibility Assessment]] - [[#🌍 DEIB Assessment]] - [[#✅ Logical validity]] - [[#🔍 DARVO Analysis]] - [[#🔍 SEO Evaluation]] - [[#🎯 Conclusion]] ### References: Include a list of sources consulted and cited in the article. - Make WordPress Core: Workflows — https://make.wordpress.org/core/2023/07/04/workflows/ ## 🧭 Introduction “Provide seamless collaboration during the entire editorial process, from draft to publication. Allow users to add comments, suggest edits, and tag other users for peer review. Ensure the interface remains focused on a smooth experience for writers and editors.” (0%) The article outlines goals for Phase 3 workflows in WordPress, focusing on collaborative editing, structured review, permissions, previews, revisions clarity, and support from solo creators to large editorial teams. It also notes the importance of workflows for both unpublished and already-published content. (0%) ## 🎯 Scope Overview “This is a summary of the broad tasks we need to look into:” (25%) - Inline block comments with resolution states and tie-ins to revisions and “pending review.” - “Tasks” integrated into publish flow to block or guide publication readiness. - Shareable draft links with permission controls and revision browsing; extend to Site Editor design changes. - Extension points for in‑app previews so plugins can render role-based or context-based versions. (25%) ## 💬 Inline Comments & Review States - Introduce inline comments on blocks. - Use comment types; allow resolved/unresolved states. - Comment status folds within revisions so comments map to specific edit states. - Connect with “pending review” to gate publication. (25%) ## 🧩 Tasks in the Publish Flow - Add configurable “tasks” to highlight missing actions (e.g., word count, empty media, fields). - Attach tasks to statuses like “pending review,” including for already-published content. - Extensible by plugins and applicable beyond posts (e.g., WooCommerce order fulfillment). (25%) ## 🔗 Sharing Drafts, Previews, and Design Changes - Share draft links with permissions and clear revision browsing. - Extend previewing and sharing to Site Editor design changes across styles, templates, patterns. (25%) ## 🧱 Extension Points for In‑App Previews - Provide hooks so plugins can show variants: subscriber vs. non-subscriber, with/without ads, RSS vs. email rendering, etc. - Unified mechanics across editors for seamless integration. (25%) ## 🗂️ Multi-Entity Saving, Scheduling, and Snapshots - Improve multi-entity saving to schedule design changes across styles, templates, patterns, pages, and posts. - Possibly name future revisions to orchestrate site-wide changes. - Provide preview snapshots before going live. (50%) ## 🔧 Version Control Hook Points - Explore hook points allowing external VCS to take over internal revisions when desired. (50%) ## 🔐 Granular Permissions for Patterns & Templates - Control at a granular level rather than blanket locks. - Example: lock patterns to “content only” for authors while leaving full control for admins. (50%) ## 👥 Multi-Author Representation - Consider multi-author support on posts or improve representation via real-time collaboration and revision authorship. (50%) ## 🤝 Get Involved “There’s been a lot of interest… Let’s capture and highlight feedback to ensure all use cases are represented.” (75%) ## 📝 Summary: The article proposes Phase 3 workflow enhancements to make WordPress a first-class collaborative CMS. Core themes: inline block-level comments tied to revisions; task-based publish gating; shareable, permissioned previews for content and design; plugin extension points for context-aware previews; robust multi-entity scheduling and named future revisions; optional VCS integration; granular permissions at the pattern/template level; and better multi-author representation. The initiative aims to support everyone from solo creators to complex editorial teams and invites community participation. ## 📖 Main Content: The roadmap emphasizes end-to-end editorial collaboration: - Comments become first-class citizens at the block level, with resolution states persisted per revision state for historical clarity. This means reviewers can contextualize feedback against specific edits and authors can manage feedback lifecycles. - Tasks in the publish flow function like guardrails and checklists. They can block publication until criteria are met (e.g., empty media placeholders filled, min/max word counts, required fields). Because tasks are status-aware and extensible, plugins can introduce domain-specific checks (e.g., compliance, accessibility, eCommerce readiness). - Sharing is broadened beyond posts to site-wide design artifacts. Permissioned links allow stakeholders to preview and comment on both content and design changes without full access. - Extension points enable side-by-side experiences: subscriber vs. public views, ad vs. ad-free, or rendering modes like RSS/email to support editorial QA across channels. - Multi-entity saving and scheduling unify rollouts across styles, templates, patterns, posts, and pages—critical for coordinating campaigns or seasonal redesigns. Named future revisions and preview snapshots support change management and approvals. - Hook points for version control pave the way for Git-based workflows to optionally supersede WordPress revisions—attractive for engineering-heavy teams. - Granular permissions replace blunt locking, allowing authors to edit content within patterns while preserving design integrity for administrators. - Multi-author representation acknowledges complex authorship and real-time collaboration, clarifying who did what and when. - The post closes by inviting community feedback and contributions. ### 🗒️ Notes - Collaboration goals (0%): - Seamless draft-to-publication collaboration. - Add comments, suggest edits, tag users. - Keep UI writer/editor friendly. - Review and gating (0%/25%): - Tasks/checklists prevent premature publishing. - Handle placeholders, word count, required fields. - Apply to unpublished and published content. - Inline block comments (25%): - Use comment types. - Resolved state tracking. - Comments tied to specific revisions. - Integrate with “pending review.” - Sharing and previews (25%): - Permissioned draft links. - Revision browsing clarity. - Extend to Site Editor design changes. - In‑app preview extensions (25%): - Role/context-based renders (subscribers, ads, RSS/email). - Unified hooks for plugin integration. - Multi-entity scheduling (50%): > [!note]+ Document Notes > tags: > - #wordpress > - #gutenberg > - #workflows > Author: Make WordPress Core > Source: Make WordPress (Core blog) > Reference: https://make.wordpress.org/core/2023/07/04/workflows/ > date created: 2025-08-22 00:00 > > # Title: WordPress Phase 3 Workflows: Collaboration, Review, and Publishing Flow > <!-- deep-read:sections start --> ## Table of Contents: - [🧭 Introduction](#-introduction) - [🎯 Scope Overview](#-scope-overview) - [💬 Inline Comments & Review States](#-inline-comments--review-states) - [🧩 Tasks in the Publish Flow](#-tasks-in-the-publish-flow) - [🔗 Sharing Drafts, Previews, and Design Changes](#-sharing-drafts-previews-and-design-changes) - [🧱 Extension Points for In‑App Previews](#-extension-points-for-in-app-previews) - [🗂️ Multi-Entity Saving, Scheduling, and Snapshots](#-multi-entity-saving-scheduling-and-snapshots) - [🔧 Version Control Hook Points](#-version-control-hook-points) - [🔐 Granular Permissions for Patterns & Templates](#-granular-permissions-for-patterns--templates) - [👥 Multi-Author Representation](#-multi-author-representation) - [🤝 Get Involved](#-get-involved) - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#-notes) - [📖 References](#-references) - [🗣️ Paraphrase](#-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical validity](#-logical-validity) - [🔍 DARVO Analysis](#-darvo-analysis) - [🔍 SEO Evaluation](#-seo-evaluation) - [🎯 Conclusion](#-conclusion) ### References: Include a list of sources consulted and cited in the article. - Make WordPress Core: Workflows — https://make.wordpress.org/core/2023/07/04/workflows/ ## 🧭 Introduction “Provide seamless collaboration during the entire editorial process, from draft to publication. Allow users to add comments, suggest edits, and tag other users for peer review. Ensure the interface remains focused on a smooth experience for writers and editors.” (0%) The article outlines goals for Phase 3 workflows in WordPress, focusing on collaborative editing, structured review, permissions, previews, revisions clarity, and support from solo creators to large editorial teams. It also notes the importance of workflows for both unpublished and already-published content. (0%) ## 🎯 Scope Overview “This is a summary of the broad tasks we need to look into:” (25%) - Inline block comments with resolution states and tie-ins to revisions and “pending review.” - “Tasks” integrated into publish flow to block or guide publication readiness. - Shareable draft links with permission controls and revision browsing; extend to Site Editor design changes. - Extension points for in‑app previews so plugins can render role-based or context-based versions. (25%) ## 💬 Inline Comments & Review States - Introduce inline comments on blocks. - Use comment types; allow resolved/unresolved states. - Comment status folds within revisions so comments map to specific edit states. - Connect with “pending review” to gate publication. (25%) ## 🧩 Tasks in the Publish Flow - Add configurable “tasks” to highlight missing actions (e.g., word count, empty media, fields). - Attach tasks to statuses like “pending review,” including for already-published content. - Extensible by plugins and applicable beyond posts (e.g., WooCommerce order fulfillment). (25%) ## 🔗 Sharing Drafts, Previews, and Design Changes - Share draft links with permissions and clear revision browsing. - Extend previewing and sharing to Site Editor design changes across styles, templates, patterns. (25%) ## 🧱 Extension Points for In‑App Previews - Provide hooks so plugins can show variants: subscriber vs. non-subscriber, with/without ads, RSS vs. email rendering, etc. - Unified mechanics across editors for seamless integration. (25%) ## 🗂️ Multi-Entity Saving, Scheduling, and Snapshots - Improve multi-entity saving to schedule design changes across styles, templates, patterns, pages, and posts. - Possibly name future revisions to orchestrate site-wide changes. - Provide preview snapshots before going live. (50%) ## 🔧 Version Control Hook Points - Explore hook points allowing external VCS to take over internal revisions when desired. (50%) ## 🔐 Granular Permissions for Patterns & Templates - Control at a granular level rather than blanket locks. - Example: lock patterns to “content only” for authors while leaving full control for admins. (50%) ## 👥 Multi-Author Representation - Consider multi-author support on posts or improve representation via real-time collaboration and revision authorship. (50%) ## 🤝 Get Involved “There’s been a lot of interest… Let’s capture and highlight feedback to ensure all use cases are represented.” (75%) ## 📝 Summary: The article proposes Phase 3 workflow enhancements to make WordPress a first-class collaborative CMS. Core themes: inline block-level comments tied to revisions; task-based publish gating; shareable, permissioned previews for content and design; plugin extension points for context-aware previews; robust multi-entity scheduling and named future revisions; optional VCS integration; granular permissions at the pattern/template level; and better multi-author representation. The initiative aims to support everyone from solo creators to complex editorial teams and invites community participation. ## 📖 Main Content: The roadmap emphasizes end-to-end editorial collaboration: - Comments become first-class citizens at the block level, with resolution states persisted per revision state for historical clarity. This means reviewers can contextualize feedback against specific edits and authors can manage feedback lifecycles. - Tasks in the publish flow function like guardrails and checklists. They can block publication until criteria are met (e.g., empty media placeholders filled, min/max word counts, required fields). Because tasks are status-aware and extensible, plugins can introduce domain-specific checks (e.g., compliance, accessibility, eCommerce readiness). - Sharing is broadened beyond posts to site-wide design artifacts. Permissioned links allow stakeholders to preview and comment on both content and design changes without full access. - Extension points enable side-by-side experiences: subscriber vs. public views, ad vs. ad-free, or rendering modes like RSS/email to support editorial QA across channels. - Multi-entity saving and scheduling unify rollouts across styles, templates, patterns, posts, and pages—critical for coordinating campaigns or seasonal redesigns. Named future revisions and preview snapshots support change management and approvals. - Hook points for version control pave the way for Git-based workflows to optionally supersede WordPress revisions—attractive for engineering-heavy teams. - Granular permissions replace blunt locking, allowing authors to edit content within patterns while preserving design integrity for administrators. - Multi-author representation acknowledges complex authorship and real-time collaboration, clarifying who did what and when. - The post closes by inviting community feedback and contributions. ### 🗒️ Notes - Collaboration goals (0%): - Seamless draft-to-publication collaboration. - Add comments, suggest edits, tag users. - Keep UI writer/editor friendly. - Review and gating (0%/25%): - Tasks/checklists prevent premature publishing. - Handle placeholders, word count, required fields. - Apply to unpublished and published content. - Inline block comments (25%): - Use comment types. - Resolved state tracking. - Comments tied to specific revisions. - Integrate with “pending review.” - Sharing and previews (25%): - Permissioned draft links. - Revision browsing clarity. - Extend to Site Editor design changes. - In‑app preview extensions (25%): - Role/context-based renders (subscribers, ads, RSS/email). - Unified hooks for plugin integration. - Multi-entity scheduling (50%): - Coordinate styles, templates, patterns, posts/pages. - Named future revisions; preview snapshots. - VCS hook points (50%): - Let external VCS assume revision control. - Granular permissions (50%): - Content-only locks for authors; admins retain full control. - Multi-author representation (50%): - Improve authorship display with real-time collaboration. - Community involvement (75%): - Capture broad use cases and feedback. ## 📖 References: - Make WordPress Core: Workflows — https://make.wordpress.org/core/2023/07/04/workflows/ ## 🗣️ Paraphrase: 1) Original idea (0%): “Provide seamless collaboration… add comments, suggest edits… ensure the interface remains focused…” Paraphrase: The aim is an uninterrupted editorial experience, enabling commenters, suggested changes, and user mentions, all within a writer-centric, low-friction interface. 2) Original idea (25%): “Explore introducing support for ‘tasks’ in publish flow… highlight missing actions… configurable by users and extensible by plugins.” Paraphrase: Introduce configurable, plugin-extendable checklists into the publishing pipeline to surface unmet requirements and, when needed, block publication until standards are met. ## 📰 Newsletter: This week in WordPress, we’re talking collaboration superpowers. Phase 3 workflows are shaping up to be a game-changer: inline block comments tied to revisions, task-based publish guardrails, permissioned draft links, and plugin-friendly preview modes (think subscriber vs. public views or ad/no-ad toggles). For site-wide orchestration, multi-entity scheduling and named future revisions promise campaign-ready rollouts and snapshot previews. Learning corner: if you’re new to web dev, this is a perfect case study in human-centered tooling—clear UX, robust permissions, and composable extension points. Community shoutouts to everyone sharing use cases and plugin prototypes—keep them coming. Plugin builders: start planning hooks for in‑app previews and task integrations; editorial teams: prepare your checklists. Read the roadmap on the Core blog in “Workflows” and share feedback so your needs land in Core. Bonus points for accessibility and DEIB-focused review criteria in your publish tasks. ## ✅ Action Items: Tailored prompt for a Developer Advocate at GoDaddy (open source/WordPress, educator, future OSPO director): - Purpose: Analyze how each article informs open-source advocacy, contributor onboarding, and sustainable community practices in WordPress. - Prompt: “Using this article, map concrete impacts on: 1) Contributor Experience: Identify features that lower barriers (e.g., inline comments, tasks, granular permissions). Describe how these support first-time and returning contributors in content and code contexts. 2) Education & Curriculum: Propose tutorials and workshops (PHP/JS/HTML/CSS/Git/GitHub) that teach implementing tasks API, preview hooks, and multi-entity scheduling. Include learning objectives, outcomes, and assessment rubrics. 3) OSPO Alignment: Explain governance and compliance benefits (VCS hook points, revision auditability, permission models). Outline policies for change management, code review, and documentation standards. 4) Sustainability & Funding: Suggest task checklists for accessibility, performance, and maintenance to reduce long-term costs; propose community funding pitches linked to these workflow improvements. 5) Transparency & Inclusivity: Define DEIB-aligned review tasks (inclusive language, alt text, caption completeness) and contributor recognition mechanisms (multi-author representation, revision authorship). 6) Advocacy Plan: Draft a talk/workshop abstract and a contributor onboarding guide that leverage these features to accelerate safe, inclusive collaboration. Deliverables: a) Teaching outline with code labs; b) Sample plugin spec adding task checks; c) Policy template for editorial workflows; d) Metrics plan for contributor engagement and content quality.” ## 🧪 Hypotheses: - H1: Integrating task-based gating reduces publish errors and post-publication edits by ≥30% for editorial teams. - H2: Inline block comments tied to revisions shorten review cycles by ≥20%. - H3: Permissioned previews increase stakeholder engagement pre-publication and reduce last-minute design/content rollbacks. - H4: Multi-entity scheduling with named future revisions improves success rate of coordinated releases and campaign timing. - H5: VCS hook points increase adoption among engineering-heavy organizations migrating to WordPress. ### 📊 Methodology: - Data sources: WordPress telemetry (opt-in), plugin logs, editorial calendars, Git/VCS commit histories, support tickets, and user surveys. - Designs: - A/B tests: teams using tasks vs. control teams without tasks. - Time-series: pre/post adoption of inline comments and previews. - Cohort analysis: solo creators vs. agencies vs. newsrooms. - Mixed methods: quantitative metrics + qualitative interviews. - Analysis: - Survival analysis for time-to-publication. - Interrupted time series for error rates. - Thematic coding of reviewer feedback. - Diff-based mapping of revision/comment alignment. ### ❓ Questions: - What minimum viable “tasks” should Core ship, and what remains plugin territory? - How will comment states map across complex revision trees or rebases? - What permissions granularity is ideal for patterns/templates without overwhelming admins? - How are preview snapshots stored, versioned, and expired? - What security model governs shareable preview links? - How will multi-author representation interact with bylines and existing co-author plugins? ### 🔮 Future Research: - UX studies on cognitive load of tasks vs. publish speed. - Heuristics for auto-generating tasks (e.g., missing alt text detection). - Schema for named future revisions and cross-entity dependency graphs. - Standardized APIs for preview contexts (email, RSS, AMP, app shells). - Best practices for Git-over-revisions and conflict resolution UI. ### 💡 Implications: - Advancing knowledge: Formalizes “content ops” within CMS UX research. - Practice: Reduces editorial risk, improves governance, and increases contributor velocity. - Policy: Encourages organizations to codify accessibility, security, and DEIB checks into publication workflows. ### 🧠 Learning Styles Assessment: - Readability level: Upper-intermediate technical (approx. Grade 10–12). - Visual (Spatial): - Present: High-level structure, mention of a mockup. - Improve: Add diagrams of workflow states, flowcharts for tasks, and UI annotated screenshots. - Aural: - Present: None. - Improve: Record an audio summary and a short podcast Q&A with Core contributors. - Verbal (Linguistic): - Present: Clear, concise goals; actionable bullets. - Improve: Add narrative examples and links to deeper docs. - Physical (Kinesthetic): - Present: None directly. - Improve: Provide sandbox exercises and step-by-step “create a task policy” labs. - Logical (Mathematical): - Present: Systematic breakdown of features and states. - Improve: Add state diagrams, checklists as formal specs, acceptance criteria. - Social (Interpersonal): - Present: Invitation to community involvement. - Improve: Link to discussion forums, calls for testing, and working groups. - Solitary (Intrapersonal): - Present: N/A. - Improve: Reflection prompts for evaluating team workflow maturity. - Naturalistic: - Present: None. - Improve: Use sustainability analogies (e.g., lifecycle stewardship of content). ### 📊 Accessibility Assessment: - Screen Reader Compatibility: - Observation: As a Core blog post, likely semantic but lacks explicit alt text detail. - Improve: Ensure all images/mockups have descriptive alt text; headings are hierarchical; landmarks present. - Keyboard Navigation: - Observation: Standard theme likely OK; interactive demos not present. - Improve: Verify focus states, skip links, and tab order in any embedded prototypes. - Contrast and Readability: - Observation: Core site generally good contrast. - Improve: Confirm WCAG AA contrast for text and interactive elements. - Text Resizing: - Observation: Likely responsive. - Improve: Test zoom up to 200% with no loss of functionality and support prefers-reduced-motion. ### 🌍 DEIB (Diversity, Equity, Inclusion, and Belonging) Assessment: - Cultural Relevance: - Present: Broad, global contributor framing. - Improve: Include examples from diverse newsrooms, NGOs, and non-English locales. - Inclusive Language: - Present: Neutral and inclusive terminology. - Improve: Glossary for terms like “multi-entity,” “patterns,” “revisions” for non-native speakers. - Neurodiversity Support: - Present: Bulleted clarity. - Improve: More headers, shorter sentences, visuals, and explicit checklists. - Representation: - Present: Not addressed explicitly. - Improve: Case studies highlighting diverse contributors and roles. - Psychological Safety: - Present: Open invitation to feedback. - Improve: Code of conduct reminder, clear moderation and inclusive engagement norms. ### ✅ Logical validity: - Tone: Professional, neutral, roadmap/requirements style. - Strong reasoning: - Causal reasoning (0%/25%): Tasks in publish flow will prevent incomplete posts from being published. Strength: Addresses a common failure mode; Suggestion: Add data or case studies. - Logical flow: Intro → Scope → Specific capability clusters → Community call (coherent progression). Suggestion: Add dependency mapping. - Balanced and nuanced views: Supports solo users and large teams; acknowledges published-content workflows. Suggestion: Provide trade-offs (complexity vs. power). - Ethical reasoning: Implicit in permissions and governance. Suggestion: Make privacy and audit trails explicit. - Potential gaps/fallacies: - Hasty generalization risk: Assuming these features fit all workflows without presenting evidence. Improve: Pilot studies with varied orgs. - Appeal to novelty risk: New features assumed better. Improve: Compare to existing plugin ecosystems and articulate migration paths. - Missing counterarguments: Overhead/complexity for small sites. Improve: Show opt-in/gradual enablement. 🔍 DARVO Analysis - Deny: No denial present; the post proposes features and invites input. - Attack: No attacks; tone is constructive. - Reverse Victim and Offender: Not applicable; no adversarial framing. - Notes: The content avoids rhetorical manipulation; it uses neutral, inclusive language and community-centered calls-to-action. ### 🔍 SEO Evaluation: - Keywords: - Likely targets: “WordPress workflows,” “Gutenberg collaboration,” “inline comments,” “publish flow tasks,” “site editor previews.” - Placement: Present in title and headers; could be strengthened in first 100 words with exact phrases. - Meta Description: - Suggestion: “Explore WordPress Phase 3 workflows: inline block comments, task-based publish checks, permissioned previews, multi-entity scheduling, and VCS hooks.” - Title Tag: - Current: “Workflows.” Improve: “WordPress Phase 3 Workflows: Collaboration, Tasks, Previews.” - Headers: - Use descriptive H2/H3s embedding keywords (e.g., “Inline Block Comments,” “Task-Based Publish Flow”). - Content Length: - Concise. For SEO depth, expand with examples, images, and links. - Internal/External Links: - Add internal links to revisions, Site Editor docs, and permission management. Add external links to Gutenberg Handbook. - URL Structure: - Good: /workflows/ is clean and short. - Image Optimization: - Ensure mockups include alt text, optimized sizes, descriptive filenames. - Mobile Optimization: - Core site is responsive; verify page speed with Lighthouse. - User Engagement: - Add CTAs: contribute to discussions, test features, link to GitHub issues or Make posts. - Schema Markup: - Use Article schema; consider HowTo/FAQ if relevant. - Social Sharing: - Ensure Open Graph/Twitter Card tags with descriptive summary and image. ## 🎯 Conclusion: The Workflows article sets a practical, extensible vision for WordPress Phase 3: granular collaboration (inline comments), rigorous readiness (tasks), safer sharing and previews, coordinated multi-entity rollouts, optional VCS alignment, nuanced permissions, and clearer authorship. It balances needs from solo creators to enterprise teams and invites broad community participation to refine implementation details. By formalizing “content ops” in Core, WordPress is poised to reduce editorial risk, improve governance, and enhance contributor experience across the ecosystem. <!-- deep-read:sections end --> ## Highlights - . Allow users to add comments, suggest edits, and tag other users for peer review. Ensure the interface remains focused on a smooth experience for writers and editors. ([View Highlight](https://read.readwise.io/read/01h5jqm5tkh9fc5pky8zwa9c0b)) - For example, an author could leave empty media blocks in a story they are writing and mark them to be completed by another team member, ensuring the post cannot be published while empty placeholders are still there. ([View Highlight](https://read.readwise.io/read/01h5jqnb0bdtf6hxgc4pp89z03)) - Make it straightforward to share different types of content, from posts to design changes, while controlling access through permissions. ([View Highlight](https://read.readwise.io/read/01h5jqnjrbfe84eysgft766b17)) - The tools and infrastructure developed need to support simpler use cases (one author sharing previews with friends for feedback) all the way to larger editorial teams, managing deadlines, handoffs, and more sophisticated review processes. Plugins should be able to take it further. ([View Highlight](https://read.readwise.io/read/01h5jqp674xkcvwds9vhdz0hwz)) - Introduce inline comments on blocks within the editor experience. Explore using comment types to store them. Allow marking comments as resolved. Status of comments also need to fold within individual revisions, so that it’s easy to see what specific edit state a comment refers to. Possible connection with “pending review” functionality. ([View Highlight](https://read.readwise.io/read/01h5jqvr1t5q77sxpe51nkg3yb)) - Explore introducing support for “tasks” in publish flow. ([View Highlight](https://read.readwise.io/read/01h5jqpsa84btphrydpa86sbnv)) - Ability to share draft links with permission controls and clear revision browsing. ([View Highlight](https://read.readwise.io/read/01h5jqq00312ft427278pmx2md)) - Introduce extension points for in-app previewing. ([View Highlight](https://read.readwise.io/read/01h5jqq6hfkexmtxd6zddqwyxj)) - Improve multi-entity saving to allow scheduling design changes on block themes that can be managed through the various revisions systems (styles, templates, patterns, pages, posts). Possibly allow naming future revisions to better manage and orchestrate changes throughout a site. Preview snapshots of a site before they go live. ([View Highlight](https://read.readwise.io/read/01h5jqqns0dkcrs7gn9d7rh9va)) - Explore hook points for version control systems to smoothly take over internal revision systems if desired. ([View Highlight](https://read.readwise.io/read/01h5jqr41srqf0q25yfs92cegg)) - Control access with granular permissions for patterns and templates rather than general locking. ([View Highlight](https://read.readwise.io/read/01h5jqqzm97nmrwd00kbdvxrjm)) - Consider multi-author support on posts or improve how it can be represented as a side effect of real-time collaboration and revision authorship. ([View Highlight](https://read.readwise.io/read/01h5jqr76f06pyx0wzm7fwcqwk)) - Note: 1) What are the main projects listed under Phase 3 in the Collaboration roadmap? 2) How will the Workflows feature improve the publishing flow and collaboration during the editorial process? 3) Can you explain how the "tasks" feature works and how it can be configured by users and plugins? 1. What is the purpose of introducing inline comments on blocks within the editor experience? - The purpose of introducing inline comments on blocks within the editor experience is to allow users to add comments, suggest edits, and tag other users for peer review. 2. What are some of the highlights of the improve multi-entity saving? - Some of the highlights of the improve multi-entity saving are scheduling design changes on block themes that can be managed through the various revisions systems, naming future revisions to better manage and orchestrate changes throughout a site, and previewing snapshots of a site before they go live. 3. What is the goal of the tools and infrastructure developed for Workflows? - The goal of the tools and infrastructure developed for Workflows is to support simpler use cases all the way to larger editorial teams, managing deadlines, handoffs, and more sophisticated review processes, while plugins should be able to take it further.