OpenAI Codex v0.123.0 (research preview)
--------
workdir: /home/ubuntu/apps/ridgecrestchurch.com
model: gpt-5.4-mini
provider: openai
approval: never
sandbox: danger-full-access
reasoning effort: none
reasoning summaries: none
session id: 019ef5bf-3695-7880-8049-d3fcbf48bd7d
--------
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-506/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)

## Optional Flatlogic/AppWizzy Body Link Target

1. https://flatlogic.com/build/insurance-claims-management-software-builder?utm_source=ridgecrestchurch.com
   Title: Insurance Claims Management Software Builder | Flatlogic
   Priority: 1000000
2. https://flatlogic.com/build/legal-case-management-software-builder?utm_source=ridgecrestchurch.com
   Title: Legal Case Management Software Builder | Flatlogic
   Priority: 1000000
3. https://flatlogic.com/blog/ai-web-app-builders-production-is-the-bottleneck/?utm_source=ridgecrestchurch.com
   Title: AI Web App Builders Made Building Easy, Production Is the Bottleneck - Flatlogic Blog
   Priority: 1000000
4. https://flatlogic.com/blog/are-ai-web-builders-the-new-website-templates/?utm_source=ridgecrestchurch.com
   Title: Are AI Web Builders Becoming the New Website Templates? - Flatlogic Blog
   Priority: 1000000
5. https://flatlogic.com/generator?utm_source=ridgecrestchurch.com
   Title: AI Web Application Generator & App Builder | Flatlogic
   Priority: 1
   Anchor guidance: link to this page as: "web app generator", "AI web app generator", "web app builder", "AI web app builder", etc

Link placement requirement:

- Use at most one of the exact URLs above as a visitor-facing contextual body link inside the article content.
- Use a Flatlogic/AppWizzy link only when the article topic naturally relates to software, SaaS, app development, internal tools, automation, business operations, or digital workflows.
- If none of the provided targets fits the article topic, do not insert a Flatlogic/AppWizzy mention or a generic "useful resource" sentence.
- Keep the URL exactly as rendered, including `utm_source=ridgecrestchurch.com` for Flatlogic URLs.
- Do not place multiple Flatlogic/AppWizzy links in one article, and do not place them next to each other or in a link list.
- Do not place this link in the footer, sidebar, menu, author bio, image metadata, caption-only content, or hidden markup.
- Do not make claims that the site is affiliated with Flatlogic/AppWizzy unless the site context explicitly says so.
- Mention Flatlogic/AppWizzy only in neutral third-person language. Do not write as Flatlogic/AppWizzy, do not use "we", "our platform", "our tool", "we built", "we recommend", or similar first-person/self-promotional phrasing around Flatlogic/AppWizzy.
- Do not use Flatlogic/AppWizzy names or URLs as image inspiration, filenames, alt text, screenshots, or visual branding.

## Article Request

- Topic: How to Prepare a Prayer Request for Ridgecrest (A Simple, Respectful Template)
- WordPress post status: publish
- Planned publication time: None.
- Extra human instructions: This article was started from the Blog Automation Queue hourly runner. Use ARTICLE_CONTENT_PLAN.md plan item ID 112 as the source of truth. Prepared article brief: Working title: How to Prepare a Prayer Request for Ridgecrest (A Simple, Respectful Template)
Slug hint: how-to-prepare-prayer-request-template
Meta description: Learn how to write a meaningful prayer request for Ridgecrest Baptist Church with this practical template and guidance.

Reader intent:
Help readers write a meaningful prayer request quickly and appropriately, and understand what happens after they submit it.

Thesis:
Providing a clear template and do/don’t guidance will empower church members to submit prayer requests that are respectful and easy for the church to respond to.

Writer brief:
Create a practical guide that helps readers understand how to prepare a prayer request for Ridgecrest Baptist Church. The article should be structured to provide a clear template and specific do’s and don’ts to ensure requests are respectful and effective. Emphasize clarity and appropriateness in communication.

Author voice notes:
Maintain a strategic and pragmatic tone throughout the article. Focus on clarity and actionable guidance. Use concise language and avoid overly emotional expressions. Keep the reader grounded in practical steps they can take.

Key takeaways:
- Understanding the importance of context in prayer requests
- A copy/paste template for easy submission
- Essential do's and don'ts for writing requests
- Guidance on phrasing requests for healing or support
- Instructions on submission and what to expect afterwards

Outline:
1. Why We Ask for a Little Context
   Purpose: Explain the importance of providing context in prayer requests for effective prayer support.
  - Helps the prayer team pray specifically
  - Ensures requests are handled appropriately
  - Builds a sense of community and support
2. A Quick Template You Can Copy/Paste
   Purpose: Provide a practical template for readers to use when submitting their requests.
  - Name: [Your Name]
  - Request: [Brief description of your request]
  - Details: [Any specific details to include]
  - Timeframe: [When you need support]
  - Ongoing vs. One-time: [Specify if this is a recurring request]
  - Sharing Preference: [Public or private prayer]
3. Do Include:
   Purpose: List the essential elements that should be included in a prayer request.
  - Clarity in the request
  - Specific needs and relevant dates
  - Confidentiality preferences
4. Don’t Include:
   Purpose: Highlight what should be avoided in prayer requests.
  - Overly personal details
  - Anything uncomfortable to share publicly
5. If You’re Requesting Healing, Guidance, or Comfort
   Purpose: Provide example prompts for wording requests in sensitive situations.
  - Use compassionate language
  - Be clear about the type of support needed
  - Examples of phrasing requests
6. If You’re Submitting for Someone Else
   Purpose: Guide readers on how to phrase requests for others while respecting their privacy.
  - Mention the relationship to the person
  - Ensure consent is obtained before submitting
7. Sharing Preferences
   Purpose: Explain the difference between public prayer and private requests.
  - What to choose based on comfort level
  - Implications of each choice
8. How to Submit
   Purpose: Direct readers on how to submit their prayer requests and what to expect afterwards.
  - Link to the church’s prayer request/contact path
  - Outline the process after submission
  - Encouragement to keep praying while waiting
9. Closing: Encouragement
   Purpose: Provide a final note of encouragement to readers.
  - Reinforce the importance of prayer
  - Encourage ongoing communication with the church

Internal link plan:
- /contacts.html: Direct readers to the contact page for more information.
- /contact.php: Provide an alternative contact method for prayer requests.
- /contact.htm: Ensure all contact options are available.
- /news.html: Link to updates that may be relevant to prayer requests.
- /resources: Guide readers to additional resources for prayer and support.

Image direction:
A real photo of a person writing on a notepad or using a phone to draft a message (generic, non-identifying), plus a small inset photo of an open Bible or a prayer journal on a table.

Must include:
- Clear template for prayer requests
- Do's and Don'ts for effective communication
- Instructions on how to submit requests

Avoid:
- Duplicating content from the planned 'How to Submit a Prayer Request or Praise Report (and What Happens Next)' article
- Guaranteeing response times or specific outcomes
- Including unverifiable claims about who will see the request

Quality checklist:
- Ensure clarity and conciseness in language
- Maintain a respectful tone throughout
- Follow the structured outline closely
- Include actionable steps for the reader Article kind: evergreen Research status: not_required Reader intent: Help readers write a meaningful prayer request quickly and appropriately, and understand what happens after they submit it. Planned outline: Why we ask for a little context (so our prayer team can pray specifically) | A quick template you can copy/paste (Name, Request, Details, Timeframe, Ongoing vs. one-time, Sharing preference) | Do include: clarity, specific needs, relevant dates, and whether it’s confidential | Don’t include: overly personal details, anything you’re not comfortable sharing publicly | If you’re requesting healing, guidance, or comfort: example prompts for wording | If you’re submitting for someone else: how to phrase relationship and consent | Sharing preferences: public prayer vs. private request (what to choose) | How to submit (link to the church’s prayer request/contact path) and what to expect after you send it | Closing: encouragement and how to keep praying while you wait Image direction: A real photo of a person writing on a notepad or using a phone to draft a message (generic, non-identifying), plus a small inset photo of an open Bible or a prayer journal on a table. Preferred internal links: /contacts.html, /contact.php, /contact.htm, /news.html, /resources Avoid: Duplicate the planned “How to Submit a Prayer Request or Praise Report (and What Happens Next)” topic, Guarantee response times or specific outcomes, Include any unverifiable claims about who will see the request or how quickly it will be prayed over

## Selected Article Content Plan Item

- Plan item ID: 112
- Plan order: 22
- Article kind: evergreen
- Planned title: How to Prepare a Prayer Request for Ridgecrest (A Simple, Respectful Template)
- Slug hint: how-to-prepare-prayer-request-template
- Reader intent: Help readers write a meaningful prayer request quickly and appropriately, and understand what happens after they submit it.
- Angle: Provide a clear, practical template and do/don’t guidance so people know what to include and how to phrase requests in a way that’s easy for the church to respond to.
- Image direction: A real photo of a person writing on a notepad or using a phone to draft a message (generic, non-identifying), plus a small inset photo of an open Bible or a prayer journal on a table.
- Author hint: Use the selected virtual author.

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

Outline:
- Why we ask for a little context (so our prayer team can pray specifically)
- A quick template you can copy/paste (Name, Request, Details, Timeframe, Ongoing vs. one-time, Sharing preference)
- Do include: clarity, specific needs, relevant dates, and whether it’s confidential
- Don’t include: overly personal details, anything you’re not comfortable sharing publicly
- If you’re requesting healing, guidance, or comfort: example prompts for wording
- If you’re submitting for someone else: how to phrase relationship and consent
- Sharing preferences: public prayer vs. private request (what to choose)
- How to submit (link to the church’s prayer request/contact path) and what to expect after you send it
- Closing: encouragement and how to keep praying while you wait

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

Avoid:
- Duplicate the planned “How to Submit a Prayer Request or Praise Report (and What Happens Next)” topic
- Guarantee response times or specific outcomes
- Include any unverifiable claims about who will see the request or how quickly it will be prayed over

Content plan rules:

- If a selected content plan item is provided, write that specific planned article.
- Do not skip ahead, swap the topic, or invent a replacement article unless the selected item is unsafe or impossible.
- Use the selected reader intent, angle, outline, image direction, internal link targets, and avoid notes as private planning guidance.
- If the selected item is article_kind `research_trend`, use the stored trend research summary and sources as the current-context source of truth. Do not invent fresh news claims or fake citations beyond those sources.
- Do not mention the content plan, plan item ID, or private planning fields in public post content.

## Virtual Author

Write as this virtual author persona:

Name: Marcus Reed
Slug: marcus-reed
Role: Business web strategy editor
Language: English
Public bio: Marcus writes about website strategy, online operations, and the practical choices small businesses make when their web presence needs to grow up.
Character formula: Business Ruler Sage
Formula: Ruler + Sage
Meaning: A pragmatic strategic voice for business owners who need priorities, positioning, and operational direction.
Worldview: A mature web presence is a system of priorities, trust signals, operations, and business tradeoffs.
Voice guidance: Strategic, pragmatic, concise, priority-driven. Focus on decisions, sequencing, outcomes, and management clarity.
Humor: Dry businesslike humor, used sparingly.
Shadow tension: Can sound too executive or cold; keep the reader practical and grounded.
Usage notes: Best for web strategy, service positioning, operational planning, and business website growth.
Archetype blend: Ruler + Sage
Standard archetype voice guidance:

Primary archetype card: Ruler
Meaning: The authority figure who represents order, control, responsibility, and legacy.
First-person lens: Chaos is easy; order is expensive, and someone must decide, protect, punish, and carry blame.
Traits: disciplined, strategic, commanding, protective, status-aware
Worldview: The world is a system to govern, with resources, borders, threats, and consequences.
Self-relation: I identify with the role and fear weakness, betrayal, and irrelevance.
Language patterns: Decide; We hold the line; What is the cost; Responsibility is not optional
Humor: Dry, restrained, often intimidating.
Shadow risk to avoid unless intentionally requested: Tyranny, paranoia, emotional coldness, control addiction.

Secondary archetype card: Sage
Meaning: The guide who gives wisdom, tools, training, moral direction, and perspective.
First-person lens: I have seen this pattern before; I cannot walk the path for them, but I can prepare them for its cost.
Traits: wise, patient, observant, cryptic, perspective-driven
Worldview: The world is a pattern of cycles, choices, consequences, and lessons arriving in disguise.
Self-relation: My wisdom was bought through failure, guilt, and responsibility.
Language patterns: The question is not; You already know the answer; Not all victories; There are doors that only open after loss
Humor: Dry, gentle, superior but affectionate.
Shadow risk to avoid unless intentionally requested: Patronizing secrecy, benevolent manipulation, hiding too much for the greater good.
Shadow tension: Can sound too top-down; should respect small-team constraints and avoid boardroom theater.
Worldview: A website is not decoration; it is part of the operating system of a business.
Reader relationship: Pragmatic advisor helping the reader make cleaner business decisions.
Humor style: Restrained, dry, usually one sentence to puncture vague business language.
Voice traits: strategic, concise, pragmatic, priority-driven
Vocabulary / recurring language: priority, business case, operational cost, signal, decision point
Avoid voice: corporate jargon fog, growth-hack cliches, fake executive experience, overconfident ROI claims
CTA style: Direct the reader toward a concrete business decision: audit, prioritize, simplify, or ask for a quote.
Credibility boundaries: Do not claim certifications, licenses, formal employment, client history, or lived experience unless explicitly provided by the task., Use first person sparingly for editorial framing, not for unverifiable personal anecdotes., For legal, medical, financial, safety, or compliance topics, keep claims conservative and source-aware.
Personality: Strategic, concise, pragmatic, and focused on what actually moves the business forward.
Writing style: Executive summaries, priority lists, strategic framing, cost-of-delay thinking, and clear do-this-next endings.
Expertise topics: business websites, web strategy, service positioning, hosting decisions, operational planning
Avoid topics: financial projections, legal advice, investment advice, guaranteed growth claims
Tone tags: strategic, pragmatic, direct, businesslike
Private operator notes: Useful for business strategy, service landing support articles, and practical management content.

Rules for the author:

- Use the author's voice, mood, pacing, and style.
- Treat archetype fields as private writing guidance. Do not literally mention the archetype labels unless the article topic is archetypes.
- Express the author through choices of structure, rhythm, reader relationship, examples, humor, and CTA style; do not roleplay as a fictional character.
- Use humor only at the level defined in the author card and never when it would undercut serious safety, legal, medical, or financial context.
- Do not claim real-world credentials, employment, certifications, personal experience, or lived experience unless explicitly present in the author card.
- Treat the public bio as byline/bio direction, not as proof of a real person.
- Follow the author credibility boundaries and avoid-voice list.
- Respect avoid topics and site safety/context rules.

## WordPress Implementation Requirements

- Use `wp-cli` for WordPress changes.
- When using `wp eval`, guard optional WordPress/theme helper calls with `function_exists()`. For attachment alt text, use `get_post_meta( $id, '_wp_attachment_image_alt', true )`; do not assume helpers such as `wp_get_attachment_image_alt()` exist.
- Create or reuse a WordPress user for this author when practical.
- Suggested `user_login`: `marcus-reed`.
- Suggested `display_name`: `Marcus Reed`.
- Use a safe placeholder email on this domain if WordPress requires an email and no author email exists.
- Create a new WordPress `post`, not a page.
- Set the post status to `publish`.
- When a planned publication time is provided and the requested status is `publish`, schedule the post for that time with WordPress status `future` if the planned time is still ahead; otherwise publish immediately.
- Assign the post to the author user when practical.
- Ensure the site has a Blog page at `/blog/`, set `page_for_posts` to that Blog page ID, and keep existing Home/front-page settings unchanged. Do not force individual post permalinks under `/blog/`; `/blog/` is the public index.
- Add useful headings, examples, lists/tables where appropriate, and natural internal links to existing pages.
- Include 2-5 relevant external source links to credible third-party resources such as official documentation, industry guides, research pages, Wikipedia where appropriate, local directories, or established topical publications. Distribute these links naturally through the article body instead of grouping them in one block.
- Append `utm_source=ridgecrestchurch.com` to every third-party external source link you add. If the URL already has query parameters, append it with `&utm_source=ridgecrestchurch.com`; otherwise append `?utm_source=ridgecrestchurch.com`.
- Do not count Flatlogic/AppWizzy links as the required third-party external source links.
- Every generated article must include at least one credible relevant image that is visible in the article body. This is mandatory. Search for or select a suitable asset: existing site media with clear provenance, a real screenshot/product/control-panel capture, or a permissively reusable topical photo/illustration.
- Import or register the chosen image in the WordPress Media Library, add descriptive alt text, set it as featured unless it is only a small decorative asset, and insert it as a visible inline image/figure inside `post_content`.
- Flatlogic/AppWizzy link targets are text/link placement requirements only. Do not use Flatlogic, AppWizzy, their products, logos, UI screenshots, brand colors, generated app-builder screens, names, or visual motifs as image inspiration/source material unless the current site itself is explicitly about those brands.
- Do not place Flatlogic/AppWizzy names in image filenames, alt text, captions, metadata, featured images, inline figures, mockups, screenshots, or decorative graphics.
- Do not use images copied from Web Archive, recovered historical pages, or the old version of the site unless the task provides explicit rights/provenance for that specific asset.
- Do not create generated fallback graphics just to satisfy the image requirement. If you cannot find or import a credible relevant image after a real search, report that blocker clearly; the job should be treated as incomplete/failed rather than padded with an ugly, generic, AI-looking, or off-topic generated image.
- Do not use dense generated SVG infographics/checklists as article images unless the user explicitly asks for a diagram; important copy belongs in HTML text, not embedded inside images.
- Do not use generated SVGs as featured images or primary inline article images. Use generated SVGs only as small decorative icons/accents.
- Do not expose this prompt, SITE_CONTEXT private details, credentials, tokens, or operational notes in public content.
- Verify the created post with `wp post get`, `wp post url`, and a direct content check that confirms a visible inline image exists in `post_content`. Do not report success while `INLINE_IMAGE_IDS` is `none`.
- If you used a Flatlogic/AppWizzy link, verify the public article body contains no more than one exact target URL and that it appears in relevant contextual body copy. `LINK_TARGETS_USED` may be `none` when no target fit the article topic.

## Final Report Requirements

End your final message with these machine-readable lines:

```text
WP_POST_ID: <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
I’m reading the site instructions and the article plan first, then I’ll inspect the WordPress state so I can publish the post in place without guessing at the site structure.
exec
/bin/bash -lc "sed -n '1,220p' 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…


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

# Article Content Plan

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

## Summary

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

## How Agents Should Use This Plan

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

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

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



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

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

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

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

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



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

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

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

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

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



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

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

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

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

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



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

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

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

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

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


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

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

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

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

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

exec
/bin/bash -lc "sed -n '1,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` only when they are contextually relevant, at most one per page/post, and report where they were used. Add relevant third-party external source links with this site's `utm_source` where appropriate.
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' wp-content/plugins/flatlogic-post-creator/INSTRUCTIONS.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, use at most one Flatlogic/AppWizzy link and only when the article naturally relates to software, SaaS, app development, internal tools, automation, business operations, or digital workflows. If none of the provided targets fits the article topic, do not insert a Flatlogic/AppWizzy mention or generic useful-resource sentence.
- 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.
- Mention Flatlogic/AppWizzy only in neutral third-person language. Do not write as Flatlogic/AppWizzy, do not use "we", "our platform", "our tool", "we built", "we recommend", or similar first-person/self-promotional phrasing around Flatlogic/AppWizzy.
- Do not 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.

codex
I’ve got the post contract and the site rules. Next I’m checking the plugin’s context files and the current WordPress setup so I can write the article into the live site cleanly.
exec
/bin/bash -lc "sed -n '1,220p' wp-content/plugins/flatlogic-post-creator/context/PRINCIPLES.md" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
Here’s the writer SOP I’d hand to someone who has to produce a serious, quotable article.

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

## Operating definitions

Use these before you write a word.

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

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

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

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

My recommended floor for a serious non-breaking article:

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

That is my operating minimum, not a universal law.

---

## 1. Why this story exists

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

### 1.1 Ask

Write down answers to these, in one sentence each:

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

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

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

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

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

### 1.2 Write

Create a 5-line assignment brief:

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

### 1.3 Produce

A one-sentence story brief:

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

### 1.4 Gate

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

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

Kill or reframe.

---

## 2. Convert the topic into a question tree

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

### 2.1 Ask

Turn the topic into a precise question.

Bad:

* “AI code editors vs traditional IDEs”

Better:

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

### 2.2 Build the tree

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

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

### 2.3 Write two counterweights

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

Example:

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

### 2.4 Gate

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

---

## 3. Build the evidence matrix before collecting facts

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

### 3.1 Create a matrix

Make a table or spreadsheet with these columns:

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

### 3.2 Use a source hierarchy

Rank sources like this:

**Tier A — primary**

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

**Tier B — on-record participants**

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

**Tier C — independent interpreters**

* analysts
* academics
* domain experts
* critics

**Tier D — secondary synthesis**

* other articles
* industry reports
* commentary

### 3.3 Use a support rule

My recommended rule for each material claim:

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

### 3.4 Gate

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

---

## 4. Scan the field and locate the gap

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

### 4.1 Search in this order

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

### 4.2 For each existing article, extract

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

### 4.3 Produce a “gap memo”

Write 5 bullets:

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

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

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

Article Title Checklist
Keep titles about 55-60 characters long
Use target keywords in titles
Use numbers in titles (e.g. “5 ways to…”, “Top 10…”, etc.) where possible.
Use words like HOW, WHY, WHAT, and WHERE – help people understand what they will find on the page
Use words like BEST, TOP, ULTIMATE; GUIDE, REVIEW, TUTORIAL – to entice users to click
Write unique titles, no duplicates!
Article Structure
1. Intro is important
   Here you identify the core problem and the theme of the article. Then, clarify the neutral solution path or options the article will cover. There must be a link between “the pain” and the proposed solution direction.
   The intro must include at least 2 references to authoritative sources that confirm 1) the existence of the problem and 2) the rationale for the proposed solution direction. (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 credible third-party sources or relevant case studies – at least 2 (with links)
   The text includes relevant internal links only when they are useful for the reader and naturally fit the article topic
   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 "find wp-content/plugins/flatlogic-post-creator/context -maxdepth 1 -type f -name '*.md' | sort" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
wp-content/plugins/flatlogic-post-creator/context/PRINCIPLES.md

exec
/bin/bash -lc 'wp core is-installed && wp option get home && wp option get siteurl && wp theme list --status=active --fields=name,status && wp db prefix && wp post list --post_type=post --fields=ID,post_title,post_name,post_status --format=table' in /home/ubuntu/apps/ridgecrestchurch.com
codex
The site is installed and the active theme is up. I’m now checking the existing pages, media library, and blog index so I can reuse what’s already there instead of inventing new structure.
exec
/bin/bash -lc 'wp option get page_for_posts && wp option get show_on_front && wp option get page_on_front' 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,post_status --format=table' 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 712ms:
ID	post_title	post_name	post_mime_type	post_status
114	Sunday Meet and Greet Volunteers	sunday-meet-and-greet-volunteers	image/jpeg	inherit
89	Wednesday Night Kids Check-In Scene	wednesday-night-kids-check-in-scene	image/jpeg	inherit
86	Ridgecrest Events Calendar Page Screenshot	ridgecrest-events-calendar-page-screenshot	image/png	inherit
79	Ridgecrest Website Navigation Screenshot	ridgecrest-website-navigation-screenshot	image/png	inherit
76	Sunday Service Planning Desk	sunday-service-planning-desk	image/jpeg	inherit
1	Ridgecrest Baptist Church Logo	ridgecrest-baptist-church-logo	image/gif	inherit
2	Ridgecrest Service Times	ridgecrest-service-times	image/gif	inherit
3	Ridgecrest Events Calendar	ridgecrest-events-calendar	image/gif	inherit
4	Ridgecrest Connection Graphic	ridgecrest-connection-graphic	image/gif	inherit
5	Ridgecrest Sermons Graphic	ridgecrest-sermons-graphic	image/gif	inherit
6	Ridgecrest Contact Graphic	ridgecrest-contact-graphic	image/gif	inherit
7	Ridgecrest Map Graphic	ridgecrest-map-graphic	image/gif	inherit
8	Ridgecrest Community Illustration	ridgecrest-community-illustration	image/jpeg	inherit
9	Ridgecrest Main Entrance	church-exterior	image/jpeg	inherit
10	Worship Service	worship-service	image/jpeg	inherit
11	Children Ministry	children-ministry	image/jpeg	inherit
12	Youth Worship	youth-worship	image/jpeg	inherit

 succeeded in 718ms:
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 648ms:
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
8	june-park	June Park	june-park@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

 succeeded in 1889ms:
23
page
13

 succeeded in 15335ms:
https://ridgecrestchurch.com
https://ridgecrestchurch.com
name	status
church	active
flbg_
ID	post_title	post_name	post_status
113	Ministry Spotlight: How Our Teams Serve on Sundays (Greeters, Ushers, and Hospitality)	ministry-spotlight-sunday-teams	publish
112	How to Plan Your Week Around Church (Sunday-Wednesday Rhythm at Ridgecrest)	how-to-plan-your-week-around-church-sunday-wednesday-rhythm	publish
109	Ridgecrest Baptist Church Events FAQ: Times, Arrival, Seating, and Kids Check-In	ridgecrest-baptist-church-events-faq	publish
94	How to Submit a Prayer Request or Praise Report (and What Happens Next)	submit-prayer-request-praise-report	publish
93	Church Resources for New Families: Where to Start This Week	church-resources-for-new-families	publish
91	What to Bring (and Wear) to Church at Ridgecrest: A Practical Guide for Sundays	what-to-bring-and-wear-to-church-ridgecrest	publish
88	How to Prepare for a Youth or Kids Wednesday Night Program	prepare-for-wednesday-kids-youth	publish
87	How to Use Our Events Calendar: RSVP, Reminders, and What to Bring	how-to-use-events-calendar-rsvp-reminders-what-to-bring	publish
80	What to Expect at Ridgecrest Baptist Church (Visitor-Friendly Guide)	what-to-expect-ridgecrest-baptist-church	publish
78	How to Get Involved at Ridgecrest: A First-Timer’s Guide to Ministries, Kids, and Youth	get-involved-first-timers-guide	publish
77	How to Plan a Great Sunday: A Simple Church Service Checklist	how-to-plan-a-great-sunday-checklist	publish
74	How to Plan Your First Visit to Ridgecrest Baptist Church	first-visit-ridgecrest-baptist-church	publish
51	Welcome to Ridgecrest News	welcome-to-ridgecrest-news	publish

codex
The blog index is already in place, so I can focus on the article itself. I’m checking categories and the available image assets now, then I’ll draft the post and attach a real inline image from the library.
exec
/bin/bash -lc 'wp term list category --fields=term_id,name,slug,count --format=table' in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "wp eval 'if (function_exists(\"wp_get_attachment_image_src\")) { foreach ([76,79,86,89,114,8,9,10,11,12] as "'$id) { $img = wp_get_attachment_image_src($id, "full"); if ($img) { echo $id . "|" . $img[0] . "|" . $img[1] . "x" . $img[2] . PHP_EOL; } } }'"'" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "wp eval 'foreach ([76,79,86,89,114,8,9,10,11,12] as "'$id) { $p = get_post($id); if ($p) { $file = get_attached_file($id); $alt = get_post_meta($id, "_wp_attachment_image_alt", true); echo $id . "|" . $p->post_title . "|" . $file . "|" . $alt . PHP_EOL; } }'"'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 517ms:
term_id	name	slug	count

 succeeded in 540ms:
76|https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg|0x0
79|https://ridgecrestchurch.com/wp-content/uploads/imports/ridgecrest-home-navigation-screenshot.png|0x0
86|https://ridgecrestchurch.com/wp-content/uploads/imports/events-calendar-page-screenshot.png|0x0
89|https://ridgecrestchurch.com/wp-content/uploads/imports/wednesday-night-kids-check-in-scene.jpg|0x0
114|https://ridgecrestchurch.com/wp-content/uploads/imports/review-fix/meet-greet-0038.jpg|0x0
8|https://ridgecrestchurch.com/wp-content/uploads/imports/groups.jpg|120x112
9|https://ridgecrestchurch.com/wp-content/uploads/imports/church-exterior.jpg|2250x1500
10|https://ridgecrestchurch.com/wp-content/uploads/imports/worship-service.jpg|4032x3024
11|https://ridgecrestchurch.com/wp-content/uploads/imports/children-ministry.jpg|4112x3088
12|https://ridgecrestchurch.com/wp-content/uploads/imports/youth-worship.jpg|5184x3888

 succeeded in 562ms:
76|Sunday Service Planning Desk|/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg|Planning materials on a desk with a calendar and smartphone for Sunday service coordination
79|Ridgecrest Website Navigation Screenshot|/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/ridgecrest-home-navigation-screenshot.png|Phone showing Ridgecrest Baptist Church website navigation
86|Ridgecrest Events Calendar Page Screenshot|/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/events-calendar-page-screenshot.png|Screenshot of the Ridgecrest Baptist Church Events Calendar page showing the weekly schedule and event sections
89|Wednesday Night Kids Check-In Scene|/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/wednesday-night-kids-check-in-scene.jpg|Children's ministry check-in area with volunteers helping families register before a program begins
114|Sunday Meet and Greet Volunteers|/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/review-fix/meet-greet-0038.jpg|Church volunteers welcoming and greeting attendees before a Sunday service
8|Ridgecrest Community Illustration|/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/groups.jpg|Illustration representing gathered church community
9|Ridgecrest Main Entrance|/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/church-exterior.jpg|Main entrance and covered walkway at Ridgecrest Baptist Church in Blanchard, Oklahoma
10|Worship Service|/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/worship-service.jpg|People gathered for a worship service at Ridgecrest Baptist Church
11|Children Ministry|/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/children-ministry.jpg|Children participating in ministry activities at Ridgecrest Baptist Church
12|Youth Worship|/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/youth-worship.jpg|Students gathered for youth worship

codex
I found a strong candidate asset already in the library: a planning desk with a calendar and smartphone. I’m doing one more scan for anything even closer to a prayer journal or Bible image before I lock the article artwork.
exec
/bin/bash -lc "find wp-content/uploads -type f \\( -iname '*bible*' -o -iname '*journal*' -o -iname '*prayer*' -o -iname '*notepad*' -o -iname '*notes*' -o -iname '*writing*' \\) | sort" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
wp-content/uploads/flatlogic-article-tasks/job-255/submit-prayer-request-praise-report.html

exec
/bin/bash -lc "wp post list --post_type=attachment --fields=ID,post_title,post_name --format=csv | rg -i 'bible|journal|prayer|notepad|desk|phone|paper|writing|notes'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 488ms:
76,"Sunday Service Planning Desk",sunday-service-planning-desk

codex
The only close asset match is the planning-desk photo, which is good enough for a “prepare your request” guide. I’m checking one existing task artifact now only to avoid accidentally echoing a near-duplicate structure, then I’ll write the new post.
exec
/bin/bash -lc "sed -n '1,240p' wp-content/uploads/flatlogic-article-tasks/job-255/submit-prayer-request-praise-report.html" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
<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>

exec
/bin/bash -lc 'wp post get 23 --fields=ID,post_title,post_name,post_status --format=json' in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 556ms:
{"ID":23,"post_title":"Blog","post_status":"publish","post_name":"blog"}

codex
I’ve got enough structure to write the article. Before I publish, I’m checking whether the legacy contact paths actually exist so I only link readers to routes that work.
exec
/bin/bash -lc "rg --files -g 'contact.php' -g 'contact.htm' -g 'contacts.html' -g 'news.html' -g 'resources'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
wp-content/plugins/internal-links/vendor/freemius/wordpress-sdk/templates/forms/deactivation/contact.php
wp-content/plugins/internal-links/vendor/freemius/wordpress-sdk/templates/contact.php
wp-content/plugins/internal-links-premium/vendor/freemius/wordpress-sdk/templates/forms/deactivation/contact.php
wp-content/plugins/internal-links-premium/vendor/freemius/wordpress-sdk/templates/contact.php

exec
/bin/bash -lc "wp eval 'foreach ([\"/contact.php\",\"/contact.htm\",\"/contacts.html\",\"/news.html\",\"/resources\"] as "'$path) { $page = url_to_postid(home_url($path)); echo $path . "|" . $page . PHP_EOL; }'"'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 548ms:
/contact.php|0
/contact.htm|0
/contacts.html|0
/news.html|0
/resources|22

codex
The legacy paths aren’t mapped in WordPress, so I’m verifying whether they still resolve at the web server level before I decide whether to use them or the current page slugs.
exec
/bin/bash -lc 'curl -I -L --max-redirs 3 https://ridgecrestchurch.com/contacts.html' in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc 'curl -I -L --max-redirs 3 https://ridgecrestchurch.com/contact.php' in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc 'curl -I -L --max-redirs 3 https://ridgecrestchurch.com/news.html' in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 506ms:
  0     0    0  HTTP/2 301 
date: Tue, 23 Jun 2026 18:31:20 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=i%2FiqyTaSUySCEU7DafRCCE%2Fkar4w%2B%2ByvFmEndHfeiHD0bIKSKQ1jmIvy14gPW7iDVLaGpO%2BcjYtFLehXwQg8YOWmtNFRksTw%2F8ihuZcBW8hkT86IIn%2FMk6efkV5c4Ogy5nJSv37iuw%3D%3D"}]}
nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
cf-ray: a10591b14e21b813-WAW
alt-svc: h3=":443"; ma=86400

HTTP/1.1 200 OK
Date: Tue, 23 Jun 2026 18:31:21 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=3qR85a0WDzkAoPi%2FvbzuKPE3xNg%2BFLPuo5mzQTj1CIdgqghoVDnHU7iq0pj6tIHcD2OU9EMLEBCAv%2FFsUqba4UJSx1FvKvQ0%2Fro7Dh8Hn0tWpllyfICzbgV1UtJtS%2BFs1aYcmyUBdw%3D%3D"}]}
Nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
CF-RAY: a10591b1ad8f89fe-WAW
alt-svc: h3=":443"; ma=86400

   0    0     0      0      0 --:--:-- --:--:-- --:--:--     0  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0

 succeeded in 481ms:
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:-- HTTP/2 301 
date: Tue, 23 Jun 2026 18:31:20 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=ISLmDH%2FdrpTr%2BRBKYSZtSJU7HNt6kmsUoYu0HPwNwhekb%2FXaiBh%2BY1VIbiFPYUC%2FvpSWTauP%2BJaxMS0B4NxVwc43x6rkfo2tJlgVLBDO3LcLiafN7ISVotEIjhL6NAVqbI%2BfoPtBqw%3D%3D"}]}
nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
cf-ray: a10591b2088a70c1-WAW
alt-svc: h3=":443"; ma=86400

HTTP/1.1 200 OK
Date: Tue, 23 Jun 2026 18:31:21 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=rDr7m22Kk9zFaQZocGbLgeXsxuh23aOUZAMLmFdWMC7SA6FsIcweRvDg0GrwZmMSWgAT8ftih0F%2BjEtU4PUNv6S4if4eN%2BH5TGNsmt3aQPa9JUR8KzsWhqzVu7T%2BLNCl0kZPvJJQTQ%3D%3D"}]}
Nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
CF-RAY: a10591b26f7689fe-WAW
alt-svc: h3=":443"; ma=86400

    0

 succeeded in 516ms:
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     HTTP/2 301 
date: Tue, 23 Jun 2026 18:31:20 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=aLoZVm8x6%2FrebcGwzTsdX%2B5NNCt%2BuHqfe7gomdk589vJwgmCh2Rf5ZiBkrqxijTtOh5WpfFh%2BSO%2FZA5JRbi45vV4NellhSDlOgSKeiJgkvfarJRd%2BNrbPUTjU1%2BXF%2F%2B7eBSStT5utQ%3D%3D"}]}
nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
cf-ray: a10591b208b0c3b3-WAW
alt-svc: h3=":443"; ma=86400

HTTP/1.1 200 OK
Date: Tue, 23 Jun 2026 18:31:21 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=yckntBiHEAgulTliqscBd%2B%2BxgOPSppHNm10aGxHR92%2FblIVz%2BNRbr2NrLDJ7X8C9m7V9jiyW2PK0qSTzs3RsNsvY3k5zjrctg%2FmXT6qVocArDqqhgL%2B%2FvlfCSozJ9XZM9eS%2FPoibMA%3D%3D"}]}
Nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
CF-RAY: a10591b25d42bfda-WAW
alt-svc: h3=":443"; ma=86400

0

codex
The legacy contact and news URLs do redirect cleanly, so I can use them naturally in the article. I’m checking the chosen image file once before publishing so I don’t ship a broken visual.
exec
/bin/bash -lc 'curl -I https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg' in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0  0 58445    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
HTTP/2 200 
date: Tue, 23 Jun 2026 18:31:24 GMT
content-type: image/jpeg
content-length: 58445
accept-ranges: bytes
etag: "e44d-6519037fa4632"
last-modified: Mon, 11 May 2026 20:01:56 GMT
server: cloudflare
cache-control: max-age=14400
cf-cache-status: MISS
report-to: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=KnlbkQCtSNIEYrEXI9%2FkYSgaCeWq2P0u9cmJ%2F7hS7vs%2FLsrPjz03C8v74HAtwI4xSjjXsVQIrfsqmfgwgj2kfNnNSBXBoAEJV8mbYBEC1VxoueGKXs2hFPIC5GutPCndLZ%2FPg3VSqg%3D%3D"}]}
nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
cf-ray: a10591ca6b1af9da-WAW
alt-svc: h3=":443"; ma=86400


exec
/bin/bash -lc 'curl -I https://ridgecrestchurch.com/wp-content/uploads/imports/church-exterior.jpg' in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0  0 2775k    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
HTTP/2 200 
date: Tue, 23 Jun 2026 18:31:24 GMT
content-type: image/jpeg
content-length: 2841646
accept-ranges: bytes
etag: "2b5c2e-651370d8c1015"
last-modified: Thu, 07 May 2026 09:39:12 GMT
server: cloudflare
cache-control: max-age=14400
cf-cache-status: MISS
report-to: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=%2FGJbOK3ul0zTFsquW2FdCmsGzhwqLQmtTj5oDmBJUUDp0n1CGv%2FJ3BOHsie7DZiDnTcTMiV8Pq3O7OiwfIXjaSBnET%2BNmvUQC%2FSoTaASD4sAHhixHydvWITUi8djJKylo6sdjlFKwA%3D%3D"}]}
nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
cf-ray: a10591cb28d41170-WAW
alt-svc: h3=":443"; ma=86400


codex
I’m writing the article body now with the requested template, do/don’t guidance, and a visible inline image. I’m keeping the language practical and avoiding anything that would imply guaranteed handling or a fixed response time.
apply patch
patch: completed
/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html
diff --git a//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html
new file mode 100644
index 0000000000000000000000000000000000000000..8528939ff7211beb80e6eac7fe0a495ab02800ed
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html
@@ -0,0 +1,247 @@
+<p><strong><em>A prayer request does not need to sound polished. It needs to be clear enough for the church to pray without guessing.</em></strong></p>
+
+<p><strong>By Marcus Reed</strong> | Updated June 23, 2026</p>
+
+<p>When people sit down to write a prayer request, the same practical questions come up fast: How much context is enough? What should stay private? Can I ask for prayer for someone else? And how do I make the request easy for the church to read and use well?</p>
+
+<p>Those are good questions. Prayer is not a performance, and the Bible treats it that way. <a href="https://www.biblegateway.com/passage/?search=Philippians+4%3A6-7&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">Philippians 4:6-7</a> points toward honest, direct prayer; <a href="https://www.biblegateway.com/passage/?search=Matthew+6%3A6&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">Matthew 6:6</a> reminds believers that prayer can also be private and disciplined. A useful church request follows the same logic: enough context to be specific, enough restraint to protect what should stay private, and enough clarity that people can pray with purpose.</p>
+
+<p>If you want the shortest path, start with the church <a href="/contacts.html">Contacts</a> page, or use the site's <a href="/contact.php">contact form</a> if that is more convenient. If you are looking for broader church information while you prepare your message, the <a href="/resources">Resources</a> page is a good place to get oriented.</p>
+
+<figure class="wp-block-image size-large">
+  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg" alt="Planning materials on a desk with a calendar and smartphone for Sunday service coordination" class="wp-image-76" style="width:100%;height:auto;" />
+  <figcaption>A simple request starts with the same discipline as any good plan: enough detail to be useful, not so much that the point gets buried.</figcaption>
+</figure>
+
+<h2>Why We Ask for a Little Context</h2>
+
+<p>Prayer teams do better with signal than with noise. A short note that says what is happening, who it affects, and what kind of prayer is needed gives the church something concrete to carry. A vague request forces people to fill in the blanks, and that is where confusion starts.</p>
+
+<p>Context also helps the church handle requests appropriately. Some needs are fine to share broadly. Some should stay with a limited group. Some should be treated as private pastoral matters. The more clearly you state your preference, the less guesswork is required on the other side.</p>
+
+<p>There is a third reason, and it is the one people often skip: context respects the person who is asking for prayer. A request that is too thin can feel detached; a request that is too detailed can feel exposed. The goal is not to narrate your whole life. The goal is to give enough information for faithful prayer and responsible care.</p>
+
+<h2>A Quick Template You Can Copy and Paste</h2>
+
+<p>If you are not sure where to start, use this format. It is simple on purpose.</p>
+
+<pre><code>Name: [Your name]
+Request: [One short sentence about the need]
+Details: [Only the facts that help people pray well]
+Timeframe: [Today, this week, on [date], or ongoing]
+Ongoing vs. one-time: [One-time / recurring]
+Sharing preference: [Public / private / limited sharing]
+Contact: [Optional phone or email if a follow-up may help]</code></pre>
+
+<p>That is enough for most situations. If you need more privacy, leave out the contact line and keep the description general. If the request is for someone else, say so clearly in the first line so the church understands the relationship and the permission level.</p>
+
+<p>A few quick definitions help here:</p>
+
+<ul>
+  <li><strong>Public prayer:</strong> a request that can be shared more broadly with the church.</li>
+  <li><strong>Private request:</strong> a request that should stay with a smaller, limited group.</li>
+  <li><strong>Ongoing request:</strong> a situation that needs repeated prayer over time.</li>
+  <li><strong>Timeframe:</strong> when the need is happening or when support is most important.</li>
+</ul>
+
+<p>Think of the template as a floor, not a ceiling. You can always add a sentence, but you do not need to write a paragraph for every line. A church can work with a concise request. It cannot work with a mystery wrapped in spiritual language.</p>
+
+<h2>Do Include</h2>
+
+<p>The most useful prayer requests include the facts that actually help someone pray.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Include this</th>
+      <th>Why it helps</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>A clear request in one sentence</td>
+      <td>It tells the reader exactly what kind of prayer you are asking for.</td>
+    </tr>
+    <tr>
+      <td>Specific needs or concerns</td>
+      <td>“Healing,” “wisdom,” “travel safety,” or “comfort” are easier to pray for than a vague concern.</td>
+    </tr>
+    <tr>
+      <td>Relevant dates or timeframes</td>
+      <td>Dates help the church know what matters now, this week, or later.</td>
+    </tr>
+    <tr>
+      <td>Whether the request is confidential</td>
+      <td>Privacy preferences should be stated plainly, not left to interpretation.</td>
+    </tr>
+    <tr>
+      <td>Whether the request is ongoing</td>
+      <td>A continuing need may be placed on a prayer list differently from a one-time update.</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>One useful habit: write the request as if someone else has to read it once, understand it immediately, and pray right away. That is the operational standard. Church communication is not a scavenger hunt.</p>
+
+<p>Here are a few examples of good, concise wording:</p>
+
+<ul>
+  <li><strong>Healing:</strong> “Please pray for Sarah as she prepares for surgery on Thursday. We are asking for peace, skill for the medical team, and steady recovery.”</li>
+  <li><strong>Family support:</strong> “Please pray for our family during a difficult week. We need wisdom, patience, and rest.”</li>
+  <li><strong>Guidance:</strong> “Please pray for discernment as I make a work decision by the end of the month.”</li>
+  <li><strong>Comfort:</strong> “Please pray for comfort and strength after a recent loss. This can stay private.”</li>
+</ul>
+
+<p>Notice what is not happening there. There is no long backstory, no dramatic language, and no pressure to explain every detail. The request stays readable.</p>
+
+<h2>Don’t Include</h2>
+
+<p>Good judgment matters. A prayer request is not the right place for everything.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Leave this out</th>
+      <th>Why to avoid it</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Overly personal details</td>
+      <td>If it would make you uncomfortable to read out loud, it probably should not be in the request.</td>
+    </tr>
+    <tr>
+      <td>Information you do not have permission to share</td>
+      <td>Consent matters, especially when the request involves another person.</td>
+    </tr>
+    <tr>
+      <td>Long background narratives</td>
+      <td>The main need should stay visible. A request that rambles can hide the actual prayer point.</td>
+    </tr>
+    <tr>
+      <td>Unnecessary medical, family, or financial details</td>
+      <td>More detail is not always better. Sometimes it is just more detail.</td>
+    </tr>
+    <tr>
+      <td>Anything you are not comfortable sharing publicly</td>
+      <td>If it feels too exposed, mark it private or keep it brief.</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>If a detail does not help someone pray, leave it out. That is usually the right filter. The church does not need a case file. It needs enough context to respond with care.</p>
+
+<h2>If You Are Requesting Healing, Guidance, or Comfort</h2>
+
+<p>These are the situations where people often over-explain or under-explain. The middle path is usually best.</p>
+
+<p>For healing, say what kind of prayer is needed without turning the note into a medical summary. For guidance, name the decision and the deadline if there is one. For comfort, say what kind of support would be most helpful: peace, strength, patience, reassurance, or rest.</p>
+
+<p>You can borrow one of these patterns:</p>
+
+<ul>
+  <li><strong>Healing:</strong> “Please pray for healing and wise care as I recover from treatment this week.”</li>
+  <li><strong>Guidance:</strong> “Please pray for clarity as our family considers next steps for school and work.”</li>
+  <li><strong>Comfort:</strong> “Please pray for comfort, stability, and help with the next few days.”</li>
+  <li><strong>Strength:</strong> “Please pray for strength to stay steady through a difficult season.”</li>
+</ul>
+
+<p>If you want to keep a request private but still specific, say that directly:</p>
+
+<blockquote>
+  <p>“Please pray for healing for a family member this week. We are not ready to share details publicly, so please keep this private.”</p>
+</blockquote>
+
+<p>That kind of wording does two jobs at once. It gives the church a prayer focus and sets a boundary without making the request awkward.</p>
+
+<p>For a broader biblical frame, <a href="https://www.biblegateway.com/passage/?search=James+5%3A16&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">James 5:16</a> connects prayer with honest confession and mutual care. The point is not performance. The point is trust and clarity.</p>
+
+<h2>If You Are Submitting for Someone Else</h2>
+
+<p>People often ask for prayer on behalf of a spouse, child, parent, friend, or coworker. That is normal. The key is to say two things clearly: your relationship to the person and whether you have permission to share the request.</p>
+
+<p>Useful wording looks like this:</p>
+
+<ul>
+  <li><strong>With consent:</strong> “Please pray for my father, who gave me permission to share that he has a procedure next week.”</li>
+  <li><strong>Without detail:</strong> “Please pray for a friend who is facing a hard family situation.”</li>
+  <li><strong>For a child:</strong> “Please pray for our son as he starts treatment. We are asking for peace and wisdom.”</li>
+</ul>
+
+<p>What matters here is not formality. It is trust. If you are speaking for someone else, do not overshare just because you can. Use the smallest amount of information that still tells the church how to pray.</p>
+
+<p>If consent is unclear, keep the request general and private. That is the safer default. You can always add detail later if permission is granted and the situation changes.</p>
+
+<h2>Sharing Preferences: Public Prayer vs. Private Request</h2>
+
+<p>Not every request belongs in the same channel. A church needs both public prayer and private care, but they are not the same thing. Choosing the right lane keeps the request useful.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Sharing choice</th>
+      <th>Best when</th>
+      <th>What to say</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Public prayer</td>
+      <td>The need is general and you are comfortable with broader church awareness.</td>
+      <td>“Please pray for our family this week as we travel.”</td>
+    </tr>
+    <tr>
+      <td>Private request</td>
+      <td>The matter is sensitive, personal, or not ready for wider sharing.</td>
+      <td>“Please keep this private and pray for wisdom as we work through a family matter.”</td>
+    </tr>
+    <tr>
+      <td>Limited sharing</td>
+      <td>You want prayer but do not want every detail repeated.</td>
+      <td>“You may share the general need, but please leave out the details.”</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>If you are unsure, choose the more private option. That is the conservative decision and usually the right one. It is easier to expand a request later than to retract details after they have already gone farther than you intended.</p>
+
+<p>If the request becomes something broader for the church to know about, you can also look to the <a href="/news.html">News</a> page for public updates. That page is for church communication, not a place to assume personal details will be posted. Public and personal are not the same category, even when the same people are involved.</p>
+
+<h2>How to Submit</h2>
+
+<p>Once your request is ready, use the church’s normal contact paths. The simplest route is usually the <a href="/contacts.html">Contacts</a> page. If you prefer a form-based route, use <a href="/contact.php">Contact Us</a>. Either way, keep the message short, specific, and consistent with the privacy level you chose.</p>
+
+<p>A helpful submission usually has three parts:</p>
+
+<ol>
+  <li><strong>The request itself:</strong> one or two clear sentences.</li>
+  <li><strong>Your privacy note:</strong> public, private, or limited sharing.</li>
+  <li><strong>A follow-up option:</strong> a phone number or email if you want someone to reach back out.</li>
+</ol>
+
+<p>What happens after that? In practical terms, the church receives the note, reads the request, and handles it according to the communication path and privacy preference you provided. If more information is needed, someone may follow up. If no follow-up is needed, the request can still be prayed over without extra drama. That is usually the best case. Prayer requests are not package tracking.</p>
+
+<p>Do not build your wording around a guaranteed response time or a guaranteed outcome. A church can promise care and diligence. It cannot promise the timing of every answer. Keep the focus on the request itself, and keep praying while the message moves through the normal process.</p>
+
+<p>If you need more than a brief prayer note, say so. A sentence like “We would appreciate a follow-up conversation if possible” gives the church a better signal than a wall of text. If the matter is urgent, say that plainly near the top of the message. Simple language wins here.</p>
+
+<h2>A Short Checklist Before You Send</h2>
+
+<ul>
+  <li>Is the request clear in one sentence?</li>
+  <li>Did you include the type of prayer needed?</li>
+  <li>Did you leave out anything private or unnecessary?</li>
+  <li>Did you note whether the request is public, private, or limited?</li>
+  <li>If it is for someone else, did you mention your relationship and consent?</li>
+  <li>If timing matters, did you include the relevant date or timeframe?</li>
+</ul>
+
+<p>If you can answer yes to those six questions, the request is probably ready. There is no prize for over-writing it.</p>
+
+<h2>Closing Encouragement</h2>
+
+<p>A good prayer request is not fancy. It is faithful, clear, and respectful. If you keep the message focused on the need, the timing, and the privacy level, you make it easier for the church to do what churches are supposed to do: pray, care, and respond with wisdom.</p>
+
+<p>Start with the <a href="/contacts.html">Contacts</a> page or <a href="/contact.php">Contact Us</a> form, keep your wording simple, and let the church know whether the request should stay private. If you want to think through other next steps while you wait, the <a href="/resources">Resources</a> page can point you to additional support, and <a href="/news.html">News</a> can help you stay aware of broader church updates.</p>
+
+<p>Finally, keep praying after you submit. That part still matters. The church can handle the message, but you should still bring the burden to God directly. <a href="https://www.biblegateway.com/passage/?search=1+Thessalonians+5%3A17&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">1 Thessalonians 5:17</a> keeps the instruction short for a reason.</p>

diff --git a//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html
new file mode 100644
index 0000000000000000000000000000000000000000..8528939ff7211beb80e6eac7fe0a495ab02800ed
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html
@@ -0,0 +1,247 @@
+<p><strong><em>A prayer request does not need to sound polished. It needs to be clear enough for the church to pray without guessing.</em></strong></p>
+
+<p><strong>By Marcus Reed</strong> | Updated June 23, 2026</p>
+
+<p>When people sit down to write a prayer request, the same practical questions come up fast: How much context is enough? What should stay private? Can I ask for prayer for someone else? And how do I make the request easy for the church to read and use well?</p>
+
+<p>Those are good questions. Prayer is not a performance, and the Bible treats it that way. <a href="https://www.biblegateway.com/passage/?search=Philippians+4%3A6-7&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">Philippians 4:6-7</a> points toward honest, direct prayer; <a href="https://www.biblegateway.com/passage/?search=Matthew+6%3A6&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">Matthew 6:6</a> reminds believers that prayer can also be private and disciplined. A useful church request follows the same logic: enough context to be specific, enough restraint to protect what should stay private, and enough clarity that people can pray with purpose.</p>
+
+<p>If you want the shortest path, start with the church <a href="/contacts.html">Contacts</a> page, or use the site's <a href="/contact.php">contact form</a> if that is more convenient. If you are looking for broader church information while you prepare your message, the <a href="/resources">Resources</a> page is a good place to get oriented.</p>
+
+<figure class="wp-block-image size-large">
+  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg" alt="Planning materials on a desk with a calendar and smartphone for Sunday service coordination" class="wp-image-76" style="width:100%;height:auto;" />
+  <figcaption>A simple request starts with the same discipline as any good plan: enough detail to be useful, not so much that the point gets buried.</figcaption>
+</figure>
+
+<h2>Why We Ask for a Little Context</h2>
+
+<p>Prayer teams do better with signal than with noise. A short note that says what is happening, who it affects, and what kind of prayer is needed gives the church something concrete to carry. A vague request forces people to fill in the blanks, and that is where confusion starts.</p>
+
+<p>Context also helps the church handle requests appropriately. Some needs are fine to share broadly. Some should stay with a limited group. Some should be treated as private pastoral matters. The more clearly you state your preference, the less guesswork is required on the other side.</p>
+
+<p>There is a third reason, and it is the one people often skip: context respects the person who is asking for prayer. A request that is too thin can feel detached; a request that is too detailed can feel exposed. The goal is not to narrate your whole life. The goal is to give enough information for faithful prayer and responsible care.</p>
+
+<h2>A Quick Template You Can Copy and Paste</h2>
+
+<p>If you are not sure where to start, use this format. It is simple on purpose.</p>
+
+<pre><code>Name: [Your name]
+Request: [One short sentence about the need]
+Details: [Only the facts that help people pray well]
+Timeframe: [Today, this week, on [date], or ongoing]
+Ongoing vs. one-time: [One-time / recurring]
+Sharing preference: [Public / private / limited sharing]
+Contact: [Optional phone or email if a follow-up may help]</code></pre>
+
+<p>That is enough for most situations. If you need more privacy, leave out the contact line and keep the description general. If the request is for someone else, say so clearly in the first line so the church understands the relationship and the permission level.</p>
+
+<p>A few quick definitions help here:</p>
+
+<ul>
+  <li><strong>Public prayer:</strong> a request that can be shared more broadly with the church.</li>
+  <li><strong>Private request:</strong> a request that should stay with a smaller, limited group.</li>
+  <li><strong>Ongoing request:</strong> a situation that needs repeated prayer over time.</li>
+  <li><strong>Timeframe:</strong> when the need is happening or when support is most important.</li>
+</ul>
+
+<p>Think of the template as a floor, not a ceiling. You can always add a sentence, but you do not need to write a paragraph for every line. A church can work with a concise request. It cannot work with a mystery wrapped in spiritual language.</p>
+
+<h2>Do Include</h2>
+
+<p>The most useful prayer requests include the facts that actually help someone pray.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Include this</th>
+      <th>Why it helps</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>A clear request in one sentence</td>
+      <td>It tells the reader exactly what kind of prayer you are asking for.</td>
+    </tr>
+    <tr>
+      <td>Specific needs or concerns</td>
+      <td>“Healing,” “wisdom,” “travel safety,” or “comfort” are easier to pray for than a vague concern.</td>
+    </tr>
+    <tr>
+      <td>Relevant dates or timeframes</td>
+      <td>Dates help the church know what matters now, this week, or later.</td>
+    </tr>
+    <tr>
+      <td>Whether the request is confidential</td>
+      <td>Privacy preferences should be stated plainly, not left to interpretation.</td>
+    </tr>
+    <tr>
+      <td>Whether the request is ongoing</td>
+      <td>A continuing need may be placed on a prayer list differently from a one-time update.</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>One useful habit: write the request as if someone else has to read it once, understand it immediately, and pray right away. That is the operational standard. Church communication is not a scavenger hunt.</p>
+
+<p>Here are a few examples of good, concise wording:</p>
+
+<ul>
+  <li><strong>Healing:</strong> “Please pray for Sarah as she prepares for surgery on Thursday. We are asking for peace, skill for the medical team, and steady recovery.”</li>
+  <li><strong>Family support:</strong> “Please pray for our family during a difficult week. We need wisdom, patience, and rest.”</li>
+  <li><strong>Guidance:</strong> “Please pray for discernment as I make a work decision by the end of the month.”</li>
+  <li><strong>Comfort:</strong> “Please pray for comfort and strength after a recent loss. This can stay private.”</li>
+</ul>
+
+<p>Notice what is not happening there. There is no long backstory, no dramatic language, and no pressure to explain every detail. The request stays readable.</p>
+
+<h2>Don’t Include</h2>
+
+<p>Good judgment matters. A prayer request is not the right place for everything.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Leave this out</th>
+      <th>Why to avoid it</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Overly personal details</td>
+      <td>If it would make you uncomfortable to read out loud, it probably should not be in the request.</td>
+    </tr>
+    <tr>
+      <td>Information you do not have permission to share</td>
+      <td>Consent matters, especially when the request involves another person.</td>
+    </tr>
+    <tr>
+      <td>Long background narratives</td>
+      <td>The main need should stay visible. A request that rambles can hide the actual prayer point.</td>
+    </tr>
+    <tr>
+      <td>Unnecessary medical, family, or financial details</td>
+      <td>More detail is not always better. Sometimes it is just more detail.</td>
+    </tr>
+    <tr>
+      <td>Anything you are not comfortable sharing publicly</td>
+      <td>If it feels too exposed, mark it private or keep it brief.</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>If a detail does not help someone pray, leave it out. That is usually the right filter. The church does not need a case file. It needs enough context to respond with care.</p>
+
+<h2>If You Are Requesting Healing, Guidance, or Comfort</h2>
+
+<p>These are the situations where people often over-explain or under-explain. The middle path is usually best.</p>
+
+<p>For healing, say what kind of prayer is needed without turning the note into a medical summary. For guidance, name the decision and the deadline if there is one. For comfort, say what kind of support would be most helpful: peace, strength, patience, reassurance, or rest.</p>
+
+<p>You can borrow one of these patterns:</p>
+
+<ul>
+  <li><strong>Healing:</strong> “Please pray for healing and wise care as I recover from treatment this week.”</li>
+  <li><strong>Guidance:</strong> “Please pray for clarity as our family considers next steps for school and work.”</li>
+  <li><strong>Comfort:</strong> “Please pray for comfort, stability, and help with the next few days.”</li>
+  <li><strong>Strength:</strong> “Please pray for strength to stay steady through a difficult season.”</li>
+</ul>
+
+<p>If you want to keep a request private but still specific, say that directly:</p>
+
+<blockquote>
+  <p>“Please pray for healing for a family member this week. We are not ready to share details publicly, so please keep this private.”</p>
+</blockquote>
+
+<p>That kind of wording does two jobs at once. It gives the church a prayer focus and sets a boundary without making the request awkward.</p>
+
+<p>For a broader biblical frame, <a href="https://www.biblegateway.com/passage/?search=James+5%3A16&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">James 5:16</a> connects prayer with honest confession and mutual care. The point is not performance. The point is trust and clarity.</p>
+
+<h2>If You Are Submitting for Someone Else</h2>
+
+<p>People often ask for prayer on behalf of a spouse, child, parent, friend, or coworker. That is normal. The key is to say two things clearly: your relationship to the person and whether you have permission to share the request.</p>
+
+<p>Useful wording looks like this:</p>
+
+<ul>
+  <li><strong>With consent:</strong> “Please pray for my father, who gave me permission to share that he has a procedure next week.”</li>
+  <li><strong>Without detail:</strong> “Please pray for a friend who is facing a hard family situation.”</li>
+  <li><strong>For a child:</strong> “Please pray for our son as he starts treatment. We are asking for peace and wisdom.”</li>
+</ul>
+
+<p>What matters here is not formality. It is trust. If you are speaking for someone else, do not overshare just because you can. Use the smallest amount of information that still tells the church how to pray.</p>
+
+<p>If consent is unclear, keep the request general and private. That is the safer default. You can always add detail later if permission is granted and the situation changes.</p>
+
+<h2>Sharing Preferences: Public Prayer vs. Private Request</h2>
+
+<p>Not every request belongs in the same channel. A church needs both public prayer and private care, but they are not the same thing. Choosing the right lane keeps the request useful.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Sharing choice</th>
+      <th>Best when</th>
+      <th>What to say</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Public prayer</td>
+      <td>The need is general and you are comfortable with broader church awareness.</td>
+      <td>“Please pray for our family this week as we travel.”</td>
+    </tr>
+    <tr>
+      <td>Private request</td>
+      <td>The matter is sensitive, personal, or not ready for wider sharing.</td>
+      <td>“Please keep this private and pray for wisdom as we work through a family matter.”</td>
+    </tr>
+    <tr>
+      <td>Limited sharing</td>
+      <td>You want prayer but do not want every detail repeated.</td>
+      <td>“You may share the general need, but please leave out the details.”</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>If you are unsure, choose the more private option. That is the conservative decision and usually the right one. It is easier to expand a request later than to retract details after they have already gone farther than you intended.</p>
+
+<p>If the request becomes something broader for the church to know about, you can also look to the <a href="/news.html">News</a> page for public updates. That page is for church communication, not a place to assume personal details will be posted. Public and personal are not the same category, even when the same people are involved.</p>
+
+<h2>How to Submit</h2>
+
+<p>Once your request is ready, use the church’s normal contact paths. The simplest route is usually the <a href="/contacts.html">Contacts</a> page. If you prefer a form-based route, use <a href="/contact.php">Contact Us</a>. Either way, keep the message short, specific, and consistent with the privacy level you chose.</p>
+
+<p>A helpful submission usually has three parts:</p>
+
+<ol>
+  <li><strong>The request itself:</strong> one or two clear sentences.</li>
+  <li><strong>Your privacy note:</strong> public, private, or limited sharing.</li>
+  <li><strong>A follow-up option:</strong> a phone number or email if you want someone to reach back out.</li>
+</ol>
+
+<p>What happens after that? In practical terms, the church receives the note, reads the request, and handles it according to the communication path and privacy preference you provided. If more information is needed, someone may follow up. If no follow-up is needed, the request can still be prayed over without extra drama. That is usually the best case. Prayer requests are not package tracking.</p>
+
+<p>Do not build your wording around a guaranteed response time or a guaranteed outcome. A church can promise care and diligence. It cannot promise the timing of every answer. Keep the focus on the request itself, and keep praying while the message moves through the normal process.</p>
+
+<p>If you need more than a brief prayer note, say so. A sentence like “We would appreciate a follow-up conversation if possible” gives the church a better signal than a wall of text. If the matter is urgent, say that plainly near the top of the message. Simple language wins here.</p>
+
+<h2>A Short Checklist Before You Send</h2>
+
+<ul>
+  <li>Is the request clear in one sentence?</li>
+  <li>Did you include the type of prayer needed?</li>
+  <li>Did you leave out anything private or unnecessary?</li>
+  <li>Did you note whether the request is public, private, or limited?</li>
+  <li>If it is for someone else, did you mention your relationship and consent?</li>
+  <li>If timing matters, did you include the relevant date or timeframe?</li>
+</ul>
+
+<p>If you can answer yes to those six questions, the request is probably ready. There is no prize for over-writing it.</p>
+
+<h2>Closing Encouragement</h2>
+
+<p>A good prayer request is not fancy. It is faithful, clear, and respectful. If you keep the message focused on the need, the timing, and the privacy level, you make it easier for the church to do what churches are supposed to do: pray, care, and respond with wisdom.</p>
+
+<p>Start with the <a href="/contacts.html">Contacts</a> page or <a href="/contact.php">Contact Us</a> form, keep your wording simple, and let the church know whether the request should stay private. If you want to think through other next steps while you wait, the <a href="/resources">Resources</a> page can point you to additional support, and <a href="/news.html">News</a> can help you stay aware of broader church updates.</p>
+
+<p>Finally, keep praying after you submit. That part still matters. The church can handle the message, but you should still bring the burden to God directly. <a href="https://www.biblegateway.com/passage/?search=1+Thessalonians+5%3A17&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">1 Thessalonians 5:17</a> keeps the instruction short for a reason.</p>

codex
The draft is in place. I’m checking length and then I’ll push it into WordPress, set the author and featured image, and verify the public URL plus inline image.
exec
/bin/bash -lc 'wc -w wp-content/uploads/flatlogic-article-tasks/job-506/article.html' in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
2190 wp-content/uploads/flatlogic-article-tasks/job-506/article.html

exec
/bin/bash -lc "sed -n '1,260p' wp-content/uploads/flatlogic-article-tasks/job-506/article.html" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
<p><strong><em>A prayer request does not need to sound polished. It needs to be clear enough for the church to pray without guessing.</em></strong></p>

<p><strong>By Marcus Reed</strong> | Updated June 23, 2026</p>

<p>When people sit down to write a prayer request, the same practical questions come up fast: How much context is enough? What should stay private? Can I ask for prayer for someone else? And how do I make the request easy for the church to read and use well?</p>

<p>Those are good questions. Prayer is not a performance, and the Bible treats it that way. <a href="https://www.biblegateway.com/passage/?search=Philippians+4%3A6-7&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">Philippians 4:6-7</a> points toward honest, direct prayer; <a href="https://www.biblegateway.com/passage/?search=Matthew+6%3A6&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">Matthew 6:6</a> reminds believers that prayer can also be private and disciplined. A useful church request follows the same logic: enough context to be specific, enough restraint to protect what should stay private, and enough clarity that people can pray with purpose.</p>

<p>If you want the shortest path, start with the church <a href="/contacts.html">Contacts</a> page, or use the site's <a href="/contact.php">contact form</a> if that is more convenient. If you are looking for broader church information while you prepare your message, the <a href="/resources">Resources</a> page is a good place to get oriented.</p>

<figure class="wp-block-image size-large">
  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg" alt="Planning materials on a desk with a calendar and smartphone for Sunday service coordination" class="wp-image-76" style="width:100%;height:auto;" />
  <figcaption>A simple request starts with the same discipline as any good plan: enough detail to be useful, not so much that the point gets buried.</figcaption>
</figure>

<h2>Why We Ask for a Little Context</h2>

<p>Prayer teams do better with signal than with noise. A short note that says what is happening, who it affects, and what kind of prayer is needed gives the church something concrete to carry. A vague request forces people to fill in the blanks, and that is where confusion starts.</p>

<p>Context also helps the church handle requests appropriately. Some needs are fine to share broadly. Some should stay with a limited group. Some should be treated as private pastoral matters. The more clearly you state your preference, the less guesswork is required on the other side.</p>

<p>There is a third reason, and it is the one people often skip: context respects the person who is asking for prayer. A request that is too thin can feel detached; a request that is too detailed can feel exposed. The goal is not to narrate your whole life. The goal is to give enough information for faithful prayer and responsible care.</p>

<h2>A Quick Template You Can Copy and Paste</h2>

<p>If you are not sure where to start, use this format. It is simple on purpose.</p>

<pre><code>Name: [Your name]
Request: [One short sentence about the need]
Details: [Only the facts that help people pray well]
Timeframe: [Today, this week, on [date], or ongoing]
Ongoing vs. one-time: [One-time / recurring]
Sharing preference: [Public / private / limited sharing]
Contact: [Optional phone or email if a follow-up may help]</code></pre>

<p>That is enough for most situations. If you need more privacy, leave out the contact line and keep the description general. If the request is for someone else, say so clearly in the first line so the church understands the relationship and the permission level.</p>

<p>A few quick definitions help here:</p>

<ul>
  <li><strong>Public prayer:</strong> a request that can be shared more broadly with the church.</li>
  <li><strong>Private request:</strong> a request that should stay with a smaller, limited group.</li>
  <li><strong>Ongoing request:</strong> a situation that needs repeated prayer over time.</li>
  <li><strong>Timeframe:</strong> when the need is happening or when support is most important.</li>
</ul>

<p>Think of the template as a floor, not a ceiling. You can always add a sentence, but you do not need to write a paragraph for every line. A church can work with a concise request. It cannot work with a mystery wrapped in spiritual language.</p>

<h2>Do Include</h2>

<p>The most useful prayer requests include the facts that actually help someone pray.</p>

<table>
  <thead>
    <tr>
      <th>Include this</th>
      <th>Why it helps</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>A clear request in one sentence</td>
      <td>It tells the reader exactly what kind of prayer you are asking for.</td>
    </tr>
    <tr>
      <td>Specific needs or concerns</td>
      <td>“Healing,” “wisdom,” “travel safety,” or “comfort” are easier to pray for than a vague concern.</td>
    </tr>
    <tr>
      <td>Relevant dates or timeframes</td>
      <td>Dates help the church know what matters now, this week, or later.</td>
    </tr>
    <tr>
      <td>Whether the request is confidential</td>
      <td>Privacy preferences should be stated plainly, not left to interpretation.</td>
    </tr>
    <tr>
      <td>Whether the request is ongoing</td>
      <td>A continuing need may be placed on a prayer list differently from a one-time update.</td>
    </tr>
  </tbody>
</table>

<p>One useful habit: write the request as if someone else has to read it once, understand it immediately, and pray right away. That is the operational standard. Church communication is not a scavenger hunt.</p>

<p>Here are a few examples of good, concise wording:</p>

<ul>
  <li><strong>Healing:</strong> “Please pray for Sarah as she prepares for surgery on Thursday. We are asking for peace, skill for the medical team, and steady recovery.”</li>
  <li><strong>Family support:</strong> “Please pray for our family during a difficult week. We need wisdom, patience, and rest.”</li>
  <li><strong>Guidance:</strong> “Please pray for discernment as I make a work decision by the end of the month.”</li>
  <li><strong>Comfort:</strong> “Please pray for comfort and strength after a recent loss. This can stay private.”</li>
</ul>

<p>Notice what is not happening there. There is no long backstory, no dramatic language, and no pressure to explain every detail. The request stays readable.</p>

<h2>Don’t Include</h2>

<p>Good judgment matters. A prayer request is not the right place for everything.</p>

<table>
  <thead>
    <tr>
      <th>Leave this out</th>
      <th>Why to avoid it</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Overly personal details</td>
      <td>If it would make you uncomfortable to read out loud, it probably should not be in the request.</td>
    </tr>
    <tr>
      <td>Information you do not have permission to share</td>
      <td>Consent matters, especially when the request involves another person.</td>
    </tr>
    <tr>
      <td>Long background narratives</td>
      <td>The main need should stay visible. A request that rambles can hide the actual prayer point.</td>
    </tr>
    <tr>
      <td>Unnecessary medical, family, or financial details</td>
      <td>More detail is not always better. Sometimes it is just more detail.</td>
    </tr>
    <tr>
      <td>Anything you are not comfortable sharing publicly</td>
      <td>If it feels too exposed, mark it private or keep it brief.</td>
    </tr>
  </tbody>
</table>

<p>If a detail does not help someone pray, leave it out. That is usually the right filter. The church does not need a case file. It needs enough context to respond with care.</p>

<h2>If You Are Requesting Healing, Guidance, or Comfort</h2>

<p>These are the situations where people often over-explain or under-explain. The middle path is usually best.</p>

<p>For healing, say what kind of prayer is needed without turning the note into a medical summary. For guidance, name the decision and the deadline if there is one. For comfort, say what kind of support would be most helpful: peace, strength, patience, reassurance, or rest.</p>

<p>You can borrow one of these patterns:</p>

<ul>
  <li><strong>Healing:</strong> “Please pray for healing and wise care as I recover from treatment this week.”</li>
  <li><strong>Guidance:</strong> “Please pray for clarity as our family considers next steps for school and work.”</li>
  <li><strong>Comfort:</strong> “Please pray for comfort, stability, and help with the next few days.”</li>
  <li><strong>Strength:</strong> “Please pray for strength to stay steady through a difficult season.”</li>
</ul>

<p>If you want to keep a request private but still specific, say that directly:</p>

<blockquote>
  <p>“Please pray for healing for a family member this week. We are not ready to share details publicly, so please keep this private.”</p>
</blockquote>

<p>That kind of wording does two jobs at once. It gives the church a prayer focus and sets a boundary without making the request awkward.</p>

<p>For a broader biblical frame, <a href="https://www.biblegateway.com/passage/?search=James+5%3A16&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">James 5:16</a> connects prayer with honest confession and mutual care. The point is not performance. The point is trust and clarity.</p>

<h2>If You Are Submitting for Someone Else</h2>

<p>People often ask for prayer on behalf of a spouse, child, parent, friend, or coworker. That is normal. The key is to say two things clearly: your relationship to the person and whether you have permission to share the request.</p>

<p>Useful wording looks like this:</p>

<ul>
  <li><strong>With consent:</strong> “Please pray for my father, who gave me permission to share that he has a procedure next week.”</li>
  <li><strong>Without detail:</strong> “Please pray for a friend who is facing a hard family situation.”</li>
  <li><strong>For a child:</strong> “Please pray for our son as he starts treatment. We are asking for peace and wisdom.”</li>
</ul>

<p>What matters here is not formality. It is trust. If you are speaking for someone else, do not overshare just because you can. Use the smallest amount of information that still tells the church how to pray.</p>

<p>If consent is unclear, keep the request general and private. That is the safer default. You can always add detail later if permission is granted and the situation changes.</p>

<h2>Sharing Preferences: Public Prayer vs. Private Request</h2>

<p>Not every request belongs in the same channel. A church needs both public prayer and private care, but they are not the same thing. Choosing the right lane keeps the request useful.</p>

<table>
  <thead>
    <tr>
      <th>Sharing choice</th>
      <th>Best when</th>
      <th>What to say</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Public prayer</td>
      <td>The need is general and you are comfortable with broader church awareness.</td>
      <td>“Please pray for our family this week as we travel.”</td>
    </tr>
    <tr>
      <td>Private request</td>
      <td>The matter is sensitive, personal, or not ready for wider sharing.</td>
      <td>“Please keep this private and pray for wisdom as we work through a family matter.”</td>
    </tr>
    <tr>
      <td>Limited sharing</td>
      <td>You want prayer but do not want every detail repeated.</td>
      <td>“You may share the general need, but please leave out the details.”</td>
    </tr>
  </tbody>
</table>

<p>If you are unsure, choose the more private option. That is the conservative decision and usually the right one. It is easier to expand a request later than to retract details after they have already gone farther than you intended.</p>

<p>If the request becomes something broader for the church to know about, you can also look to the <a href="/news.html">News</a> page for public updates. That page is for church communication, not a place to assume personal details will be posted. Public and personal are not the same category, even when the same people are involved.</p>

<h2>How to Submit</h2>

<p>Once your request is ready, use the church’s normal contact paths. The simplest route is usually the <a href="/contacts.html">Contacts</a> page. If you prefer a form-based route, use <a href="/contact.php">Contact Us</a>. Either way, keep the message short, specific, and consistent with the privacy level you chose.</p>

<p>A helpful submission usually has three parts:</p>

<ol>
  <li><strong>The request itself:</strong> one or two clear sentences.</li>
  <li><strong>Your privacy note:</strong> public, private, or limited sharing.</li>
  <li><strong>A follow-up option:</strong> a phone number or email if you want someone to reach back out.</li>
</ol>

<p>What happens after that? In practical terms, the church receives the note, reads the request, and handles it according to the communication path and privacy preference you provided. If more information is needed, someone may follow up. If no follow-up is needed, the request can still be prayed over without extra drama. That is usually the best case. Prayer requests are not package tracking.</p>

<p>Do not build your wording around a guaranteed response time or a guaranteed outcome. A church can promise care and diligence. It cannot promise the timing of every answer. Keep the focus on the request itself, and keep praying while the message moves through the normal process.</p>

<p>If you need more than a brief prayer note, say so. A sentence like “We would appreciate a follow-up conversation if possible” gives the church a better signal than a wall of text. If the matter is urgent, say that plainly near the top of the message. Simple language wins here.</p>

<h2>A Short Checklist Before You Send</h2>

<ul>
  <li>Is the request clear in one sentence?</li>
  <li>Did you include the type of prayer needed?</li>
  <li>Did you leave out anything private or unnecessary?</li>
  <li>Did you note whether the request is public, private, or limited?</li>
  <li>If it is for someone else, did you mention your relationship and consent?</li>
  <li>If timing matters, did you include the relevant date or timeframe?</li>
</ul>

<p>If you can answer yes to those six questions, the request is probably ready. There is no prize for over-writing it.</p>

<h2>Closing Encouragement</h2>

<p>A good prayer request is not fancy. It is faithful, clear, and respectful. If you keep the message focused on the need, the timing, and the privacy level, you make it easier for the church to do what churches are supposed to do: pray, care, and respond with wisdom.</p>

<p>Start with the <a href="/contacts.html">Contacts</a> page or <a href="/contact.php">Contact Us</a> form, keep your wording simple, and let the church know whether the request should stay private. If you want to think through other next steps while you wait, the <a href="/resources">Resources</a> page can point you to additional support, and <a href="/news.html">News</a> can help you stay aware of broader church updates.</p>

<p>Finally, keep praying after you submit. That part still matters. The church can handle the message, but you should still bring the burden to God directly. <a href="https://www.biblegateway.com/passage/?search=1+Thessalonians+5%3A17&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">1 Thessalonians 5:17</a> keeps the instruction short for a reason.</p>

diff --git a//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html
new file mode 100644
index 0000000000000000000000000000000000000000..8528939ff7211beb80e6eac7fe0a495ab02800ed
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html
@@ -0,0 +1,247 @@
+<p><strong><em>A prayer request does not need to sound polished. It needs to be clear enough for the church to pray without guessing.</em></strong></p>
+
+<p><strong>By Marcus Reed</strong> | Updated June 23, 2026</p>
+
+<p>When people sit down to write a prayer request, the same practical questions come up fast: How much context is enough? What should stay private? Can I ask for prayer for someone else? And how do I make the request easy for the church to read and use well?</p>
+
+<p>Those are good questions. Prayer is not a performance, and the Bible treats it that way. <a href="https://www.biblegateway.com/passage/?search=Philippians+4%3A6-7&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">Philippians 4:6-7</a> points toward honest, direct prayer; <a href="https://www.biblegateway.com/passage/?search=Matthew+6%3A6&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">Matthew 6:6</a> reminds believers that prayer can also be private and disciplined. A useful church request follows the same logic: enough context to be specific, enough restraint to protect what should stay private, and enough clarity that people can pray with purpose.</p>
+
+<p>If you want the shortest path, start with the church <a href="/contacts.html">Contacts</a> page, or use the site's <a href="/contact.php">contact form</a> if that is more convenient. If you are looking for broader church information while you prepare your message, the <a href="/resources">Resources</a> page is a good place to get oriented.</p>
+
+<figure class="wp-block-image size-large">
+  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg" alt="Planning materials on a desk with a calendar and smartphone for Sunday service coordination" class="wp-image-76" style="width:100%;height:auto;" />
+  <figcaption>A simple request starts with the same discipline as any good plan: enough detail to be useful, not so much that the point gets buried.</figcaption>
+</figure>
+
+<h2>Why We Ask for a Little Context</h2>
+
+<p>Prayer teams do better with signal than with noise. A short note that says what is happening, who it affects, and what kind of prayer is needed gives the church something concrete to carry. A vague request forces people to fill in the blanks, and that is where confusion starts.</p>
+
+<p>Context also helps the church handle requests appropriately. Some needs are fine to share broadly. Some should stay with a limited group. Some should be treated as private pastoral matters. The more clearly you state your preference, the less guesswork is required on the other side.</p>
+
+<p>There is a third reason, and it is the one people often skip: context respects the person who is asking for prayer. A request that is too thin can feel detached; a request that is too detailed can feel exposed. The goal is not to narrate your whole life. The goal is to give enough information for faithful prayer and responsible care.</p>
+
+<h2>A Quick Template You Can Copy and Paste</h2>
+
+<p>If you are not sure where to start, use this format. It is simple on purpose.</p>
+
+<pre><code>Name: [Your name]
+Request: [One short sentence about the need]
+Details: [Only the facts that help people pray well]
+Timeframe: [Today, this week, on [date], or ongoing]
+Ongoing vs. one-time: [One-time / recurring]
+Sharing preference: [Public / private / limited sharing]
+Contact: [Optional phone or email if a follow-up may help]</code></pre>
+
+<p>That is enough for most situations. If you need more privacy, leave out the contact line and keep the description general. If the request is for someone else, say so clearly in the first line so the church understands the relationship and the permission level.</p>
+
+<p>A few quick definitions help here:</p>
+
+<ul>
+  <li><strong>Public prayer:</strong> a request that can be shared more broadly with the church.</li>
+  <li><strong>Private request:</strong> a request that should stay with a smaller, limited group.</li>
+  <li><strong>Ongoing request:</strong> a situation that needs repeated prayer over time.</li>
+  <li><strong>Timeframe:</strong> when the need is happening or when support is most important.</li>
+</ul>
+
+<p>Think of the template as a floor, not a ceiling. You can always add a sentence, but you do not need to write a paragraph for every line. A church can work with a concise request. It cannot work with a mystery wrapped in spiritual language.</p>
+
+<h2>Do Include</h2>
+
+<p>The most useful prayer requests include the facts that actually help someone pray.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Include this</th>
+      <th>Why it helps</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>A clear request in one sentence</td>
+      <td>It tells the reader exactly what kind of prayer you are asking for.</td>
+    </tr>
+    <tr>
+      <td>Specific needs or concerns</td>
+      <td>“Healing,” “wisdom,” “travel safety,” or “comfort” are easier to pray for than a vague concern.</td>
+    </tr>
+    <tr>
+      <td>Relevant dates or timeframes</td>
+      <td>Dates help the church know what matters now, this week, or later.</td>
+    </tr>
+    <tr>
+      <td>Whether the request is confidential</td>
+      <td>Privacy preferences should be stated plainly, not left to interpretation.</td>
+    </tr>
+    <tr>
+      <td>Whether the request is ongoing</td>
+      <td>A continuing need may be placed on a prayer list differently from a one-time update.</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>One useful habit: write the request as if someone else has to read it once, understand it immediately, and pray right away. That is the operational standard. Church communication is not a scavenger hunt.</p>
+
+<p>Here are a few examples of good, concise wording:</p>
+
+<ul>
+  <li><strong>Healing:</strong> “Please pray for Sarah as she prepares for surgery on Thursday. We are asking for peace, skill for the medical team, and steady recovery.”</li>
+  <li><strong>Family support:</strong> “Please pray for our family during a difficult week. We need wisdom, patience, and rest.”</li>
+  <li><strong>Guidance:</strong> “Please pray for discernment as I make a work decision by the end of the month.”</li>
+  <li><strong>Comfort:</strong> “Please pray for comfort and strength after a recent loss. This can stay private.”</li>
+</ul>
+
+<p>Notice what is not happening there. There is no long backstory, no dramatic language, and no pressure to explain every detail. The request stays readable.</p>
+
+<h2>Don’t Include</h2>
+
+<p>Good judgment matters. A prayer request is not the right place for everything.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Leave this out</th>
+      <th>Why to avoid it</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Overly personal details</td>
+      <td>If it would make you uncomfortable to read out loud, it probably should not be in the request.</td>
+    </tr>
+    <tr>
+      <td>Information you do not have permission to share</td>
+      <td>Consent matters, especially when the request involves another person.</td>
+    </tr>
+    <tr>
+      <td>Long background narratives</td>
+      <td>The main need should stay visible. A request that rambles can hide the actual prayer point.</td>
+    </tr>
+    <tr>
+      <td>Unnecessary medical, family, or financial details</td>
+      <td>More detail is not always better. Sometimes it is just more detail.</td>
+    </tr>
+    <tr>
+      <td>Anything you are not comfortable sharing publicly</td>
+      <td>If it feels too exposed, mark it private or keep it brief.</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>If a detail does not help someone pray, leave it out. That is usually the right filter. The church does not need a case file. It needs enough context to respond with care.</p>
+
+<h2>If You Are Requesting Healing, Guidance, or Comfort</h2>
+
+<p>These are the situations where people often over-explain or under-explain. The middle path is usually best.</p>
+
+<p>For healing, say what kind of prayer is needed without turning the note into a medical summary. For guidance, name the decision and the deadline if there is one. For comfort, say what kind of support would be most helpful: peace, strength, patience, reassurance, or rest.</p>
+
+<p>You can borrow one of these patterns:</p>
+
+<ul>
+  <li><strong>Healing:</strong> “Please pray for healing and wise care as I recover from treatment this week.”</li>
+  <li><strong>Guidance:</strong> “Please pray for clarity as our family considers next steps for school and work.”</li>
+  <li><strong>Comfort:</strong> “Please pray for comfort, stability, and help with the next few days.”</li>
+  <li><strong>Strength:</strong> “Please pray for strength to stay steady through a difficult season.”</li>
+</ul>
+
+<p>If you want to keep a request private but still specific, say that directly:</p>
+
+<blockquote>
+  <p>“Please pray for healing for a family member this week. We are not ready to share details publicly, so please keep this private.”</p>
+</blockquote>
+
+<p>That kind of wording does two jobs at once. It gives the church a prayer focus and sets a boundary without making the request awkward.</p>
+
+<p>For a broader biblical frame, <a href="https://www.biblegateway.com/passage/?search=James+5%3A16&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">James 5:16</a> connects prayer with honest confession and mutual care. The point is not performance. The point is trust and clarity.</p>
+
+<h2>If You Are Submitting for Someone Else</h2>
+
+<p>People often ask for prayer on behalf of a spouse, child, parent, friend, or coworker. That is normal. The key is to say two things clearly: your relationship to the person and whether you have permission to share the request.</p>
+
+<p>Useful wording looks like this:</p>
+
+<ul>
+  <li><strong>With consent:</strong> “Please pray for my father, who gave me permission to share that he has a procedure next week.”</li>
+  <li><strong>Without detail:</strong> “Please pray for a friend who is facing a hard family situation.”</li>
+  <li><strong>For a child:</strong> “Please pray for our son as he starts treatment. We are asking for peace and wisdom.”</li>
+</ul>
+
+<p>What matters here is not formality. It is trust. If you are speaking for someone else, do not overshare just because you can. Use the smallest amount of information that still tells the church how to pray.</p>
+
+<p>If consent is unclear, keep the request general and private. That is the safer default. You can always add detail later if permission is granted and the situation changes.</p>
+
+<h2>Sharing Preferences: Public Prayer vs. Private Request</h2>
+
+<p>Not every request belongs in the same channel. A church needs both public prayer and private care, but they are not the same thing. Choosing the right lane keeps the request useful.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Sharing choice</th>
+      <th>Best when</th>
+      <th>What to say</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Public prayer</td>
+      <td>The need is general and you are comfortable with broader church awareness.</td>
+      <td>“Please pray for our family this week as we travel.”</td>
+    </tr>
+    <tr>
+      <td>Private request</td>
+      <td>The matter is sensitive, personal, or not ready for wider sharing.</td>
+      <td>“Please keep this private and pray for wisdom as we work through a family matter.”</td>
+    </tr>
+    <tr>
+      <td>Limited sharing</td>
+      <td>You want prayer but do not want every detail repeated.</td>
+      <td>“You may share the general need, but please leave out the details.”</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>If you are unsure, choose the more private option. That is the conservative decision and usually the right one. It is easier to expand a request later than to retract details after they have already gone farther than you intended.</p>
+
+<p>If the request becomes something broader for the church to know about, you can also look to the <a href="/news.html">News</a> page for public updates. That page is for church communication, not a place to assume personal details will be posted. Public and personal are not the same category, even when the same people are involved.</p>
+
+<h2>How to Submit</h2>
+
+<p>Once your request is ready, use the church’s normal contact paths. The simplest route is usually the <a href="/contacts.html">Contacts</a> page. If you prefer a form-based route, use <a href="/contact.php">Contact Us</a>. Either way, keep the message short, specific, and consistent with the privacy level you chose.</p>
+
+<p>A helpful submission usually has three parts:</p>
+
+<ol>
+  <li><strong>The request itself:</strong> one or two clear sentences.</li>
+  <li><strong>Your privacy note:</strong> public, private, or limited sharing.</li>
+  <li><strong>A follow-up option:</strong> a phone number or email if you want someone to reach back out.</li>
+</ol>
+
+<p>What happens after that? In practical terms, the church receives the note, reads the request, and handles it according to the communication path and privacy preference you provided. If more information is needed, someone may follow up. If no follow-up is needed, the request can still be prayed over without extra drama. That is usually the best case. Prayer requests are not package tracking.</p>
+
+<p>Do not build your wording around a guaranteed response time or a guaranteed outcome. A church can promise care and diligence. It cannot promise the timing of every answer. Keep the focus on the request itself, and keep praying while the message moves through the normal process.</p>
+
+<p>If you need more than a brief prayer note, say so. A sentence like “We would appreciate a follow-up conversation if possible” gives the church a better signal than a wall of text. If the matter is urgent, say that plainly near the top of the message. Simple language wins here.</p>
+
+<h2>A Short Checklist Before You Send</h2>
+
+<ul>
+  <li>Is the request clear in one sentence?</li>
+  <li>Did you include the type of prayer needed?</li>
+  <li>Did you leave out anything private or unnecessary?</li>
+  <li>Did you note whether the request is public, private, or limited?</li>
+  <li>If it is for someone else, did you mention your relationship and consent?</li>
+  <li>If timing matters, did you include the relevant date or timeframe?</li>
+</ul>
+
+<p>If you can answer yes to those six questions, the request is probably ready. There is no prize for over-writing it.</p>
+
+<h2>Closing Encouragement</h2>
+
+<p>A good prayer request is not fancy. It is faithful, clear, and respectful. If you keep the message focused on the need, the timing, and the privacy level, you make it easier for the church to do what churches are supposed to do: pray, care, and respond with wisdom.</p>
+
+<p>Start with the <a href="/contacts.html">Contacts</a> page or <a href="/contact.php">Contact Us</a> form, keep your wording simple, and let the church know whether the request should stay private. If you want to think through other next steps while you wait, the <a href="/resources">Resources</a> page can point you to additional support, and <a href="/news.html">News</a> can help you stay aware of broader church updates.</p>
+
+<p>Finally, keep praying after you submit. That part still matters. The church can handle the message, but you should still bring the burden to God directly. <a href="https://www.biblegateway.com/passage/?search=1+Thessalonians+5%3A17&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">1 Thessalonians 5:17</a> keeps the instruction short for a reason.</p>

codex
The draft is a little short of the site’s article-length floor, so I’m adding one compact section with common mistakes and practical examples. That will bring it up to the expected weight without padding it with fluff.
apply patch
patch: completed
/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html
diff --git a//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html
new file mode 100644
index 0000000000000000000000000000000000000000..ba0db7a98ca7aaf1f97d1e0d7779b046be5e686a
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html
@@ -0,0 +1,281 @@
+<p><strong><em>A prayer request does not need to sound polished. It needs to be clear enough for the church to pray without guessing.</em></strong></p>
+
+<p><strong>By Marcus Reed</strong> | Updated June 23, 2026</p>
+
+<p>When people sit down to write a prayer request, the same practical questions come up fast: How much context is enough? What should stay private? Can I ask for prayer for someone else? And how do I make the request easy for the church to read and use well?</p>
+
+<p>Those are good questions. Prayer is not a performance, and the Bible treats it that way. <a href="https://www.biblegateway.com/passage/?search=Philippians+4%3A6-7&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">Philippians 4:6-7</a> points toward honest, direct prayer; <a href="https://www.biblegateway.com/passage/?search=Matthew+6%3A6&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">Matthew 6:6</a> reminds believers that prayer can also be private and disciplined. A useful church request follows the same logic: enough context to be specific, enough restraint to protect what should stay private, and enough clarity that people can pray with purpose.</p>
+
+<p>If you want the shortest path, start with the church <a href="/contacts.html">Contacts</a> page, or use the site's <a href="/contact.php">contact form</a> if that is more convenient. If you are looking for broader church information while you prepare your message, the <a href="/resources">Resources</a> page is a good place to get oriented.</p>
+
+<figure class="wp-block-image size-large">
+  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg" alt="Planning materials on a desk with a calendar and smartphone for Sunday service coordination" class="wp-image-76" style="width:100%;height:auto;" />
+  <figcaption>A simple request starts with the same discipline as any good plan: enough detail to be useful, not so much that the point gets buried.</figcaption>
+</figure>
+
+<h2>Why We Ask for a Little Context</h2>
+
+<p>Prayer teams do better with signal than with noise. A short note that says what is happening, who it affects, and what kind of prayer is needed gives the church something concrete to carry. A vague request forces people to fill in the blanks, and that is where confusion starts.</p>
+
+<p>Context also helps the church handle requests appropriately. Some needs are fine to share broadly. Some should stay with a limited group. Some should be treated as private pastoral matters. The more clearly you state your preference, the less guesswork is required on the other side.</p>
+
+<p>There is a third reason, and it is the one people often skip: context respects the person who is asking for prayer. A request that is too thin can feel detached; a request that is too detailed can feel exposed. The goal is not to narrate your whole life. The goal is to give enough information for faithful prayer and responsible care.</p>
+
+<h2>A Quick Template You Can Copy and Paste</h2>
+
+<p>If you are not sure where to start, use this format. It is simple on purpose.</p>
+
+<pre><code>Name: [Your name]
+Request: [One short sentence about the need]
+Details: [Only the facts that help people pray well]
+Timeframe: [Today, this week, on [date], or ongoing]
+Ongoing vs. one-time: [One-time / recurring]
+Sharing preference: [Public / private / limited sharing]
+Contact: [Optional phone or email if a follow-up may help]</code></pre>
+
+<p>That is enough for most situations. If you need more privacy, leave out the contact line and keep the description general. If the request is for someone else, say so clearly in the first line so the church understands the relationship and the permission level.</p>
+
+<p>A few quick definitions help here:</p>
+
+<ul>
+  <li><strong>Public prayer:</strong> a request that can be shared more broadly with the church.</li>
+  <li><strong>Private request:</strong> a request that should stay with a smaller, limited group.</li>
+  <li><strong>Ongoing request:</strong> a situation that needs repeated prayer over time.</li>
+  <li><strong>Timeframe:</strong> when the need is happening or when support is most important.</li>
+</ul>
+
+<p>Think of the template as a floor, not a ceiling. You can always add a sentence, but you do not need to write a paragraph for every line. A church can work with a concise request. It cannot work with a mystery wrapped in spiritual language.</p>
+
+<h2>Do Include</h2>
+
+<p>The most useful prayer requests include the facts that actually help someone pray.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Include this</th>
+      <th>Why it helps</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>A clear request in one sentence</td>
+      <td>It tells the reader exactly what kind of prayer you are asking for.</td>
+    </tr>
+    <tr>
+      <td>Specific needs or concerns</td>
+      <td>“Healing,” “wisdom,” “travel safety,” or “comfort” are easier to pray for than a vague concern.</td>
+    </tr>
+    <tr>
+      <td>Relevant dates or timeframes</td>
+      <td>Dates help the church know what matters now, this week, or later.</td>
+    </tr>
+    <tr>
+      <td>Whether the request is confidential</td>
+      <td>Privacy preferences should be stated plainly, not left to interpretation.</td>
+    </tr>
+    <tr>
+      <td>Whether the request is ongoing</td>
+      <td>A continuing need may be placed on a prayer list differently from a one-time update.</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>One useful habit: write the request as if someone else has to read it once, understand it immediately, and pray right away. That is the operational standard. Church communication is not a scavenger hunt.</p>
+
+<p>Here are a few examples of good, concise wording:</p>
+
+<ul>
+  <li><strong>Healing:</strong> “Please pray for Sarah as she prepares for surgery on Thursday. We are asking for peace, skill for the medical team, and steady recovery.”</li>
+  <li><strong>Family support:</strong> “Please pray for our family during a difficult week. We need wisdom, patience, and rest.”</li>
+  <li><strong>Guidance:</strong> “Please pray for discernment as I make a work decision by the end of the month.”</li>
+  <li><strong>Comfort:</strong> “Please pray for comfort and strength after a recent loss. This can stay private.”</li>
+</ul>
+
+<p>Notice what is not happening there. There is no long backstory, no dramatic language, and no pressure to explain every detail. The request stays readable.</p>
+
+<h2>Don’t Include</h2>
+
+<p>Good judgment matters. A prayer request is not the right place for everything.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Leave this out</th>
+      <th>Why to avoid it</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Overly personal details</td>
+      <td>If it would make you uncomfortable to read out loud, it probably should not be in the request.</td>
+    </tr>
+    <tr>
+      <td>Information you do not have permission to share</td>
+      <td>Consent matters, especially when the request involves another person.</td>
+    </tr>
+    <tr>
+      <td>Long background narratives</td>
+      <td>The main need should stay visible. A request that rambles can hide the actual prayer point.</td>
+    </tr>
+    <tr>
+      <td>Unnecessary medical, family, or financial details</td>
+      <td>More detail is not always better. Sometimes it is just more detail.</td>
+    </tr>
+    <tr>
+      <td>Anything you are not comfortable sharing publicly</td>
+      <td>If it feels too exposed, mark it private or keep it brief.</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>If a detail does not help someone pray, leave it out. That is usually the right filter. The church does not need a case file. It needs enough context to respond with care.</p>
+
+<h2>If You Are Requesting Healing, Guidance, or Comfort</h2>
+
+<p>These are the situations where people often over-explain or under-explain. The middle path is usually best.</p>
+
+<p>For healing, say what kind of prayer is needed without turning the note into a medical summary. For guidance, name the decision and the deadline if there is one. For comfort, say what kind of support would be most helpful: peace, strength, patience, reassurance, or rest.</p>
+
+<p>You can borrow one of these patterns:</p>
+
+<ul>
+  <li><strong>Healing:</strong> “Please pray for healing and wise care as I recover from treatment this week.”</li>
+  <li><strong>Guidance:</strong> “Please pray for clarity as our family considers next steps for school and work.”</li>
+  <li><strong>Comfort:</strong> “Please pray for comfort, stability, and help with the next few days.”</li>
+  <li><strong>Strength:</strong> “Please pray for strength to stay steady through a difficult season.”</li>
+</ul>
+
+<p>If you want to keep a request private but still specific, say that directly:</p>
+
+<blockquote>
+  <p>“Please pray for healing for a family member this week. We are not ready to share details publicly, so please keep this private.”</p>
+</blockquote>
+
+<p>That kind of wording does two jobs at once. It gives the church a prayer focus and sets a boundary without making the request awkward.</p>
+
+<p>For a broader biblical frame, <a href="https://www.biblegateway.com/passage/?search=James+5%3A16&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">James 5:16</a> connects prayer with honest confession and mutual care. The point is not performance. The point is trust and clarity.</p>
+
+<h2>If You Are Submitting for Someone Else</h2>
+
+<p>People often ask for prayer on behalf of a spouse, child, parent, friend, or coworker. That is normal. The key is to say two things clearly: your relationship to the person and whether you have permission to share the request.</p>
+
+<p>Useful wording looks like this:</p>
+
+<ul>
+  <li><strong>With consent:</strong> “Please pray for my father, who gave me permission to share that he has a procedure next week.”</li>
+  <li><strong>Without detail:</strong> “Please pray for a friend who is facing a hard family situation.”</li>
+  <li><strong>For a child:</strong> “Please pray for our son as he starts treatment. We are asking for peace and wisdom.”</li>
+</ul>
+
+<p>What matters here is not formality. It is trust. If you are speaking for someone else, do not overshare just because you can. Use the smallest amount of information that still tells the church how to pray.</p>
+
+<p>If consent is unclear, keep the request general and private. That is the safer default. You can always add detail later if permission is granted and the situation changes.</p>
+
+<h2>Sharing Preferences: Public Prayer vs. Private Request</h2>
+
+<p>Not every request belongs in the same channel. A church needs both public prayer and private care, but they are not the same thing. Choosing the right lane keeps the request useful.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Sharing choice</th>
+      <th>Best when</th>
+      <th>What to say</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Public prayer</td>
+      <td>The need is general and you are comfortable with broader church awareness.</td>
+      <td>“Please pray for our family this week as we travel.”</td>
+    </tr>
+    <tr>
+      <td>Private request</td>
+      <td>The matter is sensitive, personal, or not ready for wider sharing.</td>
+      <td>“Please keep this private and pray for wisdom as we work through a family matter.”</td>
+    </tr>
+    <tr>
+      <td>Limited sharing</td>
+      <td>You want prayer but do not want every detail repeated.</td>
+      <td>“You may share the general need, but please leave out the details.”</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>If you are unsure, choose the more private option. That is the conservative decision and usually the right one. It is easier to expand a request later than to retract details after they have already gone farther than you intended.</p>
+
+<p>If the request becomes something broader for the church to know about, you can also look to the <a href="/news.html">News</a> page for public updates. That page is for church communication, not a place to assume personal details will be posted. Public and personal are not the same category, even when the same people are involved.</p>
+
+<h2>How to Submit</h2>
+
+<p>Once your request is ready, use the church’s normal contact paths. The simplest route is usually the <a href="/contacts.html">Contacts</a> page. If you prefer a form-based route, use <a href="/contact.php">Contact Us</a>. Either way, keep the message short, specific, and consistent with the privacy level you chose.</p>
+
+<p>A helpful submission usually has three parts:</p>
+
+<ol>
+  <li><strong>The request itself:</strong> one or two clear sentences.</li>
+  <li><strong>Your privacy note:</strong> public, private, or limited sharing.</li>
+  <li><strong>A follow-up option:</strong> a phone number or email if you want someone to reach back out.</li>
+</ol>
+
+<p>What happens after that? In practical terms, the church receives the note, reads the request, and handles it according to the communication path and privacy preference you provided. If more information is needed, someone may follow up. If no follow-up is needed, the request can still be prayed over without extra drama. That is usually the best case. Prayer requests are not package tracking.</p>
+
+<p>Do not build your wording around a guaranteed response time or a guaranteed outcome. A church can promise care and diligence. It cannot promise the timing of every answer. Keep the focus on the request itself, and keep praying while the message moves through the normal process.</p>
+
+<p>If you need more than a brief prayer note, say so. A sentence like “We would appreciate a follow-up conversation if possible” gives the church a better signal than a wall of text. If the matter is urgent, say that plainly near the top of the message. Simple language wins here.</p>
+
+<h2>A Short Checklist Before You Send</h2>
+
+<ul>
+  <li>Is the request clear in one sentence?</li>
+  <li>Did you include the type of prayer needed?</li>
+  <li>Did you leave out anything private or unnecessary?</li>
+  <li>Did you note whether the request is public, private, or limited?</li>
+  <li>If it is for someone else, did you mention your relationship and consent?</li>
+  <li>If timing matters, did you include the relevant date or timeframe?</li>
+</ul>
+
+<p>If you can answer yes to those six questions, the request is probably ready. There is no prize for over-writing it.</p>
+
+<h2>Common Mistakes That Make Requests Harder to Use</h2>
+
+<p>Most weak prayer requests fail for ordinary reasons, not dramatic ones. The note is too vague, too long, too private in the wrong place, or too public for the situation. Clean that up before you send it and you save everyone time.</p>
+
+<ul>
+  <li><strong>Leaving out the actual request:</strong> “Please pray for my family” is not enough by itself. Add the reason.</li>
+  <li><strong>Writing a full explanation first:</strong> the prayer point should show up in the first sentence, not after three paragraphs.</li>
+  <li><strong>Using code words:</strong> if the church has to decode your message, it is not a clear request.</li>
+  <li><strong>Sharing too much detail:</strong> more information is not always more help. Sometimes it is just more exposure.</li>
+  <li><strong>Forgetting the privacy note:</strong> public, private, or limited sharing should never be a guessing game.</li>
+</ul>
+
+<p>A practical test helps here: read the request out loud once. If it sounds muddled, you probably wrote too much or too little. Trim it until the sentence does the job.</p>
+
+<h2>Three Finished Examples</h2>
+
+<p>If you would rather copy a complete version than build one piece by piece, use one of these as a model:</p>
+
+<blockquote>
+  <p><strong>Example 1:</strong> “Please pray for my mother as she prepares for surgery on Monday. We are asking for peace, skill for the doctors, and a smooth recovery. Please keep this private.”</p>
+</blockquote>
+
+<blockquote>
+  <p><strong>Example 2:</strong> “Please pray for our family this month as we handle a move, a new school schedule, and a lot of change. We would appreciate wisdom and steadiness. The general request may be shared, but please leave out details.”</p>
+</blockquote>
+
+<blockquote>
+  <p><strong>Example 3:</strong> “Please pray for a friend who is grieving. I have permission to ask for prayer, but not to share more details publicly. Please pray for comfort and rest.”</p>
+</blockquote>
+
+<p>These examples are short for a reason. They say what is needed, when it matters, and how public the request may be. That is the job.</p>
+
+<p>If you need help thinking through what kind of support fits the situation, the <a href="/resources">Resources</a> page is a sensible next stop. It will not solve every problem, which is a rare and refreshing limitation for a church website.</p>
+
+<h2>Closing Encouragement</h2>
+
+<p>A good prayer request is not fancy. It is faithful, clear, and respectful. If you keep the message focused on the need, the timing, and the privacy level, you make it easier for the church to do what churches are supposed to do: pray, care, and respond with wisdom.</p>
+
+<p>Start with the <a href="/contacts.html">Contacts</a> page or <a href="/contact.php">Contact Us</a> form, keep your wording simple, and let the church know whether the request should stay private. If you want to think through other next steps while you wait, the <a href="/resources">Resources</a> page can point you to additional support, and <a href="/news.html">News</a> can help you stay aware of broader church updates.</p>
+
+<p>Finally, keep praying after you submit. That part still matters. The church can handle the message, but you should still bring the burden to God directly. <a href="https://www.biblegateway.com/passage/?search=1+Thessalonians+5%3A17&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">1 Thessalonians 5:17</a> keeps the instruction short for a reason.</p>

diff --git a//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html
new file mode 100644
index 0000000000000000000000000000000000000000..ba0db7a98ca7aaf1f97d1e0d7779b046be5e686a
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html
@@ -0,0 +1,281 @@
+<p><strong><em>A prayer request does not need to sound polished. It needs to be clear enough for the church to pray without guessing.</em></strong></p>
+
+<p><strong>By Marcus Reed</strong> | Updated June 23, 2026</p>
+
+<p>When people sit down to write a prayer request, the same practical questions come up fast: How much context is enough? What should stay private? Can I ask for prayer for someone else? And how do I make the request easy for the church to read and use well?</p>
+
+<p>Those are good questions. Prayer is not a performance, and the Bible treats it that way. <a href="https://www.biblegateway.com/passage/?search=Philippians+4%3A6-7&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">Philippians 4:6-7</a> points toward honest, direct prayer; <a href="https://www.biblegateway.com/passage/?search=Matthew+6%3A6&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">Matthew 6:6</a> reminds believers that prayer can also be private and disciplined. A useful church request follows the same logic: enough context to be specific, enough restraint to protect what should stay private, and enough clarity that people can pray with purpose.</p>
+
+<p>If you want the shortest path, start with the church <a href="/contacts.html">Contacts</a> page, or use the site's <a href="/contact.php">contact form</a> if that is more convenient. If you are looking for broader church information while you prepare your message, the <a href="/resources">Resources</a> page is a good place to get oriented.</p>
+
+<figure class="wp-block-image size-large">
+  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg" alt="Planning materials on a desk with a calendar and smartphone for Sunday service coordination" class="wp-image-76" style="width:100%;height:auto;" />
+  <figcaption>A simple request starts with the same discipline as any good plan: enough detail to be useful, not so much that the point gets buried.</figcaption>
+</figure>
+
+<h2>Why We Ask for a Little Context</h2>
+
+<p>Prayer teams do better with signal than with noise. A short note that says what is happening, who it affects, and what kind of prayer is needed gives the church something concrete to carry. A vague request forces people to fill in the blanks, and that is where confusion starts.</p>
+
+<p>Context also helps the church handle requests appropriately. Some needs are fine to share broadly. Some should stay with a limited group. Some should be treated as private pastoral matters. The more clearly you state your preference, the less guesswork is required on the other side.</p>
+
+<p>There is a third reason, and it is the one people often skip: context respects the person who is asking for prayer. A request that is too thin can feel detached; a request that is too detailed can feel exposed. The goal is not to narrate your whole life. The goal is to give enough information for faithful prayer and responsible care.</p>
+
+<h2>A Quick Template You Can Copy and Paste</h2>
+
+<p>If you are not sure where to start, use this format. It is simple on purpose.</p>
+
+<pre><code>Name: [Your name]
+Request: [One short sentence about the need]
+Details: [Only the facts that help people pray well]
+Timeframe: [Today, this week, on [date], or ongoing]
+Ongoing vs. one-time: [One-time / recurring]
+Sharing preference: [Public / private / limited sharing]
+Contact: [Optional phone or email if a follow-up may help]</code></pre>
+
+<p>That is enough for most situations. If you need more privacy, leave out the contact line and keep the description general. If the request is for someone else, say so clearly in the first line so the church understands the relationship and the permission level.</p>
+
+<p>A few quick definitions help here:</p>
+
+<ul>
+  <li><strong>Public prayer:</strong> a request that can be shared more broadly with the church.</li>
+  <li><strong>Private request:</strong> a request that should stay with a smaller, limited group.</li>
+  <li><strong>Ongoing request:</strong> a situation that needs repeated prayer over time.</li>
+  <li><strong>Timeframe:</strong> when the need is happening or when support is most important.</li>
+</ul>
+
+<p>Think of the template as a floor, not a ceiling. You can always add a sentence, but you do not need to write a paragraph for every line. A church can work with a concise request. It cannot work with a mystery wrapped in spiritual language.</p>
+
+<h2>Do Include</h2>
+
+<p>The most useful prayer requests include the facts that actually help someone pray.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Include this</th>
+      <th>Why it helps</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>A clear request in one sentence</td>
+      <td>It tells the reader exactly what kind of prayer you are asking for.</td>
+    </tr>
+    <tr>
+      <td>Specific needs or concerns</td>
+      <td>“Healing,” “wisdom,” “travel safety,” or “comfort” are easier to pray for than a vague concern.</td>
+    </tr>
+    <tr>
+      <td>Relevant dates or timeframes</td>
+      <td>Dates help the church know what matters now, this week, or later.</td>
+    </tr>
+    <tr>
+      <td>Whether the request is confidential</td>
+      <td>Privacy preferences should be stated plainly, not left to interpretation.</td>
+    </tr>
+    <tr>
+      <td>Whether the request is ongoing</td>
+      <td>A continuing need may be placed on a prayer list differently from a one-time update.</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>One useful habit: write the request as if someone else has to read it once, understand it immediately, and pray right away. That is the operational standard. Church communication is not a scavenger hunt.</p>
+
+<p>Here are a few examples of good, concise wording:</p>
+
+<ul>
+  <li><strong>Healing:</strong> “Please pray for Sarah as she prepares for surgery on Thursday. We are asking for peace, skill for the medical team, and steady recovery.”</li>
+  <li><strong>Family support:</strong> “Please pray for our family during a difficult week. We need wisdom, patience, and rest.”</li>
+  <li><strong>Guidance:</strong> “Please pray for discernment as I make a work decision by the end of the month.”</li>
+  <li><strong>Comfort:</strong> “Please pray for comfort and strength after a recent loss. This can stay private.”</li>
+</ul>
+
+<p>Notice what is not happening there. There is no long backstory, no dramatic language, and no pressure to explain every detail. The request stays readable.</p>
+
+<h2>Don’t Include</h2>
+
+<p>Good judgment matters. A prayer request is not the right place for everything.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Leave this out</th>
+      <th>Why to avoid it</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Overly personal details</td>
+      <td>If it would make you uncomfortable to read out loud, it probably should not be in the request.</td>
+    </tr>
+    <tr>
+      <td>Information you do not have permission to share</td>
+      <td>Consent matters, especially when the request involves another person.</td>
+    </tr>
+    <tr>
+      <td>Long background narratives</td>
+      <td>The main need should stay visible. A request that rambles can hide the actual prayer point.</td>
+    </tr>
+    <tr>
+      <td>Unnecessary medical, family, or financial details</td>
+      <td>More detail is not always better. Sometimes it is just more detail.</td>
+    </tr>
+    <tr>
+      <td>Anything you are not comfortable sharing publicly</td>
+      <td>If it feels too exposed, mark it private or keep it brief.</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>If a detail does not help someone pray, leave it out. That is usually the right filter. The church does not need a case file. It needs enough context to respond with care.</p>
+
+<h2>If You Are Requesting Healing, Guidance, or Comfort</h2>
+
+<p>These are the situations where people often over-explain or under-explain. The middle path is usually best.</p>
+
+<p>For healing, say what kind of prayer is needed without turning the note into a medical summary. For guidance, name the decision and the deadline if there is one. For comfort, say what kind of support would be most helpful: peace, strength, patience, reassurance, or rest.</p>
+
+<p>You can borrow one of these patterns:</p>
+
+<ul>
+  <li><strong>Healing:</strong> “Please pray for healing and wise care as I recover from treatment this week.”</li>
+  <li><strong>Guidance:</strong> “Please pray for clarity as our family considers next steps for school and work.”</li>
+  <li><strong>Comfort:</strong> “Please pray for comfort, stability, and help with the next few days.”</li>
+  <li><strong>Strength:</strong> “Please pray for strength to stay steady through a difficult season.”</li>
+</ul>
+
+<p>If you want to keep a request private but still specific, say that directly:</p>
+
+<blockquote>
+  <p>“Please pray for healing for a family member this week. We are not ready to share details publicly, so please keep this private.”</p>
+</blockquote>
+
+<p>That kind of wording does two jobs at once. It gives the church a prayer focus and sets a boundary without making the request awkward.</p>
+
+<p>For a broader biblical frame, <a href="https://www.biblegateway.com/passage/?search=James+5%3A16&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">James 5:16</a> connects prayer with honest confession and mutual care. The point is not performance. The point is trust and clarity.</p>
+
+<h2>If You Are Submitting for Someone Else</h2>
+
+<p>People often ask for prayer on behalf of a spouse, child, parent, friend, or coworker. That is normal. The key is to say two things clearly: your relationship to the person and whether you have permission to share the request.</p>
+
+<p>Useful wording looks like this:</p>
+
+<ul>
+  <li><strong>With consent:</strong> “Please pray for my father, who gave me permission to share that he has a procedure next week.”</li>
+  <li><strong>Without detail:</strong> “Please pray for a friend who is facing a hard family situation.”</li>
+  <li><strong>For a child:</strong> “Please pray for our son as he starts treatment. We are asking for peace and wisdom.”</li>
+</ul>
+
+<p>What matters here is not formality. It is trust. If you are speaking for someone else, do not overshare just because you can. Use the smallest amount of information that still tells the church how to pray.</p>
+
+<p>If consent is unclear, keep the request general and private. That is the safer default. You can always add detail later if permission is granted and the situation changes.</p>
+
+<h2>Sharing Preferences: Public Prayer vs. Private Request</h2>
+
+<p>Not every request belongs in the same channel. A church needs both public prayer and private care, but they are not the same thing. Choosing the right lane keeps the request useful.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Sharing choice</th>
+      <th>Best when</th>
+      <th>What to say</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Public prayer</td>
+      <td>The need is general and you are comfortable with broader church awareness.</td>
+      <td>“Please pray for our family this week as we travel.”</td>
+    </tr>
+    <tr>
+      <td>Private request</td>
+      <td>The matter is sensitive, personal, or not ready for wider sharing.</td>
+      <td>“Please keep this private and pray for wisdom as we work through a family matter.”</td>
+    </tr>
+    <tr>
+      <td>Limited sharing</td>
+      <td>You want prayer but do not want every detail repeated.</td>
+      <td>“You may share the general need, but please leave out the details.”</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>If you are unsure, choose the more private option. That is the conservative decision and usually the right one. It is easier to expand a request later than to retract details after they have already gone farther than you intended.</p>
+
+<p>If the request becomes something broader for the church to know about, you can also look to the <a href="/news.html">News</a> page for public updates. That page is for church communication, not a place to assume personal details will be posted. Public and personal are not the same category, even when the same people are involved.</p>
+
+<h2>How to Submit</h2>
+
+<p>Once your request is ready, use the church’s normal contact paths. The simplest route is usually the <a href="/contacts.html">Contacts</a> page. If you prefer a form-based route, use <a href="/contact.php">Contact Us</a>. Either way, keep the message short, specific, and consistent with the privacy level you chose.</p>
+
+<p>A helpful submission usually has three parts:</p>
+
+<ol>
+  <li><strong>The request itself:</strong> one or two clear sentences.</li>
+  <li><strong>Your privacy note:</strong> public, private, or limited sharing.</li>
+  <li><strong>A follow-up option:</strong> a phone number or email if you want someone to reach back out.</li>
+</ol>
+
+<p>What happens after that? In practical terms, the church receives the note, reads the request, and handles it according to the communication path and privacy preference you provided. If more information is needed, someone may follow up. If no follow-up is needed, the request can still be prayed over without extra drama. That is usually the best case. Prayer requests are not package tracking.</p>
+
+<p>Do not build your wording around a guaranteed response time or a guaranteed outcome. A church can promise care and diligence. It cannot promise the timing of every answer. Keep the focus on the request itself, and keep praying while the message moves through the normal process.</p>
+
+<p>If you need more than a brief prayer note, say so. A sentence like “We would appreciate a follow-up conversation if possible” gives the church a better signal than a wall of text. If the matter is urgent, say that plainly near the top of the message. Simple language wins here.</p>
+
+<h2>A Short Checklist Before You Send</h2>
+
+<ul>
+  <li>Is the request clear in one sentence?</li>
+  <li>Did you include the type of prayer needed?</li>
+  <li>Did you leave out anything private or unnecessary?</li>
+  <li>Did you note whether the request is public, private, or limited?</li>
+  <li>If it is for someone else, did you mention your relationship and consent?</li>
+  <li>If timing matters, did you include the relevant date or timeframe?</li>
+</ul>
+
+<p>If you can answer yes to those six questions, the request is probably ready. There is no prize for over-writing it.</p>
+
+<h2>Common Mistakes That Make Requests Harder to Use</h2>
+
+<p>Most weak prayer requests fail for ordinary reasons, not dramatic ones. The note is too vague, too long, too private in the wrong place, or too public for the situation. Clean that up before you send it and you save everyone time.</p>
+
+<ul>
+  <li><strong>Leaving out the actual request:</strong> “Please pray for my family” is not enough by itself. Add the reason.</li>
+  <li><strong>Writing a full explanation first:</strong> the prayer point should show up in the first sentence, not after three paragraphs.</li>
+  <li><strong>Using code words:</strong> if the church has to decode your message, it is not a clear request.</li>
+  <li><strong>Sharing too much detail:</strong> more information is not always more help. Sometimes it is just more exposure.</li>
+  <li><strong>Forgetting the privacy note:</strong> public, private, or limited sharing should never be a guessing game.</li>
+</ul>
+
+<p>A practical test helps here: read the request out loud once. If it sounds muddled, you probably wrote too much or too little. Trim it until the sentence does the job.</p>
+
+<h2>Three Finished Examples</h2>
+
+<p>If you would rather copy a complete version than build one piece by piece, use one of these as a model:</p>
+
+<blockquote>
+  <p><strong>Example 1:</strong> “Please pray for my mother as she prepares for surgery on Monday. We are asking for peace, skill for the doctors, and a smooth recovery. Please keep this private.”</p>
+</blockquote>
+
+<blockquote>
+  <p><strong>Example 2:</strong> “Please pray for our family this month as we handle a move, a new school schedule, and a lot of change. We would appreciate wisdom and steadiness. The general request may be shared, but please leave out details.”</p>
+</blockquote>
+
+<blockquote>
+  <p><strong>Example 3:</strong> “Please pray for a friend who is grieving. I have permission to ask for prayer, but not to share more details publicly. Please pray for comfort and rest.”</p>
+</blockquote>
+
+<p>These examples are short for a reason. They say what is needed, when it matters, and how public the request may be. That is the job.</p>
+
+<p>If you need help thinking through what kind of support fits the situation, the <a href="/resources">Resources</a> page is a sensible next stop. It will not solve every problem, which is a rare and refreshing limitation for a church website.</p>
+
+<h2>Closing Encouragement</h2>
+
+<p>A good prayer request is not fancy. It is faithful, clear, and respectful. If you keep the message focused on the need, the timing, and the privacy level, you make it easier for the church to do what churches are supposed to do: pray, care, and respond with wisdom.</p>
+
+<p>Start with the <a href="/contacts.html">Contacts</a> page or <a href="/contact.php">Contact Us</a> form, keep your wording simple, and let the church know whether the request should stay private. If you want to think through other next steps while you wait, the <a href="/resources">Resources</a> page can point you to additional support, and <a href="/news.html">News</a> can help you stay aware of broader church updates.</p>
+
+<p>Finally, keep praying after you submit. That part still matters. The church can handle the message, but you should still bring the burden to God directly. <a href="https://www.biblegateway.com/passage/?search=1+Thessalonians+5%3A17&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">1 Thessalonians 5:17</a> keeps the instruction short for a reason.</p>

exec
/bin/bash -lc 'wc -w wp-content/uploads/flatlogic-article-tasks/job-506/article.html' in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
2555 wp-content/uploads/flatlogic-article-tasks/job-506/article.html

diff --git a//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html
new file mode 100644
index 0000000000000000000000000000000000000000..ba0db7a98ca7aaf1f97d1e0d7779b046be5e686a
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html
@@ -0,0 +1,281 @@
+<p><strong><em>A prayer request does not need to sound polished. It needs to be clear enough for the church to pray without guessing.</em></strong></p>
+
+<p><strong>By Marcus Reed</strong> | Updated June 23, 2026</p>
+
+<p>When people sit down to write a prayer request, the same practical questions come up fast: How much context is enough? What should stay private? Can I ask for prayer for someone else? And how do I make the request easy for the church to read and use well?</p>
+
+<p>Those are good questions. Prayer is not a performance, and the Bible treats it that way. <a href="https://www.biblegateway.com/passage/?search=Philippians+4%3A6-7&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">Philippians 4:6-7</a> points toward honest, direct prayer; <a href="https://www.biblegateway.com/passage/?search=Matthew+6%3A6&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">Matthew 6:6</a> reminds believers that prayer can also be private and disciplined. A useful church request follows the same logic: enough context to be specific, enough restraint to protect what should stay private, and enough clarity that people can pray with purpose.</p>
+
+<p>If you want the shortest path, start with the church <a href="/contacts.html">Contacts</a> page, or use the site's <a href="/contact.php">contact form</a> if that is more convenient. If you are looking for broader church information while you prepare your message, the <a href="/resources">Resources</a> page is a good place to get oriented.</p>
+
+<figure class="wp-block-image size-large">
+  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg" alt="Planning materials on a desk with a calendar and smartphone for Sunday service coordination" class="wp-image-76" style="width:100%;height:auto;" />
+  <figcaption>A simple request starts with the same discipline as any good plan: enough detail to be useful, not so much that the point gets buried.</figcaption>
+</figure>
+
+<h2>Why We Ask for a Little Context</h2>
+
+<p>Prayer teams do better with signal than with noise. A short note that says what is happening, who it affects, and what kind of prayer is needed gives the church something concrete to carry. A vague request forces people to fill in the blanks, and that is where confusion starts.</p>
+
+<p>Context also helps the church handle requests appropriately. Some needs are fine to share broadly. Some should stay with a limited group. Some should be treated as private pastoral matters. The more clearly you state your preference, the less guesswork is required on the other side.</p>
+
+<p>There is a third reason, and it is the one people often skip: context respects the person who is asking for prayer. A request that is too thin can feel detached; a request that is too detailed can feel exposed. The goal is not to narrate your whole life. The goal is to give enough information for faithful prayer and responsible care.</p>
+
+<h2>A Quick Template You Can Copy and Paste</h2>
+
+<p>If you are not sure where to start, use this format. It is simple on purpose.</p>
+
+<pre><code>Name: [Your name]
+Request: [One short sentence about the need]
+Details: [Only the facts that help people pray well]
+Timeframe: [Today, this week, on [date], or ongoing]
+Ongoing vs. one-time: [One-time / recurring]
+Sharing preference: [Public / private / limited sharing]
+Contact: [Optional phone or email if a follow-up may help]</code></pre>
+
+<p>That is enough for most situations. If you need more privacy, leave out the contact line and keep the description general. If the request is for someone else, say so clearly in the first line so the church understands the relationship and the permission level.</p>
+
+<p>A few quick definitions help here:</p>
+
+<ul>
+  <li><strong>Public prayer:</strong> a request that can be shared more broadly with the church.</li>
+  <li><strong>Private request:</strong> a request that should stay with a smaller, limited group.</li>
+  <li><strong>Ongoing request:</strong> a situation that needs repeated prayer over time.</li>
+  <li><strong>Timeframe:</strong> when the need is happening or when support is most important.</li>
+</ul>
+
+<p>Think of the template as a floor, not a ceiling. You can always add a sentence, but you do not need to write a paragraph for every line. A church can work with a concise request. It cannot work with a mystery wrapped in spiritual language.</p>
+
+<h2>Do Include</h2>
+
+<p>The most useful prayer requests include the facts that actually help someone pray.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Include this</th>
+      <th>Why it helps</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>A clear request in one sentence</td>
+      <td>It tells the reader exactly what kind of prayer you are asking for.</td>
+    </tr>
+    <tr>
+      <td>Specific needs or concerns</td>
+      <td>“Healing,” “wisdom,” “travel safety,” or “comfort” are easier to pray for than a vague concern.</td>
+    </tr>
+    <tr>
+      <td>Relevant dates or timeframes</td>
+      <td>Dates help the church know what matters now, this week, or later.</td>
+    </tr>
+    <tr>
+      <td>Whether the request is confidential</td>
+      <td>Privacy preferences should be stated plainly, not left to interpretation.</td>
+    </tr>
+    <tr>
+      <td>Whether the request is ongoing</td>
+      <td>A continuing need may be placed on a prayer list differently from a one-time update.</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>One useful habit: write the request as if someone else has to read it once, understand it immediately, and pray right away. That is the operational standard. Church communication is not a scavenger hunt.</p>
+
+<p>Here are a few examples of good, concise wording:</p>
+
+<ul>
+  <li><strong>Healing:</strong> “Please pray for Sarah as she prepares for surgery on Thursday. We are asking for peace, skill for the medical team, and steady recovery.”</li>
+  <li><strong>Family support:</strong> “Please pray for our family during a difficult week. We need wisdom, patience, and rest.”</li>
+  <li><strong>Guidance:</strong> “Please pray for discernment as I make a work decision by the end of the month.”</li>
+  <li><strong>Comfort:</strong> “Please pray for comfort and strength after a recent loss. This can stay private.”</li>
+</ul>
+
+<p>Notice what is not happening there. There is no long backstory, no dramatic language, and no pressure to explain every detail. The request stays readable.</p>
+
+<h2>Don’t Include</h2>
+
+<p>Good judgment matters. A prayer request is not the right place for everything.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Leave this out</th>
+      <th>Why to avoid it</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Overly personal details</td>
+      <td>If it would make you uncomfortable to read out loud, it probably should not be in the request.</td>
+    </tr>
+    <tr>
+      <td>Information you do not have permission to share</td>
+      <td>Consent matters, especially when the request involves another person.</td>
+    </tr>
+    <tr>
+      <td>Long background narratives</td>
+      <td>The main need should stay visible. A request that rambles can hide the actual prayer point.</td>
+    </tr>
+    <tr>
+      <td>Unnecessary medical, family, or financial details</td>
+      <td>More detail is not always better. Sometimes it is just more detail.</td>
+    </tr>
+    <tr>
+      <td>Anything you are not comfortable sharing publicly</td>
+      <td>If it feels too exposed, mark it private or keep it brief.</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>If a detail does not help someone pray, leave it out. That is usually the right filter. The church does not need a case file. It needs enough context to respond with care.</p>
+
+<h2>If You Are Requesting Healing, Guidance, or Comfort</h2>
+
+<p>These are the situations where people often over-explain or under-explain. The middle path is usually best.</p>
+
+<p>For healing, say what kind of prayer is needed without turning the note into a medical summary. For guidance, name the decision and the deadline if there is one. For comfort, say what kind of support would be most helpful: peace, strength, patience, reassurance, or rest.</p>
+
+<p>You can borrow one of these patterns:</p>
+
+<ul>
+  <li><strong>Healing:</strong> “Please pray for healing and wise care as I recover from treatment this week.”</li>
+  <li><strong>Guidance:</strong> “Please pray for clarity as our family considers next steps for school and work.”</li>
+  <li><strong>Comfort:</strong> “Please pray for comfort, stability, and help with the next few days.”</li>
+  <li><strong>Strength:</strong> “Please pray for strength to stay steady through a difficult season.”</li>
+</ul>
+
+<p>If you want to keep a request private but still specific, say that directly:</p>
+
+<blockquote>
+  <p>“Please pray for healing for a family member this week. We are not ready to share details publicly, so please keep this private.”</p>
+</blockquote>
+
+<p>That kind of wording does two jobs at once. It gives the church a prayer focus and sets a boundary without making the request awkward.</p>
+
+<p>For a broader biblical frame, <a href="https://www.biblegateway.com/passage/?search=James+5%3A16&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">James 5:16</a> connects prayer with honest confession and mutual care. The point is not performance. The point is trust and clarity.</p>
+
+<h2>If You Are Submitting for Someone Else</h2>
+
+<p>People often ask for prayer on behalf of a spouse, child, parent, friend, or coworker. That is normal. The key is to say two things clearly: your relationship to the person and whether you have permission to share the request.</p>
+
+<p>Useful wording looks like this:</p>
+
+<ul>
+  <li><strong>With consent:</strong> “Please pray for my father, who gave me permission to share that he has a procedure next week.”</li>
+  <li><strong>Without detail:</strong> “Please pray for a friend who is facing a hard family situation.”</li>
+  <li><strong>For a child:</strong> “Please pray for our son as he starts treatment. We are asking for peace and wisdom.”</li>
+</ul>
+
+<p>What matters here is not formality. It is trust. If you are speaking for someone else, do not overshare just because you can. Use the smallest amount of information that still tells the church how to pray.</p>
+
+<p>If consent is unclear, keep the request general and private. That is the safer default. You can always add detail later if permission is granted and the situation changes.</p>
+
+<h2>Sharing Preferences: Public Prayer vs. Private Request</h2>
+
+<p>Not every request belongs in the same channel. A church needs both public prayer and private care, but they are not the same thing. Choosing the right lane keeps the request useful.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Sharing choice</th>
+      <th>Best when</th>
+      <th>What to say</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Public prayer</td>
+      <td>The need is general and you are comfortable with broader church awareness.</td>
+      <td>“Please pray for our family this week as we travel.”</td>
+    </tr>
+    <tr>
+      <td>Private request</td>
+      <td>The matter is sensitive, personal, or not ready for wider sharing.</td>
+      <td>“Please keep this private and pray for wisdom as we work through a family matter.”</td>
+    </tr>
+    <tr>
+      <td>Limited sharing</td>
+      <td>You want prayer but do not want every detail repeated.</td>
+      <td>“You may share the general need, but please leave out the details.”</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>If you are unsure, choose the more private option. That is the conservative decision and usually the right one. It is easier to expand a request later than to retract details after they have already gone farther than you intended.</p>
+
+<p>If the request becomes something broader for the church to know about, you can also look to the <a href="/news.html">News</a> page for public updates. That page is for church communication, not a place to assume personal details will be posted. Public and personal are not the same category, even when the same people are involved.</p>
+
+<h2>How to Submit</h2>
+
+<p>Once your request is ready, use the church’s normal contact paths. The simplest route is usually the <a href="/contacts.html">Contacts</a> page. If you prefer a form-based route, use <a href="/contact.php">Contact Us</a>. Either way, keep the message short, specific, and consistent with the privacy level you chose.</p>
+
+<p>A helpful submission usually has three parts:</p>
+
+<ol>
+  <li><strong>The request itself:</strong> one or two clear sentences.</li>
+  <li><strong>Your privacy note:</strong> public, private, or limited sharing.</li>
+  <li><strong>A follow-up option:</strong> a phone number or email if you want someone to reach back out.</li>
+</ol>
+
+<p>What happens after that? In practical terms, the church receives the note, reads the request, and handles it according to the communication path and privacy preference you provided. If more information is needed, someone may follow up. If no follow-up is needed, the request can still be prayed over without extra drama. That is usually the best case. Prayer requests are not package tracking.</p>
+
+<p>Do not build your wording around a guaranteed response time or a guaranteed outcome. A church can promise care and diligence. It cannot promise the timing of every answer. Keep the focus on the request itself, and keep praying while the message moves through the normal process.</p>
+
+<p>If you need more than a brief prayer note, say so. A sentence like “We would appreciate a follow-up conversation if possible” gives the church a better signal than a wall of text. If the matter is urgent, say that plainly near the top of the message. Simple language wins here.</p>
+
+<h2>A Short Checklist Before You Send</h2>
+
+<ul>
+  <li>Is the request clear in one sentence?</li>
+  <li>Did you include the type of prayer needed?</li>
+  <li>Did you leave out anything private or unnecessary?</li>
+  <li>Did you note whether the request is public, private, or limited?</li>
+  <li>If it is for someone else, did you mention your relationship and consent?</li>
+  <li>If timing matters, did you include the relevant date or timeframe?</li>
+</ul>
+
+<p>If you can answer yes to those six questions, the request is probably ready. There is no prize for over-writing it.</p>
+
+<h2>Common Mistakes That Make Requests Harder to Use</h2>
+
+<p>Most weak prayer requests fail for ordinary reasons, not dramatic ones. The note is too vague, too long, too private in the wrong place, or too public for the situation. Clean that up before you send it and you save everyone time.</p>
+
+<ul>
+  <li><strong>Leaving out the actual request:</strong> “Please pray for my family” is not enough by itself. Add the reason.</li>
+  <li><strong>Writing a full explanation first:</strong> the prayer point should show up in the first sentence, not after three paragraphs.</li>
+  <li><strong>Using code words:</strong> if the church has to decode your message, it is not a clear request.</li>
+  <li><strong>Sharing too much detail:</strong> more information is not always more help. Sometimes it is just more exposure.</li>
+  <li><strong>Forgetting the privacy note:</strong> public, private, or limited sharing should never be a guessing game.</li>
+</ul>
+
+<p>A practical test helps here: read the request out loud once. If it sounds muddled, you probably wrote too much or too little. Trim it until the sentence does the job.</p>
+
+<h2>Three Finished Examples</h2>
+
+<p>If you would rather copy a complete version than build one piece by piece, use one of these as a model:</p>
+
+<blockquote>
+  <p><strong>Example 1:</strong> “Please pray for my mother as she prepares for surgery on Monday. We are asking for peace, skill for the doctors, and a smooth recovery. Please keep this private.”</p>
+</blockquote>
+
+<blockquote>
+  <p><strong>Example 2:</strong> “Please pray for our family this month as we handle a move, a new school schedule, and a lot of change. We would appreciate wisdom and steadiness. The general request may be shared, but please leave out details.”</p>
+</blockquote>
+
+<blockquote>
+  <p><strong>Example 3:</strong> “Please pray for a friend who is grieving. I have permission to ask for prayer, but not to share more details publicly. Please pray for comfort and rest.”</p>
+</blockquote>
+
+<p>These examples are short for a reason. They say what is needed, when it matters, and how public the request may be. That is the job.</p>
+
+<p>If you need help thinking through what kind of support fits the situation, the <a href="/resources">Resources</a> page is a sensible next stop. It will not solve every problem, which is a rare and refreshing limitation for a church website.</p>
+
+<h2>Closing Encouragement</h2>
+
+<p>A good prayer request is not fancy. It is faithful, clear, and respectful. If you keep the message focused on the need, the timing, and the privacy level, you make it easier for the church to do what churches are supposed to do: pray, care, and respond with wisdom.</p>
+
+<p>Start with the <a href="/contacts.html">Contacts</a> page or <a href="/contact.php">Contact Us</a> form, keep your wording simple, and let the church know whether the request should stay private. If you want to think through other next steps while you wait, the <a href="/resources">Resources</a> page can point you to additional support, and <a href="/news.html">News</a> can help you stay aware of broader church updates.</p>
+
+<p>Finally, keep praying after you submit. That part still matters. The church can handle the message, but you should still bring the burden to God directly. <a href="https://www.biblegateway.com/passage/?search=1+Thessalonians+5%3A17&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">1 Thessalonians 5:17</a> keeps the instruction short for a reason.</p>

codex
The article is at the right length now. I’m publishing it with Marcus Reed as author, then I’ll set the featured image and verify the rendered post.
exec
/bin/bash -lc 'post_id=$(wp post create --post_type=post --post_status=publish --post_title='"'How to Prepare a Prayer Request for Ridgecrest (A Simple, Respectful Template)' --post_name='how-to-prepare-prayer-request-template' --post_author=5 --post_excerpt='Learn how to write a meaningful prayer request for Ridgecrest Baptist Church with this practical template and guidance.' --post_content=\""'$(<wp-content/uploads/flatlogic-article-tasks/job-506/article.html)" --porcelain) && echo "$post_id"' in /home/ubuntu/apps/ridgecrestchurch.com
diff --git a//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html
new file mode 100644
index 0000000000000000000000000000000000000000..ba0db7a98ca7aaf1f97d1e0d7779b046be5e686a
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html
@@ -0,0 +1,281 @@
+<p><strong><em>A prayer request does not need to sound polished. It needs to be clear enough for the church to pray without guessing.</em></strong></p>
+
+<p><strong>By Marcus Reed</strong> | Updated June 23, 2026</p>
+
+<p>When people sit down to write a prayer request, the same practical questions come up fast: How much context is enough? What should stay private? Can I ask for prayer for someone else? And how do I make the request easy for the church to read and use well?</p>
+
+<p>Those are good questions. Prayer is not a performance, and the Bible treats it that way. <a href="https://www.biblegateway.com/passage/?search=Philippians+4%3A6-7&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">Philippians 4:6-7</a> points toward honest, direct prayer; <a href="https://www.biblegateway.com/passage/?search=Matthew+6%3A6&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">Matthew 6:6</a> reminds believers that prayer can also be private and disciplined. A useful church request follows the same logic: enough context to be specific, enough restraint to protect what should stay private, and enough clarity that people can pray with purpose.</p>
+
+<p>If you want the shortest path, start with the church <a href="/contacts.html">Contacts</a> page, or use the site's <a href="/contact.php">contact form</a> if that is more convenient. If you are looking for broader church information while you prepare your message, the <a href="/resources">Resources</a> page is a good place to get oriented.</p>
+
+<figure class="wp-block-image size-large">
+  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg" alt="Planning materials on a desk with a calendar and smartphone for Sunday service coordination" class="wp-image-76" style="width:100%;height:auto;" />
+  <figcaption>A simple request starts with the same discipline as any good plan: enough detail to be useful, not so much that the point gets buried.</figcaption>
+</figure>
+
+<h2>Why We Ask for a Little Context</h2>
+
+<p>Prayer teams do better with signal than with noise. A short note that says what is happening, who it affects, and what kind of prayer is needed gives the church something concrete to carry. A vague request forces people to fill in the blanks, and that is where confusion starts.</p>
+
+<p>Context also helps the church handle requests appropriately. Some needs are fine to share broadly. Some should stay with a limited group. Some should be treated as private pastoral matters. The more clearly you state your preference, the less guesswork is required on the other side.</p>
+
+<p>There is a third reason, and it is the one people often skip: context respects the person who is asking for prayer. A request that is too thin can feel detached; a request that is too detailed can feel exposed. The goal is not to narrate your whole life. The goal is to give enough information for faithful prayer and responsible care.</p>
+
+<h2>A Quick Template You Can Copy and Paste</h2>
+
+<p>If you are not sure where to start, use this format. It is simple on purpose.</p>
+
+<pre><code>Name: [Your name]
+Request: [One short sentence about the need]
+Details: [Only the facts that help people pray well]
+Timeframe: [Today, this week, on [date], or ongoing]
+Ongoing vs. one-time: [One-time / recurring]
+Sharing preference: [Public / private / limited sharing]
+Contact: [Optional phone or email if a follow-up may help]</code></pre>
+
+<p>That is enough for most situations. If you need more privacy, leave out the contact line and keep the description general. If the request is for someone else, say so clearly in the first line so the church understands the relationship and the permission level.</p>
+
+<p>A few quick definitions help here:</p>
+
+<ul>
+  <li><strong>Public prayer:</strong> a request that can be shared more broadly with the church.</li>
+  <li><strong>Private request:</strong> a request that should stay with a smaller, limited group.</li>
+  <li><strong>Ongoing request:</strong> a situation that needs repeated prayer over time.</li>
+  <li><strong>Timeframe:</strong> when the need is happening or when support is most important.</li>
+</ul>
+
+<p>Think of the template as a floor, not a ceiling. You can always add a sentence, but you do not need to write a paragraph for every line. A church can work with a concise request. It cannot work with a mystery wrapped in spiritual language.</p>
+
+<h2>Do Include</h2>
+
+<p>The most useful prayer requests include the facts that actually help someone pray.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Include this</th>
+      <th>Why it helps</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>A clear request in one sentence</td>
+      <td>It tells the reader exactly what kind of prayer you are asking for.</td>
+    </tr>
+    <tr>
+      <td>Specific needs or concerns</td>
+      <td>“Healing,” “wisdom,” “travel safety,” or “comfort” are easier to pray for than a vague concern.</td>
+    </tr>
+    <tr>
+      <td>Relevant dates or timeframes</td>
+      <td>Dates help the church know what matters now, this week, or later.</td>
+    </tr>
+    <tr>
+      <td>Whether the request is confidential</td>
+      <td>Privacy preferences should be stated plainly, not left to interpretation.</td>
+    </tr>
+    <tr>
+      <td>Whether the request is ongoing</td>
+      <td>A continuing need may be placed on a prayer list differently from a one-time update.</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>One useful habit: write the request as if someone else has to read it once, understand it immediately, and pray right away. That is the operational standard. Church communication is not a scavenger hunt.</p>
+
+<p>Here are a few examples of good, concise wording:</p>
+
+<ul>
+  <li><strong>Healing:</strong> “Please pray for Sarah as she prepares for surgery on Thursday. We are asking for peace, skill for the medical team, and steady recovery.”</li>
+  <li><strong>Family support:</strong> “Please pray for our family during a difficult week. We need wisdom, patience, and rest.”</li>
+  <li><strong>Guidance:</strong> “Please pray for discernment as I make a work decision by the end of the month.”</li>
+  <li><strong>Comfort:</strong> “Please pray for comfort and strength after a recent loss. This can stay private.”</li>
+</ul>
+
+<p>Notice what is not happening there. There is no long backstory, no dramatic language, and no pressure to explain every detail. The request stays readable.</p>
+
+<h2>Don’t Include</h2>
+
+<p>Good judgment matters. A prayer request is not the right place for everything.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Leave this out</th>
+      <th>Why to avoid it</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Overly personal details</td>
+      <td>If it would make you uncomfortable to read out loud, it probably should not be in the request.</td>
+    </tr>
+    <tr>
+      <td>Information you do not have permission to share</td>
+      <td>Consent matters, especially when the request involves another person.</td>
+    </tr>
+    <tr>
+      <td>Long background narratives</td>
+      <td>The main need should stay visible. A request that rambles can hide the actual prayer point.</td>
+    </tr>
+    <tr>
+      <td>Unnecessary medical, family, or financial details</td>
+      <td>More detail is not always better. Sometimes it is just more detail.</td>
+    </tr>
+    <tr>
+      <td>Anything you are not comfortable sharing publicly</td>
+      <td>If it feels too exposed, mark it private or keep it brief.</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>If a detail does not help someone pray, leave it out. That is usually the right filter. The church does not need a case file. It needs enough context to respond with care.</p>
+
+<h2>If You Are Requesting Healing, Guidance, or Comfort</h2>
+
+<p>These are the situations where people often over-explain or under-explain. The middle path is usually best.</p>
+
+<p>For healing, say what kind of prayer is needed without turning the note into a medical summary. For guidance, name the decision and the deadline if there is one. For comfort, say what kind of support would be most helpful: peace, strength, patience, reassurance, or rest.</p>
+
+<p>You can borrow one of these patterns:</p>
+
+<ul>
+  <li><strong>Healing:</strong> “Please pray for healing and wise care as I recover from treatment this week.”</li>
+  <li><strong>Guidance:</strong> “Please pray for clarity as our family considers next steps for school and work.”</li>
+  <li><strong>Comfort:</strong> “Please pray for comfort, stability, and help with the next few days.”</li>
+  <li><strong>Strength:</strong> “Please pray for strength to stay steady through a difficult season.”</li>
+</ul>
+
+<p>If you want to keep a request private but still specific, say that directly:</p>
+
+<blockquote>
+  <p>“Please pray for healing for a family member this week. We are not ready to share details publicly, so please keep this private.”</p>
+</blockquote>
+
+<p>That kind of wording does two jobs at once. It gives the church a prayer focus and sets a boundary without making the request awkward.</p>
+
+<p>For a broader biblical frame, <a href="https://www.biblegateway.com/passage/?search=James+5%3A16&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">James 5:16</a> connects prayer with honest confession and mutual care. The point is not performance. The point is trust and clarity.</p>
+
+<h2>If You Are Submitting for Someone Else</h2>
+
+<p>People often ask for prayer on behalf of a spouse, child, parent, friend, or coworker. That is normal. The key is to say two things clearly: your relationship to the person and whether you have permission to share the request.</p>
+
+<p>Useful wording looks like this:</p>
+
+<ul>
+  <li><strong>With consent:</strong> “Please pray for my father, who gave me permission to share that he has a procedure next week.”</li>
+  <li><strong>Without detail:</strong> “Please pray for a friend who is facing a hard family situation.”</li>
+  <li><strong>For a child:</strong> “Please pray for our son as he starts treatment. We are asking for peace and wisdom.”</li>
+</ul>
+
+<p>What matters here is not formality. It is trust. If you are speaking for someone else, do not overshare just because you can. Use the smallest amount of information that still tells the church how to pray.</p>
+
+<p>If consent is unclear, keep the request general and private. That is the safer default. You can always add detail later if permission is granted and the situation changes.</p>
+
+<h2>Sharing Preferences: Public Prayer vs. Private Request</h2>
+
+<p>Not every request belongs in the same channel. A church needs both public prayer and private care, but they are not the same thing. Choosing the right lane keeps the request useful.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Sharing choice</th>
+      <th>Best when</th>
+      <th>What to say</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Public prayer</td>
+      <td>The need is general and you are comfortable with broader church awareness.</td>
+      <td>“Please pray for our family this week as we travel.”</td>
+    </tr>
+    <tr>
+      <td>Private request</td>
+      <td>The matter is sensitive, personal, or not ready for wider sharing.</td>
+      <td>“Please keep this private and pray for wisdom as we work through a family matter.”</td>
+    </tr>
+    <tr>
+      <td>Limited sharing</td>
+      <td>You want prayer but do not want every detail repeated.</td>
+      <td>“You may share the general need, but please leave out the details.”</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>If you are unsure, choose the more private option. That is the conservative decision and usually the right one. It is easier to expand a request later than to retract details after they have already gone farther than you intended.</p>
+
+<p>If the request becomes something broader for the church to know about, you can also look to the <a href="/news.html">News</a> page for public updates. That page is for church communication, not a place to assume personal details will be posted. Public and personal are not the same category, even when the same people are involved.</p>
+
+<h2>How to Submit</h2>
+
+<p>Once your request is ready, use the church’s normal contact paths. The simplest route is usually the <a href="/contacts.html">Contacts</a> page. If you prefer a form-based route, use <a href="/contact.php">Contact Us</a>. Either way, keep the message short, specific, and consistent with the privacy level you chose.</p>
+
+<p>A helpful submission usually has three parts:</p>
+
+<ol>
+  <li><strong>The request itself:</strong> one or two clear sentences.</li>
+  <li><strong>Your privacy note:</strong> public, private, or limited sharing.</li>
+  <li><strong>A follow-up option:</strong> a phone number or email if you want someone to reach back out.</li>
+</ol>
+
+<p>What happens after that? In practical terms, the church receives the note, reads the request, and handles it according to the communication path and privacy preference you provided. If more information is needed, someone may follow up. If no follow-up is needed, the request can still be prayed over without extra drama. That is usually the best case. Prayer requests are not package tracking.</p>
+
+<p>Do not build your wording around a guaranteed response time or a guaranteed outcome. A church can promise care and diligence. It cannot promise the timing of every answer. Keep the focus on the request itself, and keep praying while the message moves through the normal process.</p>
+
+<p>If you need more than a brief prayer note, say so. A sentence like “We would appreciate a follow-up conversation if possible” gives the church a better signal than a wall of text. If the matter is urgent, say that plainly near the top of the message. Simple language wins here.</p>
+
+<h2>A Short Checklist Before You Send</h2>
+
+<ul>
+  <li>Is the request clear in one sentence?</li>
+  <li>Did you include the type of prayer needed?</li>
+  <li>Did you leave out anything private or unnecessary?</li>
+  <li>Did you note whether the request is public, private, or limited?</li>
+  <li>If it is for someone else, did you mention your relationship and consent?</li>
+  <li>If timing matters, did you include the relevant date or timeframe?</li>
+</ul>
+
+<p>If you can answer yes to those six questions, the request is probably ready. There is no prize for over-writing it.</p>
+
+<h2>Common Mistakes That Make Requests Harder to Use</h2>
+
+<p>Most weak prayer requests fail for ordinary reasons, not dramatic ones. The note is too vague, too long, too private in the wrong place, or too public for the situation. Clean that up before you send it and you save everyone time.</p>
+
+<ul>
+  <li><strong>Leaving out the actual request:</strong> “Please pray for my family” is not enough by itself. Add the reason.</li>
+  <li><strong>Writing a full explanation first:</strong> the prayer point should show up in the first sentence, not after three paragraphs.</li>
+  <li><strong>Using code words:</strong> if the church has to decode your message, it is not a clear request.</li>
+  <li><strong>Sharing too much detail:</strong> more information is not always more help. Sometimes it is just more exposure.</li>
+  <li><strong>Forgetting the privacy note:</strong> public, private, or limited sharing should never be a guessing game.</li>
+</ul>
+
+<p>A practical test helps here: read the request out loud once. If it sounds muddled, you probably wrote too much or too little. Trim it until the sentence does the job.</p>
+
+<h2>Three Finished Examples</h2>
+
+<p>If you would rather copy a complete version than build one piece by piece, use one of these as a model:</p>
+
+<blockquote>
+  <p><strong>Example 1:</strong> “Please pray for my mother as she prepares for surgery on Monday. We are asking for peace, skill for the doctors, and a smooth recovery. Please keep this private.”</p>
+</blockquote>
+
+<blockquote>
+  <p><strong>Example 2:</strong> “Please pray for our family this month as we handle a move, a new school schedule, and a lot of change. We would appreciate wisdom and steadiness. The general request may be shared, but please leave out details.”</p>
+</blockquote>
+
+<blockquote>
+  <p><strong>Example 3:</strong> “Please pray for a friend who is grieving. I have permission to ask for prayer, but not to share more details publicly. Please pray for comfort and rest.”</p>
+</blockquote>
+
+<p>These examples are short for a reason. They say what is needed, when it matters, and how public the request may be. That is the job.</p>
+
+<p>If you need help thinking through what kind of support fits the situation, the <a href="/resources">Resources</a> page is a sensible next stop. It will not solve every problem, which is a rare and refreshing limitation for a church website.</p>
+
+<h2>Closing Encouragement</h2>
+
+<p>A good prayer request is not fancy. It is faithful, clear, and respectful. If you keep the message focused on the need, the timing, and the privacy level, you make it easier for the church to do what churches are supposed to do: pray, care, and respond with wisdom.</p>
+
+<p>Start with the <a href="/contacts.html">Contacts</a> page or <a href="/contact.php">Contact Us</a> form, keep your wording simple, and let the church know whether the request should stay private. If you want to think through other next steps while you wait, the <a href="/resources">Resources</a> page can point you to additional support, and <a href="/news.html">News</a> can help you stay aware of broader church updates.</p>
+
+<p>Finally, keep praying after you submit. That part still matters. The church can handle the message, but you should still bring the burden to God directly. <a href="https://www.biblegateway.com/passage/?search=1+Thessalonians+5%3A17&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">1 Thessalonians 5:17</a> keeps the instruction short for a reason.</p>

 succeeded in 908ms:
116

exec
/bin/bash -lc "wp eval 'if (function_exists(\"set_post_thumbnail\")) { "'$ok = set_post_thumbnail(116, 76); echo $ok ? "featured-set" : "featured-failed"; } else { echo "no-helper"; }'"'" in /home/ubuntu/apps/ridgecrestchurch.com
diff --git a//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html
new file mode 100644
index 0000000000000000000000000000000000000000..ba0db7a98ca7aaf1f97d1e0d7779b046be5e686a
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html
@@ -0,0 +1,281 @@
+<p><strong><em>A prayer request does not need to sound polished. It needs to be clear enough for the church to pray without guessing.</em></strong></p>
+
+<p><strong>By Marcus Reed</strong> | Updated June 23, 2026</p>
+
+<p>When people sit down to write a prayer request, the same practical questions come up fast: How much context is enough? What should stay private? Can I ask for prayer for someone else? And how do I make the request easy for the church to read and use well?</p>
+
+<p>Those are good questions. Prayer is not a performance, and the Bible treats it that way. <a href="https://www.biblegateway.com/passage/?search=Philippians+4%3A6-7&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">Philippians 4:6-7</a> points toward honest, direct prayer; <a href="https://www.biblegateway.com/passage/?search=Matthew+6%3A6&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">Matthew 6:6</a> reminds believers that prayer can also be private and disciplined. A useful church request follows the same logic: enough context to be specific, enough restraint to protect what should stay private, and enough clarity that people can pray with purpose.</p>
+
+<p>If you want the shortest path, start with the church <a href="/contacts.html">Contacts</a> page, or use the site's <a href="/contact.php">contact form</a> if that is more convenient. If you are looking for broader church information while you prepare your message, the <a href="/resources">Resources</a> page is a good place to get oriented.</p>
+
+<figure class="wp-block-image size-large">
+  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg" alt="Planning materials on a desk with a calendar and smartphone for Sunday service coordination" class="wp-image-76" style="width:100%;height:auto;" />
+  <figcaption>A simple request starts with the same discipline as any good plan: enough detail to be useful, not so much that the point gets buried.</figcaption>
+</figure>
+
+<h2>Why We Ask for a Little Context</h2>
+
+<p>Prayer teams do better with signal than with noise. A short note that says what is happening, who it affects, and what kind of prayer is needed gives the church something concrete to carry. A vague request forces people to fill in the blanks, and that is where confusion starts.</p>
+
+<p>Context also helps the church handle requests appropriately. Some needs are fine to share broadly. Some should stay with a limited group. Some should be treated as private pastoral matters. The more clearly you state your preference, the less guesswork is required on the other side.</p>
+
+<p>There is a third reason, and it is the one people often skip: context respects the person who is asking for prayer. A request that is too thin can feel detached; a request that is too detailed can feel exposed. The goal is not to narrate your whole life. The goal is to give enough information for faithful prayer and responsible care.</p>
+
+<h2>A Quick Template You Can Copy and Paste</h2>
+
+<p>If you are not sure where to start, use this format. It is simple on purpose.</p>
+
+<pre><code>Name: [Your name]
+Request: [One short sentence about the need]
+Details: [Only the facts that help people pray well]
+Timeframe: [Today, this week, on [date], or ongoing]
+Ongoing vs. one-time: [One-time / recurring]
+Sharing preference: [Public / private / limited sharing]
+Contact: [Optional phone or email if a follow-up may help]</code></pre>
+
+<p>That is enough for most situations. If you need more privacy, leave out the contact line and keep the description general. If the request is for someone else, say so clearly in the first line so the church understands the relationship and the permission level.</p>
+
+<p>A few quick definitions help here:</p>
+
+<ul>
+  <li><strong>Public prayer:</strong> a request that can be shared more broadly with the church.</li>
+  <li><strong>Private request:</strong> a request that should stay with a smaller, limited group.</li>
+  <li><strong>Ongoing request:</strong> a situation that needs repeated prayer over time.</li>
+  <li><strong>Timeframe:</strong> when the need is happening or when support is most important.</li>
+</ul>
+
+<p>Think of the template as a floor, not a ceiling. You can always add a sentence, but you do not need to write a paragraph for every line. A church can work with a concise request. It cannot work with a mystery wrapped in spiritual language.</p>
+
+<h2>Do Include</h2>
+
+<p>The most useful prayer requests include the facts that actually help someone pray.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Include this</th>
+      <th>Why it helps</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>A clear request in one sentence</td>
+      <td>It tells the reader exactly what kind of prayer you are asking for.</td>
+    </tr>
+    <tr>
+      <td>Specific needs or concerns</td>
+      <td>“Healing,” “wisdom,” “travel safety,” or “comfort” are easier to pray for than a vague concern.</td>
+    </tr>
+    <tr>
+      <td>Relevant dates or timeframes</td>
+      <td>Dates help the church know what matters now, this week, or later.</td>
+    </tr>
+    <tr>
+      <td>Whether the request is confidential</td>
+      <td>Privacy preferences should be stated plainly, not left to interpretation.</td>
+    </tr>
+    <tr>
+      <td>Whether the request is ongoing</td>
+      <td>A continuing need may be placed on a prayer list differently from a one-time update.</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>One useful habit: write the request as if someone else has to read it once, understand it immediately, and pray right away. That is the operational standard. Church communication is not a scavenger hunt.</p>
+
+<p>Here are a few examples of good, concise wording:</p>
+
+<ul>
+  <li><strong>Healing:</strong> “Please pray for Sarah as she prepares for surgery on Thursday. We are asking for peace, skill for the medical team, and steady recovery.”</li>
+  <li><strong>Family support:</strong> “Please pray for our family during a difficult week. We need wisdom, patience, and rest.”</li>
+  <li><strong>Guidance:</strong> “Please pray for discernment as I make a work decision by the end of the month.”</li>
+  <li><strong>Comfort:</strong> “Please pray for comfort and strength after a recent loss. This can stay private.”</li>
+</ul>
+
+<p>Notice what is not happening there. There is no long backstory, no dramatic language, and no pressure to explain every detail. The request stays readable.</p>
+
+<h2>Don’t Include</h2>
+
+<p>Good judgment matters. A prayer request is not the right place for everything.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Leave this out</th>
+      <th>Why to avoid it</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Overly personal details</td>
+      <td>If it would make you uncomfortable to read out loud, it probably should not be in the request.</td>
+    </tr>
+    <tr>
+      <td>Information you do not have permission to share</td>
+      <td>Consent matters, especially when the request involves another person.</td>
+    </tr>
+    <tr>
+      <td>Long background narratives</td>
+      <td>The main need should stay visible. A request that rambles can hide the actual prayer point.</td>
+    </tr>
+    <tr>
+      <td>Unnecessary medical, family, or financial details</td>
+      <td>More detail is not always better. Sometimes it is just more detail.</td>
+    </tr>
+    <tr>
+      <td>Anything you are not comfortable sharing publicly</td>
+      <td>If it feels too exposed, mark it private or keep it brief.</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>If a detail does not help someone pray, leave it out. That is usually the right filter. The church does not need a case file. It needs enough context to respond with care.</p>
+
+<h2>If You Are Requesting Healing, Guidance, or Comfort</h2>
+
+<p>These are the situations where people often over-explain or under-explain. The middle path is usually best.</p>
+
+<p>For healing, say what kind of prayer is needed without turning the note into a medical summary. For guidance, name the decision and the deadline if there is one. For comfort, say what kind of support would be most helpful: peace, strength, patience, reassurance, or rest.</p>
+
+<p>You can borrow one of these patterns:</p>
+
+<ul>
+  <li><strong>Healing:</strong> “Please pray for healing and wise care as I recover from treatment this week.”</li>
+  <li><strong>Guidance:</strong> “Please pray for clarity as our family considers next steps for school and work.”</li>
+  <li><strong>Comfort:</strong> “Please pray for comfort, stability, and help with the next few days.”</li>
+  <li><strong>Strength:</strong> “Please pray for strength to stay steady through a difficult season.”</li>
+</ul>
+
+<p>If you want to keep a request private but still specific, say that directly:</p>
+
+<blockquote>
+  <p>“Please pray for healing for a family member this week. We are not ready to share details publicly, so please keep this private.”</p>
+</blockquote>
+
+<p>That kind of wording does two jobs at once. It gives the church a prayer focus and sets a boundary without making the request awkward.</p>
+
+<p>For a broader biblical frame, <a href="https://www.biblegateway.com/passage/?search=James+5%3A16&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">James 5:16</a> connects prayer with honest confession and mutual care. The point is not performance. The point is trust and clarity.</p>
+
+<h2>If You Are Submitting for Someone Else</h2>
+
+<p>People often ask for prayer on behalf of a spouse, child, parent, friend, or coworker. That is normal. The key is to say two things clearly: your relationship to the person and whether you have permission to share the request.</p>
+
+<p>Useful wording looks like this:</p>
+
+<ul>
+  <li><strong>With consent:</strong> “Please pray for my father, who gave me permission to share that he has a procedure next week.”</li>
+  <li><strong>Without detail:</strong> “Please pray for a friend who is facing a hard family situation.”</li>
+  <li><strong>For a child:</strong> “Please pray for our son as he starts treatment. We are asking for peace and wisdom.”</li>
+</ul>
+
+<p>What matters here is not formality. It is trust. If you are speaking for someone else, do not overshare just because you can. Use the smallest amount of information that still tells the church how to pray.</p>
+
+<p>If consent is unclear, keep the request general and private. That is the safer default. You can always add detail later if permission is granted and the situation changes.</p>
+
+<h2>Sharing Preferences: Public Prayer vs. Private Request</h2>
+
+<p>Not every request belongs in the same channel. A church needs both public prayer and private care, but they are not the same thing. Choosing the right lane keeps the request useful.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Sharing choice</th>
+      <th>Best when</th>
+      <th>What to say</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Public prayer</td>
+      <td>The need is general and you are comfortable with broader church awareness.</td>
+      <td>“Please pray for our family this week as we travel.”</td>
+    </tr>
+    <tr>
+      <td>Private request</td>
+      <td>The matter is sensitive, personal, or not ready for wider sharing.</td>
+      <td>“Please keep this private and pray for wisdom as we work through a family matter.”</td>
+    </tr>
+    <tr>
+      <td>Limited sharing</td>
+      <td>You want prayer but do not want every detail repeated.</td>
+      <td>“You may share the general need, but please leave out the details.”</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>If you are unsure, choose the more private option. That is the conservative decision and usually the right one. It is easier to expand a request later than to retract details after they have already gone farther than you intended.</p>
+
+<p>If the request becomes something broader for the church to know about, you can also look to the <a href="/news.html">News</a> page for public updates. That page is for church communication, not a place to assume personal details will be posted. Public and personal are not the same category, even when the same people are involved.</p>
+
+<h2>How to Submit</h2>
+
+<p>Once your request is ready, use the church’s normal contact paths. The simplest route is usually the <a href="/contacts.html">Contacts</a> page. If you prefer a form-based route, use <a href="/contact.php">Contact Us</a>. Either way, keep the message short, specific, and consistent with the privacy level you chose.</p>
+
+<p>A helpful submission usually has three parts:</p>
+
+<ol>
+  <li><strong>The request itself:</strong> one or two clear sentences.</li>
+  <li><strong>Your privacy note:</strong> public, private, or limited sharing.</li>
+  <li><strong>A follow-up option:</strong> a phone number or email if you want someone to reach back out.</li>
+</ol>
+
+<p>What happens after that? In practical terms, the church receives the note, reads the request, and handles it according to the communication path and privacy preference you provided. If more information is needed, someone may follow up. If no follow-up is needed, the request can still be prayed over without extra drama. That is usually the best case. Prayer requests are not package tracking.</p>
+
+<p>Do not build your wording around a guaranteed response time or a guaranteed outcome. A church can promise care and diligence. It cannot promise the timing of every answer. Keep the focus on the request itself, and keep praying while the message moves through the normal process.</p>
+
+<p>If you need more than a brief prayer note, say so. A sentence like “We would appreciate a follow-up conversation if possible” gives the church a better signal than a wall of text. If the matter is urgent, say that plainly near the top of the message. Simple language wins here.</p>
+
+<h2>A Short Checklist Before You Send</h2>
+
+<ul>
+  <li>Is the request clear in one sentence?</li>
+  <li>Did you include the type of prayer needed?</li>
+  <li>Did you leave out anything private or unnecessary?</li>
+  <li>Did you note whether the request is public, private, or limited?</li>
+  <li>If it is for someone else, did you mention your relationship and consent?</li>
+  <li>If timing matters, did you include the relevant date or timeframe?</li>
+</ul>
+
+<p>If you can answer yes to those six questions, the request is probably ready. There is no prize for over-writing it.</p>
+
+<h2>Common Mistakes That Make Requests Harder to Use</h2>
+
+<p>Most weak prayer requests fail for ordinary reasons, not dramatic ones. The note is too vague, too long, too private in the wrong place, or too public for the situation. Clean that up before you send it and you save everyone time.</p>
+
+<ul>
+  <li><strong>Leaving out the actual request:</strong> “Please pray for my family” is not enough by itself. Add the reason.</li>
+  <li><strong>Writing a full explanation first:</strong> the prayer point should show up in the first sentence, not after three paragraphs.</li>
+  <li><strong>Using code words:</strong> if the church has to decode your message, it is not a clear request.</li>
+  <li><strong>Sharing too much detail:</strong> more information is not always more help. Sometimes it is just more exposure.</li>
+  <li><strong>Forgetting the privacy note:</strong> public, private, or limited sharing should never be a guessing game.</li>
+</ul>
+
+<p>A practical test helps here: read the request out loud once. If it sounds muddled, you probably wrote too much or too little. Trim it until the sentence does the job.</p>
+
+<h2>Three Finished Examples</h2>
+
+<p>If you would rather copy a complete version than build one piece by piece, use one of these as a model:</p>
+
+<blockquote>
+  <p><strong>Example 1:</strong> “Please pray for my mother as she prepares for surgery on Monday. We are asking for peace, skill for the doctors, and a smooth recovery. Please keep this private.”</p>
+</blockquote>
+
+<blockquote>
+  <p><strong>Example 2:</strong> “Please pray for our family this month as we handle a move, a new school schedule, and a lot of change. We would appreciate wisdom and steadiness. The general request may be shared, but please leave out details.”</p>
+</blockquote>
+
+<blockquote>
+  <p><strong>Example 3:</strong> “Please pray for a friend who is grieving. I have permission to ask for prayer, but not to share more details publicly. Please pray for comfort and rest.”</p>
+</blockquote>
+
+<p>These examples are short for a reason. They say what is needed, when it matters, and how public the request may be. That is the job.</p>
+
+<p>If you need help thinking through what kind of support fits the situation, the <a href="/resources">Resources</a> page is a sensible next stop. It will not solve every problem, which is a rare and refreshing limitation for a church website.</p>
+
+<h2>Closing Encouragement</h2>
+
+<p>A good prayer request is not fancy. It is faithful, clear, and respectful. If you keep the message focused on the need, the timing, and the privacy level, you make it easier for the church to do what churches are supposed to do: pray, care, and respond with wisdom.</p>
+
+<p>Start with the <a href="/contacts.html">Contacts</a> page or <a href="/contact.php">Contact Us</a> form, keep your wording simple, and let the church know whether the request should stay private. If you want to think through other next steps while you wait, the <a href="/resources">Resources</a> page can point you to additional support, and <a href="/news.html">News</a> can help you stay aware of broader church updates.</p>
+
+<p>Finally, keep praying after you submit. That part still matters. The church can handle the message, but you should still bring the burden to God directly. <a href="https://www.biblegateway.com/passage/?search=1+Thessalonians+5%3A17&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">1 Thessalonians 5:17</a> keeps the instruction short for a reason.</p>

 succeeded in 506ms:
featured-set
codex
The post is published. I’m doing the final checks now: post record, public URL, featured image, and a direct scan of the stored content to confirm the inline image markup is actually there.
exec
/bin/bash -lc 'wp post get 116 --fields=ID,post_title,post_name,post_status,post_author,post_excerpt --format=json' in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc 'wp post url 116' in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc 'wp post meta get 116 _thumbnail_id' in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "wp post get 116 --field=post_content | rg -n 'wp-image-76|sunday-service-planning-desk|Contacts|contact.php|news.html|Resources|BibleGateway'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 717ms:
{"ID":116,"post_author":"5","post_title":"How to Prepare a Prayer Request for Ridgecrest (A Simple, Respectful Template)","post_excerpt":"Learn how to write a meaningful prayer request for Ridgecrest Baptist Church with this practical template and guidance.","post_status":"publish","post_name":"how-to-prepare-prayer-request-template"}

 succeeded in 613ms:
https://ridgecrestchurch.com/how-to-prepare-prayer-request-template/

 succeeded in 645ms:
9:<p>If you want the shortest path, start with the church <a href="/contacts.html">Contacts</a> page, or use the site's <a href="/contact.php">contact form</a> if that is more convenient. If you are looking for broader church information while you prepare your message, the <a href="/resources">Resources</a> page is a good place to get oriented.</p>
12:  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg" alt="Planning materials on a desk with a calendar and smartphone for Sunday service coordination" class="wp-image-76" style="width:100%;height:auto;" />
208:<p>If the request becomes something broader for the church to know about, you can also look to the <a href="/news.html">News</a> page for public updates. That page is for church communication, not a place to assume personal details will be posted. Public and personal are not the same category, even when the same people are involved.</p>
212:<p>Once your request is ready, use the church’s normal contact paths. The simplest route is usually the <a href="/contacts.html">Contacts</a> page. If you prefer a form-based route, use <a href="/contact.php">Contact Us</a>. Either way, keep the message short, specific, and consistent with the privacy level you chose.</p>
273:<p>If you need help thinking through what kind of support fits the situation, the <a href="/resources">Resources</a> page is a sensible next stop. It will not solve every problem, which is a rare and refreshing limitation for a church website.</p>
279:<p>Start with the <a href="/contacts.html">Contacts</a> page or <a href="/contact.php">Contact Us</a> form, keep your wording simple, and let the church know whether the request should stay private. If you want to think through other next steps while you wait, the <a href="/resources">Resources</a> page can point you to additional support, and <a href="/news.html">News</a> can help you stay aware of broader church updates.</p>

diff --git a//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html
new file mode 100644
index 0000000000000000000000000000000000000000..ba0db7a98ca7aaf1f97d1e0d7779b046be5e686a
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html
@@ -0,0 +1,281 @@
+<p><strong><em>A prayer request does not need to sound polished. It needs to be clear enough for the church to pray without guessing.</em></strong></p>
+
+<p><strong>By Marcus Reed</strong> | Updated June 23, 2026</p>
+
+<p>When people sit down to write a prayer request, the same practical questions come up fast: How much context is enough? What should stay private? Can I ask for prayer for someone else? And how do I make the request easy for the church to read and use well?</p>
+
+<p>Those are good questions. Prayer is not a performance, and the Bible treats it that way. <a href="https://www.biblegateway.com/passage/?search=Philippians+4%3A6-7&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">Philippians 4:6-7</a> points toward honest, direct prayer; <a href="https://www.biblegateway.com/passage/?search=Matthew+6%3A6&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">Matthew 6:6</a> reminds believers that prayer can also be private and disciplined. A useful church request follows the same logic: enough context to be specific, enough restraint to protect what should stay private, and enough clarity that people can pray with purpose.</p>
+
+<p>If you want the shortest path, start with the church <a href="/contacts.html">Contacts</a> page, or use the site's <a href="/contact.php">contact form</a> if that is more convenient. If you are looking for broader church information while you prepare your message, the <a href="/resources">Resources</a> page is a good place to get oriented.</p>
+
+<figure class="wp-block-image size-large">
+  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg" alt="Planning materials on a desk with a calendar and smartphone for Sunday service coordination" class="wp-image-76" style="width:100%;height:auto;" />
+  <figcaption>A simple request starts with the same discipline as any good plan: enough detail to be useful, not so much that the point gets buried.</figcaption>
+</figure>
+
+<h2>Why We Ask for a Little Context</h2>
+
+<p>Prayer teams do better with signal than with noise. A short note that says what is happening, who it affects, and what kind of prayer is needed gives the church something concrete to carry. A vague request forces people to fill in the blanks, and that is where confusion starts.</p>
+
+<p>Context also helps the church handle requests appropriately. Some needs are fine to share broadly. Some should stay with a limited group. Some should be treated as private pastoral matters. The more clearly you state your preference, the less guesswork is required on the other side.</p>
+
+<p>There is a third reason, and it is the one people often skip: context respects the person who is asking for prayer. A request that is too thin can feel detached; a request that is too detailed can feel exposed. The goal is not to narrate your whole life. The goal is to give enough information for faithful prayer and responsible care.</p>
+
+<h2>A Quick Template You Can Copy and Paste</h2>
+
+<p>If you are not sure where to start, use this format. It is simple on purpose.</p>
+
+<pre><code>Name: [Your name]
+Request: [One short sentence about the need]
+Details: [Only the facts that help people pray well]
+Timeframe: [Today, this week, on [date], or ongoing]
+Ongoing vs. one-time: [One-time / recurring]
+Sharing preference: [Public / private / limited sharing]
+Contact: [Optional phone or email if a follow-up may help]</code></pre>
+
+<p>That is enough for most situations. If you need more privacy, leave out the contact line and keep the description general. If the request is for someone else, say so clearly in the first line so the church understands the relationship and the permission level.</p>
+
+<p>A few quick definitions help here:</p>
+
+<ul>
+  <li><strong>Public prayer:</strong> a request that can be shared more broadly with the church.</li>
+  <li><strong>Private request:</strong> a request that should stay with a smaller, limited group.</li>
+  <li><strong>Ongoing request:</strong> a situation that needs repeated prayer over time.</li>
+  <li><strong>Timeframe:</strong> when the need is happening or when support is most important.</li>
+</ul>
+
+<p>Think of the template as a floor, not a ceiling. You can always add a sentence, but you do not need to write a paragraph for every line. A church can work with a concise request. It cannot work with a mystery wrapped in spiritual language.</p>
+
+<h2>Do Include</h2>
+
+<p>The most useful prayer requests include the facts that actually help someone pray.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Include this</th>
+      <th>Why it helps</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>A clear request in one sentence</td>
+      <td>It tells the reader exactly what kind of prayer you are asking for.</td>
+    </tr>
+    <tr>
+      <td>Specific needs or concerns</td>
+      <td>“Healing,” “wisdom,” “travel safety,” or “comfort” are easier to pray for than a vague concern.</td>
+    </tr>
+    <tr>
+      <td>Relevant dates or timeframes</td>
+      <td>Dates help the church know what matters now, this week, or later.</td>
+    </tr>
+    <tr>
+      <td>Whether the request is confidential</td>
+      <td>Privacy preferences should be stated plainly, not left to interpretation.</td>
+    </tr>
+    <tr>
+      <td>Whether the request is ongoing</td>
+      <td>A continuing need may be placed on a prayer list differently from a one-time update.</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>One useful habit: write the request as if someone else has to read it once, understand it immediately, and pray right away. That is the operational standard. Church communication is not a scavenger hunt.</p>
+
+<p>Here are a few examples of good, concise wording:</p>
+
+<ul>
+  <li><strong>Healing:</strong> “Please pray for Sarah as she prepares for surgery on Thursday. We are asking for peace, skill for the medical team, and steady recovery.”</li>
+  <li><strong>Family support:</strong> “Please pray for our family during a difficult week. We need wisdom, patience, and rest.”</li>
+  <li><strong>Guidance:</strong> “Please pray for discernment as I make a work decision by the end of the month.”</li>
+  <li><strong>Comfort:</strong> “Please pray for comfort and strength after a recent loss. This can stay private.”</li>
+</ul>
+
+<p>Notice what is not happening there. There is no long backstory, no dramatic language, and no pressure to explain every detail. The request stays readable.</p>
+
+<h2>Don’t Include</h2>
+
+<p>Good judgment matters. A prayer request is not the right place for everything.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Leave this out</th>
+      <th>Why to avoid it</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Overly personal details</td>
+      <td>If it would make you uncomfortable to read out loud, it probably should not be in the request.</td>
+    </tr>
+    <tr>
+      <td>Information you do not have permission to share</td>
+      <td>Consent matters, especially when the request involves another person.</td>
+    </tr>
+    <tr>
+      <td>Long background narratives</td>
+      <td>The main need should stay visible. A request that rambles can hide the actual prayer point.</td>
+    </tr>
+    <tr>
+      <td>Unnecessary medical, family, or financial details</td>
+      <td>More detail is not always better. Sometimes it is just more detail.</td>
+    </tr>
+    <tr>
+      <td>Anything you are not comfortable sharing publicly</td>
+      <td>If it feels too exposed, mark it private or keep it brief.</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>If a detail does not help someone pray, leave it out. That is usually the right filter. The church does not need a case file. It needs enough context to respond with care.</p>
+
+<h2>If You Are Requesting Healing, Guidance, or Comfort</h2>
+
+<p>These are the situations where people often over-explain or under-explain. The middle path is usually best.</p>
+
+<p>For healing, say what kind of prayer is needed without turning the note into a medical summary. For guidance, name the decision and the deadline if there is one. For comfort, say what kind of support would be most helpful: peace, strength, patience, reassurance, or rest.</p>
+
+<p>You can borrow one of these patterns:</p>
+
+<ul>
+  <li><strong>Healing:</strong> “Please pray for healing and wise care as I recover from treatment this week.”</li>
+  <li><strong>Guidance:</strong> “Please pray for clarity as our family considers next steps for school and work.”</li>
+  <li><strong>Comfort:</strong> “Please pray for comfort, stability, and help with the next few days.”</li>
+  <li><strong>Strength:</strong> “Please pray for strength to stay steady through a difficult season.”</li>
+</ul>
+
+<p>If you want to keep a request private but still specific, say that directly:</p>
+
+<blockquote>
+  <p>“Please pray for healing for a family member this week. We are not ready to share details publicly, so please keep this private.”</p>
+</blockquote>
+
+<p>That kind of wording does two jobs at once. It gives the church a prayer focus and sets a boundary without making the request awkward.</p>
+
+<p>For a broader biblical frame, <a href="https://www.biblegateway.com/passage/?search=James+5%3A16&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">James 5:16</a> connects prayer with honest confession and mutual care. The point is not performance. The point is trust and clarity.</p>
+
+<h2>If You Are Submitting for Someone Else</h2>
+
+<p>People often ask for prayer on behalf of a spouse, child, parent, friend, or coworker. That is normal. The key is to say two things clearly: your relationship to the person and whether you have permission to share the request.</p>
+
+<p>Useful wording looks like this:</p>
+
+<ul>
+  <li><strong>With consent:</strong> “Please pray for my father, who gave me permission to share that he has a procedure next week.”</li>
+  <li><strong>Without detail:</strong> “Please pray for a friend who is facing a hard family situation.”</li>
+  <li><strong>For a child:</strong> “Please pray for our son as he starts treatment. We are asking for peace and wisdom.”</li>
+</ul>
+
+<p>What matters here is not formality. It is trust. If you are speaking for someone else, do not overshare just because you can. Use the smallest amount of information that still tells the church how to pray.</p>
+
+<p>If consent is unclear, keep the request general and private. That is the safer default. You can always add detail later if permission is granted and the situation changes.</p>
+
+<h2>Sharing Preferences: Public Prayer vs. Private Request</h2>
+
+<p>Not every request belongs in the same channel. A church needs both public prayer and private care, but they are not the same thing. Choosing the right lane keeps the request useful.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Sharing choice</th>
+      <th>Best when</th>
+      <th>What to say</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Public prayer</td>
+      <td>The need is general and you are comfortable with broader church awareness.</td>
+      <td>“Please pray for our family this week as we travel.”</td>
+    </tr>
+    <tr>
+      <td>Private request</td>
+      <td>The matter is sensitive, personal, or not ready for wider sharing.</td>
+      <td>“Please keep this private and pray for wisdom as we work through a family matter.”</td>
+    </tr>
+    <tr>
+      <td>Limited sharing</td>
+      <td>You want prayer but do not want every detail repeated.</td>
+      <td>“You may share the general need, but please leave out the details.”</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>If you are unsure, choose the more private option. That is the conservative decision and usually the right one. It is easier to expand a request later than to retract details after they have already gone farther than you intended.</p>
+
+<p>If the request becomes something broader for the church to know about, you can also look to the <a href="/news.html">News</a> page for public updates. That page is for church communication, not a place to assume personal details will be posted. Public and personal are not the same category, even when the same people are involved.</p>
+
+<h2>How to Submit</h2>
+
+<p>Once your request is ready, use the church’s normal contact paths. The simplest route is usually the <a href="/contacts.html">Contacts</a> page. If you prefer a form-based route, use <a href="/contact.php">Contact Us</a>. Either way, keep the message short, specific, and consistent with the privacy level you chose.</p>
+
+<p>A helpful submission usually has three parts:</p>
+
+<ol>
+  <li><strong>The request itself:</strong> one or two clear sentences.</li>
+  <li><strong>Your privacy note:</strong> public, private, or limited sharing.</li>
+  <li><strong>A follow-up option:</strong> a phone number or email if you want someone to reach back out.</li>
+</ol>
+
+<p>What happens after that? In practical terms, the church receives the note, reads the request, and handles it according to the communication path and privacy preference you provided. If more information is needed, someone may follow up. If no follow-up is needed, the request can still be prayed over without extra drama. That is usually the best case. Prayer requests are not package tracking.</p>
+
+<p>Do not build your wording around a guaranteed response time or a guaranteed outcome. A church can promise care and diligence. It cannot promise the timing of every answer. Keep the focus on the request itself, and keep praying while the message moves through the normal process.</p>
+
+<p>If you need more than a brief prayer note, say so. A sentence like “We would appreciate a follow-up conversation if possible” gives the church a better signal than a wall of text. If the matter is urgent, say that plainly near the top of the message. Simple language wins here.</p>
+
+<h2>A Short Checklist Before You Send</h2>
+
+<ul>
+  <li>Is the request clear in one sentence?</li>
+  <li>Did you include the type of prayer needed?</li>
+  <li>Did you leave out anything private or unnecessary?</li>
+  <li>Did you note whether the request is public, private, or limited?</li>
+  <li>If it is for someone else, did you mention your relationship and consent?</li>
+  <li>If timing matters, did you include the relevant date or timeframe?</li>
+</ul>
+
+<p>If you can answer yes to those six questions, the request is probably ready. There is no prize for over-writing it.</p>
+
+<h2>Common Mistakes That Make Requests Harder to Use</h2>
+
+<p>Most weak prayer requests fail for ordinary reasons, not dramatic ones. The note is too vague, too long, too private in the wrong place, or too public for the situation. Clean that up before you send it and you save everyone time.</p>
+
+<ul>
+  <li><strong>Leaving out the actual request:</strong> “Please pray for my family” is not enough by itself. Add the reason.</li>
+  <li><strong>Writing a full explanation first:</strong> the prayer point should show up in the first sentence, not after three paragraphs.</li>
+  <li><strong>Using code words:</strong> if the church has to decode your message, it is not a clear request.</li>
+  <li><strong>Sharing too much detail:</strong> more information is not always more help. Sometimes it is just more exposure.</li>
+  <li><strong>Forgetting the privacy note:</strong> public, private, or limited sharing should never be a guessing game.</li>
+</ul>
+
+<p>A practical test helps here: read the request out loud once. If it sounds muddled, you probably wrote too much or too little. Trim it until the sentence does the job.</p>
+
+<h2>Three Finished Examples</h2>
+
+<p>If you would rather copy a complete version than build one piece by piece, use one of these as a model:</p>
+
+<blockquote>
+  <p><strong>Example 1:</strong> “Please pray for my mother as she prepares for surgery on Monday. We are asking for peace, skill for the doctors, and a smooth recovery. Please keep this private.”</p>
+</blockquote>
+
+<blockquote>
+  <p><strong>Example 2:</strong> “Please pray for our family this month as we handle a move, a new school schedule, and a lot of change. We would appreciate wisdom and steadiness. The general request may be shared, but please leave out details.”</p>
+</blockquote>
+
+<blockquote>
+  <p><strong>Example 3:</strong> “Please pray for a friend who is grieving. I have permission to ask for prayer, but not to share more details publicly. Please pray for comfort and rest.”</p>
+</blockquote>
+
+<p>These examples are short for a reason. They say what is needed, when it matters, and how public the request may be. That is the job.</p>
+
+<p>If you need help thinking through what kind of support fits the situation, the <a href="/resources">Resources</a> page is a sensible next stop. It will not solve every problem, which is a rare and refreshing limitation for a church website.</p>
+
+<h2>Closing Encouragement</h2>
+
+<p>A good prayer request is not fancy. It is faithful, clear, and respectful. If you keep the message focused on the need, the timing, and the privacy level, you make it easier for the church to do what churches are supposed to do: pray, care, and respond with wisdom.</p>
+
+<p>Start with the <a href="/contacts.html">Contacts</a> page or <a href="/contact.php">Contact Us</a> form, keep your wording simple, and let the church know whether the request should stay private. If you want to think through other next steps while you wait, the <a href="/resources">Resources</a> page can point you to additional support, and <a href="/news.html">News</a> can help you stay aware of broader church updates.</p>
+
+<p>Finally, keep praying after you submit. That part still matters. The church can handle the message, but you should still bring the burden to God directly. <a href="https://www.biblegateway.com/passage/?search=1+Thessalonians+5%3A17&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">1 Thessalonians 5:17</a> keeps the instruction short for a reason.</p>

 succeeded in 773ms:
76

codex
The database checks are good. I’m doing one last web-facing verification on the published URL and the blog index so the final report can be precise about what is live.
exec
/bin/bash -lc 'curl -I -L --max-redirs 3 https://ridgecrestchurch.com/how-to-prepare-prayer-request-template/' in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc 'curl -I -L --max-redirs 3 https://ridgecrestchurch.com/blog/' in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "curl -L --max-redirs 3 https://ridgecrestchurch.com/how-to-prepare-prayer-request-template/ | rg -n 'sunday-service-planning-desk.jpg|wp-image-76|Philippians|Matthew 6:6|James 5:16'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 476ms:
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0HTTP/2 200 
date: Tue, 23 Jun 2026 18:32:46 GMT
content-type: text/html; charset=UTF-8
link: <https://ridgecrestchurch.com/wp-json/>; rel="https://api.w.org/", <https://ridgecrestchurch.com/wp-json/wp/v2/posts/116>; rel="alternate"; title="JSON"; type="application/json", <https://ridgecrestchurch.com/?p=116>; 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=GtcsaYlYpW%2BJGeL98ogS8f56Na%2FirxKH2uMEgtwKUiVa7cytKp6yqIicefT7%2F079knTXIc8jDXM%2BhFiuCvYAdqAvaLuHxde%2FURoQ4Nog3zII2caElV%2FAoXWpGX6RTH3ybEw61qOkXA%3D%3D"}]}
nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
cf-ray: a10593c60b87736b-WAW
alt-svc: h3=":443"; ma=86400

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0

 succeeded in 535ms:
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0100 54334    0 54334    0     0  95483      0 --:--:-- --:--:-- --:--:-- 95490
21:	<meta property="og:image" content="https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg" />
31:	<script type="application/ld+json" class="yoast-schema-graph">{"@context":"https://schema.org","@graph":[{"@type":"Article","@id":"https://ridgecrestchurch.com/how-to-prepare-prayer-request-template/#article","isPartOf":{"@id":"https://ridgecrestchurch.com/how-to-prepare-prayer-request-template/"},"author":{"name":"Marcus Reed","@id":"https://ridgecrestchurch.com/#/schema/person/2698d86a6f04ff1d1a31b78a07d47018"},"headline":"How to Prepare a Prayer Request for Ridgecrest (A Simple, Respectful Template)","datePublished":"2026-06-23T18:32:35+00:00","mainEntityOfPage":{"@id":"https://ridgecrestchurch.com/how-to-prepare-prayer-request-template/"},"wordCount":2391,"publisher":{"@id":"https://ridgecrestchurch.com/#organization"},"image":{"@id":"https://ridgecrestchurch.com/how-to-prepare-prayer-request-template/#primaryimage"},"thumbnailUrl":"https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg","inLanguage":"en-US"},{"@type":"WebPage","@id":"https://ridgecrestchurch.com/how-to-prepare-prayer-request-template/","url":"https://ridgecrestchurch.com/how-to-prepare-prayer-request-template/","name":"How to Prepare a Prayer Request for Ridgecrest (A Simple, Respectful Template) - Ridgecrest Baptist Church","isPartOf":{"@id":"https://ridgecrestchurch.com/#website"},"primaryImageOfPage":{"@id":"https://ridgecrestchurch.com/how-to-prepare-prayer-request-template/#primaryimage"},"image":{"@id":"https://ridgecrestchurch.com/how-to-prepare-prayer-request-template/#primaryimage"},"thumbnailUrl":"https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg","datePublished":"2026-06-23T18:32:35+00:00","breadcrumb":{"@id":"https://ridgecrestchurch.com/how-to-prepare-prayer-request-template/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https://ridgecrestchurch.com/how-to-prepare-prayer-request-template/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https://ridgecrestchurch.com/how-to-prepare-prayer-request-template/#primaryimage","url":"https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg","contentUrl":"https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg","caption":"Planning materials on a desk with a calendar and smartphone for Sunday service coordination"},{"@type":"BreadcrumbList","@id":"https://ridgecrestchurch.com/how-to-prepare-prayer-request-template/#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 Prepare a Prayer Request for Ridgecrest (A Simple, Respectful Template)"}]},{"@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/2698d86a6f04ff1d1a31b78a07d47018","name":"Marcus Reed","url":"https://ridgecrestchurch.com/author/marcus-reed/"}]}</script>
430:<p>Those are good questions. Prayer is not a performance, and the Bible treats it that way. <a href="https://www.biblegateway.com/passage/?search=Philippians+4%3A6-7&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">Philippians 4:6-7</a> points toward honest, direct prayer; <a href="https://www.biblegateway.com/passage/?search=Matthew+6%3A6&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">Matthew 6:6</a> reminds believers that prayer can also be private and disciplined. A useful church request follows the same logic: enough context to be specific, enough restraint to protect what should stay private, and enough clarity that people can pray with purpose.</p>
433:  <img decoding="async" data-src="https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg" alt="Planning materials on a desk with a calendar and smartphone for Sunday service coordination" class="wp-image-76 lazyload" style="--smush-placeholder-width: 1024px; --smush-placeholder-aspect-ratio: 1024/683;width:100%;height:auto;" src="data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==" /><figcaption>A simple request starts with the same discipline as any good plan: enough detail to be useful, not so much that the point gets buried.</figcaption></figure>
545:<p>For a broader biblical frame, <a href="https://www.biblegateway.com/passage/?search=James+5%3A16&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">James 5:16</a> connects prayer with honest confession and mutual care. The point is not performance. The point is trust and clarity.</p>

diff --git a//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html
new file mode 100644
index 0000000000000000000000000000000000000000..ba0db7a98ca7aaf1f97d1e0d7779b046be5e686a
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html
@@ -0,0 +1,281 @@
+<p><strong><em>A prayer request does not need to sound polished. It needs to be clear enough for the church to pray without guessing.</em></strong></p>
+
+<p><strong>By Marcus Reed</strong> | Updated June 23, 2026</p>
+
+<p>When people sit down to write a prayer request, the same practical questions come up fast: How much context is enough? What should stay private? Can I ask for prayer for someone else? And how do I make the request easy for the church to read and use well?</p>
+
+<p>Those are good questions. Prayer is not a performance, and the Bible treats it that way. <a href="https://www.biblegateway.com/passage/?search=Philippians+4%3A6-7&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">Philippians 4:6-7</a> points toward honest, direct prayer; <a href="https://www.biblegateway.com/passage/?search=Matthew+6%3A6&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">Matthew 6:6</a> reminds believers that prayer can also be private and disciplined. A useful church request follows the same logic: enough context to be specific, enough restraint to protect what should stay private, and enough clarity that people can pray with purpose.</p>
+
+<p>If you want the shortest path, start with the church <a href="/contacts.html">Contacts</a> page, or use the site's <a href="/contact.php">contact form</a> if that is more convenient. If you are looking for broader church information while you prepare your message, the <a href="/resources">Resources</a> page is a good place to get oriented.</p>
+
+<figure class="wp-block-image size-large">
+  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg" alt="Planning materials on a desk with a calendar and smartphone for Sunday service coordination" class="wp-image-76" style="width:100%;height:auto;" />
+  <figcaption>A simple request starts with the same discipline as any good plan: enough detail to be useful, not so much that the point gets buried.</figcaption>
+</figure>
+
+<h2>Why We Ask for a Little Context</h2>
+
+<p>Prayer teams do better with signal than with noise. A short note that says what is happening, who it affects, and what kind of prayer is needed gives the church something concrete to carry. A vague request forces people to fill in the blanks, and that is where confusion starts.</p>
+
+<p>Context also helps the church handle requests appropriately. Some needs are fine to share broadly. Some should stay with a limited group. Some should be treated as private pastoral matters. The more clearly you state your preference, the less guesswork is required on the other side.</p>
+
+<p>There is a third reason, and it is the one people often skip: context respects the person who is asking for prayer. A request that is too thin can feel detached; a request that is too detailed can feel exposed. The goal is not to narrate your whole life. The goal is to give enough information for faithful prayer and responsible care.</p>
+
+<h2>A Quick Template You Can Copy and Paste</h2>
+
+<p>If you are not sure where to start, use this format. It is simple on purpose.</p>
+
+<pre><code>Name: [Your name]
+Request: [One short sentence about the need]
+Details: [Only the facts that help people pray well]
+Timeframe: [Today, this week, on [date], or ongoing]
+Ongoing vs. one-time: [One-time / recurring]
+Sharing preference: [Public / private / limited sharing]
+Contact: [Optional phone or email if a follow-up may help]</code></pre>
+
+<p>That is enough for most situations. If you need more privacy, leave out the contact line and keep the description general. If the request is for someone else, say so clearly in the first line so the church understands the relationship and the permission level.</p>
+
+<p>A few quick definitions help here:</p>
+
+<ul>
+  <li><strong>Public prayer:</strong> a request that can be shared more broadly with the church.</li>
+  <li><strong>Private request:</strong> a request that should stay with a smaller, limited group.</li>
+  <li><strong>Ongoing request:</strong> a situation that needs repeated prayer over time.</li>
+  <li><strong>Timeframe:</strong> when the need is happening or when support is most important.</li>
+</ul>
+
+<p>Think of the template as a floor, not a ceiling. You can always add a sentence, but you do not need to write a paragraph for every line. A church can work with a concise request. It cannot work with a mystery wrapped in spiritual language.</p>
+
+<h2>Do Include</h2>
+
+<p>The most useful prayer requests include the facts that actually help someone pray.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Include this</th>
+      <th>Why it helps</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>A clear request in one sentence</td>
+      <td>It tells the reader exactly what kind of prayer you are asking for.</td>
+    </tr>
+    <tr>
+      <td>Specific needs or concerns</td>
+      <td>“Healing,” “wisdom,” “travel safety,” or “comfort” are easier to pray for than a vague concern.</td>
+    </tr>
+    <tr>
+      <td>Relevant dates or timeframes</td>
+      <td>Dates help the church know what matters now, this week, or later.</td>
+    </tr>
+    <tr>
+      <td>Whether the request is confidential</td>
+      <td>Privacy preferences should be stated plainly, not left to interpretation.</td>
+    </tr>
+    <tr>
+      <td>Whether the request is ongoing</td>
+      <td>A continuing need may be placed on a prayer list differently from a one-time update.</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>One useful habit: write the request as if someone else has to read it once, understand it immediately, and pray right away. That is the operational standard. Church communication is not a scavenger hunt.</p>
+
+<p>Here are a few examples of good, concise wording:</p>
+
+<ul>
+  <li><strong>Healing:</strong> “Please pray for Sarah as she prepares for surgery on Thursday. We are asking for peace, skill for the medical team, and steady recovery.”</li>
+  <li><strong>Family support:</strong> “Please pray for our family during a difficult week. We need wisdom, patience, and rest.”</li>
+  <li><strong>Guidance:</strong> “Please pray for discernment as I make a work decision by the end of the month.”</li>
+  <li><strong>Comfort:</strong> “Please pray for comfort and strength after a recent loss. This can stay private.”</li>
+</ul>
+
+<p>Notice what is not happening there. There is no long backstory, no dramatic language, and no pressure to explain every detail. The request stays readable.</p>
+
+<h2>Don’t Include</h2>
+
+<p>Good judgment matters. A prayer request is not the right place for everything.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Leave this out</th>
+      <th>Why to avoid it</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Overly personal details</td>
+      <td>If it would make you uncomfortable to read out loud, it probably should not be in the request.</td>
+    </tr>
+    <tr>
+      <td>Information you do not have permission to share</td>
+      <td>Consent matters, especially when the request involves another person.</td>
+    </tr>
+    <tr>
+      <td>Long background narratives</td>
+      <td>The main need should stay visible. A request that rambles can hide the actual prayer point.</td>
+    </tr>
+    <tr>
+      <td>Unnecessary medical, family, or financial details</td>
+      <td>More detail is not always better. Sometimes it is just more detail.</td>
+    </tr>
+    <tr>
+      <td>Anything you are not comfortable sharing publicly</td>
+      <td>If it feels too exposed, mark it private or keep it brief.</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>If a detail does not help someone pray, leave it out. That is usually the right filter. The church does not need a case file. It needs enough context to respond with care.</p>
+
+<h2>If You Are Requesting Healing, Guidance, or Comfort</h2>
+
+<p>These are the situations where people often over-explain or under-explain. The middle path is usually best.</p>
+
+<p>For healing, say what kind of prayer is needed without turning the note into a medical summary. For guidance, name the decision and the deadline if there is one. For comfort, say what kind of support would be most helpful: peace, strength, patience, reassurance, or rest.</p>
+
+<p>You can borrow one of these patterns:</p>
+
+<ul>
+  <li><strong>Healing:</strong> “Please pray for healing and wise care as I recover from treatment this week.”</li>
+  <li><strong>Guidance:</strong> “Please pray for clarity as our family considers next steps for school and work.”</li>
+  <li><strong>Comfort:</strong> “Please pray for comfort, stability, and help with the next few days.”</li>
+  <li><strong>Strength:</strong> “Please pray for strength to stay steady through a difficult season.”</li>
+</ul>
+
+<p>If you want to keep a request private but still specific, say that directly:</p>
+
+<blockquote>
+  <p>“Please pray for healing for a family member this week. We are not ready to share details publicly, so please keep this private.”</p>
+</blockquote>
+
+<p>That kind of wording does two jobs at once. It gives the church a prayer focus and sets a boundary without making the request awkward.</p>
+
+<p>For a broader biblical frame, <a href="https://www.biblegateway.com/passage/?search=James+5%3A16&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">James 5:16</a> connects prayer with honest confession and mutual care. The point is not performance. The point is trust and clarity.</p>
+
+<h2>If You Are Submitting for Someone Else</h2>
+
+<p>People often ask for prayer on behalf of a spouse, child, parent, friend, or coworker. That is normal. The key is to say two things clearly: your relationship to the person and whether you have permission to share the request.</p>
+
+<p>Useful wording looks like this:</p>
+
+<ul>
+  <li><strong>With consent:</strong> “Please pray for my father, who gave me permission to share that he has a procedure next week.”</li>
+  <li><strong>Without detail:</strong> “Please pray for a friend who is facing a hard family situation.”</li>
+  <li><strong>For a child:</strong> “Please pray for our son as he starts treatment. We are asking for peace and wisdom.”</li>
+</ul>
+
+<p>What matters here is not formality. It is trust. If you are speaking for someone else, do not overshare just because you can. Use the smallest amount of information that still tells the church how to pray.</p>
+
+<p>If consent is unclear, keep the request general and private. That is the safer default. You can always add detail later if permission is granted and the situation changes.</p>
+
+<h2>Sharing Preferences: Public Prayer vs. Private Request</h2>
+
+<p>Not every request belongs in the same channel. A church needs both public prayer and private care, but they are not the same thing. Choosing the right lane keeps the request useful.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Sharing choice</th>
+      <th>Best when</th>
+      <th>What to say</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Public prayer</td>
+      <td>The need is general and you are comfortable with broader church awareness.</td>
+      <td>“Please pray for our family this week as we travel.”</td>
+    </tr>
+    <tr>
+      <td>Private request</td>
+      <td>The matter is sensitive, personal, or not ready for wider sharing.</td>
+      <td>“Please keep this private and pray for wisdom as we work through a family matter.”</td>
+    </tr>
+    <tr>
+      <td>Limited sharing</td>
+      <td>You want prayer but do not want every detail repeated.</td>
+      <td>“You may share the general need, but please leave out the details.”</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>If you are unsure, choose the more private option. That is the conservative decision and usually the right one. It is easier to expand a request later than to retract details after they have already gone farther than you intended.</p>
+
+<p>If the request becomes something broader for the church to know about, you can also look to the <a href="/news.html">News</a> page for public updates. That page is for church communication, not a place to assume personal details will be posted. Public and personal are not the same category, even when the same people are involved.</p>
+
+<h2>How to Submit</h2>
+
+<p>Once your request is ready, use the church’s normal contact paths. The simplest route is usually the <a href="/contacts.html">Contacts</a> page. If you prefer a form-based route, use <a href="/contact.php">Contact Us</a>. Either way, keep the message short, specific, and consistent with the privacy level you chose.</p>
+
+<p>A helpful submission usually has three parts:</p>
+
+<ol>
+  <li><strong>The request itself:</strong> one or two clear sentences.</li>
+  <li><strong>Your privacy note:</strong> public, private, or limited sharing.</li>
+  <li><strong>A follow-up option:</strong> a phone number or email if you want someone to reach back out.</li>
+</ol>
+
+<p>What happens after that? In practical terms, the church receives the note, reads the request, and handles it according to the communication path and privacy preference you provided. If more information is needed, someone may follow up. If no follow-up is needed, the request can still be prayed over without extra drama. That is usually the best case. Prayer requests are not package tracking.</p>
+
+<p>Do not build your wording around a guaranteed response time or a guaranteed outcome. A church can promise care and diligence. It cannot promise the timing of every answer. Keep the focus on the request itself, and keep praying while the message moves through the normal process.</p>
+
+<p>If you need more than a brief prayer note, say so. A sentence like “We would appreciate a follow-up conversation if possible” gives the church a better signal than a wall of text. If the matter is urgent, say that plainly near the top of the message. Simple language wins here.</p>
+
+<h2>A Short Checklist Before You Send</h2>
+
+<ul>
+  <li>Is the request clear in one sentence?</li>
+  <li>Did you include the type of prayer needed?</li>
+  <li>Did you leave out anything private or unnecessary?</li>
+  <li>Did you note whether the request is public, private, or limited?</li>
+  <li>If it is for someone else, did you mention your relationship and consent?</li>
+  <li>If timing matters, did you include the relevant date or timeframe?</li>
+</ul>
+
+<p>If you can answer yes to those six questions, the request is probably ready. There is no prize for over-writing it.</p>
+
+<h2>Common Mistakes That Make Requests Harder to Use</h2>
+
+<p>Most weak prayer requests fail for ordinary reasons, not dramatic ones. The note is too vague, too long, too private in the wrong place, or too public for the situation. Clean that up before you send it and you save everyone time.</p>
+
+<ul>
+  <li><strong>Leaving out the actual request:</strong> “Please pray for my family” is not enough by itself. Add the reason.</li>
+  <li><strong>Writing a full explanation first:</strong> the prayer point should show up in the first sentence, not after three paragraphs.</li>
+  <li><strong>Using code words:</strong> if the church has to decode your message, it is not a clear request.</li>
+  <li><strong>Sharing too much detail:</strong> more information is not always more help. Sometimes it is just more exposure.</li>
+  <li><strong>Forgetting the privacy note:</strong> public, private, or limited sharing should never be a guessing game.</li>
+</ul>
+
+<p>A practical test helps here: read the request out loud once. If it sounds muddled, you probably wrote too much or too little. Trim it until the sentence does the job.</p>
+
+<h2>Three Finished Examples</h2>
+
+<p>If you would rather copy a complete version than build one piece by piece, use one of these as a model:</p>
+
+<blockquote>
+  <p><strong>Example 1:</strong> “Please pray for my mother as she prepares for surgery on Monday. We are asking for peace, skill for the doctors, and a smooth recovery. Please keep this private.”</p>
+</blockquote>
+
+<blockquote>
+  <p><strong>Example 2:</strong> “Please pray for our family this month as we handle a move, a new school schedule, and a lot of change. We would appreciate wisdom and steadiness. The general request may be shared, but please leave out details.”</p>
+</blockquote>
+
+<blockquote>
+  <p><strong>Example 3:</strong> “Please pray for a friend who is grieving. I have permission to ask for prayer, but not to share more details publicly. Please pray for comfort and rest.”</p>
+</blockquote>
+
+<p>These examples are short for a reason. They say what is needed, when it matters, and how public the request may be. That is the job.</p>
+
+<p>If you need help thinking through what kind of support fits the situation, the <a href="/resources">Resources</a> page is a sensible next stop. It will not solve every problem, which is a rare and refreshing limitation for a church website.</p>
+
+<h2>Closing Encouragement</h2>
+
+<p>A good prayer request is not fancy. It is faithful, clear, and respectful. If you keep the message focused on the need, the timing, and the privacy level, you make it easier for the church to do what churches are supposed to do: pray, care, and respond with wisdom.</p>
+
+<p>Start with the <a href="/contacts.html">Contacts</a> page or <a href="/contact.php">Contact Us</a> form, keep your wording simple, and let the church know whether the request should stay private. If you want to think through other next steps while you wait, the <a href="/resources">Resources</a> page can point you to additional support, and <a href="/news.html">News</a> can help you stay aware of broader church updates.</p>
+
+<p>Finally, keep praying after you submit. That part still matters. The church can handle the message, but you should still bring the burden to God directly. <a href="https://www.biblegateway.com/passage/?search=1+Thessalonians+5%3A17&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">1 Thessalonians 5:17</a> keeps the instruction short for a reason.</p>

 succeeded in 752ms:
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
HTTP/2 200 
date: Tue, 23 Jun 2026 18:32:46 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=w8qIgHYpCuvr4%2B9Cl9NjKaHmCKMB7luwG3IEd02d9MiHkvxCBTxjY8RWnW1iWMThoiWRZrkNJmUuuc9XgQjQLkxz5tvFJQMMkYwoGFPMIed%2BWcAwMouTyNrtMZVUJ7H3pErOuFdlRg%3D%3D"}]}
nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
cf-ray: a10593c6ee9128ff-WAW
alt-svc: h3=":443"; ma=86400


codex
The rendered word count is still a bit below the target, so I’m adding one more practical section instead of relying on markup length. That keeps the post within the brief and gets the body over the line.
apply patch
patch: completed
/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html
diff --git a//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html
new file mode 100644
index 0000000000000000000000000000000000000000..f7fefbfb9d84c8f4b50ac2545de2e25c0e2b1e55
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html
@@ -0,0 +1,297 @@
+<p><strong><em>A prayer request does not need to sound polished. It needs to be clear enough for the church to pray without guessing.</em></strong></p>
+
+<p><strong>By Marcus Reed</strong> | Updated June 23, 2026</p>
+
+<p>When people sit down to write a prayer request, the same practical questions come up fast: How much context is enough? What should stay private? Can I ask for prayer for someone else? And how do I make the request easy for the church to read and use well?</p>
+
+<p>Those are good questions. Prayer is not a performance, and the Bible treats it that way. <a href="https://www.biblegateway.com/passage/?search=Philippians+4%3A6-7&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">Philippians 4:6-7</a> points toward honest, direct prayer; <a href="https://www.biblegateway.com/passage/?search=Matthew+6%3A6&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">Matthew 6:6</a> reminds believers that prayer can also be private and disciplined. A useful church request follows the same logic: enough context to be specific, enough restraint to protect what should stay private, and enough clarity that people can pray with purpose.</p>
+
+<p>If you want the shortest path, start with the church <a href="/contacts.html">Contacts</a> page, or use the site's <a href="/contact.php">contact form</a> if that is more convenient. If you are looking for broader church information while you prepare your message, the <a href="/resources">Resources</a> page is a good place to get oriented.</p>
+
+<figure class="wp-block-image size-large">
+  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg" alt="Planning materials on a desk with a calendar and smartphone for Sunday service coordination" class="wp-image-76" style="width:100%;height:auto;" />
+  <figcaption>A simple request starts with the same discipline as any good plan: enough detail to be useful, not so much that the point gets buried.</figcaption>
+</figure>
+
+<h2>Why We Ask for a Little Context</h2>
+
+<p>Prayer teams do better with signal than with noise. A short note that says what is happening, who it affects, and what kind of prayer is needed gives the church something concrete to carry. A vague request forces people to fill in the blanks, and that is where confusion starts.</p>
+
+<p>Context also helps the church handle requests appropriately. Some needs are fine to share broadly. Some should stay with a limited group. Some should be treated as private pastoral matters. The more clearly you state your preference, the less guesswork is required on the other side.</p>
+
+<p>There is a third reason, and it is the one people often skip: context respects the person who is asking for prayer. A request that is too thin can feel detached; a request that is too detailed can feel exposed. The goal is not to narrate your whole life. The goal is to give enough information for faithful prayer and responsible care.</p>
+
+<h2>A Quick Template You Can Copy and Paste</h2>
+
+<p>If you are not sure where to start, use this format. It is simple on purpose.</p>
+
+<pre><code>Name: [Your name]
+Request: [One short sentence about the need]
+Details: [Only the facts that help people pray well]
+Timeframe: [Today, this week, on [date], or ongoing]
+Ongoing vs. one-time: [One-time / recurring]
+Sharing preference: [Public / private / limited sharing]
+Contact: [Optional phone or email if a follow-up may help]</code></pre>
+
+<p>That is enough for most situations. If you need more privacy, leave out the contact line and keep the description general. If the request is for someone else, say so clearly in the first line so the church understands the relationship and the permission level.</p>
+
+<p>A few quick definitions help here:</p>
+
+<ul>
+  <li><strong>Public prayer:</strong> a request that can be shared more broadly with the church.</li>
+  <li><strong>Private request:</strong> a request that should stay with a smaller, limited group.</li>
+  <li><strong>Ongoing request:</strong> a situation that needs repeated prayer over time.</li>
+  <li><strong>Timeframe:</strong> when the need is happening or when support is most important.</li>
+</ul>
+
+<p>Think of the template as a floor, not a ceiling. You can always add a sentence, but you do not need to write a paragraph for every line. A church can work with a concise request. It cannot work with a mystery wrapped in spiritual language.</p>
+
+<h2>Do Include</h2>
+
+<p>The most useful prayer requests include the facts that actually help someone pray.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Include this</th>
+      <th>Why it helps</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>A clear request in one sentence</td>
+      <td>It tells the reader exactly what kind of prayer you are asking for.</td>
+    </tr>
+    <tr>
+      <td>Specific needs or concerns</td>
+      <td>“Healing,” “wisdom,” “travel safety,” or “comfort” are easier to pray for than a vague concern.</td>
+    </tr>
+    <tr>
+      <td>Relevant dates or timeframes</td>
+      <td>Dates help the church know what matters now, this week, or later.</td>
+    </tr>
+    <tr>
+      <td>Whether the request is confidential</td>
+      <td>Privacy preferences should be stated plainly, not left to interpretation.</td>
+    </tr>
+    <tr>
+      <td>Whether the request is ongoing</td>
+      <td>A continuing need may be placed on a prayer list differently from a one-time update.</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>One useful habit: write the request as if someone else has to read it once, understand it immediately, and pray right away. That is the operational standard. Church communication is not a scavenger hunt.</p>
+
+<p>Here are a few examples of good, concise wording:</p>
+
+<ul>
+  <li><strong>Healing:</strong> “Please pray for Sarah as she prepares for surgery on Thursday. We are asking for peace, skill for the medical team, and steady recovery.”</li>
+  <li><strong>Family support:</strong> “Please pray for our family during a difficult week. We need wisdom, patience, and rest.”</li>
+  <li><strong>Guidance:</strong> “Please pray for discernment as I make a work decision by the end of the month.”</li>
+  <li><strong>Comfort:</strong> “Please pray for comfort and strength after a recent loss. This can stay private.”</li>
+</ul>
+
+<p>Notice what is not happening there. There is no long backstory, no dramatic language, and no pressure to explain every detail. The request stays readable.</p>
+
+<h2>Don’t Include</h2>
+
+<p>Good judgment matters. A prayer request is not the right place for everything.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Leave this out</th>
+      <th>Why to avoid it</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Overly personal details</td>
+      <td>If it would make you uncomfortable to read out loud, it probably should not be in the request.</td>
+    </tr>
+    <tr>
+      <td>Information you do not have permission to share</td>
+      <td>Consent matters, especially when the request involves another person.</td>
+    </tr>
+    <tr>
+      <td>Long background narratives</td>
+      <td>The main need should stay visible. A request that rambles can hide the actual prayer point.</td>
+    </tr>
+    <tr>
+      <td>Unnecessary medical, family, or financial details</td>
+      <td>More detail is not always better. Sometimes it is just more detail.</td>
+    </tr>
+    <tr>
+      <td>Anything you are not comfortable sharing publicly</td>
+      <td>If it feels too exposed, mark it private or keep it brief.</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>If a detail does not help someone pray, leave it out. That is usually the right filter. The church does not need a case file. It needs enough context to respond with care.</p>
+
+<h2>If You Are Requesting Healing, Guidance, or Comfort</h2>
+
+<p>These are the situations where people often over-explain or under-explain. The middle path is usually best.</p>
+
+<p>For healing, say what kind of prayer is needed without turning the note into a medical summary. For guidance, name the decision and the deadline if there is one. For comfort, say what kind of support would be most helpful: peace, strength, patience, reassurance, or rest.</p>
+
+<p>You can borrow one of these patterns:</p>
+
+<ul>
+  <li><strong>Healing:</strong> “Please pray for healing and wise care as I recover from treatment this week.”</li>
+  <li><strong>Guidance:</strong> “Please pray for clarity as our family considers next steps for school and work.”</li>
+  <li><strong>Comfort:</strong> “Please pray for comfort, stability, and help with the next few days.”</li>
+  <li><strong>Strength:</strong> “Please pray for strength to stay steady through a difficult season.”</li>
+</ul>
+
+<p>If you want to keep a request private but still specific, say that directly:</p>
+
+<blockquote>
+  <p>“Please pray for healing for a family member this week. We are not ready to share details publicly, so please keep this private.”</p>
+</blockquote>
+
+<p>That kind of wording does two jobs at once. It gives the church a prayer focus and sets a boundary without making the request awkward.</p>
+
+<p>For a broader biblical frame, <a href="https://www.biblegateway.com/passage/?search=James+5%3A16&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">James 5:16</a> connects prayer with honest confession and mutual care. The point is not performance. The point is trust and clarity.</p>
+
+<h2>If You Are Submitting for Someone Else</h2>
+
+<p>People often ask for prayer on behalf of a spouse, child, parent, friend, or coworker. That is normal. The key is to say two things clearly: your relationship to the person and whether you have permission to share the request.</p>
+
+<p>Useful wording looks like this:</p>
+
+<ul>
+  <li><strong>With consent:</strong> “Please pray for my father, who gave me permission to share that he has a procedure next week.”</li>
+  <li><strong>Without detail:</strong> “Please pray for a friend who is facing a hard family situation.”</li>
+  <li><strong>For a child:</strong> “Please pray for our son as he starts treatment. We are asking for peace and wisdom.”</li>
+</ul>
+
+<p>What matters here is not formality. It is trust. If you are speaking for someone else, do not overshare just because you can. Use the smallest amount of information that still tells the church how to pray.</p>
+
+<p>If consent is unclear, keep the request general and private. That is the safer default. You can always add detail later if permission is granted and the situation changes.</p>
+
+<h2>Sharing Preferences: Public Prayer vs. Private Request</h2>
+
+<p>Not every request belongs in the same channel. A church needs both public prayer and private care, but they are not the same thing. Choosing the right lane keeps the request useful.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Sharing choice</th>
+      <th>Best when</th>
+      <th>What to say</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Public prayer</td>
+      <td>The need is general and you are comfortable with broader church awareness.</td>
+      <td>“Please pray for our family this week as we travel.”</td>
+    </tr>
+    <tr>
+      <td>Private request</td>
+      <td>The matter is sensitive, personal, or not ready for wider sharing.</td>
+      <td>“Please keep this private and pray for wisdom as we work through a family matter.”</td>
+    </tr>
+    <tr>
+      <td>Limited sharing</td>
+      <td>You want prayer but do not want every detail repeated.</td>
+      <td>“You may share the general need, but please leave out the details.”</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>If you are unsure, choose the more private option. That is the conservative decision and usually the right one. It is easier to expand a request later than to retract details after they have already gone farther than you intended.</p>
+
+<p>If the request becomes something broader for the church to know about, you can also look to the <a href="/news.html">News</a> page for public updates. That page is for church communication, not a place to assume personal details will be posted. Public and personal are not the same category, even when the same people are involved.</p>
+
+<h2>How to Submit</h2>
+
+<p>Once your request is ready, use the church’s normal contact paths. The simplest route is usually the <a href="/contacts.html">Contacts</a> page. If you prefer a form-based route, use <a href="/contact.php">Contact Us</a>. Either way, keep the message short, specific, and consistent with the privacy level you chose.</p>
+
+<p>A helpful submission usually has three parts:</p>
+
+<ol>
+  <li><strong>The request itself:</strong> one or two clear sentences.</li>
+  <li><strong>Your privacy note:</strong> public, private, or limited sharing.</li>
+  <li><strong>A follow-up option:</strong> a phone number or email if you want someone to reach back out.</li>
+</ol>
+
+<p>What happens after that? In practical terms, the church receives the note, reads the request, and handles it according to the communication path and privacy preference you provided. If more information is needed, someone may follow up. If no follow-up is needed, the request can still be prayed over without extra drama. That is usually the best case. Prayer requests are not package tracking.</p>
+
+<p>Do not build your wording around a guaranteed response time or a guaranteed outcome. A church can promise care and diligence. It cannot promise the timing of every answer. Keep the focus on the request itself, and keep praying while the message moves through the normal process.</p>
+
+<p>If you need more than a brief prayer note, say so. A sentence like “We would appreciate a follow-up conversation if possible” gives the church a better signal than a wall of text. If the matter is urgent, say that plainly near the top of the message. Simple language wins here.</p>
+
+<h2>A Short Checklist Before You Send</h2>
+
+<ul>
+  <li>Is the request clear in one sentence?</li>
+  <li>Did you include the type of prayer needed?</li>
+  <li>Did you leave out anything private or unnecessary?</li>
+  <li>Did you note whether the request is public, private, or limited?</li>
+  <li>If it is for someone else, did you mention your relationship and consent?</li>
+  <li>If timing matters, did you include the relevant date or timeframe?</li>
+</ul>
+
+<p>If you can answer yes to those six questions, the request is probably ready. There is no prize for over-writing it.</p>
+
+<h2>If You Are Not Sure What to Say</h2>
+
+<p>Some people stall because they think they need perfect wording before they can ask for prayer. They do not. You only need enough clarity to make the need understandable. Start with the most basic version of the request, then add one detail that helps the church pray well. That is often enough.</p>
+
+<p>A simple three-step method works:</p>
+
+<ol>
+  <li><strong>Name the need.</strong> Say whether the prayer is for healing, guidance, comfort, travel, or another concern.</li>
+  <li><strong>Add the timing.</strong> If there is a date, deadline, or season that matters, include it.</li>
+  <li><strong>Set the privacy level.</strong> Tell the church whether the note is public, private, or limited.</li>
+</ol>
+
+<p>If you still feel stuck, write the message as if you were sending it to one mature Christian friend who will pray responsibly and not gossip. That mental model is useful. It trims away performance language and leaves only what matters. If the request gets more specific later, you can always send an update through the same church contact path.</p>
+
+<p>That is another reason the template matters. It lets you begin before you feel fully composed. Most people are not composed when they need prayer. That is usually the point.</p>
+
+<h2>Common Mistakes That Make Requests Harder to Use</h2>
+
+<p>Most weak prayer requests fail for ordinary reasons, not dramatic ones. The note is too vague, too long, too private in the wrong place, or too public for the situation. Clean that up before you send it and you save everyone time.</p>
+
+<ul>
+  <li><strong>Leaving out the actual request:</strong> “Please pray for my family” is not enough by itself. Add the reason.</li>
+  <li><strong>Writing a full explanation first:</strong> the prayer point should show up in the first sentence, not after three paragraphs.</li>
+  <li><strong>Using code words:</strong> if the church has to decode your message, it is not a clear request.</li>
+  <li><strong>Sharing too much detail:</strong> more information is not always more help. Sometimes it is just more exposure.</li>
+  <li><strong>Forgetting the privacy note:</strong> public, private, or limited sharing should never be a guessing game.</li>
+</ul>
+
+<p>A practical test helps here: read the request out loud once. If it sounds muddled, you probably wrote too much or too little. Trim it until the sentence does the job.</p>
+
+<h2>Three Finished Examples</h2>
+
+<p>If you would rather copy a complete version than build one piece by piece, use one of these as a model:</p>
+
+<blockquote>
+  <p><strong>Example 1:</strong> “Please pray for my mother as she prepares for surgery on Monday. We are asking for peace, skill for the doctors, and a smooth recovery. Please keep this private.”</p>
+</blockquote>
+
+<blockquote>
+  <p><strong>Example 2:</strong> “Please pray for our family this month as we handle a move, a new school schedule, and a lot of change. We would appreciate wisdom and steadiness. The general request may be shared, but please leave out details.”</p>
+</blockquote>
+
+<blockquote>
+  <p><strong>Example 3:</strong> “Please pray for a friend who is grieving. I have permission to ask for prayer, but not to share more details publicly. Please pray for comfort and rest.”</p>
+</blockquote>
+
+<p>These examples are short for a reason. They say what is needed, when it matters, and how public the request may be. That is the job.</p>
+
+<p>If you need help thinking through what kind of support fits the situation, the <a href="/resources">Resources</a> page is a sensible next stop. It will not solve every problem, which is a rare and refreshing limitation for a church website.</p>
+
+<h2>Closing Encouragement</h2>
+
+<p>A good prayer request is not fancy. It is faithful, clear, and respectful. If you keep the message focused on the need, the timing, and the privacy level, you make it easier for the church to do what churches are supposed to do: pray, care, and respond with wisdom.</p>
+
+<p>Start with the <a href="/contacts.html">Contacts</a> page or <a href="/contact.php">Contact Us</a> form, keep your wording simple, and let the church know whether the request should stay private. If you want to think through other next steps while you wait, the <a href="/resources">Resources</a> page can point you to additional support, and <a href="/news.html">News</a> can help you stay aware of broader church updates.</p>
+
+<p>Finally, keep praying after you submit. That part still matters. The church can handle the message, but you should still bring the burden to God directly. <a href="https://www.biblegateway.com/passage/?search=1+Thessalonians+5%3A17&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">1 Thessalonians 5:17</a> keeps the instruction short for a reason.</p>

diff --git a//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html
new file mode 100644
index 0000000000000000000000000000000000000000..f7fefbfb9d84c8f4b50ac2545de2e25c0e2b1e55
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html
@@ -0,0 +1,297 @@
+<p><strong><em>A prayer request does not need to sound polished. It needs to be clear enough for the church to pray without guessing.</em></strong></p>
+
+<p><strong>By Marcus Reed</strong> | Updated June 23, 2026</p>
+
+<p>When people sit down to write a prayer request, the same practical questions come up fast: How much context is enough? What should stay private? Can I ask for prayer for someone else? And how do I make the request easy for the church to read and use well?</p>
+
+<p>Those are good questions. Prayer is not a performance, and the Bible treats it that way. <a href="https://www.biblegateway.com/passage/?search=Philippians+4%3A6-7&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">Philippians 4:6-7</a> points toward honest, direct prayer; <a href="https://www.biblegateway.com/passage/?search=Matthew+6%3A6&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">Matthew 6:6</a> reminds believers that prayer can also be private and disciplined. A useful church request follows the same logic: enough context to be specific, enough restraint to protect what should stay private, and enough clarity that people can pray with purpose.</p>
+
+<p>If you want the shortest path, start with the church <a href="/contacts.html">Contacts</a> page, or use the site's <a href="/contact.php">contact form</a> if that is more convenient. If you are looking for broader church information while you prepare your message, the <a href="/resources">Resources</a> page is a good place to get oriented.</p>
+
+<figure class="wp-block-image size-large">
+  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg" alt="Planning materials on a desk with a calendar and smartphone for Sunday service coordination" class="wp-image-76" style="width:100%;height:auto;" />
+  <figcaption>A simple request starts with the same discipline as any good plan: enough detail to be useful, not so much that the point gets buried.</figcaption>
+</figure>
+
+<h2>Why We Ask for a Little Context</h2>
+
+<p>Prayer teams do better with signal than with noise. A short note that says what is happening, who it affects, and what kind of prayer is needed gives the church something concrete to carry. A vague request forces people to fill in the blanks, and that is where confusion starts.</p>
+
+<p>Context also helps the church handle requests appropriately. Some needs are fine to share broadly. Some should stay with a limited group. Some should be treated as private pastoral matters. The more clearly you state your preference, the less guesswork is required on the other side.</p>
+
+<p>There is a third reason, and it is the one people often skip: context respects the person who is asking for prayer. A request that is too thin can feel detached; a request that is too detailed can feel exposed. The goal is not to narrate your whole life. The goal is to give enough information for faithful prayer and responsible care.</p>
+
+<h2>A Quick Template You Can Copy and Paste</h2>
+
+<p>If you are not sure where to start, use this format. It is simple on purpose.</p>
+
+<pre><code>Name: [Your name]
+Request: [One short sentence about the need]
+Details: [Only the facts that help people pray well]
+Timeframe: [Today, this week, on [date], or ongoing]
+Ongoing vs. one-time: [One-time / recurring]
+Sharing preference: [Public / private / limited sharing]
+Contact: [Optional phone or email if a follow-up may help]</code></pre>
+
+<p>That is enough for most situations. If you need more privacy, leave out the contact line and keep the description general. If the request is for someone else, say so clearly in the first line so the church understands the relationship and the permission level.</p>
+
+<p>A few quick definitions help here:</p>
+
+<ul>
+  <li><strong>Public prayer:</strong> a request that can be shared more broadly with the church.</li>
+  <li><strong>Private request:</strong> a request that should stay with a smaller, limited group.</li>
+  <li><strong>Ongoing request:</strong> a situation that needs repeated prayer over time.</li>
+  <li><strong>Timeframe:</strong> when the need is happening or when support is most important.</li>
+</ul>
+
+<p>Think of the template as a floor, not a ceiling. You can always add a sentence, but you do not need to write a paragraph for every line. A church can work with a concise request. It cannot work with a mystery wrapped in spiritual language.</p>
+
+<h2>Do Include</h2>
+
+<p>The most useful prayer requests include the facts that actually help someone pray.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Include this</th>
+      <th>Why it helps</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>A clear request in one sentence</td>
+      <td>It tells the reader exactly what kind of prayer you are asking for.</td>
+    </tr>
+    <tr>
+      <td>Specific needs or concerns</td>
+      <td>“Healing,” “wisdom,” “travel safety,” or “comfort” are easier to pray for than a vague concern.</td>
+    </tr>
+    <tr>
+      <td>Relevant dates or timeframes</td>
+      <td>Dates help the church know what matters now, this week, or later.</td>
+    </tr>
+    <tr>
+      <td>Whether the request is confidential</td>
+      <td>Privacy preferences should be stated plainly, not left to interpretation.</td>
+    </tr>
+    <tr>
+      <td>Whether the request is ongoing</td>
+      <td>A continuing need may be placed on a prayer list differently from a one-time update.</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>One useful habit: write the request as if someone else has to read it once, understand it immediately, and pray right away. That is the operational standard. Church communication is not a scavenger hunt.</p>
+
+<p>Here are a few examples of good, concise wording:</p>
+
+<ul>
+  <li><strong>Healing:</strong> “Please pray for Sarah as she prepares for surgery on Thursday. We are asking for peace, skill for the medical team, and steady recovery.”</li>
+  <li><strong>Family support:</strong> “Please pray for our family during a difficult week. We need wisdom, patience, and rest.”</li>
+  <li><strong>Guidance:</strong> “Please pray for discernment as I make a work decision by the end of the month.”</li>
+  <li><strong>Comfort:</strong> “Please pray for comfort and strength after a recent loss. This can stay private.”</li>
+</ul>
+
+<p>Notice what is not happening there. There is no long backstory, no dramatic language, and no pressure to explain every detail. The request stays readable.</p>
+
+<h2>Don’t Include</h2>
+
+<p>Good judgment matters. A prayer request is not the right place for everything.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Leave this out</th>
+      <th>Why to avoid it</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Overly personal details</td>
+      <td>If it would make you uncomfortable to read out loud, it probably should not be in the request.</td>
+    </tr>
+    <tr>
+      <td>Information you do not have permission to share</td>
+      <td>Consent matters, especially when the request involves another person.</td>
+    </tr>
+    <tr>
+      <td>Long background narratives</td>
+      <td>The main need should stay visible. A request that rambles can hide the actual prayer point.</td>
+    </tr>
+    <tr>
+      <td>Unnecessary medical, family, or financial details</td>
+      <td>More detail is not always better. Sometimes it is just more detail.</td>
+    </tr>
+    <tr>
+      <td>Anything you are not comfortable sharing publicly</td>
+      <td>If it feels too exposed, mark it private or keep it brief.</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>If a detail does not help someone pray, leave it out. That is usually the right filter. The church does not need a case file. It needs enough context to respond with care.</p>
+
+<h2>If You Are Requesting Healing, Guidance, or Comfort</h2>
+
+<p>These are the situations where people often over-explain or under-explain. The middle path is usually best.</p>
+
+<p>For healing, say what kind of prayer is needed without turning the note into a medical summary. For guidance, name the decision and the deadline if there is one. For comfort, say what kind of support would be most helpful: peace, strength, patience, reassurance, or rest.</p>
+
+<p>You can borrow one of these patterns:</p>
+
+<ul>
+  <li><strong>Healing:</strong> “Please pray for healing and wise care as I recover from treatment this week.”</li>
+  <li><strong>Guidance:</strong> “Please pray for clarity as our family considers next steps for school and work.”</li>
+  <li><strong>Comfort:</strong> “Please pray for comfort, stability, and help with the next few days.”</li>
+  <li><strong>Strength:</strong> “Please pray for strength to stay steady through a difficult season.”</li>
+</ul>
+
+<p>If you want to keep a request private but still specific, say that directly:</p>
+
+<blockquote>
+  <p>“Please pray for healing for a family member this week. We are not ready to share details publicly, so please keep this private.”</p>
+</blockquote>
+
+<p>That kind of wording does two jobs at once. It gives the church a prayer focus and sets a boundary without making the request awkward.</p>
+
+<p>For a broader biblical frame, <a href="https://www.biblegateway.com/passage/?search=James+5%3A16&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">James 5:16</a> connects prayer with honest confession and mutual care. The point is not performance. The point is trust and clarity.</p>
+
+<h2>If You Are Submitting for Someone Else</h2>
+
+<p>People often ask for prayer on behalf of a spouse, child, parent, friend, or coworker. That is normal. The key is to say two things clearly: your relationship to the person and whether you have permission to share the request.</p>
+
+<p>Useful wording looks like this:</p>
+
+<ul>
+  <li><strong>With consent:</strong> “Please pray for my father, who gave me permission to share that he has a procedure next week.”</li>
+  <li><strong>Without detail:</strong> “Please pray for a friend who is facing a hard family situation.”</li>
+  <li><strong>For a child:</strong> “Please pray for our son as he starts treatment. We are asking for peace and wisdom.”</li>
+</ul>
+
+<p>What matters here is not formality. It is trust. If you are speaking for someone else, do not overshare just because you can. Use the smallest amount of information that still tells the church how to pray.</p>
+
+<p>If consent is unclear, keep the request general and private. That is the safer default. You can always add detail later if permission is granted and the situation changes.</p>
+
+<h2>Sharing Preferences: Public Prayer vs. Private Request</h2>
+
+<p>Not every request belongs in the same channel. A church needs both public prayer and private care, but they are not the same thing. Choosing the right lane keeps the request useful.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Sharing choice</th>
+      <th>Best when</th>
+      <th>What to say</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Public prayer</td>
+      <td>The need is general and you are comfortable with broader church awareness.</td>
+      <td>“Please pray for our family this week as we travel.”</td>
+    </tr>
+    <tr>
+      <td>Private request</td>
+      <td>The matter is sensitive, personal, or not ready for wider sharing.</td>
+      <td>“Please keep this private and pray for wisdom as we work through a family matter.”</td>
+    </tr>
+    <tr>
+      <td>Limited sharing</td>
+      <td>You want prayer but do not want every detail repeated.</td>
+      <td>“You may share the general need, but please leave out the details.”</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>If you are unsure, choose the more private option. That is the conservative decision and usually the right one. It is easier to expand a request later than to retract details after they have already gone farther than you intended.</p>
+
+<p>If the request becomes something broader for the church to know about, you can also look to the <a href="/news.html">News</a> page for public updates. That page is for church communication, not a place to assume personal details will be posted. Public and personal are not the same category, even when the same people are involved.</p>
+
+<h2>How to Submit</h2>
+
+<p>Once your request is ready, use the church’s normal contact paths. The simplest route is usually the <a href="/contacts.html">Contacts</a> page. If you prefer a form-based route, use <a href="/contact.php">Contact Us</a>. Either way, keep the message short, specific, and consistent with the privacy level you chose.</p>
+
+<p>A helpful submission usually has three parts:</p>
+
+<ol>
+  <li><strong>The request itself:</strong> one or two clear sentences.</li>
+  <li><strong>Your privacy note:</strong> public, private, or limited sharing.</li>
+  <li><strong>A follow-up option:</strong> a phone number or email if you want someone to reach back out.</li>
+</ol>
+
+<p>What happens after that? In practical terms, the church receives the note, reads the request, and handles it according to the communication path and privacy preference you provided. If more information is needed, someone may follow up. If no follow-up is needed, the request can still be prayed over without extra drama. That is usually the best case. Prayer requests are not package tracking.</p>
+
+<p>Do not build your wording around a guaranteed response time or a guaranteed outcome. A church can promise care and diligence. It cannot promise the timing of every answer. Keep the focus on the request itself, and keep praying while the message moves through the normal process.</p>
+
+<p>If you need more than a brief prayer note, say so. A sentence like “We would appreciate a follow-up conversation if possible” gives the church a better signal than a wall of text. If the matter is urgent, say that plainly near the top of the message. Simple language wins here.</p>
+
+<h2>A Short Checklist Before You Send</h2>
+
+<ul>
+  <li>Is the request clear in one sentence?</li>
+  <li>Did you include the type of prayer needed?</li>
+  <li>Did you leave out anything private or unnecessary?</li>
+  <li>Did you note whether the request is public, private, or limited?</li>
+  <li>If it is for someone else, did you mention your relationship and consent?</li>
+  <li>If timing matters, did you include the relevant date or timeframe?</li>
+</ul>
+
+<p>If you can answer yes to those six questions, the request is probably ready. There is no prize for over-writing it.</p>
+
+<h2>If You Are Not Sure What to Say</h2>
+
+<p>Some people stall because they think they need perfect wording before they can ask for prayer. They do not. You only need enough clarity to make the need understandable. Start with the most basic version of the request, then add one detail that helps the church pray well. That is often enough.</p>
+
+<p>A simple three-step method works:</p>
+
+<ol>
+  <li><strong>Name the need.</strong> Say whether the prayer is for healing, guidance, comfort, travel, or another concern.</li>
+  <li><strong>Add the timing.</strong> If there is a date, deadline, or season that matters, include it.</li>
+  <li><strong>Set the privacy level.</strong> Tell the church whether the note is public, private, or limited.</li>
+</ol>
+
+<p>If you still feel stuck, write the message as if you were sending it to one mature Christian friend who will pray responsibly and not gossip. That mental model is useful. It trims away performance language and leaves only what matters. If the request gets more specific later, you can always send an update through the same church contact path.</p>
+
+<p>That is another reason the template matters. It lets you begin before you feel fully composed. Most people are not composed when they need prayer. That is usually the point.</p>
+
+<h2>Common Mistakes That Make Requests Harder to Use</h2>
+
+<p>Most weak prayer requests fail for ordinary reasons, not dramatic ones. The note is too vague, too long, too private in the wrong place, or too public for the situation. Clean that up before you send it and you save everyone time.</p>
+
+<ul>
+  <li><strong>Leaving out the actual request:</strong> “Please pray for my family” is not enough by itself. Add the reason.</li>
+  <li><strong>Writing a full explanation first:</strong> the prayer point should show up in the first sentence, not after three paragraphs.</li>
+  <li><strong>Using code words:</strong> if the church has to decode your message, it is not a clear request.</li>
+  <li><strong>Sharing too much detail:</strong> more information is not always more help. Sometimes it is just more exposure.</li>
+  <li><strong>Forgetting the privacy note:</strong> public, private, or limited sharing should never be a guessing game.</li>
+</ul>
+
+<p>A practical test helps here: read the request out loud once. If it sounds muddled, you probably wrote too much or too little. Trim it until the sentence does the job.</p>
+
+<h2>Three Finished Examples</h2>
+
+<p>If you would rather copy a complete version than build one piece by piece, use one of these as a model:</p>
+
+<blockquote>
+  <p><strong>Example 1:</strong> “Please pray for my mother as she prepares for surgery on Monday. We are asking for peace, skill for the doctors, and a smooth recovery. Please keep this private.”</p>
+</blockquote>
+
+<blockquote>
+  <p><strong>Example 2:</strong> “Please pray for our family this month as we handle a move, a new school schedule, and a lot of change. We would appreciate wisdom and steadiness. The general request may be shared, but please leave out details.”</p>
+</blockquote>
+
+<blockquote>
+  <p><strong>Example 3:</strong> “Please pray for a friend who is grieving. I have permission to ask for prayer, but not to share more details publicly. Please pray for comfort and rest.”</p>
+</blockquote>
+
+<p>These examples are short for a reason. They say what is needed, when it matters, and how public the request may be. That is the job.</p>
+
+<p>If you need help thinking through what kind of support fits the situation, the <a href="/resources">Resources</a> page is a sensible next stop. It will not solve every problem, which is a rare and refreshing limitation for a church website.</p>
+
+<h2>Closing Encouragement</h2>
+
+<p>A good prayer request is not fancy. It is faithful, clear, and respectful. If you keep the message focused on the need, the timing, and the privacy level, you make it easier for the church to do what churches are supposed to do: pray, care, and respond with wisdom.</p>
+
+<p>Start with the <a href="/contacts.html">Contacts</a> page or <a href="/contact.php">Contact Us</a> form, keep your wording simple, and let the church know whether the request should stay private. If you want to think through other next steps while you wait, the <a href="/resources">Resources</a> page can point you to additional support, and <a href="/news.html">News</a> can help you stay aware of broader church updates.</p>
+
+<p>Finally, keep praying after you submit. That part still matters. The church can handle the message, but you should still bring the burden to God directly. <a href="https://www.biblegateway.com/passage/?search=1+Thessalonians+5%3A17&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">1 Thessalonians 5:17</a> keeps the instruction short for a reason.</p>

codex
I’ve added the final guidance section. I’m updating the published post now so the live version matches the finished draft, then I’ll re-run the verification checks.
exec
/bin/bash -lc 'wp post update 116 --post_content="$(<wp-content/uploads/flatlogic-article-tasks/job-506/article.html)"' in /home/ubuntu/apps/ridgecrestchurch.com
diff --git a//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html
new file mode 100644
index 0000000000000000000000000000000000000000..f7fefbfb9d84c8f4b50ac2545de2e25c0e2b1e55
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html
@@ -0,0 +1,297 @@
+<p><strong><em>A prayer request does not need to sound polished. It needs to be clear enough for the church to pray without guessing.</em></strong></p>
+
+<p><strong>By Marcus Reed</strong> | Updated June 23, 2026</p>
+
+<p>When people sit down to write a prayer request, the same practical questions come up fast: How much context is enough? What should stay private? Can I ask for prayer for someone else? And how do I make the request easy for the church to read and use well?</p>
+
+<p>Those are good questions. Prayer is not a performance, and the Bible treats it that way. <a href="https://www.biblegateway.com/passage/?search=Philippians+4%3A6-7&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">Philippians 4:6-7</a> points toward honest, direct prayer; <a href="https://www.biblegateway.com/passage/?search=Matthew+6%3A6&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">Matthew 6:6</a> reminds believers that prayer can also be private and disciplined. A useful church request follows the same logic: enough context to be specific, enough restraint to protect what should stay private, and enough clarity that people can pray with purpose.</p>
+
+<p>If you want the shortest path, start with the church <a href="/contacts.html">Contacts</a> page, or use the site's <a href="/contact.php">contact form</a> if that is more convenient. If you are looking for broader church information while you prepare your message, the <a href="/resources">Resources</a> page is a good place to get oriented.</p>
+
+<figure class="wp-block-image size-large">
+  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg" alt="Planning materials on a desk with a calendar and smartphone for Sunday service coordination" class="wp-image-76" style="width:100%;height:auto;" />
+  <figcaption>A simple request starts with the same discipline as any good plan: enough detail to be useful, not so much that the point gets buried.</figcaption>
+</figure>
+
+<h2>Why We Ask for a Little Context</h2>
+
+<p>Prayer teams do better with signal than with noise. A short note that says what is happening, who it affects, and what kind of prayer is needed gives the church something concrete to carry. A vague request forces people to fill in the blanks, and that is where confusion starts.</p>
+
+<p>Context also helps the church handle requests appropriately. Some needs are fine to share broadly. Some should stay with a limited group. Some should be treated as private pastoral matters. The more clearly you state your preference, the less guesswork is required on the other side.</p>
+
+<p>There is a third reason, and it is the one people often skip: context respects the person who is asking for prayer. A request that is too thin can feel detached; a request that is too detailed can feel exposed. The goal is not to narrate your whole life. The goal is to give enough information for faithful prayer and responsible care.</p>
+
+<h2>A Quick Template You Can Copy and Paste</h2>
+
+<p>If you are not sure where to start, use this format. It is simple on purpose.</p>
+
+<pre><code>Name: [Your name]
+Request: [One short sentence about the need]
+Details: [Only the facts that help people pray well]
+Timeframe: [Today, this week, on [date], or ongoing]
+Ongoing vs. one-time: [One-time / recurring]
+Sharing preference: [Public / private / limited sharing]
+Contact: [Optional phone or email if a follow-up may help]</code></pre>
+
+<p>That is enough for most situations. If you need more privacy, leave out the contact line and keep the description general. If the request is for someone else, say so clearly in the first line so the church understands the relationship and the permission level.</p>
+
+<p>A few quick definitions help here:</p>
+
+<ul>
+  <li><strong>Public prayer:</strong> a request that can be shared more broadly with the church.</li>
+  <li><strong>Private request:</strong> a request that should stay with a smaller, limited group.</li>
+  <li><strong>Ongoing request:</strong> a situation that needs repeated prayer over time.</li>
+  <li><strong>Timeframe:</strong> when the need is happening or when support is most important.</li>
+</ul>
+
+<p>Think of the template as a floor, not a ceiling. You can always add a sentence, but you do not need to write a paragraph for every line. A church can work with a concise request. It cannot work with a mystery wrapped in spiritual language.</p>
+
+<h2>Do Include</h2>
+
+<p>The most useful prayer requests include the facts that actually help someone pray.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Include this</th>
+      <th>Why it helps</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>A clear request in one sentence</td>
+      <td>It tells the reader exactly what kind of prayer you are asking for.</td>
+    </tr>
+    <tr>
+      <td>Specific needs or concerns</td>
+      <td>“Healing,” “wisdom,” “travel safety,” or “comfort” are easier to pray for than a vague concern.</td>
+    </tr>
+    <tr>
+      <td>Relevant dates or timeframes</td>
+      <td>Dates help the church know what matters now, this week, or later.</td>
+    </tr>
+    <tr>
+      <td>Whether the request is confidential</td>
+      <td>Privacy preferences should be stated plainly, not left to interpretation.</td>
+    </tr>
+    <tr>
+      <td>Whether the request is ongoing</td>
+      <td>A continuing need may be placed on a prayer list differently from a one-time update.</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>One useful habit: write the request as if someone else has to read it once, understand it immediately, and pray right away. That is the operational standard. Church communication is not a scavenger hunt.</p>
+
+<p>Here are a few examples of good, concise wording:</p>
+
+<ul>
+  <li><strong>Healing:</strong> “Please pray for Sarah as she prepares for surgery on Thursday. We are asking for peace, skill for the medical team, and steady recovery.”</li>
+  <li><strong>Family support:</strong> “Please pray for our family during a difficult week. We need wisdom, patience, and rest.”</li>
+  <li><strong>Guidance:</strong> “Please pray for discernment as I make a work decision by the end of the month.”</li>
+  <li><strong>Comfort:</strong> “Please pray for comfort and strength after a recent loss. This can stay private.”</li>
+</ul>
+
+<p>Notice what is not happening there. There is no long backstory, no dramatic language, and no pressure to explain every detail. The request stays readable.</p>
+
+<h2>Don’t Include</h2>
+
+<p>Good judgment matters. A prayer request is not the right place for everything.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Leave this out</th>
+      <th>Why to avoid it</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Overly personal details</td>
+      <td>If it would make you uncomfortable to read out loud, it probably should not be in the request.</td>
+    </tr>
+    <tr>
+      <td>Information you do not have permission to share</td>
+      <td>Consent matters, especially when the request involves another person.</td>
+    </tr>
+    <tr>
+      <td>Long background narratives</td>
+      <td>The main need should stay visible. A request that rambles can hide the actual prayer point.</td>
+    </tr>
+    <tr>
+      <td>Unnecessary medical, family, or financial details</td>
+      <td>More detail is not always better. Sometimes it is just more detail.</td>
+    </tr>
+    <tr>
+      <td>Anything you are not comfortable sharing publicly</td>
+      <td>If it feels too exposed, mark it private or keep it brief.</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>If a detail does not help someone pray, leave it out. That is usually the right filter. The church does not need a case file. It needs enough context to respond with care.</p>
+
+<h2>If You Are Requesting Healing, Guidance, or Comfort</h2>
+
+<p>These are the situations where people often over-explain or under-explain. The middle path is usually best.</p>
+
+<p>For healing, say what kind of prayer is needed without turning the note into a medical summary. For guidance, name the decision and the deadline if there is one. For comfort, say what kind of support would be most helpful: peace, strength, patience, reassurance, or rest.</p>
+
+<p>You can borrow one of these patterns:</p>
+
+<ul>
+  <li><strong>Healing:</strong> “Please pray for healing and wise care as I recover from treatment this week.”</li>
+  <li><strong>Guidance:</strong> “Please pray for clarity as our family considers next steps for school and work.”</li>
+  <li><strong>Comfort:</strong> “Please pray for comfort, stability, and help with the next few days.”</li>
+  <li><strong>Strength:</strong> “Please pray for strength to stay steady through a difficult season.”</li>
+</ul>
+
+<p>If you want to keep a request private but still specific, say that directly:</p>
+
+<blockquote>
+  <p>“Please pray for healing for a family member this week. We are not ready to share details publicly, so please keep this private.”</p>
+</blockquote>
+
+<p>That kind of wording does two jobs at once. It gives the church a prayer focus and sets a boundary without making the request awkward.</p>
+
+<p>For a broader biblical frame, <a href="https://www.biblegateway.com/passage/?search=James+5%3A16&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">James 5:16</a> connects prayer with honest confession and mutual care. The point is not performance. The point is trust and clarity.</p>
+
+<h2>If You Are Submitting for Someone Else</h2>
+
+<p>People often ask for prayer on behalf of a spouse, child, parent, friend, or coworker. That is normal. The key is to say two things clearly: your relationship to the person and whether you have permission to share the request.</p>
+
+<p>Useful wording looks like this:</p>
+
+<ul>
+  <li><strong>With consent:</strong> “Please pray for my father, who gave me permission to share that he has a procedure next week.”</li>
+  <li><strong>Without detail:</strong> “Please pray for a friend who is facing a hard family situation.”</li>
+  <li><strong>For a child:</strong> “Please pray for our son as he starts treatment. We are asking for peace and wisdom.”</li>
+</ul>
+
+<p>What matters here is not formality. It is trust. If you are speaking for someone else, do not overshare just because you can. Use the smallest amount of information that still tells the church how to pray.</p>
+
+<p>If consent is unclear, keep the request general and private. That is the safer default. You can always add detail later if permission is granted and the situation changes.</p>
+
+<h2>Sharing Preferences: Public Prayer vs. Private Request</h2>
+
+<p>Not every request belongs in the same channel. A church needs both public prayer and private care, but they are not the same thing. Choosing the right lane keeps the request useful.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Sharing choice</th>
+      <th>Best when</th>
+      <th>What to say</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Public prayer</td>
+      <td>The need is general and you are comfortable with broader church awareness.</td>
+      <td>“Please pray for our family this week as we travel.”</td>
+    </tr>
+    <tr>
+      <td>Private request</td>
+      <td>The matter is sensitive, personal, or not ready for wider sharing.</td>
+      <td>“Please keep this private and pray for wisdom as we work through a family matter.”</td>
+    </tr>
+    <tr>
+      <td>Limited sharing</td>
+      <td>You want prayer but do not want every detail repeated.</td>
+      <td>“You may share the general need, but please leave out the details.”</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>If you are unsure, choose the more private option. That is the conservative decision and usually the right one. It is easier to expand a request later than to retract details after they have already gone farther than you intended.</p>
+
+<p>If the request becomes something broader for the church to know about, you can also look to the <a href="/news.html">News</a> page for public updates. That page is for church communication, not a place to assume personal details will be posted. Public and personal are not the same category, even when the same people are involved.</p>
+
+<h2>How to Submit</h2>
+
+<p>Once your request is ready, use the church’s normal contact paths. The simplest route is usually the <a href="/contacts.html">Contacts</a> page. If you prefer a form-based route, use <a href="/contact.php">Contact Us</a>. Either way, keep the message short, specific, and consistent with the privacy level you chose.</p>
+
+<p>A helpful submission usually has three parts:</p>
+
+<ol>
+  <li><strong>The request itself:</strong> one or two clear sentences.</li>
+  <li><strong>Your privacy note:</strong> public, private, or limited sharing.</li>
+  <li><strong>A follow-up option:</strong> a phone number or email if you want someone to reach back out.</li>
+</ol>
+
+<p>What happens after that? In practical terms, the church receives the note, reads the request, and handles it according to the communication path and privacy preference you provided. If more information is needed, someone may follow up. If no follow-up is needed, the request can still be prayed over without extra drama. That is usually the best case. Prayer requests are not package tracking.</p>
+
+<p>Do not build your wording around a guaranteed response time or a guaranteed outcome. A church can promise care and diligence. It cannot promise the timing of every answer. Keep the focus on the request itself, and keep praying while the message moves through the normal process.</p>
+
+<p>If you need more than a brief prayer note, say so. A sentence like “We would appreciate a follow-up conversation if possible” gives the church a better signal than a wall of text. If the matter is urgent, say that plainly near the top of the message. Simple language wins here.</p>
+
+<h2>A Short Checklist Before You Send</h2>
+
+<ul>
+  <li>Is the request clear in one sentence?</li>
+  <li>Did you include the type of prayer needed?</li>
+  <li>Did you leave out anything private or unnecessary?</li>
+  <li>Did you note whether the request is public, private, or limited?</li>
+  <li>If it is for someone else, did you mention your relationship and consent?</li>
+  <li>If timing matters, did you include the relevant date or timeframe?</li>
+</ul>
+
+<p>If you can answer yes to those six questions, the request is probably ready. There is no prize for over-writing it.</p>
+
+<h2>If You Are Not Sure What to Say</h2>
+
+<p>Some people stall because they think they need perfect wording before they can ask for prayer. They do not. You only need enough clarity to make the need understandable. Start with the most basic version of the request, then add one detail that helps the church pray well. That is often enough.</p>
+
+<p>A simple three-step method works:</p>
+
+<ol>
+  <li><strong>Name the need.</strong> Say whether the prayer is for healing, guidance, comfort, travel, or another concern.</li>
+  <li><strong>Add the timing.</strong> If there is a date, deadline, or season that matters, include it.</li>
+  <li><strong>Set the privacy level.</strong> Tell the church whether the note is public, private, or limited.</li>
+</ol>
+
+<p>If you still feel stuck, write the message as if you were sending it to one mature Christian friend who will pray responsibly and not gossip. That mental model is useful. It trims away performance language and leaves only what matters. If the request gets more specific later, you can always send an update through the same church contact path.</p>
+
+<p>That is another reason the template matters. It lets you begin before you feel fully composed. Most people are not composed when they need prayer. That is usually the point.</p>
+
+<h2>Common Mistakes That Make Requests Harder to Use</h2>
+
+<p>Most weak prayer requests fail for ordinary reasons, not dramatic ones. The note is too vague, too long, too private in the wrong place, or too public for the situation. Clean that up before you send it and you save everyone time.</p>
+
+<ul>
+  <li><strong>Leaving out the actual request:</strong> “Please pray for my family” is not enough by itself. Add the reason.</li>
+  <li><strong>Writing a full explanation first:</strong> the prayer point should show up in the first sentence, not after three paragraphs.</li>
+  <li><strong>Using code words:</strong> if the church has to decode your message, it is not a clear request.</li>
+  <li><strong>Sharing too much detail:</strong> more information is not always more help. Sometimes it is just more exposure.</li>
+  <li><strong>Forgetting the privacy note:</strong> public, private, or limited sharing should never be a guessing game.</li>
+</ul>
+
+<p>A practical test helps here: read the request out loud once. If it sounds muddled, you probably wrote too much or too little. Trim it until the sentence does the job.</p>
+
+<h2>Three Finished Examples</h2>
+
+<p>If you would rather copy a complete version than build one piece by piece, use one of these as a model:</p>
+
+<blockquote>
+  <p><strong>Example 1:</strong> “Please pray for my mother as she prepares for surgery on Monday. We are asking for peace, skill for the doctors, and a smooth recovery. Please keep this private.”</p>
+</blockquote>
+
+<blockquote>
+  <p><strong>Example 2:</strong> “Please pray for our family this month as we handle a move, a new school schedule, and a lot of change. We would appreciate wisdom and steadiness. The general request may be shared, but please leave out details.”</p>
+</blockquote>
+
+<blockquote>
+  <p><strong>Example 3:</strong> “Please pray for a friend who is grieving. I have permission to ask for prayer, but not to share more details publicly. Please pray for comfort and rest.”</p>
+</blockquote>
+
+<p>These examples are short for a reason. They say what is needed, when it matters, and how public the request may be. That is the job.</p>
+
+<p>If you need help thinking through what kind of support fits the situation, the <a href="/resources">Resources</a> page is a sensible next stop. It will not solve every problem, which is a rare and refreshing limitation for a church website.</p>
+
+<h2>Closing Encouragement</h2>
+
+<p>A good prayer request is not fancy. It is faithful, clear, and respectful. If you keep the message focused on the need, the timing, and the privacy level, you make it easier for the church to do what churches are supposed to do: pray, care, and respond with wisdom.</p>
+
+<p>Start with the <a href="/contacts.html">Contacts</a> page or <a href="/contact.php">Contact Us</a> form, keep your wording simple, and let the church know whether the request should stay private. If you want to think through other next steps while you wait, the <a href="/resources">Resources</a> page can point you to additional support, and <a href="/news.html">News</a> can help you stay aware of broader church updates.</p>
+
+<p>Finally, keep praying after you submit. That part still matters. The church can handle the message, but you should still bring the burden to God directly. <a href="https://www.biblegateway.com/passage/?search=1+Thessalonians+5%3A17&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">1 Thessalonians 5:17</a> keeps the instruction short for a reason.</p>

 succeeded in 684ms:
Success: Updated post 116.

codex
The live post is updated. I’m checking the final rendered text count and the page output one more time so I can report the result accurately.
exec
/bin/bash -lc "wp eval '"'$post = get_post(116); echo str_word_count(wp_strip_all_tags($post->post_content)) . PHP_EOL;'"'" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "curl -L --max-redirs 3 https://ridgecrestchurch.com/blog/ | rg -n 'how-to-prepare-prayer-request-template|How to Prepare a Prayer Request for Ridgecrest'" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "curl -L --max-redirs 3 https://ridgecrestchurch.com/how-to-prepare-prayer-request-template/ | rg -n 'wordCount|sunday-service-planning-desk.jpg|wp-image-76|If You Are Not Sure What to Say|Common Mistakes That Make Requests Harder to Use'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 549ms:
2627

diff --git a//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html
new file mode 100644
index 0000000000000000000000000000000000000000..f7fefbfb9d84c8f4b50ac2545de2e25c0e2b1e55
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html
@@ -0,0 +1,297 @@
+<p><strong><em>A prayer request does not need to sound polished. It needs to be clear enough for the church to pray without guessing.</em></strong></p>
+
+<p><strong>By Marcus Reed</strong> | Updated June 23, 2026</p>
+
+<p>When people sit down to write a prayer request, the same practical questions come up fast: How much context is enough? What should stay private? Can I ask for prayer for someone else? And how do I make the request easy for the church to read and use well?</p>
+
+<p>Those are good questions. Prayer is not a performance, and the Bible treats it that way. <a href="https://www.biblegateway.com/passage/?search=Philippians+4%3A6-7&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">Philippians 4:6-7</a> points toward honest, direct prayer; <a href="https://www.biblegateway.com/passage/?search=Matthew+6%3A6&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">Matthew 6:6</a> reminds believers that prayer can also be private and disciplined. A useful church request follows the same logic: enough context to be specific, enough restraint to protect what should stay private, and enough clarity that people can pray with purpose.</p>
+
+<p>If you want the shortest path, start with the church <a href="/contacts.html">Contacts</a> page, or use the site's <a href="/contact.php">contact form</a> if that is more convenient. If you are looking for broader church information while you prepare your message, the <a href="/resources">Resources</a> page is a good place to get oriented.</p>
+
+<figure class="wp-block-image size-large">
+  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg" alt="Planning materials on a desk with a calendar and smartphone for Sunday service coordination" class="wp-image-76" style="width:100%;height:auto;" />
+  <figcaption>A simple request starts with the same discipline as any good plan: enough detail to be useful, not so much that the point gets buried.</figcaption>
+</figure>
+
+<h2>Why We Ask for a Little Context</h2>
+
+<p>Prayer teams do better with signal than with noise. A short note that says what is happening, who it affects, and what kind of prayer is needed gives the church something concrete to carry. A vague request forces people to fill in the blanks, and that is where confusion starts.</p>
+
+<p>Context also helps the church handle requests appropriately. Some needs are fine to share broadly. Some should stay with a limited group. Some should be treated as private pastoral matters. The more clearly you state your preference, the less guesswork is required on the other side.</p>
+
+<p>There is a third reason, and it is the one people often skip: context respects the person who is asking for prayer. A request that is too thin can feel detached; a request that is too detailed can feel exposed. The goal is not to narrate your whole life. The goal is to give enough information for faithful prayer and responsible care.</p>
+
+<h2>A Quick Template You Can Copy and Paste</h2>
+
+<p>If you are not sure where to start, use this format. It is simple on purpose.</p>
+
+<pre><code>Name: [Your name]
+Request: [One short sentence about the need]
+Details: [Only the facts that help people pray well]
+Timeframe: [Today, this week, on [date], or ongoing]
+Ongoing vs. one-time: [One-time / recurring]
+Sharing preference: [Public / private / limited sharing]
+Contact: [Optional phone or email if a follow-up may help]</code></pre>
+
+<p>That is enough for most situations. If you need more privacy, leave out the contact line and keep the description general. If the request is for someone else, say so clearly in the first line so the church understands the relationship and the permission level.</p>
+
+<p>A few quick definitions help here:</p>
+
+<ul>
+  <li><strong>Public prayer:</strong> a request that can be shared more broadly with the church.</li>
+  <li><strong>Private request:</strong> a request that should stay with a smaller, limited group.</li>
+  <li><strong>Ongoing request:</strong> a situation that needs repeated prayer over time.</li>
+  <li><strong>Timeframe:</strong> when the need is happening or when support is most important.</li>
+</ul>
+
+<p>Think of the template as a floor, not a ceiling. You can always add a sentence, but you do not need to write a paragraph for every line. A church can work with a concise request. It cannot work with a mystery wrapped in spiritual language.</p>
+
+<h2>Do Include</h2>
+
+<p>The most useful prayer requests include the facts that actually help someone pray.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Include this</th>
+      <th>Why it helps</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>A clear request in one sentence</td>
+      <td>It tells the reader exactly what kind of prayer you are asking for.</td>
+    </tr>
+    <tr>
+      <td>Specific needs or concerns</td>
+      <td>“Healing,” “wisdom,” “travel safety,” or “comfort” are easier to pray for than a vague concern.</td>
+    </tr>
+    <tr>
+      <td>Relevant dates or timeframes</td>
+      <td>Dates help the church know what matters now, this week, or later.</td>
+    </tr>
+    <tr>
+      <td>Whether the request is confidential</td>
+      <td>Privacy preferences should be stated plainly, not left to interpretation.</td>
+    </tr>
+    <tr>
+      <td>Whether the request is ongoing</td>
+      <td>A continuing need may be placed on a prayer list differently from a one-time update.</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>One useful habit: write the request as if someone else has to read it once, understand it immediately, and pray right away. That is the operational standard. Church communication is not a scavenger hunt.</p>
+
+<p>Here are a few examples of good, concise wording:</p>
+
+<ul>
+  <li><strong>Healing:</strong> “Please pray for Sarah as she prepares for surgery on Thursday. We are asking for peace, skill for the medical team, and steady recovery.”</li>
+  <li><strong>Family support:</strong> “Please pray for our family during a difficult week. We need wisdom, patience, and rest.”</li>
+  <li><strong>Guidance:</strong> “Please pray for discernment as I make a work decision by the end of the month.”</li>
+  <li><strong>Comfort:</strong> “Please pray for comfort and strength after a recent loss. This can stay private.”</li>
+</ul>
+
+<p>Notice what is not happening there. There is no long backstory, no dramatic language, and no pressure to explain every detail. The request stays readable.</p>
+
+<h2>Don’t Include</h2>
+
+<p>Good judgment matters. A prayer request is not the right place for everything.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Leave this out</th>
+      <th>Why to avoid it</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Overly personal details</td>
+      <td>If it would make you uncomfortable to read out loud, it probably should not be in the request.</td>
+    </tr>
+    <tr>
+      <td>Information you do not have permission to share</td>
+      <td>Consent matters, especially when the request involves another person.</td>
+    </tr>
+    <tr>
+      <td>Long background narratives</td>
+      <td>The main need should stay visible. A request that rambles can hide the actual prayer point.</td>
+    </tr>
+    <tr>
+      <td>Unnecessary medical, family, or financial details</td>
+      <td>More detail is not always better. Sometimes it is just more detail.</td>
+    </tr>
+    <tr>
+      <td>Anything you are not comfortable sharing publicly</td>
+      <td>If it feels too exposed, mark it private or keep it brief.</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>If a detail does not help someone pray, leave it out. That is usually the right filter. The church does not need a case file. It needs enough context to respond with care.</p>
+
+<h2>If You Are Requesting Healing, Guidance, or Comfort</h2>
+
+<p>These are the situations where people often over-explain or under-explain. The middle path is usually best.</p>
+
+<p>For healing, say what kind of prayer is needed without turning the note into a medical summary. For guidance, name the decision and the deadline if there is one. For comfort, say what kind of support would be most helpful: peace, strength, patience, reassurance, or rest.</p>
+
+<p>You can borrow one of these patterns:</p>
+
+<ul>
+  <li><strong>Healing:</strong> “Please pray for healing and wise care as I recover from treatment this week.”</li>
+  <li><strong>Guidance:</strong> “Please pray for clarity as our family considers next steps for school and work.”</li>
+  <li><strong>Comfort:</strong> “Please pray for comfort, stability, and help with the next few days.”</li>
+  <li><strong>Strength:</strong> “Please pray for strength to stay steady through a difficult season.”</li>
+</ul>
+
+<p>If you want to keep a request private but still specific, say that directly:</p>
+
+<blockquote>
+  <p>“Please pray for healing for a family member this week. We are not ready to share details publicly, so please keep this private.”</p>
+</blockquote>
+
+<p>That kind of wording does two jobs at once. It gives the church a prayer focus and sets a boundary without making the request awkward.</p>
+
+<p>For a broader biblical frame, <a href="https://www.biblegateway.com/passage/?search=James+5%3A16&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">James 5:16</a> connects prayer with honest confession and mutual care. The point is not performance. The point is trust and clarity.</p>
+
+<h2>If You Are Submitting for Someone Else</h2>
+
+<p>People often ask for prayer on behalf of a spouse, child, parent, friend, or coworker. That is normal. The key is to say two things clearly: your relationship to the person and whether you have permission to share the request.</p>
+
+<p>Useful wording looks like this:</p>
+
+<ul>
+  <li><strong>With consent:</strong> “Please pray for my father, who gave me permission to share that he has a procedure next week.”</li>
+  <li><strong>Without detail:</strong> “Please pray for a friend who is facing a hard family situation.”</li>
+  <li><strong>For a child:</strong> “Please pray for our son as he starts treatment. We are asking for peace and wisdom.”</li>
+</ul>
+
+<p>What matters here is not formality. It is trust. If you are speaking for someone else, do not overshare just because you can. Use the smallest amount of information that still tells the church how to pray.</p>
+
+<p>If consent is unclear, keep the request general and private. That is the safer default. You can always add detail later if permission is granted and the situation changes.</p>
+
+<h2>Sharing Preferences: Public Prayer vs. Private Request</h2>
+
+<p>Not every request belongs in the same channel. A church needs both public prayer and private care, but they are not the same thing. Choosing the right lane keeps the request useful.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Sharing choice</th>
+      <th>Best when</th>
+      <th>What to say</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Public prayer</td>
+      <td>The need is general and you are comfortable with broader church awareness.</td>
+      <td>“Please pray for our family this week as we travel.”</td>
+    </tr>
+    <tr>
+      <td>Private request</td>
+      <td>The matter is sensitive, personal, or not ready for wider sharing.</td>
+      <td>“Please keep this private and pray for wisdom as we work through a family matter.”</td>
+    </tr>
+    <tr>
+      <td>Limited sharing</td>
+      <td>You want prayer but do not want every detail repeated.</td>
+      <td>“You may share the general need, but please leave out the details.”</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>If you are unsure, choose the more private option. That is the conservative decision and usually the right one. It is easier to expand a request later than to retract details after they have already gone farther than you intended.</p>
+
+<p>If the request becomes something broader for the church to know about, you can also look to the <a href="/news.html">News</a> page for public updates. That page is for church communication, not a place to assume personal details will be posted. Public and personal are not the same category, even when the same people are involved.</p>
+
+<h2>How to Submit</h2>
+
+<p>Once your request is ready, use the church’s normal contact paths. The simplest route is usually the <a href="/contacts.html">Contacts</a> page. If you prefer a form-based route, use <a href="/contact.php">Contact Us</a>. Either way, keep the message short, specific, and consistent with the privacy level you chose.</p>
+
+<p>A helpful submission usually has three parts:</p>
+
+<ol>
+  <li><strong>The request itself:</strong> one or two clear sentences.</li>
+  <li><strong>Your privacy note:</strong> public, private, or limited sharing.</li>
+  <li><strong>A follow-up option:</strong> a phone number or email if you want someone to reach back out.</li>
+</ol>
+
+<p>What happens after that? In practical terms, the church receives the note, reads the request, and handles it according to the communication path and privacy preference you provided. If more information is needed, someone may follow up. If no follow-up is needed, the request can still be prayed over without extra drama. That is usually the best case. Prayer requests are not package tracking.</p>
+
+<p>Do not build your wording around a guaranteed response time or a guaranteed outcome. A church can promise care and diligence. It cannot promise the timing of every answer. Keep the focus on the request itself, and keep praying while the message moves through the normal process.</p>
+
+<p>If you need more than a brief prayer note, say so. A sentence like “We would appreciate a follow-up conversation if possible” gives the church a better signal than a wall of text. If the matter is urgent, say that plainly near the top of the message. Simple language wins here.</p>
+
+<h2>A Short Checklist Before You Send</h2>
+
+<ul>
+  <li>Is the request clear in one sentence?</li>
+  <li>Did you include the type of prayer needed?</li>
+  <li>Did you leave out anything private or unnecessary?</li>
+  <li>Did you note whether the request is public, private, or limited?</li>
+  <li>If it is for someone else, did you mention your relationship and consent?</li>
+  <li>If timing matters, did you include the relevant date or timeframe?</li>
+</ul>
+
+<p>If you can answer yes to those six questions, the request is probably ready. There is no prize for over-writing it.</p>
+
+<h2>If You Are Not Sure What to Say</h2>
+
+<p>Some people stall because they think they need perfect wording before they can ask for prayer. They do not. You only need enough clarity to make the need understandable. Start with the most basic version of the request, then add one detail that helps the church pray well. That is often enough.</p>
+
+<p>A simple three-step method works:</p>
+
+<ol>
+  <li><strong>Name the need.</strong> Say whether the prayer is for healing, guidance, comfort, travel, or another concern.</li>
+  <li><strong>Add the timing.</strong> If there is a date, deadline, or season that matters, include it.</li>
+  <li><strong>Set the privacy level.</strong> Tell the church whether the note is public, private, or limited.</li>
+</ol>
+
+<p>If you still feel stuck, write the message as if you were sending it to one mature Christian friend who will pray responsibly and not gossip. That mental model is useful. It trims away performance language and leaves only what matters. If the request gets more specific later, you can always send an update through the same church contact path.</p>
+
+<p>That is another reason the template matters. It lets you begin before you feel fully composed. Most people are not composed when they need prayer. That is usually the point.</p>
+
+<h2>Common Mistakes That Make Requests Harder to Use</h2>
+
+<p>Most weak prayer requests fail for ordinary reasons, not dramatic ones. The note is too vague, too long, too private in the wrong place, or too public for the situation. Clean that up before you send it and you save everyone time.</p>
+
+<ul>
+  <li><strong>Leaving out the actual request:</strong> “Please pray for my family” is not enough by itself. Add the reason.</li>
+  <li><strong>Writing a full explanation first:</strong> the prayer point should show up in the first sentence, not after three paragraphs.</li>
+  <li><strong>Using code words:</strong> if the church has to decode your message, it is not a clear request.</li>
+  <li><strong>Sharing too much detail:</strong> more information is not always more help. Sometimes it is just more exposure.</li>
+  <li><strong>Forgetting the privacy note:</strong> public, private, or limited sharing should never be a guessing game.</li>
+</ul>
+
+<p>A practical test helps here: read the request out loud once. If it sounds muddled, you probably wrote too much or too little. Trim it until the sentence does the job.</p>
+
+<h2>Three Finished Examples</h2>
+
+<p>If you would rather copy a complete version than build one piece by piece, use one of these as a model:</p>
+
+<blockquote>
+  <p><strong>Example 1:</strong> “Please pray for my mother as she prepares for surgery on Monday. We are asking for peace, skill for the doctors, and a smooth recovery. Please keep this private.”</p>
+</blockquote>
+
+<blockquote>
+  <p><strong>Example 2:</strong> “Please pray for our family this month as we handle a move, a new school schedule, and a lot of change. We would appreciate wisdom and steadiness. The general request may be shared, but please leave out details.”</p>
+</blockquote>
+
+<blockquote>
+  <p><strong>Example 3:</strong> “Please pray for a friend who is grieving. I have permission to ask for prayer, but not to share more details publicly. Please pray for comfort and rest.”</p>
+</blockquote>
+
+<p>These examples are short for a reason. They say what is needed, when it matters, and how public the request may be. That is the job.</p>
+
+<p>If you need help thinking through what kind of support fits the situation, the <a href="/resources">Resources</a> page is a sensible next stop. It will not solve every problem, which is a rare and refreshing limitation for a church website.</p>
+
+<h2>Closing Encouragement</h2>
+
+<p>A good prayer request is not fancy. It is faithful, clear, and respectful. If you keep the message focused on the need, the timing, and the privacy level, you make it easier for the church to do what churches are supposed to do: pray, care, and respond with wisdom.</p>
+
+<p>Start with the <a href="/contacts.html">Contacts</a> page or <a href="/contact.php">Contact Us</a> form, keep your wording simple, and let the church know whether the request should stay private. If you want to think through other next steps while you wait, the <a href="/resources">Resources</a> page can point you to additional support, and <a href="/news.html">News</a> can help you stay aware of broader church updates.</p>
+
+<p>Finally, keep praying after you submit. That part still matters. The church can handle the message, but you should still bring the burden to God directly. <a href="https://www.biblegateway.com/passage/?search=1+Thessalonians+5%3A17&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">1 Thessalonians 5:17</a> keeps the instruction short for a reason.</p>

 succeeded in 466ms:
100 52240    0 52240    0     0   102k      0 --:--:-- --:--:-- --:--:--  102k
414:			<header class="entry-header">	<h2 class="entry-title" itemprop="headline"><a href="https://ridgecrestchurch.com/how-to-prepare-prayer-request-template/" rel="bookmark">How to Prepare a Prayer Request for Ridgecrest (A Simple, Respectful Template)</a></h2>
420:<a href="https://ridgecrestchurch.com/how-to-prepare-prayer-request-template/" title="How to Prepare a Prayer Request for Ridgecrest (A Simple, Respectful Template)"><img data-src="https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg" class="wp-post-image lazyload" alt="Planning materials on a desk with a calendar and smartphone for Sunday service coordination" decoding="async" itemprop="image" src="data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==" style="--smush-placeholder-width: 1024px; --smush-placeholder-aspect-ratio: 1024/683;" /></a><p>Learn how to write a meaningful prayer request for Ridgecrest Baptist Church with this practical template and guidance.</p>

 succeeded in 551ms:
100 13672    0 13672    0     0  23509      0 --:--:-- --:--:-- --:--:-- 23491100 55776    0 55776    0     0  95587      0 --:--:-- --:--:-- --:--:-- 95506
22:	<meta property="og:image" content="https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg" />
32:	<script type="application/ld+json" class="yoast-schema-graph">{"@context":"https://schema.org","@graph":[{"@type":"Article","@id":"https://ridgecrestchurch.com/how-to-prepare-prayer-request-template/#article","isPartOf":{"@id":"https://ridgecrestchurch.com/how-to-prepare-prayer-request-template/"},"author":{"name":"Marcus Reed","@id":"https://ridgecrestchurch.com/#/schema/person/2698d86a6f04ff1d1a31b78a07d47018"},"headline":"How to Prepare a Prayer Request for Ridgecrest (A Simple, Respectful Template)","datePublished":"2026-06-23T18:32:35+00:00","dateModified":"2026-06-23T18:32:54+00:00","mainEntityOfPage":{"@id":"https://ridgecrestchurch.com/how-to-prepare-prayer-request-template/"},"wordCount":2592,"publisher":{"@id":"https://ridgecrestchurch.com/#organization"},"image":{"@id":"https://ridgecrestchurch.com/how-to-prepare-prayer-request-template/#primaryimage"},"thumbnailUrl":"https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg","inLanguage":"en-US"},{"@type":"WebPage","@id":"https://ridgecrestchurch.com/how-to-prepare-prayer-request-template/","url":"https://ridgecrestchurch.com/how-to-prepare-prayer-request-template/","name":"How to Prepare a Prayer Request for Ridgecrest (A Simple, Respectful Template) - Ridgecrest Baptist Church","isPartOf":{"@id":"https://ridgecrestchurch.com/#website"},"primaryImageOfPage":{"@id":"https://ridgecrestchurch.com/how-to-prepare-prayer-request-template/#primaryimage"},"image":{"@id":"https://ridgecrestchurch.com/how-to-prepare-prayer-request-template/#primaryimage"},"thumbnailUrl":"https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg","datePublished":"2026-06-23T18:32:35+00:00","dateModified":"2026-06-23T18:32:54+00:00","breadcrumb":{"@id":"https://ridgecrestchurch.com/how-to-prepare-prayer-request-template/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https://ridgecrestchurch.com/how-to-prepare-prayer-request-template/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https://ridgecrestchurch.com/how-to-prepare-prayer-request-template/#primaryimage","url":"https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg","contentUrl":"https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg","caption":"Planning materials on a desk with a calendar and smartphone for Sunday service coordination"},{"@type":"BreadcrumbList","@id":"https://ridgecrestchurch.com/how-to-prepare-prayer-request-template/#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 Prepare a Prayer Request for Ridgecrest (A Simple, Respectful Template)"}]},{"@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/2698d86a6f04ff1d1a31b78a07d47018","name":"Marcus Reed","url":"https://ridgecrestchurch.com/author/marcus-reed/"}]}</script>
434:  <img decoding="async" data-src="https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg" alt="Planning materials on a desk with a calendar and smartphone for Sunday service coordination" class="wp-image-76 lazyload" style="--smush-placeholder-width: 1024px; --smush-placeholder-aspect-ratio: 1024/683;width:100%;height:auto;" src="data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==" /><figcaption>A simple request starts with the same discipline as any good plan: enough detail to be useful, not so much that the point gets buried.</figcaption></figure>
608:<h2>If You Are Not Sure What to Say</h2>
618:<h2>Common Mistakes That Make Requests Harder to Use</h2>

codex
Published the prayer-request article as a new WordPress post, assigned it to Marcus Reed, set the featured image, and verified that the post URL and blog index both resolve publicly. The article uses the existing planning-desk photo as the visible inline image and includes the requested template, do/don’t guidance, submission steps, and privacy framing.

Remaining risk: the available in-library image is a close thematic fit rather than the exact prayer-journal/Bible composition in the brief, but it renders correctly and satisfies the visible image requirement.

WP_POST_ID: 116
WP_POST_STATUS: publish
WP_POST_URL: https://ridgecrestchurch.com/how-to-prepare-prayer-request-template/
WP_AUTHOR_USER: marcus-reed (Marcus Reed)
FEATURED_IMAGE_ID: 76
INLINE_IMAGE_IDS: 76
BLOG_INDEX_STATUS: ready; url=https://ridgecrestchurch.com/blog/; page_for_posts=23
LINK_TARGETS_USED: none
LEGACY_PATH_STATUS: not_applicable
VERIFICATION: wp post get/url confirmed; curl 200 on article and /blog/; inline image and featured image confirmed
diff --git a//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html
new file mode 100644
index 0000000000000000000000000000000000000000..f7fefbfb9d84c8f4b50ac2545de2e25c0e2b1e55
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-506/article.html
@@ -0,0 +1,297 @@
+<p><strong><em>A prayer request does not need to sound polished. It needs to be clear enough for the church to pray without guessing.</em></strong></p>
+
+<p><strong>By Marcus Reed</strong> | Updated June 23, 2026</p>
+
+<p>When people sit down to write a prayer request, the same practical questions come up fast: How much context is enough? What should stay private? Can I ask for prayer for someone else? And how do I make the request easy for the church to read and use well?</p>
+
+<p>Those are good questions. Prayer is not a performance, and the Bible treats it that way. <a href="https://www.biblegateway.com/passage/?search=Philippians+4%3A6-7&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">Philippians 4:6-7</a> points toward honest, direct prayer; <a href="https://www.biblegateway.com/passage/?search=Matthew+6%3A6&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">Matthew 6:6</a> reminds believers that prayer can also be private and disciplined. A useful church request follows the same logic: enough context to be specific, enough restraint to protect what should stay private, and enough clarity that people can pray with purpose.</p>
+
+<p>If you want the shortest path, start with the church <a href="/contacts.html">Contacts</a> page, or use the site's <a href="/contact.php">contact form</a> if that is more convenient. If you are looking for broader church information while you prepare your message, the <a href="/resources">Resources</a> page is a good place to get oriented.</p>
+
+<figure class="wp-block-image size-large">
+  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg" alt="Planning materials on a desk with a calendar and smartphone for Sunday service coordination" class="wp-image-76" style="width:100%;height:auto;" />
+  <figcaption>A simple request starts with the same discipline as any good plan: enough detail to be useful, not so much that the point gets buried.</figcaption>
+</figure>
+
+<h2>Why We Ask for a Little Context</h2>
+
+<p>Prayer teams do better with signal than with noise. A short note that says what is happening, who it affects, and what kind of prayer is needed gives the church something concrete to carry. A vague request forces people to fill in the blanks, and that is where confusion starts.</p>
+
+<p>Context also helps the church handle requests appropriately. Some needs are fine to share broadly. Some should stay with a limited group. Some should be treated as private pastoral matters. The more clearly you state your preference, the less guesswork is required on the other side.</p>
+
+<p>There is a third reason, and it is the one people often skip: context respects the person who is asking for prayer. A request that is too thin can feel detached; a request that is too detailed can feel exposed. The goal is not to narrate your whole life. The goal is to give enough information for faithful prayer and responsible care.</p>
+
+<h2>A Quick Template You Can Copy and Paste</h2>
+
+<p>If you are not sure where to start, use this format. It is simple on purpose.</p>
+
+<pre><code>Name: [Your name]
+Request: [One short sentence about the need]
+Details: [Only the facts that help people pray well]
+Timeframe: [Today, this week, on [date], or ongoing]
+Ongoing vs. one-time: [One-time / recurring]
+Sharing preference: [Public / private / limited sharing]
+Contact: [Optional phone or email if a follow-up may help]</code></pre>
+
+<p>That is enough for most situations. If you need more privacy, leave out the contact line and keep the description general. If the request is for someone else, say so clearly in the first line so the church understands the relationship and the permission level.</p>
+
+<p>A few quick definitions help here:</p>
+
+<ul>
+  <li><strong>Public prayer:</strong> a request that can be shared more broadly with the church.</li>
+  <li><strong>Private request:</strong> a request that should stay with a smaller, limited group.</li>
+  <li><strong>Ongoing request:</strong> a situation that needs repeated prayer over time.</li>
+  <li><strong>Timeframe:</strong> when the need is happening or when support is most important.</li>
+</ul>
+
+<p>Think of the template as a floor, not a ceiling. You can always add a sentence, but you do not need to write a paragraph for every line. A church can work with a concise request. It cannot work with a mystery wrapped in spiritual language.</p>
+
+<h2>Do Include</h2>
+
+<p>The most useful prayer requests include the facts that actually help someone pray.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Include this</th>
+      <th>Why it helps</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>A clear request in one sentence</td>
+      <td>It tells the reader exactly what kind of prayer you are asking for.</td>
+    </tr>
+    <tr>
+      <td>Specific needs or concerns</td>
+      <td>“Healing,” “wisdom,” “travel safety,” or “comfort” are easier to pray for than a vague concern.</td>
+    </tr>
+    <tr>
+      <td>Relevant dates or timeframes</td>
+      <td>Dates help the church know what matters now, this week, or later.</td>
+    </tr>
+    <tr>
+      <td>Whether the request is confidential</td>
+      <td>Privacy preferences should be stated plainly, not left to interpretation.</td>
+    </tr>
+    <tr>
+      <td>Whether the request is ongoing</td>
+      <td>A continuing need may be placed on a prayer list differently from a one-time update.</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>One useful habit: write the request as if someone else has to read it once, understand it immediately, and pray right away. That is the operational standard. Church communication is not a scavenger hunt.</p>
+
+<p>Here are a few examples of good, concise wording:</p>
+
+<ul>
+  <li><strong>Healing:</strong> “Please pray for Sarah as she prepares for surgery on Thursday. We are asking for peace, skill for the medical team, and steady recovery.”</li>
+  <li><strong>Family support:</strong> “Please pray for our family during a difficult week. We need wisdom, patience, and rest.”</li>
+  <li><strong>Guidance:</strong> “Please pray for discernment as I make a work decision by the end of the month.”</li>
+  <li><strong>Comfort:</strong> “Please pray for comfort and strength after a recent loss. This can stay private.”</li>
+</ul>
+
+<p>Notice what is not happening there. There is no long backstory, no dramatic language, and no pressure to explain every detail. The request stays readable.</p>
+
+<h2>Don’t Include</h2>
+
+<p>Good judgment matters. A prayer request is not the right place for everything.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Leave this out</th>
+      <th>Why to avoid it</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Overly personal details</td>
+      <td>If it would make you uncomfortable to read out loud, it probably should not be in the request.</td>
+    </tr>
+    <tr>
+      <td>Information you do not have permission to share</td>
+      <td>Consent matters, especially when the request involves another person.</td>
+    </tr>
+    <tr>
+      <td>Long background narratives</td>
+      <td>The main need should stay visible. A request that rambles can hide the actual prayer point.</td>
+    </tr>
+    <tr>
+      <td>Unnecessary medical, family, or financial details</td>
+      <td>More detail is not always better. Sometimes it is just more detail.</td>
+    </tr>
+    <tr>
+      <td>Anything you are not comfortable sharing publicly</td>
+      <td>If it feels too exposed, mark it private or keep it brief.</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>If a detail does not help someone pray, leave it out. That is usually the right filter. The church does not need a case file. It needs enough context to respond with care.</p>
+
+<h2>If You Are Requesting Healing, Guidance, or Comfort</h2>
+
+<p>These are the situations where people often over-explain or under-explain. The middle path is usually best.</p>
+
+<p>For healing, say what kind of prayer is needed without turning the note into a medical summary. For guidance, name the decision and the deadline if there is one. For comfort, say what kind of support would be most helpful: peace, strength, patience, reassurance, or rest.</p>
+
+<p>You can borrow one of these patterns:</p>
+
+<ul>
+  <li><strong>Healing:</strong> “Please pray for healing and wise care as I recover from treatment this week.”</li>
+  <li><strong>Guidance:</strong> “Please pray for clarity as our family considers next steps for school and work.”</li>
+  <li><strong>Comfort:</strong> “Please pray for comfort, stability, and help with the next few days.”</li>
+  <li><strong>Strength:</strong> “Please pray for strength to stay steady through a difficult season.”</li>
+</ul>
+
+<p>If you want to keep a request private but still specific, say that directly:</p>
+
+<blockquote>
+  <p>“Please pray for healing for a family member this week. We are not ready to share details publicly, so please keep this private.”</p>
+</blockquote>
+
+<p>That kind of wording does two jobs at once. It gives the church a prayer focus and sets a boundary without making the request awkward.</p>
+
+<p>For a broader biblical frame, <a href="https://www.biblegateway.com/passage/?search=James+5%3A16&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">James 5:16</a> connects prayer with honest confession and mutual care. The point is not performance. The point is trust and clarity.</p>
+
+<h2>If You Are Submitting for Someone Else</h2>
+
+<p>People often ask for prayer on behalf of a spouse, child, parent, friend, or coworker. That is normal. The key is to say two things clearly: your relationship to the person and whether you have permission to share the request.</p>
+
+<p>Useful wording looks like this:</p>
+
+<ul>
+  <li><strong>With consent:</strong> “Please pray for my father, who gave me permission to share that he has a procedure next week.”</li>
+  <li><strong>Without detail:</strong> “Please pray for a friend who is facing a hard family situation.”</li>
+  <li><strong>For a child:</strong> “Please pray for our son as he starts treatment. We are asking for peace and wisdom.”</li>
+</ul>
+
+<p>What matters here is not formality. It is trust. If you are speaking for someone else, do not overshare just because you can. Use the smallest amount of information that still tells the church how to pray.</p>
+
+<p>If consent is unclear, keep the request general and private. That is the safer default. You can always add detail later if permission is granted and the situation changes.</p>
+
+<h2>Sharing Preferences: Public Prayer vs. Private Request</h2>
+
+<p>Not every request belongs in the same channel. A church needs both public prayer and private care, but they are not the same thing. Choosing the right lane keeps the request useful.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>Sharing choice</th>
+      <th>Best when</th>
+      <th>What to say</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Public prayer</td>
+      <td>The need is general and you are comfortable with broader church awareness.</td>
+      <td>“Please pray for our family this week as we travel.”</td>
+    </tr>
+    <tr>
+      <td>Private request</td>
+      <td>The matter is sensitive, personal, or not ready for wider sharing.</td>
+      <td>“Please keep this private and pray for wisdom as we work through a family matter.”</td>
+    </tr>
+    <tr>
+      <td>Limited sharing</td>
+      <td>You want prayer but do not want every detail repeated.</td>
+      <td>“You may share the general need, but please leave out the details.”</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>If you are unsure, choose the more private option. That is the conservative decision and usually the right one. It is easier to expand a request later than to retract details after they have already gone farther than you intended.</p>
+
+<p>If the request becomes something broader for the church to know about, you can also look to the <a href="/news.html">News</a> page for public updates. That page is for church communication, not a place to assume personal details will be posted. Public and personal are not the same category, even when the same people are involved.</p>
+
+<h2>How to Submit</h2>
+
+<p>Once your request is ready, use the church’s normal contact paths. The simplest route is usually the <a href="/contacts.html">Contacts</a> page. If you prefer a form-based route, use <a href="/contact.php">Contact Us</a>. Either way, keep the message short, specific, and consistent with the privacy level you chose.</p>
+
+<p>A helpful submission usually has three parts:</p>
+
+<ol>
+  <li><strong>The request itself:</strong> one or two clear sentences.</li>
+  <li><strong>Your privacy note:</strong> public, private, or limited sharing.</li>
+  <li><strong>A follow-up option:</strong> a phone number or email if you want someone to reach back out.</li>
+</ol>
+
+<p>What happens after that? In practical terms, the church receives the note, reads the request, and handles it according to the communication path and privacy preference you provided. If more information is needed, someone may follow up. If no follow-up is needed, the request can still be prayed over without extra drama. That is usually the best case. Prayer requests are not package tracking.</p>
+
+<p>Do not build your wording around a guaranteed response time or a guaranteed outcome. A church can promise care and diligence. It cannot promise the timing of every answer. Keep the focus on the request itself, and keep praying while the message moves through the normal process.</p>
+
+<p>If you need more than a brief prayer note, say so. A sentence like “We would appreciate a follow-up conversation if possible” gives the church a better signal than a wall of text. If the matter is urgent, say that plainly near the top of the message. Simple language wins here.</p>
+
+<h2>A Short Checklist Before You Send</h2>
+
+<ul>
+  <li>Is the request clear in one sentence?</li>
+  <li>Did you include the type of prayer needed?</li>
+  <li>Did you leave out anything private or unnecessary?</li>
+  <li>Did you note whether the request is public, private, or limited?</li>
+  <li>If it is for someone else, did you mention your relationship and consent?</li>
+  <li>If timing matters, did you include the relevant date or timeframe?</li>
+</ul>
+
+<p>If you can answer yes to those six questions, the request is probably ready. There is no prize for over-writing it.</p>
+
+<h2>If You Are Not Sure What to Say</h2>
+
+<p>Some people stall because they think they need perfect wording before they can ask for prayer. They do not. You only need enough clarity to make the need understandable. Start with the most basic version of the request, then add one detail that helps the church pray well. That is often enough.</p>
+
+<p>A simple three-step method works:</p>
+
+<ol>
+  <li><strong>Name the need.</strong> Say whether the prayer is for healing, guidance, comfort, travel, or another concern.</li>
+  <li><strong>Add the timing.</strong> If there is a date, deadline, or season that matters, include it.</li>
+  <li><strong>Set the privacy level.</strong> Tell the church whether the note is public, private, or limited.</li>
+</ol>
+
+<p>If you still feel stuck, write the message as if you were sending it to one mature Christian friend who will pray responsibly and not gossip. That mental model is useful. It trims away performance language and leaves only what matters. If the request gets more specific later, you can always send an update through the same church contact path.</p>
+
+<p>That is another reason the template matters. It lets you begin before you feel fully composed. Most people are not composed when they need prayer. That is usually the point.</p>
+
+<h2>Common Mistakes That Make Requests Harder to Use</h2>
+
+<p>Most weak prayer requests fail for ordinary reasons, not dramatic ones. The note is too vague, too long, too private in the wrong place, or too public for the situation. Clean that up before you send it and you save everyone time.</p>
+
+<ul>
+  <li><strong>Leaving out the actual request:</strong> “Please pray for my family” is not enough by itself. Add the reason.</li>
+  <li><strong>Writing a full explanation first:</strong> the prayer point should show up in the first sentence, not after three paragraphs.</li>
+  <li><strong>Using code words:</strong> if the church has to decode your message, it is not a clear request.</li>
+  <li><strong>Sharing too much detail:</strong> more information is not always more help. Sometimes it is just more exposure.</li>
+  <li><strong>Forgetting the privacy note:</strong> public, private, or limited sharing should never be a guessing game.</li>
+</ul>
+
+<p>A practical test helps here: read the request out loud once. If it sounds muddled, you probably wrote too much or too little. Trim it until the sentence does the job.</p>
+
+<h2>Three Finished Examples</h2>
+
+<p>If you would rather copy a complete version than build one piece by piece, use one of these as a model:</p>
+
+<blockquote>
+  <p><strong>Example 1:</strong> “Please pray for my mother as she prepares for surgery on Monday. We are asking for peace, skill for the doctors, and a smooth recovery. Please keep this private.”</p>
+</blockquote>
+
+<blockquote>
+  <p><strong>Example 2:</strong> “Please pray for our family this month as we handle a move, a new school schedule, and a lot of change. We would appreciate wisdom and steadiness. The general request may be shared, but please leave out details.”</p>
+</blockquote>
+
+<blockquote>
+  <p><strong>Example 3:</strong> “Please pray for a friend who is grieving. I have permission to ask for prayer, but not to share more details publicly. Please pray for comfort and rest.”</p>
+</blockquote>
+
+<p>These examples are short for a reason. They say what is needed, when it matters, and how public the request may be. That is the job.</p>
+
+<p>If you need help thinking through what kind of support fits the situation, the <a href="/resources">Resources</a> page is a sensible next stop. It will not solve every problem, which is a rare and refreshing limitation for a church website.</p>
+
+<h2>Closing Encouragement</h2>
+
+<p>A good prayer request is not fancy. It is faithful, clear, and respectful. If you keep the message focused on the need, the timing, and the privacy level, you make it easier for the church to do what churches are supposed to do: pray, care, and respond with wisdom.</p>
+
+<p>Start with the <a href="/contacts.html">Contacts</a> page or <a href="/contact.php">Contact Us</a> form, keep your wording simple, and let the church know whether the request should stay private. If you want to think through other next steps while you wait, the <a href="/resources">Resources</a> page can point you to additional support, and <a href="/news.html">News</a> can help you stay aware of broader church updates.</p>
+
+<p>Finally, keep praying after you submit. That part still matters. The church can handle the message, but you should still bring the burden to God directly. <a href="https://www.biblegateway.com/passage/?search=1+Thessalonians+5%3A17&amp;version=NIV&amp;utm_source=ridgecrestchurch.com" target="_blank" rel="noopener">1 Thessalonians 5:17</a> keeps the instruction short for a reason.</p>

tokens used
136,782
