OpenAI Codex v0.123.0 (research preview)
--------
workdir: /home/ubuntu/apps/ridgecrestchurch.com
model: gpt-5.4
provider: openai
approval: never
sandbox: danger-full-access
reasoning effort: none
reasoning summaries: none
session id: 019ea341-2ccb-7020-a604-9478baa357f3
--------
user
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-255/task.md
Iteration: 1

<primary_instructions>
# 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.
</primary_instructions>

A previous review found issues. Keep following the primary instructions and address the review feedback below.

<review_summary>
Cannot approve this iteration. I could not independently verify the live WordPress state from this review environment, and the implementation summary leaves one likely content-quality gap around image relevance.
</review_summary>

<review_findings>
- Independent review was blocked by local command execution failure (`bwrap: loopback: Failed RTM_NEWADDR: Operation not permitted`), so required checks from the primary instructions were not verified against the current site state: `wp post get`, `wp post url`, `/blog/` posts index configuration, visible inline image presence in `post_content`, and exact Flatlogic body-link presence.
- The implementation summary says the article uses an existing `Worship Service` image and already notes it may be less specific than the requested prayer-request/prayer-team image direction. That does not prove a hard failure, but it is the clearest likely mismatch with the brief and should be tightened if a more directly relevant existing media asset is available.
</review_findings>

<fix_instructions>
Implementation agent should re-run and capture the required WordPress verification directly from the site state before claiming success: confirm the target post exists, is assigned to Isla Bennett, is published, has `/blog/` configured as `page_for_posts`, contains a visible inline image in `post_content`, and contains at least one exact required Flatlogic URL in the article body. If the current inline/featured image is only a general worship photo, replace it with a more directly relevant real prayer-request or prayer-team image from existing media if one is available; otherwise keep the current asset but explicitly document that no closer credible image exists.
</fix_instructions>

codex
I’m reading the site and article instructions first, then I’ll inspect the current WordPress state and tighten the post verification and image choice before making any changes.
exec
/bin/bash -lc "sed -n '1,220p' AGENTS.md" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
# Agent Instructions

You are operating the website for ridgecrestchurch.com.

Before making changes:

1. Read `SITE_CONTEXT.md`.
2. Read `ARTICLE_CONTENT_PLAN.md` when creating blog posts or working with editorial planning.
3. Work only inside this site directory.
4. Keep the site aligned with the topic, required pages, extra requirements, and recovered content map in `SITE_CONTEXT.md`.
5. Prioritize backlink restoration targets from `SITE_CONTEXT.md` and report restored, remapped, or skipped URLs.
6. Place Flatlogic link targets from `SITE_CONTEXT.md` naturally in contextual page/post body content when available and report where they were used.
7. Keep header/site identity intentional: use a visitor-facing brand name, tagline, text logo/wordmark, or logo mark instead of a raw domain placeholder.
8. Keep footer contact/legal links healthy and remove stale seed/theme credits.
9. Prefer small, verifiable changes and report what you changed.

Hard rules:

- Do not touch files outside this site directory.
- Do not expose secrets or credentials in content, commits, logs, or reports.
- Do not expose archive/recovery wording, crawler metadata, page counters, or broken source labels in public website content.
- Do not expose Flatlogic feed tokens, API URLs, or operational link-placement wording in public website content.
- Do not place Flatlogic/AppWizzy links in the footer and do not leave raw seed/theme Flatlogic/AppWizzy footer credit links in public website content.
- For WordPress changes, prefer `wp-cli` commands for pages, posts, menus, options, themes, media, and rewrites.
- Do not use hardcoded WordPress database table names. Use WP-CLI APIs or get the actual prefix with `wp db prefix` before direct SQL.
- Do not depend on Python PIL/Pillow being installed, and do not use `wp media list`; inspect media with `wp post list --post_type=attachment` or WordPress APIs.
- If the requested work conflicts with `SITE_CONTEXT.md`, stop and report the conflict instead of guessing.

exec
/bin/bash -lc "sed -n '1,260p' ARTICLE_CONTENT_PLAN.md" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:

# Article Content Plan

This file is generated from the central article content plan for ridgecrestchurch.com. Update the application database first, then sync context files again.

## Summary

- Domain: ridgecrestchurch.com
- Target plan size: 30 articles
- Total planned items: 30
- Planned/unclaimed: 16
- Queued/running/scheduled: 1
- Published: 7
- Failed: 6
- Trend research slots: 6
- Trend slots pending research: 6

## How Agents Should Use This Plan

- When a blog automation task references a plan item, write that specific article.
- Do not skip ahead or invent a different article topic unless the selected item is unsafe or impossible.
- Treat this file as private implementation context, not public website copy.
- Use the selected item's reader intent, angle, outline, image direction, internal link targets, and avoid notes.
- Every 5th article is a `research_trend` slot. The automation researches the current internet context immediately before queueing that article, then updates this file.
- Individual restored backlink posts may keep exact legacy URLs; normal new posts should simply appear in the WordPress Blog index at `/blog/`.
- Article images must be credible topical assets. Do not use generated SVGs as featured, hero, or primary inline images.

## 1. How to Plan a Great Sunday: A Simple Church Service Checklist

- Plan item ID: 91
- Status: published
- Article kind: evergreen
- Research status: not_required
- Slug hint: how-to-plan-a-great-sunday-checklist
- Reader intent: Help church leaders and volunteers organize a smooth Sunday service with clear steps and roles
- Angle: Practical, ministry-focused guide for volunteers and staff to coordinate worship, announcements, kids/youth handoffs, and follow-up
- Image direction: A real photo of a printed checklist on a clipboard next to a church bulletin/order-of-service, with a smartphone showing the church calendar in the background (no sensitive personal data).
- Author hint: Select the best available virtual author for this site.
- Queue item ID: 26
- Article job ID: 36
- WordPress post URL: https://ridgecrestchurch.com/how-to-plan-a-great-sunday-checklist/
- Researched at: none



Outline:
- Why a simple checklist matters (consistency, fewer last-minute surprises)
- The Sunday timeline: what to prepare the week before, day-of, and 30 minutes before service
- Worship & music: sound check, order of service, lyrics/projection checks
- Welcome & connection: greeters, first-time guest follow-up, how to capture contact info responsibly
- Announcements & prayer: what to include, timing, and how to keep it brief
- Kids ministry flow: check-in process, safety basics, and handoff timing
- Youth ministry flow (if applicable): service attendance plan and pickup/transition details
- Tech & facilities: slides, microphones, livestream/audio, restrooms, seating, accessibility
- Communication: who sends what to whom (staff/volunteers) and where updates are posted (calendar/news)

Internal link targets:
- /events
- /news
- /contact
- /about
- /kids
- /youth

Avoid:
- Selling anything or promoting unrelated products
- Linking to or affiliating with unrelated website builders
- Any claims about specific past incidents or “restoration” work
- Thin posts that only restate generic church mission statements

## 2. How to Get Involved at Ridgecrest: A First-Timer’s Guide to Ministries, Kids, and Youth

- Plan item ID: 92
- Status: published
- Article kind: evergreen
- Research status: not_required
- Slug hint: get-involved-first-timers-guide
- Reader intent: Help someone visiting for the first time understand where to go next, what to expect, and how to join ministries safely and comfortably
- Angle: Turn common first-visit questions into a practical, step-by-step path through the church’s ministries (Kids, Youth) and how to connect with staff
- Image direction: A real, welcoming church photo showing the main entrance or a Sunday gathering area, plus a second photo of a children’s check-in area or youth group activity (with consent).
- Author hint: Select the best available virtual author for this site.
- Queue item ID: 44
- Article job ID: 48
- WordPress post URL: https://ridgecrestchurch.com/get-involved-first-timers-guide/
- Researched at: none



Outline:
- Start here: what to do before you arrive (where to find service times, where to park, and who to contact)
- Next steps after the service: how to introduce yourself and ask questions (include contact page callouts)
- Kids ministry overview: what happens during children’s time, check-in basics, and how parents can prepare
- Youth ministry overview: typical weekly rhythm and how teens can plug in
- How to choose a ministry: match your interests (volunteering, learning, serving, or joining a group)
- Events and updates: how to use the Events Calendar and News pages to stay informed
- Need help fast? Quick links to Contacts and Church Map, plus what information to include in a message
- FAQ: “Do I need to register?”, “What if I’m not sure where to go?”, “How do I get connected to the right person?”

Internal link targets:
- /
- /about.html
- /contacts.html
- /news.html
- /events.html
- /kids.html (or /kids/ if used) /youth.html (or /youth/)

Avoid:
- Any claims about specific attendance numbers, conversions, or outcomes
- Duplicate of the existing “How to Plan a Great Sunday” checklist topic
- Thin posts that only repeat navigation labels without actionable guidance
- Unverifiable testimonials or case studies

## 3. What to Expect at Ridgecrest Baptist Church (Visitor-Friendly Guide)

- Plan item ID: 93
- Status: published
- Article kind: evergreen
- Research status: not_required
- Slug hint: what-to-expect-ridgecrest-baptist-church
- Reader intent: Help a first-time visitor know what will happen, where to go, and how to connect without pressure.
- Angle: Set expectations for first-time guests with a simple, reassuring walkthrough of Sunday flow plus where to find key info on the site.
- Image direction: A real, wide photo of the church sanctuary entrance or a welcoming foyer scene (people greeting at the door), plus a smaller inset photo of a printed bulletin or a phone showing the church website navigation (no logos from other organizations).
- Author hint: Select the best available virtual author for this site.
- Queue item ID: 59
- Article job ID: 63
- WordPress post URL: https://ridgecrestchurch.com/what-to-expect-ridgecrest-baptist-church/
- Researched at: none



Outline:
- Welcome note: you’re not expected to “know the routine”
- Before you arrive: parking, entrances, and where to check event details (link to Events Calendar)
- Sunday morning flow (typical order): greeting, worship, message, prayer, and how long it usually takes
- Kids & Youth: what’s available and how parents can find check-in info (link to /Kids and /Youth)
- What to wear and what to bring (Bible optional; bring a question, not a performance)
- Where to sit and how to get help if you’re unsure (ushers/greeters; direct visitors to /contact for questions)
- After the service: how to meet someone, ask about next steps, and get connected to a ministry
- Accessibility & comfort: accommodations you can request ahead of time (invite readers to message via /contact)
- FAQ: “Do I need to join anything?” “Can I just attend?” “How do I contact the church?”

Internal link targets:
- /
- /events
- /news.html
- /about/
- /kids
- /youth.html,

Avoid:
- Duplicating the existing “How to Get Involved…” first-timer guide
- Generic sermon-only content with no visitor logistics
- Commercial or unrelated service comparisons
- Making claims about specific attendance, outcomes, or internal restoration/backlink metrics

## 4. How to Use Our Events Calendar: RSVP, Reminders, and What to Bring

- Plan item ID: 94
- Status: published
- Article kind: evergreen
- Research status: not_required
- Slug hint: how-to-use-events-calendar-rsvp-reminders-what-to-bring
- Reader intent: Help me quickly find upcoming events, RSVP/confirm details, set reminders, and know what to bring so I feel comfortable attending.
- Angle: Practical walkthrough for visitors and regular attendees on navigating the church events calendar and preparing for common event types.
- Image direction: A real photo of a church bulletin/printed event flyer on a table beside a phone showing a calendar event (no brand ads), or a clean screenshot-style photo of the Events Calendar section on a desktop browser with event details visible.
- Author hint: Select the best available virtual author for this site.
- Queue item ID: 76
- Article job ID: 80
- WordPress post URL: https://ridgecrestchurch.com/how-to-use-events-calendar-rsvp-reminders-what-to-bring/
- Researched at: none



Outline:
- Where to find the Events Calendar (and how to scan it fast)
- Understanding event details: date/time, location, and age groups
- RSVP/confirmation basics (what to do if an event requires it, and who to contact)
- Setting reminders: phone calendar tips and email/text confirmation expectations
- What to bring for common events (worship services, kids/youth activities, community events)
- Accessibility and family needs: seating, check-in, and contact options
- If you’re unsure: when to reach out and what questions to ask
- Quick checklist recap (before you go)

Internal link targets:
- /events-calendar
- /contacts.html
- /contact.php
- /kids
- /youth
- /about

Avoid:
- Posting duplicate titles or obvious variants of existing plan items (e.g., first-timer guide to ministries/kids/youth, Sunday service checklist).
- Thin filler content that doesn’t explain specific steps for using the calendar.
- Commercial language or sponsorship-style framing.
- Unverifiable claims about attendance or outcomes.

## 5. Trend Research Slot: Church Newsletter & News Updates: How We Share What’s Happening (and How You Can Contribute)

- Plan item ID: 95
- Status: failed
- Article kind: research_trend
- Research status: failed
- Slug hint: church-newsletter-news-updates-how-to-contribute
- Reader intent: Understand a current development, trend, or timely question related to this site's topic. Seed intent: Understand what to look for in the News section and learn how to submit an announcement or request prayer/event coverage.
- Angle: Research a current, timely internet topic for this site before writing. Seed angle: Explain the church’s news workflow in a transparent, visitor-friendly way—what kinds of updates appear, how often, and how members can submit items for review.
- Image direction: A real photo of the church office bulletin/news table or a close-up of a printed church bulletin with a laptop showing the News page layout (no brand ads).
- Author hint: Select the best available virtual author for this site.
- Queue item ID: none
- Article job ID: none
- WordPress post URL: none
- Researched at: none
- Error: OpenAI responses API failed with 400: {
  "error": {
    "message": "Invalid schema for response_format 'article_trend_research_plan': In context=('properties', 'sources', 'items', 'properties', 'url'), 'uri' is not a valid format.",
    "type": "invalid_request_error",
    "param": "text.format.schema",
    "code": "invalid_json_schema"
  }
}


Outline:
- What you’ll find in the News area (sermons, upcoming events, ministry spotlights, announcements)
- How we decide what gets posted (timing, relevance, accuracy, and pastoral review)
- Typical posting cadence (e.g., weekly/biweekly) and where to check first (News page + Events Calendar)
- How to submit an update (who to contact, what details to include, deadlines, and preferred contact method)
- What happens after you submit (confirmation, review, and when it may appear)
- Tips for making your request easy to publish (clear title, date/time, location, contact person, brief description)
- Frequently asked questions (“Can I submit late?” “Do you post flyers?” “Where do I find sermon links?”)
- Call to action: reach out through Contacts/Contact page and check the Events Calendar for dates

Internal link targets:
- /news.html
- /events-calendar/
- /contacts.html
- /contact.php
- /
- /about.html

Avoid:
- Duplicate or closely rephrase the existing checklist/first-timer/event-calendar how-to titles
- Any claims about specific internal processes that can’t be verified (keep it general and invitation-based)
- Commercial or promotional language for products/services
- Fake testimonials or unverifiable “case study” outcomes

## 6. How to Prepare for a Youth or Kids Wednesday Night Program

- Plan item ID: 96
- Status: published
- Article kind: evergreen
- Research status: not_required
- Slug hint: prepare-for-wednesday-kids-youth
- Reader intent: Help parents and guardians know exactly what to do before attending Ridgecrest’s Kids or Youth midweek programs, reducing uncertainty for first-time families.
- Angle: Practical, step-by-step preparation guide for families—what to bring, arrival tips, pickup procedures, and how to communicate with staff.
- Image direction: A real photo of a church entry/check-in area (or a close, non-identifying shot of a family arriving and greeting a volunteer) with a printed checklist card on a clipboard in the foreground.
- Author hint: Select the best available virtual author for this site.
- Queue item ID: 97
- Article job ID: 101
- WordPress post URL: https://ridgecrestchurch.com/prepare-for-wednesday-kids-youth/

exec
/bin/bash -lc "sed -n '1,260p' wp-content/plugins/flatlogic-post-creator/INSTRUCTIONS.MD" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "rg --files wp-content/plugins/flatlogic-post-creator/context -g '*.md'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
# Flatlogic Post Creator

You are creating or updating live WordPress blog posts inside the current site workspace.

This skill is for posts and article-like backlink restoration targets, not website pages. Use it for blog posts, news/resource articles, guide/tutorial/review-style URLs, dated archive URLs, and long article-like legacy slugs. Use `flatlogic-page-creator` for Home, About, Contact, service pages, legal pages, navigation, and page-like backlink targets.

Do not stop at writing markdown. The expected output is a real WordPress post created or updated with `wp-cli`.

## Required Reading

Before changing anything:

1. Read `AGENTS.md` if it exists.
2. Read `SITE_CONTEXT.md` if it exists.
3. Read `ARTICLE_CONTENT_PLAN.md` if it exists.
4. Read `wp-content/plugins/flatlogic-post-creator/context/PRINCIPLES.md`.
5. Read `wp-content/plugins/flatlogic-post-creator/context/FINAL_REQUIREMENTS.MD`.
6. Read the task file or user instruction that launched this run.

Treat `SITE_CONTEXT.md`, `ARTICLE_CONTENT_PLAN.md`, and the task file as the current site contract. If they conflict, prefer the explicit task for this post and explain the conflict in the final report.

## Target Contract

Identify each target post before writing:

- Post title
- Intended slug or legacy path
- Public URL, if provided
- Language
- Post purpose and search/user intent
- Source notes or historical content, if provided
- Required internal links
- Required external/link-target links, if provided
- Backlink restoration status, if this post restores an old URL
- Author/persona requirements, if provided

When an author voice card is provided, treat it as private writing guidance:

- Use archetype, worldview, reader relationship, humor style, voice traits, vocabulary, CTA style, and credibility boundaries to shape the article.
- Do not literally mention archetype labels, private voice notes, or internal prompt fields in public content unless the article topic explicitly requires it.
- Do not roleplay as a fictional character. Translate the voice card into prose choices: structure, rhythm, examples, level of warmth, level of humor, and how directly the author speaks to the reader.
- Do not claim real-world credentials, employment, certifications, personal experience, or lived experience unless explicitly provided in the public author card or task.
- Keep humor inside the author card's limits and avoid humor when it would undercut serious safety, legal, medical, financial, or compliance context.

If the task is one article, create or update only that post and the minimum related taxonomy/media settings needed for it to work.

If the task is a batch of post-like backlink targets, restore every target as a WordPress post with a successful public URL whenever technically possible. Topical mismatch with the new site is not a reason to skip or redirect a backlink target. If the original topic is unrelated, create a safe neutral legacy-resource post that acknowledges the resource category without publishing unsafe or spammy material.

## Content Rules

- Build a normal visitor-facing article, not a restoration report.
- Never publish that the post was restored, reconstructed, generated, historical, based on archives, based on backlinks, or based on an old site unless the task explicitly asks for that public messaging.
- Use historical/source notes only as private implementation context.
- Remove crawler artifacts, archive navigation, duplicated menus, pagination fragments, broken labels, spam text, and unsafe content before publishing.
- Do not publish adult, gambling, hacked, parked, spam, pharma, malware, scam, counterfeit, or otherwise harmful content even if it appears in source notes.
- Preserve the original article intent, terminology, structure, and tone when clean source notes are available.
- If source notes are thin, create a credible article that fits the site topic, required pages, and visitor intent.
- Use the language from the task or site context.
- Keep copy specific and useful. Avoid generic filler.

## WordPress Implementation

Use `wp-cli` where practical.

Do not use hardcoded WordPress database table names such as `wp_options`, `wp_posts`, or `wp_postmeta`. Provisioned sites may use a custom table prefix. Prefer `wp option`, `wp post`, `wp term`, `wp eval`, and other WP-CLI APIs. If direct SQL is unavoidable, first get the actual prefix with `wp db prefix` and build table names from that prefix.

When using `wp eval`, do not assume optional WordPress/theme helper functions are loaded. Guard helper calls with `function_exists()`. For attachment alt text, use `get_post_meta( $id, '_wp_attachment_image_alt', true )` instead of non-core helpers such as `wp_get_attachment_image_alt()`. For Custom CSS, prefer theme mods/options or guard Custom CSS helper calls before using them.

Before or after publishing posts, ensure the site has a Blog index:

- Find or create a WordPress page titled `Blog` with slug `/blog/`.
- Set `page_for_posts` to the Blog page ID.
- Keep `show_on_front=page` and `page_on_front` unchanged if Home is already configured.
- Do not change legacy post slugs just to place posts under `/blog/`; `/blog/` is the public index where posts can be found, while individual restored posts may keep exact legacy URLs.
- Verify `/blog/` returns a successful public response. When practical after publishing, confirm `/blog/` links to at least one created/updated post.

Minimum checks:

```bash
wp core is-installed
wp option get home
wp option get siteurl
wp theme list --status=active
wp db prefix
wp post list --post_type=post --fields=ID,post_title,post_name,post_status --format=table
```

Create or update posts with stable title, slug, content, excerpt/meta description where practical, author if requested, categories/tags when helpful, and requested status.

Recommended commands:

```bash
wp post create --post_type=post --post_status=publish --post_title="..." --post_name="..." --post_content="$(cat post.html)" --porcelain
wp post update "$post_id" --post_title="..." --post_name="..." --post_content="$(cat post.html)"
```

For legacy/backlink URLs:

- Restore the exact path/slug when WordPress can represent it cleanly as a post permalink.
- If the exact path cannot be represented as a normal WordPress post permalink, create the closest safe post and add a safe redirect or rewrite only when technical constraints require it.
- Do not redirect or skip a backlink target only because it is off-topic for the current site brief. Off-topic backlink targets should still become safe, visitor-facing posts that return `200`.
- If the target source text is unsafe, hacked/spammy, adult, gambling, pharma, scammy, or unavailable, do not publish that unsafe content. Instead, create a clean neutral post for the legacy URL using safe copy such as an updated resource note, buying guide, maintenance checklist, glossary, or general informational article that does not make false claims.
- Redirect only when the target is explicitly marked as redirect-only, technically impossible to represent, or would require publishing unsafe content that cannot be safely rewritten.
- Do not create WordPress pages for post-like backlink targets.
- Verify important backlink paths with HTTP checks.

## Images

Use relevant thematic images. Substantive posts must include at least one credible relevant image that is visible in the article body. This requirement is mandatory, not optional.

- Prefer existing site media or recoverable original assets when they are clean and usable.
- Search for or select relevant permissively reusable photos, clean illustrations, existing site media, recovered media, or real screenshots/product/control-panel captures. Make a real attempt to find a suitable asset instead of defaulting to generated art or no image.
- Prefer simple, natural thematic photos or clean low-text illustrations over generated diagrams.
- 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, 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. Third-party link targets should never make the article look like Flatlogic/AppWizzy content.
- Do not create generated fallback graphics just to satisfy the image requirement. If no credible image can be found or imported after a real search, report the blocker clearly and treat the post as incomplete/failed rather than padding it with an ugly, generic, AI-looking, or off-topic generated image.
- Do not create complex text-heavy SVGs/infographics/checklists unless the user explicitly requests a diagram. Important copy must live in HTML text, not inside the image.
- Avoid images that depend on tiny labels, dense UI-like annotations, or embedded paragraphs because they often crop badly and become unreadable in WordPress layouts.
- Do not use generated SVGs as featured images or as the primary/most prominent inline article image. Use generated SVGs only for small icons, accents, or secondary decorative visuals.
- For lead/featured article imagery, use a relevant photo, a real product/control-panel screenshot, or a clean topical illustration. Do not use large generated SVGs as the lead, featured, or primary inline image.
- If a generated SVG fallback is unavoidable, keep it decorative, simple, and low-text; never use it as the main content, checklist, hero, featured image, lead visual, or primary inline article image.
- Import or register images in the WordPress Media Library.
- Add descriptive alt text.
- Set a featured image unless the only credible image is a small decorative asset; the visible inline article image is still mandatory.
- Include at least one visible inline image/figure in substantive posts. Do not report success while `INLINE_IMAGE_IDS` is `none`.
- Do not hotlink external image URLs as the final implementation.
- Do not depend on Python PIL/Pillow being installed. If image processing libraries are unavailable, use the original safe image asset, register it through WordPress APIs, and fix display size with HTML/CSS/WordPress settings.
- Do not use `wp media list`; it may not exist. To inspect media, use `wp post list --post_type=attachment` or WordPress APIs.

If `wp media import` fails because GD/Imagick is unavailable, you may register the attachment manually through WordPress APIs, but verify the image renders publicly.
After placing an image, verify the public HTML/CSS does not crop it awkwardly or make it nearly invisible. If the image is a poor topical fit, replace it with a simpler relevant image instead of defending it.

## Links

- Use useful internal links to related pages and posts.
- Use provided link targets naturally and sparingly.
- For new generated blog/resource articles, if Flatlogic/AppWizzy link targets are provided in the task or `SITE_CONTEXT.md`, include at least one exact target URL as a contextual body link unless the task explicitly forbids it. If none is a perfect topical fit, use a short neutral "useful resource" sentence that still helps the reader.
- Keep provided Flatlogic target URLs exactly as rendered, including `utm_source`.
- Do not place Flatlogic or AppWizzy links in the footer, sidebar, menu, author bio, hidden markup, image metadata, or caption-only content.
- Do not make claims that the site is affiliated with Flatlogic/AppWizzy unless the site context explicitly says so.
- Do not stuff links.
- Use descriptive anchor text, not "click here".
- Prefer contextual body placements for Flatlogic link targets.

## Verification

Before finishing:

1. Verify the post exists with `wp post get`.
2. Verify its URL with `wp post url`.
3. Fetch the public URL or legacy path with `curl -I` or `curl -L`.
4. Confirm the content contains the required headings, links, and visible image if required.
5. Flush rewrites if slugs, permalinks, or redirects changed.
6. Verify `/blog/` exists, `page_for_posts` is set to the Blog page, and the Blog index can surface published posts.

## Final Response Contract

For a single-post task, end your final message with these machine-readable lines:

```text
WP_POST_ID: <id or none>
WP_POST_STATUS: <publish|draft|future|pending|none>
WP_POST_URL: <url or none>
WP_AUTHOR_USER: <login/display name or none>
FEATURED_IMAGE_ID: <id or none>
INLINE_IMAGE_IDS: <comma-separated ids or none>
LEGACY_PATH_STATUS: <restored|redirected|not_applicable|failed>
BLOG_INDEX_STATUS: <ready|created|updated|partial|failed; url and page_for_posts summary>
LINK_TARGETS_USED: <comma-separated urls or none>
VERIFICATION: <short result>
```

For a batch of post-like backlink targets, use these exact marker names:

```text
WP_POST_BATCH_STATUS:
WP_POSTS_CREATED_OR_UPDATED:
POST_TARGETS_RESTORED:
POST_TARGETS_REDIRECTED:
POST_TARGETS_SKIPPED:
FEATURED_IMAGE_IDS:
INLINE_IMAGE_IDS:
BLOG_INDEX_STATUS:
LINK_TARGETS_USED:
VERIFICATION:
```

Also include a short human-readable summary of what changed and any remaining risk.

 succeeded in 0ms:
wp-content/plugins/flatlogic-post-creator/context/PRINCIPLES.md

exec
/bin/bash -lc "sed -n '1,260p' SITE_CONTEXT.md" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
# Site Context

This file is generated from Site Inventory. Update the central site record first, then sync context files again.

## Identity

- Domain: ridgecrestchurch.com
- Public URL: https://ridgecrestchurch.com
- Site path: /home/ubuntu/apps/ridgecrestchurch.com
- Restore mode: wordpress
- Lifecycle status: content_ready
- Language: English

## Local Market Guidance

- Local market: United States / U.S. audience inferred from the domain, source notes, topic, or brief.
- Reflect the U.S. audience naturally in page copy, examples, service framing, calls to action, and policy/utility pages when relevant.
- Use U.S. English spelling and plain-language U.S. visitor assumptions unless the task explicitly specifies another language or market.
- You may mention serving U.S. visitors, customers, families, churches, small businesses, or communities when it fits the site topic.
- Do not invent a city, state, street address, phone number, local service area, licenses, company registrations, state-specific legal guarantees, or compliance claims unless they are present in the source context.

## Topic

Church website (Ridgecrest Baptist Church)

## Site Goals

- Build and maintain a normal visitor-facing website for this domain.
- Use recovered content only as private source material for page intent, structure, and copy direction.
- Do not publish archive/recovery wording, crawler metadata, page counters, duplicate menus, or broken navigation labels.
- Keep public content clean, current, safe, and useful for visitors.
- Use `ARTICLE_CONTENT_PLAN.md` as the editorial sequence for future blog posts generated by automation.

## Required Pages

- Home
- About Us
- Ministries
- Kids
- Youth
- Events Calendar
- News
- Contacts
- Church Map
- Resources

## Recovered Content Map

### 1. Ridgecrest Baptist Church

- Path: /
- Page type: home


Content sections:
- Ridgecrest Baptist Church Children & Preschool Meet on Wednesday nights 6:30-8 PM, Preschool in Main Building and Children K-5 in the Children's building. About Us Ministries KIDs Events Calendar YOUTH WHAT TO EXPECT Imagine a church where you could check out Christianity and seek answers to spiritual questions completely without pressure, where the dress is casual, the message is relevant, and you can remain as anonymous as you wish. Through informal and contemporary services, we want to be a…

Internal links:
- 83 captures: http://www.ridgecrestchurch.com/web/20151103035217*/http://www.ridgecrestchurch.com/
- About Us: http://www.ridgecrestchurch.com/about.html
- Ministries: http://www.ridgecrestchurch.com/ministries.html
- KIDs: http://www.ridgecrestchurch.com/kids.html
- Events Calendar: http://www.ridgecrestchurch.com/events.html
- YOUTH: http://www.ridgecrestchurch.com/youth.html

Images:
- loading: https://web-static.archive.org/_static/images/loading.gif
- Logo: http://www.ridgecrestchurch.com/web/20151103035217im_/http://www.ridgecrestchurch.com/images/logo.gif
- Service Times: http://www.ridgecrestchurch.com/web/20151103035217im_/http://www.ridgecrestchurch.com/images/service-times.gif
- http://www.ridgecrestchurch.com/web/20151103035217im_/http://www.ridgecrestchurch.com/images/div.gif
- Events Calendar: http://www.ridgecrestchurch.com/web/20151103035217im_/http://www.ridgecrestchurch.com/images/events.gif
- Sermons: http://www.ridgecrestchurch.com/web/20151103035217im_/http://www.ridgecrestchurch.com/images/sermons.gif
- Life Groups: http://www.ridgecrestchurch.com/web/20151103035217im_/http://www.ridgecrestchurch.com/images/connect.gif
- https://web.archive.org/web/20151103035217im_/https://www.paypalobjects.com/en_US/i/scr/pixel.gif


### 2. Ridgecrest Baptist Church

- Path: /
- Page type: home


Content sections:
- Ridgecrest Baptist Church Children & Preschool Meet on Wednesday nights 6:30-8 PM, Preschool in Main Building and Children K-5 in the Children's building. About Us Ministries KIDs Events Calendar YOUTH WHAT TO EXPECT Imagine a church where you could check out Christianity and seek answers to spiritual questions completely without pressure, where the dress is casual, the message is relevant, and you can remain as anonymous as you wish. Through informal and contemporary services, we want to be a…

Internal links:
- 83 captures: http://ridgecrestchurch.com/web/20130619093042*/http://ridgecrestchurch.com/
- About Us: http://ridgecrestchurch.com/about.html
- Ministries: http://ridgecrestchurch.com/ministries.html
- KIDs: http://ridgecrestchurch.com/kids.html
- Events Calendar: http://ridgecrestchurch.com/events.html
- YOUTH: http://ridgecrestchurch.com/youth.html

Images:
- loading: https://web-static.archive.org/_static/images/loading.gif
- Logo: http://ridgecrestchurch.com/web/20130619093042im_/http://ridgecrestchurch.com/images/logo.gif
- Service Times: http://ridgecrestchurch.com/web/20130619093042im_/http://ridgecrestchurch.com/images/service-times.gif
- http://ridgecrestchurch.com/web/20130619093042im_/http://ridgecrestchurch.com/images/div.gif
- Events Calendar: http://ridgecrestchurch.com/web/20130619093042im_/http://ridgecrestchurch.com/images/events.gif
- Sermons: http://ridgecrestchurch.com/web/20130619093042im_/http://ridgecrestchurch.com/images/sermons.gif
- Life Groups: http://ridgecrestchurch.com/web/20130619093042im_/http://ridgecrestchurch.com/images/connect.gif
- recent news: http://ridgecrestchurch.com/web/20130619093042im_/http://ridgecrestchurch.com/images/map-directions.gif


### 3. Ridgecrest Baptist Church

- Path: /index.html
- Page type: home


Content sections:
- Ridgecrest Baptist Church Children & Preschool Meet on Wednesday nights 6:30-8 PM, Preschool in Main Building and Children K-5 in the Children's building. About Us Ministries KIDs Events Calendar YOUTH WHAT TO EXPECT Imagine a church where you could check out Christianity and seek answers to spiritual questions completely without pressure, where the dress is casual, the message is relevant, and you can remain as anonymous as you wish. Through informal and contemporary services, we want to be a…

Internal links:
- 22 captures: http://www.ridgecrestchurch.com/web/20120507045803*/http://www.ridgecrestchurch.com/index.html
- About Us: http://www.ridgecrestchurch.com/about.html
- Ministries: http://www.ridgecrestchurch.com/ministries.html
- KIDs: http://www.ridgecrestchurch.com/kids.html
- Events Calendar: http://www.ridgecrestchurch.com/events.html
- YOUTH: http://www.ridgecrestchurch.com/youth.html

Images:
- loading: https://web-static.archive.org/_static/images/loading.gif
- Logo: http://www.ridgecrestchurch.com/web/20120507045803im_/http://www.ridgecrestchurch.com/images/logo.gif
- Service Times: http://www.ridgecrestchurch.com/web/20120507045803im_/http://www.ridgecrestchurch.com/images/service-times.gif
- http://www.ridgecrestchurch.com/web/20120507045803im_/http://www.ridgecrestchurch.com/images/div.gif
- Events Calendar: http://www.ridgecrestchurch.com/web/20120507045803im_/http://www.ridgecrestchurch.com/images/events.gif
- Sermons: http://www.ridgecrestchurch.com/web/20120507045803im_/http://www.ridgecrestchurch.com/images/sermons.gif
- Life Groups: http://www.ridgecrestchurch.com/web/20120507045803im_/http://www.ridgecrestchurch.com/images/connect.gif
- http://www.ridgecrestchurch.com/web/20120507045803im_/http://www.ridgecrestchurch.com/images/freedom%20celebration%202012.jpg


### 4. Ridgecrest Baptist Church

- Path: /index.html
- Page type: home


Content sections:
- Ridgecrest Baptist Church About Us Ministries KIDs Events Calendar YOUTH WHAT TO EXPECT Imagine a church where you could check out Christianity and seek answers to spiritual questions completely without pressure, where the dress is casual, the message is relevant, and you can remain as anonymous as you wish. Through informal and contemporary services, we want to be a place where you can be yourself no matter where you are at in your spiritual journey . &copy; 2009 Ridgecrest Baptist Church Cont…

Internal links:
- 22 captures: http://ridgecrestchurch.com/web/20100925215051*/http://ridgecrestchurch.com/index.html
- About Us: http://ridgecrestchurch.com/about.html
- Ministries: http://ridgecrestchurch.com/ministries.html
- KIDs: http://ridgecrestchurch.com/kids.html
- Events Calendar: http://ridgecrestchurch.com/events.html
- YOUTH: http://ridgecrestchurch.com/youth.html

Images:
- loading: https://web-static.archive.org/_static/images/loading.gif
- Logo: http://ridgecrestchurch.com/web/20100925215051im_/http://ridgecrestchurch.com/images/logo.gif
- Service Times: http://ridgecrestchurch.com/web/20100925215051im_/http://ridgecrestchurch.com/images/service-times.gif
- http://ridgecrestchurch.com/web/20100925215051im_/http://ridgecrestchurch.com/images/div.gif
- Events Calendar: http://ridgecrestchurch.com/web/20100925215051im_/http://ridgecrestchurch.com/images/events.gif
- Sermons: http://ridgecrestchurch.com/web/20100925215051im_/http://ridgecrestchurch.com/images/sermons.gif
- Life Groups: http://ridgecrestchurch.com/web/20100925215051im_/http://ridgecrestchurch.com/images/connect.gif
- recent news: http://ridgecrestchurch.com/web/20100925215051im_/http://ridgecrestchurch.com/images/map-directions.gif


### 5. Ridgecrest Baptist Church-About Us

- Path: /about.html
- Page type: about


Content sections:
- Ridgecrest Baptist Church-About Us About Us Ministries KIDs Events Calendar YOUTH ABOUT US 10 CORE VALUES OF R . I . D . G . E . C . R . E . S . T . Make my joy complete by being of the same mind, maintaining the same love, united in spirit, intent on one purpose. Philippians 2:2 (NAS) R esponding to God in worship for Who He is, What He has done and What he will do. So then, my friends, because of God's great mercy to us I appeal to you: Offer yourselves as a living sacrifice to God, dedicated…

Internal links:
- 14 captures: http://ridgecrestchurch.com/web/20100925215046*/http://ridgecrestchurch.com/about.html
- About Us: http://ridgecrestchurch.com/about.html
- Ministries: http://ridgecrestchurch.com/ministries.html
- KIDs: http://ridgecrestchurch.com/kids.html
- Events Calendar: http://ridgecrestchurch.com/events.html
- YOUTH: http://ridgecrestchurch.com/youth.html

Images:
- loading: https://web-static.archive.org/_static/images/loading.gif
- Logo: http://ridgecrestchurch.com/web/20100925215046im_/http://ridgecrestchurch.com/images/logo.gif
- Service Times: http://ridgecrestchurch.com/web/20100925215046im_/http://ridgecrestchurch.com/images/service-times.gif
- http://ridgecrestchurch.com/web/20100925215046im_/http://ridgecrestchurch.com/images/div.gif
- pic: http://ridgecrestchurch.com/web/20100925215046im_/http://ridgecrestchurch.com/images/groups.jpg


### 6. News-Ridgecrest Baptist Church

- Path: /news.html
- Page type: article


Content sections:
- News-Ridgecrest Baptist Church About Us Ministries Resources Events Calendar Contacts CHURCH NEWS Upcoming Events: 5th Quarter for students 6th-12th Grade . Right after football game until Midnight - Nov 7th Toby Mac Concert - Nov 8th Super Sellabration Craft fair/vendor show/garage sale/pancake breakfast/indian tacos! -Nov 15th All Church Thanksgiving Dinner right after churc…

Internal links:
- 5 captures: http://ridgecrestchurch.com/web/20160623042123*/http://ridgecrestchurch.com/news.html
- About Us: http://ridgecrestchurch.com/about.html
- Ministries: http://ridgecrestchurch.com/ministries.html
- Resources: http://ridgecrestchurch.com/resources.html
- Events Calendar: http://ridgecrestchurch.com/events.html
- Contacts: http://ridgecrestchurch.com/contacts.html
- Church Map: http://ridgecrestchurch.com/directions.html
- Events: http://ridgecrestchurch.com/events.html

Images:
- loading: https://web-static.archive.org/_static/images/loading.gif
- Logo: http://ridgecrestchurch.com/web/20160623042123im_/http://ridgecrestchurch.com/images/logo.gif
- Service Times: http://ridgecrestchurch.com/web/20160623042123im_/http://ridgecrestchurch.com/images/service-times.gif
- http://ridgecrestchurch.com/web/20160623042123im_/http://ridgecrestchurch.com/images/div.gif


### 7. Contacts-Ridgecrest Baptist Church

- Path: /contacts.html
- Page type: contact


Content sections:
- Contacts-Ridgecrest Baptist Church About Us Ministries Resources Events Calendar Contacts CONTACT US Church Staff: David Rivers - Senior Pastor Derreck Fraysur - Children's Pastor Kim Rivers - Youth Ministry Director Delynna Kelley - Preschool/Nursery Director Kim Rivers- Ministry Assistant PHONE : 1&middot;405-387-2811 FAX: 1&middot;405-387-2812 E-MAIL US: ridgecrest@pldi.net Ridgecrest Baptist Church 1118 S. Sara Road Blanchard, OK 73010 MAP & DIRECTIONS &raquo; Church Map | Events | Contact…

Internal links:
- 7 captures: http://ridgecrestchurch.com/web/20131126055955*/http://ridgecrestchurch.com/contacts.html
- About Us: http://ridgecrestchurch.com/about.html
- Ministries: http://ridgecrestchurch.com/ministries.html
- Resources: http://ridgecrestchurch.com/resources.html
- Events Calendar: http://ridgecrestchurch.com/events.html
- Contacts: http://ridgecrestchurch.com/contacts.html
- MAP & DIRECTIONS &raquo;: http://ridgecrestchurch.com/directions.html
- Church Map: http://ridgecrestchurch.com/directions.html

Images:
- loading: https://web-static.archive.org/_static/images/loading.gif
- Logo: http://ridgecrestchurch.com/web/20131126055955im_/http://ridgecrestchurch.com/images/logo.gif
- Service Times: http://ridgecrestchurch.com/web/20131126055955im_/http://ridgecrestchurch.com/images/service-times.gif
- http://ridgecrestchurch.com/web/20131126055955im_/http://ridgecrestchurch.com/images/div.gif
- Contact Us: http://ridgecrestchurch.com/web/20131126055955im_/http://ridgecrestchurch.com/images/contact-info.gif


### 8. Ridgecrest Church | Bridgecreek | Blanchard | Tuttle - A Purpose Driven Church

- Path: /contact.php
- Page type: contact
- Meta description: Welcome to the Ridgecrest Baptist Church, a southern baptist church where Jesus is Lord. We are located in the bridgecreek Oklahoma area close to Blanchard, Newcastle, Tuttle Oklahoma. We are a purpose driven church with a great youth service as well as other great family related activities in the tri-city Oklahoma Area. If you are looking for a true bible teaching church come to Ridgecrest and hear David Rivers preach this Sunday.. You are invited as our special guest.


Content sections:
- Ridgecrest Church | Bridgecreek | Blanchard | Tuttle - A Purpose Driven Church Main Menu Ridgecrest Home Service Times Ministries Salvation Event Calendar Mailing List Announcements Contact Us Youth Calendar Contact Us No matter if you are a member of Ridgecrest Church, new to the neighborhood and looking for a church home or just have biblical questions you would like to ask, we are here for you. Please complete the following form and we will get back with you as soon as possible. If you need…

Internal links:
- 7 captures: http://www.ridgecrestchurch.com/web/20070516055136*/http://www.ridgecrestchurch.com/contact.php
- Ridgecrest Home: http://www.ridgecrestchurch.com/index.html
- Service Times: http://www.ridgecrestchurch.com/servicetimes.htm
- Ministries: http://www.ridgecrestchurch.com/ministries.htm
- Salvation: http://www.ridgecrestchurch.com/salvation.htm
- Event Calendar: http://www.ridgecrestchurch.com/calendar.htm
- Mailing List: http://www.ridgecrestchurch.com/mailinglist.shtml
- Announcements: http://www.ridgecrestchurch.com/announcements.php

Images:
- loading: https://web-static.archive.org/_static/images/loading.gif

codex
I’ve got the site contract and post-creator rules. Next I’m loading the remaining plugin context files, then I’ll inspect the existing post, author, blog index, and available prayer-related media directly through `wp-cli`.
exec
/bin/bash -lc "sed -n '1,220p' wp-content/plugins/flatlogic-post-creator/context/PRINCIPLES.md" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
Here’s the writer SOP I’d hand to someone who has to produce a serious, quotable article.

The core idea is simple and brutal: a topic is not a story. A story is a question under conditions of evidence. The best philosophical shorthand I found is Rosenstiel’s: “the method is objective, not the journalist.” Reuters translates that into newsroom practice by putting accuracy ahead of speed. AP and ProPublica push the same logic toward verifiable facts, multiple viewpoints, disciplined attribution, and corrections. Google’s search guidance converges with that worldview: helpful, reliable, people-first, original, transparent—not SEO theater. ([Tom Rosenstiel][1])

## Operating definitions

Use these before you write a word.

**T** = topic
**R** = target reader
**Q** = core question
**H** = working hypothesis
**C** = set of material claims
**E** = evidence matrix mapping each claim to support

**Material claim** = any statement that would change the reader’s conclusion, action, or trust if it turned out to be false.

**Publish condition** = the article is not ready until:

1. every material claim in **C** is supported,
2. the strongest counterargument has been heard and answered,
3. the reader promise is fulfilled,
4. authorship, date, and sourcing are sufficiently transparent.

My recommended floor for a serious non-breaking article:

* sources scanned: **20+**
* sources read closely: **8+**
* primary sources: **3+**
* independent human sources: **2+**
* explicit contrary voice/source: **1+**
* original example, test, or observed case: **1+**
* unsupported material claims: **0**

That is my operating minimum, not a universal law.

---

## 1. Why this story exists

This phase exists because good journalism starts from the reader’s information need, not from the writer’s desire to publish. API frames engagement around the audience’s information needs and wants; Nieman recommends asking what larger issue or trend the immediate topic reveals; Google explicitly prioritizes people-first content over content made to manipulate rankings. ([American Press Institute][2])

### 1.1 Ask

Write down answers to these, in one sentence each:

1. **Why now?**
   What changed, surfaced, broke, became confusing, or became consequential?

2. **Why this reader?**
   Who is the intelligent non-beginner reader here? Founder? PM? engineer? buyer? policymaker?

3. **Why this publication?**
   Why should this piece appear here rather than anywhere else?

4. **Why does this matter?**
   What decision, belief, or action could change after reading it?

5. **What larger issue does this topic open onto?**
   Not just the narrow topic—what bigger tension sits underneath it?

### 1.2 Write

Create a 5-line assignment brief:

* Reader:
* Core question:
* Why now:
* What is new here:
* What would make this worth quoting:

### 1.3 Produce

A one-sentence story brief:

> “For [reader], this article will answer [question] so they can [decide/understand], because [why now/stakes].”

### 1.4 Gate

Do **not** proceed if any of these are true:

* your “why now” is just “the keyword has volume,”
* your “reader” is “everyone,”
* your “what is new” is actually “I will summarize existing coverage.”

Kill or reframe.

---

## 2. Convert the topic into a question tree

Nieman’s craft advice is dead right here: a central embedded question drives the narrative, and the best stories often carry a second, larger question underneath the first. ([Nieman Storyboard][3])

### 2.1 Ask

Turn the topic into a precise question.

Bad:

* “AI code editors vs traditional IDEs”

Better:

* “For which tasks, users, and team contexts do AI code editors actually save net time once debugging, review, and rework are counted?”

### 2.2 Build the tree

Break **Q** into at least six subquestions:

1. **Definition** — what exactly are we talking about?
2. **Mechanism** — how does it work?
3. **Evidence** — what proves or weakens the claim?
4. **Comparison** — compared with what baseline?
5. **Objection** — what would a smart skeptic say?
6. **Implication** — what should the reader conclude or do?

### 2.3 Write two counterweights

* **H1:** your current best answer.
* **H0 / counter-hypothesis:** the strongest version of the opposite answer.

Example:

* H1: AI code editors are faster for scaffolding and repetitive refactors.
* H0: any speed gains disappear once debugging, context recovery, and review are included.

### 2.4 Gate

If you cannot state the strongest opposing case fairly, you are still doing advocacy, not research.

---

## 3. Build the evidence matrix before collecting facts

ProPublica’s standard is useful here: pursue questions that can be answered with verifiable facts. Reuters emphasizes sourcing and accuracy; AP says anything that could reasonably be disputed should be attributed. ([ProPublica][4])

### 3.1 Create a matrix

Make a table or spreadsheet with these columns:

* Claim ID
* Claim
* Why it matters
* Best source type
* Candidate sources
* Status: unverified / partial / verified
* Notes / contradictions

### 3.2 Use a source hierarchy

Rank sources like this:

**Tier A — primary**

* original documents
* raw data
* product documentation
* filings
* transcripts
* direct observation
* your own test

**Tier B — on-record participants**

* builders
* operators
* users
* witnesses
* executives with direct knowledge

**Tier C — independent interpreters**

* analysts
* academics
* domain experts
* critics

**Tier D — secondary synthesis**

* other articles
* industry reports
* commentary

### 3.3 Use a support rule

My recommended rule for each material claim:

* preferred: **1 primary source + 1 corroboration**
* acceptable: **2 independent reliable sources**
* if the claim is negative, surprising, reputationally risky, or high-stakes:
  **+ response from affected party + one extra corroboration**

### 3.4 Gate

Any important claim that lives only in Tier D is a red flag.

---

## 4. Scan the field and locate the gap

Attribution is not decoration. API calls it a roadmap back to the people, documents, and other work behind the piece. Google’s systems also try to show original content, including original reporting, ahead of pages that merely cite it. Rosenstiel’s verification framework treats originality as a core principle. ([American Press Institute][5])

### 4.1 Search in this order

1. primary documents and first-party material,
2. best existing reporting,
3. expert commentary,
4. critics and contrary cases.

### 4.2 For each existing article, extract

* the core claim,
* the evidence used,
* what it assumes,
* what it ignores,
* what it gets wrong or leaves vague.

### 4.3 Produce a “gap memo”

Write 5 bullets:

exec
/bin/bash -lc "sed -n '1,260p' wp-content/uploads/flatlogic-article-tasks/job-255/task.md" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
# 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.


exec
/bin/bash -lc "sed -n '1,260p' wp-content/plugins/flatlogic-post-creator/context/FINAL_REQUIREMENTS.MD" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
TOPICS FOR ARTICLES
Key Points For Writing Article:
Imprint (author, date of writing/update)
Title!
An example of how it can be
Title - How To Build a Fabulous CRM System On A Tight Budget in 2023
At least >2,500 words
Write from “I”, and tell as a story.
Create and add TABLES, MAPs, or at least LISTS to illustrate ideas. Use HTML/table/list content for dense information, not text-heavy image graphics.
Every substantive article must include at least one credible relevant image visible in the article body. This requirement is mandatory. Prefer clean topical photos, real screenshots/product captures, existing site media, recovered media, or simple low-text illustrations. Search for or select a suitable permissively reusable asset instead of defaulting to generated art or no image. Flatlogic/AppWizzy link targets are text/link placement requirements only; do not use 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 satisfy the image requirement with generated fallback graphics, dense generated SVG infographics/checklists, ugly AI-looking images, off-topic visuals, or third-party branded visuals. Do not use generated SVGs as featured images or primary inline article images; generated SVGs are only acceptable as small decorative icons/accents. If no credible image can be found or imported after a real search, report the blocker and treat the article as incomplete/failed. Do not report success while `INLINE_IMAGE_IDS` is `none`.
Highlight important statements in bold.
Use at least a few examples to align with the user
Link to existing content on the Website (surveys, landing pages, quotes)

INTRO
#1 Paragraph - catchy sentence encouraging to read the article to the end. Highlighted in bold/italic at the beginning of the article.
#2 Paragraph - Listing 3-4 questions the reader asks when searching for an article. The following is a quote from a famous person in the field.
#3 Paragraph - a paragraph telling about the existence of the problem and its significance with links to the study of the problem
#4 Paragraph - What the reader will learn after reading the article to the end

Main Part
Terminology/Definitions section - Expand the meaning of terms and abbreviations in the article
Disclosure of the main idea
Conclusion
A brief listing of the key points of the article

Article Title Checklist
Keep titles about 55-60 characters long
Use target keywords in titles
Use numbers in titles (e.g. “5 ways to…”, “Top 10…”, etc.) where possible.
Use words like HOW, WHY, WHAT, and WHERE – help people understand what they will find on the page
Use words like BEST, TOP, ULTIMATE; GUIDE, REVIEW, TUTORIAL – to entice users to click
Write unique titles, no duplicates!
Article Structure
1. Intro is important
   Here you identify the core problem, the theme of the article. Then, clarify the solution to the problem which will be shown in the article. There must be a link between “the pain” and “our solution”.
   The intro must include at least 2 references to authoritative sources that confirm 1) the existence of the problem and 2) the rationale for our proposal to solve it. (links, quotes, research, numbers, etc. – reasons to believe)
   A brief overview of what the reader will find in the article (a good chance to insert keywords)
   Please do not write “In my opinion”. Better “According to research” + link to research.
   *Please do not write “Some items…”. Better “15+ items”, “More than 22 items..”, “Less than 1,436,000 items…” and so on.

2. Table of contents
   *Generated automatically

3. Article Body
   The essence of the problem and solutions are revealed
   Examples of successful solutions are given (from our case studies or other sources) – at least 2 (with links)
   The text has at least 2 links to our theme related blog posts
   If it is a “20+ tools…” topic, then it has the following structure:
   Learn in Chapter 4 “How to describe “20+ tools” topic in a blog post”
   If it’s a “Scientific Article”
   The article must have a “digital value” – “5 methods…” “8 best solutions…” and so on ( H2 subheadings)
   Segmented into methods/types/etc.
   Each method or solution is a separate chapter (H3 subheadings).
4. How to describe “20+ tools…” topic in blog post*:
   *Blog post in this case is a list of different items (e.g. list of companies, tools, books, places, organizations, courses, etc.)

**ideally, it covers 3 obligatory points + 2-3 additional points

<h2>Item Title</h2>
1. Item image <img> – obligatory

2. Item description – obligatory

Describe the item in 1-3 paragraphs.

____________

One of the options below is obligatory

Option 1

3.1.1 Item pros:

Describe the item’s pros in 2-4 sentences

3.1.2 Item cons:

Describe the item’s cons in 2-4 sentences

Option 2

3.2 Key features:

Feature 1
Feature 2
Feature 3
etc
__________

Additional

*Single out the main points of the product/item you’re writing about

Price (e.g. for tools, books, etc)
Website/source link
Demo link
Size (e.g. for the company, organization, etc)
Location (e.g. for the company, organization, etc)
Language
Author, etc
5. Conclusion
   Sum up the idea of the article, make an overview of what was described
   Add call-to-action for subscription/consultation / etc.

codex
I’m at the verification stage now: checking the current post, author, `/blog/` configuration, and searching the media library for a more prayer-specific image before I decide whether the existing asset needs replacement.
exec
/bin/bash -lc 'wp core is-installed' in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc 'wp user list --fields=ID,user_login,display_name,user_email --format=table' in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc 'wp post list --post_type=post --fields=ID,post_title,post_name,post_status,post_author --format=table' in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc 'wp option get page_for_posts && wp post list --post_type=page --fields=ID,post_title,post_name,post_status --format=table' in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc 'wp post list --post_type=attachment --fields=ID,post_title,post_mime_type,guid --format=table' in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 323ms:
 succeeded in 575ms:
ID	user_login	display_name	user_email
1	admin	admin	admin@ridgecrestchurch.com
3	grant-vale	Grant Vale	grant-vale@ridgecrestchurch.com
4	isla-bennett	Isla Bennett	isla-bennett@ridgecrestchurch.com
2	lena-ortiz	Lena Ortiz	lena-ortiz@ridgecrestchurch.com
5	marcus-reed	Marcus Reed	marcus-reed@ridgecrestchurch.com
7	nora-finch	Nora Finch	nora-finch@ridgecrestchurch.com
6	rowan-ellis	Rowan Ellis	rowan-ellis@ridgecrestchurch.com

 succeeded in 565ms:
ID	post_title	post_mime_type	guid
89	Wednesday Night Kids Check-In Scene	image/jpeg	https://ridgecrestchurch.com/wp-content/uploads/imports/wednesday-night-kids-check-in-scene.jpg
86	Ridgecrest Events Calendar Page Screenshot	image/png	http://ridgecrestchurch.com/wp-content/uploads/imports/events-calendar-page-screenshot.png
79	Ridgecrest Website Navigation Screenshot	image/png	https://ridgecrestchurch.com/ridgecrest-website-navigation-screenshot/
76	Sunday Service Planning Desk	image/jpeg	http://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg
1	Ridgecrest Baptist Church Logo	image/gif	https://ridgecrestchurch.com/wp-content/uploads/imports/logo.gif
2	Ridgecrest Service Times	image/gif	https://ridgecrestchurch.com/wp-content/uploads/imports/service-times.gif
3	Ridgecrest Events Calendar	image/gif	https://ridgecrestchurch.com/wp-content/uploads/imports/events.gif
4	Ridgecrest Connection Graphic	image/gif	https://ridgecrestchurch.com/wp-content/uploads/imports/connect.gif
5	Ridgecrest Sermons Graphic	image/gif	https://ridgecrestchurch.com/wp-content/uploads/imports/sermons.gif
6	Ridgecrest Contact Graphic	image/gif	https://ridgecrestchurch.com/wp-content/uploads/imports/contact-info.gif
7	Ridgecrest Map Graphic	image/gif	https://ridgecrestchurch.com/wp-content/uploads/imports/map-directions.gif
8	Ridgecrest Community Illustration	image/jpeg	https://ridgecrestchurch.com/wp-content/uploads/imports/groups.jpg
9	Ridgecrest Main Entrance	image/jpeg	https://ridgecrestchurch.com/wp-content/uploads/imports/church-exterior.jpg
10	Worship Service	image/jpeg	https://ridgecrestchurch.com/wp-content/uploads/imports/worship-service.jpg
11	Children Ministry	image/jpeg	https://ridgecrestchurch.com/wp-content/uploads/imports/children-ministry.jpg
12	Youth Worship	image/jpeg	https://ridgecrestchurch.com/wp-content/uploads/imports/youth-worship.jpg

 succeeded in 658ms:
ID	post_title	post_name	post_status	post_author
94	How to Submit a Prayer Request or Praise Report (and What Happens Next)	submit-prayer-request-praise-report	publish	4
93	Church Resources for New Families: Where to Start This Week	church-resources-for-new-families	publish	7
91	What to Bring (and Wear) to Church at Ridgecrest: A Practical Guide for Sundays	what-to-bring-and-wear-to-church-ridgecrest	publish	4
88	How to Prepare for a Youth or Kids Wednesday Night Program	prepare-for-wednesday-kids-youth	publish	2
87	How to Use Our Events Calendar: RSVP, Reminders, and What to Bring	how-to-use-events-calendar-rsvp-reminders-what-to-bring	publish	6
80	What to Expect at Ridgecrest Baptist Church (Visitor-Friendly Guide)	what-to-expect-ridgecrest-baptist-church	publish	5
78	How to Get Involved at Ridgecrest: A First-Timer’s Guide to Ministries, Kids, and Youth	get-involved-first-timers-guide	publish	4
77	How to Plan a Great Sunday: A Simple Church Service Checklist	how-to-plan-a-great-sunday-checklist	publish	3
74	How to Plan Your First Visit to Ridgecrest Baptist Church	first-visit-ridgecrest-baptist-church	publish	2
51	Welcome to Ridgecrest News	welcome-to-ridgecrest-news	publish	0

 succeeded in 1199ms:
23
ID	post_title	post_name	post_status
25	Terms of Use	terms-of-use	publish
26	Cookie Policy	cookie-policy	publish
18	Events Calendar	events-calendar	publish
19	News	news	publish
20	Contacts	contacts	publish
21	Church Map	church-map	publish
22	Resources	resources	publish
23	Blog	blog	publish
24	Privacy Policy	privacy-policy	publish
13	Home	home	publish
14	About Us	about-us	publish
15	Ministries	ministries	publish
16	Kids	kids	publish
17	Youth	youth	publish

codex
The post and author already exist as expected. The media library is thin, so I’m checking the current article markup and the page-for-posts setup now to confirm whether there’s any closer prayer-related image than the existing general church photos.
exec
/bin/bash -lc 'wp post get 94 --field=post_content' in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc 'wp post get 94 --format=json' in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc 'wp post url 94' in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc 'wp post meta get 94 _thumbnail_id' in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 531ms:
https://ridgecrestchurch.com/submit-prayer-request-praise-report/

 succeeded in 555ms:
<p><strong><em>If you have been carrying something heavy, or if you have good news you want to thank God for, sharing it with the church should feel simple, respectful, and safe. A prayer request or praise report is not a test of wording. It is one way the church cares for one another.</em></strong></p>

<p><strong>By Isla Bennett</strong> | Updated June 7, 2026</p>

<p>People usually come to this question with a few practical concerns in mind: Where do I send a prayer request? What details should I include? Who will see it? Can I ask for privacy? Can I send an update later? Those are wise questions. Knowing what to expect makes it much easier to reach out when something matters.</p>

<p>This guide explains how to submit a prayer request or praise report to Ridgecrest Baptist Church, what kind of information is most helpful, and how requests are typically handled with pastoral care and discretion. If you want the short version first, start with <a href="/contacts.html">Contacts</a> or the church <a href="/contact.php">contact form</a>, keep the details clear and simple, and tell the church whether your request is private or may be shared more broadly.</p>

<figure class="wp-block-image size-large">
  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/worship-service.jpg" alt="People gathered for a worship service at Ridgecrest Baptist Church" class="wp-image-10" />
  <figcaption>Prayer requests and praise reports are one way the church shares burdens, gratitude, and care together.</figcaption>
</figure>

<h2>Why the Church Invites Prayer Requests and Praise Reports</h2>

<p>Church life is not only about attending a service. It is also about caring for one another in the middle of ordinary weeks, difficult seasons, and thankful moments. A prayer request gives others a way to stand with you. A praise report gives the church a chance to celebrate God&rsquo;s faithfulness with you.</p>

<p>Some people hesitate because they do not want to be a burden. Others worry they will share too much or not enough. Both concerns are understandable. The good news is that a clear, modest message is enough. You do not need to write a full life history for the church to pray well.</p>

<p>If you are new to Ridgecrest, the <a href="/">home page</a> and <a href="/resources">Resources</a> page can also help you get your bearings before you reach out.</p>

<h2>Where to Submit a Prayer Request or Praise Report</h2>

<p>The safest first step is to use one of the church&rsquo;s public contact paths. Ridgecrest already provides two straightforward ways to start:</p>

<ul>
  <li><strong><a href="/contacts.html">Contacts</a>:</strong> a simple page with the church&rsquo;s email, phone number, and address.</li>
  <li><strong><a href="/contact.php">Contact Us</a>:</strong> an additional contact page for sending a message through the site.</li>
</ul>

<p>If your request is connected to a church-wide update or you want to see how broader announcements are shared, you can also keep an eye on <a href="/news.html">News</a>. That page is useful for general updates, but it should not be treated as a promise that any personal request will be posted publicly.</p>

<p>When you reach out, use the channel that helps you communicate most clearly. For many people, that means a short email or contact-form note. If the matter is urgent, sensitive, or easier to explain in conversation, a phone call may be the better first step.</p>

<h2>What to Include, and What to Leave Out</h2>

<p>The goal is clarity without oversharing. A helpful request usually answers four simple questions: What is happening? Who is it for? How would you like the church to pray? How private should this remain?</p>

<table>
  <thead>
    <tr>
      <th>Helpful to include</th>
      <th>Better to leave out unless necessary</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Name of the person involved, if sharing the name is appropriate</td>
      <td>Private medical details or personal information you do not have permission to share</td>
    </tr>
    <tr>
      <td>A short description of the situation</td>
      <td>Long background stories that make the main request harder to understand</td>
    </tr>
    <tr>
      <td>A clear prayer focus, such as comfort, healing, wisdom, travel safety, or thanksgiving</td>
      <td>Details about another person&rsquo;s conflict, finances, or family situation that belong in a private pastoral conversation</td>
    </tr>
    <tr>
      <td>Whether the request is private, limited, or okay to share more broadly</td>
      <td>Anything that could embarrass, expose, or pressure someone else without consent</td>
    </tr>
  </tbody>
</table>

<p>A few examples can help:</p>

<ul>
  <li><strong>Prayer request:</strong> “Please pray for my mother as she prepares for surgery this week. We are asking for peace, wisdom for the medical team, and a steady recovery. Please keep this with the church leadership and prayer team only.”</li>
  <li><strong>Praise report:</strong> “Thank you for praying for our family during a difficult month. We are grateful for a clear answer and would love for the church to rejoice with us.”</li>
  <li><strong>Short urgent request:</strong> “Please pray for safe travel and calm hearts for our family tonight. This can stay private.”</li>
</ul>

<p>That level of detail is usually enough to help the church respond thoughtfully without creating confusion or unnecessary exposure.</p>

<h2>How Requests Are Usually Reviewed</h2>

<p>Most churches route prayer needs through a small group of trusted people rather than sending every message everywhere at once. At Ridgecrest, a request submitted through the public contact channels may be seen first by pastoral staff, ministry staff, or another appropriate church contact. From there, it can be handled according to the level of privacy you asked for and the kind of care the situation calls for.</p>

<p>That means a request may be:</p>

<ul>
  <li>Kept with a limited group for private prayer</li>
  <li>Shared with a prayer team or church leaders when appropriate</li>
  <li>Answered with a follow-up question if more clarity is needed</li>
  <li>Directed toward pastoral care if the situation requires a more personal conversation</li>
</ul>

<p>The important point is not the exact internal route. The important point is that you should say clearly whether your request is private, whether a name may be used, and whether any part of it may be shared beyond the first person who receives it.</p>

<h2>How a Request May Be Used</h2>

<p>Not every prayer request or praise report is handled the same way, and that is a good thing. Some should remain private. Some are suitable for a smaller prayer circle. Some praise reports may be appropriate to mention in a broader church context if the person involved is comfortable with that.</p>

<p>In practical terms, your message may be used in one of three ways:</p>

<ol>
  <li><strong>Private prayer:</strong> the request stays with a limited group who can pray quietly and carefully.</li>
  <li><strong>Shared ministry prayer:</strong> the request is passed to a prayer team or church leaders who regularly pray for church needs.</li>
  <li><strong>Public sharing with permission:</strong> a praise report or carefully worded request may be included in a broader church update, announcement, or follow-up if you have given clear permission.</li>
</ol>

<p>If you are not sure what to allow, choose the more private option first. It is easier to expand sharing later than to pull back details that were shared too widely.</p>

<h2>Timing: What to Expect After You Submit</h2>

<p>Because churches balance worship, ministry, family care, and everyday administration, it is wise to think in terms of care rather than an exact service-level promise. Some requests are acknowledged quickly. Others may simply be received and prayed over without a long reply. That does not mean they were ignored.</p>

<p>A healthy expectation is this:</p>

<ul>
  <li>Your request should be sent through a public church channel that is already monitored.</li>
  <li>If the church needs more information, someone may reach back out.</li>
  <li>If the matter is urgent, say so plainly near the beginning of your message.</li>
  <li>If you are sending a praise update after an earlier request, mention that connection so the church understands the context right away.</li>
</ul>

<p>If you need ongoing pastoral help rather than a single prayer note, say that clearly. A prayer request can open the door to a deeper conversation, but it should not be expected to carry every detail by itself.</p>

<h2>Privacy and Consent Matter</h2>

<p>This is where many people need the most reassurance. You do not need to choose between silence and full public disclosure. There is a middle ground, and it is often the wisest one.</p>

<p>Before submitting a request about another person, ask whether you have permission to share their name or details. If you do not, keep the wording general. “Please pray for a friend facing a difficult week” is often more loving than sharing specifics that are not yours to tell.</p>

<p>It also helps to state your preference directly in the message:</p>

<ul>
  <li><strong>Private:</strong> for pastoral staff or a limited prayer team only</li>
  <li><strong>Limited sharing:</strong> okay to share the need, but not every detail</li>
  <li><strong>Public with permission:</strong> okay to mention more broadly in church communication</li>
</ul>

<p>If you are trying to keep personal updates organized at home, an optional outside planning tool like this <a href="https://flatlogic.com/generator?utm_source=ridgecrestchurch.com">web app generator</a> may help you sketch a private reminder workflow for your own notes. That is only a neutral resource for personal organization. A short message through the church&rsquo;s normal contact channels is still all you need to submit a request.</p>

<h2>How to Update or Withdraw a Request</h2>

<p>Prayer requests often change. A situation may improve, become more urgent, or no longer need to be shared. That is normal. If something changes, send a short follow-up through the same public contact path you used before, or use <a href="/contacts.html">Contacts</a> if you are unsure where the earlier request went.</p>

<p>A good update usually includes:</p>

<ul>
  <li>The original request in one sentence</li>
  <li>The new update or praise report</li>
  <li>Whether the church should keep sharing, limit sharing, or stop sharing the request</li>
</ul>

<p>For example: “This is an update to the prayer request for our family last week. Thank you for praying. The surgery went well, and we would be grateful if the church would now pray for recovery. Please keep this limited to the prayer team.”</p>

<p>If you need to withdraw a request, say that plainly and politely. It is entirely reasonable to ask that a request no longer be shared beyond those who have already received it.</p>

<h2>FAQ</h2>

<h3>Can I submit a request anonymously?</h3>

<p>You can often submit a request with limited identifying details, especially if the main need is general prayer. Even so, it is usually helpful for the church to have at least enough information to understand the request and know whether a follow-up is needed. If privacy matters, say so directly and keep the wording general.</p>

<h3>Can I request urgent prayer?</h3>

<p>Yes. If something is urgent, say that near the top of the message and choose the clearest contact method available on <a href="/contacts.html">Contacts</a> or <a href="/contact.php">Contact Us</a>. Urgent does not require dramatic wording. A plain sentence is better: “This is urgent, and we would appreciate prayer today.”</p>

<h3>Will my request be shared online?</h3>

<p>Not by default. Public church communication should depend on appropriateness and permission, not assumption. If you are comfortable with broader sharing, say so. If you are not, say that too. The <a href="/news.html">News</a> page is for church updates, but personal requests should not be assumed to belong there.</p>

<h3>What if I am not sure how much to say?</h3>

<p>Start small. Share the situation in one or two sentences, name the kind of prayer you are asking for, and note your privacy preference. The church can ask for more context if more is needed.</p>

<h2>A Gentle Next Step</h2>

<p>If something is on your heart today, begin with one clear message. Use <a href="/contacts.html">Contacts</a> or <a href="/contact.php">Contact Us</a>, explain the need briefly, and tell the church whether the request is private or shareable. If you are sending a praise report, include that too. Churches need both kinds of messages: the ones that ask for prayer and the ones that say, with relief and gratitude, “Thank you. The Lord has been kind to us.”</p>

<p>And if you are still finding your way around the site, the <a href="/">home page</a>, <a href="/news.html">News</a>, and <a href="/resources">Resources</a> pages can help you take the next step without feeling rushed.</p>

 succeeded in 552ms:
{"ID":94,"post_author":"4","post_date":"2026-06-07 13:02:28","post_date_gmt":"2026-06-07 18:02:28","post_content":"<p><strong><em>If you have been carrying something heavy, or if you have good news you want to thank God for, sharing it with the church should feel simple, respectful, and safe. A prayer request or praise report is not a test of wording. It is one way the church cares for one another.<\/em><\/strong><\/p>\n\n<p><strong>By Isla Bennett<\/strong> | Updated June 7, 2026<\/p>\n\n<p>People usually come to this question with a few practical concerns in mind: Where do I send a prayer request? What details should I include? Who will see it? Can I ask for privacy? Can I send an update later? Those are wise questions. Knowing what to expect makes it much easier to reach out when something matters.<\/p>\n\n<p>This guide explains how to submit a prayer request or praise report to Ridgecrest Baptist Church, what kind of information is most helpful, and how requests are typically handled with pastoral care and discretion. If you want the short version first, start with <a href=\"\/contacts.html\">Contacts<\/a> or the church <a href=\"\/contact.php\">contact form<\/a>, keep the details clear and simple, and tell the church whether your request is private or may be shared more broadly.<\/p>\n\n<figure class=\"wp-block-image size-large\">\n  <img src=\"https:\/\/ridgecrestchurch.com\/wp-content\/uploads\/imports\/worship-service.jpg\" alt=\"People gathered for a worship service at Ridgecrest Baptist Church\" class=\"wp-image-10\" \/>\n  <figcaption>Prayer requests and praise reports are one way the church shares burdens, gratitude, and care together.<\/figcaption>\n<\/figure>\n\n<h2>Why the Church Invites Prayer Requests and Praise Reports<\/h2>\n\n<p>Church life is not only about attending a service. It is also about caring for one another in the middle of ordinary weeks, difficult seasons, and thankful moments. A prayer request gives others a way to stand with you. A praise report gives the church a chance to celebrate God&rsquo;s faithfulness with you.<\/p>\n\n<p>Some people hesitate because they do not want to be a burden. Others worry they will share too much or not enough. Both concerns are understandable. The good news is that a clear, modest message is enough. You do not need to write a full life history for the church to pray well.<\/p>\n\n<p>If you are new to Ridgecrest, the <a href=\"\/\">home page<\/a> and <a href=\"\/resources\">Resources<\/a> page can also help you get your bearings before you reach out.<\/p>\n\n<h2>Where to Submit a Prayer Request or Praise Report<\/h2>\n\n<p>The safest first step is to use one of the church&rsquo;s public contact paths. Ridgecrest already provides two straightforward ways to start:<\/p>\n\n<ul>\n  <li><strong><a href=\"\/contacts.html\">Contacts<\/a>:<\/strong> a simple page with the church&rsquo;s email, phone number, and address.<\/li>\n  <li><strong><a href=\"\/contact.php\">Contact Us<\/a>:<\/strong> an additional contact page for sending a message through the site.<\/li>\n<\/ul>\n\n<p>If your request is connected to a church-wide update or you want to see how broader announcements are shared, you can also keep an eye on <a href=\"\/news.html\">News<\/a>. That page is useful for general updates, but it should not be treated as a promise that any personal request will be posted publicly.<\/p>\n\n<p>When you reach out, use the channel that helps you communicate most clearly. For many people, that means a short email or contact-form note. If the matter is urgent, sensitive, or easier to explain in conversation, a phone call may be the better first step.<\/p>\n\n<h2>What to Include, and What to Leave Out<\/h2>\n\n<p>The goal is clarity without oversharing. A helpful request usually answers four simple questions: What is happening? Who is it for? How would you like the church to pray? How private should this remain?<\/p>\n\n<table>\n  <thead>\n    <tr>\n      <th>Helpful to include<\/th>\n      <th>Better to leave out unless necessary<\/th>\n    <\/tr>\n  <\/thead>\n  <tbody>\n    <tr>\n      <td>Name of the person involved, if sharing the name is appropriate<\/td>\n      <td>Private medical details or personal information you do not have permission to share<\/td>\n    <\/tr>\n    <tr>\n      <td>A short description of the situation<\/td>\n      <td>Long background stories that make the main request harder to understand<\/td>\n    <\/tr>\n    <tr>\n      <td>A clear prayer focus, such as comfort, healing, wisdom, travel safety, or thanksgiving<\/td>\n      <td>Details about another person&rsquo;s conflict, finances, or family situation that belong in a private pastoral conversation<\/td>\n    <\/tr>\n    <tr>\n      <td>Whether the request is private, limited, or okay to share more broadly<\/td>\n      <td>Anything that could embarrass, expose, or pressure someone else without consent<\/td>\n    <\/tr>\n  <\/tbody>\n<\/table>\n\n<p>A few examples can help:<\/p>\n\n<ul>\n  <li><strong>Prayer request:<\/strong> \u201cPlease pray for my mother as she prepares for surgery this week. We are asking for peace, wisdom for the medical team, and a steady recovery. Please keep this with the church leadership and prayer team only.\u201d<\/li>\n  <li><strong>Praise report:<\/strong> \u201cThank you for praying for our family during a difficult month. We are grateful for a clear answer and would love for the church to rejoice with us.\u201d<\/li>\n  <li><strong>Short urgent request:<\/strong> \u201cPlease pray for safe travel and calm hearts for our family tonight. This can stay private.\u201d<\/li>\n<\/ul>\n\n<p>That level of detail is usually enough to help the church respond thoughtfully without creating confusion or unnecessary exposure.<\/p>\n\n<h2>How Requests Are Usually Reviewed<\/h2>\n\n<p>Most churches route prayer needs through a small group of trusted people rather than sending every message everywhere at once. At Ridgecrest, a request submitted through the public contact channels may be seen first by pastoral staff, ministry staff, or another appropriate church contact. From there, it can be handled according to the level of privacy you asked for and the kind of care the situation calls for.<\/p>\n\n<p>That means a request may be:<\/p>\n\n<ul>\n  <li>Kept with a limited group for private prayer<\/li>\n  <li>Shared with a prayer team or church leaders when appropriate<\/li>\n  <li>Answered with a follow-up question if more clarity is needed<\/li>\n  <li>Directed toward pastoral care if the situation requires a more personal conversation<\/li>\n<\/ul>\n\n<p>The important point is not the exact internal route. The important point is that you should say clearly whether your request is private, whether a name may be used, and whether any part of it may be shared beyond the first person who receives it.<\/p>\n\n<h2>How a Request May Be Used<\/h2>\n\n<p>Not every prayer request or praise report is handled the same way, and that is a good thing. Some should remain private. Some are suitable for a smaller prayer circle. Some praise reports may be appropriate to mention in a broader church context if the person involved is comfortable with that.<\/p>\n\n<p>In practical terms, your message may be used in one of three ways:<\/p>\n\n<ol>\n  <li><strong>Private prayer:<\/strong> the request stays with a limited group who can pray quietly and carefully.<\/li>\n  <li><strong>Shared ministry prayer:<\/strong> the request is passed to a prayer team or church leaders who regularly pray for church needs.<\/li>\n  <li><strong>Public sharing with permission:<\/strong> a praise report or carefully worded request may be included in a broader church update, announcement, or follow-up if you have given clear permission.<\/li>\n<\/ol>\n\n<p>If you are not sure what to allow, choose the more private option first. It is easier to expand sharing later than to pull back details that were shared too widely.<\/p>\n\n<h2>Timing: What to Expect After You Submit<\/h2>\n\n<p>Because churches balance worship, ministry, family care, and everyday administration, it is wise to think in terms of care rather than an exact service-level promise. Some requests are acknowledged quickly. Others may simply be received and prayed over without a long reply. That does not mean they were ignored.<\/p>\n\n<p>A healthy expectation is this:<\/p>\n\n<ul>\n  <li>Your request should be sent through a public church channel that is already monitored.<\/li>\n  <li>If the church needs more information, someone may reach back out.<\/li>\n  <li>If the matter is urgent, say so plainly near the beginning of your message.<\/li>\n  <li>If you are sending a praise update after an earlier request, mention that connection so the church understands the context right away.<\/li>\n<\/ul>\n\n<p>If you need ongoing pastoral help rather than a single prayer note, say that clearly. A prayer request can open the door to a deeper conversation, but it should not be expected to carry every detail by itself.<\/p>\n\n<h2>Privacy and Consent Matter<\/h2>\n\n<p>This is where many people need the most reassurance. You do not need to choose between silence and full public disclosure. There is a middle ground, and it is often the wisest one.<\/p>\n\n<p>Before submitting a request about another person, ask whether you have permission to share their name or details. If you do not, keep the wording general. \u201cPlease pray for a friend facing a difficult week\u201d is often more loving than sharing specifics that are not yours to tell.<\/p>\n\n<p>It also helps to state your preference directly in the message:<\/p>\n\n<ul>\n  <li><strong>Private:<\/strong> for pastoral staff or a limited prayer team only<\/li>\n  <li><strong>Limited sharing:<\/strong> okay to share the need, but not every detail<\/li>\n  <li><strong>Public with permission:<\/strong> okay to mention more broadly in church communication<\/li>\n<\/ul>\n\n<p>If you are trying to keep personal updates organized at home, an optional outside planning tool like this <a href=\"https:\/\/flatlogic.com\/generator?utm_source=ridgecrestchurch.com\">web app generator<\/a> may help you sketch a private reminder workflow for your own notes. That is only a neutral resource for personal organization. A short message through the church&rsquo;s normal contact channels is still all you need to submit a request.<\/p>\n\n<h2>How to Update or Withdraw a Request<\/h2>\n\n<p>Prayer requests often change. A situation may improve, become more urgent, or no longer need to be shared. That is normal. If something changes, send a short follow-up through the same public contact path you used before, or use <a href=\"\/contacts.html\">Contacts<\/a> if you are unsure where the earlier request went.<\/p>\n\n<p>A good update usually includes:<\/p>\n\n<ul>\n  <li>The original request in one sentence<\/li>\n  <li>The new update or praise report<\/li>\n  <li>Whether the church should keep sharing, limit sharing, or stop sharing the request<\/li>\n<\/ul>\n\n<p>For example: \u201cThis is an update to the prayer request for our family last week. Thank you for praying. The surgery went well, and we would be grateful if the church would now pray for recovery. Please keep this limited to the prayer team.\u201d<\/p>\n\n<p>If you need to withdraw a request, say that plainly and politely. It is entirely reasonable to ask that a request no longer be shared beyond those who have already received it.<\/p>\n\n<h2>FAQ<\/h2>\n\n<h3>Can I submit a request anonymously?<\/h3>\n\n<p>You can often submit a request with limited identifying details, especially if the main need is general prayer. Even so, it is usually helpful for the church to have at least enough information to understand the request and know whether a follow-up is needed. If privacy matters, say so directly and keep the wording general.<\/p>\n\n<h3>Can I request urgent prayer?<\/h3>\n\n<p>Yes. If something is urgent, say that near the top of the message and choose the clearest contact method available on <a href=\"\/contacts.html\">Contacts<\/a> or <a href=\"\/contact.php\">Contact Us<\/a>. Urgent does not require dramatic wording. A plain sentence is better: \u201cThis is urgent, and we would appreciate prayer today.\u201d<\/p>\n\n<h3>Will my request be shared online?<\/h3>\n\n<p>Not by default. Public church communication should depend on appropriateness and permission, not assumption. If you are comfortable with broader sharing, say so. If you are not, say that too. The <a href=\"\/news.html\">News<\/a> page is for church updates, but personal requests should not be assumed to belong there.<\/p>\n\n<h3>What if I am not sure how much to say?<\/h3>\n\n<p>Start small. Share the situation in one or two sentences, name the kind of prayer you are asking for, and note your privacy preference. The church can ask for more context if more is needed.<\/p>\n\n<h2>A Gentle Next Step<\/h2>\n\n<p>If something is on your heart today, begin with one clear message. Use <a href=\"\/contacts.html\">Contacts<\/a> or <a href=\"\/contact.php\">Contact Us<\/a>, explain the need briefly, and tell the church whether the request is private or shareable. If you are sending a praise report, include that too. Churches need both kinds of messages: the ones that ask for prayer and the ones that say, with relief and gratitude, \u201cThank you. The Lord has been kind to us.\u201d<\/p>\n\n<p>And if you are still finding your way around the site, the <a href=\"\/\">home page<\/a>, <a href=\"\/news.html\">News<\/a>, and <a href=\"\/resources\">Resources<\/a> pages can help you take the next step without feeling rushed.<\/p>","post_title":"How to Submit a Prayer Request or Praise Report (and What Happens Next)","post_excerpt":"Learn how to share your prayer requests and praise reports with Ridgecrest Baptist Church, understand the process, and what to expect after submission.","post_status":"publish","comment_status":"closed","ping_status":"closed","post_password":"","post_name":"submit-prayer-request-praise-report","to_ping":"","pinged":"","post_modified":"2026-06-07 13:02:28","post_modified_gmt":"2026-06-07 18:02:28","post_content_filtered":"","post_parent":0,"guid":"https:\/\/ridgecrestchurch.com\/submit-prayer-request-praise-report\/","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","url":"https:\/\/ridgecrestchurch.com\/submit-prayer-request-praise-report\/"}

 succeeded in 550ms:
10

codex
The article itself is in place and already includes the required body link and inline image. I’m doing one more pass through the local uploads/theme assets for any prayer-card or prayer-team photo that would fit the brief better than the current worship image.
exec
/bin/bash -lc "rg --files wp-content/uploads wp-content/themes -g '*.{jpg,jpeg,png,gif,webp}'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
wp-content/uploads/imports/sunday-service-planning-desk.jpg
wp-content/uploads/imports/worship-service.jpg
wp-content/uploads/imports/events-calendar-page-screenshot.png
wp-content/uploads/imports/connect.gif
wp-content/uploads/imports/children-ministry.jpg
wp-content/uploads/imports/church-exterior.jpg
wp-content/uploads/imports/wednesday-night-kids-check-in-scene.jpg
wp-content/uploads/imports/groups.jpg
wp-content/uploads/imports/logo.gif
wp-content/uploads/imports/sermons.gif
wp-content/uploads/imports/map-directions.gif
wp-content/uploads/imports/events.gif
wp-content/uploads/imports/ridgecrest-home-navigation-screenshot.png
wp-content/uploads/imports/youth-group.jpg
wp-content/uploads/imports/youth-worship.jpg
wp-content/uploads/imports/service-times.gif
wp-content/uploads/imports/contact-info.gif
wp-content/themes/flb/img/services.png
wp-content/themes/church/images/bg.png
wp-content/themes/church/images/button.png
wp-content/themes/church/images/header.jpg
wp-content/themes/church/screenshot.png
wp-content/themes/flb/img/team/dmitry.jpg
wp-content/themes/flb/img/team/natalie.jpg
wp-content/themes/flb/img/team/philip.jpg
wp-content/themes/flb/img/team/daniel.jpg
wp-content/themes/flb/img/team/michael.jpg
wp-content/themes/flb/img/team/dmitry-square.jpg
wp-content/themes/flb/img/team/raman.jpg
wp-content/themes/flb/img/team/artem.jpg
wp-content/themes/flb/img/team/sergey.png
wp-content/themes/flb/img/team/anastasia-square.jpg
wp-content/themes/flb/img/team/artem-square.jpg
wp-content/themes/flb/img/team/philip-square.jpg
wp-content/themes/flb/img/team/veronika.jpg
wp-content/themes/flb/img/team/uladzimir.jpg
wp-content/themes/flb/img/team/sergey-square.jpg
wp-content/themes/flb/img/team/anastasia.jpg
wp-content/themes/flb/img/team/philip.png
wp-content/themes/flb/img/team/sergey.jpg
wp-content/themes/flb/img/team/natalie-square.jpg
wp-content/themes/flb/img/team/michael.png
wp-content/themes/flb/img/flat/Toilet-Paper.png
wp-content/themes/flb/img/flat/Map.png
wp-content/themes/flb/img/flat/Pensils.png
wp-content/themes/flb/img/flat/Watches.png
wp-content/themes/flb/img/flat/Mail.png
wp-content/themes/flb/img/flat/Chat.png
wp-content/themes/flb/img/flat/Compas.png
wp-content/themes/flb/img/flat/Retina-Ready.png
wp-content/themes/flb/img/flat/Gift-Box.png
wp-content/themes/flb/img/flat/Calendar.png
wp-content/themes/flb/img/flat/Book.png
wp-content/themes/flb/img/flat/Pocket.png
wp-content/themes/flb/img/flat/Infinity-Loop.png
wp-content/themes/flb/img/flat/Clipboard.png
wp-content/themes/flb/img/Altan.png
wp-content/themes/flb/img/open-source.png
wp-content/themes/flb/img/tobias.png
wp-content/themes/flb/img/daniel.jpg
wp-content/themes/flb/img/HTML5.png
wp-content/themes/flb/img/works/react-native-starter.png
wp-content/themes/flb/img/works/amd-1000.png
wp-content/themes/flb/img/works/light-blue-1000.png
wp-content/themes/flb/img/works/light-blue.png
wp-content/themes/flb/img/works/infradash1000.png
wp-content/themes/flb/img/works/evalanche1000.png
wp-content/themes/flb/img/works/react-dashboard.png
wp-content/themes/flb/img/works/construct.png
wp-content/themes/flb/img/works/sing-1000.png
wp-content/themes/flb/img/works/sing.png
wp-content/themes/flb/img/works/schnapchen1000.png
wp-content/themes/flb/img/javascript.png
wp-content/themes/flb/img/team.png
wp-content/themes/flb/img/slogan-bg.jpeg
wp-content/themes/flb/img/client-works/Infradash500.png
wp-content/themes/flb/img/client-works/SchnapchenLogo.png
wp-content/themes/flb/img/client-works/Evalanche500.png
wp-content/themes/flb/img/client-works/Infradash1000.png
wp-content/themes/flb/img/client-works/shnappchen/Mobile3_schnaphen.png
wp-content/themes/flb/img/client-works/shnappchen/Mobile4_schnaphen.png
wp-content/themes/flb/img/client-works/shnappchen/Mobile1_schnaphen.png
wp-content/themes/flb/img/client-works/shnappchen/Header_schnaphen.png
wp-content/themes/flb/img/client-works/shnappchen/MobileNew3_schnaphen.png
wp-content/themes/flb/img/client-works/shnappchen/MobileNew2_schnaphen.png
wp-content/themes/flb/img/client-works/shnappchen/ipad_schnaphen.png
wp-content/themes/flb/img/client-works/shnappchen/Mobile2_schnaphen.png
wp-content/themes/flb/img/client-works/shnappchen/MobileNew1_schnaphen.png
wp-content/themes/flb/img/client-works/Schnapchen1000.png
wp-content/themes/flb/img/client-works/EvalancheLogo.png
wp-content/themes/flb/img/client-works/Schnapchen500.png
wp-content/themes/flb/img/client-works/InfradashLogo.png
wp-content/themes/flb/img/client-works/Evalanche1000.png
wp-content/themes/flb/img/client-works/evelanche/MacBook_Evalanche.png
wp-content/themes/flb/img/client-works/evelanche/Evalanche_screen.png
wp-content/themes/flb/img/wordpress.png
wp-content/themes/flb/img/rails.png
wp-content/themes/flb/img/services-bg.jpg
wp-content/themes/flb/img/bg-work.png
wp-content/themes/flb/img/favicon1.png
wp-content/themes/flb/img/web-bg.jpg
wp-content/themes/flb/img/background.png
wp-content/themes/flb/img/quoteMark.png
wp-content/themes/flb/img/about-bg.jpg
wp-content/themes/flb/img/backbone.png
wp-content/themes/flb/img/CSS3.png
wp-content/themes/flb/img/react.png
wp-content/themes/flb/img/web-services.png
wp-content/themes/flb/img/flatlogic-test.png
wp-content/themes/flb/img/slogan-products.png
wp-content/themes/flb/img/angular.png
wp-content/themes/flb/img/favicon.png
wp-content/themes/flb/img/careers-bg.jpeg
wp-content/themes/flb/img/logo.jpg
wp-content/themes/flb/img/map.png
wp-content/themes/flb/img/java.png
wp-content/themes/flb/img/d3.png
wp-content/themes/flb/img/png/skypeLogo.png
wp-content/themes/flb/img/png/mailLogo.png
wp-content/themes/flb/img/png/inLogo.png
wp-content/themes/flb/img/png/fbLogo.png
wp-content/themes/flb/img/png/mailLogoGray.png
wp-content/themes/flb/img/png/gitLogo.png
wp-content/themes/flb/img/png/twLogo.png
wp-content/themes/flb/img/clients.png
wp-content/themes/flb/img/background_new.png
wp-content/themes/flb/img/node-js.png
wp-content/themes/omega/screenshot.png
wp-content/themes/twentytwentyfive/assets/images/coral-square.webp
wp-content/themes/twentytwentyfive/assets/images/link-in-bio-image.webp
wp-content/themes/twentytwentyfive/assets/images/marshland-birds-square.webp
wp-content/themes/twentytwentyfive/assets/images/northern-buttercups-flowers.webp
wp-content/themes/twentytwentyfive/assets/images/link-in-bio-background.webp
wp-content/themes/twentytwentyfive/assets/images/delphinium-flowers.webp
wp-content/themes/twentytwentyfive/assets/images/coming-soon-bg-image.webp
wp-content/themes/twentytwentyfive/assets/images/akaka-falls-state-park-flora.webp
wp-content/themes/twentytwentyfive/assets/images/woman-splashing-water.webp
wp-content/themes/twentytwentyfive/assets/images/404-image.webp
wp-content/themes/twentytwentyfive/assets/images/category-anthuriums.webp
wp-content/themes/twentytwentyfive/assets/images/dallas-creek-square.webp
wp-content/themes/twentytwentyfive/assets/images/vash-gon-square.webp
wp-content/themes/twentytwentyfive/assets/images/poster-image-background.webp
wp-content/themes/twentytwentyfive/assets/images/star-thristle-flower.webp
wp-content/themes/twentytwentyfive/assets/images/parthenon-square.webp
wp-content/themes/twentytwentyfive/assets/images/malibu-plantlife.webp
wp-content/themes/twentytwentyfive/assets/images/typewriter.webp
wp-content/themes/twentytwentyfive/assets/images/book-image.webp
wp-content/themes/twentytwentyfive/assets/images/hero-podcast.webp
wp-content/themes/twentytwentyfive/assets/images/red-hibiscus-closeup.webp
wp-content/themes/twentytwentyfive/assets/images/botany-flowers.webp
wp-content/themes/twentytwentyfive/assets/images/services-subscriber-photo.webp
wp-content/themes/twentytwentyfive/assets/images/ruins-image.webp
wp-content/themes/twentytwentyfive/assets/images/book-image-landing.webp
wp-content/themes/twentytwentyfive/assets/images/category-sunflowers.webp
wp-content/themes/twentytwentyfive/assets/images/man-in-hat.webp
wp-content/themes/twentytwentyfive/assets/images/botany-flowers-closeup.webp
wp-content/themes/twentytwentyfive/assets/images/location.webp
wp-content/themes/twentytwentyfive/assets/images/grid-flower-2.webp
wp-content/themes/twentytwentyfive/assets/images/grid-flower-1.webp
wp-content/themes/twentytwentyfive/assets/images/flower-meadow-square.webp
wp-content/themes/twentytwentyfive/assets/images/agenda-img-4.webp
wp-content/themes/twentytwentyfive/assets/images/category-cactus.webp
wp-content/themes/twentytwentyfive/assets/images/nurse.webp
wp-content/themes/twentytwentyfive/assets/images/campanula-alliariifolia-flower.webp
wp-content/themes/flb/screenshot.png
wp-content/themes/twentytwentyfive/screenshot.png

exec
/bin/bash -lc "find wp-content/uploads -maxdepth 3 -type f | sed 's#"'^#/#'"' | sort" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
/wp-content/uploads/flatlogic-article-tasks/job-101/check-article-image.php
/wp-content/uploads/flatlogic-article-tasks/job-101/task.md
/wp-content/uploads/flatlogic-article-tasks/job-122/task.md
/wp-content/uploads/flatlogic-article-tasks/job-131/task.md
/wp-content/uploads/flatlogic-article-tasks/job-148/task.md
/wp-content/uploads/flatlogic-article-tasks/job-185/task.md
/wp-content/uploads/flatlogic-article-tasks/job-199/check-article-image.php
/wp-content/uploads/flatlogic-article-tasks/job-199/post-102.html
/wp-content/uploads/flatlogic-article-tasks/job-199/task.md
/wp-content/uploads/flatlogic-article-tasks/job-225/check-article-image.php
/wp-content/uploads/flatlogic-article-tasks/job-225/task.md
/wp-content/uploads/flatlogic-article-tasks/job-25/check-article-image.php
/wp-content/uploads/flatlogic-article-tasks/job-25/first-visit-post.html
/wp-content/uploads/flatlogic-article-tasks/job-25/task.md
/wp-content/uploads/flatlogic-article-tasks/job-255/submit-prayer-request-praise-report.html
/wp-content/uploads/flatlogic-article-tasks/job-255/task.md
/wp-content/uploads/flatlogic-article-tasks/job-36/check-article-image.php
/wp-content/uploads/flatlogic-article-tasks/job-36/how-to-plan-a-great-sunday-checklist.html
/wp-content/uploads/flatlogic-article-tasks/job-36/task.md
/wp-content/uploads/flatlogic-article-tasks/job-48/check-article-image.php
/wp-content/uploads/flatlogic-article-tasks/job-48/task.md
/wp-content/uploads/flatlogic-article-tasks/job-63/check-article-image.php
/wp-content/uploads/flatlogic-article-tasks/job-63/task.md
/wp-content/uploads/flatlogic-article-tasks/job-63/what-to-expect-ridgecrest-baptist-church.html
/wp-content/uploads/flatlogic-article-tasks/job-80/check-article-image.php
/wp-content/uploads/flatlogic-article-tasks/job-80/how-to-use-events-calendar-rsvp-reminders-what-to-bring.html
/wp-content/uploads/flatlogic-article-tasks/job-80/task.md
/wp-content/uploads/flatlogic-page-tasks/job-44/build_site.php
/wp-content/uploads/flatlogic-page-tasks/job-44/task.md
/wp-content/uploads/flatlogic-site-polish-tasks/job-44/task.md
/wp-content/uploads/imports/children-ministry.jpg
/wp-content/uploads/imports/church-exterior.jpg
/wp-content/uploads/imports/connect.gif
/wp-content/uploads/imports/contact-info.gif
/wp-content/uploads/imports/events-calendar-page-screenshot.png
/wp-content/uploads/imports/events.gif
/wp-content/uploads/imports/groups.jpg
/wp-content/uploads/imports/logo.gif
/wp-content/uploads/imports/map-directions.gif
/wp-content/uploads/imports/ridgecrest-home-navigation-screenshot.png
/wp-content/uploads/imports/sermons.gif
/wp-content/uploads/imports/service-times.gif
/wp-content/uploads/imports/sunday-service-planning-desk.jpg
/wp-content/uploads/imports/wednesday-night-kids-check-in-scene.jpg
/wp-content/uploads/imports/worship-service.jpg
/wp-content/uploads/imports/youth-group.jpg
/wp-content/uploads/imports/youth-worship.jpg

exec
/bin/bash -lc 'wp option get show_on_front && wp option get page_on_front && wp option get page_for_posts && wp option get home && wp option get siteurl' in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 2605ms:
page
13
23
https://ridgecrestchurch.com
https://ridgecrestchurch.com

codex
I’ve confirmed there isn’t a better prayer-specific real photo in local media. I’m finishing with direct checks against the live-generated post and `/blog/` output so the report can name the verified state instead of inferring it.
exec
/bin/bash -lc 'curl -I -L -s https://ridgecrestchurch.com/submit-prayer-request-praise-report/' in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc 'curl -L -s https://ridgecrestchurch.com/blog/ | rg -n "submit-prayer-request-praise-report|How to Submit a Prayer Request or Praise Report"' in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "curl -L -s https://ridgecrestchurch.com/submit-prayer-request-praise-report/ | rg -n \"worship-service\\.jpg|flatlogic\\.com/generator\\?utm_source=ridgecrestchurch\\.com|How to Submit a Prayer Request or Praise Report|Contacts|News\"" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "wp eval '"'$post = get_post(94); $content = $post ? $post->post_content : ""; preg_match_all("/wp-image-([0-9]+)/", $content, $m); $ids = array_values(array_unique($m[1] ?? [])); $has_link = strpos($content, "https://flatlogic.com/generator?utm_source=ridgecrestchurch.com") !== false; echo "INLINE_IMAGE_IDS=" . ($ids ? implode(",", $ids) : "none") . PHP_EOL; echo "HAS_LINK=" . ($has_link ? "yes" : "no") . PHP_EOL; echo "HAS_CONTACTS_HTML=" . (strpos($content, "/contacts.html") !== false ? "yes" : "no") . PHP_EOL; echo "HAS_CONTACT_PHP=" . (strpos($content, "/contact.php") !== false ? "yes" : "no") . PHP_EOL; echo "HAS_NEWS_HTML=" . (strpos($content, "/news.html") !== false ? "yes" : "no") . PHP_EOL;'"'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 510ms:
INLINE_IMAGE_IDS=10
HAS_LINK=yes
HAS_CONTACTS_HTML=yes
HAS_CONTACT_PHP=yes
HAS_NEWS_HTML=yes

 succeeded in 718ms:
HTTP/2 200 
date: Sun, 07 Jun 2026 18:04:19 GMT
content-type: text/html; charset=UTF-8
link: <https://ridgecrestchurch.com/wp-json/>; rel="https://api.w.org/", <https://ridgecrestchurch.com/wp-json/wp/v2/posts/94>; rel="alternate"; title="JSON"; type="application/json", <https://ridgecrestchurch.com/?p=94>; rel=shortlink
server: cloudflare
cf-cache-status: DYNAMIC
report-to: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=LKe8mhCwkIipkZ0V7DBhR9WP%2BOfNijT0ZUeL5LjmfkvKDROOEL6s7skzKf%2B8kAg7fzy%2Fwdsc2GapVyvqL2syq1KH5DNCys6%2FmxQTVroCuml3PDjAh6pWhWP1NNWcK7MM%2BVkGEvZbFg%3D%3D"}]}
nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
cf-ray: a081941d2b1ed241-WAW
alt-svc: h3=":443"; ma=86400


 succeeded in 775ms:
12:	<title>How to Submit a Prayer Request or Praise Report (and What Happens Next) - Ridgecrest Baptist Church</title>
16:	<meta property="og:title" content="How to Submit a Prayer Request or Praise Report (and What Happens Next)" />
21:	<meta property="og:image" content="https://ridgecrestchurch.com/wp-content/uploads/imports/worship-service.jpg" />
31:	<script type="application/ld+json" class="yoast-schema-graph">{"@context":"https://schema.org","@graph":[{"@type":"Article","@id":"https://ridgecrestchurch.com/submit-prayer-request-praise-report/#article","isPartOf":{"@id":"https://ridgecrestchurch.com/submit-prayer-request-praise-report/"},"author":{"name":"Isla Bennett","@id":"https://ridgecrestchurch.com/#/schema/person/62f7e8f676b7100f3b2f62d31ba377d6"},"headline":"How to Submit a Prayer Request or Praise Report (and What Happens Next)","datePublished":"2026-06-07T18:02:28+00:00","mainEntityOfPage":{"@id":"https://ridgecrestchurch.com/submit-prayer-request-praise-report/"},"wordCount":1922,"publisher":{"@id":"https://ridgecrestchurch.com/#organization"},"image":{"@id":"https://ridgecrestchurch.com/submit-prayer-request-praise-report/#primaryimage"},"thumbnailUrl":"https://ridgecrestchurch.com/wp-content/uploads/imports/worship-service.jpg","inLanguage":"en-US"},{"@type":"WebPage","@id":"https://ridgecrestchurch.com/submit-prayer-request-praise-report/","url":"https://ridgecrestchurch.com/submit-prayer-request-praise-report/","name":"How to Submit a Prayer Request or Praise Report (and What Happens Next) - Ridgecrest Baptist Church","isPartOf":{"@id":"https://ridgecrestchurch.com/#website"},"primaryImageOfPage":{"@id":"https://ridgecrestchurch.com/submit-prayer-request-praise-report/#primaryimage"},"image":{"@id":"https://ridgecrestchurch.com/submit-prayer-request-praise-report/#primaryimage"},"thumbnailUrl":"https://ridgecrestchurch.com/wp-content/uploads/imports/worship-service.jpg","datePublished":"2026-06-07T18:02:28+00:00","breadcrumb":{"@id":"https://ridgecrestchurch.com/submit-prayer-request-praise-report/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https://ridgecrestchurch.com/submit-prayer-request-praise-report/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https://ridgecrestchurch.com/submit-prayer-request-praise-report/#primaryimage","url":"https://ridgecrestchurch.com/wp-content/uploads/imports/worship-service.jpg","contentUrl":"https://ridgecrestchurch.com/wp-content/uploads/imports/worship-service.jpg","width":4032,"height":3024,"caption":"People gathered for a worship service at Ridgecrest Baptist Church"},{"@type":"BreadcrumbList","@id":"https://ridgecrestchurch.com/submit-prayer-request-praise-report/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://ridgecrestchurch.com/"},{"@type":"ListItem","position":2,"name":"Blog","item":"https://ridgecrestchurch.com/blog/"},{"@type":"ListItem","position":3,"name":"How to Submit a Prayer Request or Praise Report (and What Happens Next)"}]},{"@type":"WebSite","@id":"https://ridgecrestchurch.com/#website","url":"https://ridgecrestchurch.com/","name":"Ridgecrest Baptist Church","description":"A welcoming family church in Blanchard, Oklahoma","publisher":{"@id":"https://ridgecrestchurch.com/#organization"},"alternateName":"Ridgecrest Church","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://ridgecrestchurch.com/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https://ridgecrestchurch.com/#organization","name":"Ridgecrest Baptist Church","url":"https://ridgecrestchurch.com/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https://ridgecrestchurch.com/#/schema/logo/image/","url":"https://ridgecrestchurch.com/wp-content/uploads/imports/logo.gif","contentUrl":"https://ridgecrestchurch.com/wp-content/uploads/imports/logo.gif","width":null,"height":null,"caption":"Ridgecrest Baptist Church"},"image":{"@id":"https://ridgecrestchurch.com/#/schema/logo/image/"}},{"@type":"Person","@id":"https://ridgecrestchurch.com/#/schema/person/62f7e8f676b7100f3b2f62d31ba377d6","name":"Isla Bennett","description":"Isla writes about support experiences, service pages, customer communication, and the human side of running reliable online services.","url":"https://ridgecrestchurch.com/author/isla-bennett/"}]}</script>
409:<li id="menu-item-46" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-46"><a href="https://ridgecrestchurch.com/news/">News</a></li>
411:<li id="menu-item-48" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-48"><a href="https://ridgecrestchurch.com/contacts/">Contacts</a></li>
421:			<header class="entry-header">	<h1 class="entry-title" itemprop="headline">How to Submit a Prayer Request or Praise Report (and What Happens Next)</h1>
430:<p>This guide explains how to submit a prayer request or praise report to Ridgecrest Baptist Church, what kind of information is most helpful, and how requests are typically handled with pastoral care and discretion. If you want the short version first, start with <a href="/contacts.html">Contacts</a> or the church <a href="/contact.php">contact form</a>, keep the details clear and simple, and tell the church whether your request is private or may be shared more broadly.</p>
432:  <img decoding="async" width="4032" height="3024" data-src="https://ridgecrestchurch.com/wp-content/uploads/imports/worship-service.jpg" alt="People gathered for a worship service at Ridgecrest Baptist Church" class="wp-image-10 lazyload" src="data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==" style="--smush-placeholder-width: 4032px; --smush-placeholder-aspect-ratio: 4032/3024;" /><figcaption>Prayer requests and praise reports are one way the church shares burdens, gratitude, and care together.</figcaption></figure>
440:<li><strong><a href="/contacts.html">Contacts</a>:</strong> a simple page with the church&rsquo;s email, phone number, and address.</li>
443:<p>If your request is connected to a church-wide update or you want to see how broader announcements are shared, you can also keep an eye on <a href="/news.html">News</a>. That page is useful for general updates, but it should not be treated as a promise that any personal request will be posted publicly.</p>
518:<p>If you are trying to keep personal updates organized at home, an optional outside planning tool like this <a href="https://flatlogic.com/generator?utm_source=ridgecrestchurch.com">web app generator</a> may help you sketch a private reminder workflow for your own notes. That is only a neutral resource for personal organization. A short message through the church&rsquo;s normal contact channels is still all you need to submit a request.</p>
520:<p>Prayer requests often change. A situation may improve, become more urgent, or no longer need to be shared. That is normal. If something changes, send a short follow-up through the same public contact path you used before, or use <a href="/contacts.html">Contacts</a> if you are unsure where the earlier request went.</p>
533:<p>Yes. If something is urgent, say that near the top of the message and choose the clearest contact method available on <a href="/contacts.html">Contacts</a> or <a href="/contact.php">Contact Us</a>. Urgent does not require dramatic wording. A plain sentence is better: “This is urgent, and we would appreciate prayer today.”</p>
535:<p>Not by default. Public church communication should depend on appropriateness and permission, not assumption. If you are comfortable with broader sharing, say so. If you are not, say that too. The <a href="/news.html">News</a> page is for church updates, but personal requests should not be assumed to belong there.</p>
539:<p>If something is on your heart today, begin with one clear message. Use <a href="/contacts.html">Contacts</a> or <a href="/contact.php">Contact Us</a>, explain the need briefly, and tell the church whether the request is private or shareable. If you are sending a praise report, include that too. Churches need both kinds of messages: the ones that ask for prayer and the ones that say, with relief and gratitude, “Thank you. The Lord has been kind to us.”</p>
540:<p>And if you are still finding your way around the site, the <a href="/">home page</a>, <a href="/news.html">News</a>, and <a href="/resources">Resources</a> pages can help you take the next step without feeling rushed.</p>

 succeeded in 785ms:
413:			<header class="entry-header">	<h2 class="entry-title" itemprop="headline"><a href="https://ridgecrestchurch.com/submit-prayer-request-praise-report/" rel="bookmark">How to Submit a Prayer Request or Praise Report (and What Happens Next)</a></h2>
419:<a href="https://ridgecrestchurch.com/submit-prayer-request-praise-report/" title="How to Submit a Prayer Request or Praise Report (and What Happens Next)"><img width="4032" height="3024" data-src="https://ridgecrestchurch.com/wp-content/uploads/imports/worship-service.jpg" class="wp-post-image lazyload" alt="People gathered for a worship service at Ridgecrest Baptist Church" decoding="async" itemprop="image" src="data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==" style="--smush-placeholder-width: 4032px; --smush-placeholder-aspect-ratio: 4032/3024;" /></a><p>Learn how to share your prayer requests and praise reports with Ridgecrest Baptist Church, understand the process, and what to expect after submission.</p>

codex
I re-verified the existing implementation directly with `wp-cli` and live HTTP checks. No content change was needed: post `94` exists, is published, is assigned to `isla-bennett`, resolves at its public URL, includes a visible inline image in `post_content`, and contains the exact required Flatlogic body link. `/blog/` is configured as the posts index with page ID `23`, and the blog index surfaces this article.

I also checked the local media inventory for a closer prayer-request or prayer-team photo. None exists in the current site media beyond general church/worship/kids/youth imagery, so the current real photo remains in place. That is the only notable content-fit limitation. Backlink target `/` was not changed in this pass.

WP_POST_ID: 94
WP_POST_STATUS: publish
WP_POST_URL: https://ridgecrestchurch.com/submit-prayer-request-praise-report/
WP_AUTHOR_USER: isla-bennett / Isla Bennett
FEATURED_IMAGE_ID: 10
INLINE_IMAGE_IDS: 10
BLOG_INDEX_STATUS: ready; /blog/ is page ID 23 and `page_for_posts=23`
LINK_TARGETS_USED: https://flatlogic.com/generator?utm_source=ridgecrestchurch.com

Verified: `wp post get 94`, `wp post url 94`, live `curl -I/-L` on the post URL, `/blog/` live output, `page_for_posts`, featured image `10`, inline image ID `10`, and exact Flatlogic URL presence in article body. Limitation: no more directly relevant prayer-request/prayer-team photo exists in current local media, so the article still uses the best available real worship image.
tokens used
47,337
