You are the implementation agent in a non-interactive Codex loop. Work only inside the provided context directory. Make reasonable assumptions, implement directly, and do not ask follow-up questions. When finished, summarize what changed and mention any remaining risks or uncertainty. Context directory: /home/ubuntu/apps/ridgecrestchurch.com Instruction file: /home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/task.md Iteration: 0 # 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) ## Optional Flatlogic/AppWizzy Body Link Target 1. https://flatlogic.com/build/insurance-claims-management-software-builder?utm_source=ridgecrestchurch.com Title: Insurance Claims Management Software Builder | Flatlogic Priority: 1000000 2. https://flatlogic.com/build/legal-case-management-software-builder?utm_source=ridgecrestchurch.com Title: Legal Case Management Software Builder | Flatlogic Priority: 1000000 3. https://flatlogic.com/blog/ai-web-app-builders-production-is-the-bottleneck/?utm_source=ridgecrestchurch.com Title: AI Web App Builders Made Building Easy, Production Is the Bottleneck - Flatlogic Blog Priority: 1000000 4. https://flatlogic.com/blog/are-ai-web-builders-the-new-website-templates/?utm_source=ridgecrestchurch.com Title: Are AI Web Builders Becoming the New Website Templates? - Flatlogic Blog Priority: 1000000 5. https://flatlogic.com/generator?utm_source=ridgecrestchurch.com Title: AI Web Application Generator & App Builder | Flatlogic Priority: 1 Anchor guidance: link to this page as: "web app generator", "AI web app generator", "web app builder", "AI web app builder", etc Link placement requirement: - Use at most one of the exact URLs above as a visitor-facing contextual body link inside the article content. - Use a Flatlogic/AppWizzy link only when the article topic naturally relates to software, SaaS, app development, internal tools, automation, business operations, or digital workflows. - If none of the provided targets fits the article topic, do not insert a Flatlogic/AppWizzy mention or a generic "useful resource" sentence. - Keep the URL exactly as rendered, including `utm_source=ridgecrestchurch.com` for Flatlogic URLs. - Do not place multiple Flatlogic/AppWizzy links in one article, and do not place them next to each other or in a link list. - Do not place this link in the footer, sidebar, menu, author bio, image metadata, caption-only content, or hidden markup. - Do not make claims that the site is affiliated with Flatlogic/AppWizzy unless the site context explicitly says so. - Mention Flatlogic/AppWizzy only in neutral third-person language. Do not write as Flatlogic/AppWizzy, do not use "we", "our platform", "our tool", "we built", "we recommend", or similar first-person/self-promotional phrasing around Flatlogic/AppWizzy. - Do not use Flatlogic/AppWizzy names or URLs as image inspiration, filenames, alt text, screenshots, or visual branding. ## Article Request - Topic: How to Prepare a Prayer Request for Ridgecrest (A Simple, Respectful Template) - 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 112 as the source of truth. Prepared article brief: Working title: How to Prepare a Prayer Request for Ridgecrest (A Simple, Respectful Template) Slug hint: how-to-prepare-prayer-request-template Meta description: Learn how to write a meaningful prayer request for Ridgecrest Baptist Church with this practical template and guidance. Reader intent: Help readers write a meaningful prayer request quickly and appropriately, and understand what happens after they submit it. Thesis: Providing a clear template and do/don’t guidance will empower church members to submit prayer requests that are respectful and easy for the church to respond to. Writer brief: Create a practical guide that helps readers understand how to prepare a prayer request for Ridgecrest Baptist Church. The article should be structured to provide a clear template and specific do’s and don’ts to ensure requests are respectful and effective. Emphasize clarity and appropriateness in communication. Author voice notes: Maintain a strategic and pragmatic tone throughout the article. Focus on clarity and actionable guidance. Use concise language and avoid overly emotional expressions. Keep the reader grounded in practical steps they can take. Key takeaways: - Understanding the importance of context in prayer requests - A copy/paste template for easy submission - Essential do's and don'ts for writing requests - Guidance on phrasing requests for healing or support - Instructions on submission and what to expect afterwards Outline: 1. Why We Ask for a Little Context Purpose: Explain the importance of providing context in prayer requests for effective prayer support. - Helps the prayer team pray specifically - Ensures requests are handled appropriately - Builds a sense of community and support 2. A Quick Template You Can Copy/Paste Purpose: Provide a practical template for readers to use when submitting their requests. - Name: [Your Name] - Request: [Brief description of your request] - Details: [Any specific details to include] - Timeframe: [When you need support] - Ongoing vs. One-time: [Specify if this is a recurring request] - Sharing Preference: [Public or private prayer] 3. Do Include: Purpose: List the essential elements that should be included in a prayer request. - Clarity in the request - Specific needs and relevant dates - Confidentiality preferences 4. Don’t Include: Purpose: Highlight what should be avoided in prayer requests. - Overly personal details - Anything uncomfortable to share publicly 5. If You’re Requesting Healing, Guidance, or Comfort Purpose: Provide example prompts for wording requests in sensitive situations. - Use compassionate language - Be clear about the type of support needed - Examples of phrasing requests 6. If You’re Submitting for Someone Else Purpose: Guide readers on how to phrase requests for others while respecting their privacy. - Mention the relationship to the person - Ensure consent is obtained before submitting 7. Sharing Preferences Purpose: Explain the difference between public prayer and private requests. - What to choose based on comfort level - Implications of each choice 8. How to Submit Purpose: Direct readers on how to submit their prayer requests and what to expect afterwards. - Link to the church’s prayer request/contact path - Outline the process after submission - Encouragement to keep praying while waiting 9. Closing: Encouragement Purpose: Provide a final note of encouragement to readers. - Reinforce the importance of prayer - Encourage ongoing communication with the church Internal link plan: - /contacts.html: Direct readers to the contact page for more information. - /contact.php: Provide an alternative contact method for prayer requests. - /contact.htm: Ensure all contact options are available. - /news.html: Link to updates that may be relevant to prayer requests. - /resources: Guide readers to additional resources for prayer and support. Image direction: A real photo of a person writing on a notepad or using a phone to draft a message (generic, non-identifying), plus a small inset photo of an open Bible or a prayer journal on a table. Must include: - Clear template for prayer requests - Do's and Don'ts for effective communication - Instructions on how to submit requests Avoid: - Duplicating content from the planned 'How to Submit a Prayer Request or Praise Report (and What Happens Next)' article - Guaranteeing response times or specific outcomes - Including unverifiable claims about who will see the request Quality checklist: - Ensure clarity and conciseness in language - Maintain a respectful tone throughout - Follow the structured outline closely - Include actionable steps for the reader Article kind: evergreen Research status: not_required Reader intent: Help readers write a meaningful prayer request quickly and appropriately, and understand what happens after they submit it. Planned outline: Why we ask for a little context (so our prayer team can pray specifically) | A quick template you can copy/paste (Name, Request, Details, Timeframe, Ongoing vs. one-time, Sharing preference) | Do include: clarity, specific needs, relevant dates, and whether it’s confidential | Don’t include: overly personal details, anything you’re not comfortable sharing publicly | If you’re requesting healing, guidance, or comfort: example prompts for wording | If you’re submitting for someone else: how to phrase relationship and consent | Sharing preferences: public prayer vs. private request (what to choose) | How to submit (link to the church’s prayer request/contact path) and what to expect after you send it | Closing: encouragement and how to keep praying while you wait Image direction: A real photo of a person writing on a notepad or using a phone to draft a message (generic, non-identifying), plus a small inset photo of an open Bible or a prayer journal on a table. Preferred internal links: /contacts.html, /contact.php, /contact.htm, /news.html, /resources Avoid: Duplicate the planned “How to Submit a Prayer Request or Praise Report (and What Happens Next)” topic, Guarantee response times or specific outcomes, Include any unverifiable claims about who will see the request or how quickly it will be prayed over ## Selected Article Content Plan Item - Plan item ID: 112 - Plan order: 22 - Article kind: evergreen - Planned title: How to Prepare a Prayer Request for Ridgecrest (A Simple, Respectful Template) - Slug hint: how-to-prepare-prayer-request-template - Reader intent: Help readers write a meaningful prayer request quickly and appropriately, and understand what happens after they submit it. - Angle: Provide a clear, practical template and do/don’t guidance so people know what to include and how to phrase requests in a way that’s easy for the church to respond to. - Image direction: A real photo of a person writing on a notepad or using a phone to draft a message (generic, non-identifying), plus a small inset photo of an open Bible or a prayer journal on a table. - Author hint: Use the selected virtual author. Research: - Research status: not required for this evergreen plan item. Outline: - Why we ask for a little context (so our prayer team can pray specifically) - A quick template you can copy/paste (Name, Request, Details, Timeframe, Ongoing vs. one-time, Sharing preference) - Do include: clarity, specific needs, relevant dates, and whether it’s confidential - Don’t include: overly personal details, anything you’re not comfortable sharing publicly - If you’re requesting healing, guidance, or comfort: example prompts for wording - If you’re submitting for someone else: how to phrase relationship and consent - Sharing preferences: public prayer vs. private request (what to choose) - How to submit (link to the church’s prayer request/contact path) and what to expect after you send it - Closing: encouragement and how to keep praying while you wait Preferred internal link targets: - /contacts.html - /contact.php - /contact.htm - /news.html - /resources Avoid: - Duplicate the planned “How to Submit a Prayer Request or Praise Report (and What Happens Next)” topic - Guarantee response times or specific outcomes - Include any unverifiable claims about who will see the request or how quickly it will be prayed over 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. - 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. - 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 count Flatlogic/AppWizzy links as the required third-party external source links. - 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`. - 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 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`. - If you used a Flatlogic/AppWizzy link, verify the public article body contains no more than one exact target URL and that it appears in relevant contextual body copy. `LINK_TARGETS_USED` may be `none` when no target fit the article topic. ## 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: ``` Also briefly mention what you verified and any limitations.