{"id":48,"date":"2026-07-09T07:11:27","date_gmt":"2026-07-09T07:11:27","guid":{"rendered":"https:\/\/flowz.orauria.com\/phone-photo-to-campaign-workflow-mindset\/"},"modified":"2026-07-09T09:57:43","modified_gmt":"2026-07-09T09:57:43","slug":"phone-photo-to-campaign-workflow-mindset","status":"publish","type":"post","link":"https:\/\/flowz.orauria.com\/vi\/phone-photo-to-campaign-workflow-mindset\/","title":{"rendered":"From Phone Photo to Campaign: A Workflow Mindset for Small Brands"},"content":{"rendered":"<h1>From Phone Photo to Campaign: A Workflow Mindset for Small Brands<\/h1>\n<p>The most common excuse in small-brand ecommerce is also the least true: <em>&quot;We can&#x27;t shoot a campaign \u2014 we only have phone photos.&quot;<\/em> The phone is not the bottleneck. The <strong>workflow<\/strong> is.<\/p>\n<p>A founder snaps a product on a kitchen table. It is slightly crooked, the light is mixed, the background is busy. Most teams do one of two things: post it anyway and hope, or open an AI tool, generate something prettier, and discover marketing needs six more formats by Friday. Both paths treat the image as a <strong>one-off<\/strong>. Neither treats it as the <strong>first node<\/strong> in a pipeline.<\/p>\n<p><strong>AI product photo workflow<\/strong> for small brands is not about fixing a single file. It is about turning a rough reference into a <strong>campaign system<\/strong> \u2014 hero, lifestyle scenes, social crops, email header \u2014 with creative direction that survives every step.<\/p>\n<blockquote>\n<p><strong>Key Takeaways<\/strong><\/p>\n<ul>\n<li>Your phone photo is a <strong>reference asset<\/strong>, not a final deliverable. The workflow starts with what you have, not what you wish you had.<\/li>\n<li>In 2026, Adobe found <strong>72% of creators<\/strong> frequently create content on mobile \u2014 and <strong>60%<\/strong> used more than one creative AI tool in three months to match the right tool to each task (Adobe, 2025\u20132026).<\/li>\n<li>The <strong>Phone \u2192 Campaign pipeline<\/strong> has five stages: Capture, Clean, Direct, Extend, Adapt. Skip a stage and you rebuild from scratch next launch.<\/li>\n<li>Workflow mindset beats better prompts: save the <strong>creative logic<\/strong>, not just the pixels.<\/li>\n<\/ul>\n<\/blockquote>\n<p>If you have read <a href=\"\/posts\/ai-ecommerce-design-not-ai-image\/\">AI Ecommerce Design Is Not AI Image<\/a>, you know commercial creative is a system \u2014 not a single render. This article is the <strong>SME entry point<\/strong>: how to run that system when your only studio is a windowsill and your only camera is in your pocket.<\/p>\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" src=\"https:\/\/flowz.orauria.com\/wp-content\/uploads\/2026\/07\/hero-phone-product.jpg\" alt=\"Hand holding smartphone photographing product for ecommerce reference\"\/><figcaption>Your phone is node one \u2014 not a dead end.<\/figcaption><\/figure>\n<h2>Why Do Small Brands Treat Phone Photos as Dead Ends?<\/h2>\n<p>Three beliefs block the pipeline before it starts:<\/p>\n<p><strong>1. &quot;Professional means professional camera.&quot;<\/strong> Buyers care about clarity, context, and trust \u2014 not EXIF data. A well-directed phone reference processed through a consistent workflow often outperforms a random DSLR shot with no brief.<\/p>\n<p><strong>2. &quot;AI will fix everything in one click.&quot;<\/strong> Adobe&#x27;s 2026 Creators&#x27; Toolkit Report found <strong>57% of creators<\/strong> say AI outputs need moderate or extensive editing before publish. AI accelerates production; it does not replace <strong>creative direction<\/strong>.<\/p>\n<p><strong>3. &quot;We will redo it properly later.&quot;<\/strong> &quot;Later&quot; becomes never. Meanwhile every channel gets a different ad hoc image \u2014 and the brand drifts before it scales.<\/p>\n<h2>What Is the Phone \u2192 Campaign Workflow?<\/h2>\n<p>A <strong>campaign<\/strong> is not one image. It is a coordinated set: marketplace hero, PDP gallery, paid social, email, maybe short video. The Phone \u2192 Campaign workflow maps how one capture becomes that set without reinventing the brief each time.<\/p>\n<table>\n<tbody>\n<tr>\n<th>Stage<\/th>\n<th>Job<\/th>\n<th>Question it answers<\/th>\n<\/tr>\n<tr>\n<td><strong>1. Capture<\/strong><\/td>\n<td>Document the real product<\/td>\n<td>What does truth look like?<\/td>\n<\/tr>\n<tr>\n<td><strong>2. Clean<\/strong><\/td>\n<td>Normalize the reference<\/td>\n<td>Can AI read shape, label, color accurately?<\/td>\n<\/tr>\n<tr>\n<td><strong>3. Direct<\/strong><\/td>\n<td>Apply SCENE \/ context map<\/td>\n<td>What story and scenes does this SKU need?<\/td>\n<\/tr>\n<tr>\n<td><strong>4. Extend<\/strong><\/td>\n<td>Generate scene family<\/td>\n<td>What images belong in the same world?<\/td>\n<\/tr>\n<tr>\n<td><strong>5. Adapt<\/strong><\/td>\n<td>Export per channel<\/td>\n<td>What does each platform require?<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>This is <a href=\"\/posts\/ai-ecommerce-design-not-ai-image\/\">AI ecommerce design<\/a> at SME scale \u2014 five layers compressed into a pipeline a two-person team can run in an afternoon.<\/p>\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" src=\"https:\/\/flowz.orauria.com\/wp-content\/uploads\/2026\/07\/workflow-dashboard.jpg\" alt=\"Five-stage phone to campaign workflow pipeline on analytics dashboard\"\/><figcaption>Capture \u2192 Clean \u2192 Direct \u2192 Extend \u2192 Adapt: five stages, one pipeline.<\/figcaption><\/figure>\n<h2>Stage 1: Capture \u2014 What Phone Photos Actually Need<\/h2>\n<p>You do not need a light tent. You need <strong>repeatable capture rules<\/strong>:<\/p>\n<ul>\n<li><strong>One hero angle<\/strong> that shows label, shape, and true color<\/li>\n<li><strong>Even, indirect light<\/strong> \u2014 window light beats overhead kitchen LED<\/li>\n<li><strong>Simple background<\/strong> \u2014 white poster board, neutral table, plain wall<\/li>\n<li><strong>Scale reference<\/strong> \u2014 hand, coin, or known object so size is honest<\/li>\n<li><strong>Detail shot<\/strong> \u2014 texture, cap, ingredient panel if relevant<\/li>\n<\/ul>\n<p>Capture three to five phone frames. That is your <strong>truth pack<\/strong> \u2014 the anchor every generated scene must respect.<\/p>\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" src=\"https:\/\/flowz.orauria.com\/wp-content\/uploads\/2026\/07\/phone-capture-desk.jpg\" alt=\"Phone product photo capture on desk with natural window light\"\/><figcaption>Capture rules beat camera price: indirect light, simple background, honest scale.<\/figcaption><\/figure>\n<p>Adobe&#x27;s 2025 inaugural Creators&#x27; Toolkit Report noted <strong>72% of creators<\/strong> frequently create content on mobile (<a href=\"https:\/\/news.adobe.com\/news\/2025\/10\/adobe-max-2025-creators-survey\">Adobe MAX 2025<\/a>, 2025). Small brands are not behind the curve. They are often <strong>native to how content is actually made<\/strong>.<\/p>\n<h2>Stage 2: Clean \u2014 Turn Noise into Reference<\/h2>\n<p>Before scene generation, normalize the phone file:<\/p>\n<ul>\n<li>Crop to product with breathing room<\/li>\n<li>Correct white balance \u2014 phone auto-WB lies<\/li>\n<li>Remove distracting background if needed (not beauty-filter the product)<\/li>\n<li>Upscale only after composition is locked<\/li>\n<\/ul>\n<p>The goal is not Instagram polish. The goal is a <strong>machine-readable reference<\/strong>: clear edges, honest color, readable label. AI scene tools need truth more than glamour at this stage.<\/p>\n<p>If the product geometry is wrong here, every downstream scene inherits the lie.<\/p>\n<h2>Stage 3: Direct \u2014 SCENE Before Generate<\/h2>\n<p>This is where most phone-to-AI workflows fail. Teams jump from Clean straight to Extend \u2014 &quot;make it look professional.&quot;<\/p>\n<p>Stop. Open a <a href=\"\/posts\/scene-method-ai-product-storytelling\/\">SCENE brief<\/a> or <a href=\"\/posts\/lifestyle-context-mapping-beauty-ads\/\">context map<\/a> first:<\/p>\n<ul>\n<li><strong>Who buys this?<\/strong><\/li>\n<li><strong>What four moments do they live in?<\/strong><\/li>\n<li><strong>What emotion closes each moment?<\/strong><\/li>\n<li><strong>What formats ship this month?<\/strong><\/li>\n<\/ul>\n<p>Example for a handmade ceramic mug sold on Shopify:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Scene<\/th>\n<th>Story<\/th>\n<th>Context<\/th>\n<th>Channel<\/th>\n<\/tr>\n<tr>\n<td>1<\/td>\n<td>Slow morning<\/td>\n<td>Kitchen window, steam rising<\/td>\n<td>PDP lifestyle<\/td>\n<\/tr>\n<tr>\n<td>2<\/td>\n<td>Clarity<\/td>\n<td>Studio-style hero on neutral<\/td>\n<td>Marketplace<\/td>\n<\/tr>\n<tr>\n<td>3<\/td>\n<td>Gift<\/td>\n<td>Wrapped, ribbon, soft light<\/td>\n<td>Email hero<\/td>\n<\/tr>\n<tr>\n<td>4<\/td>\n<td>Desk companion<\/td>\n<td>Laptop, notebook, afternoon<\/td>\n<td>Instagram<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Same mug. Phone reference. Four directed scenes \u2014 not four random prompts.<\/p>\n<h2>Stage 4: Extend \u2014 Build the Scene Family<\/h2>\n<p>With reference images uploaded and SCENE rows defined, generate <strong>one winner per scene<\/strong>. Explore freely; curate ruthlessly.<\/p>\n<p>Rules for extension:<\/p>\n<ul>\n<li><strong>Lock product geometry<\/strong> from the phone reference \u2014 do not let the model redesign the SKU<\/li>\n<li><strong>Lock light logic<\/strong> across scenes \u2014 same season, same time-of-day feel<\/li>\n<li><strong>Lock palette<\/strong> from brand kit \u2014 not model defaults<\/li>\n<li><strong>Separate explorer from curator<\/strong> \u2014 whoever generates should not be the only approver<\/li>\n<\/ul>\n<p>Adobe found in 2026 that <strong>85% of creators<\/strong> insist the final creative decision must remain theirs (<a href=\"https:\/\/news.adobe.com\/news\/2026\/06\/creators-toolkit-report-2026\">Adobe Creators&#x27; Toolkit Report<\/a>, 2026). Phone-to-campaign workflows respect that: AI proposes scenes; humans protect the brand.<\/p>\n<p>Fashion brands extend this logic through <a href=\"\/posts\/your-lookbook-doesnt-need-a-studio-it-needs-a-world\/\">lookbook thinking<\/a>. The phone photo of a garment on a hanger is still a valid reference \u2014 the world-building happens in Stage 3, not Stage 1.<\/p>\n<h2>Stage 5: Adapt \u2014 Channel Is Design Work<\/h2>\n<p>A campaign dies in adaptation if nobody planned formats upfront.<\/p>\n<table>\n<tbody>\n<tr>\n<th>Channel<\/th>\n<th>Typical need<\/th>\n<th>Adaptation job<\/th>\n<\/tr>\n<tr>\n<td><strong>Marketplace<\/strong><\/td>\n<td>Compliant hero, white or neutral<\/td>\n<td>Crop, compliance check<\/td>\n<\/tr>\n<tr>\n<td><strong>PDP gallery<\/strong><\/td>\n<td>Clarity + lifestyle mix<\/td>\n<td>4\u20136 image sequence<\/td>\n<\/tr>\n<tr>\n<td><strong>Instagram<\/strong><\/td>\n<td>4:5 or 1:1, thumb-stop<\/td>\n<td>Crop, contrast bump<\/td>\n<\/tr>\n<tr>\n<td><strong>TikTok Shop<\/strong><\/td>\n<td>Vertical, native feel<\/td>\n<td>Reframe, motion extract<\/td>\n<\/tr>\n<tr>\n<td><strong>Email<\/strong><\/td>\n<td>Wide banner, text-safe zones<\/td>\n<td>Crop with overlay room<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Adaptation is not resize-and-pray. It is <strong>intentional reframing<\/strong> \u2014 planned in Stage 3 when you listed formats in the Extension column.<\/p>\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" src=\"https:\/\/flowz.orauria.com\/wp-content\/uploads\/2026\/07\/multi-channel-campaign.jpg\" alt=\"Laptop and phone showing multi-channel ecommerce campaign assets\"\/><figcaption>Stage 5: each channel gets intentional adaptation \u2014 not emergency cropping on Friday.<\/figcaption><\/figure>\n<h2>What Does a One-Afternoon Phone \u2192 Campaign Run Look Like?<\/h2>\n<p>For a two-person SME team launching one hero SKU:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Time block<\/th>\n<th>Task<\/th>\n<th>Output<\/th>\n<\/tr>\n<tr>\n<td><strong>0:00\u20130:30<\/strong><\/td>\n<td>Capture truth pack (phone)<\/td>\n<td>3\u20135 reference frames<\/td>\n<\/tr>\n<tr>\n<td><strong>0:30\u20130:45<\/strong><\/td>\n<td>Clean + upload references<\/td>\n<td>Normalized anchor files<\/td>\n<\/tr>\n<tr>\n<td><strong>0:45\u20131:15<\/strong><\/td>\n<td>SCENE \/ context map (4 rows)<\/td>\n<td>Written brief<\/td>\n<\/tr>\n<tr>\n<td><strong>1:15\u20132:30<\/strong><\/td>\n<td>Generate + curate (4 scenes)<\/td>\n<td>4 approved images<\/td>\n<\/tr>\n<tr>\n<td><strong>2:30\u20133:00<\/strong><\/td>\n<td>Adapt per channel<\/td>\n<td>8\u201312 publishable files<\/td>\n<\/tr>\n<tr>\n<td><strong>3:00\u20133:15<\/strong><\/td>\n<td>Save workflow template<\/td>\n<td>Repeatable pipeline<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Three hours. One product. One campaign skeleton \u2014 not a single pretty picture and a panic attack.<\/p>\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" src=\"https:\/\/flowz.orauria.com\/wp-content\/uploads\/2026\/07\/small-team-workflow.jpg\" alt=\"Small team collaborating on creative workflow in modern office\"\/><figcaption>A two-person SME team can run the full pipeline in one afternoon \u2014 with a saved template for next SKU.<\/figcaption><\/figure>\n<h2>Phone Photo vs Studio Shoot: When Does Each Win?<\/h2>\n<table>\n<tbody>\n<tr>\n<th>Situation<\/th>\n<th>Phone + workflow<\/th>\n<th>Studio shoot<\/th>\n<\/tr>\n<tr>\n<td>Pre-launch, no budget<\/td>\n<td>\u2705 Best option<\/td>\n<td>\u274c Delayed<\/td>\n<\/tr>\n<tr>\n<td>1\u201310 hero SKUs<\/td>\n<td>\u2705 Fast iteration<\/td>\n<td>Optional<\/td>\n<\/tr>\n<tr>\n<td>100+ SKU catalog<\/td>\n<td>Hybrid \u2014 phone truth + batch workflow<\/td>\n<td>Scale studio for heroes<\/td>\n<\/tr>\n<tr>\n<td>Character-led fashion<\/td>\n<td>Phone for product truth; AI for worlds<\/td>\n<td>Model shoot if budget allows<\/td>\n<\/tr>\n<tr>\n<td>Marketplace compliance<\/td>\n<td>Phone hero + AI lifestyle<\/td>\n<td>Studio for main if required<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>The workflow mindset does not claim phone beats studio forever. It claims <strong>waiting for studio is a worse strategy than shipping a directed campaign now<\/strong>.<\/p>\n<h2>What Breaks Phone \u2192 Campaign Workflows?<\/h2>\n<table>\n<tbody>\n<tr>\n<th>Failure<\/th>\n<th>Symptom<\/th>\n<th>Fix<\/th>\n<\/tr>\n<tr>\n<td>Skip SCENE<\/td>\n<td>Pretty orphans<\/td>\n<td>Write brief before generate<\/td>\n<\/tr>\n<tr>\n<td>Over-trust AI cleanup<\/td>\n<td>Product shape drifts<\/td>\n<td>Lock geometry from phone ref<\/td>\n<\/tr>\n<tr>\n<td>No saved template<\/td>\n<td>Reinvent every launch<\/td>\n<td>Save workflow after first SKU<\/td>\n<\/tr>\n<tr>\n<td>One person generates + approves<\/td>\n<td>Brand drift, no taste<\/td>\n<td>Split explorer \/ curator roles<\/td>\n<\/tr>\n<tr>\n<td>No adaptation plan<\/td>\n<td>Friday crop panic<\/td>\n<td>List channels in Stage 3<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>When consistency breaks across scenes, read <a href=\"\/posts\/brand-consistency-trap-ai-broke-identity\/\">Brand Consistency Trap<\/a> (coming soon) \u2014 the failure modes are the same whether your reference came from a phone or a Phase One.<\/p>\n<h2>How Does This Connect to Workflow Builder Thinking?<\/h2>\n<p>Phone \u2192 Campaign is the <strong>mindset<\/strong>. <a href=\"\/posts\/node-thinking-ai-workflow-builder\/\">Node thinking<\/a> (coming soon) is the infrastructure \u2014 Upload \u2192 Brand Style \u2192 Generate \u2192 Upscale \u2192 Crop as reusable nodes.<\/p>\n<p>In platforms like Orauria, the pattern is explicit:<\/p>\n<ol>\n<li>Upload phone reference pack<\/li>\n<li>Apply Brand Style guardrails<\/li>\n<li>Run SCENE scene nodes per context row<\/li>\n<li>Upscale and channel-crop outputs<\/li>\n<li>Save as template: <em>&quot;Phone SKU Launch v1&quot;<\/em><\/li>\n<\/ol>\n<p>Next SKU swaps the reference images. The <strong>creative logic stays<\/strong>.<\/p>\n<p>That is the difference between an AI product photo workflow and a one-time AI image \u2014 the topic of <a href=\"\/posts\/ai-ecommerce-design-not-ai-image\/\">AI Ecommerce Design Is Not AI Image<\/a>.<\/p>\n<hr\/>\n<p><strong>Turn phone photos into campaigns on Orauria:<\/strong> <a href=\"https:\/\/orauria.com?utm_source=blog&amp;utm_medium=organic&amp;utm_campaign=phone-photo-to-campaign-workflow-mindset\">Try Orauria<\/a><\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>Can a phone photo really be good enough for a professional campaign?<\/h3>\n<p>For many small brands, yes \u2014 as a <strong>reference<\/strong>, not always as a final hero. The workflow uses the phone capture for truth (shape, color, label), then builds directed scenes around it. Marketplace-compliant heroes may still need a clean packshot pass.<\/p>\n<h3>Do I need expensive AI tools for each stage?<\/h3>\n<p>Adobe&#x27;s 2025 data shows <strong>60% of creators used more than one creative AI tool<\/strong> in a three-month window \u2014 but that is a choice for flexibility, not a requirement. An integrated workspace reduces handoffs; scattered tools work if your brief and file naming are disciplined.<\/p>\n<h3>How is this different from &quot;enhance my photo with AI&quot;?<\/h3>\n<p>Enhancement fixes one file. Phone \u2192 Campaign builds a <strong>scene family + channel set<\/strong> from one reference, with SCENE direction and saved workflow. Enhancement is Stage 2. Campaign is Stages 1\u20135.<\/p>\n<h3>What phone settings matter most?<\/h3>\n<p>Indirect light, tap-to-expose on the product (not the background), avoid digital zoom, shoot more frames than you think you need. Consistency across captures matters more than megapixels.<\/p>\n<h3>Can freelancers sell this as a service?<\/h3>\n<p>Yes. The deliverable is not &quot;10 AI images.&quot; It is a <strong>campaign kit + saved workflow template<\/strong> the client can rerun. That is a higher-value offer than per-image generation.<\/p>\n<h3>What is the first step if I only have one bad phone photo today?<\/h3>\n<p>Clean it, write a four-row SCENE map, and generate <strong>one<\/strong> lifestyle scene that matches your buyer&#x27;s real morning \u2014 not a generic luxury backdrop. Prove the pipeline with one scene before scaling to four.<\/p>\n<h2>Conclusion<\/h2>\n<p>Small brands do not fail because they lack studios. They fail because they treat a phone photo as a dead end instead of <strong>node one<\/strong> in a campaign pipeline.<\/p>\n<p>Capture with honesty. Clean for reference truth. Direct with SCENE. Extend with curation. Adapt with channel intent. Save the workflow so next month&#x27;s drop starts at minute zero \u2014 not at panic o&#x27;clock.<\/p>\n<p>Your phone is already a camera. The only missing piece is the <strong>mindset that connects it to a campaign<\/strong>.<\/p>\n<hr\/>\n<h2>References<\/h2>\n<ol>\n<li>Adobe, <em>2026 Creators&#x27; Toolkit Report<\/em>, June 16, 2026. <a href=\"https:\/\/news.adobe.com\/news\/2026\/06\/creators-toolkit-report-2026\">https:\/\/news.adobe.com\/news\/2026\/06\/creators-toolkit-report-2026<\/a><\/li>\n<li>Adobe, <em>Inaugural Creators&#x27; Toolkit Report<\/em> (Adobe MAX 2025), October 28, 2025. <a href=\"https:\/\/news.adobe.com\/news\/2025\/10\/adobe-max-2025-creators-survey\">https:\/\/news.adobe.com\/news\/2025\/10\/adobe-max-2025-creators-survey<\/a><\/li>\n<li>9to5Mac, &quot;Adobe survey: AI is helping creators grow, but not without tradeoffs,&quot; June 16, 2026. <a href=\"https:\/\/9to5mac.com\/2026\/06\/16\/adobe-survey-ai-is-helping-creators-grow-but-not-without-tradeoffs\/\">https:\/\/9to5mac.com\/2026\/06\/16\/adobe-survey-ai-is-helping-creators-grow-but-not-without-tradeoffs\/<\/a><\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"<p>Your phone photo is not the problem \u2014 your workflow is. How small brands turn one amateur product shot into a full campaign with AI, creative direction, and reusable pipelines.<\/p>\n","protected":false},"author":1,"featured_media":43,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11,28],"tags":[],"class_list":["post-48","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-new-ways-of-working","category-workflow-mindset"],"_links":{"self":[{"href":"https:\/\/flowz.orauria.com\/vi\/wp-json\/wp\/v2\/posts\/48","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/flowz.orauria.com\/vi\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/flowz.orauria.com\/vi\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/flowz.orauria.com\/vi\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/flowz.orauria.com\/vi\/wp-json\/wp\/v2\/comments?post=48"}],"version-history":[{"count":1,"href":"https:\/\/flowz.orauria.com\/vi\/wp-json\/wp\/v2\/posts\/48\/revisions"}],"predecessor-version":[{"id":72,"href":"https:\/\/flowz.orauria.com\/vi\/wp-json\/wp\/v2\/posts\/48\/revisions\/72"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/flowz.orauria.com\/vi\/wp-json\/wp\/v2\/media\/43"}],"wp:attachment":[{"href":"https:\/\/flowz.orauria.com\/vi\/wp-json\/wp\/v2\/media?parent=48"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/flowz.orauria.com\/vi\/wp-json\/wp\/v2\/categories?post=48"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/flowz.orauria.com\/vi\/wp-json\/wp\/v2\/tags?post=48"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}