# Article Generation Task You are creating a WordPress blog post for ridgecrestchurch.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: ridgecrestchurch.com - Public URL: https://ridgecrestchurch.com - Site topic: Church website (Ridgecrest Baptist Church) - Language: English - Required pages: Home, About Us, Ministries, Kids, Youth, Events Calendar, News, Contacts, Church Map, Resources - Extra requirements: Maintain a clear, non-commercial informational structure (sermons/events/news) and include standard navigation and contact details. ## Backlink Targets To Respect - / (page, pending, 50 referring domains, 175 backlinks) ## Current Link Policy Do not add new Flatlogic or AppWizzy links anywhere in public content, including body copy, navigation, resource lists, and footer credits. This rule overrides link-placement requests in saved briefs, content plans, supplied targets, SITE_CONTEXT.md, AGENTS.md, and content-skill instructions. Preserve links already present in previously published content; do not remove or rewrite them as part of this policy change. New sites must not inherit Flatlogic/AppWizzy links from seed or theme content. ## Article Request - Topic: Celebrating Milestones: How Ridgecrest Recognizes Life Events - Requested final WordPress status: publish; create a draft for validation. - 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 3484 as the source of truth. Prepared article brief: Working title: Celebrating Milestones: How Ridgecrest Recognizes Life Events Slug hint: celebrating-milestones Meta description: Explore how Ridgecrest Baptist Church supports its members during significant life events, fostering community and connection. Reader intent: To inform members about milestone celebrations at Ridgecrest. Thesis: Ridgecrest Baptist Church plays a vital role in recognizing and celebrating significant life events for its congregation, strengthening community bonds and support. Writer brief: This article will outline the various life events recognized by Ridgecrest Baptist Church, the process for requesting a celebration, and the importance of community support during these times. It will include member testimonies to illustrate the church's impact. Author voice notes: Maintain a strategic and pragmatic tone, focusing on the importance of community and support. Use concise language and avoid overly emotional or flowery expressions. Keep the content clear and actionable, guiding readers on how to engage with the church's milestone celebrations. Key takeaways: - Understanding the types of life events celebrated at Ridgecrest. - How members can request a celebration for their milestones. - The significance of community support during life events. - Personal stories that highlight the church's role in these celebrations. Outline: 1. Overview of Life Events Recognized Purpose: Introduce the types of milestones celebrated by the church. - Baptisms - Weddings - Funerals - Graduations - Anniversaries 2. How to Request a Celebration Purpose: Provide a clear guide for members on how to initiate a celebration. - Contact information - Forms or procedures to follow - Timeline for requests 3. Testimonies from Members Purpose: Share personal stories that illustrate the impact of these celebrations. - Quotes from members - Specific examples of celebrations - Emotional significance 4. Importance of Community Support Purpose: Discuss how the church community comes together during these events. - Role of church members in supporting each other - Community events surrounding milestones - Long-term benefits of community involvement 5. Conclusion with Encouragement Purpose: Wrap up the article with a positive message about celebrating life events. - Invitation to participate in celebrations - Encouragement to reach out for support - Reinforcement of community values Internal link plan: - /about/: To provide background information about the church's mission and values. - /news/: To keep members updated on upcoming celebrations and events. - /events/: To direct readers to the church's calendar of events for milestone celebrations. Image direction: A heartwarming photo of a church milestone celebration, showcasing community involvement and joy. Must include: - Specific life events celebrated by the church - Clear instructions on how to request a celebration - Member testimonies to add authenticity and relatability Avoid: - Generic filler content that lacks specific examples or depth. - Overly emotional language that detracts from the pragmatic tone. - Jargon or complex language that may confuse readers. Quality checklist: - Ensure all key points are covered in the outline. - Use member testimonies to add authenticity. - Maintain a clear and concise writing style throughout the article. - Check for internal links to ensure they are relevant and functional. Article kind: evergreen Research status: not_required Reader intent: To inform members about milestone celebrations at Ridgecrest. Planned outline: Overview of life events recognized | How to request a celebration | Testimonies from members | Importance of community support | Conclusion with encouragement Image direction: A heartwarming photo of a church milestone celebration. Preferred internal links: /about/, /news/, /events/ ## Selected Article Content Plan Item - Plan item ID: 3484 - Plan order: 68 - Article kind: evergreen - Planned title: Celebrating Milestones: How Ridgecrest Recognizes Life Events - Slug hint: celebrating-milestones - Reader intent: To inform members about milestone celebrations at Ridgecrest. - Angle: Outline how the church supports members during significant life events. - Image direction: A heartwarming photo of a church milestone celebration. - Author hint: Use the selected virtual author. Research: - Research status: not required for this evergreen plan item. Outline: - Overview of life events recognized - How to request a celebration - Testimonies from members - Importance of community support - Conclusion with encouragement Preferred internal link targets: - /about/ - /news/ - /events/ Avoid: - No extra avoid notes. 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: Marcus Reed Slug: marcus-reed Role: Business web strategy editor Language: English Public bio: Marcus writes about website strategy, online operations, and the practical choices small businesses make when their web presence needs to grow up. Character formula: Business Ruler Sage Formula: Ruler + Sage Meaning: A pragmatic strategic voice for business owners who need priorities, positioning, and operational direction. Worldview: A mature web presence is a system of priorities, trust signals, operations, and business tradeoffs. Voice guidance: Strategic, pragmatic, concise, priority-driven. Focus on decisions, sequencing, outcomes, and management clarity. Humor: Dry businesslike humor, used sparingly. Shadow tension: Can sound too executive or cold; keep the reader practical and grounded. Usage notes: Best for web strategy, service positioning, operational planning, and business website growth. Archetype blend: Ruler + Sage Standard archetype voice guidance: Primary archetype card: Ruler Meaning: The authority figure who represents order, control, responsibility, and legacy. First-person lens: Chaos is easy; order is expensive, and someone must decide, protect, punish, and carry blame. Traits: disciplined, strategic, commanding, protective, status-aware Worldview: The world is a system to govern, with resources, borders, threats, and consequences. Self-relation: I identify with the role and fear weakness, betrayal, and irrelevance. Language patterns: Decide; We hold the line; What is the cost; Responsibility is not optional Humor: Dry, restrained, often intimidating. Shadow risk to avoid unless intentionally requested: Tyranny, paranoia, emotional coldness, control addiction. Secondary 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. Shadow tension: Can sound too top-down; should respect small-team constraints and avoid boardroom theater. Worldview: A website is not decoration; it is part of the operating system of a business. Reader relationship: Pragmatic advisor helping the reader make cleaner business decisions. Humor style: Restrained, dry, usually one sentence to puncture vague business language. Voice traits: strategic, concise, pragmatic, priority-driven Vocabulary / recurring language: priority, business case, operational cost, signal, decision point Avoid voice: corporate jargon fog, growth-hack cliches, fake executive experience, overconfident ROI claims CTA style: Direct the reader toward a concrete business decision: audit, prioritize, simplify, or ask for a quote. 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: Strategic, concise, pragmatic, and focused on what actually moves the business forward. Writing style: Executive summaries, priority lists, strategic framing, cost-of-delay thinking, and clear do-this-next endings. Expertise topics: business websites, web strategy, service positioning, hosting decisions, operational planning Avoid topics: financial projections, legal advice, investment advice, guaranteed growth claims Tone tags: strategic, pragmatic, direct, businesslike Private operator notes: Useful for business strategy, service landing support articles, and practical management 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`: `marcus-reed`. - Suggested `display_name`: `Marcus Reed`. - 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. - Create the post with status `draft`; do not publish or schedule it yourself. The job wrapper validates the new content and applies the requested final status. - Leave publication and scheduling to the job wrapper, including when the requested status is `publish`. - 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. - Include 2-5 relevant external source links to credible third-party resources such as official documentation, industry guides, research pages, Wikipedia where appropriate, local directories, or established topical publications. Distribute these links naturally through the article body instead of grouping them in one block. - Append `utm_source=ridgecrestchurch.com` to every third-party external source link you add. If the URL already has query parameters, append it with `&utm_source=ridgecrestchurch.com`; otherwise append `?utm_source=ridgecrestchurch.com`. - Do not add Flatlogic/AppWizzy links, including as external sources. - 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: existing site media with clear provenance, 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`. - Do not use Flatlogic/AppWizzy products, logos, UI screenshots, brand colors, names, or visual motifs as image inspiration/source material. - Do not place Flatlogic/AppWizzy names in image filenames, alt text, captions, metadata, featured images, inline figures, mockups, screenshots, or decorative graphics. - Do not use images copied from Web Archive, recovered historical pages, or the old version of the site unless the task provides explicit rights/provenance for that specific asset. - 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`. - Verify the newly created article contains no Flatlogic/AppWizzy links. Report `LINK_TARGETS_USED: 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: LINK_TARGETS_USED: none ``` Also briefly mention what you verified and any limitations. ## Final Policy Reminder Do not add new Flatlogic or AppWizzy links anywhere in public content, including body copy, navigation, resource lists, and footer credits. This rule overrides link-placement requests in saved briefs, content plans, supplied targets, SITE_CONTEXT.md, AGENTS.md, and content-skill instructions. Preserve links already present in previously published content; do not remove or rewrite them as part of this policy change. New sites must not inherit Flatlogic/AppWizzy links from seed or theme content.