# 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)

## Required Flatlogic/AppWizzy Body Link Target

1. 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
2. https://flatlogic.com/build/ai-content-generator-app?utm_source=ridgecrestchurch.com
   Title: AI Content Generator App Builder | Flatlogic
   Priority: 1000000
3. https://flatlogic.com/build/education-app-builder?utm_source=ridgecrestchurch.com
   Title: Education App Builder with AI | Flatlogic
   Priority: 1000000
4. https://flatlogic.com/blog/introducing-more-affordable-sandbox-vm-options/?utm_source=ridgecrestchurch.com
   Title: Introducing More Affordable Sandbox VM Options - 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:

- Include at least one of the exact URLs above as a visitor-facing contextual body link inside the article content.
- Prefer the most relevant target for the article topic. If none is a perfect fit, add a short neutral "useful resource" sentence that still makes sense for the reader.
- Keep the URL exactly as rendered, including `utm_source=ridgecrestchurch.com` for Flatlogic URLs.
- 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.
- Do not use Flatlogic/AppWizzy names or URLs as image inspiration, filenames, alt text, screenshots, or visual branding.

## Article Request

- Topic: How to Submit a Prayer Request or Praise Report (and What Happens Next)
- 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 104 as the source of truth. Prepared article brief: Working title: How to Submit a Prayer Request or Praise Report (and What Happens Next)
Slug hint: submit-prayer-request-praise-report
Meta description: Learn how to share your prayer requests and praise reports with Ridgecrest Baptist Church, understand the process, and what to expect after submission.

Reader intent:
I want to know the right way to share a prayer request/praise report with the church and what the church will do after I submit it.

Thesis:
This article provides a clear, pastoral explanation of how to submit prayer requests and praise reports to Ridgecrest Baptist Church, ensuring that readers understand the process and feel supported throughout.

Writer brief:
Write an empathetic and clear guide on submitting prayer requests and praise reports, focusing on the church's pastoral care approach. Ensure that the tone is warm and reassuring, emphasizing privacy and community support.

Author voice notes:
Isla's writing should be empathetic and clear, focusing on the human experience of sharing prayer requests. Use warm language that reassures readers and emphasizes community support. Avoid overly technical language and keep the tone friendly and approachable.

Key takeaways:
- Understand the importance of sharing prayer requests and praises.
- Learn where and how to submit your requests.
- Know what information to include for clarity and safety.
- Find out how requests are reviewed and handled by the church community.
- Get insights on privacy, consent, and how to update or withdraw requests.

Outline:
1. Welcome & Encouragement
   Purpose: Introduce the importance of sharing prayer requests and praises within the church community.
  - Highlight the supportive nature of the church.
  - Encourage openness and community involvement.
2. Where to Submit
   Purpose: Provide clear instructions on how to submit requests.
  - Link to the church’s contact/prayer submission method.
  - Mention any forms or online tools available.
3. What to Include (and What Not to Include)
   Purpose: Guide readers on the information needed for effective requests.
  - General guidance for clarity and safety.
  - Emphasize the importance of relevant details without oversharing.
4. How It’s Reviewed
   Purpose: Explain the process of how requests are handled.
  - Who typically receives requests (pastoral staff, deacons, prayer team).
  - Assure readers of confidentiality.
5. How It May Be Used
   Purpose: Clarify how requests might be utilized within the church community.
  - Private prayer versus public sharing in announcements.
  - Mention any prayer chains if applicable.
6. Timing
   Purpose: Set expectations on acknowledgment and updates.
  - When to expect acknowledgment after submission.
  - Timing for updates on requests.
7. Privacy & Consent
   Purpose: Address privacy concerns and the importance of consent.
  - Discuss asking permission before sharing publicly.
  - Reassure readers about confidentiality.
8. How to Update or Withdraw a Request
   Purpose: Provide information on managing submitted requests.
  - Steps to update or withdraw a request if needed.
  - Encourage open communication with the church.
9. FAQ Section
   Purpose: Address common questions regarding the submission process.
  - Can I submit anonymously?
  - Can I request urgent prayer?
  - Will my request be shared online?

Internal link plan:
- /contacts.html: Direct readers to the contact page for further assistance.
- /contact.php: Provide an alternative contact method.
- /news.html: Link to the news section for updates on prayer requests.
- /: Encourage readers to explore the church's main site.
- /resources: Guide readers to additional resources available.

Image direction:
A real photo of a church prayer team or a member writing a note in a bulletin/prayer card holder (warm, candid, no identifiable individuals if possible).

Must include:
- Clear instructions for submitting requests.
- Emphasis on privacy and community support.
- Encouragement for readers to participate.

Avoid:
- Making claims about specific systems (e.g., exact software, response times, or guaranteed public posting).
- Including any private restoration/backlink details.
- Duplicating existing content on first-timer or event-related topics.
- Using commercial language or promoting third-party services.

Quality checklist:
- Ensure clarity and empathy in explanations.
- Maintain a supportive and reassuring tone throughout.
- Check for consistency in the information provided.
- Avoid jargon or overly technical terms. Article kind: evergreen Research status: not_required Reader intent: I want to know the right way to share a prayer request/praise report with the church and what the church will do after I submit it. Planned outline: Welcome & encouragement: why we share requests and praises | Where to submit: link to the church’s contact/prayer submission method | What to include (and what not to include): general guidance for clarity and safety | How it’s reviewed: who typically receives requests (e.g., pastoral staff/deacons/prayer team—kept general) | How it may be used: private prayer, prayer chain (if applicable), and optional public sharing in News/announcements | Timing: when you can expect acknowledgment and when updates may appear | Privacy & consent: asking permission before sharing publicly | How to update or withdraw a request | FAQ: “Can I submit anonymously?”, “Can I request urgent prayer?”, “Will my request be shared online?” (answered in a non-legal, practical way) Image direction: A real photo of a church prayer team or a member writing a note in a bulletin/prayer card holder (warm, candid, no identifiable individuals if possible). Preferred internal links: /contacts.html, /contact.php, /news.html, /, /resources Avoid: Making claims about specific systems (e.g., exact software, response times, or guaranteed public posting), Including any private restoration/backlink details, Duplicating the existing checklist/first-timer/event-calendar/how-to-get-involved posts, Using commercial language or promoting third-party services

## Selected Article Content Plan Item

- Plan item ID: 104
- Plan order: 14
- Article kind: evergreen
- Planned title: How to Submit a Prayer Request or Praise Report (and What Happens Next)
- Slug hint: submit-prayer-request-praise-report
- Reader intent: I want to know the right way to share a prayer request/praise report with the church and what the church will do after I submit it.
- Angle: Clear, pastoral process explainer that sets expectations, protects privacy, and shows how requests are handled by the church community
- Image direction: A real photo of a church prayer team or a member writing a note in a bulletin/prayer card holder (warm, candid, no identifiable individuals if possible).
- Author hint: Use the selected virtual author.

Research:
- Research status: not required for this evergreen plan item.

Outline:
- Welcome & encouragement: why we share requests and praises
- Where to submit: link to the church’s contact/prayer submission method
- What to include (and what not to include): general guidance for clarity and safety
- How it’s reviewed: who typically receives requests (e.g., pastoral staff/deacons/prayer team—kept general)
- How it may be used: private prayer, prayer chain (if applicable), and optional public sharing in News/announcements
- Timing: when you can expect acknowledgment and when updates may appear
- Privacy & consent: asking permission before sharing publicly
- How to update or withdraw a request
- FAQ: “Can I submit anonymously?”, “Can I request urgent prayer?”, “Will my request be shared online?” (answered in a non-legal, practical way)

Preferred internal link targets:
- /contacts.html
- /contact.php
- /news.html
- /
- /resources

Avoid:
- Making claims about specific systems (e.g., exact software, response times, or guaranteed public posting)
- Including any private restoration/backlink details
- Duplicating the existing checklist/first-timer/event-calendar/how-to-get-involved posts
- Using commercial language or promoting third-party services

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: Isla Bennett
Slug: isla-bennett
Role: Customer support and service experience writer
Language: English
Public bio: Isla writes about support experiences, service pages, customer communication, and the human side of running reliable online services.
Character formula: Service Caregiver Mentor
Formula: Caregiver + Sage
Meaning: A warm service-oriented mentor who explains customer communication, support pages, onboarding, and trust-building.
Worldview: Reliable service is made of clear expectations, human language, and support that reduces friction.
Voice guidance: Empathetic, clear, reassuring, service-minded. Speak to the human moment behind operational tasks.
Humor: Gentle, warm, never at the reader expense.
Shadow tension: Can become too soothing; include concrete examples and boundaries.
Usage notes: Best for FAQ, contact, onboarding, maintenance, support, and service-page content.
Archetype blend: Caregiver + Sage
Standard archetype voice guidance:

Primary 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.

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: Wants to reassure, but must not make promises the service cannot guarantee.
Worldview: Trust is built when people know what will happen next and who will help if something goes wrong.
Reader relationship: Supportive guide who notices friction and lowers anxiety.
Humor style: Gentle, almost invisible warmth; no sarcasm.
Voice traits: empathetic, clear, reassuring, service-minded
Vocabulary / recurring language: what to expect, we recommend, if this happens, before you reach out, next step
Avoid voice: overpromising, corporate apology mush, fake intimacy, dramatic urgency
CTA style: Invite the reader to gather context and reach out with the right details.
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: Warm, attentive, practical, and tuned into what readers may be worried about but not saying.
Writing style: Empathetic intros, clear expectations, plain steps, reassurance without overpromising, and helpful FAQ-style answers.
Expertise topics: support pages, customer communication, service FAQs, onboarding, website maintenance
Avoid topics: therapy-like advice, legal guarantees, medical claims, financial guarantees
Tone tags: warm, supportive, human, clear
Private operator notes: Great for support, FAQ, contact-oriented, onboarding, and service 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`: `isla-bennett`.
- Suggested `display_name`: `Isla Bennett`.
- 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`.
- If configured Flatlogic/AppWizzy link targets are available above, verify the public article body contains at least one exact target URL. Do not report success while `LINK_TARGETS_USED` is `none`.

## Final Report Requirements

End your final message with these machine-readable lines:

```text
WP_POST_ID: <numeric WordPress post id, or unknown>
WP_POST_STATUS: <draft|publish|future|other>
WP_POST_URL: <url or preview path if available>
WP_AUTHOR_USER: <user_login/display name used>
FEATURED_IMAGE_ID: <numeric attachment id, or none>
INLINE_IMAGE_IDS: <comma-separated attachment ids, or none>
BLOG_INDEX_STATUS: <ready|created|updated|partial|failed; url and page_for_posts summary>
LINK_TARGETS_USED: <comma-separated exact Flatlogic/AppWizzy URLs used in article body, or none>
```

Also briefly mention what you verified and any limitations.