{"id":1233,"date":"2026-09-03T21:42:44","date_gmt":"2026-09-03T21:42:44","guid":{"rendered":"https:\/\/wp001.tenwrite.com\/cms-publishing-workflow-a-practical-guide-for-content-teams\/"},"modified":"2026-09-03T21:42:44","modified_gmt":"2026-09-03T21:42:44","slug":"cms-publishing-workflow-a-practical-guide-for-content-teams","status":"publish","type":"post","link":"https:\/\/wp001.tenwrite.com\/cms-publishing-workflow-a-practical-guide-for-content-teams\/","title":{"rendered":"CMS Publishing Workflow: A Practical Guide for Content Teams"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">An approved article is not automatically a publishable CMS item. The document may contain the final wording while the destination still needs a slug, taxonomy, images, excerpts, SEO fields, or a release date. Those details become visible only when someone prepares the content in the CMS and checks how it will render there.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A practical <strong>CMS publishing workflow<\/strong> covers that last mile: moving an approved source into a CMS-ready item, choosing the correct release state, and confirming the destination after scheduling or publication. It does not replace research, writing, substantive editing, or client approval. It makes sure those decisions survive the move into WordPress or another publishing system.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This guide gives content teams a repeatable path from an approved Google Doc to a verified CMS result. The same model can support manual publishing, a CMS integration, or a tool such as Tenwrite that lets a team review, revise, schedule, or save generated content as a CMS draft before it goes live.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What a CMS publishing workflow includes\u2014and what it does not<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><img decoding=\"async\" src=\"https:\/\/wp001.tenwrite.com\/wp-content\/uploads\/2026\/09\/6e4f066cdd.webp\" alt=\"Flow showing an approved source becoming a CMS-ready item, moving through a release state, and ending as a verified destination.\">\n<em>A CMS publishing workflow moves an approved source through CMS preparation, a selected release state, and destination verification.<\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A CMS publishing workflow starts when the source has been approved for CMS preparation. It ends when the destination has reached the intended state and the team has recorded enough information to find and troubleshoot the item later.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The stages are:<\/p>\n\n\n\n<p class=\"is-layout-flow wp-block-quote-is-layout-flow\"><strong>Approved source \u2192 CMS-ready item \u2192 Release state \u2192 Verified destination<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Each stage answers a different question:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Stage<\/th><th>Input<\/th><th>Main question<\/th><th>Recorded outcome<\/th><\/tr><\/thead><tbody><tr><td>Approved source<\/td><td>Final editorial document and publishing instructions<\/td><td>Is this the version that should be prepared?<\/td><td>Source link, version, and approval status<\/td><\/tr><tr><td>CMS-ready item<\/td><td>Approved source package and destination details<\/td><td>Have the body, assets, and fields been assembled correctly?<\/td><td>CMS item ID or draft link and preparation notes<\/td><\/tr><tr><td>Release state<\/td><td>Prepared CMS item and timing or review conditions<\/td><td>Should it return, remain a draft, be scheduled, or go live?<\/td><td>Selected status, owner, and reason<\/td><\/tr><tr><td>Verified destination<\/td><td>CMS result after scheduling or publication<\/td><td>Does the destination match the intended outcome?<\/td><td>URL or scheduled record, verification time, and follow-up<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">This boundary matters because content approval and CMS readiness are different decisions. An editor can approve the wording in a Google Doc while the featured image is still missing. A client can approve the article while the release date remains undecided. A CMS publisher can import the content successfully while discovering that an instruction has no equivalent destination field.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For the editorial background that comes before this stage, see the guide to a <a href=\"https:\/\/wp001.tenwrite.com\/cms-approval-workflow-for-agency-content-teams-from-approved-source-to-published-post\/\">CMS approval workflow for agency content teams<\/a>. This article begins after that approval has been granted and concentrates on preparing, releasing, and verifying the destination.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">The four states between approved source and live page<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A useful CMS publishing workflow does not treat \u201cpublished\u201d as the only successful result. The correct outcome depends on what is unresolved and whether the release conditions are satisfied.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>State<\/th><th>Use this state when<\/th><th>Do not advance when<\/th><th>Recorded outcome<\/th><\/tr><\/thead><tbody><tr><td><strong>Return for correction<\/strong><\/td><td>The approved source has a material change, missing required input, conflicting instruction, or unresolved asset or metadata decision.<\/td><td>The person preparing the item would have to guess, silently edit approved wording, or substitute an unapproved asset.<\/td><td>Return reason, owner, required correction, and source version to use next.<\/td><\/tr><tr><td><strong>CMS draft<\/strong><\/td><td>The content is assembled, but a CMS-side review, client confirmation, asset decision, or destination check remains.<\/td><td>Required fields or rendered content have not been inspected in the destination context.<\/td><td>Draft link or ID, open issue, reviewer, and next action.<\/td><\/tr><tr><td><strong>Scheduled release<\/strong><\/td><td>The content and destination checks are complete, but publication must occur at a confirmed future date or time.<\/td><td>The release time is provisional, the timezone is unclear, or a required approval is still pending.<\/td><td>Scheduled URL or item ID, release time and timezone, owner, and final status.<\/td><\/tr><tr><td><strong>Live publication<\/strong><\/td><td>The source, CMS item, required fields, preview, timing, and release authorization are all complete.<\/td><td>Any material discrepancy remains, even if the article looks acceptable in the editor.<\/td><td>Live URL, publication time, verifier, and follow-up note.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">These states are conceptual rather than universal CMS labels. A particular system may use different names or permissions. The important part is preserving the decision behind the state.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, \u201cdraft\u201d should not mean \u201csomeone imported the article.\u201d It should mean that the item is intentionally held because a defined review or preparation task remains. Likewise, \u201cscheduled\u201d should mean that the content is complete and the timing is confirmed\u2014not merely that someone entered a date while other issues were open.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Set the source package before content enters the CMS<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The source package is the set of inputs the publisher needs to prepare the CMS item without reconstructing decisions from comments, chat messages, and separate spreadsheets. It can be a short section in the project record or a structured row linked to the approved document.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">At minimum, assemble:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Approved source:<\/strong> the exact Google Doc link, document name, and version or approval date.<\/li>\n\n\n\n<li><strong>CMS destination:<\/strong> the client site, post type, destination URL direction, and slug instruction where applicable.<\/li>\n\n\n\n<li><strong>Core copy:<\/strong> the approved title, body content, headings, lists, links, and calls to action.<\/li>\n\n\n\n<li><strong>Publishing fields:<\/strong> excerpt direction, category, tags, author or byline treatment where applicable, and SEO fields required by that site.<\/li>\n\n\n\n<li><strong>Assets:<\/strong> featured-image instruction, in-body images, filenames or source references, captions, and alt-text ownership where used.<\/li>\n\n\n\n<li><strong>Release instruction:<\/strong> return, draft, schedule, or publish expectation, including a confirmed date and timezone when scheduling is requested.<\/li>\n\n\n\n<li><strong>Open items:<\/strong> any missing asset, unresolved link, alternate title, pending client note, or destination-specific limitation.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Consider a package for an article called \u201cChoosing a Backup Process for a Small Business Site\u201d:<\/p>\n\n\n\n<pre><code class=\"language-text\">Source: approved Google Doc \u2014 client article \u2014 v3\nDestination: Client A WordPress site\nSlug direction: \/small-business-site-backup-process\/\nCategory: Site Operations\nTags: backups, WordPress maintenance\nExcerpt: Use the approved two-sentence excerpt in the brief\nFeatured image: supplied by client; not yet attached\nRelease instruction: schedule after featured image confirmation\nOpen item: confirm whether the supplied image is licensed for the client site\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">This package shows why editorial approval is not the same as release approval. The article can be approved for wording while the image and licensing decision remain open. The correct next state is not \u201cpublish\u201d; it is either <strong>return for correction<\/strong> if the source package is incomplete, or <strong>CMS draft<\/strong> if the publisher can assemble the item while clearly recording the open issue.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A practical completion condition is simple: another trained publisher should be able to identify the source, destination, required fields, assets, release instruction, and unresolved decisions without opening a private message thread. If they cannot, the package is not ready for CMS preparation.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Prepare the CMS item: body content, assets, and metadata<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">CMS preparation is a translation pass, not a copy-and-paste task. The source document and the destination may represent the same article through different fields, templates, and rendering rules.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Use a field map for the destination site. The example below is deliberately small, but it makes missing mappings visible:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Approved source input<\/th><th>CMS destination<\/th><th>Preparation check<\/th><th>Outcome<\/th><\/tr><\/thead><tbody><tr><td>Document title<\/td><td>Post title<\/td><td>Confirm the approved title is used once and does not include internal notes or alternatives.<\/td><td>Title matches the source package.<\/td><\/tr><tr><td>Heading structure<\/td><td>Post body headings<\/td><td>Check that headings remain hierarchical and are not merely bold paragraphs.<\/td><td>Body structure is readable in the editor and preview.<\/td><\/tr><tr><td>Paragraphs, lists, and tables<\/td><td>Post body content<\/td><td>Inspect list nesting, table behavior, spacing, and any unsupported formatting.<\/td><td>Content is usable in the destination template.<\/td><\/tr><tr><td>Linked words and URLs<\/td><td>Body links<\/td><td>Open representative links and compare visible anchor text with the intended destination.<\/td><td>Links point to the approved targets or are flagged.<\/td><\/tr><tr><td>Image instructions<\/td><td>Featured-image or body-image fields<\/td><td>Confirm placement, image selection, caption, and alt-text ownership where the CMS supports them.<\/td><td>Every required asset has a clear status.<\/td><\/tr><tr><td>Category and tags<\/td><td>Taxonomy fields<\/td><td>Select only approved or valid destination terms; do not invent a near-duplicate term to fill a blank.<\/td><td>Taxonomy matches the source package and site rules.<\/td><\/tr><tr><td>Excerpt direction<\/td><td>Excerpt field or template behavior<\/td><td>Confirm whether the site uses a separate excerpt and whether the supplied wording fits that field.<\/td><td>Excerpt is entered, intentionally blank, or flagged.<\/td><\/tr><tr><td>SEO title and description<\/td><td>Available SEO fields<\/td><td>Populate supported fields only; distinguish an SEO field from the visible post title or excerpt.<\/td><td>Required metadata is present or its absence is recorded.<\/td><\/tr><tr><td>Slug direction<\/td><td>Permalink field<\/td><td>Check the final slug for the intended wording and destination path.<\/td><td>URL direction is confirmed or sent back for a decision.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">The pass should happen in this order:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Structure:<\/strong> confirm the title, heading hierarchy, paragraphs, lists, tables, and emphasis.<\/li>\n\n\n\n<li><strong>Links:<\/strong> test representative internal, external, and call-to-action links. A link passes when it reaches the intended destination and its anchor text still makes sense in context.<\/li>\n\n\n\n<li><strong>Assets:<\/strong> match each image instruction to a destination placement. Do not treat a missing featured image as a cosmetic issue if the site template expects one.<\/li>\n\n\n\n<li><strong>Taxonomy:<\/strong> compare the selected category and tags with the source package and the destination\u2019s available terms.<\/li>\n\n\n\n<li><strong>Metadata:<\/strong> fill the excerpt, SEO fields, and URL settings that this site actually supports.<\/li>\n\n\n\n<li><strong>Rendering:<\/strong> open the CMS preview and inspect the assembled page rather than relying on the source document\u2019s appearance.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">If a source instruction has no valid destination field, flag it. Do not silently approximate a missing CMS field by placing the instruction in the body, changing the visible title, or adding an unapproved taxonomy term. The recorded outcome can be \u201cdestination limitation returned for decision\u201d; that is more useful than a plausible but undocumented substitution.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Teams that need a deeper look at the conversion layer can use this <a href=\"https:\/\/wp001.tenwrite.com\/google-doc-to-html-a-clean-handoff-workflow-for-wordpress-content-teams\/\">Google Doc to HTML handoff workflow<\/a>. Clean markup can help, but it does not replace checking WordPress fields, templates, assets, and release settings.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Choose the release path: draft, schedule, publish, or return<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Once the CMS item exists, apply the same decision rules every time. A compact decision path is:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Did the approved source or any required input change?<\/strong> If yes, return the item for correction or confirmation. Do not publish a version whose source decision is no longer current.<\/li>\n\n\n\n<li><strong>Are required CMS fields, assets, or destination checks incomplete?<\/strong> If yes, keep the item as a CMS draft and record the missing work.<\/li>\n\n\n\n<li><strong>Is the item complete but tied to a confirmed future release time?<\/strong> If yes, schedule it with the correct timezone and release owner.<\/li>\n\n\n\n<li><strong>Are all release conditions complete, with no remaining timing or approval dependency?<\/strong> If yes, publish it.<\/li>\n\n\n\n<li><strong>If none of these conditions can be established,<\/strong> stop and ask for the missing decision rather than selecting a status by habit.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">The distinction between draft and return is especially useful. Return for correction means the source package itself needs a decision or change. CMS draft means the source is usable, but destination preparation or review is not finished. That keeps the publisher from rewriting approved copy merely to make the CMS entry look complete.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A release decision is complete only when the status and reason are recorded. For example:<\/p>\n\n\n\n<pre><code class=\"language-text\">Status: CMS draft\nReason: Article body and taxonomy prepared; featured image awaiting client confirmation\nNext owner: Account editor\nNext action: Confirm image license or provide replacement\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">After the image is confirmed and the preview passes, the record can change to:<\/p>\n\n\n\n<pre><code class=\"language-text\">Status: Scheduled\nReason: Required fields and preview verified; client release date confirmed\nRelease: 2026-10-15, 09:00 America\/New_York\nOwner: Publishing operator\n<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Run destination-specific checks before release<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A Google Doc can look correct while the CMS result is wrong. The destination may use a different heading renderer, strip formatting, apply a template, display an excerpt in a listing, or require a separate featured-image field. These checks belong in the CMS preview or destination interface.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Use a focused pre-release pass rather than trying to inspect every possible site behavior:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Heading hierarchy:<\/strong> confirm the title and body headings render in the intended order, with no accidental heading created from bold text.<\/li>\n\n\n\n<li><strong>Links:<\/strong> open important links and a representative sample of ordinary links. Check both the target and the visible anchor text.<\/li>\n\n\n\n<li><strong>Images:<\/strong> confirm the right image appears in the right location, scales acceptably, and has the required caption or alt text where applicable.<\/li>\n\n\n\n<li><strong>Featured image:<\/strong> verify the separate featured-image assignment if the destination template uses one.<\/li>\n\n\n\n<li><strong>Taxonomy:<\/strong> check the displayed category and tags against the approved package.<\/li>\n\n\n\n<li><strong>Excerpt:<\/strong> inspect the excerpt field or the listing behavior if the site uses excerpts separately from the article body.<\/li>\n\n\n\n<li><strong>SEO fields:<\/strong> verify the fields supported by that site and plugin configuration without assuming every CMS exposes the same options.<\/li>\n\n\n\n<li><strong>Template elements:<\/strong> look for author treatment, breadcrumbs, related-content areas, calls to action, or other destination elements that can affect the page even though they are absent from the source document.<\/li>\n\n\n\n<li><strong>URL and status:<\/strong> confirm the intended slug, post type, current status, and scheduled time where relevant.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Use an explicit pass\/fail condition:<\/p>\n\n\n\n<p class=\"is-layout-flow wp-block-quote-is-layout-flow\"><strong>Pass:<\/strong> required fields are populated or intentionally blank, the rendered preview matches the approved source package, and no unresolved material issue remains.<\/p>\n<p><strong>Fail:<\/strong> any required field, asset, link, structural element, or release condition is missing, incorrect, or undecided.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A failed check should produce a next action, not just a comment. \u201cImage wrong\u201d is incomplete. \u201cReplace the featured image with <code>client-a-backup.jpg<\/code>; publishing operator owns the change; rerun preview check\u201d gives the next person a usable instruction.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For a platform-specific extension, the <a href=\"https:\/\/wp001.tenwrite.com\/wordpress-google-docs-integration-a-controlled-publishing-workflow-for-agencies\/\">WordPress Google Docs integration workflow<\/a> covers the transfer into WordPress. The destination preview still needs to be checked for the individual site\u2019s fields and template behavior.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Verify the live result and record the outcome<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The workflow is not finished when someone clicks <strong>Publish<\/strong> or <strong>Schedule<\/strong>. Verification confirms that the CMS reached the intended state and gives the team a reference if the page later needs correction.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For a live post, check:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>The live URL opens and matches the intended destination.<\/li>\n\n\n\n<li>The visible title, headings, body content, links, and images render as expected.<\/li>\n\n\n\n<li>The publication status and visible publication date are correct.<\/li>\n\n\n\n<li>Key metadata is present where the site exposes or requires it.<\/li>\n\n\n\n<li>The page is not displaying an obvious draft, placeholder, missing-asset, or template error.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">For a scheduled post, verify the item in the CMS rather than pretending that a future page has already been validated as live. Confirm the scheduled status, date, time, timezone, destination URL or slug, and any remaining release dependency. After the release, perform the live checks appropriate to the site.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A minimal publishing log might contain:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Source<\/th><th>Destination<\/th><th>Status<\/th><th>Release time<\/th><th>Owner<\/th><th>Verification or follow-up<\/th><\/tr><\/thead><tbody><tr><td>Approved Google Doc v3<\/td><td>WordPress post 1842<\/td><td>Scheduled<\/td><td>2026-10-15 09:00 ET<\/td><td>Publishing operator<\/td><td>Verify live rendering after release<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Do not build a large governance system when a small record answers the practical troubleshooting questions: Which source was used? Where did it go? What state is it in? Who handled it? When should someone check it? What remains open?<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If an item fails after release, compare the live result with the CMS preview and then with the approved source package. That sequence helps isolate whether the problem came from source preparation, a CMS field, template rendering, scheduling, or a post-release change.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Worked example: publishing one approved client article across the final mile<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><img decoding=\"async\" src=\"https:\/\/wp001.tenwrite.com\/wp-content\/uploads\/2026\/09\/9fc3400fb3.webp\" alt=\"Timeline of an approved client article moving from source-package confirmation to CMS draft, featured-image confirmation, scheduled release, and live verification.\">\n<em>An illustrative agency article remains a CMS draft until its featured image is confirmed, then moves to a scheduled release and post-release verification.<\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Consider an illustrative agency article for Client A: <strong>\u201cHow to Reduce Downtime During a WordPress Update.\u201d<\/strong> The article has been edited and approved in Google Docs. The agency publishes several client articles each week, but the client\u2019s featured-image requirement makes this item a useful example.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">1. Confirm the source package<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The publishing operator receives the approved Google Doc link, the final title, the body copy, a slug direction, the \u201cSite Operations\u201d category, three approved tags, an excerpt, and the client\u2019s image instructions. The release note says: \u201cSchedule for October 15 at 9:00 a.m. Eastern after final CMS check.\u201d<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The operator records the source version and opens the destination site profile. The package is complete except for one item: the supplied image has not yet been confirmed for use as the featured image.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Decision:<\/strong> prepare the article as a CMS draft rather than schedule it.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Recorded outcome:<\/strong> \u201cDraft created; featured-image confirmation open with account editor.\u201d<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2. Assemble and inspect the CMS item<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The body is moved into the WordPress post editor. The operator checks that the title is in the title field, the section headings are structured correctly, the three links reach their intended destinations, and the image instruction is not accidentally left as editorial text in the body.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The category and tags are selected from the client site\u2019s existing taxonomy. The excerpt and supported SEO fields are entered from the source package. The permalink is checked against the approved slug direction.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The first preview shows that the article body is correct, but the featured-image field is empty. The missing image is not repaired by choosing a visually similar stock image because that would change an approved source input.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Decision:<\/strong> keep the item in CMS draft.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Recorded outcome:<\/strong> \u201cBody, links, taxonomy, excerpt, slug, and metadata pass; featured image unresolved.\u201d<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">3. Resolve the open input<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The account editor confirms that the client-approved image may be used and records the filename in the package. The publishing operator attaches it as the featured image, checks its placement in the preview, and confirms the supplied alt-text instruction.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is the exact decision that changes the release path: the required asset is no longer unresolved, and the client\u2019s release time is confirmed. The article has moved from \u201ccomplete enough to review as a draft\u201d to \u201ccomplete and waiting for a future release.\u201d<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Decision:<\/strong> change the status from CMS draft to scheduled.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Recorded outcome:<\/strong> \u201cPreview passed; featured image confirmed; scheduled for October 15 at 9:00 a.m. Eastern.\u201d<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">4. Verify and close the release<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The operator records the WordPress post ID, scheduled time, source link, destination site, and owner. After the release time, someone opens the live URL and checks the visible title, headings, links, image, taxonomy display, excerpt behavior, and key metadata.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The final record might read:<\/p>\n\n\n\n<pre><code class=\"language-text\">Source: Client A approved Google Doc \u2014 v3\nDestination: https:\/\/client-a.example.com\/wordpress-update-downtime\/\nStatus: Published\nRelease: 2026-10-15 09:00 America\/New_York\nOwner: Publishing operator\nVerified: 2026-10-15 09:12 America\/New_York\nFollow-up: None\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The example is intentionally ordinary. Its value is not a claim about one CMS\u2019s universal behavior; it is the separation of decisions. The agency did not confuse an approved document with a live page, did not invent a replacement for a missing image, and did not lose the reason the item remained a draft.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">To extend this model across several client sites, define the destination-specific fields and release rules for each site, then keep the common decision states consistent. A WordPress site may expose a particular taxonomy or SEO field; a Blogger destination may represent the same information differently. The stable part is the sequence of questions: Is the source current? Is the destination item complete? What remains unresolved? What release time applies? What happened afterward?<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If your team\u2019s bottleneck is the repetitive move from Google Docs into WordPress or Blogger, Tenwrite can reduce that preparation work while preserving a reviewable destination state. Start by examining one recurring article type and identify where time is lost: source conversion, CMS assembly, release selection, or post-publish verification. Then keep the state decision visible instead of treating automation as permission to publish unfinished work.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Learn how to build a CMS publishing workflow that moves approved content through CMS preparation, release decisions, and destination verification without publishing unfinished work.<\/p>\n","protected":false},"author":2,"featured_media":1232,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"tenwrite_seo":{"title":"CMS Publishing Workflow: A Practical Guide for Content Teams","description":"Learn how to move approved content through CMS preparation, release decisions, and destination verification without publishing unfinished work.","focusKeyword":"cms publishing workflow","canonicalUrl":"","noIndex":false,"noFollow":false},"_yoast_wpseo_title":"","_yoast_wpseo_metadesc":"","_yoast_wpseo_focuskw":"","_yoast_wpseo_canonical":"","_yoast_wpseo_meta-robots-noindex":"","_yoast_wpseo_meta-robots-nofollow":"","rank_math_title":"","rank_math_description":"","rank_math_focus_keyword":"","rank_math_canonical_url":"","rank_math_robots":[],"footnotes":""},"categories":[4],"tags":[64,57],"class_list":["post-1233","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-wordpress","tag-agency-publishing","tag-content-approval-workflow"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.0.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"Learn how to build a CMS publishing workflow that moves approved content through CMS preparation, release decisions, and destination verification without publishing unfinished work.\" \/>\n\t<meta name=\"robots\" content=\"noindex, nofollow, max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Rupam Poddar\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/wp001.tenwrite.com\/cms-publishing-workflow-a-practical-guide-for-content-teams\/\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.0.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"en_US\" \/>\n\t\t<meta property=\"og:site_name\" content=\"Tenwrite Blog - Discover tips and guides on publishing Google Docs to WordPress and Blogger.\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"CMS Publishing Workflow: A Practical Guide for Content Teams - Tenwrite Blog\" \/>\n\t\t<meta property=\"og:description\" content=\"Learn how to build a CMS publishing workflow that moves approved content through CMS preparation, release decisions, and destination verification without publishing unfinished work.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/wp001.tenwrite.com\/cms-publishing-workflow-a-practical-guide-for-content-teams\/\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/wp001.tenwrite.com\/wp-content\/uploads\/2026\/09\/b2f97ddeef.webp\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/wp001.tenwrite.com\/wp-content\/uploads\/2026\/09\/b2f97ddeef.webp\" \/>\n\t\t<meta property=\"og:image:width\" content=\"1600\" \/>\n\t\t<meta property=\"og:image:height\" content=\"900\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2026-09-03T21:42:44+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2026-09-03T21:42:44+00:00\" \/>\n\t\t<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n\t\t<meta name=\"twitter:title\" content=\"CMS Publishing Workflow: A Practical Guide for Content Teams - Tenwrite Blog\" \/>\n\t\t<meta name=\"twitter:description\" content=\"Learn how to build a CMS publishing workflow that moves approved content through CMS preparation, release decisions, and destination verification without publishing unfinished work.\" \/>\n\t\t<meta name=\"twitter:image\" content=\"https:\/\/wp001.tenwrite.com\/wp-content\/uploads\/2026\/09\/b2f97ddeef.webp\" \/>\n\t\t<script type=\"application\/ld+json\" class=\"aioseo-schema\">\n\t\t\t{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"BlogPosting\",\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/cms-publishing-workflow-a-practical-guide-for-content-teams\\\/#blogposting\",\"name\":\"CMS Publishing Workflow: A Practical Guide for Content Teams - Tenwrite Blog\",\"headline\":\"CMS Publishing Workflow: A Practical Guide for Content Teams\",\"author\":{\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/author\\\/rupam\\\/#author\"},\"publisher\":{\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/#organization\"},\"image\":{\"@type\":\"ImageObject\",\"url\":\"https:\\\/\\\/wp001.tenwrite.com\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/b2f97ddeef.webp\",\"width\":1600,\"height\":900},\"datePublished\":\"2026-09-03T21:42:44+00:00\",\"dateModified\":\"2026-09-03T21:42:44+00:00\",\"inLanguage\":\"en-US\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/cms-publishing-workflow-a-practical-guide-for-content-teams\\\/#webpage\"},\"isPartOf\":{\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/cms-publishing-workflow-a-practical-guide-for-content-teams\\\/#webpage\"},\"articleSection\":\"WordPress, agency publishing, content approval workflow\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/cms-publishing-workflow-a-practical-guide-for-content-teams\\\/#breadcrumblist\",\"itemListElement\":[{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/wp001.tenwrite.com#listItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/wp001.tenwrite.com\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/category\\\/wordpress\\\/#listItem\",\"name\":\"WordPress\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/category\\\/wordpress\\\/#listItem\",\"position\":2,\"name\":\"WordPress\",\"item\":\"https:\\\/\\\/wp001.tenwrite.com\\\/category\\\/wordpress\\\/\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/cms-publishing-workflow-a-practical-guide-for-content-teams\\\/#listItem\",\"name\":\"CMS Publishing Workflow: A Practical Guide for Content Teams\"},\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/wp001.tenwrite.com#listItem\",\"name\":\"Home\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/cms-publishing-workflow-a-practical-guide-for-content-teams\\\/#listItem\",\"position\":3,\"name\":\"CMS Publishing Workflow: A Practical Guide for Content Teams\",\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/category\\\/wordpress\\\/#listItem\",\"name\":\"WordPress\"}}]},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/#organization\",\"name\":\"Tenwrite Blog\",\"description\":\"Discover tips and guides on publishing Google Docs to WordPress and Blogger.\",\"url\":\"https:\\\/\\\/wp001.tenwrite.com\\\/\",\"sameAs\":[\"https:\\\/\\\/www.youtube.com\\\/@tenwrite\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/author\\\/rupam\\\/#author\",\"url\":\"https:\\\/\\\/wp001.tenwrite.com\\\/author\\\/rupam\\\/\",\"name\":\"Rupam Poddar\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/cms-publishing-workflow-a-practical-guide-for-content-teams\\\/#authorImage\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/b3549e6840b1384554f94451ec47b32e5227ba632974ff50abee6a185adf885d?s=96&d=mm&r=g\",\"width\":96,\"height\":96,\"caption\":\"Rupam Poddar\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/cms-publishing-workflow-a-practical-guide-for-content-teams\\\/#webpage\",\"url\":\"https:\\\/\\\/wp001.tenwrite.com\\\/cms-publishing-workflow-a-practical-guide-for-content-teams\\\/\",\"name\":\"CMS Publishing Workflow: A Practical Guide for Content Teams - Tenwrite Blog\",\"description\":\"Learn how to build a CMS publishing workflow that moves approved content through CMS preparation, release decisions, and destination verification without publishing unfinished work.\",\"inLanguage\":\"en-US\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/#website\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/cms-publishing-workflow-a-practical-guide-for-content-teams\\\/#breadcrumblist\"},\"author\":{\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/author\\\/rupam\\\/#author\"},\"creator\":{\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/author\\\/rupam\\\/#author\"},\"image\":{\"@type\":\"ImageObject\",\"url\":\"https:\\\/\\\/wp001.tenwrite.com\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/b2f97ddeef.webp\",\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/cms-publishing-workflow-a-practical-guide-for-content-teams\\\/#mainImage\",\"width\":1600,\"height\":900},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/cms-publishing-workflow-a-practical-guide-for-content-teams\\\/#mainImage\"},\"datePublished\":\"2026-09-03T21:42:44+00:00\",\"dateModified\":\"2026-09-03T21:42:44+00:00\"},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/#website\",\"url\":\"https:\\\/\\\/wp001.tenwrite.com\\\/\",\"name\":\"Tenwrite Blog\",\"description\":\"Discover tips and guides on publishing Google Docs to WordPress and Blogger.\",\"inLanguage\":\"en-US\",\"publisher\":{\"@id\":\"https:\\\/\\\/wp001.tenwrite.com\\\/#organization\"}}]}\n\t\t<\/script>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"CMS Publishing Workflow: A Practical Guide for Content Teams - Tenwrite Blog","description":"Learn how to build a CMS publishing workflow that moves approved content through CMS preparation, release decisions, and destination verification without publishing unfinished work.","canonical_url":"https:\/\/wp001.tenwrite.com\/cms-publishing-workflow-a-practical-guide-for-content-teams\/","robots":"noindex, nofollow, max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"BlogPosting","@id":"https:\/\/wp001.tenwrite.com\/cms-publishing-workflow-a-practical-guide-for-content-teams\/#blogposting","name":"CMS Publishing Workflow: A Practical Guide for Content Teams - Tenwrite Blog","headline":"CMS Publishing Workflow: A Practical Guide for Content Teams","author":{"@id":"https:\/\/wp001.tenwrite.com\/author\/rupam\/#author"},"publisher":{"@id":"https:\/\/wp001.tenwrite.com\/#organization"},"image":{"@type":"ImageObject","url":"https:\/\/wp001.tenwrite.com\/wp-content\/uploads\/2026\/09\/b2f97ddeef.webp","width":1600,"height":900},"datePublished":"2026-09-03T21:42:44+00:00","dateModified":"2026-09-03T21:42:44+00:00","inLanguage":"en-US","mainEntityOfPage":{"@id":"https:\/\/wp001.tenwrite.com\/cms-publishing-workflow-a-practical-guide-for-content-teams\/#webpage"},"isPartOf":{"@id":"https:\/\/wp001.tenwrite.com\/cms-publishing-workflow-a-practical-guide-for-content-teams\/#webpage"},"articleSection":"WordPress, agency publishing, content approval workflow"},{"@type":"BreadcrumbList","@id":"https:\/\/wp001.tenwrite.com\/cms-publishing-workflow-a-practical-guide-for-content-teams\/#breadcrumblist","itemListElement":[{"@type":"ListItem","@id":"https:\/\/wp001.tenwrite.com#listItem","position":1,"name":"Home","item":"https:\/\/wp001.tenwrite.com","nextItem":{"@type":"ListItem","@id":"https:\/\/wp001.tenwrite.com\/category\/wordpress\/#listItem","name":"WordPress"}},{"@type":"ListItem","@id":"https:\/\/wp001.tenwrite.com\/category\/wordpress\/#listItem","position":2,"name":"WordPress","item":"https:\/\/wp001.tenwrite.com\/category\/wordpress\/","nextItem":{"@type":"ListItem","@id":"https:\/\/wp001.tenwrite.com\/cms-publishing-workflow-a-practical-guide-for-content-teams\/#listItem","name":"CMS Publishing Workflow: A Practical Guide for Content Teams"},"previousItem":{"@type":"ListItem","@id":"https:\/\/wp001.tenwrite.com#listItem","name":"Home"}},{"@type":"ListItem","@id":"https:\/\/wp001.tenwrite.com\/cms-publishing-workflow-a-practical-guide-for-content-teams\/#listItem","position":3,"name":"CMS Publishing Workflow: A Practical Guide for Content Teams","previousItem":{"@type":"ListItem","@id":"https:\/\/wp001.tenwrite.com\/category\/wordpress\/#listItem","name":"WordPress"}}]},{"@type":"Organization","@id":"https:\/\/wp001.tenwrite.com\/#organization","name":"Tenwrite Blog","description":"Discover tips and guides on publishing Google Docs to WordPress and Blogger.","url":"https:\/\/wp001.tenwrite.com\/","sameAs":["https:\/\/www.youtube.com\/@tenwrite"]},{"@type":"Person","@id":"https:\/\/wp001.tenwrite.com\/author\/rupam\/#author","url":"https:\/\/wp001.tenwrite.com\/author\/rupam\/","name":"Rupam Poddar","image":{"@type":"ImageObject","@id":"https:\/\/wp001.tenwrite.com\/cms-publishing-workflow-a-practical-guide-for-content-teams\/#authorImage","url":"https:\/\/secure.gravatar.com\/avatar\/b3549e6840b1384554f94451ec47b32e5227ba632974ff50abee6a185adf885d?s=96&d=mm&r=g","width":96,"height":96,"caption":"Rupam Poddar"}},{"@type":"WebPage","@id":"https:\/\/wp001.tenwrite.com\/cms-publishing-workflow-a-practical-guide-for-content-teams\/#webpage","url":"https:\/\/wp001.tenwrite.com\/cms-publishing-workflow-a-practical-guide-for-content-teams\/","name":"CMS Publishing Workflow: A Practical Guide for Content Teams - Tenwrite Blog","description":"Learn how to build a CMS publishing workflow that moves approved content through CMS preparation, release decisions, and destination verification without publishing unfinished work.","inLanguage":"en-US","isPartOf":{"@id":"https:\/\/wp001.tenwrite.com\/#website"},"breadcrumb":{"@id":"https:\/\/wp001.tenwrite.com\/cms-publishing-workflow-a-practical-guide-for-content-teams\/#breadcrumblist"},"author":{"@id":"https:\/\/wp001.tenwrite.com\/author\/rupam\/#author"},"creator":{"@id":"https:\/\/wp001.tenwrite.com\/author\/rupam\/#author"},"image":{"@type":"ImageObject","url":"https:\/\/wp001.tenwrite.com\/wp-content\/uploads\/2026\/09\/b2f97ddeef.webp","@id":"https:\/\/wp001.tenwrite.com\/cms-publishing-workflow-a-practical-guide-for-content-teams\/#mainImage","width":1600,"height":900},"primaryImageOfPage":{"@id":"https:\/\/wp001.tenwrite.com\/cms-publishing-workflow-a-practical-guide-for-content-teams\/#mainImage"},"datePublished":"2026-09-03T21:42:44+00:00","dateModified":"2026-09-03T21:42:44+00:00"},{"@type":"WebSite","@id":"https:\/\/wp001.tenwrite.com\/#website","url":"https:\/\/wp001.tenwrite.com\/","name":"Tenwrite Blog","description":"Discover tips and guides on publishing Google Docs to WordPress and Blogger.","inLanguage":"en-US","publisher":{"@id":"https:\/\/wp001.tenwrite.com\/#organization"}}]},"og:locale":"en_US","og:site_name":"Tenwrite Blog - Discover tips and guides on publishing Google Docs to WordPress and Blogger.","og:type":"article","og:title":"CMS Publishing Workflow: A Practical Guide for Content Teams - Tenwrite Blog","og:description":"Learn how to build a CMS publishing workflow that moves approved content through CMS preparation, release decisions, and destination verification without publishing unfinished work.","og:url":"https:\/\/wp001.tenwrite.com\/cms-publishing-workflow-a-practical-guide-for-content-teams\/","og:image":"https:\/\/wp001.tenwrite.com\/wp-content\/uploads\/2026\/09\/b2f97ddeef.webp","og:image:secure_url":"https:\/\/wp001.tenwrite.com\/wp-content\/uploads\/2026\/09\/b2f97ddeef.webp","og:image:width":1600,"og:image:height":900,"article:published_time":"2026-09-03T21:42:44+00:00","article:modified_time":"2026-09-03T21:42:44+00:00","twitter:card":"summary_large_image","twitter:title":"CMS Publishing Workflow: A Practical Guide for Content Teams - Tenwrite Blog","twitter:description":"Learn how to build a CMS publishing workflow that moves approved content through CMS preparation, release decisions, and destination verification without publishing unfinished work.","twitter:image":"https:\/\/wp001.tenwrite.com\/wp-content\/uploads\/2026\/09\/b2f97ddeef.webp"},"aioseo_meta_data":[],"aioseo_breadcrumb":"<div class=\"aioseo-breadcrumbs\"><span class=\"aioseo-breadcrumb\">\n\t\t\t<a href=\"https:\/\/wp001.tenwrite.com\" title=\"Home\">Home<\/a>\n\t\t<\/span><span class=\"aioseo-breadcrumb-separator\">&raquo;<\/span><span class=\"aioseo-breadcrumb\">\n\t\t\t<a href=\"https:\/\/wp001.tenwrite.com\/category\/wordpress\/\" title=\"WordPress\">WordPress<\/a>\n\t\t<\/span><span class=\"aioseo-breadcrumb-separator\">&raquo;<\/span><span class=\"aioseo-breadcrumb\">\n\t\t\tCMS Publishing Workflow: A Practical Guide for Content Teams\n\t\t<\/span><\/div>","aioseo_breadcrumb_json":[{"label":"Home","link":"https:\/\/wp001.tenwrite.com"},{"label":"WordPress","link":"https:\/\/wp001.tenwrite.com\/category\/wordpress\/"},{"label":"CMS Publishing Workflow: A Practical Guide for Content Teams","link":"https:\/\/wp001.tenwrite.com\/cms-publishing-workflow-a-practical-guide-for-content-teams\/"}],"_links":{"self":[{"href":"https:\/\/wp001.tenwrite.com\/wp-json\/wp\/v2\/posts\/1233","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wp001.tenwrite.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wp001.tenwrite.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wp001.tenwrite.com\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/wp001.tenwrite.com\/wp-json\/wp\/v2\/comments?post=1233"}],"version-history":[{"count":0,"href":"https:\/\/wp001.tenwrite.com\/wp-json\/wp\/v2\/posts\/1233\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/wp001.tenwrite.com\/wp-json\/wp\/v2\/media\/1232"}],"wp:attachment":[{"href":"https:\/\/wp001.tenwrite.com\/wp-json\/wp\/v2\/media?parent=1233"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wp001.tenwrite.com\/wp-json\/wp\/v2\/categories?post=1233"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wp001.tenwrite.com\/wp-json\/wp\/v2\/tags?post=1233"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}