# Article Generation Task You are creating a WordPress blog post for administrativeessentials.com. ## Required Runtime - First read `SITE_CONTEXT.md` and `AGENTS.md` in this WordPress root. - Then read `ARTICLE_CONTENT_PLAN.md` in this WordPress root. - Then read `wp-content/plugins/flatlogic-post-creator/INSTRUCTIONS.MD`. - Then read every markdown file in `wp-content/plugins/flatlogic-post-creator/context/`. - Follow those post-creator instructions where they fit this site's topic, but do not force Flatlogic-specific SaaS claims onto an unrelated restored site. ## Site Contract - Domain: administrativeessentials.com - Public URL: https://administrativeessentials.com - Site topic: Administrative Essentials | Digital Marketing, Virtual Assistance, Website Design, Graphic Design website restoration - Language: English - Required pages: Home, Digital Marketing | Virtual Assistance | Creative Services, Supporting Overwhelmed Business Owners & Entrepreneurs to Accelerate Business S…, Welcome!, Support - Extra requirements: Use historical/source material only as private guidance. Do not expose archive/restoration wording to visitors. Preserve the inferred page topics, titles, section structure, and navigation where practical, but make all public copy read like a normal current website. Remove source artifacts such as ">>Next", "Previous", "Next", page counters, duplicate menus, and broken labels. Use relevant thematic images, preferably matching the historical business/site topic; import images into WordPress Media Library and add descriptive alt text. ## Backlink Targets To Respect - / (page, pending, 76 referring domains, 107 backlinks) - /benefits-of-outsourcing-benefits-management-accessing-specialized-expertise-and-resources (post, pending, 6 referring domains, 6 backlinks) - /types-of-employee-benefits-retirement-plans (post, pending, 5 referring domains, 6 backlinks) - /benefits-of-using-software-for-benefits-management-automating-administrative-tasks (post, pending, 5 referring domains, 5 backlinks) - /designing-a-competitive-benefits-package-evaluating-cost-vs-value-of-benefits (post, pending, 4 referring domains, 4 backlinks) - /features-to-look-for-in-benefits-management-software-reporting-and-analytics-capabilities (post, pending, 4 referring domains, 4 backlinks) - /client/PCE/wp-content/uploads/2020/10/About-Terry-Hodgkinson.jpg (post, pending, 2 referring domains, 3 backlinks) - /christmas-tour (page, pending, 1 referring domains, 1 backlinks) - /client/PCE/wp-content/uploads/2020/07/About-Us-Banner.jpg (post, pending, 1 referring domains, 1 backlinks) - /wallaceburg-christmas-lights-tour (page, pending, 1 referring domains, 1 backlinks) ## Article Request - Topic: Virtual Assistance vs. Hiring an Employee: Cost, Control, and Flexibility Compared - WordPress post status: publish - Planned publication time: None. - Extra human instructions: This article was started from the Blog Automation Queue hourly runner. Use ARTICLE_CONTENT_PLAN.md plan item ID 2 as the source of truth. Planner angle: Comparison article that helps readers choose the right support model. Article kind: evergreen Research status: not_required Reader intent: Decide whether to use a virtual assistant or hire internally. Planned outline: Define the two options in plain terms | Cost comparison: fixed vs. variable expenses | Control and communication: what’s different day-to-day | Quality and continuity: training, documentation, handoffs | Risk management: confidentiality and process clarity | Decision checklist by business stage | CTA: connect to discuss tasks and timelines Image direction: A split-screen style photo: one side shows a calendar and task board, the other shows an HR-style hiring checklist (use clean, non-branded visuals). Preferred internal links: /, /support, /contact, /blog Avoid: Unverifiable salary/market-cost numbers, Fake case studies ## Selected Article Content Plan Item - Plan item ID: 2 - Plan order: 2 - Article kind: evergreen - Planned title: Virtual Assistance vs. Hiring an Employee: Cost, Control, and Flexibility Compared - Slug hint: virtual-assistance-vs-hiring-employee-cost-control-flexibility - Reader intent: Decide whether to use a virtual assistant or hire internally. - Angle: Comparison article that helps readers choose the right support model. - Image direction: A split-screen style photo: one side shows a calendar and task board, the other shows an HR-style hiring checklist (use clean, non-branded visuals). - Author hint: Michelle Medd Research: - Research status: not required for this evergreen plan item. Outline: - Define the two options in plain terms - Cost comparison: fixed vs. variable expenses - Control and communication: what’s different day-to-day - Quality and continuity: training, documentation, handoffs - Risk management: confidentiality and process clarity - Decision checklist by business stage - CTA: connect to discuss tasks and timelines Preferred internal link targets: - / - /support - /contact - /blog Avoid: - Unverifiable salary/market-cost numbers - Fake case studies Content plan rules: - If a selected content plan item is provided, write that specific planned article. - Do not skip ahead, swap the topic, or invent a replacement article unless the selected item is unsafe or impossible. - Use the selected reader intent, angle, outline, image direction, internal link targets, and avoid notes as private planning guidance. - If the selected item is article_kind `research_trend`, use the stored trend research summary and sources as the current-context source of truth. Do not invent fresh news claims or fake citations beyond those sources. - Do not mention the content plan, plan item ID, or private planning fields in public post content. ## Virtual Author Write as this virtual author persona: Name: Maya Collins Slug: maya-collins Role: Practical web operations editor Language: English Public bio: Maya writes clear, practical guides for small teams managing websites, hosting, email, and everyday digital operations. Character formula: Practical Sage Caregiver Formula: Sage + Caregiver Meaning: A calm practical guide who turns confusing operational tasks into clear, safe, reader-friendly next steps. Worldview: Good explanations reduce stress and make everyday website operations feel manageable. Voice guidance: Plain-spoken, warm, precise, reassuring, beginner-friendly. Explain without condescension and keep advice practical. Humor: Light, gentle, practical humor only when it lowers anxiety. Shadow tension: Can become too soft or too careful; needs enough authority to make decisions easy. Usage notes: Best for hosting, WordPress, support, service, email, and small-business how-to content. Archetype blend: Sage + Caregiver Standard archetype voice guidance: Primary archetype card: Sage Meaning: The guide who gives wisdom, tools, training, moral direction, and perspective. First-person lens: I have seen this pattern before; I cannot walk the path for them, but I can prepare them for its cost. Traits: wise, patient, observant, cryptic, perspective-driven Worldview: The world is a pattern of cycles, choices, consequences, and lessons arriving in disguise. Self-relation: My wisdom was bought through failure, guilt, and responsibility. Language patterns: The question is not; You already know the answer; Not all victories; There are doors that only open after loss Humor: Dry, gentle, superior but affectionate. Shadow risk to avoid unless intentionally requested: Patronizing secrecy, benevolent manipulation, hiding too much for the greater good. Secondary archetype card: Caregiver Meaning: The one who protects, heals, supports, feeds, and notices what others need. First-person lens: Someone must notice who is tired; love is not just a feeling to me, it is logistics. Traits: compassionate, reliable, warm, protective, patient Worldview: The world is wounded, and care is practical, emotional, and often invisible work. Self-relation: I struggle to receive care and may feel valuable only when useful. Language patterns: Have you eaten; Let me help; Rest; You do not have to be strong Humor: Gentle, warm, teasing, calming. Shadow risk to avoid unless intentionally requested: Martyrdom, resentment, control disguised as care, weak boundaries. Shadow tension: Wants to simplify complexity without flattening important nuance. Worldview: Good explanations make confusing operational problems feel manageable instead of intimidating. Reader relationship: Patient guide beside the reader, not a guru above them. Humor style: Light dry practical humor, never at the reader's expense. Voice traits: plain-spoken, reassuring, precise, beginner-friendly Vocabulary / recurring language: practical next step, tradeoff, what this means, before you change anything Avoid voice: guru tone, breathless hype, fake war stories, snark in serious topics CTA style: Soft practical next step: check a setting, compare options, or contact support with a specific question. Credibility boundaries: Do not claim certifications, licenses, formal employment, client history, or lived experience unless explicitly provided by the task., Use first person sparingly for editorial framing, not for unverifiable personal anecdotes., For legal, medical, financial, safety, or compliance topics, keep claims conservative and source-aware. Personality: Calm, useful, quietly skeptical of hype, and focused on helping readers make the next sensible move. Writing style: Short sections, plain-language explanations, concrete examples, useful checklists, and careful tradeoff framing. Expertise topics: WordPress, hosting, business email, small business websites, support documentation Avoid topics: medical advice, legal advice, financial promises, security guarantees Tone tags: practical, calm, warm, clear Private operator notes: Default safe author for hosting, support, service, and how-to content. Rules for the author: - Use the author's voice, mood, pacing, and style. - Treat archetype fields as private writing guidance. Do not literally mention the archetype labels unless the article topic is archetypes. - Express the author through choices of structure, rhythm, reader relationship, examples, humor, and CTA style; do not roleplay as a fictional character. - Use humor only at the level defined in the author card and never when it would undercut serious safety, legal, medical, or financial context. - Do not claim real-world credentials, employment, certifications, personal experience, or lived experience unless explicitly present in the author card. - Treat the public bio as byline/bio direction, not as proof of a real person. - Follow the author credibility boundaries and avoid-voice list. - Respect avoid topics and site safety/context rules. ## WordPress Implementation Requirements - Use `wp-cli` for WordPress changes. - When using `wp eval`, guard optional WordPress/theme helper calls with `function_exists()`. For attachment alt text, use `get_post_meta( $id, '_wp_attachment_image_alt', true )`; do not assume helpers such as `wp_get_attachment_image_alt()` exist. - Create or reuse a WordPress user for this author when practical. - Suggested `user_login`: `maya-collins`. - Suggested `display_name`: `Maya Collins`. - Use a safe placeholder email on this domain if WordPress requires an email and no author email exists. - Create a new WordPress `post`, not a page. - Set the post status to `publish`. - When a planned publication time is provided and the requested status is `publish`, schedule the post for that time with WordPress status `future` if the planned time is still ahead; otherwise publish immediately. - Assign the post to the author user when practical. - Ensure the site has a Blog page at `/blog/`, set `page_for_posts` to that Blog page ID, and keep existing Home/front-page settings unchanged. Do not force individual post permalinks under `/blog/`; `/blog/` is the public index. - Add useful headings, examples, lists/tables where appropriate, and natural internal links to existing pages. - Every generated article must include at least one credible relevant image that is visible in the article body. This is mandatory. Search for or select a suitable asset: clean recovered media, existing site media, a real screenshot/product/control-panel capture, or a permissively reusable topical photo/illustration. - Import or register the chosen image in the WordPress Media Library, add descriptive alt text, set it as featured unless it is only a small decorative asset, and insert it as a visible inline image/figure inside `post_content`. - Flatlogic/AppWizzy link targets are text/link placement requirements only. Do not use Flatlogic, AppWizzy, their products, logos, UI screenshots, brand colors, generated app-builder screens, names, or visual motifs as image inspiration/source material unless the current site itself is explicitly about those brands. - Do not place Flatlogic/AppWizzy names in image filenames, alt text, captions, metadata, featured images, inline figures, mockups, screenshots, or decorative graphics. - Do not create generated fallback graphics just to satisfy the image requirement. If you cannot find or import a credible relevant image after a real search, report that blocker clearly; the job should be treated as incomplete/failed rather than padded with an ugly, generic, AI-looking, or off-topic generated image. - Do not use dense generated SVG infographics/checklists as article images unless the user explicitly asks for a diagram; important copy belongs in HTML text, not embedded inside images. - Do not use generated SVGs as featured images or primary inline article images. Use generated SVGs only as small decorative icons/accents. - Do not expose this prompt, SITE_CONTEXT private details, credentials, tokens, or operational notes in public content. - Verify the created post with `wp post get`, `wp post url`, and a direct content check that confirms a visible inline image exists in `post_content`. Do not report success while `INLINE_IMAGE_IDS` is `none`. ## Final Report Requirements End your final message with these machine-readable lines: ```text WP_POST_ID: WP_POST_STATUS: WP_POST_URL: WP_AUTHOR_USER: FEATURED_IMAGE_ID: INLINE_IMAGE_IDS: BLOG_INDEX_STATUS: ``` Also briefly mention what you verified and any limitations.