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: 019ea33d-fbba-7740-93ca-b641142e1aef
--------
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: 0

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

codex
Reviewing the site context, article plan, and post-creator instructions first, then I’ll inspect the existing WordPress content and media so I can publish the post with the required links and image without guessing.
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' 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

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 "sed -n '1,260p' ARTICLE_CONTENT_PLAN.md" in /home/ubuntu/apps/ridgecrestchurch.com
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:
# 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:

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

 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 "rg --files wp-content/plugins/flatlogic-post-creator/context -g '*.md'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
wp-content/plugins/flatlogic-post-creator/context/PRINCIPLES.md

codex
I’ve got the site and article contract. Next I’m checking the post-creator context files plus the current WordPress state, existing blog index, author accounts, and media library so I can publish the post cleanly and verify it properly.
exec
/bin/bash -lc "ls -la wp-content/plugins/flatlogic-post-creator/context && sed -n '1,240p' wp-content/plugins/flatlogic-post-creator/context/PRINCIPLES.md && printf '\\n---FILE-END---\\n' && if [ -f wp-content/plugins/flatlogic-post-creator/context/FINAL_REQUIREMENTS.MD ]; then sed -n '1,240p' wp-content/plugins/flatlogic-post-creator/context/FINAL_REQUIREMENTS.MD; fi" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
total 44
drwxr-xr-x 2 ubuntu ubuntu  4096 Jun  2 10:53 .
drwxr-xr-x 3 ubuntu ubuntu  4096 Jun  2 10:53 ..
-rw-rw-r-- 1 ubuntu ubuntu  5502 Jun  2 10:53 FINAL_REQUIREMENTS.MD
-rw-rw-r-- 1 ubuntu ubuntu 24662 Jun  2 10:53 PRINCIPLES.md
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:

* consensus in the field,
* unresolved disagreement,
* missing evidence,
* cliché framing everyone uses,
* your likely point of difference.

### 4.4 Gate

If you cannot name at least **3** gaps in current coverage, you haven’t read enough.

---

## 5. Do primary reporting, not elegant aggregation

Rosenstiel makes originality explicit: do your own work. Google says its systems are built to surface original reporting prominently. For technical or product topics, firsthand testing is vastly stronger than secondhand description. ([Tom Rosenstiel][6])

### 5.1 Gather original material

Depending on the topic, that means:

---FILE-END---
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.

exec
/bin/bash -lc 'wp core is-installed && wp option get home && wp option get siteurl && wp theme list --status=active --format=table && wp db prefix' 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_date --format=table' in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc '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_name,post_mime_type,guid --format=table | sed -n '1,120p'" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc 'wp user list --fields=ID,user_login,display_name,user_email,roles --format=table' in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 748ms:
ID	post_title	post_name	post_mime_type	guid
89	Wednesday Night Kids Check-In Scene	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	ridgecrest-events-calendar-page-screenshot	image/png	http://ridgecrestchurch.com/wp-content/uploads/imports/events-calendar-page-screenshot.png
79	Ridgecrest Website Navigation Screenshot	ridgecrest-website-navigation-screenshot	image/png	https://ridgecrestchurch.com/ridgecrest-website-navigation-screenshot/
76	Sunday Service Planning Desk	sunday-service-planning-desk	image/jpeg	http://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg
1	Ridgecrest Baptist Church Logo	ridgecrest-baptist-church-logo	image/gif	https://ridgecrestchurch.com/wp-content/uploads/imports/logo.gif
2	Ridgecrest Service Times	ridgecrest-service-times	image/gif	https://ridgecrestchurch.com/wp-content/uploads/imports/service-times.gif
3	Ridgecrest Events Calendar	ridgecrest-events-calendar	image/gif	https://ridgecrestchurch.com/wp-content/uploads/imports/events.gif
4	Ridgecrest Connection Graphic	ridgecrest-connection-graphic	image/gif	https://ridgecrestchurch.com/wp-content/uploads/imports/connect.gif
5	Ridgecrest Sermons Graphic	ridgecrest-sermons-graphic	image/gif	https://ridgecrestchurch.com/wp-content/uploads/imports/sermons.gif
6	Ridgecrest Contact Graphic	ridgecrest-contact-graphic	image/gif	https://ridgecrestchurch.com/wp-content/uploads/imports/contact-info.gif
7	Ridgecrest Map Graphic	ridgecrest-map-graphic	image/gif	https://ridgecrestchurch.com/wp-content/uploads/imports/map-directions.gif
8	Ridgecrest Community Illustration	ridgecrest-community-illustration	image/jpeg	https://ridgecrestchurch.com/wp-content/uploads/imports/groups.jpg
9	Ridgecrest Main Entrance	church-exterior	image/jpeg	https://ridgecrestchurch.com/wp-content/uploads/imports/church-exterior.jpg
10	Worship Service	worship-service	image/jpeg	https://ridgecrestchurch.com/wp-content/uploads/imports/worship-service.jpg
11	Children Ministry	children-ministry	image/jpeg	https://ridgecrestchurch.com/wp-content/uploads/imports/children-ministry.jpg
12	Youth Worship	youth-worship	image/jpeg	https://ridgecrestchurch.com/wp-content/uploads/imports/youth-worship.jpg

 succeeded in 822ms:
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

 succeeded in 848ms:
ID	post_title	post_name	post_status	post_date
93	Church Resources for New Families: Where to Start This Week	church-resources-for-new-families	publish	2026-06-04 12:02:39
91	What to Bring (and Wear) to Church at Ridgecrest: A Practical Guide for Sundays	what-to-bring-and-wear-to-church-ridgecrest	publish	2026-06-01 14:32:23
88	How to Prepare for a Youth or Kids Wednesday Night Program	prepare-for-wednesday-kids-youth	publish	2026-05-24 13:03:30
87	How to Use Our Events Calendar: RSVP, Reminders, and What to Bring	how-to-use-events-calendar-rsvp-reminders-what-to-bring	publish	2026-05-20 13:34:08
80	What to Expect at Ridgecrest Baptist Church (Visitor-Friendly Guide)	what-to-expect-ridgecrest-baptist-church	publish	2026-05-17 13:02:29
78	How to Get Involved at Ridgecrest: A First-Timer’s Guide to Ministries, Kids, and Youth	get-involved-first-timers-guide	publish	2026-05-14 13:03:50
77	How to Plan a Great Sunday: A Simple Church Service Checklist	how-to-plan-a-great-sunday-checklist	publish	2026-05-11 15:03:13
74	How to Plan Your First Visit to Ridgecrest Baptist Church	first-visit-ridgecrest-baptist-church	publish	2026-05-08 13:12:34
51	Welcome to Ridgecrest News	welcome-to-ridgecrest-news	publish	2026-05-07 04:49:19

 succeeded in 971ms:
ID	user_login	display_name	user_email	roles
1	admin	admin	admin@ridgecrestchurch.com	administrator
3	grant-vale	Grant Vale	grant-vale@ridgecrestchurch.com	author
4	isla-bennett	Isla Bennett	isla-bennett@ridgecrestchurch.com	author
2	lena-ortiz	Lena Ortiz	lena-ortiz@ridgecrestchurch.com	author
5	marcus-reed	Marcus Reed	marcus-reed@ridgecrestchurch.com	author
7	nora-finch	Nora Finch	nora-finch@ridgecrestchurch.com	author
6	rowan-ellis	Rowan Ellis	rowan-ellis@ridgecrestchurch.com	author

codex
The site already has the required pages, the `Blog` page, and the author account I need. I’m polling the remaining WordPress checks now, then I’ll inspect the relevant existing pages and recent post structure so the new article matches the site’s tone and linking pattern.
 succeeded in 8845ms:
https://ridgecrestchurch.com
https://ridgecrestchurch.com
name	status	update	version	update_version	auto_update
church	active	none	0.7.7		off
flbg_

exec
/bin/bash -lc "wp post get 20 --field=post_content | sed -n '1,240p'" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "wp post get 22 --field=post_content | sed -n '1,220p'" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "wp post get 19 --field=post_content | sed -n '1,220p'" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "wp post get 93 --field=post_content | sed -n '1,260p'" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc 'wp option get page_for_posts && wp option get show_on_front && wp option get page_on_front && wp post url 23' in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 653ms:
<p><strong><em>If you are new to Ridgecrest and trying to figure out where to begin, the short answer is this: start with a few key pages, make one simple plan for the week, and let the church know what would make your family’s first visit easier.</em></strong></p>

<p>New families usually ask a pretty practical set of questions: Where do we park? Which page matters first? What should we read before showing up with kids or students in tow? That is a normal place to start. Church websites can feel a little like opening ten tabs when you only needed three.</p>

<p>This guide gives you a quick map of the most helpful Ridgecrest pages, a five-to-ten-minute plan for this week, and a few simple questions to ask before your first visit. If you like the plain version first, you are in the right place.</p>

<figure class="wp-block-image size-large"><img src="https://ridgecrestchurch.com/wp-content/uploads/imports/church-exterior.jpg" alt="Main entrance at Ridgecrest Baptist Church in Blanchard, Oklahoma" class="wp-image-9" /><figcaption>The main entrance is a helpful landmark to notice before your first visit.</figcaption></figure>

<h2>Start Here: The Most Helpful Pages for Families</h2>
<p>If you only have a few minutes, these are the pages worth opening first:</p>
<ul>
<li><a href="https://ridgecrestchurch.com/">Home</a>: a quick first look at the church and the main paths families use most often.</li>
<li><a href="https://ridgecrestchurch.com/about-us/">About Us</a>: the best place to get a feel for Ridgecrest&rsquo;s tone, values, and what kind of church life matters here.</li>
<li><a href="https://ridgecrestchurch.com/kids/">Kids</a>: helpful if you have preschool or elementary-age children and want to review class timing, check-in expectations, and where to ask questions.</li>
<li><a href="https://ridgecrestchurch.com/youth/">Youth</a>: the page to open if you have a student in 6th through 12th grade and want the plain version of the weekly rhythm.</li>
<li><a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>: the fastest way to confirm what is happening this week and whether anything special is changing the normal schedule.</li>
<li><a href="https://ridgecrestchurch.com/news/">News</a>: useful for headline updates, reminders, and church-wide announcements.</li>
<li><a href="https://ridgecrestchurch.com/contacts/">Contacts</a>: where to go when one clear answer from a real person would save you ten minutes of guessing.</li>
<li><a href="https://ridgecrestchurch.com/church-map/">Church Map</a>: the page that helps you sort out the route before Sunday morning or Wednesday night.</li>
</ul>

<h2>This Week&rsquo;s Plan in 5 to 10 Minutes</h2>
<p>Here is a simple first-week plan for families who want to get oriented without turning it into a homework assignment:</p>
<ol>
<li><strong>Check the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>.</strong> Confirm the current weekly rhythm. Ridgecrest lists Sunday classes at 8:45 a.m., Sunday worship at 10:00 a.m., and Wednesday kids and youth gatherings beginning at 6:30 p.m.</li>
<li><strong>Read the latest <a href="https://ridgecrestchurch.com/news/">News</a> page.</strong> This helps you spot current reminders and any church-wide announcements before you arrive.</li>
<li><strong>Open the page that fits your family.</strong> Parents with younger children should review <a href="https://ridgecrestchurch.com/kids/">Kids</a>. Families with teenagers should read <a href="https://ridgecrestchurch.com/youth/">Youth</a>. Some families need both tabs, which is a very modern form of cardio.</li>
<li><strong>Look at the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a>.</strong> The address, route link, and arrival notes make the first visit feel less uncertain.</li>
<li><strong>Keep the <a href="https://ridgecrestchurch.com/contacts/">Contacts</a> page open.</strong> If one question is still hanging around, send it before you visit.</li>
</ol>

<h2>What to Look for on the Kids and Youth Pages</h2>
<p>When you open a ministry page, do not just skim for a title and move on. Look for the details that make the first visit smoother.</p>

<table>
<thead>
<tr>
<th>Page</th>
<th>What to notice</th>
<th>Why it helps</th>
</tr>
</thead>
<tbody>
<tr>
<td><a href="https://ridgecrestchurch.com/kids/">Kids</a></td>
<td>Sunday classes begin at 8:45 a.m. The page also notes that preschool meets in the main building and kindergarten through 5th grade meets in the children&rsquo;s building on Wednesdays beginning at 6:30 p.m.</td>
<td>You can decide whether Sunday morning or Wednesday night is the better first step and know which part of campus applies to your child.</td>
</tr>
<tr>
<td><a href="https://ridgecrestchurch.com/youth/">Youth</a></td>
<td>The page explains that Ridgecrest Youth serves students in 6th through 12th grade and gathers on Wednesdays beginning at 6:30 p.m. for worship, teaching, discussion, and fellowship.</td>
<td>You know the age range, the basic format, and the weekly entry point without having to guess whether a student program fits your family.</td>
</tr>
<tr>
<td>Both pages</td>
<td>Notice how often they point back to <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>, <a href="https://ridgecrestchurch.com/news/">News</a>, and <a href="https://ridgecrestchurch.com/contacts/">Contacts</a>.</td>
<td>That pattern tells you where the church expects families to confirm updates, ask questions, and plan ahead.</td>
</tr>
</tbody>
</table>

<p>The short answer is that you are looking for <strong>times, age ranges, location clues, and the best contact path</strong>. Once you have those four things, the first visit tends to feel much more normal.</p>

<h2>How to Use the Church Map Before You Arrive</h2>
<p>The <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> page is not just for people who are new to town. It is also helpful for families who want to remove one more unknown before loading everyone into the car.</p>

<p>Ridgecrest lists the campus at <strong>1118 S. Sara Road, Blanchard, OK 73010</strong> and provides a direct map link. The page also points families toward the main campus entrance and suggests arriving a few minutes early, especially if you are visiting with children. That is good low-drama advice. Early arrival is rarely glamorous, but it is very effective.</p>

<p>If you need details beyond the basic route, such as accessibility help or the best place to start with young children, use the <a href="https://ridgecrestchurch.com/contacts/">Contacts</a> page before you come. That is better than making a brave but uninformed parking-lot decision.</p>

<h2>How to Contact Ridgecrest and What to Include</h2>
<p>The <a href="https://ridgecrestchurch.com/contacts/">Contacts</a> page gives families three clear options: email, phone, and address details for the church campus. If you want the fastest helpful reply, include the kind of details that let staff point you to the right page or ministry right away.</p>

<ul>
<li>Your child or student&rsquo;s age range.</li>
<li>Whether you are planning to visit on a Sunday morning or Wednesday evening.</li>
<li>Any question about check-in, where to go first, or which building applies to your family.</li>
<li>Accessibility needs, arrival concerns, or anything else that would make the first visit easier.</li>
<li>If you are looking for one person to start with, whether your question is general, kids-related, or youth-related.</li>
</ul>

<p>You can also use the public contact details already listed on the site: <a href="mailto:admin@ridgecrestchurch.com">admin@ridgecrestchurch.com</a>, phone <strong>(405) 387-2811</strong>, and the Blanchard campus address above.</p>

<p>If your family likes keeping one simple planning list for school, church, and activities in the same place, a neutral outside resource like <a href="https://flatlogic.com/build/education-app-builder?utm_source=ridgecrestchurch.com">https://flatlogic.com/build/education-app-builder?utm_source=ridgecrestchurch.com</a> may give you ideas for organizing that workflow. It is not required for visiting Ridgecrest, of course. A calendar check and one clear message to the church will do the job just fine.</p>

<h2>FAQ: A Few Questions New Families Usually Ask</h2>
<h3>Do we need to register first?</h3>
<p>Usually, the simplest starting point is just to review the page that fits your family and come to a regular gathering. If a special event needs extra details, the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> or <a href="https://ridgecrestchurch.com/news/">News</a> page is the place to watch for that information. If you do not see the answer, ask before you come.</p>

<h3>What if we miss a Wednesday?</h3>
<p>That is not a problem. You do not need to treat one missed week like a closed door. Check the next gathering on the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>, read the latest <a href="https://ridgecrestchurch.com/news/">News</a> update, and start with the next clear opportunity.</p>

<h3>Can we visit before committing?</h3>
<p>Yes. Ridgecrest&rsquo;s public pages repeatedly point visitors toward a welcoming, low-pressure first step. The <a href="https://ridgecrestchurch.com/about-us/">About Us</a> page and the home page both frame the church as a place where people can come, listen, and ask honest questions without pressure to perform.</p>

<h3>What if I still do not know where to go when we arrive?</h3>
<p>Use the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> and <a href="https://ridgecrestchurch.com/contacts/">Contacts</a> pages ahead of time, and if you still feel unsure, arrive a few minutes early and ask for help at the entrance. That is a completely normal first-visit move.</p>

<h2>A Simple Next Step for This Week</h2>
<p>If you want the short version, here it is: open <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>, read <a href="https://ridgecrestchurch.com/news/">News</a>, review <a href="https://ridgecrestchurch.com/kids/">Kids</a> or <a href="https://ridgecrestchurch.com/youth/">Youth</a>, then use <a href="https://ridgecrestchurch.com/contacts/">Contacts</a> to confirm anything that still feels unclear.</p>

<p>That small plan is enough to turn a vague &ldquo;maybe sometime&rdquo; into a real next step. If your family is ready to visit, use the church site as your map and let Ridgecrest know what would help you feel prepared for the next service or program.</p>

 succeeded in 717ms:
<section class="rc-hero">
  <div>
    <p class="rc-eyebrow">Contacts</p>
    <h1>Reach out before you visit or whenever you need help getting connected.</h1>
    <p>If you have questions about worship times, children’s ministry, student ministry, prayer needs, or how to find the church, we are glad to help.</p>
    <ul class="rc-meta">
      <li><strong>Email</strong> <a href="mailto:admin@ridgecrestchurch.com">admin@ridgecrestchurch.com</a></li>
      <li><strong>Phone</strong> (405) 387-2811</li>
      <li><strong>Address</strong> 1118 S. Sara Road, Blanchard, OK 73010</li>
    </ul>
  </div>
  <figure class="rc-media"><img src="https://ridgecrestchurch.com/wp-content/uploads/imports/church-exterior.jpg" alt="Exterior view of Ridgecrest Baptist Church" loading="lazy"></figure>
</section>

<section class="rc-section">
  <div class="rc-grid rc-grid-2">
    <div class="rc-card">
      <h2>General questions</h2>
      <p>Email <a href="mailto:admin@ridgecrestchurch.com">admin@ridgecrestchurch.com</a> for first-visit questions, ministry information, event details, or prayer needs.</p>
    </div>
    <div class="rc-card">
      <h2>Phone support</h2>
      <p>Call (405) 387-2811 if you need help on Sunday morning, directions to the campus, or clarification about a ministry gathering.</p>
    </div>
  </div>
</section>

<section class="rc-section rc-split">
  <div>
    <h2>How we can help before your first visit</h2>
    <p>Let us know whether you need directions, kids ministry details, or guidance on where to start. We can point you to the right page, gathering, or ministry contact so your first visit feels simple.</p>
    <p>You may also want to review the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> and <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> before you come.</p>
  </div>
  <figure class="rc-media"><img src="https://ridgecrestchurch.com/wp-content/uploads/imports/church-exterior.jpg" alt="Church exterior and entrance" loading="lazy"></figure>
</section>

<section class="rc-section">
  <div class="rc-card rc-card-wide">
    <figure class="rc-media rc-media-small"><img src="https://ridgecrestchurch.com/wp-content/uploads/imports/church-exterior.jpg" alt="Church campus entrance in Blanchard" loading="lazy"></figure>
    <div>
      <h2>Need directions right now?</h2>
      <p>Visit the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> page for route guidance, nearby community references, and a direct map link.</p>
    </div>
  </div>
</section>

 succeeded in 804ms:
<section class="rc-hero">
  <div>
    <p class="rc-eyebrow">News</p>
    <h1>Church news, announcements, and practical updates for the Ridgecrest family.</h1>
    <p>This page highlights the kinds of updates members and guests most often need: schedule reminders, ministry highlights, student and kids activities, and church-wide announcements. Longer written updates will also appear on the <a href="https://ridgecrestchurch.com/blog/">Blog</a> as posts are published.</p>
    <div class="rc-actions">
      <a class="rc-button" href="https://ridgecrestchurch.com/blog/">Visit the Blog</a>
      <a class="rc-button secondary" href="https://ridgecrestchurch.com/events-calendar/">See Upcoming Events</a>
    </div>
  </div>
  <figure class="rc-media"><img src="https://ridgecrestchurch.com/wp-content/uploads/imports/worship-service.jpg" alt="Church family during worship service" loading="lazy"></figure>
</section>

<section class="rc-section">
  <div class="rc-grid rc-grid-2">
    <div class="rc-card">
      <h3>This week at Ridgecrest</h3>
      <p>Sunday classes meet at 8:45 a.m. and worship begins at 10:00 a.m. Wednesday night kids and youth ministries begin at 6:30 p.m.</p>
    </div>
    <div class="rc-card">
      <h3>Where to look next</h3>
      <p>Use the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for dates and the <a href="https://ridgecrestchurch.com/resources/">Resources</a> page for study support, family helps, and church-life tools.</p>
    </div>
  </div>
</section>

<section class="rc-section rc-split">
  <div>
    <h2>Announcements we share regularly</h2>
    <ul class="rc-bullets">
      <li>Weekly worship and ministry reminders</li>
      <li>Student and children’s ministry events</li>
      <li>Church-wide fellowship meals and special gatherings</li>
      <li>Prayer needs and ministry opportunities</li>
    </ul>
    <p>If you need to confirm a detail before visiting, use the <a href="https://ridgecrestchurch.com/contacts/">Contacts</a> page.</p>
  </div>
  <figure class="rc-media"><img src="https://ridgecrestchurch.com/wp-content/uploads/imports/worship-service.jpg" alt="Church worship gathering" loading="lazy"></figure>
</section>

<section class="rc-section rc-callout">
  <h2>Stay informed without missing the essentials</h2>
  <p>Check this page for headline items, then visit the Blog for future article-style updates and ministry stories.</p>
  <div class="rc-actions">
    <a class="rc-button secondary" href="https://ridgecrestchurch.com/blog/">Open Blog Index</a>
    <a class="rc-button secondary" href="https://ridgecrestchurch.com/resources/">Open Resources</a>
  </div>
</section>

 succeeded in 881ms:
<section class="rc-hero">
  <div>
    <p class="rc-eyebrow">Resources</p>
    <h1>Helpful tools for Bible study, family discipleship, and staying connected to church life.</h1>
    <p>This page gathers practical resources that support worship on Sunday and faithfulness throughout the week. It is a useful starting point for members, guests, and ministry volunteers who want one place for the most-requested links.</p>
    <div class="rc-actions">
      <a class="rc-button" href="https://ridgecrestchurch.com/news/">Read Current News</a>
      <a class="rc-button" href="https://ridgecrestchurch.com/blog/">Visit the Blog</a>
    </div>
  </div>
  <figure class="rc-media"><img src="https://ridgecrestchurch.com/wp-content/uploads/imports/worship-service.jpg" alt="Church worship and Bible teaching" loading="lazy"></figure>
</section>

<section class="rc-section">
  <div class="rc-grid rc-grid-2">
    <div class="rc-card">
      <h2>Worship and study support</h2>
      <p>Use this page for sermon follow-up, Bible reading prompts, and reminders about where the church is gathering during the week. Start with the <a href="https://ridgecrestchurch.com/news/">News</a> page for current announcements and the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for timing.</p>
    </div>
    <div class="rc-card">
      <h2>Family discipleship</h2>
      <p>Parents can coordinate with our <a href="https://ridgecrestchurch.com/kids/">Kids</a> and <a href="https://ridgecrestchurch.com/youth/">Youth</a> pages to help children and students carry the truths of Sunday into the rest of the week.</p>
    </div>
  </div>
</section>

<section class="rc-section rc-split">
  <div>
    <h2>Planning tools for church administration</h2>
    <p>Most church communication still works well through conversation, email, and simple calendars. When a staff or volunteer team wants to sketch a lightweight internal process for follow-up, registration, or reminders, a <a href="https://appwizzy.com/">vibe coding tool</a> can help them test the idea before adopting anything permanent.</p>
    <p>If a church or nonprofit eventually needs a more tailored workflow for registrations, ministry databases, or event communication, it may be worth reviewing <a href="https://flatlogic.com/services/custom-web-development-services?utm_source=ridgecrestchurch.com">custom web development services</a> alongside the existing process.</p>
  </div>
  <figure class="rc-media"><img src="https://ridgecrestchurch.com/wp-content/uploads/imports/church-exterior.jpg" alt="Church campus supporting ministry throughout the week" loading="lazy"></figure>
</section>

<section class="rc-section">
  <div class="rc-card rc-card-wide">
    <figure class="rc-media rc-media-small"><img src="https://ridgecrestchurch.com/wp-content/uploads/imports/church-exterior.jpg" alt="Exterior view of Ridgecrest Baptist Church" loading="lazy"></figure>
    <div>
      <h2>Need a simple next step?</h2>
      <p>If you are new to Ridgecrest, start with <a href="https://ridgecrestchurch.com/about-us/">About Us</a>, then check <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> and <a href="https://ridgecrestchurch.com/contacts/">Contacts</a> before your first visit.</p>
    </div>
  </div>
</section>

 succeeded in 2508ms:
23
page
13
https://ridgecrestchurch.com/blog/

codex
I’ve checked the current content pattern. The remaining work is straightforward: find a credible prayer-related image, draft the post in the site’s existing article style, publish it under Isla Bennett, and then run the required WordPress and public-url verification.
exec
/bin/bash -lc "curl -I -L -s https://ridgecrestchurch.com/contacts.html | sed -n '1,20p'" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "find wp-content/uploads -maxdepth 3 -type f | sed -n '1,220p'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
wp-content/uploads/imports/contact-info.gif
wp-content/uploads/imports/service-times.gif
wp-content/uploads/imports/youth-worship.jpg
wp-content/uploads/imports/youth-group.jpg
wp-content/uploads/imports/ridgecrest-home-navigation-screenshot.png
wp-content/uploads/imports/events.gif
wp-content/uploads/imports/map-directions.gif
wp-content/uploads/imports/sermons.gif
wp-content/uploads/imports/logo.gif
wp-content/uploads/imports/groups.jpg
wp-content/uploads/imports/wednesday-night-kids-check-in-scene.jpg
wp-content/uploads/imports/church-exterior.jpg
wp-content/uploads/imports/children-ministry.jpg
wp-content/uploads/imports/connect.gif
wp-content/uploads/imports/events-calendar-page-screenshot.png
wp-content/uploads/imports/worship-service.jpg
wp-content/uploads/imports/sunday-service-planning-desk.jpg
wp-content/uploads/flatlogic-article-tasks/job-185/task.md
wp-content/uploads/flatlogic-article-tasks/job-25/check-article-image.php
wp-content/uploads/flatlogic-article-tasks/job-25/task.md
wp-content/uploads/flatlogic-article-tasks/job-25/first-visit-post.html
wp-content/uploads/flatlogic-article-tasks/job-122/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-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-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-131/task.md
wp-content/uploads/flatlogic-article-tasks/job-36/check-article-image.php
wp-content/uploads/flatlogic-article-tasks/job-36/task.md
wp-content/uploads/flatlogic-article-tasks/job-36/how-to-plan-a-great-sunday-checklist.html
wp-content/uploads/flatlogic-article-tasks/job-63/what-to-expect-ridgecrest-baptist-church.html
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-101/check-article-image.php
wp-content/uploads/flatlogic-article-tasks/job-101/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-148/task.md
wp-content/uploads/flatlogic-article-tasks/job-255/task.md
wp-content/uploads/flatlogic-page-tasks/job-44/task.md
wp-content/uploads/flatlogic-page-tasks/job-44/build_site.php
wp-content/uploads/flatlogic-site-polish-tasks/job-44/task.md

exec
/bin/bash -lc "curl -I -L -s https://ridgecrestchurch.com/contact.php | sed -n '1,20p'" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "curl -I -L -s https://ridgecrestchurch.com/news.html | sed -n '1,20p'" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "curl -I -L -s https://ridgecrestchurch.com/resources | sed -n '1,20p'" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "wp post get 88 --field=post_content | sed -n '1,240p'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 535ms:
HTTP/2 301 
date: Sun, 07 Jun 2026 18:00:46 GMT
content-type: text/html; charset=iso-8859-1
location: http://ridgecrestchurch.com/contacts/
server: cloudflare
cf-cache-status: DYNAMIC
report-to: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=O2xuhGZSENnbwWX4tJzM7iNsmRhIdV6TS1KxQSP4tq5nssIOOsn1KZ4lb7%2FcJ%2BXNbJMWMUMvA9GHcHancTBi2Wml8KPugl%2BX1OhSPVCN%2BKkJuP15ZEzH%2BKhF7FbA9aO9ccMBKBC%2B0Q%3D%3D"}]}
nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
cf-ray: a0818eeb9d0164d7-WAW
alt-svc: h3=":443"; ma=86400

HTTP/1.1 200 OK
Date: Sun, 07 Jun 2026 18:00:47 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
link: <https://ridgecrestchurch.com/wp-json/>; rel="https://api.w.org/", <https://ridgecrestchurch.com/wp-json/wp/v2/pages/20>; rel="alternate"; title="JSON"; type="application/json", <https://ridgecrestchurch.com/?p=20>; 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=8DL64RO2nl9jWt4SUp9NtGnpUFfRedZ6fFPbvyhtAZGGE6BhQeffbuXQ%2BMBiULbSFeXPeUPUf9b3tb1zftqk60qL7cvgJY39ftFsOyX3nJS7LVvFK7QKU%2FYEDlxNxT8KdhE633lhYQ%3D%3D"}]}
Nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}

 succeeded in 526ms:
HTTP/2 301 
date: Sun, 07 Jun 2026 18:00:46 GMT
content-type: text/html; charset=iso-8859-1
location: http://ridgecrestchurch.com/news/
server: cloudflare
cf-cache-status: DYNAMIC
report-to: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=k7Vlmmn9B9KPBZg%2BI13wPxuhdvc6SlVMjfeZph3vjDjalFRdv%2FIfx0ywoJFWYEJ1%2F51vxGirTolUZxUdGlbnaVCx0a0%2BUhLU%2B62MnNI9OJAimtc4Sp3Ls1VZVrn9eh1mIeaId%2FzLQg%3D%3D"}]}
nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
cf-ray: a0818eec6e674a11-WAW
alt-svc: h3=":443"; ma=86400

HTTP/1.1 200 OK
Date: Sun, 07 Jun 2026 18:00:47 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
link: <https://ridgecrestchurch.com/wp-json/>; rel="https://api.w.org/", <https://ridgecrestchurch.com/wp-json/wp/v2/pages/19>; rel="alternate"; title="JSON"; type="application/json", <https://ridgecrestchurch.com/?p=19>; 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=UlGHIwJgQMtkm3H%2FqX11mKrnuyz8I6usFM0IWrcsN8K3iX8tSrbp9xQh7TIdRaCfDf1D0HzDQRYJ9z%2B31UwxAbwO0iVyX%2BFIohVQw1Mh5UZx6JSME6dDfs6VYHkfOM%2BhE4OdK3Oadw%3D%3D"}]}
Nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}

 succeeded in 591ms:
<p><strong><em>If Wednesday Night is your child’s first trip to Ridgecrest Kids or Youth, the goal is not to predict every detail. The safer plan is to confirm the current listing, bring the basics, arrive with a little margin, and know who to ask if something changes.</em></strong></p>

<p><strong>By Lena Ortiz</strong> | Updated May 24, 2026</p>

<p>This guide is for parents and guardians bringing children or students to a Ridgecrest Wednesday Night program. It is a preparation checklist and a simple walkthrough, not a replacement for that week’s instructions. The order is straightforward: check the details, pack the essentials, handle arrival and check-in, understand the general flow, and finish with a clear pickup plan.</p>

<p>The weekly details still matter most. Before you leave home, verify the specific Wednesday on the <a href="/events-calendar/">Events Calendar</a> and scan <a href="/news.html">News</a> for reminders or schedule changes. Last-minute questions are easier when you have already checked the listing.</p>

<figure class="wp-block-image size-large">
  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/wednesday-night-kids-check-in-scene.jpg" alt="Children&#8217;s ministry check-in area with volunteers helping families register before a program begins" class="wp-image-89" />
  <figcaption>Illustrative children&#8217;s ministry check-in area showing how a Wednesday Night arrival station may be organized. Photo by PortableChurch, used under CC BY-ND 2.0.</figcaption>
</figure>

<h2>Quick overview: who this is for and how Wednesday Night usually works</h2>

<p>If your family is heading to <a href="/kids.html">Kids</a> or <a href="/youth.html">Youth</a> on a Wednesday evening, the reasonable default is to think in phases rather than trying to memorize a hundred tiny details. In most cases, the evening works like this:</p>

<ol>
  <li><strong>Before you come:</strong> confirm the latest information for that Wednesday.</li>
  <li><strong>Arrival:</strong> park, go to the entry or check-in area, and let staff or volunteers guide the next step.</li>
  <li><strong>Program time:</strong> children and students move into their age-group setting for teaching, activities, and time together.</li>
  <li><strong>Pickup:</strong> return at the listed dismissal time and follow the church’s release process.</li>
</ol>

<p>The site’s current pages give a few stable reference points. Ridgecrest’s <a href="/kids.html">Kids</a> page says preschool meets in the main building and kindergarten through 5th grade meets in the children’s building beginning at 6:30 p.m. The <a href="/youth.html">Youth</a> page says students in 6th through 12th grade also gather beginning at 6:30 p.m. Even so, the safest practice is still to verify the specific Wednesday on the calendar and news pages before you head out.</p>

<h2>Before you come: check the latest details first</h2>

<p>Most midweek confusion comes from assuming one normal week looks exactly like the next. Sometimes it does. Sometimes a reminder, room note, or special activity changes the pattern enough that you will be glad you checked first.</p>

<ul>
  <li><strong>Start with <a href="/events-calendar/">the Events Calendar</a>.</strong> Confirm the Wednesday Night listing, timing, and whether the note points you to another page.</li>
  <li><strong>Then read <a href="/news.html">News</a>.</strong> Use it to catch reminders, highlights, or any church-wide announcement that might affect the evening.</li>
  <li><strong>If you are new to Ridgecrest, review <a href="/about.html">About Us</a>.</strong> It gives helpful context for how the church approaches family ministry without turning this article into a general first-visit guide.</li>
  <li><strong>If anything still feels unclear, use <a href="/contacts.html">Contacts</a> before you leave home.</strong> Asking one direct question is better than guessing three policies in the parking lot.</li>
</ul>

<p>If you are unsure where to go or whether the week includes anything unusual, plan to arrive a little early. That is the safest reasonable default for first-time families and for weeks with special notes.</p>

<h2>What to bring: essentials checklist</h2>

<p>Most families do not need a complicated packing routine. A short, repeatable checklist is usually enough.</p>

<ul>
  <li><strong>Comfortable clothes</strong> that fit a normal church evening with group activity.</li>
  <li><strong>A labeled water bottle</strong> if that helps your child or student stay settled.</li>
  <li><strong>A Bible or notebook</strong> if your child’s group uses it, or if your student likes to take notes.</li>
  <li><strong>Any form or information the church requested</strong> in that week’s listing or message.</li>
  <li><strong>Necessary medical or care information</strong> that leaders should know before the program begins.</li>
  <li><strong>A small comfort item</strong> only if your child is allowed to bring one; if you are not sure, confirm at check-in.</li>
</ul>

<p>If the <a href="/events-calendar/">Events Calendar</a> or <a href="/news.html">News</a> page mentions something specific for that week, follow that instruction over any general checklist. The recurring plan is helpful, but the current note wins.</p>

<p>Some families also prefer a simple digital checklist so nothing gets missed during the dinner-to-carpool transition. If that is your style, this neutral resource on a <a href="https://flatlogic.com/generator?utm_source=ridgecrestchurch.com">web app generator</a> can help you sketch a private reminder workflow for your household.</p>

<h2>Arrival and check-in: where to go first</h2>

<p>For most families, the best arrival plan is simple: park, head toward the main entry or designated check-in area, and let the first staff member or volunteer you meet point you the rest of the way. The site does not publish a full room-by-room Wednesday Night map, so this article should not pretend otherwise.</p>

<p>What check-in typically involves:</p>

<ul>
  <li>The parent or guardian gives the child’s or student’s name.</li>
  <li>Staff or volunteers confirm where that age group is gathering.</li>
  <li>You share any important pickup information if the church requests it.</li>
  <li>Your child or student is guided to the next step.</li>
</ul>

<p>Have these basics ready before you walk in:</p>

<ul>
  <li>Child or student name</li>
  <li>Parent or guardian name</li>
  <li>Best phone number for that evening</li>
  <li>Authorized pickup information if someone else may arrive at dismissal</li>
  <li>Any urgent health, allergy, or accessibility note</li>
</ul>

<p>If plans change on the way to church, or if you realize you need to ask before you arrive, the fastest clean path is the <a href="/contacts.html">Contacts</a> page. The site currently lists <code>admin@ridgecrestchurch.com</code> and <code>(405) 387-2811</code>, which is more reliable than trying to locate the right person after the program is already moving.</p>

<h2>During the program: what to expect at a high level</h2>

<p>The purpose of this section is orientation, not overpromising. Wednesday Night programs are typically age-grouped gatherings led by church staff and volunteers. According to the current ministry pages, Kids serves preschool through elementary ages, and Youth serves students in grades 6 through 12.</p>

<p>In most cases, families can expect a general rhythm like this:</p>

<table>
  <thead>
    <tr>
      <th>Phase</th>
      <th>What usually happens</th>
      <th>What parents should watch for</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Arrival</td>
      <td>Families check in, confirm the right group, and get oriented.</td>
      <td>Ask your first-night questions here instead of saving them for pickup.</td>
    </tr>
    <tr>
      <td>Group time</td>
      <td>Children or students join their age-based setting with leaders and peers.</td>
      <td>Make sure leaders know any urgent instructions that affect the evening.</td>
    </tr>
    <tr>
      <td>Teaching and activities</td>
      <td>Expect a mix of Bible teaching, discussion, prayer, and age-appropriate activity.</td>
      <td>If the weekly listing mentions a special theme or item, use that as your reference point.</td>
    </tr>
    <tr>
      <td>Wrap-up and dismissal</td>
      <td>The program ends at the dismissal time listed for that Wednesday.</td>
      <td>Be ready for pickup on time and follow the church’s release process.</td>
    </tr>
  </tbody>
</table>

<p>If you want ministry-specific background before the first week, the <a href="/kids.html">Kids</a> and <a href="/youth.html">Youth</a> pages give a more complete picture of how Ridgecrest describes each ministry.</p>

<h2>Communication: how to reach leaders if something changes</h2>

<p>Parents usually need one thing during a midweek program: a clear communication path if plans shift. If you are delayed, need to update pickup, or want to flag a concern before the evening begins, use the contact route the church already publishes.</p>

<ul>
  <li><strong>Start with <a href="/contacts.html">Contacts</a>.</strong> That page has the current phone number, email address, and physical address.</li>
  <li><strong>Use the weekly listing if it names a specific Wednesday Night contact.</strong> When a one-off event has a special instruction, follow that instruction first.</li>
  <li><strong>Choose the simplest path.</strong> Contacting the church office or listed point of contact is usually safer than trying to track down an individual leader while the program is underway.</li>
</ul>

<p>The practical rule is simple: send useful information early. “My daughter is coming to Kids, and my husband will handle pickup tonight” is better than leaving everyone to reconstruct the plan at dismissal.</p>

<h2>Pickup process: timing and authorized pickup</h2>

<p>Pickup is where a calm plan pays off. The objective is not speed for its own sake; it is clarity. Plan to arrive at the dismissal time listed for that Wednesday, and assume the church will want to release children to the correct adult rather than to the nearest familiar-looking person.</p>

<p>A typical pickup pattern looks like this:</p>

<ol>
  <li>Arrive on time for the dismissal window listed on the weekly entry.</li>
  <li>Go to the pickup or release area identified by staff or volunteers.</li>
  <li>Confirm that you are the parent, guardian, or authorized pickup person if asked.</li>
  <li>Receive your child and any final instruction for the evening or the next week.</li>
</ol>

<p>If someone else needs to pick up your child or student, do not rely on improvisation. Follow the church’s process for that Wednesday if it is listed, or contact the church ahead of time through <a href="/contacts.html">Contacts</a>. The point is to reduce confusion, not create a dramatic reveal at the end of the night.</p>

<h2>Allergies and accessibility: flag needs ahead of time</h2>

<p>If your child has an allergy, mobility need, communication support need, or another accessibility consideration, it is wise to communicate that before Wednesday Night when possible. Early notice gives the church time to respond well and saves you from having to compress important details into a 20-second doorway conversation.</p>

<p>Use <a href="/contacts.html">Contacts</a> and include:</p>

<ul>
  <li>Child or student name</li>
  <li>What to avoid or watch for</li>
  <li>What helps your child participate well</li>
  <li>Any pickup or communication instruction connected to that need</li>
</ul>

<p>You do not need to write a full case file. A short, clear message is usually the best fit.</p>

<h2>First-time tips: useful questions to ask at check-in</h2>

<p>First-time families do not need to know everything. They need to know the next thing. If you want a better first week, ask a few concrete questions at check-in and let the staff or volunteers narrow the uncertainty.</p>

<ul>
  <li>Where should we go first tonight?</li>
  <li>Is there anything different about this Wednesday’s schedule?</li>
  <li>What should my child or student do after check-in?</li>
  <li>Who should I contact if our plans change during the program?</li>
  <li>How does pickup work at the end of the evening?</li>
  <li>Where should I wait, or should I return right at dismissal?</li>
  <li>Is there anything specific we should bring next week?</li>
  <li>Would it help to label a water bottle or personal item?</li>
</ul>

<p>That set of questions is specific enough to help and short enough to use in real life. Staff and volunteers expect first-time families. They can usually walk you through the steps more quickly than a parent can assemble a theory from partial information.</p>

<h2>A simple Wednesday Night preparation checklist</h2>

<ul>
  <li>Check <a href="/events-calendar/">the Events Calendar</a> for the specific Wednesday Night listing.</li>
  <li>Read <a href="/news.html">News</a> for reminders, special notes, or schedule changes.</li>
  <li>Review <a href="/kids.html">Kids</a> or <a href="/youth.html">Youth</a> if this is your first week.</li>
  <li>Pack a labeled water bottle, comfortable clothes, and a Bible or notebook if your child’s group uses it.</li>
  <li>Arrive a little early if you are not sure where to go.</li>
  <li>Keep parent contact and pickup details ready at check-in.</li>
  <li>Use <a href="/contacts.html">Contacts</a> for questions, changes, allergies, or accessibility needs.</li>
  <li>Return at the dismissal time listed for that Wednesday and follow the church’s pickup process.</li>
</ul>

<p>The best fit is usually the safest reasonable default: verify the current details, bring the basics, ask the first useful question, and let the evening become more familiar one step at a time.</p>

 succeeded in 780ms:
HTTP/2 301 
date: Sun, 07 Jun 2026 18:00:46 GMT
content-type: text/html; charset=iso-8859-1
location: http://ridgecrestchurch.com/contacts/
server: cloudflare
cf-cache-status: DYNAMIC
report-to: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=hT4Hr9i4vAKnJ%2Br%2BPAwxMYouqiEShJaah6ii16CEkJAj81eHX%2BUwOliTr5iSDasniWPRUVm%2FdJAFvhrtO4m49XiccoIo%2FRaQZYBpnGlZpIVJLenGrgQjhaS9B%2FwjNflODfIo3yYsZA%3D%3D"}]}
nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
cf-ray: a0818eec8f92798e-WAW
alt-svc: h3=":443"; ma=86400

HTTP/1.1 200 OK
Date: Sun, 07 Jun 2026 18:00:47 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
link: <https://ridgecrestchurch.com/wp-json/>; rel="https://api.w.org/", <https://ridgecrestchurch.com/wp-json/wp/v2/pages/20>; rel="alternate"; title="JSON"; type="application/json", <https://ridgecrestchurch.com/?p=20>; 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=sDg9dxBJ4tyNeKpN2zaL6wU1jwDzRloQkiu5xat8ySpgmF1E0LCXC40R51r4zeGUFvgyAVEeEJjv1%2B1gPfjqjfsdtQvWQG6SqWV4dsLVKvMlTX6fO7rl%2FOjSPXW0sJqv8gQWB5OeVA%3D%3D"}]}
Nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}

 succeeded in 907ms:
HTTP/2 301 
date: Sun, 07 Jun 2026 18:00:47 GMT
content-type: text/html; charset=UTF-8
location: https://ridgecrestchurch.com/resources/
server: cloudflare
x-redirect-by: WordPress
cf-cache-status: DYNAMIC
report-to: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=%2BbWS5eE74sCnDkHen8aRWdXN%2FnFY7jgR%2BtDfyvkdAJ7N1YWSrn9NpeCfXo2yUr5QUBLplzHx6T0pIRWHa9V9q%2Ft6bREp06grtNjOWS2SaSKZbDLPiWTQ6Whb96JBXfa38Mb29UH7Rw%3D%3D"}]}
nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
cf-ray: a0818eec9cc3eead-WAW
alt-svc: h3=":443"; ma=86400

HTTP/2 200 
date: Sun, 07 Jun 2026 18:00:47 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/pages/22>; rel="alternate"; title="JSON"; type="application/json", <https://ridgecrestchurch.com/?p=22>; 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=C42qj%2FjdPw3zDYndDS2C8nsBw6QV7aC87%2Bw%2F9UFNEeZJDpb8rs521QaUIWWVcQVLYR7RzRuPJWbiWtMpMAw2hJiWe8shdL6wiUhe4AWBX2FbtAH1YP3hIiYMgkrQYBH03xI9DepjNw%3D%3D"}]}
nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}

codex
I’m on the image step now. I’m checking for a real, permissively reusable prayer-related photo that fits the article better than the generic worship imagery already in the library, because the task requires a credible inline image rather than a filler visual.
exec
/bin/bash -lc "curl -s 'https://api.openverse.org/v1/images/?q=church%20prayer%20card&license_type=commercial,modification' | sed -n '1,220p'" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "curl -s 'https://api.openverse.org/v1/images/?q=prayer%20team%20church&license_type=commercial,modification' | sed -n '1,220p'" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "curl -s 'https://api.openverse.org/v1/images/?q=writing%20prayer%20request&license_type=commercial,modification' | sed -n '1,220p'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 721ms:
{"result_count":7,"page_count":1,"page_size":20,"page":1,"results":[{"id":"bc1a9163-8fcb-4c96-8f3c-7ef845afb3fa","title":"PAUL MULDOON SIGNING","indexed_on":"2020-04-10T22:21:25.729742Z","foreign_landing_url":"https://www.flickr.com/photos/8521690@N02/10572168084","url":"https://live.staticflickr.com/5550/10572168084_960d7692b6_b.jpg","creator":"summonedbyfells","creator_url":"https://www.flickr.com/photos/8521690@N02","license":"by","license_version":"2.0","license_url":"https://creativecommons.org/licenses/by/2.0/","provider":"flickr","source":"flickr","category":null,"filesize":null,"filetype":null,"tags":[{"name":"church","accuracy":null,"unstable__provider":"flickr"},{"name":"durham","accuracy":null,"unstable__provider":"flickr"},{"name":"paulmuldoon","accuracy":null,"unstable__provider":"flickr"},{"name":"adult","accuracy":0.99294,"unstable__provider":"clarifai"},{"name":"banking","accuracy":0.90145,"unstable__provider":"clarifai"},{"name":"book series","accuracy":0.92822,"unstable__provider":"clarifai"},{"name":"business","accuracy":0.96783,"unstable__provider":"clarifai"},{"name":"computer","accuracy":0.90625,"unstable__provider":"clarifai"},{"name":"indoors","accuracy":0.91989,"unstable__provider":"clarifai"},{"name":"man","accuracy":0.98182,"unstable__provider":"clarifai"},{"name":"one","accuracy":0.98876,"unstable__provider":"clarifai"},{"name":"people","accuracy":0.99369,"unstable__provider":"clarifai"},{"name":"portrait","accuracy":0.98151,"unstable__provider":"clarifai"},{"name":"room","accuracy":0.91502,"unstable__provider":"clarifai"},{"name":"technology","accuracy":0.90521,"unstable__provider":"clarifai"},{"name":"wear","accuracy":0.92722,"unstable__provider":"clarifai"}],"attribution":"\"PAUL MULDOON SIGNING\" by summonedbyfells is licensed under CC BY 2.0. To view a copy of this license, visit https://creativecommons.org/licenses/by/2.0/.","fields_matched":["description"],"mature":false,"height":1024,"width":767,"thumbnail":"https://api.openverse.org/v1/images/bc1a9163-8fcb-4c96-8f3c-7ef845afb3fa/thumb/","detail_url":"https://api.openverse.org/v1/images/bc1a9163-8fcb-4c96-8f3c-7ef845afb3fa/","related_url":"https://api.openverse.org/v1/images/bc1a9163-8fcb-4c96-8f3c-7ef845afb3fa/related/","unstable__sensitivity":[]},{"id":"bcd25a4b-ebcb-408c-b2c4-43af5d58bdb8","title":"Fotheringhay Church","indexed_on":"2020-04-29T06:08:34.063100Z","foreign_landing_url":"https://www.flickr.com/photos/27042541@N06/2964470055","url":"https://live.staticflickr.com/3165/2964470055_ca5d7dcc45_b.jpg","creator":"janebelindasmith","creator_url":"https://www.flickr.com/photos/27042541@N06","license":"by","license_version":"2.0","license_url":"https://creativecommons.org/licenses/by/2.0/","provider":"flickr","source":"flickr","category":null,"filesize":null,"filetype":null,"tags":[{"name":"fotheringhaychurch","accuracy":null,"unstable__provider":"flickr"},{"name":"maryqueenofscots","accuracy":null,"unstable__provider":"flickr"}],"attribution":"\"Fotheringhay Church\" by janebelindasmith is licensed under CC BY 2.0. To view a copy of this license, visit https://creativecommons.org/licenses/by/2.0/.","fields_matched":["description"],"mature":false,"height":775,"width":1024,"thumbnail":"https://api.openverse.org/v1/images/bcd25a4b-ebcb-408c-b2c4-43af5d58bdb8/thumb/","detail_url":"https://api.openverse.org/v1/images/bcd25a4b-ebcb-408c-b2c4-43af5d58bdb8/","related_url":"https://api.openverse.org/v1/images/bcd25a4b-ebcb-408c-b2c4-43af5d58bdb8/related/","unstable__sensitivity":[]},{"id":"bca142fa-75db-481a-85f6-609581cbe428","title":"Joss House of Prayer in San Francisco (CHS-364)","indexed_on":"2020-03-28T02:23:36.937083Z","foreign_landing_url":"https://www.flickr.com/photos/50398299@N08/16607469786","url":"https://live.staticflickr.com/8672/16607469786_44915c8d7e_b.jpg","creator":"Fæ","creator_url":"https://www.flickr.com/photos/50398299@N08","license":"by","license_version":"2.0","license_url":"https://creativecommons.org/licenses/by/2.0/","provider":"flickr","source":"flickr","category":null,"filesize":null,"filetype":null,"tags":[{"name":"californiahistoricalsocietycollection18601960","accuracy":null,"unstable__provider":"flickr"},{"name":"glassplatenegatives","accuracy":null,"unstable__provider":"flickr"},{"name":"wikimediacommons","accuracy":null,"unstable__provider":"flickr"},{"name":"chair","accuracy":0.90924,"unstable__provider":"clarifai"},{"name":"furniture","accuracy":0.98054,"unstable__provider":"clarifai"},{"name":"group","accuracy":0.92159,"unstable__provider":"clarifai"},{"name":"indoors","accuracy":0.9144,"unstable__provider":"clarifai"},{"name":"old","accuracy":0.90762,"unstable__provider":"clarifai"},{"name":"people","accuracy":0.97397,"unstable__provider":"clarifai"},{"name":"room","accuracy":0.96262,"unstable__provider":"clarifai"},{"name":"seat","accuracy":0.92519,"unstable__provider":"clarifai"},{"name":"table","accuracy":0.92558,"unstable__provider":"clarifai"}],"attribution":"\"Joss House of Prayer in San Francisco (CHS-364)\" by Fæ is licensed under CC BY 2.0. To view a copy of this license, visit https://creativecommons.org/licenses/by/2.0/.","fields_matched":["description","title"],"mature":false,"height":782,"width":1024,"thumbnail":"https://api.openverse.org/v1/images/bca142fa-75db-481a-85f6-609581cbe428/thumb/","detail_url":"https://api.openverse.org/v1/images/bca142fa-75db-481a-85f6-609581cbe428/","related_url":"https://api.openverse.org/v1/images/bca142fa-75db-481a-85f6-609581cbe428/related/","unstable__sensitivity":[]},{"id":"95338429-b489-4752-be15-4b7a4e968e8f","title":"2005_0305tokyo05c050004","indexed_on":"2020-04-24T00:26:31.979214Z","foreign_landing_url":"https://www.flickr.com/photos/12357841@N02/3289003742","url":"https://live.staticflickr.com/3370/3289003742_5fc914fc39_b.jpg","creator":"Me in ME","creator_url":"https://www.flickr.com/photos/12357841@N02","license":"by","license_version":"2.0","license_url":"https://creativecommons.org/licenses/by/2.0/","provider":"flickr","source":"flickr","category":null,"filesize":null,"filetype":null,"tags":[],"attribution":"\"2005_0305tokyo05c050004\" by Me in ME is licensed under CC BY 2.0. To view a copy of this license, visit https://creativecommons.org/licenses/by/2.0/.","fields_matched":["description"],"mature":false,"height":771,"width":1024,"thumbnail":"https://api.openverse.org/v1/images/95338429-b489-4752-be15-4b7a4e968e8f/thumb/","detail_url":"https://api.openverse.org/v1/images/95338429-b489-4752-be15-4b7a4e968e8f/","related_url":"https://api.openverse.org/v1/images/95338429-b489-4752-be15-4b7a4e968e8f/related/","unstable__sensitivity":[]},{"id":"3c42a24c-9d79-4ef6-a8b8-64a8e09c8ff6","title":"Professor Yitzhak Melamed non-grata letter by Rabbi Joseph Benjamin Serfaty","indexed_on":"2023-12-03T14:20:32.705460Z","foreign_landing_url":"https://commons.wikimedia.org/w/index.php?curid=112938020","url":"https://upload.wikimedia.org/wikipedia/commons/1/1b/Professor_Yitzhak_Melamed_non-grata_letter_by_Rabbi_Joseph_Benjamin_Serfaty.jpg","creator":"Rabbi Joseph Benjamin Serfaty","creator_url":null,"license":"by-sa","license_version":"4.0","license_url":"https://creativecommons.org/licenses/by-sa/4.0/","provider":"wikimedia","source":"wikimedia","category":null,"filesize":22428,"filetype":"jpg","tags":[],"attribution":"\"Professor Yitzhak Melamed non-grata letter by Rabbi Joseph Benjamin Serfaty\" by Rabbi Joseph Benjamin Serfaty is licensed under CC BY-SA 4.0. To view a copy of this license, visit https://creativecommons.org/licenses/by-sa/4.0/.","fields_matched":["description"],"mature":false,"height":523,"width":370,"thumbnail":"https://api.openverse.org/v1/images/3c42a24c-9d79-4ef6-a8b8-64a8e09c8ff6/thumb/","detail_url":"https://api.openverse.org/v1/images/3c42a24c-9d79-4ef6-a8b8-64a8e09c8ff6/","related_url":"https://api.openverse.org/v1/images/3c42a24c-9d79-4ef6-a8b8-64a8e09c8ff6/related/","unstable__sensitivity":[]},{"id":"b1e44ab5-3a61-4d3d-b6f8-2375dfa9083a","title":"Outside Chapel Siggiewi","indexed_on":"2024-05-26T14:16:57.731164Z","foreign_landing_url":"https://commons.wikimedia.org/w/index.php?curid=115494633","url":"https://upload.wikimedia.org/wikipedia/commons/5/57/Outside_Chapel_Siggiewi.jpg","creator":"Lance Anthony","creator_url":"https://commons.wikimedia.org/wiki/User:Lance_Anthony","license":"by-sa","license_version":"4.0","license_url":"https://creativecommons.org/licenses/by-sa/4.0/","provider":"wikimedia","source":"wikimedia","category":null,"filesize":5195958,"filetype":"jpg","tags":[],"attribution":"\"Outside Chapel Siggiewi\" by Lance Anthony is licensed under CC BY-SA 4.0. To view a copy of this license, visit https://creativecommons.org/licenses/by-sa/4.0/.","fields_matched":["description"],"mature":false,"height":1230,"width":3152,"thumbnail":"https://api.openverse.org/v1/images/b1e44ab5-3a61-4d3d-b6f8-2375dfa9083a/thumb/","detail_url":"https://api.openverse.org/v1/images/b1e44ab5-3a61-4d3d-b6f8-2375dfa9083a/","related_url":"https://api.openverse.org/v1/images/b1e44ab5-3a61-4d3d-b6f8-2375dfa9083a/related/","unstable__sensitivity":[]},{"id":"b1ea0bdc-1ddb-46d1-883a-b2b3b98d89b0","title":"File:Shinto shrine votive tablets in rural Fukui prefecture.jpg","indexed_on":"2020-03-04T02:28:29.582532Z","foreign_landing_url":"https://commons.wikimedia.org/w/index.php?curid=74692205","url":"https://upload.wikimedia.org/wikipedia/commons/9/9b/Shinto_shrine_votive_tablets_in_rural_Fukui_prefecture.jpg","creator":"Gpwitteveen","creator_url":"https://commons.wikimedia.org/w/index.php?title=User:Gpwitteveen&action=edit&redlink=1","license":"by-sa","license_version":"4.0","license_url":"https://creativecommons.org/licenses/by-sa/4.0/","provider":"wikimedia","source":"wikimedia","category":null,"filesize":null,"filetype":null,"tags":[],"attribution":"\"File:Shinto shrine votive tablets in rural Fukui prefecture.jpg\" by Gpwitteveen is licensed under CC BY-SA 4.0. To view a copy of this license, visit https://creativecommons.org/licenses/by-sa/4.0/.","fields_matched":["description"],"mature":false,"height":2382,"width":3247,"thumbnail":"https://api.openverse.org/v1/images/b1ea0bdc-1ddb-46d1-883a-b2b3b98d89b0/thumb/","detail_url":"https://api.openverse.org/v1/images/b1ea0bdc-1ddb-46d1-883a-b2b3b98d89b0/","related_url":"https://api.openverse.org/v1/images/b1ea0bdc-1ddb-46d1-883a-b2b3b98d89b0/related/","unstable__sensitivity":[]}]}
 succeeded in 1018ms:
{"result_count":84,"page_count":5,"page_size":20,"page":1,"results":[{"id":"9e1694c0-423c-406b-9f2f-d6691429067d","title":"Interior - Alexander Nevsky Cathedral","indexed_on":"2020-04-03T05:36:28.180863Z","foreign_landing_url":"https://www.flickr.com/photos/8721758@N06/13339306414","url":"https://live.staticflickr.com/2867/13339306414_de0a754648_b.jpg","creator":"Jorge Lascar","creator_url":"https://www.flickr.com/photos/8721758@N06","license":"by","license_version":"2.0","license_url":"https://creativecommons.org/licenses/by/2.0/","provider":"flickr","source":"flickr","category":null,"filesize":null,"filetype":null,"tags":[],"attribution":"\"Interior - Alexander Nevsky Cathedral\" by Jorge Lascar is licensed under CC BY 2.0. To view a copy of this license, visit https://creativecommons.org/licenses/by/2.0/.","fields_matched":["description"],"mature":false,"height":680,"width":1024,"thumbnail":"https://api.openverse.org/v1/images/9e1694c0-423c-406b-9f2f-d6691429067d/thumb/","detail_url":"https://api.openverse.org/v1/images/9e1694c0-423c-406b-9f2f-d6691429067d/","related_url":"https://api.openverse.org/v1/images/9e1694c0-423c-406b-9f2f-d6691429067d/related/","unstable__sensitivity":[]},{"id":"ec9f84c5-ac1a-4070-9249-3f6c0aa18fbd","title":"The gold-domed Alexander Nevsky Cathedral - Built in honour to the Russian soldiers who liberated Bulgaria from Ottoman (Turk) rule","indexed_on":"2020-04-03T05:36:28.180863Z","foreign_landing_url":"https://www.flickr.com/photos/8721758@N06/13339065563","url":"https://live.staticflickr.com/7036/13339065563_0b51e6fe65_b.jpg","creator":"Jorge Lascar","creator_url":"https://www.flickr.com/photos/8721758@N06","license":"by","license_version":"2.0","license_url":"https://creativecommons.org/licenses/by/2.0/","provider":"flickr","source":"flickr","category":null,"filesize":null,"filetype":null,"tags":[{"name":"cloudy","accuracy":null,"unstable__provider":"flickr"},{"name":"day","accuracy":null,"unstable__provider":"flickr"}],"attribution":"\"The gold-domed Alexander Nevsky Cathedral - Built in honour to the Russian soldiers who liberated Bulgaria from Ottoman (Turk) rule\" by Jorge Lascar is licensed under CC BY 2.0. To view a copy of this license, visit https://creativecommons.org/licenses/by/2.0/.","fields_matched":["description"],"mature":false,"height":680,"width":1024,"thumbnail":"https://api.openverse.org/v1/images/ec9f84c5-ac1a-4070-9249-3f6c0aa18fbd/thumb/","detail_url":"https://api.openverse.org/v1/images/ec9f84c5-ac1a-4070-9249-3f6c0aa18fbd/","related_url":"https://api.openverse.org/v1/images/ec9f84c5-ac1a-4070-9249-3f6c0aa18fbd/related/","unstable__sensitivity":[]},{"id":"64ad5d8e-26bc-4ad6-9514-7f5079123239","title":"Alexander Nevsky Cathedral","indexed_on":"2020-04-03T05:36:28.180863Z","foreign_landing_url":"https://www.flickr.com/photos/8721758@N06/13338294805","url":"https://live.staticflickr.com/3714/13338294805_333899a98a_b.jpg","creator":"Jorge Lascar","creator_url":"https://www.flickr.com/photos/8721758@N06","license":"by","license_version":"2.0","license_url":"https://creativecommons.org/licenses/by/2.0/","provider":"flickr","source":"flickr","category":null,"filesize":null,"filetype":null,"tags":[],"attribution":"\"Alexander Nevsky Cathedral\" by Jorge Lascar is licensed under CC BY 2.0. To view a copy of this license, visit https://creativecommons.org/licenses/by/2.0/.","fields_matched":["description"],"mature":false,"height":629,"width":1024,"thumbnail":"https://api.openverse.org/v1/images/64ad5d8e-26bc-4ad6-9514-7f5079123239/thumb/","detail_url":"https://api.openverse.org/v1/images/64ad5d8e-26bc-4ad6-9514-7f5079123239/","related_url":"https://api.openverse.org/v1/images/64ad5d8e-26bc-4ad6-9514-7f5079123239/related/","unstable__sensitivity":[]},{"id":"01a85ada-1f5c-4e6e-8da3-3af1ad07d96b","title":"The gold-domed Alexander Nevsky Cathedral - Built in honour to the Russian soldiers who liberated Bulgaria from Ottoman (Turk) rule","indexed_on":"2020-04-03T05:36:28.180863Z","foreign_landing_url":"https://www.flickr.com/photos/8721758@N06/13339296444","url":"https://live.staticflickr.com/7258/13339296444_8b6fe208e2_b.jpg","creator":"Jorge Lascar","creator_url":"https://www.flickr.com/photos/8721758@N06","license":"by","license_version":"2.0","license_url":"https://creativecommons.org/licenses/by/2.0/","provider":"flickr","source":"flickr","category":null,"filesize":null,"filetype":null,"tags":[],"attribution":"\"The gold-domed Alexander Nevsky Cathedral - Built in honour to the Russian soldiers who liberated Bulgaria from Ottoman (Turk) rule\" by Jorge Lascar is licensed under CC BY 2.0. To view a copy of this license, visit https://creativecommons.org/licenses/by/2.0/.","fields_matched":["description"],"mature":false,"height":675,"width":1024,"thumbnail":"https://api.openverse.org/v1/images/01a85ada-1f5c-4e6e-8da3-3af1ad07d96b/thumb/","detail_url":"https://api.openverse.org/v1/images/01a85ada-1f5c-4e6e-8da3-3af1ad07d96b/","related_url":"https://api.openverse.org/v1/images/01a85ada-1f5c-4e6e-8da3-3af1ad07d96b/related/","unstable__sensitivity":[]},{"id":"874bb04e-ebfd-42b8-b51b-e957e9563775","title":"The gold-domed Alexander Nevsky Cathedral","indexed_on":"2020-04-03T05:36:28.180863Z","foreign_landing_url":"https://www.flickr.com/photos/8721758@N06/13339019334","url":"https://live.staticflickr.com/7055/13339019334_a6c6231e1a_b.jpg","creator":"Jorge Lascar","creator_url":"https://www.flickr.com/photos/8721758@N06","license":"by","license_version":"2.0","license_url":"https://creativecommons.org/licenses/by/2.0/","provider":"flickr","source":"flickr","category":null,"filesize":null,"filetype":null,"tags":[],"attribution":"\"The gold-domed Alexander Nevsky Cathedral\" by Jorge Lascar is licensed under CC BY 2.0. To view a copy of this license, visit https://creativecommons.org/licenses/by/2.0/.","fields_matched":["description"],"mature":false,"height":680,"width":1024,"thumbnail":"https://api.openverse.org/v1/images/874bb04e-ebfd-42b8-b51b-e957e9563775/thumb/","detail_url":"https://api.openverse.org/v1/images/874bb04e-ebfd-42b8-b51b-e957e9563775/","related_url":"https://api.openverse.org/v1/images/874bb04e-ebfd-42b8-b51b-e957e9563775/related/","unstable__sensitivity":[]},{"id":"56dbe37b-5749-4e70-aaf6-775b2852546b","title":"Detail of the façade - Alexander Nevsky Cathedral","indexed_on":"2020-04-03T05:36:28.180863Z","foreign_landing_url":"https://www.flickr.com/photos/8721758@N06/13338657774","url":"https://live.staticflickr.com/3746/13338657774_b7d843aa1b_b.jpg","creator":"Jorge Lascar","creator_url":"https://www.flickr.com/photos/8721758@N06","license":"by","license_version":"2.0","license_url":"https://creativecommons.org/licenses/by/2.0/","provider":"flickr","source":"flickr","category":null,"filesize":null,"filetype":null,"tags":[],"attribution":"\"Detail of the façade - Alexander Nevsky Cathedral\" by Jorge Lascar is licensed under CC BY 2.0. To view a copy of this license, visit https://creativecommons.org/licenses/by/2.0/.","fields_matched":["description"],"mature":false,"height":680,"width":1024,"thumbnail":"https://api.openverse.org/v1/images/56dbe37b-5749-4e70-aaf6-775b2852546b/thumb/","detail_url":"https://api.openverse.org/v1/images/56dbe37b-5749-4e70-aaf6-775b2852546b/","related_url":"https://api.openverse.org/v1/images/56dbe37b-5749-4e70-aaf6-775b2852546b/related/","unstable__sensitivity":[]},{"id":"a47cf820-7d88-4ba8-8f53-dcbba3abdee9","title":"Domes and ceiling frescoes - Alexander Nevsky Cathedral","indexed_on":"2020-04-03T05:36:28.180863Z","foreign_landing_url":"https://www.flickr.com/photos/8721758@N06/13338902155","url":"https://live.staticflickr.com/7380/13338902155_5aeeb11be2_b.jpg","creator":"Jorge Lascar","creator_url":"https://www.flickr.com/photos/8721758@N06","license":"by","license_version":"2.0","license_url":"https://creativecommons.org/licenses/by/2.0/","provider":"flickr","source":"flickr","category":null,"filesize":null,"filetype":null,"tags":[],"attribution":"\"Domes and ceiling frescoes - Alexander Nevsky Cathedral\" by Jorge Lascar is licensed under CC BY 2.0. To view a copy of this license, visit https://creativecommons.org/licenses/by/2.0/.","fields_matched":["description"],"mature":false,"height":680,"width":1024,"thumbnail":"https://api.openverse.org/v1/images/a47cf820-7d88-4ba8-8f53-dcbba3abdee9/thumb/","detail_url":"https://api.openverse.org/v1/images/a47cf820-7d88-4ba8-8f53-dcbba3abdee9/","related_url":"https://api.openverse.org/v1/images/a47cf820-7d88-4ba8-8f53-dcbba3abdee9/related/","unstable__sensitivity":[]},{"id":"24f50361-c177-48b7-a79e-156bdb623690","title":"Alexander Nevsky Cathedral","indexed_on":"2020-04-03T05:36:28.180863Z","foreign_landing_url":"https://www.flickr.com/photos/8721758@N06/13338249245","url":"https://live.staticflickr.com/7102/13338249245_3a5084efca_b.jpg","creator":"Jorge Lascar","creator_url":"https://www.flickr.com/photos/8721758@N06","license":"by","license_version":"2.0","license_url":"https://creativecommons.org/licenses/by/2.0/","provider":"flickr","source":"flickr","category":null,"filesize":null,"filetype":null,"tags":[{"name":"ancient","accuracy":0.93749,"unstable__provider":"clarifai"},{"name":"architecture","accuracy":0.9979,"unstable__provider":"clarifai"},{"name":"building","accuracy":0.98448,"unstable__provider":"clarifai"},{"name":"cathedral","accuracy":0.93736,"unstable__provider":"clarifai"},{"name":"church","accuracy":0.97346,"unstable__provider":"clarifai"},{"name":"city","accuracy":0.9692,"unstable__provider":"clarifai"},{"name":"exterior","accuracy":0.93307,"unstable__provider":"clarifai"},{"name":"facade","accuracy":0.93294,"unstable__provider":"clarifai"},{"name":"monument","accuracy":0.91378,"unstable__provider":"clarifai"},{"name":"old","accuracy":0.9663,"unstable__provider":"clarifai"},{"name":"outdoors","accuracy":0.93868,"unstable__provider":"clarifai"},{"name":"religion","accuracy":0.9721,"unstable__provider":"clarifai"},{"name":"sky","accuracy":0.94375,"unstable__provider":"clarifai"},{"name":"stone","accuracy":0.91575,"unstable__provider":"clarifai"},{"name":"tourism","accuracy":0.96323,"unstable__provider":"clarifai"},{"name":"tourist","accuracy":0.90608,"unstable__provider":"clarifai"},{"name":"town","accuracy":0.91558,"unstable__provider":"clarifai"},{"name":"traditional","accuracy":0.91436,"unstable__provider":"clarifai"},{"name":"travel","accuracy":0.98388,"unstable__provider":"clarifai"}],"attribution":"\"Alexander Nevsky Cathedral\" by Jorge Lascar is licensed under CC BY 2.0. To view a copy of this license, visit https://creativecommons.org/licenses/by/2.0/.","fields_matched":["description","tags.name"],"mature":false,"height":680,"width":1024,"thumbnail":"https://api.openverse.org/v1/images/24f50361-c177-48b7-a79e-156bdb623690/thumb/","detail_url":"https://api.openverse.org/v1/images/24f50361-c177-48b7-a79e-156bdb623690/","related_url":"https://api.openverse.org/v1/images/24f50361-c177-48b7-a79e-156bdb623690/related/","unstable__sensitivity":[]},{"id":"293afcb3-2aeb-404c-b0dc-401cdd6a536e","title":"Mosaic decorating door - Alexander Nevsky Cathedral","indexed_on":"2020-04-03T05:36:28.180863Z","foreign_landing_url":"https://www.flickr.com/photos/8721758@N06/13338881674","url":"https://live.staticflickr.com/3709/13338881674_f8ae4e9aaa_b.jpg","creator":"Jorge Lascar","creator_url":"https://www.flickr.com/photos/8721758@N06","license":"by","license_version":"2.0","license_url":"https://creativecommons.org/licenses/by/2.0/","provider":"flickr","source":"flickr","category":null,"filesize":null,"filetype":null,"tags":[],"attribution":"\"Mosaic decorating door - Alexander Nevsky Cathedral\" by Jorge Lascar is licensed under CC BY 2.0. To view a copy of this license, visit https://creativecommons.org/licenses/by/2.0/.","fields_matched":["description"],"mature":false,"height":680,"width":1024,"thumbnail":"https://api.openverse.org/v1/images/293afcb3-2aeb-404c-b0dc-401cdd6a536e/thumb/","detail_url":"https://api.openverse.org/v1/images/293afcb3-2aeb-404c-b0dc-401cdd6a536e/","related_url":"https://api.openverse.org/v1/images/293afcb3-2aeb-404c-b0dc-401cdd6a536e/related/","unstable__sensitivity":[]},{"id":"5fe5ac83-103c-47c7-9778-38102c087b35","title":"Three of the five gold domes and its 53m bell tower - Alexander Nevsky Cathedral","indexed_on":"2020-04-03T05:36:28.180863Z","foreign_landing_url":"https://www.flickr.com/photos/8721758@N06/13338821494","url":"https://live.staticflickr.com/7130/13338821494_31b5768eea_b.jpg","creator":"Jorge Lascar","creator_url":"https://www.flickr.com/photos/8721758@N06","license":"by","license_version":"2.0","license_url":"https://creativecommons.org/licenses/by/2.0/","provider":"flickr","source":"flickr","category":null,"filesize":null,"filetype":null,"tags":[],"attribution":"\"Three of the five gold domes and its 53m bell tower - Alexander Nevsky Cathedral\" by Jorge Lascar is licensed under CC BY 2.0. To view a copy of this license, visit https://creativecommons.org/licenses/by/2.0/.","fields_matched":["description"],"mature":false,"height":680,"width":1024,"thumbnail":"https://api.openverse.org/v1/images/5fe5ac83-103c-47c7-9778-38102c087b35/thumb/","detail_url":"https://api.openverse.org/v1/images/5fe5ac83-103c-47c7-9778-38102c087b35/","related_url":"https://api.openverse.org/v1/images/5fe5ac83-103c-47c7-9778-38102c087b35/related/","unstable__sensitivity":[]},{"id":"35b32be7-dace-467c-98c7-08a2189adfed","title":"One of the five gold domes - Alexander Nevsky Cathedral","indexed_on":"2020-04-03T05:36:28.180863Z","foreign_landing_url":"https://www.flickr.com/photos/8721758@N06/13338434103","url":"https://live.staticflickr.com/3772/13338434103_26a02f5072_b.jpg","creator":"Jorge Lascar","creator_url":"https://www.flickr.com/photos/8721758@N06","license":"by","license_version":"2.0","license_url":"https://creativecommons.org/licenses/by/2.0/","provider":"flickr","source":"flickr","category":null,"filesize":null,"filetype":null,"tags":[{"name":"ancient","accuracy":0.90599,"unstable__provider":"clarifai"},{"name":"architecture","accuracy":0.99719,"unstable__provider":"clarifai"},{"name":"building","accuracy":0.9773,"unstable__provider":"clarifai"},{"name":"cathedral","accuracy":0.95063,"unstable__provider":"clarifai"},{"name":"church","accuracy":0.98131,"unstable__provider":"clarifai"},{"name":"city","accuracy":0.94731,"unstable__provider":"clarifai"},{"name":"daylight","accuracy":0.91843,"unstable__provider":"clarifai"},{"name":"dome","accuracy":0.95195,"unstable__provider":"clarifai"},{"name":"monument","accuracy":0.9158,"unstable__provider":"clarifai"},{"name":"old","accuracy":0.93966,"unstable__provider":"clarifai"},{"name":"outdoors","accuracy":0.93431,"unstable__provider":"clarifai"},{"name":"religion","accuracy":0.9912,"unstable__provider":"clarifai"},{"name":"religious","accuracy":0.90249,"unstable__provider":"clarifai"},{"name":"sky","accuracy":0.92976,"unstable__provider":"clarifai"},{"name":"tourism","accuracy":0.92378,"unstable__provider":"clarifai"},{"name":"travel","accuracy":0.9794,"unstable__provider":"clarifai"}],"attribution":"\"One of the five gold domes - Alexander Nevsky Cathedral\" by Jorge Lascar is licensed under CC BY 2.0. To view a copy of this license, visit https://creativecommons.org/licenses/by/2.0/.","fields_matched":["description","tags.name"],"mature":false,"height":680,"width":1024,"thumbnail":"https://api.openverse.org/v1/images/35b32be7-dace-467c-98c7-08a2189adfed/thumb/","detail_url":"https://api.openverse.org/v1/images/35b32be7-dace-467c-98c7-08a2189adfed/","related_url":"https://api.openverse.org/v1/images/35b32be7-dace-467c-98c7-08a2189adfed/related/","unstable__sensitivity":[]},{"id":"b7789f6b-af82-4ff8-9d96-16a953ad0e94","title":"Ceiling frescoes - Alexander Nevsky Cathedral","indexed_on":"2020-04-03T05:36:28.180863Z","foreign_landing_url":"https://www.flickr.com/photos/8721758@N06/13338822773","url":"https://live.staticflickr.com/3806/13338822773_d8b7bf25ec_b.jpg","creator":"Jorge Lascar","creator_url":"https://www.flickr.com/photos/8721758@N06","license":"by","license_version":"2.0","license_url":"https://creativecommons.org/licenses/by/2.0/","provider":"flickr","source":"flickr","category":null,"filesize":null,"filetype":null,"tags":[{"name":"ancient","accuracy":0.94285,"unstable__provider":"clarifai"},{"name":"arch","accuracy":0.94605,"unstable__provider":"clarifai"},{"name":"architecture","accuracy":0.95497,"unstable__provider":"clarifai"},{"name":"art","accuracy":0.96467,"unstable__provider":"clarifai"},{"name":"cathedral","accuracy":0.97492,"unstable__provider":"clarifai"},{"name":"ceiling","accuracy":0.97819,"unstable__provider":"clarifai"},{"name":"church","accuracy":0.99565,"unstable__provider":"clarifai"},{"name":"clock","accuracy":0.92259,"unstable__provider":"clarifai"},{"name":"dome","accuracy":0.97089,"unstable__provider":"clarifai"},{"name":"gold","accuracy":0.97596,"unstable__provider":"clarifai"},{"name":"inner surface","accuracy":0.93015,"unstable__provider":"clarifai"},{"name":"inside","accuracy":0.96019,"unstable__provider":"clarifai"},{"name":"interior","accuracy":0.9565,"unstable__provider":"clarifai"},{"name":"old","accuracy":0.96874,"unstable__provider":"clarifai"},{"name":"religion","accuracy":0.99488,"unstable__provider":"clarifai"},{"name":"religious","accuracy":0.94387,"unstable__provider":"clarifai"},{"name":"saint","accuracy":0.94927,"unstable__provider":"clarifai"},{"name":"spirituality","accuracy":0.92846,"unstable__provider":"clarifai"},{"name":"symbol","accuracy":0.93559,"unstable__provider":"clarifai"},{"name":"travel","accuracy":0.92429,"unstable__provider":"clarifai"}],"attribution":"\"Ceiling frescoes - Alexander Nevsky Cathedral\" by Jorge Lascar is licensed under CC BY 2.0. To view a copy of this license, visit https://creativecommons.org/licenses/by/2.0/.","fields_matched":["description","tags.name"],"mature":false,"height":680,"width":1024,"thumbnail":"https://api.openverse.org/v1/images/b7789f6b-af82-4ff8-9d96-16a953ad0e94/thumb/","detail_url":"https://api.openverse.org/v1/images/b7789f6b-af82-4ff8-9d96-16a953ad0e94/","related_url":"https://api.openverse.org/v1/images/b7789f6b-af82-4ff8-9d96-16a953ad0e94/related/","unstable__sensitivity":[]},{"id":"05e3bbce-4346-4962-b91a-4845a6d732a7","title":"La Madone de São Paulo painting by Alexis Diaz and INTI in São Paulo downtown","indexed_on":"2020-03-05T03:41:52.809710Z","foreign_landing_url":"https://commons.wikimedia.org/w/index.php?curid=55545297","url":"https://upload.wikimedia.org/wikipedia/commons/3/3b/La_Madone_de_S%C3%A3o_Paulo_painting_by_Alexis_Diaz_and_INTI_in_S%C3%A3o_Paulo_downtown.jpg","creator":"Wilfredor","creator_url":"https://commons.wikimedia.org/wiki/User:Wilfredor","license":"by-sa","license_version":"4.0","license_url":"https://creativecommons.org/licenses/by-sa/4.0/","provider":"wikimedia","source":"wikimedia","category":null,"filesize":5032625,"filetype":"jpg","tags":[],"attribution":"\"La Madone de São Paulo painting by Alexis Diaz and INTI in São Paulo downtown\" by Wilfredor is licensed under CC BY-SA 4.0. To view a copy of this license, visit https://creativecommons.org/licenses/by-sa/4.0/.","fields_matched":["description"],"mature":false,"height":2237,"width":2760,"thumbnail":"https://api.openverse.org/v1/images/05e3bbce-4346-4962-b91a-4845a6d732a7/thumb/","detail_url":"https://api.openverse.org/v1/images/05e3bbce-4346-4962-b91a-4845a6d732a7/","related_url":"https://api.openverse.org/v1/images/05e3bbce-4346-4962-b91a-4845a6d732a7/related/","unstable__sensitivity":[]},{"id":"b86a8bbf-32db-4372-ae88-886ac307a3c1","title":"Calm Mind Mindfullness - Credit to https://homethods.com/","indexed_on":"2020-03-26T11:47:30.465729Z","foreign_landing_url":"https://www.flickr.com/photos/146625745@N08/30832433680","url":"https://live.staticflickr.com/5781/30832433680_e105926c9a_b.jpg","creator":"homethods","creator_url":"https://www.flickr.com/photos/146625745@N08","license":"by","license_version":"2.0","license_url":"https://creativecommons.org/licenses/by/2.0/","provider":"flickr","source":"flickr","category":null,"filesize":null,"filetype":null,"tags":[{"name":"belief","accuracy":null,"unstable__provider":"flickr"},{"name":"believe","accuracy":null,"unstable__provider":"flickr"},{"name":"bible","accuracy":null,"unstable__provider":"flickr"},{"name":"board","accuracy":null,"unstable__provider":"flickr"},{"name":"buddha","accuracy":null,"unstable__provider":"flickr"},{"name":"career","accuracy":null,"unstable__provider":"flickr"},{"name":"christian","accuracy":null,"unstable__provider":"flickr"},{"name":"christianity","accuracy":null,"unstable__provider":"flickr"},{"name":"church","accuracy":null,"unstable__provider":"flickr"},{"name":"comfort","accuracy":null,"unstable__provider":"flickr"},{"name":"employee","accuracy":null,"unstable__provider":"flickr"},{"name":"employer","accuracy":null,"unstable__provider":"flickr"},{"name":"faith","accuracy":null,"unstable__provider":"flickr"},{"name":"friend","accuracy":null,"unstable__provider":"flickr"},{"name":"leader","accuracy":null,"unstable__provider":"flickr"},{"name":"leadership","accuracy":null,"unstable__provider":"flickr"},{"name":"love","accuracy":null,"unstable__provider":"flickr"},{"name":"manager","accuracy":null,"unstable__provider":"flickr"},{"name":"meditate","accuracy":null,"unstable__provider":"flickr"},{"name":"meditation","accuracy":null,"unstable__provider":"flickr"},{"name":"members","accuracy":null,"unstable__provider":"flickr"},{"name":"mindfullness","accuracy":null,"unstable__provider":"flickr"},{"name":"monk","accuracy":null,"unstable__provider":"flickr"},{"name":"peace","accuracy":null,"unstable__provider":"flickr"},{"name":"pray","accuracy":null,"unstable__provider":"flickr"},{"name":"prayer","accuracy":null,"unstable__provider":"flickr"},{"name":"praying","accuracy":null,"unstable__provider":"flickr"},{"name":"startup","accuracy":null,"unstable__provider":"flickr"},{"name":"team","accuracy":null,"unstable__provider":"flickr"},{"name":"zones","accuracy":null,"unstable__provider":"flickr"}],"attribution":"\"Calm Mind Mindfullness - Credit to https://homethods.com/\" by homethods is licensed under CC BY 2.0. To view a copy of this license, visit https://creativecommons.org/licenses/by/2.0/.","fields_matched":["tags.name"],"mature":false,"height":683,"width":1024,"thumbnail":"https://api.openverse.org/v1/images/b86a8bbf-32db-4372-ae88-886ac307a3c1/thumb/","detail_url":"https://api.openverse.org/v1/images/b86a8bbf-32db-4372-ae88-886ac307a3c1/","related_url":"https://api.openverse.org/v1/images/b86a8bbf-32db-4372-ae88-886ac307a3c1/related/","unstable__sensitivity":[]},{"id":"804940f9-639d-41da-b09f-45bbeef16828","title":"Pedro Calungsod close-up (cropped)","indexed_on":"2025-05-12T00:07:33.171355Z","foreign_landing_url":"https://commons.wikimedia.org/w/index.php?curid=165039875","url":"https://upload.wikimedia.org/wikipedia/commons/a/ae/Pedro_Calungsod_close-up_%28cropped%29.JPG","creator":"Ramon FVelasquez","creator_url":"https://commons.wikimedia.org/wiki/User:Ramon_FVelasquez","license":"by-sa","license_version":"3.0","license_url":"https://creativecommons.org/licenses/by-sa/3.0/","provider":"wikimedia","source":"wikimedia","category":null,"filesize":251560,"filetype":"jpg","tags":[],"attribution":"\"Pedro Calungsod close-up (cropped)\" by Ramon FVelasquez is licensed under CC BY-SA 3.0. To view a copy of this license, visit https://creativecommons.org/licenses/by-sa/3.0/.","fields_matched":["description"],"mature":false,"height":685,"width":467,"thumbnail":"https://api.openverse.org/v1/images/804940f9-639d-41da-b09f-45bbeef16828/thumb/","detail_url":"https://api.openverse.org/v1/images/804940f9-639d-41da-b09f-45bbeef16828/","related_url":"https://api.openverse.org/v1/images/804940f9-639d-41da-b09f-45bbeef16828/related/","unstable__sensitivity":[]},{"id":"3b5e7737-d1cd-4b32-959f-f71309f97bd2","title":"Alexander Nevsky Cathedral (13338249245)","indexed_on":"2020-05-01T04:37:22.938601Z","foreign_landing_url":"https://commons.wikimedia.org/w/index.php?curid=31947453","url":"https://upload.wikimedia.org/wikipedia/commons/a/ae/Alexander_Nevsky_Cathedral_%2813338249245%29.jpg","creator":"Jorge Láscar from Australia","creator_url":"https://www.flickr.com/people/8721758@N06","license":"by","license_version":"2.0","license_url":"https://creativecommons.org/licenses/by/2.0/","provider":"wikimedia","source":"wikimedia","category":null,"filesize":5386429,"filetype":"jpg","tags":[],"attribution":"\"Alexander Nevsky Cathedral (13338249245)\" by Jorge Láscar from Australia is licensed under CC BY 2.0. To view a copy of this license, visit https://creativecommons.org/licenses/by/2.0/.","fields_matched":["description"],"mature":false,"height":2848,"width":4288,"thumbnail":"https://api.openverse.org/v1/images/3b5e7737-d1cd-4b32-959f-f71309f97bd2/thumb/","detail_url":"https://api.openverse.org/v1/images/3b5e7737-d1cd-4b32-959f-f71309f97bd2/","related_url":"https://api.openverse.org/v1/images/3b5e7737-d1cd-4b32-959f-f71309f97bd2/related/","unstable__sensitivity":[]},{"id":"e73f4802-b811-4804-a688-aad9fb6f327b","title":"ParishChurchofSt.JamesofSubicjf6617 06","indexed_on":"2020-05-19T09:15:20.019577Z","foreign_landing_url":"https://commons.wikimedia.org/w/index.php?curid=24620942","url":"https://upload.wikimedia.org/wikipedia/commons/b/b9/ParishChurchofSt.JamesofSubicjf6617_06.JPG","creator":"Ramon FVelasquez","creator_url":"https://commons.wikimedia.org/wiki/User:Ramon_FVelasquez","license":"by-sa","license_version":"3.0","license_url":"https://creativecommons.org/licenses/by-sa/3.0/","provider":"wikimedia","source":"wikimedia","category":null,"filesize":7264670,"filetype":"JPG","tags":[],"attribution":"\"ParishChurchofSt.JamesofSubicjf6617 06\" by Ramon FVelasquez is licensed under CC BY-SA 3.0. To view a copy of this license, visit https://creativecommons.org/licenses/by-sa/3.0/.","fields_matched":["description"],"mature":false,"height":3456,"width":4608,"thumbnail":"https://api.openverse.org/v1/images/e73f4802-b811-4804-a688-aad9fb6f327b/thumb/","detail_url":"https://api.openverse.org/v1/images/e73f4802-b811-4804-a688-aad9fb6f327b/","related_url":"https://api.openverse.org/v1/images/e73f4802-b811-4804-a688-aad9fb6f327b/related/","unstable__sensitivity":[]},{"id":"c187e8d2-b90d-4bb1-812b-b58011e34060","title":"Bring Your Own Beer?","indexed_on":"2018-09-11T15:05:25.829896Z","foreign_landing_url":"https://www.geograph.org.uk/photo/1919896","url":"https://s0.geograph.org.uk/geophotos/01/91/98/1919896_71b420eb.jpg","creator":"Michael Graham","creator_url":"https://geograph.org.uk/profile/3141","license":"by-sa","license_version":"2.0","license_url":"https://creativecommons.org/licenses/by-sa/2.0/","provider":"geographorguk","source":"geographorguk","category":null,"filesize":null,"filetype":null,"tags":[{"name":"architecture","accuracy":0.98178,"unstable__provider":"clarifai"},{"name":"building","accuracy":0.97564,"unstable__provider":"clarifai"},{"name":"house","accuracy":0.97082,"unstable__provider":"clarifai"},{"name":"daylight","accuracy":0.93762,"unstable__provider":"clarifai"},{"name":"home","accuracy":0.93395,"unstable__provider":"clarifai"},{"name":"outdoors","accuracy":0.92223,"unstable__provider":"clarifai"},{"name":"tree","accuracy":0.91985,"unstable__provider":"clarifai"},{"name":"church","accuracy":0.91755,"unstable__provider":"clarifai"},{"name":"old","accuracy":0.91494,"unstable__provider":"clarifai"},{"name":"religion","accuracy":0.9141,"unstable__provider":"clarifai"}],"attribution":"\"Bring Your Own Beer?\" by Michael Graham is licensed under CC BY-SA 2.0. To view a copy of this license, visit https://creativecommons.org/licenses/by-sa/2.0/.","fields_matched":["description","tags.name"],"mature":false,"height":480,"width":640,"thumbnail":"https://api.openverse.org/v1/images/c187e8d2-b90d-4bb1-812b-b58011e34060/thumb/","detail_url":"https://api.openverse.org/v1/images/c187e8d2-b90d-4bb1-812b-b58011e34060/","related_url":"https://api.openverse.org/v1/images/c187e8d2-b90d-4bb1-812b-b58011e34060/related/","unstable__sensitivity":[]},{"id":"080d416c-4cb7-42c4-a13b-6fd139c49308","title":"Subichruchjf6579 06","indexed_on":"2020-05-19T09:05:21.457720Z","foreign_landing_url":"https://commons.wikimedia.org/w/index.php?curid=24613770","url":"https://upload.wikimedia.org/wikipedia/commons/f/f2/Subichruchjf6579_06.JPG","creator":"Ramon FVelasquez","creator_url":"https://commons.wikimedia.org/wiki/User:Ramon_FVelasquez","license":"by-sa","license_version":"3.0","license_url":"https://creativecommons.org/licenses/by-sa/3.0/","provider":"wikimedia","source":"wikimedia","category":null,"filesize":6963253,"filetype":"JPG","tags":[],"attribution":"\"Subichruchjf6579 06\" by Ramon FVelasquez is licensed under CC BY-SA 3.0. To view a copy of this license, visit https://creativecommons.org/licenses/by-sa/3.0/.","fields_matched":["description"],"mature":false,"height":3456,"width":4608,"thumbnail":"https://api.openverse.org/v1/images/080d416c-4cb7-42c4-a13b-6fd139c49308/thumb/","detail_url":"https://api.openverse.org/v1/images/080d416c-4cb7-42c4-a13b-6fd139c49308/","related_url":"https://api.openverse.org/v1/images/080d416c-4cb7-42c4-a13b-6fd139c49308/related/","unstable__sensitivity":[]},{"id":"0722f63a-01a1-49c4-8c6e-3ee0792cab5b","title":"Subicchurchjf 01","indexed_on":"2020-05-19T09:15:20.019577Z","foreign_landing_url":"https://commons.wikimedia.org/w/index.php?curid=24620130","url":"https://upload.wikimedia.org/wikipedia/commons/f/f9/Subicchurchjf_01.jpg","creator":"Ramon FVelasquez","creator_url":"https://commons.wikimedia.org/wiki/User:Ramon_FVelasquez","license":"by-sa","license_version":"3.0","license_url":"https://creativecommons.org/licenses/by-sa/3.0/","provider":"wikimedia","source":"wikimedia","category":null,"filesize":175952,"filetype":"jpg","tags":[],"attribution":"\"Subicchurchjf 01\" by Ramon FVelasquez is licensed under CC BY-SA 3.0. To view a copy of this license, visit https://creativecommons.org/licenses/by-sa/3.0/.","fields_matched":["description"],"mature":false,"height":480,"width":640,"thumbnail":"https://api.openverse.org/v1/images/0722f63a-01a1-49c4-8c6e-3ee0792cab5b/thumb/","detail_url":"https://api.openverse.org/v1/images/0722f63a-01a1-49c4-8c6e-3ee0792cab5b/","related_url":"https://api.openverse.org/v1/images/0722f63a-01a1-49c4-8c6e-3ee0792cab5b/related/","unstable__sensitivity":[]}]}
 succeeded in 1578ms:
{"result_count":31,"page_count":2,"page_size":20,"page":1,"results":[{"id":"2f713cb4-0563-408b-8644-b6f08c4222dd","title":"Rev. Dr. William Barber, 'Vote your future not your fears'","indexed_on":"2020-04-04T16:30:19.322302Z","foreign_landing_url":"https://www.flickr.com/photos/47422005@N04/14556017020","url":"https://live.staticflickr.com/3921/14556017020_b8bc1dfa3b.jpg","creator":"DonkeyHotey","creator_url":"https://www.flickr.com/photos/47422005@N04","license":"by","license_version":"2.0","license_url":"https://creativecommons.org/licenses/by/2.0/","provider":"flickr","source":"flickr","category":null,"filesize":null,"filetype":null,"tags":[{"name":"art","accuracy":null,"unstable__provider":"flickr"},{"name":"campaign","accuracy":null,"unstable__provider":"flickr"},{"name":"caricatura","accuracy":null,"unstable__provider":"flickr"},{"name":"caricature","accuracy":null,"unstable__provider":"flickr"},{"name":"cartoon","accuracy":null,"unstable__provider":"flickr"},{"name":"commentary","accuracy":null,"unstable__provider":"flickr"},{"name":"donkeyhotey","accuracy":null,"unstable__provider":"flickr"},{"name":"face","accuracy":null,"unstable__provider":"flickr"},{"name":"goldsboro","accuracy":null,"unstable__provider":"flickr"},{"name":"greenleafchristianchurchdisciplesofchrist","accuracy":null,"unstable__provider":"flickr"},{"name":"karikatur","accuracy":null,"unstable__provider":"flickr"},{"name":"karikatuur","accuracy":null,"unstable__provider":"flickr"},{"name":"manipulation","accuracy":null,"unstable__provider":"flickr"},{"name":"moralmondays","accuracy":null,"unstable__provider":"flickr"},{"name":"naacp","accuracy":null,"unstable__provider":"flickr"},{"name":"nc","accuracy":null,"unstable__provider":"flickr"},{"name":"northcarolina","accuracy":null,"unstable__provider":"flickr"},{"name":"pastor","accuracy":null,"unstable__provider":"flickr"},{"name":"photo","accuracy":null,"unstable__provider":"flickr"},{"name":"photomanipulation","accuracy":null,"unstable__provider":"flickr"},{"name":"photoshop","accuracy":null,"unstable__provider":"flickr"},{"name":"political","accuracy":null,"unstable__provider":"flickr"},{"name":"politicalart","accuracy":null,"unstable__provider":"flickr"},{"name":"politicalcommentary","accuracy":null,"unstable__provider":"flickr"},{"name":"politician","accuracy":null,"unstable__provider":"flickr"},{"name":"politics","accuracy":null,"unstable__provider":"flickr"},{"name":"president","accuracy":null,"unstable__provider":"flickr"},{"name":"protests","accuracy":null,"unstable__provider":"flickr"},{"name":"revdrwilliambarber","accuracy":null,"unstable__provider":"flickr"}],"attribution":"\"Rev. Dr. William Barber, 'Vote your future not your fears'\" by DonkeyHotey is licensed under CC BY 2.0. To view a copy of this license, visit https://creativecommons.org/licenses/by/2.0/.","fields_matched":["description"],"mature":false,"height":350,"width":500,"thumbnail":"https://api.openverse.org/v1/images/2f713cb4-0563-408b-8644-b6f08c4222dd/thumb/","detail_url":"https://api.openverse.org/v1/images/2f713cb4-0563-408b-8644-b6f08c4222dd/","related_url":"https://api.openverse.org/v1/images/2f713cb4-0563-408b-8644-b6f08c4222dd/related/","unstable__sensitivity":[]},{"id":"1c863db2-8ee0-4a87-bcee-88b96109d47b","title":"Rev. Dr. William Barber - Caricature","indexed_on":"2020-04-04T16:30:19.322302Z","foreign_landing_url":"https://www.flickr.com/photos/47422005@N04/14742387132","url":"https://live.staticflickr.com/2898/14742387132_8cc37a6b1a.jpg","creator":"DonkeyHotey","creator_url":"https://www.flickr.com/photos/47422005@N04","license":"by","license_version":"2.0","license_url":"https://creativecommons.org/licenses/by/2.0/","provider":"flickr","source":"flickr","category":null,"filesize":null,"filetype":null,"tags":[{"name":"art","accuracy":null,"unstable__provider":"flickr"},{"name":"campaign","accuracy":null,"unstable__provider":"flickr"},{"name":"caricatura","accuracy":null,"unstable__provider":"flickr"},{"name":"caricature","accuracy":null,"unstable__provider":"flickr"},{"name":"cartoon","accuracy":null,"unstable__provider":"flickr"},{"name":"commentary","accuracy":null,"unstable__provider":"flickr"},{"name":"donkeyhotey","accuracy":null,"unstable__provider":"flickr"},{"name":"face","accuracy":null,"unstable__provider":"flickr"},{"name":"goldsboro","accuracy":null,"unstable__provider":"flickr"},{"name":"greenleafchristianchurchdisciplesofchrist","accuracy":null,"unstable__provider":"flickr"},{"name":"karikatur","accuracy":null,"unstable__provider":"flickr"},{"name":"karikatuur","accuracy":null,"unstable__provider":"flickr"},{"name":"manipulation","accuracy":null,"unstable__provider":"flickr"},{"name":"moralmondays","accuracy":null,"unstable__provider":"flickr"},{"name":"naacp","accuracy":null,"unstable__provider":"flickr"},{"name":"nc","accuracy":null,"unstable__provider":"flickr"},{"name":"northcarolina","accuracy":null,"unstable__provider":"flickr"},{"name":"pastor","accuracy":null,"unstable__provider":"flickr"},{"name":"photo","accuracy":null,"unstable__provider":"flickr"},{"name":"photomanipulation","accuracy":null,"unstable__provider":"flickr"},{"name":"photoshop","accuracy":null,"unstable__provider":"flickr"},{"name":"political","accuracy":null,"unstable__provider":"flickr"},{"name":"politicalart","accuracy":null,"unstable__provider":"flickr"},{"name":"politicalcommentary","accuracy":null,"unstable__provider":"flickr"},{"name":"politician","accuracy":null,"unstable__provider":"flickr"},{"name":"politics","accuracy":null,"unstable__provider":"flickr"},{"name":"president","accuracy":null,"unstable__provider":"flickr"},{"name":"protests","accuracy":null,"unstable__provider":"flickr"},{"name":"revdrwilliambarber","accuracy":null,"unstable__provider":"flickr"}],"attribution":"\"Rev. Dr. William Barber - Caricature\" by DonkeyHotey is licensed under CC BY 2.0. To view a copy of this license, visit https://creativecommons.org/licenses/by/2.0/.","fields_matched":["description"],"mature":false,"height":500,"width":357,"thumbnail":"https://api.openverse.org/v1/images/1c863db2-8ee0-4a87-bcee-88b96109d47b/thumb/","detail_url":"https://api.openverse.org/v1/images/1c863db2-8ee0-4a87-bcee-88b96109d47b/","related_url":"https://api.openverse.org/v1/images/1c863db2-8ee0-4a87-bcee-88b96109d47b/related/","unstable__sensitivity":[]},{"id":"4e81db93-6e3f-4799-a6fe-908843f8943a","title":"Rev. Dr. William Barber - Caricature","indexed_on":"2020-04-04T16:30:19.322302Z","foreign_landing_url":"https://www.flickr.com/photos/47422005@N04/14556219537","url":"https://live.staticflickr.com/2936/14556219537_476afabdcd.jpg","creator":"DonkeyHotey","creator_url":"https://www.flickr.com/photos/47422005@N04","license":"by","license_version":"2.0","license_url":"https://creativecommons.org/licenses/by/2.0/","provider":"flickr","source":"flickr","category":null,"filesize":null,"filetype":null,"tags":[{"name":"art","accuracy":null,"unstable__provider":"flickr"},{"name":"campaign","accuracy":null,"unstable__provider":"flickr"},{"name":"caricatura","accuracy":null,"unstable__provider":"flickr"},{"name":"caricature","accuracy":null,"unstable__provider":"flickr"},{"name":"cartoon","accuracy":null,"unstable__provider":"flickr"},{"name":"commentary","accuracy":null,"unstable__provider":"flickr"},{"name":"donkeyhotey","accuracy":null,"unstable__provider":"flickr"},{"name":"face","accuracy":null,"unstable__provider":"flickr"},{"name":"goldsboro","accuracy":null,"unstable__provider":"flickr"},{"name":"greenleafchristianchurchdisciplesofchrist","accuracy":null,"unstable__provider":"flickr"},{"name":"karikatur","accuracy":null,"unstable__provider":"flickr"},{"name":"karikatuur","accuracy":null,"unstable__provider":"flickr"},{"name":"manipulation","accuracy":null,"unstable__provider":"flickr"},{"name":"moralmondays","accuracy":null,"unstable__provider":"flickr"},{"name":"naacp","accuracy":null,"unstable__provider":"flickr"},{"name":"nc","accuracy":null,"unstable__provider":"flickr"},{"name":"northcarolina","accuracy":null,"unstable__provider":"flickr"},{"name":"pastor","accuracy":null,"unstable__provider":"flickr"},{"name":"photo","accuracy":null,"unstable__provider":"flickr"},{"name":"photomanipulation","accuracy":null,"unstable__provider":"flickr"},{"name":"photoshop","accuracy":null,"unstable__provider":"flickr"},{"name":"political","accuracy":null,"unstable__provider":"flickr"},{"name":"politicalart","accuracy":null,"unstable__provider":"flickr"},{"name":"politicalcommentary","accuracy":null,"unstable__provider":"flickr"},{"name":"politician","accuracy":null,"unstable__provider":"flickr"},{"name":"politics","accuracy":null,"unstable__provider":"flickr"},{"name":"president","accuracy":null,"unstable__provider":"flickr"},{"name":"protests","accuracy":null,"unstable__provider":"flickr"},{"name":"revdrwilliambarber","accuracy":null,"unstable__provider":"flickr"},{"name":"man","accuracy":0.9793,"unstable__provider":"clarifai"},{"name":"people","accuracy":0.95449,"unstable__provider":"clarifai"},{"name":"portrait","accuracy":0.93969,"unstable__provider":"clarifai"}],"attribution":"\"Rev. Dr. William Barber - Caricature\" by DonkeyHotey is licensed under CC BY 2.0. To view a copy of this license, visit https://creativecommons.org/licenses/by/2.0/.","fields_matched":["description"],"mature":false,"height":350,"width":500,"thumbnail":"https://api.openverse.org/v1/images/4e81db93-6e3f-4799-a6fe-908843f8943a/thumb/","detail_url":"https://api.openverse.org/v1/images/4e81db93-6e3f-4799-a6fe-908843f8943a/","related_url":"https://api.openverse.org/v1/images/4e81db93-6e3f-4799-a6fe-908843f8943a/related/","unstable__sensitivity":[]},{"id":"5bc99c54-8fa9-4aac-a69a-6c65d6aa4317","title":"THE DAZZLING NIGHT OF BEIJING (UNESCO Included)","indexed_on":"2020-04-21T10:53:35.745393Z","foreign_landing_url":"https://www.flickr.com/photos/41492866@N00/4531016816","url":"https://live.staticflickr.com/4018/4531016816_ff44dfe3b5_b.jpg","creator":"Mumu X","creator_url":"https://www.flickr.com/photos/41492866@N00","license":"by","license_version":"2.0","license_url":"https://creativecommons.org/licenses/by/2.0/","provider":"flickr","source":"flickr","category":null,"filesize":null,"filetype":null,"tags":[{"name":"beijing","accuracy":null,"unstable__provider":"flickr"},{"name":"china","accuracy":null,"unstable__provider":"flickr"},{"name":"night","accuracy":null,"unstable__provider":"flickr"},{"name":"postcard","accuracy":null,"unstable__provider":"flickr"},{"name":"view","accuracy":null,"unstable__provider":"flickr"},{"name":"banner","accuracy":0.95814,"unstable__provider":"clarifai"},{"name":"business","accuracy":0.91025,"unstable__provider":"clarifai"},{"name":"card","accuracy":0.91902,"unstable__provider":"clarifai"},{"name":"layout","accuracy":0.94042,"unstable__provider":"clarifai"},{"name":"set","accuracy":0.97279,"unstable__provider":"clarifai"},{"name":"template","accuracy":0.96091,"unstable__provider":"clarifai"},{"name":"World Wide Web","accuracy":0.93656,"unstable__provider":"clarifai"}],"attribution":"\"THE DAZZLING NIGHT OF BEIJING (UNESCO Included)\" by Mumu X is licensed under CC BY 2.0. To view a copy of this license, visit https://creativecommons.org/licenses/by/2.0/.","fields_matched":["description","tags.name"],"mature":false,"height":683,"width":1024,"thumbnail":"https://api.openverse.org/v1/images/5bc99c54-8fa9-4aac-a69a-6c65d6aa4317/thumb/","detail_url":"https://api.openverse.org/v1/images/5bc99c54-8fa9-4aac-a69a-6c65d6aa4317/","related_url":"https://api.openverse.org/v1/images/5bc99c54-8fa9-4aac-a69a-6c65d6aa4317/related/","unstable__sensitivity":[]},{"id":"9ee35894-3b1a-49ec-9217-ef184f1b978a","title":"Prayer to Saint Mother Euphrasia Eluvathingal","indexed_on":"2020-03-19T15:58:41.541399Z","foreign_landing_url":"https://www.flickr.com/photos/146857093@N05/32395313921","url":"https://live.staticflickr.com/559/32395313921_364f1a9834.jpg","creator":"Saints and Blesseds","creator_url":"https://www.flickr.com/photos/146857093@N05","license":"pdm","license_version":"1.0","license_url":"https://creativecommons.org/publicdomain/mark/1.0/","provider":"flickr","source":"flickr","category":null,"filesize":null,"filetype":null,"tags":[{"name":"2014","accuracy":null,"unstable__provider":"flickr"},{"name":"blessed","accuracy":null,"unstable__provider":"flickr"},{"name":"canonised","accuracy":null,"unstable__provider":"flickr"},{"name":"card","accuracy":null,"unstable__provider":"flickr"},{"name":"catholic","accuracy":null,"unstable__provider":"flickr"},{"name":"christian","accuracy":null,"unstable__provider":"flickr"},{"name":"church","accuracy":null,"unstable__provider":"flickr"},{"name":"eluvathingal","accuracy":null,"unstable__provider":"flickr"},{"name":"euphrasia","accuracy":null,"unstable__provider":"flickr"},{"name":"francis","accuracy":null,"unstable__provider":"flickr"},{"name":"god","accuracy":null,"unstable__provider":"flickr"},{"name":"heart","accuracy":null,"unstable__provider":"flickr"},{"name":"holy","accuracy":null,"unstable__provider":"flickr"},{"name":"india","accuracy":null,"unstable__provider":"flickr"},{"name":"indian","accuracy":null,"unstable__provider":"flickr"},{"name":"mother","accuracy":null,"unstable__provider":"flickr"},{"name":"nun","accuracy":null,"unstable__provider":"flickr"},{"name":"patron","accuracy":null,"unstable__provider":"flickr"},{"name":"patroness","accuracy":null,"unstable__provider":"flickr"},{"name":"pope","accuracy":null,"unstable__provider":"flickr"},{"name":"prayer","accuracy":null,"unstable__provider":"flickr"},{"name":"praying","accuracy":null,"unstable__provider":"flickr"},{"name":"religion","accuracy":null,"unstable__provider":"flickr"},{"name":"sacred","accuracy":null,"unstable__provider":"flickr"},{"name":"saint","accuracy":null,"unstable__provider":"flickr"},{"name":"servant","accuracy":null,"unstable__provider":"flickr"},{"name":"st","accuracy":null,"unstable__provider":"flickr"},{"name":"venerable","accuracy":null,"unstable__provider":"flickr"}],"attribution":"\"Prayer to Saint Mother Euphrasia Eluvathingal\" by Saints and Blesseds is marked with Public Domain Mark 1.0. To view the terms, visit https://creativecommons.org/publicdomain/mark/1.0/.","fields_matched":["title","tags.name"],"mature":false,"height":500,"width":253,"thumbnail":"https://api.openverse.org/v1/images/9ee35894-3b1a-49ec-9217-ef184f1b978a/thumb/","detail_url":"https://api.openverse.org/v1/images/9ee35894-3b1a-49ec-9217-ef184f1b978a/","related_url":"https://api.openverse.org/v1/images/9ee35894-3b1a-49ec-9217-ef184f1b978a/related/","unstable__sensitivity":[]},{"id":"f80b3833-8b24-4f23-b774-336e36a3bba4","title":"Germany - Storied castle of the Brothers and Moat, Bornhofen on the Rhine, south from river-road, Germany","indexed_on":"2020-07-31T06:45:34.210049Z","foreign_landing_url":"https://www.flickr.com/photos/70994841@N07/8166467861","url":"https://live.staticflickr.com/8203/8166467861_bd5acc1e73_b.jpg","creator":"Aussie~mobs","creator_url":"https://www.flickr.com/photos/70994841@N07","license":"pdm","license_version":"1.0","license_url":"https://creativecommons.org/publicdomain/mark/1.0/","provider":"flickr","source":"flickr","category":null,"filesize":null,"filetype":null,"tags":[{"name":"aussiemobs","accuracy":null,"unstable__provider":"flickr"},{"name":"bayervonboppard","accuracy":null,"unstable__provider":"flickr"},{"name":"bornhofen","accuracy":null,"unstable__provider":"flickr"},{"name":"castle","accuracy":null,"unstable__provider":"flickr"},{"name":"liebenstein","accuracy":null,"unstable__provider":"flickr"},{"name":"stereoscopicphotograph","accuracy":null,"unstable__provider":"flickr"},{"name":"stereoview","accuracy":null,"unstable__provider":"flickr"},{"name":"sterrenberg","accuracy":null,"unstable__provider":"flickr"},{"name":"vintage","accuracy":null,"unstable__provider":"flickr"}],"attribution":"\"Germany - Storied castle of the Brothers and Moat, Bornhofen on the Rhine, south from river-road, Germany\" by Aussie~mobs is marked with Public Domain Mark 1.0. To view the terms, visit https://creativecommons.org/publicdomain/mark/1.0/.","fields_matched":["description"],"mature":false,"height":503,"width":1024,"thumbnail":"https://api.openverse.org/v1/images/f80b3833-8b24-4f23-b774-336e36a3bba4/thumb/","detail_url":"https://api.openverse.org/v1/images/f80b3833-8b24-4f23-b774-336e36a3bba4/","related_url":"https://api.openverse.org/v1/images/f80b3833-8b24-4f23-b774-336e36a3bba4/related/","unstable__sensitivity":[]},{"id":"97e178a1-f463-4b56-9b82-2dfab91151b6","title":"Prayer to Saint Sigismund","indexed_on":"2020-03-21T06:00:33.246789Z","foreign_landing_url":"https://www.flickr.com/photos/146857093@N05/35210220833","url":"https://live.staticflickr.com/4317/35210220833_0bbed65a95_b.jpg","creator":"Saints and Blesseds","creator_url":"https://www.flickr.com/photos/146857093@N05","license":"pdm","license_version":"1.0","license_url":"https://creativecommons.org/publicdomain/mark/1.0/","provider":"flickr","source":"flickr","category":null,"filesize":null,"filetype":null,"tags":[{"name":"aggression","accuracy":null,"unstable__provider":"flickr"},{"name":"aggressive","accuracy":null,"unstable__provider":"flickr"},{"name":"anger","accuracy":null,"unstable__provider":"flickr"},{"name":"angry","accuracy":null,"unstable__provider":"flickr"},{"name":"bad","accuracy":null,"unstable__provider":"flickr"},{"name":"beati","accuracy":null,"unstable__provider":"flickr"},{"name":"beato","accuracy":null,"unstable__provider":"flickr"},{"name":"burgundy","accuracy":null,"unstable__provider":"flickr"},{"name":"card","accuracy":null,"unstable__provider":"flickr"},{"name":"catholic","accuracy":null,"unstable__provider":"flickr"},{"name":"church","accuracy":null,"unstable__provider":"flickr"},{"name":"france","accuracy":null,"unstable__provider":"flickr"},{"name":"holy","accuracy":null,"unstable__provider":"flickr"},{"name":"irate","accuracy":null,"unstable__provider":"flickr"},{"name":"irritable","accuracy":null,"unstable__provider":"flickr"},{"name":"issues","accuracy":null,"unstable__provider":"flickr"},{"name":"king","accuracy":null,"unstable__provider":"flickr"},{"name":"lord","accuracy":null,"unstable__provider":"flickr"},{"name":"management","accuracy":null,"unstable__provider":"flickr"},{"name":"patron","accuracy":null,"unstable__provider":"flickr"},{"name":"patronage","accuracy":null,"unstable__provider":"flickr"},{"name":"penitent","accuracy":null,"unstable__provider":"flickr"},{"name":"prayer","accuracy":null,"unstable__provider":"flickr"},{"name":"problem","accuracy":null,"unstable__provider":"flickr"},{"name":"problems","accuracy":null,"unstable__provider":"flickr"},{"name":"rage","accuracy":null,"unstable__provider":"flickr"},{"name":"saint","accuracy":null,"unstable__provider":"flickr"},{"name":"san","accuracy":null,"unstable__provider":"flickr"},{"name":"santi","accuracy":null,"unstable__provider":"flickr"},{"name":"santo","accuracy":null,"unstable__provider":"flickr"},{"name":"santos","accuracy":null,"unstable__provider":"flickr"},{"name":"segismundo","accuracy":null,"unstable__provider":"flickr"},{"name":"sigismund","accuracy":null,"unstable__provider":"flickr"},{"name":"sigismundo","accuracy":null,"unstable__provider":"flickr"},{"name":"st","accuracy":null,"unstable__provider":"flickr"},{"name":"temper","accuracy":null,"unstable__provider":"flickr"},{"name":"tempers","accuracy":null,"unstable__provider":"flickr"}],"attribution":"\"Prayer to Saint Sigismund\" by Saints and Blesseds is marked with Public Domain Mark 1.0. To view the terms, visit https://creativecommons.org/publicdomain/mark/1.0/.","fields_matched":["description","title","tags.name"],"mature":false,"height":749,"width":992,"thumbnail":"https://api.openverse.org/v1/images/97e178a1-f463-4b56-9b82-2dfab91151b6/thumb/","detail_url":"https://api.openverse.org/v1/images/97e178a1-f463-4b56-9b82-2dfab91151b6/","related_url":"https://api.openverse.org/v1/images/97e178a1-f463-4b56-9b82-2dfab91151b6/related/","unstable__sensitivity":[]},{"id":"34dfdbed-84b0-4a8c-88a2-38eef18615db","title":"No Known Restrictions: President Roosevelt Portrait, 1942 (LOC)","indexed_on":"2019-01-23T12:27:34.393420Z","foreign_landing_url":"https://www.flickr.com/photos/39735679@N00/2049915351","url":"https://live.staticflickr.com/2185/2049915351_434de805d3_b.jpg","creator":"pingnews.com","creator_url":"https://www.flickr.com/photos/39735679@N00","license":"pdm","license_version":"1.0","license_url":"https://creativecommons.org/publicdomain/mark/1.0/","provider":"flickr","source":"flickr","category":null,"filesize":null,"filetype":null,"tags":[{"name":"american","accuracy":null,"unstable__provider":"flickr"},{"name":"cc","accuracy":null,"unstable__provider":"flickr"},{"name":"creativecommons","accuracy":null,"unstable__provider":"flickr"},{"name":"delano","accuracy":null,"unstable__provider":"flickr"},{"name":"faces","accuracy":null,"unstable__provider":"flickr"},{"name":"farmsecurityadministration","accuracy":null,"unstable__provider":"flickr"},{"name":"fdr","accuracy":null,"unstable__provider":"flickr"},{"name":"franklin","accuracy":null,"unstable__provider":"flickr"},{"name":"fsa","accuracy":null,"unstable__provider":"flickr"},{"name":"history","accuracy":null,"unstable__provider":"flickr"},{"name":"library","accuracy":null,"unstable__provider":"flickr"},{"name":"libraryofcongress","accuracy":null,"unstable__provider":"flickr"},{"name":"loc","accuracy":null,"unstable__provider":"flickr"},{"name":"makinghistory","accuracy":null,"unstable__provider":"flickr"},{"name":"newdeal","accuracy":null,"unstable__provider":"flickr"},{"name":"pingnews","accuracy":null,"unstable__provider":"flickr"},{"name":"portrait","accuracy":null,"unstable__provider":"flickr"},{"name":"portraits","accuracy":null,"unstable__provider":"flickr"},{"name":"presidency","accuracy":null,"unstable__provider":"flickr"},{"name":"president","accuracy":null,"unstable__provider":"flickr"},{"name":"presidentroosevelt","accuracy":null,"unstable__provider":"flickr"},{"name":"public","accuracy":null,"unstable__provider":"flickr"},{"name":"publicdomain","accuracy":null,"unstable__provider":"flickr"},{"name":"roosevelt","accuracy":null,"unstable__provider":"flickr"},{"name":"royaltyfree","accuracy":null,"unstable__provider":"flickr"},{"name":"stockfoto","accuracy":null,"unstable__provider":"flickr"},{"name":"stockphoto","accuracy":null,"unstable__provider":"flickr"},{"name":"stockphotography","accuracy":null,"unstable__provider":"flickr"},{"name":"viapingnews","accuracy":null,"unstable__provider":"flickr"}],"attribution":"\"No Known Restrictions: President Roosevelt Portrait, 1942 (LOC)\" by pingnews.com is marked with Public Domain Mark 1.0. To view the terms, visit https://creativecommons.org/publicdomain/mark/1.0/.","fields_matched":["description"],"mature":false,"height":1024,"width":768,"thumbnail":"https://api.openverse.org/v1/images/34dfdbed-84b0-4a8c-88a2-38eef18615db/thumb/","detail_url":"https://api.openverse.org/v1/images/34dfdbed-84b0-4a8c-88a2-38eef18615db/","related_url":"https://api.openverse.org/v1/images/34dfdbed-84b0-4a8c-88a2-38eef18615db/related/","unstable__sensitivity":[]},{"id":"9b4974ad-50d8-4b15-bac8-acdb4f9e519a","title":"Prayer to Saint Nimatullah of Lebanon","indexed_on":"2020-02-20T12:22:24.700311Z","foreign_landing_url":"https://www.flickr.com/photos/146857093@N05/32130091330","url":"https://live.staticflickr.com/409/32130091330_5426954b4c.jpg","creator":"Saints and Blesseds","creator_url":"https://www.flickr.com/photos/146857093@N05","license":"pdm","license_version":"1.0","license_url":"https://creativecommons.org/publicdomain/mark/1.0/","provider":"flickr","source":"flickr","category":null,"filesize":null,"filetype":null,"tags":[{"name":"alhardini","accuracy":null,"unstable__provider":"flickr"},{"name":"blessed","accuracy":null,"unstable__provider":"flickr"},{"name":"card","accuracy":null,"unstable__provider":"flickr"},{"name":"catholic","accuracy":null,"unstable__provider":"flickr"},{"name":"charbel","accuracy":null,"unstable__provider":"flickr"},{"name":"christian","accuracy":null,"unstable__provider":"flickr"},{"name":"church","accuracy":null,"unstable__provider":"flickr"},{"name":"churches","accuracy":null,"unstable__provider":"flickr"},{"name":"east","accuracy":null,"unstable__provider":"flickr"},{"name":"eastern","accuracy":null,"unstable__provider":"flickr"},{"name":"faith","accuracy":null,"unstable__provider":"flickr"},{"name":"holy","accuracy":null,"unstable__provider":"flickr"},{"name":"kassab","accuracy":null,"unstable__provider":"flickr"},{"name":"kfifan","accuracy":null,"unstable__provider":"flickr"},{"name":"lebanese","accuracy":null,"unstable__provider":"flickr"},{"name":"lebanon","accuracy":null,"unstable__provider":"flickr"},{"name":"makhlouf","accuracy":null,"unstable__provider":"flickr"},{"name":"maronite","accuracy":null,"unstable__provider":"flickr"},{"name":"middle","accuracy":null,"unstable__provider":"flickr"},{"name":"monk","accuracy":null,"unstable__provider":"flickr"},{"name":"nimatullah","accuracy":null,"unstable__provider":"flickr"},{"name":"patron","accuracy":null,"unstable__provider":"flickr"},{"name":"pray","accuracy":null,"unstable__provider":"flickr"},{"name":"prayer","accuracy":null,"unstable__provider":"flickr"},{"name":"priest","accuracy":null,"unstable__provider":"flickr"},{"name":"saint","accuracy":null,"unstable__provider":"flickr"},{"name":"st","accuracy":null,"unstable__provider":"flickr"}],"attribution":"\"Prayer to Saint Nimatullah of Lebanon\" by Saints and Blesseds is marked with Public Domain Mark 1.0. To view the terms, visit https://creativecommons.org/publicdomain/mark/1.0/.","fields_matched":["title","tags.name"],"mature":false,"height":500,"width":245,"thumbnail":"https://api.openverse.org/v1/images/9b4974ad-50d8-4b15-bac8-acdb4f9e519a/thumb/","detail_url":"https://api.openverse.org/v1/images/9b4974ad-50d8-4b15-bac8-acdb4f9e519a/","related_url":"https://api.openverse.org/v1/images/9b4974ad-50d8-4b15-bac8-acdb4f9e519a/related/","unstable__sensitivity":[]},{"id":"de4fbbbe-b93c-4726-9056-c0609a7240f5","title":"Saint Chi Zhuzi","indexed_on":"2023-03-11T01:29:32.294750Z","foreign_landing_url":"https://www.flickr.com/photos/146857093@N05/51785312281","url":"https://live.staticflickr.com/65535/51785312281_509b81dc10_b.jpg","creator":"Saints and Blesseds","creator_url":"https://www.flickr.com/photos/146857093@N05","license":"pdm","license_version":"1.0","license_url":"https://creativecommons.org/publicdomain/mark/1.0/","provider":"flickr","source":"flickr","category":"photograph","filesize":null,"filetype":"jpg","tags":[{"name":"canonisation","accuracy":null,"unstable__provider":"flickr"},{"name":"card","accuracy":null,"unstable__provider":"flickr"},{"name":"catholic","accuracy":null,"unstable__provider":"flickr"},{"name":"chi","accuracy":null,"unstable__provider":"flickr"},{"name":"china","accuracy":null,"unstable__provider":"flickr"},{"name":"chinese","accuracy":null,"unstable__provider":"flickr"},{"name":"church","accuracy":null,"unstable__provider":"flickr"},{"name":"estampa","accuracy":null,"unstable__provider":"flickr"},{"name":"holy","accuracy":null,"unstable__provider":"flickr"},{"name":"man","accuracy":null,"unstable__provider":"flickr"},{"name":"martire","accuracy":null,"unstable__provider":"flickr"},{"name":"martyr","accuracy":null,"unstable__provider":"flickr"},{"name":"martyrs","accuracy":null,"unstable__provider":"flickr"},{"name":"prayer","accuracy":null,"unstable__provider":"flickr"},{"name":"saint","accuracy":null,"unstable__provider":"flickr"},{"name":"saints","accuracy":null,"unstable__provider":"flickr"},{"name":"santini","accuracy":null,"unstable__provider":"flickr"},{"name":"santino","accuracy":null,"unstable__provider":"flickr"},{"name":"santo","accuracy":null,"unstable__provider":"flickr"},{"name":"xi","accuracy":null,"unstable__provider":"flickr"},{"name":"young","accuracy":null,"unstable__provider":"flickr"},{"name":"zhu","accuracy":null,"unstable__provider":"flickr"},{"name":"zi","accuracy":null,"unstable__provider":"flickr"}],"attribution":"\"Saint Chi Zhuzi\" by Saints and Blesseds is marked with Public Domain Mark 1.0. To view the terms, visit https://creativecommons.org/publicdomain/mark/1.0/.","fields_matched":["tags.name"],"mature":false,"height":1024,"width":755,"thumbnail":"https://api.openverse.org/v1/images/de4fbbbe-b93c-4726-9056-c0609a7240f5/thumb/","detail_url":"https://api.openverse.org/v1/images/de4fbbbe-b93c-4726-9056-c0609a7240f5/","related_url":"https://api.openverse.org/v1/images/de4fbbbe-b93c-4726-9056-c0609a7240f5/related/","unstable__sensitivity":[]},{"id":"beafe2be-15eb-403d-b4c5-671e13505b8e","title":"Germany - Storied castle of the Brothers and Moat, Bornhofen on the Rhine, south from river-road, Germany","indexed_on":"2020-07-31T06:45:34.210049Z","foreign_landing_url":"https://www.flickr.com/photos/70994841@N07/8166467531","url":"https://live.staticflickr.com/8062/8166467531_e82b4921c3_b.jpg","creator":"Aussie~mobs","creator_url":"https://www.flickr.com/photos/70994841@N07","license":"pdm","license_version":"1.0","license_url":"https://creativecommons.org/publicdomain/mark/1.0/","provider":"flickr","source":"flickr","category":null,"filesize":null,"filetype":null,"tags":[{"name":"aussiemobs","accuracy":null,"unstable__provider":"flickr"},{"name":"bayervonboppard","accuracy":null,"unstable__provider":"flickr"},{"name":"bornhofen","accuracy":null,"unstable__provider":"flickr"},{"name":"castle","accuracy":null,"unstable__provider":"flickr"},{"name":"liebenstein","accuracy":null,"unstable__provider":"flickr"},{"name":"stereoscopicphotograph","accuracy":null,"unstable__provider":"flickr"},{"name":"sterrenberg","accuracy":null,"unstable__provider":"flickr"},{"name":"vintage","accuracy":null,"unstable__provider":"flickr"}],"attribution":"\"Germany - Storied castle of the Brothers and Moat, Bornhofen on the Rhine, south from river-road, Germany\" by Aussie~mobs is marked with Public Domain Mark 1.0. To view the terms, visit https://creativecommons.org/publicdomain/mark/1.0/.","fields_matched":["description"],"mature":false,"height":1017,"width":903,"thumbnail":"https://api.openverse.org/v1/images/beafe2be-15eb-403d-b4c5-671e13505b8e/thumb/","detail_url":"https://api.openverse.org/v1/images/beafe2be-15eb-403d-b4c5-671e13505b8e/","related_url":"https://api.openverse.org/v1/images/beafe2be-15eb-403d-b4c5-671e13505b8e/related/","unstable__sensitivity":[]},{"id":"699701d3-33da-4ea9-b031-6a37a40a5c04","title":"Posing in an Ottoman era costume, after missing my tour bus","indexed_on":"2020-04-06T04:36:27.517282Z","foreign_landing_url":"https://www.flickr.com/photos/77742560@N06/15951440121","url":"https://live.staticflickr.com/7567/15951440121_11200a43ed_b.jpg","creator":"shankar s.","creator_url":"https://www.flickr.com/photos/77742560@N06","license":"by","license_version":"2.0","license_url":"https://creativecommons.org/licenses/by/2.0/","provider":"flickr","source":"flickr","category":null,"filesize":null,"filetype":null,"tags":[{"name":"cobblestones","accuracy":null,"unstable__provider":"flickr"},{"name":"constantinople","accuracy":null,"unstable__provider":"flickr"},{"name":"eurasia","accuracy":null,"unstable__provider":"flickr"},{"name":"europe","accuracy":null,"unstable__provider":"flickr"},{"name":"istanbul","accuracy":null,"unstable__provider":"flickr"},{"name":"ottomaneracostume","accuracy":null,"unstable__provider":"flickr"},{"name":"ottomanrelics","accuracy":null,"unstable__provider":"flickr"},{"name":"ottomansummerpalace","accuracy":null,"unstable__provider":"flickr"},{"name":"posing","accuracy":null,"unstable__provider":"flickr"},{"name":"quirkyentranceplaza","accuracy":null,"unstable__provider":"flickr"},{"name":"topkapipalace","accuracy":null,"unstable__provider":"flickr"},{"name":"tourists","accuracy":null,"unstable__provider":"flickr"},{"name":"tu00fcrkiye","accuracy":null,"unstable__provider":"flickr"},{"name":"turkey","accuracy":null,"unstable__provider":"flickr"},{"name":"türkiye","accuracy":null,"unstable__provider":"flickr"},{"name":"architecture","accuracy":0.9803,"unstable__provider":"clarifai"},{"name":"building","accuracy":0.96667,"unstable__provider":"clarifai"},{"name":"church","accuracy":0.95835,"unstable__provider":"clarifai"},{"name":"city","accuracy":0.98126,"unstable__provider":"clarifai"},{"name":"group","accuracy":0.90168,"unstable__provider":"clarifai"},{"name":"people","accuracy":0.98812,"unstable__provider":"clarifai"},{"name":"prayer","accuracy":0.90246,"unstable__provider":"clarifai"},{"name":"religion","accuracy":0.99478,"unstable__provider":"clarifai"},{"name":"street","accuracy":0.95997,"unstable__provider":"clarifai"},{"name":"tourism","accuracy":0.95046,"unstable__provider":"clarifai"},{"name":"tourist","accuracy":0.95196,"unstable__provider":"clarifai"},{"name":"town","accuracy":0.91019,"unstable__provider":"clarifai"},{"name":"travel","accuracy":0.95009,"unstable__provider":"clarifai"}],"attribution":"\"Posing in an Ottoman era costume, after missing my tour bus\" by shankar s. is licensed under CC BY 2.0. To view a copy of this license, visit https://creativecommons.org/licenses/by/2.0/.","fields_matched":["description","tags.name"],"mature":false,"height":678,"width":1024,"thumbnail":"https://api.openverse.org/v1/images/699701d3-33da-4ea9-b031-6a37a40a5c04/thumb/","detail_url":"https://api.openverse.org/v1/images/699701d3-33da-4ea9-b031-6a37a40a5c04/","related_url":"https://api.openverse.org/v1/images/699701d3-33da-4ea9-b031-6a37a40a5c04/related/","unstable__sensitivity":[]},{"id":"9f2af8e1-2443-4e44-aec5-8bffe7db6ac6","title":"Marjory Stoneman Douglas High School banner","indexed_on":"2020-03-02T03:14:03.192862Z","foreign_landing_url":"https://commons.wikimedia.org/w/index.php?curid=69161554","url":"https://upload.wikimedia.org/wikipedia/commons/7/7f/Marjory_Stoneman_Douglas_High_School_banner.jpg","creator":"PCHS-NJROTC","creator_url":"https://commons.wikimedia.org/wiki/User:PCHS-NJROTC","license":"by-sa","license_version":"4.0","license_url":"https://creativecommons.org/licenses/by-sa/4.0/","provider":"wikimedia","source":"wikimedia","category":null,"filesize":1583328,"filetype":"jpg","tags":[],"attribution":"\"Marjory Stoneman Douglas High School banner\" by PCHS-NJROTC is licensed under CC BY-SA 4.0. To view a copy of this license, visit https://creativecommons.org/licenses/by-sa/4.0/.","fields_matched":["description"],"mature":false,"height":1836,"width":3264,"thumbnail":"https://api.openverse.org/v1/images/9f2af8e1-2443-4e44-aec5-8bffe7db6ac6/thumb/","detail_url":"https://api.openverse.org/v1/images/9f2af8e1-2443-4e44-aec5-8bffe7db6ac6/","related_url":"https://api.openverse.org/v1/images/9f2af8e1-2443-4e44-aec5-8bffe7db6ac6/related/","unstable__sensitivity":[]},{"id":"c5397052-3226-494a-8125-46cae1647222","title":"JFK Prayer Card","indexed_on":"2018-11-08T17:31:32.467511Z","foreign_landing_url":"https://www.flickr.com/photos/48094458@N00/6248259739","url":"https://live.staticflickr.com/6052/6248259739_b529006697_b.jpg","creator":"oliva732000","creator_url":"https://www.flickr.com/photos/48094458@N00","license":"by-sa","license_version":"2.0","license_url":"https://creativecommons.org/licenses/by-sa/2.0/","provider":"flickr","source":"flickr","category":null,"filesize":null,"filetype":null,"tags":[{"name":"1950s","accuracy":null,"unstable__provider":"flickr"},{"name":"1960s","accuracy":null,"unstable__provider":"flickr"},{"name":"assassination","accuracy":null,"unstable__provider":"flickr"},{"name":"cards","accuracy":null,"unstable__provider":"flickr"},{"name":"catholic","accuracy":null,"unstable__provider":"flickr"},{"name":"church","accuracy":null,"unstable__provider":"flickr"},{"name":"fitzgerald","accuracy":null,"unstable__provider":"flickr"},{"name":"history","accuracy":null,"unstable__provider":"flickr"},{"name":"ii","accuracy":null,"unstable__provider":"flickr"},{"name":"jfk","accuracy":null,"unstable__provider":"flickr"},{"name":"john","accuracy":null,"unstable__provider":"flickr"},{"name":"kennedy","accuracy":null,"unstable__provider":"flickr"},{"name":"mass","accuracy":null,"unstable__provider":"flickr"},{"name":"memorial","accuracy":null,"unstable__provider":"flickr"},{"name":"prayer","accuracy":null,"unstable__provider":"flickr"},{"name":"pre","accuracy":null,"unstable__provider":"flickr"},{"name":"president","accuracy":null,"unstable__provider":"flickr"},{"name":"religion","accuracy":null,"unstable__provider":"flickr"},{"name":"roman","accuracy":null,"unstable__provider":"flickr"},{"name":"vatican","accuracy":null,"unstable__provider":"flickr"}],"attribution":"\"JFK Prayer Card\" by oliva732000 is licensed under CC BY-SA 2.0. To view a copy of this license, visit https://creativecommons.org/licenses/by-sa/2.0/.","fields_matched":["title","tags.name"],"mature":false,"height":1024,"width":641,"thumbnail":"https://api.openverse.org/v1/images/c5397052-3226-494a-8125-46cae1647222/thumb/","detail_url":"https://api.openverse.org/v1/images/c5397052-3226-494a-8125-46cae1647222/","related_url":"https://api.openverse.org/v1/images/c5397052-3226-494a-8125-46cae1647222/related/","unstable__sensitivity":[]},{"id":"7a3832bc-2edb-4d2c-b130-69ab75dbd415","title":"The Fiery Circus","indexed_on":"2016-11-16T20:20:32.238348Z","foreign_landing_url":"https://www.flickr.com/photos/33917831@N00/1422802694","url":"https://live.staticflickr.com/1149/1422802694_3e664486a3_b.jpg","creator":"Orin Zebest","creator_url":"https://www.flickr.com/photos/33917831@N00","license":"by","license_version":"2.0","license_url":"https://creativecommons.org/licenses/by/2.0/","provider":"flickr","source":"flickr","category":null,"filesize":null,"filetype":null,"tags":[{"name":"albanybulb","accuracy":null,"unstable__provider":"flickr"},{"name":"circus","accuracy":null,"unstable__provider":"flickr"},{"name":"fiery","accuracy":null,"unstable__provider":"flickr"},{"name":"painting","accuracy":null,"unstable__provider":"flickr"},{"name":"sniff","accuracy":null,"unstable__provider":"flickr"},{"name":"tiger","accuracy":null,"unstable__provider":"flickr"},{"name":"wood","accuracy":null,"unstable__provider":"flickr"},{"name":"art","accuracy":0.9992,"unstable__provider":"clarifai"},{"name":"artistic","accuracy":0.97108,"unstable__provider":"clarifai"},{"name":"belief","accuracy":0.96803,"unstable__provider":"clarifai"},{"name":"book","accuracy":0.9589,"unstable__provider":"clarifai"},{"name":"church","accuracy":0.97562,"unstable__provider":"clarifai"},{"name":"culture","accuracy":0.95671,"unstable__provider":"clarifai"},{"name":"decoration","accuracy":0.95393,"unstable__provider":"clarifai"},{"name":"fresco","accuracy":0.96501,"unstable__provider":"clarifai"},{"name":"god","accuracy":0.99444,"unstable__provider":"clarifai"},{"name":"holy","accuracy":0.98318,"unstable__provider":"clarifai"},{"name":"illustration","accuracy":0.98569,"unstable__provider":"clarifai"},{"name":"mural","accuracy":0.98991,"unstable__provider":"clarifai"},{"name":"painting","accuracy":0.99895,"unstable__provider":"clarifai"},{"name":"prayer","accuracy":0.96228,"unstable__provider":"clarifai"},{"name":"religion","accuracy":0.9972,"unstable__provider":"clarifai"},{"name":"religious belief","accuracy":0.9576,"unstable__provider":"clarifai"},{"name":"saint","accuracy":0.98568,"unstable__provider":"clarifai"},{"name":"spirituality","accuracy":0.97044,"unstable__provider":"clarifai"},{"name":"visuals","accuracy":0.97401,"unstable__provider":"clarifai"},{"name":"wall","accuracy":0.97956,"unstable__provider":"clarifai"}],"attribution":"\"The Fiery Circus\" by Orin Zebest is licensed under CC BY 2.0. To view a copy of this license, visit https://creativecommons.org/licenses/by/2.0/.","fields_matched":["description","tags.name"],"mature":false,"height":768,"width":1024,"thumbnail":"https://api.openverse.org/v1/images/7a3832bc-2edb-4d2c-b130-69ab75dbd415/thumb/","detail_url":"https://api.openverse.org/v1/images/7a3832bc-2edb-4d2c-b130-69ab75dbd415/","related_url":"https://api.openverse.org/v1/images/7a3832bc-2edb-4d2c-b130-69ab75dbd415/related/","unstable__sensitivity":[]},{"id":"b36cdfa5-22b4-4865-bee3-05c053b77750","title":"Vatican II Prayer Card","indexed_on":"2019-04-26T15:45:45.849566Z","foreign_landing_url":"https://www.flickr.com/photos/48094458@N00/6248260169","url":"https://live.staticflickr.com/6108/6248260169_2ac3bd9f82_b.jpg","creator":"oliva732000","creator_url":"https://www.flickr.com/photos/48094458@N00","license":"by-sa","license_version":"2.0","license_url":"https://creativecommons.org/licenses/by-sa/2.0/","provider":"flickr","source":"flickr","category":null,"filesize":null,"filetype":null,"tags":[{"name":"1950s","accuracy":null,"unstable__provider":"flickr"},{"name":"1960s","accuracy":null,"unstable__provider":"flickr"},{"name":"cards","accuracy":null,"unstable__provider":"flickr"},{"name":"catholic","accuracy":null,"unstable__provider":"flickr"},{"name":"church","accuracy":null,"unstable__provider":"flickr"},{"name":"history","accuracy":null,"unstable__provider":"flickr"},{"name":"ii","accuracy":null,"unstable__provider":"flickr"},{"name":"mass","accuracy":null,"unstable__provider":"flickr"},{"name":"prayer","accuracy":null,"unstable__provider":"flickr"},{"name":"pre","accuracy":null,"unstable__provider":"flickr"},{"name":"religion","accuracy":null,"unstable__provider":"flickr"},{"name":"roman","accuracy":null,"unstable__provider":"flickr"},{"name":"vatican","accuracy":null,"unstable__provider":"flickr"}],"attribution":"\"Vatican II Prayer Card\" by oliva732000 is licensed under CC BY-SA 2.0. To view a copy of this license, visit https://creativecommons.org/licenses/by-sa/2.0/.","fields_matched":["description","title","tags.name"],"mature":false,"height":1024,"width":597,"thumbnail":"https://api.openverse.org/v1/images/b36cdfa5-22b4-4865-bee3-05c053b77750/thumb/","detail_url":"https://api.openverse.org/v1/images/b36cdfa5-22b4-4865-bee3-05c053b77750/","related_url":"https://api.openverse.org/v1/images/b36cdfa5-22b4-4865-bee3-05c053b77750/related/","unstable__sensitivity":[]},{"id":"88eb044f-eb23-4ab5-bebb-1ad414b5b176","title":"Palm Sunday at a Catholic Church during the COVID-19 pandemic (FULL)","indexed_on":"2020-04-16T01:00:13.031600Z","foreign_landing_url":"https://commons.wikimedia.org/w/index.php?curid=89148932","url":"https://upload.wikimedia.org/wikipedia/commons/7/7f/Palm_Sunday_at_a_Catholic_Church_during_the_COVID-19_pandemic_%28FULL%29.jpg","creator":"BlueShirtz","creator_url":"https://commons.wikimedia.org/wiki/User:BlueShirtz","license":"by-sa","license_version":"4.0","license_url":"https://creativecommons.org/licenses/by-sa/4.0/","provider":"wikimedia","source":"wikimedia","category":null,"filesize":3456147,"filetype":"jpg","tags":[],"attribution":"\"Palm Sunday at a Catholic Church during the COVID-19 pandemic (FULL)\" by BlueShirtz is licensed under CC BY-SA 4.0. To view a copy of this license, visit https://creativecommons.org/licenses/by-sa/4.0/.","fields_matched":["description","title"],"mature":false,"height":3024,"width":4032,"thumbnail":"https://api.openverse.org/v1/images/88eb044f-eb23-4ab5-bebb-1ad414b5b176/thumb/","detail_url":"https://api.openverse.org/v1/images/88eb044f-eb23-4ab5-bebb-1ad414b5b176/","related_url":"https://api.openverse.org/v1/images/88eb044f-eb23-4ab5-bebb-1ad414b5b176/related/","unstable__sensitivity":[]},{"id":"9075dd45-1c21-4fb6-947f-8bc4244698ce","title":"[Hackney Church.]","indexed_on":"2020-04-27T20:26:27.140711Z","foreign_landing_url":"https://www.flickr.com/photos/24029425@N06/2396179477","url":"https://live.staticflickr.com/2166/2396179477_80ef4da65f_b.jpg","creator":"Boston Public Library","creator_url":"https://www.flickr.com/photos/24029425@N06","license":"by","license_version":"2.0","license_url":"https://creativecommons.org/licenses/by/2.0/","provider":"flickr","source":"flickr","category":null,"filesize":null,"filetype":null,"tags":[],"attribution":"\"[Hackney Church.]\" by Boston Public Library is licensed under CC BY 2.0. To view a copy of this license, visit https://creativecommons.org/licenses/by/2.0/.","fields_matched":["description","title"],"mature":false,"height":298,"width":1024,"thumbnail":"https://api.openverse.org/v1/images/9075dd45-1c21-4fb6-947f-8bc4244698ce/thumb/","detail_url":"https://api.openverse.org/v1/images/9075dd45-1c21-4fb6-947f-8bc4244698ce/","related_url":"https://api.openverse.org/v1/images/9075dd45-1c21-4fb6-947f-8bc4244698ce/related/","unstable__sensitivity":[]},{"id":"7ec0caba-eb6d-48a2-b50b-ba0d1816b9cb","title":"Saint Fledh of Ireland","indexed_on":"2023-09-15T00:03:44.938026Z","foreign_landing_url":"https://www.flickr.com/photos/146857093@N05/53187979699","url":"https://live.staticflickr.com/65535/53187979699_2a02b07fc1_b.jpg","creator":"Saints and Blesseds","creator_url":"https://www.flickr.com/photos/146857093@N05","license":"by-sa","license_version":"2.0","license_url":"https://creativecommons.org/licenses/by-sa/2.0/","provider":"flickr","source":"flickr","category":"photograph","filesize":null,"filetype":"jpg","tags":[{"name":"card","accuracy":null,"unstable__provider":"flickr"},{"name":"female","accuracy":null,"unstable__provider":"flickr"},{"name":"fledh","accuracy":null,"unstable__provider":"flickr"},{"name":"ginger","accuracy":null,"unstable__provider":"flickr"},{"name":"haired","accuracy":null,"unstable__provider":"flickr"},{"name":"holy","accuracy":null,"unstable__provider":"flickr"},{"name":"irish","accuracy":null,"unstable__provider":"flickr"},{"name":"prayer","accuracy":null,"unstable__provider":"flickr"},{"name":"red","accuracy":null,"unstable__provider":"flickr"},{"name":"redhead","accuracy":null,"unstable__provider":"flickr"},{"name":"saint","accuracy":null,"unstable__provider":"flickr"},{"name":"saints","accuracy":null,"unstable__provider":"flickr"},{"name":"virgin","accuracy":null,"unstable__provider":"flickr"},{"name":"wicklow","accuracy":null,"unstable__provider":"flickr"}],"attribution":"\"Saint Fledh of Ireland\" by Saints and Blesseds is licensed under CC BY-SA 2.0. To view a copy of this license, visit https://creativecommons.org/licenses/by-sa/2.0/.","fields_matched":["description","tags.name"],"mature":false,"height":1024,"width":574,"thumbnail":"https://api.openverse.org/v1/images/7ec0caba-eb6d-48a2-b50b-ba0d1816b9cb/thumb/","detail_url":"https://api.openverse.org/v1/images/7ec0caba-eb6d-48a2-b50b-ba0d1816b9cb/","related_url":"https://api.openverse.org/v1/images/7ec0caba-eb6d-48a2-b50b-ba0d1816b9cb/related/","unstable__sensitivity":[]},{"id":"ef3aba64-c429-4f66-9a02-6ebb71258723","title":"Twelve Views Gloucester Cathedral. W","indexed_on":"2024-03-29T01:59:00.599666Z","foreign_landing_url":"https://www.rawpixel.com/image/14307856/twelve-views-gloucester-cathedral-mansell-and","url":"https://images.rawpixel.com/editor_1024/cHJpdmF0ZS9sci9pbWFnZXMvd2Vic2l0ZS8yMDI0LTAyL2xyL2dldHR5MTA3aGY4LWltYWdlLmpwZw.jpg","creator":"thegetty","creator_url":null,"license":"cc0","license_version":"1.0","license_url":"https://creativecommons.org/publicdomain/zero/1.0/","provider":"rawpixel","source":"rawpixel","category":"photograph","filesize":null,"filetype":"jpg","tags":[{"name":"architecture","accuracy":null,"unstable__provider":"rawpixel"},{"name":"building","accuracy":null,"unstable__provider":"rawpixel"},{"name":"card","accuracy":null,"unstable__provider":"rawpixel"},{"name":"church","accuracy":null,"unstable__provider":"rawpixel"},{"name":"photo","accuracy":null,"unstable__provider":"rawpixel"},{"name":"prayer","accuracy":null,"unstable__provider":"rawpixel"},{"name":"worship","accuracy":null,"unstable__provider":"rawpixel"}],"attribution":"\"Twelve Views Gloucester Cathedral. W\" by thegetty is marked with CC0 1.0. To view the terms, visit https://creativecommons.org/publicdomain/zero/1.0/.","fields_matched":["tags.name"],"mature":false,"height":3927,"width":2620,"thumbnail":"https://api.openverse.org/v1/images/ef3aba64-c429-4f66-9a02-6ebb71258723/thumb/","detail_url":"https://api.openverse.org/v1/images/ef3aba64-c429-4f66-9a02-6ebb71258723/","related_url":"https://api.openverse.org/v1/images/ef3aba64-c429-4f66-9a02-6ebb71258723/related/","unstable__sensitivity":[]}]}
codex
I have enough context to draft now. I’m writing the article HTML in the same pattern as the existing posts, using the legacy-friendly internal links the task asked for and a real library image that already exists on the site so the post can be published and verified in one pass.
exec
/bin/bash -lc "find wp-content/uploads/imports -maxdepth 1 -type f \\( -name '*.jpg' -o -name '*.png' \\) -printf '%f\\n' | sort" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
children-ministry.jpg
church-exterior.jpg
events-calendar-page-screenshot.png
groups.jpg
ridgecrest-home-navigation-screenshot.png
sunday-service-planning-desk.jpg
wednesday-night-kids-check-in-scene.jpg
worship-service.jpg
youth-group.jpg
youth-worship.jpg

exec
/bin/bash -lc "wp eval 'foreach ([8,9,10,11,12,89] as "'$id) { echo "ID:$id'"\\n\"; echo \"title=\" . get_the_title("'$id) . "'"\\n\"; echo \"alt=\" . get_post_meta("'$id, "_wp_attachment_image_alt", true) . "'"\\n\"; echo \"guid=\" . get_post("'$id)->guid . "'"\\n\\n\"; }'" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc 'wp post list --post_type=post --name=submit-prayer-request-praise-report --fields=ID,post_title,post_status --format=table' in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 549ms:
ID:8
title=Ridgecrest Community Illustration
alt=Illustration representing gathered church community
guid=https://ridgecrestchurch.com/wp-content/uploads/imports/groups.jpg

ID:9
title=Ridgecrest Main Entrance
alt=Main entrance and covered walkway at Ridgecrest Baptist Church in Blanchard, Oklahoma
guid=https://ridgecrestchurch.com/wp-content/uploads/imports/church-exterior.jpg

ID:10
title=Worship Service
alt=People gathered for a worship service at Ridgecrest Baptist Church
guid=https://ridgecrestchurch.com/wp-content/uploads/imports/worship-service.jpg

ID:11
title=Children Ministry
alt=Children participating in ministry activities at Ridgecrest Baptist Church
guid=https://ridgecrestchurch.com/wp-content/uploads/imports/children-ministry.jpg

ID:12
title=Youth Worship
alt=Students gathered for youth worship
guid=https://ridgecrestchurch.com/wp-content/uploads/imports/youth-worship.jpg

ID:89
title=Wednesday Night Kids Check-In Scene
alt=Children's ministry check-in area with volunteers helping families register before a program begins
guid=https://ridgecrestchurch.com/wp-content/uploads/imports/wednesday-night-kids-check-in-scene.jpg


 succeeded in 545ms:
ID	post_title	post_status

codex
I’m writing the article file now, then I’ll publish it with `wp-cli`, assign the existing Isla Bennett author, set the featured image, and run the post-content and URL checks the task requires.
apply patch
patch: completed
/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-255/submit-prayer-request-praise-report.html
diff --git a//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-255/submit-prayer-request-praise-report.html b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-255/submit-prayer-request-praise-report.html
new file mode 100644
index 0000000000000000000000000000000000000000..e384905c8af3a2a5387433e14b746287cd49620d
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-255/submit-prayer-request-praise-report.html
@@ -0,0 +1,174 @@
+<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>

diff --git a//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-255/submit-prayer-request-praise-report.html b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-255/submit-prayer-request-praise-report.html
new file mode 100644
index 0000000000000000000000000000000000000000..e384905c8af3a2a5387433e14b746287cd49620d
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-255/submit-prayer-request-praise-report.html
@@ -0,0 +1,174 @@
+<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>

codex
The article file is ready. I’m publishing it now with the planned slug, author, excerpt, and featured image, then I’ll verify the stored content, inline image IDs, exact Flatlogic URL, the public post URL, and the `/blog/` index.
exec
/bin/bash -lc 'POST_ID=$(wp post create --post_type=post --post_status=publish --post_title='"'How to Submit a Prayer Request or Praise Report (and What Happens Next)' --post_name='submit-prayer-request-praise-report' --post_author=4 --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_content=\""'$(< wp-content/uploads/flatlogic-article-tasks/job-255/submit-prayer-request-praise-report.html)" --porcelain) && wp post meta update "$POST_ID" _thumbnail_id 10 >/dev/null && echo "$POST_ID"' in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "curl -I -L -s https://ridgecrestchurch.com/blog/ | sed -n '1,20p'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 464ms:
HTTP/2 200 
date: Sun, 07 Jun 2026 18:02:28 GMT
content-type: text/html; charset=UTF-8
link: <https://ridgecrestchurch.com/wp-json/>; rel="https://api.w.org/"
server: cloudflare
cf-cache-status: DYNAMIC
report-to: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=XeIeEZsmh%2FBNocx%2FUiTVn1IkEYjEuYF24%2BMKYdffjX3fg4QMteOFQc1J%2FRK8POQrEMxmdMQ80AIljneUTHuDx%2FSLSvIjB%2FhAwxeySABSYtkvh68K8mb1HlC3NlKBag7qY9rPSSD1WA%3D%3D"}]}
nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
cf-ray: a081916339fea3ed-WAW
alt-svc: h3=":443"; ma=86400


diff --git a//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-255/submit-prayer-request-praise-report.html b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-255/submit-prayer-request-praise-report.html
new file mode 100644
index 0000000000000000000000000000000000000000..e384905c8af3a2a5387433e14b746287cd49620d
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-255/submit-prayer-request-praise-report.html
@@ -0,0 +1,174 @@
+<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 1572ms:
94

diff --git a//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-255/submit-prayer-request-praise-report.html b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-255/submit-prayer-request-praise-report.html
new file mode 100644
index 0000000000000000000000000000000000000000..e384905c8af3a2a5387433e14b746287cd49620d
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-255/submit-prayer-request-praise-report.html
@@ -0,0 +1,174 @@
+<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>

codex
The post is published. I’m in the verification pass now: checking the stored WordPress record, confirming the inline figure and required external URL inside `post_content`, resolving the public permalink, and making sure the blog index is still healthy.
exec
/bin/bash -lc 'wp post get 94 --fields=ID,post_title,post_name,post_status,post_author,post_date,post_excerpt --format=json' in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc 'wp post meta get 94 _thumbnail_id' in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "wp post get 94 --field=post_content | sed -n '1,320p'" 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/ | sed -n '1,260p'" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc 'wp post url 94' in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 608ms:
<!DOCTYPE html>
<html lang="en-US">
<head>
<meta charset="UTF-8">
<link rel="profile" href="https://gmpg.org/xfn/11">
<meta name='robots' content='index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1' />
	<style>img:is([sizes="auto" i], [sizes^="auto," i]) { contain-intrinsic-size: 3000px 1500px }</style>
	<meta name="viewport" content="width=device-width" />
<meta name="generator" content="WordPress 6.8.3" />

	<!-- This site is optimized with the Yoast SEO Premium plugin v26.2 (Yoast SEO v26.2) - https://yoast.com/wordpress/plugins/seo/ -->
	<title>How to Submit a Prayer Request or Praise Report (and What Happens Next) - Ridgecrest Baptist Church</title>
	<link rel="canonical" href="https://ridgecrestchurch.com/submit-prayer-request-praise-report/" />
	<meta property="og:locale" content="en_US" />
	<meta property="og:type" content="article" />
	<meta property="og:title" content="How to Submit a Prayer Request or Praise Report (and What Happens Next)" />
	<meta property="og:description" content="Learn how to share your prayer requests and praise reports with Ridgecrest Baptist Church, understand the process, and what to expect after submission." />
	<meta property="og:url" content="https://ridgecrestchurch.com/submit-prayer-request-praise-report/" />
	<meta property="og:site_name" content="Ridgecrest Baptist Church" />
	<meta property="article:published_time" content="2026-06-07T18:02:28+00:00" />
	<meta property="og:image" content="https://ridgecrestchurch.com/wp-content/uploads/imports/worship-service.jpg" />
	<meta property="og:image:width" content="700" />
	<meta property="og:image:height" content="525" />
	<meta property="og:image:type" content="image/jpeg" />
	<meta name="author" content="Isla Bennett" />
	<meta name="twitter:card" content="summary_large_image" />
	<meta name="twitter:label1" content="Written by" />
	<meta name="twitter:data1" content="Isla Bennett" />
	<meta name="twitter:label2" content="Est. reading time" />
	<meta name="twitter:data2" content="10 minutes" />
	<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>
	<!-- / Yoast SEO Premium plugin. -->


<link rel="alternate" type="application/rss+xml" title="Ridgecrest Baptist Church &raquo; Feed" href="https://ridgecrestchurch.com/feed/" />
<link rel="alternate" type="application/rss+xml" title="Ridgecrest Baptist Church &raquo; Comments Feed" href="https://ridgecrestchurch.com/comments/feed/" />
		<style>
			.lazyload,
			.lazyloading {
				max-width: 100%;
			}
		</style>
		<script type="text/javascript">
/* <![CDATA[ */
window._wpemojiSettings = {"baseUrl":"https:\/\/s.w.org\/images\/core\/emoji\/16.0.1\/72x72\/","ext":".png","svgUrl":"https:\/\/s.w.org\/images\/core\/emoji\/16.0.1\/svg\/","svgExt":".svg","source":{"concatemoji":"https:\/\/ridgecrestchurch.com\/wp-includes\/js\/wp-emoji-release.min.js?ver=6.8.3"}};
/*! This file is auto-generated */
!function(s,n){var o,i,e;function c(e){try{var t={supportTests:e,timestamp:(new Date).valueOf()};sessionStorage.setItem(o,JSON.stringify(t))}catch(e){}}function p(e,t,n){e.clearRect(0,0,e.canvas.width,e.canvas.height),e.fillText(t,0,0);var t=new Uint32Array(e.getImageData(0,0,e.canvas.width,e.canvas.height).data),a=(e.clearRect(0,0,e.canvas.width,e.canvas.height),e.fillText(n,0,0),new Uint32Array(e.getImageData(0,0,e.canvas.width,e.canvas.height).data));return t.every(function(e,t){return e===a[t]})}function u(e,t){e.clearRect(0,0,e.canvas.width,e.canvas.height),e.fillText(t,0,0);for(var n=e.getImageData(16,16,1,1),a=0;a<n.data.length;a++)if(0!==n.data[a])return!1;return!0}function f(e,t,n,a){switch(t){case"flag":return n(e,"\ud83c\udff3\ufe0f\u200d\u26a7\ufe0f","\ud83c\udff3\ufe0f\u200b\u26a7\ufe0f")?!1:!n(e,"\ud83c\udde8\ud83c\uddf6","\ud83c\udde8\u200b\ud83c\uddf6")&&!n(e,"\ud83c\udff4\udb40\udc67\udb40\udc62\udb40\udc65\udb40\udc6e\udb40\udc67\udb40\udc7f","\ud83c\udff4\u200b\udb40\udc67\u200b\udb40\udc62\u200b\udb40\udc65\u200b\udb40\udc6e\u200b\udb40\udc67\u200b\udb40\udc7f");case"emoji":return!a(e,"\ud83e\udedf")}return!1}function g(e,t,n,a){var r="undefined"!=typeof WorkerGlobalScope&&self instanceof WorkerGlobalScope?new OffscreenCanvas(300,150):s.createElement("canvas"),o=r.getContext("2d",{willReadFrequently:!0}),i=(o.textBaseline="top",o.font="600 32px Arial",{});return e.forEach(function(e){i[e]=t(o,e,n,a)}),i}function t(e){var t=s.createElement("script");t.src=e,t.defer=!0,s.head.appendChild(t)}"undefined"!=typeof Promise&&(o="wpEmojiSettingsSupports",i=["flag","emoji"],n.supports={everything:!0,everythingExceptFlag:!0},e=new Promise(function(e){s.addEventListener("DOMContentLoaded",e,{once:!0})}),new Promise(function(t){var n=function(){try{var e=JSON.parse(sessionStorage.getItem(o));if("object"==typeof e&&"number"==typeof e.timestamp&&(new Date).valueOf()<e.timestamp+604800&&"object"==typeof e.supportTests)return e.supportTests}catch(e){}return null}();if(!n){if("undefined"!=typeof Worker&&"undefined"!=typeof OffscreenCanvas&&"undefined"!=typeof URL&&URL.createObjectURL&&"undefined"!=typeof Blob)try{var e="postMessage("+g.toString()+"("+[JSON.stringify(i),f.toString(),p.toString(),u.toString()].join(",")+"));",a=new Blob([e],{type:"text/javascript"}),r=new Worker(URL.createObjectURL(a),{name:"wpTestEmojiSupports"});return void(r.onmessage=function(e){c(n=e.data),r.terminate(),t(n)})}catch(e){}c(n=g(i,f,p,u))}t(n)}).then(function(e){for(var t in e)n.supports[t]=e[t],n.supports.everything=n.supports.everything&&n.supports[t],"flag"!==t&&(n.supports.everythingExceptFlag=n.supports.everythingExceptFlag&&n.supports[t]);n.supports.everythingExceptFlag=n.supports.everythingExceptFlag&&!n.supports.flag,n.DOMReady=!1,n.readyCallback=function(){n.DOMReady=!0}}).then(function(){return e}).then(function(){var e;n.supports.everything||(n.readyCallback(),(e=n.source||{}).concatemoji?t(e.concatemoji):e.wpemoji&&e.twemoji&&(t(e.twemoji),t(e.wpemoji)))}))}((window,document),window._wpemojiSettings);
/* ]]> */
</script>
<style id='wp-emoji-styles-inline-css' type='text/css'>

	img.wp-smiley, img.emoji {
		display: inline !important;
		border: none !important;
		box-shadow: none !important;
		height: 1em !important;
		width: 1em !important;
		margin: 0 0.07em !important;
		vertical-align: -0.1em !important;
		background: none !important;
		padding: 0 !important;
	}
</style>
<link rel='stylesheet' id='wp-block-library-css' href='https://ridgecrestchurch.com/wp-includes/css/dist/block-library/style.min.css?ver=6.8.3' type='text/css' media='all' />
<style id='classic-theme-styles-inline-css' type='text/css'>
/*! This file is auto-generated */
.wp-block-button__link{color:#fff;background-color:#32373c;border-radius:9999px;box-shadow:none;text-decoration:none;padding:calc(.667em + 2px) calc(1.333em + 2px);font-size:1.125em}.wp-block-file__button{background:#32373c;color:#fff;text-decoration:none}
</style>
<style id='global-styles-inline-css' type='text/css'>
:root{--wp--preset--aspect-ratio--square: 1;--wp--preset--aspect-ratio--4-3: 4/3;--wp--preset--aspect-ratio--3-4: 3/4;--wp--preset--aspect-ratio--3-2: 3/2;--wp--preset--aspect-ratio--2-3: 2/3;--wp--preset--aspect-ratio--16-9: 16/9;--wp--preset--aspect-ratio--9-16: 9/16;--wp--preset--color--black: #000000;--wp--preset--color--cyan-bluish-gray: #abb8c3;--wp--preset--color--white: #ffffff;--wp--preset--color--pale-pink: #f78da7;--wp--preset--color--vivid-red: #cf2e2e;--wp--preset--color--luminous-vivid-orange: #ff6900;--wp--preset--color--luminous-vivid-amber: #fcb900;--wp--preset--color--light-green-cyan: #7bdcb5;--wp--preset--color--vivid-green-cyan: #00d084;--wp--preset--color--pale-cyan-blue: #8ed1fc;--wp--preset--color--vivid-cyan-blue: #0693e3;--wp--preset--color--vivid-purple: #9b51e0;--wp--preset--gradient--vivid-cyan-blue-to-vivid-purple: linear-gradient(135deg,rgba(6,147,227,1) 0%,rgb(155,81,224) 100%);--wp--preset--gradient--light-green-cyan-to-vivid-green-cyan: linear-gradient(135deg,rgb(122,220,180) 0%,rgb(0,208,130) 100%);--wp--preset--gradient--luminous-vivid-amber-to-luminous-vivid-orange: linear-gradient(135deg,rgba(252,185,0,1) 0%,rgba(255,105,0,1) 100%);--wp--preset--gradient--luminous-vivid-orange-to-vivid-red: linear-gradient(135deg,rgba(255,105,0,1) 0%,rgb(207,46,46) 100%);--wp--preset--gradient--very-light-gray-to-cyan-bluish-gray: linear-gradient(135deg,rgb(238,238,238) 0%,rgb(169,184,195) 100%);--wp--preset--gradient--cool-to-warm-spectrum: linear-gradient(135deg,rgb(74,234,220) 0%,rgb(151,120,209) 20%,rgb(207,42,186) 40%,rgb(238,44,130) 60%,rgb(251,105,98) 80%,rgb(254,248,76) 100%);--wp--preset--gradient--blush-light-purple: linear-gradient(135deg,rgb(255,206,236) 0%,rgb(152,150,240) 100%);--wp--preset--gradient--blush-bordeaux: linear-gradient(135deg,rgb(254,205,165) 0%,rgb(254,45,45) 50%,rgb(107,0,62) 100%);--wp--preset--gradient--luminous-dusk: linear-gradient(135deg,rgb(255,203,112) 0%,rgb(199,81,192) 50%,rgb(65,88,208) 100%);--wp--preset--gradient--pale-ocean: linear-gradient(135deg,rgb(255,245,203) 0%,rgb(182,227,212) 50%,rgb(51,167,181) 100%);--wp--preset--gradient--electric-grass: linear-gradient(135deg,rgb(202,248,128) 0%,rgb(113,206,126) 100%);--wp--preset--gradient--midnight: linear-gradient(135deg,rgb(2,3,129) 0%,rgb(40,116,252) 100%);--wp--preset--font-size--small: 13px;--wp--preset--font-size--medium: 20px;--wp--preset--font-size--large: 36px;--wp--preset--font-size--x-large: 42px;--wp--preset--spacing--20: 0.44rem;--wp--preset--spacing--30: 0.67rem;--wp--preset--spacing--40: 1rem;--wp--preset--spacing--50: 1.5rem;--wp--preset--spacing--60: 2.25rem;--wp--preset--spacing--70: 3.38rem;--wp--preset--spacing--80: 5.06rem;--wp--preset--shadow--natural: 6px 6px 9px rgba(0, 0, 0, 0.2);--wp--preset--shadow--deep: 12px 12px 50px rgba(0, 0, 0, 0.4);--wp--preset--shadow--sharp: 6px 6px 0px rgba(0, 0, 0, 0.2);--wp--preset--shadow--outlined: 6px 6px 0px -3px rgba(255, 255, 255, 1), 6px 6px rgba(0, 0, 0, 1);--wp--preset--shadow--crisp: 6px 6px 0px rgba(0, 0, 0, 1);}:where(.is-layout-flex){gap: 0.5em;}:where(.is-layout-grid){gap: 0.5em;}body .is-layout-flex{display: flex;}.is-layout-flex{flex-wrap: wrap;align-items: center;}.is-layout-flex > :is(*, div){margin: 0;}body .is-layout-grid{display: grid;}.is-layout-grid > :is(*, div){margin: 0;}:where(.wp-block-columns.is-layout-flex){gap: 2em;}:where(.wp-block-columns.is-layout-grid){gap: 2em;}:where(.wp-block-post-template.is-layout-flex){gap: 1.25em;}:where(.wp-block-post-template.is-layout-grid){gap: 1.25em;}.has-black-color{color: var(--wp--preset--color--black) !important;}.has-cyan-bluish-gray-color{color: var(--wp--preset--color--cyan-bluish-gray) !important;}.has-white-color{color: var(--wp--preset--color--white) !important;}.has-pale-pink-color{color: var(--wp--preset--color--pale-pink) !important;}.has-vivid-red-color{color: var(--wp--preset--color--vivid-red) !important;}.has-luminous-vivid-orange-color{color: var(--wp--preset--color--luminous-vivid-orange) !important;}.has-luminous-vivid-amber-color{color: var(--wp--preset--color--luminous-vivid-amber) !important;}.has-light-green-cyan-color{color: var(--wp--preset--color--light-green-cyan) !important;}.has-vivid-green-cyan-color{color: var(--wp--preset--color--vivid-green-cyan) !important;}.has-pale-cyan-blue-color{color: var(--wp--preset--color--pale-cyan-blue) !important;}.has-vivid-cyan-blue-color{color: var(--wp--preset--color--vivid-cyan-blue) !important;}.has-vivid-purple-color{color: var(--wp--preset--color--vivid-purple) !important;}.has-black-background-color{background-color: var(--wp--preset--color--black) !important;}.has-cyan-bluish-gray-background-color{background-color: var(--wp--preset--color--cyan-bluish-gray) !important;}.has-white-background-color{background-color: var(--wp--preset--color--white) !important;}.has-pale-pink-background-color{background-color: var(--wp--preset--color--pale-pink) !important;}.has-vivid-red-background-color{background-color: var(--wp--preset--color--vivid-red) !important;}.has-luminous-vivid-orange-background-color{background-color: var(--wp--preset--color--luminous-vivid-orange) !important;}.has-luminous-vivid-amber-background-color{background-color: var(--wp--preset--color--luminous-vivid-amber) !important;}.has-light-green-cyan-background-color{background-color: var(--wp--preset--color--light-green-cyan) !important;}.has-vivid-green-cyan-background-color{background-color: var(--wp--preset--color--vivid-green-cyan) !important;}.has-pale-cyan-blue-background-color{background-color: var(--wp--preset--color--pale-cyan-blue) !important;}.has-vivid-cyan-blue-background-color{background-color: var(--wp--preset--color--vivid-cyan-blue) !important;}.has-vivid-purple-background-color{background-color: var(--wp--preset--color--vivid-purple) !important;}.has-black-border-color{border-color: var(--wp--preset--color--black) !important;}.has-cyan-bluish-gray-border-color{border-color: var(--wp--preset--color--cyan-bluish-gray) !important;}.has-white-border-color{border-color: var(--wp--preset--color--white) !important;}.has-pale-pink-border-color{border-color: var(--wp--preset--color--pale-pink) !important;}.has-vivid-red-border-color{border-color: var(--wp--preset--color--vivid-red) !important;}.has-luminous-vivid-orange-border-color{border-color: var(--wp--preset--color--luminous-vivid-orange) !important;}.has-luminous-vivid-amber-border-color{border-color: var(--wp--preset--color--luminous-vivid-amber) !important;}.has-light-green-cyan-border-color{border-color: var(--wp--preset--color--light-green-cyan) !important;}.has-vivid-green-cyan-border-color{border-color: var(--wp--preset--color--vivid-green-cyan) !important;}.has-pale-cyan-blue-border-color{border-color: var(--wp--preset--color--pale-cyan-blue) !important;}.has-vivid-cyan-blue-border-color{border-color: var(--wp--preset--color--vivid-cyan-blue) !important;}.has-vivid-purple-border-color{border-color: var(--wp--preset--color--vivid-purple) !important;}.has-vivid-cyan-blue-to-vivid-purple-gradient-background{background: var(--wp--preset--gradient--vivid-cyan-blue-to-vivid-purple) !important;}.has-light-green-cyan-to-vivid-green-cyan-gradient-background{background: var(--wp--preset--gradient--light-green-cyan-to-vivid-green-cyan) !important;}.has-luminous-vivid-amber-to-luminous-vivid-orange-gradient-background{background: var(--wp--preset--gradient--luminous-vivid-amber-to-luminous-vivid-orange) !important;}.has-luminous-vivid-orange-to-vivid-red-gradient-background{background: var(--wp--preset--gradient--luminous-vivid-orange-to-vivid-red) !important;}.has-very-light-gray-to-cyan-bluish-gray-gradient-background{background: var(--wp--preset--gradient--very-light-gray-to-cyan-bluish-gray) !important;}.has-cool-to-warm-spectrum-gradient-background{background: var(--wp--preset--gradient--cool-to-warm-spectrum) !important;}.has-blush-light-purple-gradient-background{background: var(--wp--preset--gradient--blush-light-purple) !important;}.has-blush-bordeaux-gradient-background{background: var(--wp--preset--gradient--blush-bordeaux) !important;}.has-luminous-dusk-gradient-background{background: var(--wp--preset--gradient--luminous-dusk) !important;}.has-pale-ocean-gradient-background{background: var(--wp--preset--gradient--pale-ocean) !important;}.has-electric-grass-gradient-background{background: var(--wp--preset--gradient--electric-grass) !important;}.has-midnight-gradient-background{background: var(--wp--preset--gradient--midnight) !important;}.has-small-font-size{font-size: var(--wp--preset--font-size--small) !important;}.has-medium-font-size{font-size: var(--wp--preset--font-size--medium) !important;}.has-large-font-size{font-size: var(--wp--preset--font-size--large) !important;}.has-x-large-font-size{font-size: var(--wp--preset--font-size--x-large) !important;}
:where(.wp-block-post-template.is-layout-flex){gap: 1.25em;}:where(.wp-block-post-template.is-layout-grid){gap: 1.25em;}
:where(.wp-block-columns.is-layout-flex){gap: 2em;}:where(.wp-block-columns.is-layout-grid){gap: 2em;}
:root :where(.wp-block-pullquote){font-size: 1.5em;line-height: 1.6;}
</style>
<link rel='stylesheet' id='wordpress-popular-posts-css-css' href='https://ridgecrestchurch.com/wp-content/plugins/wordpress-popular-posts/assets/css/wpp.css?ver=6.3.4' type='text/css' media='all' />
<link rel='stylesheet' id='omega-style-css' href='https://ridgecrestchurch.com/wp-content/themes/church/style.css?ver=6.8.3' type='text/css' media='all' />
<script type="text/javascript" src="https://ridgecrestchurch.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1" id="jquery-core-js"></script>
<script type="text/javascript" src="https://ridgecrestchurch.com/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.1" id="jquery-migrate-js"></script>
<script type="text/javascript" src="https://ridgecrestchurch.com/wp-content/themes/church/js/tinynav.js?ver=6.8.3" id="tinynav-js"></script>
<script type="application/json" id="wpp-json">

{"sampling_active":0,"sampling_rate":100,"ajax_url":"https:\/\/ridgecrestchurch.com\/wp-json\/wordpress-popular-posts\/v1\/popular-posts","api_url":"https:\/\/ridgecrestchurch.com\/wp-json\/wordpress-popular-posts","ID":94,"token":"ec8da77390","lang":0,"debug":0}

</script>
<script type="text/javascript" src="https://ridgecrestchurch.com/wp-content/plugins/wordpress-popular-posts/assets/js/wpp.min.js?ver=6.3.4" id="wpp-js-js"></script>
<link rel="https://api.w.org/" href="https://ridgecrestchurch.com/wp-json/" /><link rel="alternate" title="JSON" type="application/json" href="https://ridgecrestchurch.com/wp-json/wp/v2/posts/94" /><link rel="EditURI" type="application/rsd+xml" title="RSD" href="https://ridgecrestchurch.com/xmlrpc.php?rsd" />
<link rel='shortlink' href='https://ridgecrestchurch.com/?p=94' />
<link rel="alternate" title="oEmbed (JSON)" type="application/json+oembed" href="https://ridgecrestchurch.com/wp-json/oembed/1.0/embed?url=https%3A%2F%2Fridgecrestchurch.com%2Fsubmit-prayer-request-praise-report%2F" />
            <style id="wpp-loading-animation-styles">@-webkit-keyframes bgslide{from{background-position-x:0}to{background-position-x:-200%}}@keyframes bgslide{from{background-position-x:0}to{background-position-x:-200%}}.wpp-widget-placeholder,.wpp-widget-block-placeholder,.wpp-shortcode-placeholder{margin:0 auto;width:60px;height:3px;background:#dd3737;background:linear-gradient(90deg,#dd3737 0%,#571313 10%,#dd3737 100%);background-size:200% auto;border-radius:3px;-webkit-animation:bgslide 1s infinite linear;animation:bgslide 1s infinite linear}</style>
            		<script>
			document.documentElement.className = document.documentElement.className.replace('no-js', 'js');
		</script>
				<style>
			.no-js img.lazyload {
				display: none;
			}

			figure.wp-block-image img.lazyloading {
				min-width: 150px;
			}

			.lazyload,
			.lazyloading {
				--smush-placeholder-width: 100px;
				--smush-placeholder-aspect-ratio: 1/1;
				width: var(--smush-image-width, var(--smush-placeholder-width)) !important;
				aspect-ratio: var(--smush-image-aspect-ratio, var(--smush-placeholder-aspect-ratio)) !important;
			}

						.lazyload, .lazyloading {
				opacity: 0;
			}

			.lazyloaded {
				opacity: 1;
				transition: opacity 400ms;
				transition-delay: 0ms;
			}

					</style>
			<!--[if lt IE 9]>
	<script src="https://ridgecrestchurch.com/wp-content/themes/omega/js/html5.js" type="text/javascript"></script>
	<![endif]-->

<style type="text/css" id="custom-colors-css">h1.site-title a, .site-description, .entry-meta, .header-right { color: #211b1a; } .tinynav, .nav-primary .wrap, .omega-nav-menu li ul li:hover, .footer-widgets .wrap, button, input[type="button"], input[type="reset"], input[type="submit"] { background-color: #211b1a; } .site-footer .wrap, .omega-nav-menu li:hover, .omega-nav-menu li:hover ul { background-color: #050505; } .site-inner .entry-meta a, .site-inner .entry-content a, .entry-summary a, .pagination a, .site-inner .sidebar a { color: #B75343; }</style>

<style type="text/css" id="custom-css">body.custom-background {
    background: #f3eee6;
    color: #35251d;
}
.site-header {
    padding-top: 1rem;
}
.site-header .wrap {
    display: block;
    padding: 1.5rem 0 .75rem;
}
.title-area {
    float: none;
    width: auto;
    max-width: 42rem;
    margin: 0 auto;
    text-align: center;
}
.site-title {
    font-size: clamp(2.2rem, 4vw, 3.5rem);
    line-height: 1.05;
    letter-spacing: .02em;
    margin: 0;
}
.site-title a,
.site-title a:hover {
    color: #2d1c15;
    text-decoration: none;
}
.site-description {
    font-size: 1rem;
    font-weight: 600;
    margin-top: .55rem;
    line-height: 1.5;
    text-align: center;
}
.header-right:empty,
.site-inner .sidebar:empty {
    display: none;
}
.home.page .banner,
.home.page .entry-header {
    display: none;
}
.banner {
    margin-bottom: 2rem;
}
.banner .wrap {
    overflow: hidden;
    border-radius: 18px;
}
.banner .header-image,
.banner .attachment-post-thumbnail,
.banner .wp-post-image {
    display: block;
    width: 100%;
    max-height: 340px;
    object-fit: cover;
    border-radius: 18px;
}
.nav-primary {
    margin: 0 auto 2rem;
}
.nav-primary .wrap {
    background: #211b1a;
    border-radius: 18px;
    padding: .35rem .85rem;
    max-width: 1130px;
    box-shadow: 0 16px 38px rgba(34, 22, 17, 0.14);
}
.omega-nav-menu,
.omega-nav-menu > ul {
    display: flex;
    flex-wrap: wrap;
    justify-content: center;
    gap: .15rem .5rem;
    letter-spacing: .08em;
    line-height: 1.3;
}
.omega-nav-menu .menu-item,
.omega-nav-menu .page_item {
    display: block;
}
.omega-nav-menu a {
    padding: 1rem .65rem;
    font-size: 13px;
}
.page .entry-content,
.home.page .entry-content {
    display: grid;
    gap: 2rem;
}
.site-inner {
    padding-bottom: 2rem;
}
.rc-hero,
.rc-section,
.rc-callout {
    background: #ffffff;
    border-radius: 16px;
    box-shadow: 0 10px 30px rgba(59, 44, 31, 0.08);
    padding: 2rem;
}
.rc-hero,
.rc-split {
    display: grid;
    grid-template-columns: minmax(0, 1.1fr) minmax(0, .9fr);
    gap: 2rem;
    align-items: center;
}
.rc-section-heading {
    margin-bottom: 1.25rem;
}
.rc-eyebrow {
    color: #8b5e3c;
    font-weight: 700;
    text-transform: uppercase;
    letter-spacing: .08em;
    margin-bottom: .75rem;
}
.rc-actions {
    display: flex;
    flex-wrap: wrap;
    align-items: center;
    gap: .85rem;
    margin: 1.25rem 0 1.1rem;
}
.rc-actions br {
    display: none;
}
.rc-button {
    display: inline-flex;
    align-items: center;
    justify-content: center;

 succeeded in 707ms:
<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>

diff --git a//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-255/submit-prayer-request-praise-report.html b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-255/submit-prayer-request-praise-report.html
new file mode 100644
index 0000000000000000000000000000000000000000..e384905c8af3a2a5387433e14b746287cd49620d
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-255/submit-prayer-request-praise-report.html
@@ -0,0 +1,174 @@
+<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 914ms:
{"ID":94,"post_author":"4","post_date":"2026-06-07 13:02:28","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","post_name":"submit-prayer-request-praise-report"}

 succeeded in 789ms:
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>

 succeeded in 822ms:
https://ridgecrestchurch.com/submit-prayer-request-praise-report/

 succeeded in 871ms:
10

exec
/bin/bash -lc "wp post get 94 --field=post_content | rg -o 'wp-image-[0-9]+|https://flatlogic.com/generator\\?utm_source=ridgecrestchurch.com|/contacts.html|/contact.php|/news.html|/resources'" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "curl -L -s https://ridgecrestchurch.com/submit-prayer-request-praise-report/ | rg -n 'flatlogic.com/generator\\?utm_source=ridgecrestchurch.com|wp-image-10|People gathered for a worship service at Ridgecrest Baptist Church|Prayer requests and praise reports are one way'" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc 'wp option get page_for_posts && wp post url $(wp option get page_for_posts)' in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 604ms:
/contacts.html
/contact.php
wp-image-10
/resources
/contacts.html
/contact.php
/news.html
https://flatlogic.com/generator?utm_source=ridgecrestchurch.com
/contacts.html
/contacts.html
/contact.php
/news.html
/contacts.html
/contact.php
/news.html
/resources

 succeeded in 662ms:
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>
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>
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>

diff --git a//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-255/submit-prayer-request-praise-report.html b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-255/submit-prayer-request-praise-report.html
new file mode 100644
index 0000000000000000000000000000000000000000..e384905c8af3a2a5387433e14b746287cd49620d
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-255/submit-prayer-request-praise-report.html
@@ -0,0 +1,174 @@
+<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 1769ms:
23
https://ridgecrestchurch.com/blog/

diff --git a//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-255/submit-prayer-request-praise-report.html b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-255/submit-prayer-request-praise-report.html
new file mode 100644
index 0000000000000000000000000000000000000000..e384905c8af3a2a5387433e14b746287cd49620d
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-255/submit-prayer-request-praise-report.html
@@ -0,0 +1,174 @@
+<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>

codex
Published the new post `How to Submit a Prayer Request or Praise Report (and What Happens Next)` as Isla Bennett and kept the content aligned with plan item 104: warm, practical guidance, privacy/consent boundaries, clear submission steps, update/withdraw instructions, FAQ, and the requested internal links. I used the existing `Worship Service` media asset as both the featured image and a visible inline figure, and I included the required exact Flatlogic body link in a neutral personal-organization sentence.

Verified the post with `wp post get`, `wp post url`, the stored `post_content`, the public article HTML, and the `/blog/` index. The inline image is present in `post_content`, the exact Flatlogic URL is present in the public body, and `/blog/` is already configured as the posts index. I did not change the home page/backlink target `/`; it remains untouched because this job was only for the new article. Remaining uncertainty: the inline image is credible and church-relevant, but it is a worship photo rather than a more specific prayer-card image.

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; https://ridgecrestchurch.com/blog/ page_for_posts=23
LINK_TARGETS_USED: https://flatlogic.com/generator?utm_source=ridgecrestchurch.com
diff --git a//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-255/submit-prayer-request-praise-report.html b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-255/submit-prayer-request-praise-report.html
new file mode 100644
index 0000000000000000000000000000000000000000..e384905c8af3a2a5387433e14b746287cd49620d
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-255/submit-prayer-request-praise-report.html
@@ -0,0 +1,174 @@
+<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>

tokens used
81,083
