OpenAI Codex v0.123.0 (research preview)
--------
workdir: /home/ubuntu/apps/ridgecrestchurch.com
model: gpt-5.4
provider: openai
approval: never
sandbox: danger-full-access
reasoning effort: none
reasoning summaries: none
session id: 019ee66e-aa46-7900-a161-0ff3a9fc31a8
--------
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-457/task.md
Iteration: 1

<primary_instructions>
# Article Generation Task

You are creating a WordPress blog post for ridgecrestchurch.com.

## Required Runtime

- First read `SITE_CONTEXT.md` and `AGENTS.md` in this WordPress root.
- Then read `ARTICLE_CONTENT_PLAN.md` in this WordPress root.
- Then read `wp-content/plugins/flatlogic-post-creator/INSTRUCTIONS.MD`.
- Then read every markdown file in `wp-content/plugins/flatlogic-post-creator/context/`.
- Follow those post-creator instructions where they fit this site's topic, but do not force Flatlogic-specific SaaS claims onto an unrelated restored site.

## Site Contract

- Domain: ridgecrestchurch.com
- Public URL: https://ridgecrestchurch.com
- Site topic: Church website (Ridgecrest Baptist Church)
- Language: English
- Required pages: Home, About Us, Ministries, Kids, Youth, Events Calendar, News, Contacts, Church Map, Resources
- Extra requirements: Maintain a clear, non-commercial informational structure (sermons/events/news) and include standard navigation and contact details.

## Backlink Targets To Respect

- / (page, pending, 50 referring domains, 175 backlinks)

## 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: Ministry Spotlight: How Our Teams Serve on Sundays (Greeters, Ushers, and Hospitality)
- 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 111 as the source of truth. Prepared article brief: Working title: Ministry Spotlight: How Our Teams Serve on Sundays (Greeters, Ushers, and Hospitality)
Slug hint: ministry-spotlight-sunday-teams
Meta description: Discover how the Sunday service teams at Ridgecrest Baptist Church enhance worship experiences for attendees. Learn about the roles of greeters, ushers, and hospitality volunteers,

Reader intent:
Help first-time and returning attendees understand what different Sunday teams do and how to participate or request help during the service.

Thesis:
The Sunday service teams at Ridgecrest Baptist Church play a crucial role in creating a welcoming and supportive environment for worshippers, and this article will highlight their contributions and how others can get involved.

Writer brief:
Provide a behind-the-scenes look at how the Sunday service teams operate, focusing on their roles and the importance of their contributions to the church community. Use a friendly, approachable tone to invite readers to engage with these teams.

Author voice notes:
Maintain a curious and approachable tone. Use plain language and relatable examples to engage the reader. Incorporate light humor where appropriate to make the content more inviting. Ensure the writing is informative without being overly technical or formal.

Key takeaways:
- Understanding the roles of greeters, ushers, and hospitality teams enhances the worship experience.
- Volunteering with Sunday service teams is a great way to get involved in the church community.
- Practical tips for asking for help during the service can ease first-time visitor anxiety.
- A welcoming environment is crucial for both newcomers and regular attendees.

Outline:
1. Quick welcome: why Sunday teams matter for a smooth, welcoming service
   Purpose: Introduce the importance of Sunday service teams in creating a positive experience.
  - Overview of the role of Sunday teams.
  - How they contribute to a welcoming atmosphere.
2. Greeters: what to expect at the door and how to get connected fast
   Purpose: Explain the role of greeters and their importance.
  - First impressions matter: the greeter's role.
  - How greeters help newcomers feel welcome.
3. Ushers: seating help, accessibility considerations, and where to find what you need
   Purpose: Detail the responsibilities of ushers during services.
  - Seating arrangements and accessibility support.
  - Where to find information and assistance.
4. Hospitality & communication: how we handle announcements, information, and visitor follow-up
   Purpose: Describe the hospitality team's role in communication.
  - How announcements are made.
  - Visitor follow-up processes.
5. Kids and family support touchpoints (high-level, non-duplicative of Kids page)
   Purpose: Highlight how Sunday teams support families without duplicating existing content.
  - Family-friendly initiatives during services.
  - Support for parents and children.
6. How to ask for help during the service (practical examples)
   Purpose: Provide practical advice for attendees seeking assistance.
  - Encouragement to ask for help.
  - Examples of common requests.
7. How to volunteer: what skills we look for, typical time commitment, and next steps
   Purpose: Encourage readers to consider volunteering.
  - Skills and qualities sought in volunteers.
  - Typical time commitment and how to get involved.
8. Closing: a short invitation to visit and meet the team
   Purpose: Wrap up the article with an invitation to engage.
  - Encouragement to visit Ridgecrest.
  - Invitation to meet the Sunday teams.
9. Optional sidebar: “Questions to ask before you serve” (one-minute checklist)
   Purpose: Provide additional value with a quick checklist for potential volunteers.
  - Key questions to consider before volunteering.
  - Encouragement to reflect on personal readiness.

Internal link plan:
- /: Link to the homepage for easy navigation.
- /about/: Provide context about the church and its mission.
- /ministries/: Highlight other ministries that may interest readers.
- /events-calendar/: Encourage participation in upcoming events.
- /contacts/: Provide contact information for further inquiries.
- /resources/: Direct readers to additional resources available.

Image direction:
A real church photo of a small group of volunteers welcoming attendees at the church entrance, or a candid photo of ushers/hospitality team setting up welcome materials.

Must include:
- Descriptions of each team's roles and responsibilities.
- Practical tips for attendees seeking assistance during the service.
- Information on how to volunteer with the Sunday teams.

Avoid:
- Duplicating the 'First-Timer’s Guide' or 'What to Expect at Ridgecrest' posts.
- Posting an exact RSVP/reminders/how-to-use-events-calendar guide.
- Any promotional or commercial language; keep it informational and church-focused.
- Fake stories or unverifiable claims about outcomes.

Quality checklist:
- Ensure clarity and accessibility in language and structure.
- Maintain a friendly and inviting tone throughout the article.
- Verify that all information is accurate and relevant to the church's current practices.
- Avoid jargon or overly complex language that may alienate readers. Article kind: evergreen Research status: not_required Reader intent: Help first-time and returning attendees understand what different Sunday teams do and how to participate or request help during the service. Planned outline: Quick welcome: why Sunday teams matter for a smooth, welcoming service | Greeters: what to expect at the door and how to get connected fast | Ushers: seating help, accessibility considerations, and where to find what you need | Hospitality & communication: how we handle announcements, information, and visitor follow-up | Kids and family support touchpoints (high-level, non-duplicative of Kids page) | How to ask for help during the service (practical examples) | How to volunteer: what skills we look for, typical time commitment, and next steps | Closing: a short invitation to visit and meet the team | Optional sidebar: “Questions to ask before you serve” (one-minute checklist) Image direction: A real church photo of a small group of volunteers welcoming attendees at the church entrance (or a candid photo of ushers/hospitality team setting up welcome materials). Preferred internal links: /, /about/, /ministries/, /events-calendar/, /contacts/, /resources/ Avoid: Duplicating the “First-Timer’s Guide” or “What to Expect at Ridgecrest” posts, Posting an exact RSVP/reminders/how-to-use-events-calendar guide, Any promotional or commercial language; keep it informational and church-focused, Fake stories or unverifiable claims about outcomes

## Selected Article Content Plan Item

- Plan item ID: 111
- Plan order: 21
- Article kind: evergreen
- Planned title: Ministry Spotlight: How Our Teams Serve on Sundays (Greeters, Ushers, and Hospitality)
- Slug hint: ministry-spotlight-sunday-teams
- Reader intent: Help first-time and returning attendees understand what different Sunday teams do and how to participate or request help during the service.
- Angle: A behind-the-scenes, people-first explanation of how Sunday service teams support worship and visitors at Ridgecrest—what they do, how they help, and how someone can volunteer.
- Image direction: A real church photo of a small group of volunteers welcoming attendees at the church entrance (or a candid photo of ushers/hospitality team setting up welcome materials).
- Author hint: Use the selected virtual author.

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

Outline:
- Quick welcome: why Sunday teams matter for a smooth, welcoming service
- Greeters: what to expect at the door and how to get connected fast
- Ushers: seating help, accessibility considerations, and where to find what you need
- Hospitality & communication: how we handle announcements, information, and visitor follow-up
- Kids and family support touchpoints (high-level, non-duplicative of Kids page)
- How to ask for help during the service (practical examples)
- How to volunteer: what skills we look for, typical time commitment, and next steps
- Closing: a short invitation to visit and meet the team
- Optional sidebar: “Questions to ask before you serve” (one-minute checklist)

Preferred internal link targets:
- /
- /about/
- /ministries/
- /events-calendar/
- /contacts/
- /resources/

Avoid:
- Duplicating the “First-Timer’s Guide” or “What to Expect at Ridgecrest” posts
- Posting an exact RSVP/reminders/how-to-use-events-calendar guide
- Any promotional or commercial language; keep it informational and church-focused
- Fake stories or unverifiable claims about outcomes

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: Nora Finch
Slug: nora-finch
Role: Curious explainer and resource writer
Language: English
Public bio: Nora turns unfamiliar topics into approachable guides, definitions, and resource articles for readers who want the plain version first.
Character formula: Curious Explorer Everyman
Formula: Explorer + Everyman
Meaning: A curious, relatable explainer who approaches unfamiliar topics like a smart ordinary reader asking useful questions.
Worldview: Most topics become less intimidating when someone maps the basics without pretending readers are experts.
Voice guidance: Curious, approachable, example-driven, plain-language. Define terms, compare options, and keep the reader included.
Humor: Light, relatable, observational humor.
Shadow tension: Can become too introductory; add enough specificity to avoid generic explanations.
Usage notes: Best for definitions, beginner guides, resource posts, and consumer-friendly explainers.
Archetype blend: Explorer + Everyman
Standard archetype voice guidance:

Primary archetype card: Explorer
Meaning: The restless seeker of freedom, movement, discovery, and new worlds.
First-person lens: There is more than this, always more, and safety becomes a cage when it kills the horizon.
Traits: independent, curious, restless, adaptable, freedom-driven
Worldview: The world is vast, and most people live inside small rooms built from habit.
Self-relation: I understand myself through movement and fear a successful life that feels dead.
Language patterns: Let us go; I want to see it myself; What is past the border; I do not belong here
Humor: Adventurous, casual, ironic risk humor.
Shadow risk to avoid unless intentionally requested: Abandoning commitments and calling it freedom.

Secondary archetype card: Everyman
Meaning: The ordinary human who wants belonging, dignity, survival, and a place in the world.
First-person lens: I am not special, and that is the problem and maybe the gift; I know what it is to be left out.
Traits: relatable, grounded, sincere, practical, socially aware
Worldview: The world feels large and unfair, full of people who seem more important.
Self-relation: I want to be chosen but distrust special treatment.
Language patterns: I just want to get through this; People like us; That is not fair; Why me
Humor: Awkward, relatable, observational.
Shadow risk to avoid unless intentionally requested: Passivity, resentment, fear of standing out.
Shadow tension: Loves discovery but must avoid wandering away from the reader's actual task.
Worldview: Every topic has a doorway; the writer's job is to find the one normal people can walk through.
Reader relationship: Curious peer walking through the topic with the reader.
Humor style: Warm observational humor, usually one small aside rather than a performance.
Voice traits: curious, accessible, friendly, example-driven
Vocabulary / recurring language: plain version, quick map, where this shows up, the short answer
Avoid voice: lecturing, inside-baseball jargon, over-explaining simple points, forced whimsy
CTA style: Offer the reader a simple next question to answer or a related guide to open next.
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: Curious, observant, friendly, and comfortable asking the obvious question readers may be afraid to ask.
Writing style: Uses simple framing, examples, analogies, question-led headings, and gentle transitions from basic to intermediate ideas.
Expertise topics: definitions, beginner guides, home improvement explainers, consumer research, web basics
Avoid topics: technical guarantees, health treatment advice, investment recommendations
Tone tags: curious, approachable, plain-language, light
Private operator notes: Useful for neutral legacy resources and intro-level explainers.

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`: `nora-finch`.
- Suggested `display_name`: `Nora Finch`.
- 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>

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

<review_summary>
The article appears to meet most publishing and WordPress requirements from the provided summary, but one material fix is still needed: the article image does not clearly match the requested Sunday-team spotlight topic.
</review_summary>

<review_findings>
- The implementation summary says attachment `10` is a real Ridgecrest worship photo, but also notes it is not a dedicated greeter/usher/hospitality photo. The selected plan item's image direction called for volunteers welcoming attendees or ushers/hospitality setting up materials, and the article instructions required a credible relevant image visible in the body. A generic worship photo is too weak a topical match for this specific article.
</review_findings>

<fix_instructions>
Update the post's featured and inline article image to a clearly relevant, rights-safe photo that shows Sunday welcome-team activity, such as greeters at the entrance, ushers assisting attendees, or hospitality volunteers preparing welcome materials. Keep the image in the WordPress media library, use descriptive alt text, leave the rest of the article intact unless needed for caption/context alignment, and re-verify that `post_content` contains a visible inline image after the swap.
</fix_instructions>

codex
I’m reading the site and post-creator instructions first, then I’ll inspect the existing post and swap in a more topically accurate Sunday-team image without changing the article body unless the image context needs it.
exec
/bin/bash -lc "pwd && ls -1 && printf '\\n--- AGENTS ---\\n' && sed -n '1,220p' AGENTS.md && printf '\\n--- SITE_CONTEXT ---\\n' && sed -n '1,260p' SITE_CONTEXT.md && printf '\\n--- ARTICLE_CONTENT_PLAN ---\\n' && sed -n '1,260p' ARTICLE_CONTENT_PLAN.md" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
/home/ubuntu/apps/ridgecrestchurch.com
AGENTS.md
ARTICLE_CONTENT_PLAN.md
SITE_CONTEXT.md
blog
favicon.gif
favicon.ico
index.php
license.txt
readme.html
wp-activate.php
wp-admin
wp-blog-header.php
wp-comments-post.php
wp-config-sample.php
wp-config.php
wp-content
wp-cron.php
wp-includes
wp-links-opml.php
wp-load.php
wp-login.php
wp-mail.php
wp-settings.php
wp-signup.php
wp-trackback.php
xmlrpc.php

--- AGENTS ---
# 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.

--- SITE_CONTEXT ---
# Site Context

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

## Identity

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

## Local Market Guidance

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

## Topic

Church website (Ridgecrest Baptist Church)

## Site Goals

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

## Required Pages

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

## Recovered Content Map

### 1. Ridgecrest Baptist Church

- Path: /
- Page type: home


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

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

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


### 2. Ridgecrest Baptist Church

- Path: /
- Page type: home


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

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

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


### 3. Ridgecrest Baptist Church

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


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

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

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


### 4. Ridgecrest Baptist Church

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


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

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

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


### 5. Ridgecrest Baptist Church-About Us

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


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

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

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


### 6. News-Ridgecrest Baptist Church

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


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

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

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


### 7. Contacts-Ridgecrest Baptist Church

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


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

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

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


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

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


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

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

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

--- ARTICLE_CONTENT_PLAN ---

# 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: 9
- Queued/running/scheduled: 1
- Published: 10
- 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 "printf '%s\\n' '--- TASK ---' && sed -n '1,260p' wp-content/uploads/flatlogic-article-tasks/job-457/task.md && printf '\\n--- POST CREATOR INSTRUCTIONS ---\\n' && sed -n '1,260p' wp-content/plugins/flatlogic-post-creator/INSTRUCTIONS.MD && printf '\\n--- CONTEXT FILES ---\\n' && find wp-content/plugins/flatlogic-post-creator/context -maxdepth 1 -type f -name '*.md' -print" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
--- TASK ---
# 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: Ministry Spotlight: How Our Teams Serve on Sundays (Greeters, Ushers, and Hospitality)
- 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 111 as the source of truth. Prepared article brief: Working title: Ministry Spotlight: How Our Teams Serve on Sundays (Greeters, Ushers, and Hospitality)
Slug hint: ministry-spotlight-sunday-teams
Meta description: Discover how the Sunday service teams at Ridgecrest Baptist Church enhance worship experiences for attendees. Learn about the roles of greeters, ushers, and hospitality volunteers,

Reader intent:
Help first-time and returning attendees understand what different Sunday teams do and how to participate or request help during the service.

Thesis:
The Sunday service teams at Ridgecrest Baptist Church play a crucial role in creating a welcoming and supportive environment for worshippers, and this article will highlight their contributions and how others can get involved.

Writer brief:
Provide a behind-the-scenes look at how the Sunday service teams operate, focusing on their roles and the importance of their contributions to the church community. Use a friendly, approachable tone to invite readers to engage with these teams.

Author voice notes:
Maintain a curious and approachable tone. Use plain language and relatable examples to engage the reader. Incorporate light humor where appropriate to make the content more inviting. Ensure the writing is informative without being overly technical or formal.

Key takeaways:
- Understanding the roles of greeters, ushers, and hospitality teams enhances the worship experience.
- Volunteering with Sunday service teams is a great way to get involved in the church community.
- Practical tips for asking for help during the service can ease first-time visitor anxiety.
- A welcoming environment is crucial for both newcomers and regular attendees.

Outline:
1. Quick welcome: why Sunday teams matter for a smooth, welcoming service
   Purpose: Introduce the importance of Sunday service teams in creating a positive experience.
  - Overview of the role of Sunday teams.
  - How they contribute to a welcoming atmosphere.
2. Greeters: what to expect at the door and how to get connected fast
   Purpose: Explain the role of greeters and their importance.
  - First impressions matter: the greeter's role.
  - How greeters help newcomers feel welcome.
3. Ushers: seating help, accessibility considerations, and where to find what you need
   Purpose: Detail the responsibilities of ushers during services.
  - Seating arrangements and accessibility support.
  - Where to find information and assistance.
4. Hospitality & communication: how we handle announcements, information, and visitor follow-up
   Purpose: Describe the hospitality team's role in communication.
  - How announcements are made.
  - Visitor follow-up processes.
5. Kids and family support touchpoints (high-level, non-duplicative of Kids page)
   Purpose: Highlight how Sunday teams support families without duplicating existing content.
  - Family-friendly initiatives during services.
  - Support for parents and children.
6. How to ask for help during the service (practical examples)
   Purpose: Provide practical advice for attendees seeking assistance.
  - Encouragement to ask for help.
  - Examples of common requests.
7. How to volunteer: what skills we look for, typical time commitment, and next steps
   Purpose: Encourage readers to consider volunteering.
  - Skills and qualities sought in volunteers.
  - Typical time commitment and how to get involved.
8. Closing: a short invitation to visit and meet the team
   Purpose: Wrap up the article with an invitation to engage.
  - Encouragement to visit Ridgecrest.
  - Invitation to meet the Sunday teams.
9. Optional sidebar: “Questions to ask before you serve” (one-minute checklist)
   Purpose: Provide additional value with a quick checklist for potential volunteers.
  - Key questions to consider before volunteering.
  - Encouragement to reflect on personal readiness.

Internal link plan:
- /: Link to the homepage for easy navigation.
- /about/: Provide context about the church and its mission.
- /ministries/: Highlight other ministries that may interest readers.
- /events-calendar/: Encourage participation in upcoming events.
- /contacts/: Provide contact information for further inquiries.
- /resources/: Direct readers to additional resources available.

Image direction:
A real church photo of a small group of volunteers welcoming attendees at the church entrance, or a candid photo of ushers/hospitality team setting up welcome materials.

Must include:
- Descriptions of each team's roles and responsibilities.
- Practical tips for attendees seeking assistance during the service.
- Information on how to volunteer with the Sunday teams.

Avoid:
- Duplicating the 'First-Timer’s Guide' or 'What to Expect at Ridgecrest' posts.
- Posting an exact RSVP/reminders/how-to-use-events-calendar guide.
- Any promotional or commercial language; keep it informational and church-focused.
- Fake stories or unverifiable claims about outcomes.

Quality checklist:
- Ensure clarity and accessibility in language and structure.
- Maintain a friendly and inviting tone throughout the article.
- Verify that all information is accurate and relevant to the church's current practices.
- Avoid jargon or overly complex language that may alienate readers. Article kind: evergreen Research status: not_required Reader intent: Help first-time and returning attendees understand what different Sunday teams do and how to participate or request help during the service. Planned outline: Quick welcome: why Sunday teams matter for a smooth, welcoming service | Greeters: what to expect at the door and how to get connected fast | Ushers: seating help, accessibility considerations, and where to find what you need | Hospitality & communication: how we handle announcements, information, and visitor follow-up | Kids and family support touchpoints (high-level, non-duplicative of Kids page) | How to ask for help during the service (practical examples) | How to volunteer: what skills we look for, typical time commitment, and next steps | Closing: a short invitation to visit and meet the team | Optional sidebar: “Questions to ask before you serve” (one-minute checklist) Image direction: A real church photo of a small group of volunteers welcoming attendees at the church entrance (or a candid photo of ushers/hospitality team setting up welcome materials). Preferred internal links: /, /about/, /ministries/, /events-calendar/, /contacts/, /resources/ Avoid: Duplicating the “First-Timer’s Guide” or “What to Expect at Ridgecrest” posts, Posting an exact RSVP/reminders/how-to-use-events-calendar guide, Any promotional or commercial language; keep it informational and church-focused, Fake stories or unverifiable claims about outcomes

## Selected Article Content Plan Item

- Plan item ID: 111
- Plan order: 21
- Article kind: evergreen
- Planned title: Ministry Spotlight: How Our Teams Serve on Sundays (Greeters, Ushers, and Hospitality)
- Slug hint: ministry-spotlight-sunday-teams
- Reader intent: Help first-time and returning attendees understand what different Sunday teams do and how to participate or request help during the service.
- Angle: A behind-the-scenes, people-first explanation of how Sunday service teams support worship and visitors at Ridgecrest—what they do, how they help, and how someone can volunteer.
- Image direction: A real church photo of a small group of volunteers welcoming attendees at the church entrance (or a candid photo of ushers/hospitality team setting up welcome materials).
- Author hint: Use the selected virtual author.

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

Outline:
- Quick welcome: why Sunday teams matter for a smooth, welcoming service
- Greeters: what to expect at the door and how to get connected fast
- Ushers: seating help, accessibility considerations, and where to find what you need
- Hospitality & communication: how we handle announcements, information, and visitor follow-up
- Kids and family support touchpoints (high-level, non-duplicative of Kids page)
- How to ask for help during the service (practical examples)
- How to volunteer: what skills we look for, typical time commitment, and next steps
- Closing: a short invitation to visit and meet the team
- Optional sidebar: “Questions to ask before you serve” (one-minute checklist)

Preferred internal link targets:
- /
- /about/
- /ministries/
- /events-calendar/
- /contacts/
- /resources/

Avoid:
- Duplicating the “First-Timer’s Guide” or “What to Expect at Ridgecrest” posts
- Posting an exact RSVP/reminders/how-to-use-events-calendar guide
- Any promotional or commercial language; keep it informational and church-focused
- Fake stories or unverifiable claims about outcomes

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: Nora Finch
Slug: nora-finch
Role: Curious explainer and resource writer
Language: English
Public bio: Nora turns unfamiliar topics into approachable guides, definitions, and resource articles for readers who want the plain version first.
Character formula: Curious Explorer Everyman
Formula: Explorer + Everyman
Meaning: A curious, relatable explainer who approaches unfamiliar topics like a smart ordinary reader asking useful questions.
Worldview: Most topics become less intimidating when someone maps the basics without pretending readers are experts.
Voice guidance: Curious, approachable, example-driven, plain-language. Define terms, compare options, and keep the reader included.
Humor: Light, relatable, observational humor.
Shadow tension: Can become too introductory; add enough specificity to avoid generic explanations.
Usage notes: Best for definitions, beginner guides, resource posts, and consumer-friendly explainers.
Archetype blend: Explorer + Everyman
Standard archetype voice guidance:

Primary archetype card: Explorer
Meaning: The restless seeker of freedom, movement, discovery, and new worlds.
First-person lens: There is more than this, always more, and safety becomes a cage when it kills the horizon.
Traits: independent, curious, restless, adaptable, freedom-driven
Worldview: The world is vast, and most people live inside small rooms built from habit.
Self-relation: I understand myself through movement and fear a successful life that feels dead.
Language patterns: Let us go; I want to see it myself; What is past the border; I do not belong here
Humor: Adventurous, casual, ironic risk humor.
Shadow risk to avoid unless intentionally requested: Abandoning commitments and calling it freedom.

Secondary archetype card: Everyman
Meaning: The ordinary human who wants belonging, dignity, survival, and a place in the world.
First-person lens: I am not special, and that is the problem and maybe the gift; I know what it is to be left out.
Traits: relatable, grounded, sincere, practical, socially aware
Worldview: The world feels large and unfair, full of people who seem more important.
Self-relation: I want to be chosen but distrust special treatment.
Language patterns: I just want to get through this; People like us; That is not fair; Why me
Humor: Awkward, relatable, observational.
Shadow risk to avoid unless intentionally requested: Passivity, resentment, fear of standing out.
Shadow tension: Loves discovery but must avoid wandering away from the reader's actual task.
Worldview: Every topic has a doorway; the writer's job is to find the one normal people can walk through.
Reader relationship: Curious peer walking through the topic with the reader.
Humor style: Warm observational humor, usually one small aside rather than a performance.
Voice traits: curious, accessible, friendly, example-driven
Vocabulary / recurring language: plain version, quick map, where this shows up, the short answer
Avoid voice: lecturing, inside-baseball jargon, over-explaining simple points, forced whimsy
CTA style: Offer the reader a simple next question to answer or a related guide to open next.
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: Curious, observant, friendly, and comfortable asking the obvious question readers may be afraid to ask.
Writing style: Uses simple framing, examples, analogies, question-led headings, and gentle transitions from basic to intermediate ideas.
Expertise topics: definitions, beginner guides, home improvement explainers, consumer research, web basics
Avoid topics: technical guarantees, health treatment advice, investment recommendations
Tone tags: curious, approachable, plain-language, light
Private operator notes: Useful for neutral legacy resources and intro-level explainers.

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.

--- POST CREATOR INSTRUCTIONS ---
# 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.

--- CONTEXT FILES ---
wp-content/plugins/flatlogic-post-creator/context/PRINCIPLES.md

codex
I’ve confirmed the site contract and the review target. Next I’m checking the existing post, current attachments, and the post-creator context rules so I can replace only the image assets and re-verify the live post cleanly.
exec
/bin/bash -lc "printf '%s\\n' '--- PRINCIPLES ---' && sed -n '1,260p' wp-content/plugins/flatlogic-post-creator/context/PRINCIPLES.md && printf '\\n--- FINAL REQUIREMENTS ---\\n' && sed -n '1,260p' wp-content/plugins/flatlogic-post-creator/context/FINAL_REQUIREMENTS.MD" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
--- PRINCIPLES ---
Here’s the writer SOP I’d hand to someone who has to produce a serious, quotable article.

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

## Operating definitions

Use these before you write a word.

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

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

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

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

My recommended floor for a serious non-breaking article:

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

That is my operating minimum, not a universal law.

---

## 1. Why this story exists

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

### 1.1 Ask

Write down answers to these, in one sentence each:

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

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

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

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

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

### 1.2 Write

Create a 5-line assignment brief:

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

### 1.3 Produce

A one-sentence story brief:

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

### 1.4 Gate

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

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

Kill or reframe.

---

## 2. Convert the topic into a question tree

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

### 2.1 Ask

Turn the topic into a precise question.

Bad:

* “AI code editors vs traditional IDEs”

Better:

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

### 2.2 Build the tree

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

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

### 2.3 Write two counterweights

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

Example:

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

### 2.4 Gate

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

---

## 3. Build the evidence matrix before collecting facts

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

### 3.1 Create a matrix

Make a table or spreadsheet with these columns:

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

### 3.2 Use a source hierarchy

Rank sources like this:

**Tier A — primary**

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

**Tier B — on-record participants**

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

**Tier C — independent interpreters**

* analysts
* academics
* domain experts
* critics

**Tier D — secondary synthesis**

* other articles
* industry reports
* commentary

### 3.3 Use a support rule

My recommended rule for each material claim:

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

### 3.4 Gate

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

---

## 4. Scan the field and locate the gap

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

### 4.1 Search in this order

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

### 4.2 For each existing article, extract

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

### 4.3 Produce a “gap memo”

Write 5 bullets:

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

### 4.4 Gate

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

---

## 5. Do primary reporting, not elegant aggregation

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

### 5.1 Gather original material

Depending on the topic, that means:

* documents,
* screenshots,
* exports,
* logs,
* demos,
* raw datasets,
* changelogs,
* legal terms,
* benchmark setups,
* user workflows,
* field notes.

### 5.2 If the article compares tools, products, or workflows

Freeze the test conditions **before** you test.

Define:

* **task set**

--- FINAL REQUIREMENTS ---
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 "wp core is-installed && printf '\\nHOME: ' && wp option get home && printf 'SITEURL: ' && wp option get siteurl && printf 'ACTIVE THEME:\\n' && wp theme list --status=active && printf '\\nDB PREFIX: ' && wp db prefix && printf '\\nPOSTS:\\n' && wp post list --post_type=post --fields=ID,post_title,post_name,post_status,post_author --format=table" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc 'wp post list --post_type=attachment --fields=ID,post_title,post_mime_type,guid --format=table' in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 621ms:
ID	post_title	post_mime_type	guid
89	Wednesday Night Kids Check-In Scene	image/jpeg	https://ridgecrestchurch.com/wp-content/uploads/imports/wednesday-night-kids-check-in-scene.jpg
86	Ridgecrest Events Calendar Page Screenshot	image/png	http://ridgecrestchurch.com/wp-content/uploads/imports/events-calendar-page-screenshot.png
79	Ridgecrest Website Navigation Screenshot	image/png	https://ridgecrestchurch.com/ridgecrest-website-navigation-screenshot/
76	Sunday Service Planning Desk	image/jpeg	http://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg
1	Ridgecrest Baptist Church Logo	image/gif	https://ridgecrestchurch.com/wp-content/uploads/imports/logo.gif
2	Ridgecrest Service Times	image/gif	https://ridgecrestchurch.com/wp-content/uploads/imports/service-times.gif
3	Ridgecrest Events Calendar	image/gif	https://ridgecrestchurch.com/wp-content/uploads/imports/events.gif
4	Ridgecrest Connection Graphic	image/gif	https://ridgecrestchurch.com/wp-content/uploads/imports/connect.gif
5	Ridgecrest Sermons Graphic	image/gif	https://ridgecrestchurch.com/wp-content/uploads/imports/sermons.gif
6	Ridgecrest Contact Graphic	image/gif	https://ridgecrestchurch.com/wp-content/uploads/imports/contact-info.gif
7	Ridgecrest Map Graphic	image/gif	https://ridgecrestchurch.com/wp-content/uploads/imports/map-directions.gif
8	Ridgecrest Community Illustration	image/jpeg	https://ridgecrestchurch.com/wp-content/uploads/imports/groups.jpg
9	Ridgecrest Main Entrance	image/jpeg	https://ridgecrestchurch.com/wp-content/uploads/imports/church-exterior.jpg
10	Worship Service	image/jpeg	https://ridgecrestchurch.com/wp-content/uploads/imports/worship-service.jpg
11	Children Ministry	image/jpeg	https://ridgecrestchurch.com/wp-content/uploads/imports/children-ministry.jpg
12	Youth Worship	image/jpeg	https://ridgecrestchurch.com/wp-content/uploads/imports/youth-worship.jpg

codex
The existing media library is small, and the current welcome-team image issue is real. I’m checking whether the post already exists and whether there’s any better on-site media before I import a rights-safe replacement.
exec
/bin/bash -lc "find wp-content/uploads -maxdepth 4 \\( -iname '*.jpg' -o -iname '*.jpeg' -o -iname '*.png' -o -iname '*.webp' \\) | sed 's#"'^#FILE: #'"'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
FILE: wp-content/uploads/imports/youth-worship.jpg
FILE: wp-content/uploads/imports/youth-group.jpg
FILE: wp-content/uploads/imports/ridgecrest-home-navigation-screenshot.png
FILE: wp-content/uploads/imports/groups.jpg
FILE: wp-content/uploads/imports/wednesday-night-kids-check-in-scene.jpg
FILE: wp-content/uploads/imports/church-exterior.jpg
FILE: wp-content/uploads/imports/children-ministry.jpg
FILE: wp-content/uploads/imports/events-calendar-page-screenshot.png
FILE: wp-content/uploads/imports/worship-service.jpg
FILE: wp-content/uploads/imports/sunday-service-planning-desk.jpg

 succeeded in 6516ms:

HOME: https://ridgecrestchurch.com
SITEURL: https://ridgecrestchurch.com
ACTIVE THEME:
name	status	update	version	update_version	auto_update
church	active	none	0.7.7		off

DB PREFIX: flbg_

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

exec
/bin/bash -lc "wp post list --post_type=post --fields=ID,post_title,post_name,post_status --format=csv | rg 'ministry-spotlight-sunday-teams|Ministry Spotlight: How Our Teams Serve on Sundays'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 539ms:
113,"Ministry Spotlight: How Our Teams Serve on Sundays (Greeters, Ushers, and Hospitality)",ministry-spotlight-sunday-teams,publish

codex
I’ve confirmed the target post is `113`. The current library doesn’t have a clean greeter/usher/hospitality photo, so I’m doing a targeted asset search now and then I’ll swap the featured and inline image together.
exec
/bin/bash -lc 'wp post get 113 --field=post_content' in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "wp post meta get 113 _thumbnail_id || true && printf '\\nURL: ' && wp post url 113" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "for q in 'church greeters volunteers entrance site:commons.wikimedia.org' 'church hospitality volunteers welcome table site:commons.wikimedia.org' 'church greeters door volunteers site:unsplash.com'; do printf '\\n=== %s ===\\n' \""'$q"; curl -L -A '"'Mozilla/5.0' --get --data-urlencode \"q="'$q" '"'https://duckduckgo.com/html/' | rg -o 'https?://["'^"&<> ]+'"' | head -n 12; done" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 568ms:
<p><strong><em>A welcoming Sunday rarely happens by accident. It usually happens because a few steady people are paying attention before you ever wonder where to sit, where your child should go, or whether it is okay to ask for help.</em></strong></p>

<p>If you have ever walked into a church and thought, “Do I just follow the crowd?” or “Who do I ask without feeling awkward?” this is the plain version first. At Ridgecrest Baptist Church, Sunday teams help remove little points of friction so worshippers can focus on the service instead of guessing their way through the morning.</p>

<p>This article gives a quick map of what greeters, ushers, and hospitality volunteers typically do, how families can find the right help, and what to do if you want to serve alongside them. If you want the bigger picture of the church’s mission, the <a href="https://ridgecrestchurch.com/about-us/">About Us page</a> is a good next stop. If you mainly want the “where do I go this Sunday?” version, keep reading.</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>A smooth Sunday experience is shaped by the people you meet before, during, and after the service.</figcaption>
</figure>

<h2>Why Sunday teams matter</h2>

<p>Sunday service teams do not exist to make the morning feel polished for its own sake. They exist to make the church easier to enter, easier to navigate, and easier to participate in. That matters for first-time guests, long-time members, parents carrying three things too many, and anyone who arrives needing a little extra guidance.</p>

<p>Ridgecrest’s <a href="https://ridgecrestchurch.com/">home page</a> and <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> help with the schedule ahead of time, but people still need in-person help once they arrive. That is where Sunday teams become visible in the best way: not as a performance, but as a calm presence.</p>

<p>That kind of welcome lines up with the spirit of <a href="https://www.biblegateway.com/passage/?search=Romans%2015%3A7&amp;version=NIV&amp;utm_source=ridgecrestchurch.com">Romans 15:7</a>, which points believers toward receiving one another with the same grace they have received. The short answer is simple: a church feels warmer when people are intentionally looking out for one another.</p>

<h2>Greeters: what to expect at the door</h2>

<p>Greeters are often the first faces you meet on a Sunday morning. Their job is not to corner anyone into a long conversation before coffee has done its work. Their job is to notice people, offer a welcome, and help newcomers take the next obvious step.</p>

<p>That can look very ordinary, which is usually a good sign. A greeter may point you toward the main entrance, answer a quick question about where to go, help you find the sanctuary, or direct you to the right page if you want details later on. If you are new, a greeter can also help you connect with the right ministry area, including the broader opportunities listed on the <a href="https://ridgecrestchurch.com/ministries/">Ministries page</a>.</p>

<p>For families, this first contact matters even more. A calm welcome at the door can save parents from the classic Sunday question: “Are we confidently walking in the right direction, or just walking briskly and hoping for the best?” If you have children with you, a greeter can usually point you toward the right next step and help you reach the church’s <a href="https://ridgecrestchurch.com/kids/">Kids ministry information</a> without making the morning feel complicated.</p>

<h2>Ushers: seating help, accessibility, and practical support</h2>

<p>Once you are inside, ushers help the room make sense. They assist with seating, help people find open spots, answer practical questions, and watch for needs that are easy to miss if everyone assumes someone else will handle them.</p>

<p>If you arrive late, are unsure where to sit, or need help finding a good place for your family, an usher is one of the best people to ask. Ushers can also be a helpful contact if you need directions to restrooms, classrooms, or the best path through the building. The goal is not formality. The goal is lowering the stress level by one or two clicks.</p>

<p>This also includes accessibility awareness. Someone may need a little more room, a simpler route, extra time getting seated, or help locating the most comfortable place to sit. Even when the request feels small, asking matters. An usher would generally rather help early than have someone spend the whole service quietly uncomfortable.</p>

<p>For anyone planning ahead, the <a href="https://ridgecrestchurch.com/contacts/">Contacts page</a> and <a href="https://ridgecrestchurch.com/resources/">Resources page</a> are useful places to start before Sunday. They make it easier to ask questions in advance rather than improvising once you are in the parking lot.</p>

<h2>Hospitality and communication: the people behind the smooth parts</h2>

<p>Hospitality is the broader layer that helps Sunday feel coordinated instead of scattered. This often includes welcome materials, answering basic questions, helping visitors know where to go next, and making sure people know where to look for current information.</p>

<p>At Ridgecrest, the site already points visitors toward the two most useful places for updates: the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for the weekly rhythm and the News page for highlighted announcements. In person, hospitality-minded volunteers help bridge the gap between those pages and real life. They can help someone locate a classroom, understand what happens after the service, or find the right person to speak with about ministry questions.</p>

<p>The heart behind that work fits the practical tone of <a href="https://www.biblegateway.com/passage/?search=Hebrews%2013%3A2&amp;version=NIV&amp;utm_source=ridgecrestchurch.com">Hebrews 13:2</a>, which treats hospitality as something worth practicing on purpose. In other words, welcome is not accidental background noise. It is part of how a church cares for people.</p>

<p>If you share a question or contact detail with the church, the goal is usually simple follow-up: connect you with the right person, answer the question clearly, and make the next step easier. That does not need to feel formal to be useful. Sometimes good hospitality is as basic as making sure nobody leaves with preventable confusion.</p>

<h2>Kids and family support touchpoints</h2>

<p>Sunday teams also serve families, even when their role is not labeled “kids ministry.” Greeters and ushers help parents find entrances, classrooms, seating, and the next right conversation. That matters because family logistics can feel calm or chaotic on a very thin margin.</p>

<p>The church’s <a href="https://ridgecrestchurch.com/kids/">Kids page</a> gives the fuller picture for children’s ministry, so this article will stay high-level. The practical point is that families do not have to solve everything alone on the sidewalk. If you are carrying a diaper bag, guiding an elementary-age child, and trying to remember whether you saw the right hallway, you are exactly the kind of person Sunday teams hope to help.</p>

<p>Parents can make the morning easier by checking details ahead of time, but it is still perfectly reasonable to ask for help once you arrive. That is not interrupting the system. That is the system working.</p>

<h2>How to ask for help during the service</h2>

<p>If you need help on a Sunday, the best move is usually the simplest one: ask the nearest greeter or usher. You do not need special wording. A short, direct question is enough.</p>

<ul>
  <li><strong>“Where should our family sit?”</strong> Helpful if you are visiting with children, arriving late, or prefer an easier exit.</li>
  <li><strong>“Can you point me to the kids area?”</strong> Good for parents or grandparents who want the fastest route.</li>
  <li><strong>“Who should I talk to about volunteering?”</strong> Useful if you want a next step after the service.</li>
  <li><strong>“Is there a quieter place to step out for a moment?”</strong> Helpful for families, caregivers, or anyone needing a short break.</li>
  <li><strong>“Can someone help me find the contact person for this ministry?”</strong> A practical question when you want the right follow-up instead of a vague maybe-later.</li>
</ul>

<p>If you prefer to ask before arriving, the <a href="https://ridgecrestchurch.com/contacts/">Contacts page</a> includes phone, email, and address details, and it specifically invites questions about worship, children’s ministry, student ministry, prayer needs, and directions. That is a helpful option if you want fewer unknowns before Sunday morning begins.</p>

<h2>How to volunteer with Sunday teams</h2>

<p>Serving on a Sunday team is one of the clearest ways to help people feel seen. The role does not require being the loudest person in the room or having a perfectly polished church voice. In many cases, the best fit is someone dependable, attentive, kind, and willing to notice what another person needs.</p>

<p>Useful strengths for these teams often include:</p>

<ul>
  <li>A warm, steady presence with guests and regular attenders</li>
  <li>Comfort answering simple questions or finding the right person</li>
  <li>Awareness of families, seniors, and visitors who may need extra help</li>
  <li>Reliability with arrival time and basic Sunday preparation</li>
  <li>A willingness to serve in small ways that make a big difference</li>
</ul>

<p>The time commitment will depend on the role and the church’s current scheduling, so the cleanest next step is to ask directly through the <a href="https://ridgecrestchurch.com/contacts/">Contacts page</a> or speak with someone after the service. If you are still exploring where you might fit, the <a href="https://ridgecrestchurch.com/ministries/">Ministries page</a> can help you see the broader picture before you commit.</p>

<p>This kind of service also fits the tone of <a href="https://www.biblegateway.com/passage/?search=1%20Peter%204%3A9&amp;version=NIV&amp;utm_source=ridgecrestchurch.com">1 Peter 4:9</a>, where hospitality is connected to glad-hearted service rather than reluctant duty. Sunday teams work best when people see the role not as crowd management, but as care.</p>

<h2>One-minute checklist: questions to ask before you serve</h2>

<table>
  <thead>
    <tr>
      <th>Question</th>
      <th>Why it helps</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Do I enjoy helping people feel less lost?</td>
      <td>That instinct is often a strong fit for greeting, ushering, or hospitality.</td>
    </tr>
    <tr>
      <td>Can I arrive a little early and stay attentive?</td>
      <td>These roles usually work best when volunteers are present before the service flow begins.</td>
    </tr>
    <tr>
      <td>Am I comfortable asking a leader when I do not know the answer?</td>
      <td>Good service is not pretending to know everything. It is helping people get to the right person quickly.</td>
    </tr>
    <tr>
      <td>Would I rather serve quietly than be in the spotlight?</td>
      <td>That is often exactly what makes someone effective on a Sunday team.</td>
    </tr>
  </tbody>
</table>

<h2>A simple invitation</h2>

<p>If you are visiting Ridgecrest, Sunday teams are there to make the morning easier, not more complicated. Ask the question. Take the help. Let someone point you in the right direction.</p>

<p>If you already call Ridgecrest home, Sunday service teams are also a meaningful place to serve. A smile at the door, a steady answer in the hallway, or a timely offer to help someone find their seat may not look dramatic. It just looks like church being church, which is usually the point.</p>

 succeeded in 1173ms:
10

URL: https://ridgecrestchurch.com/ministry-spotlight-sunday-teams/

 succeeded in 1409ms:
100 34965    0 34965    0     0  37936      0 --:--:-- --:--:-- --:--:-- 37936
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd
http://www.w3.org/1999/xhtml
http://www.w3.org/1999/xhtml
http://www.w3.org/1999/xhtml
http://www.w3.org/1999/xhtml

=== church hospitality volunteers welcome table site:commons.wikimedia.org ===
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0100   138  100   138    0     0   1347      0 --:--:-- --:--:-- --:--:--  1339100   138  100   138    0     0   1345      0 --:--:-- --:--:-- --:--:--  1339
100 14286    0 14286    0     0  52697      0 --:--:-- --:--:-- --:--:-- 52697
http://www.w3.org/TR/html4/loose.dtd
https://duckduckgo.com/
https://duckduckgo.com/

=== church greeters door volunteers site:unsplash.com ===
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0100   138  100   138    0     0   1366      0 --:--:-- --:--:-- --:--:--  1380
100 14250    0 14250    0     0  62310      0 --:--:-- --:--:-- --:--:-- 62310
http://www.w3.org/TR/html4/loose.dtd
https://duckduckgo.com/
https://duckduckgo.com/

codex
The article body is intact and the current inline image is attachment `10`, which is exactly the weak match the reviewer flagged. I’m now pulling a better rights-safe source image and then I’ll update both the inline figure and featured image in one pass.
exec
/bin/bash -lc 'wp post get 113 --field=guid && wp post url 113' in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "for u in 'https://unsplash.com/s/photos/church-welcome' 'https://www.pexels.com/search/church%20welcome/' 'https://www.pexels.com/search/church%20volunteers/' 'https://commons.wikimedia.org/w/index.php?search=church+volunteers&title=Special:MediaSearch&go=Go&type=image'; do printf '\\n=== %s ===\\n' \""'$u"; curl -L -A '"'Mozilla/5.0' \""'$u" | rg -o '"'https?://["'^"'"'\"'\"' <>)]+' | head -n 40; done" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 1103ms:
https://ridgecrestchurch.com/ministry-spotlight-sunday-teams/
https://ridgecrestchurch.com/ministry-spotlight-sunday-teams/

 succeeded in 2337ms:
100    22  100    22    0     0     91      0 --:--:-- --:--:-- --:--:--    92
100  4483    0  4483    0     0  12226      0 --:--:-- --:--:-- --:--:-- 12226
https://anubis.techaro.lol/docs/admin/botstopper
https://techaro.lol
https://help.unsplash.com/

=== https://www.pexels.com/search/church%20welcome/ ===
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0100  5498  100  5498    0     0  63124      0 --:--:-- --:--:-- --:--:-- 63930
https://challenges.cloudflare.com;
https://challenges.cloudflare.com;
https://challenges.cloudflare.com;
https://challenges.cloudflare.com
https://challenges.cloudflare.com

=== https://www.pexels.com/search/church%20volunteers/ ===
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0100  5507  100  5507    0     0   101k      0 --:--:-- --:--:-- --:--:--  101k
https://challenges.cloudflare.com;
https://challenges.cloudflare.com;
https://challenges.cloudflare.com;
https://challenges.cloudflare.com
https://challenges.cloudflare.com

=== https://commons.wikimedia.org/w/index.php?search=church+volunteers&title=Special:MediaSearch&go=Go&type=image ===
  % 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     0    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0  0     0    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0https://commons.wikimedia.org/wiki/File:St_Pauls_Church,_Brentford,_City_of_London_Imperial_Volunteers_memorial.jpg
https://commons.wikimedia.org/w/index.php?title=File:St_Pauls_Church,_Brentford,_City_of_London_Imperial_Volunteers_memorial.jpg\u0026action=edit
https://commons.wikimedia.org/wiki/File:St_Pauls_Church,_Brentford,_City_of_London_Imperial_Volunteers_memorial.jpg
https://upload.wikimedia.org/wikipedia/commons/thumb/c/cc/St_Pauls_Church%2C_Brentford%2C_City_of_London_Imperial_Volunteers_memorial.jpg/250px-St_Pauls_Church%2C_Brentford%2C_City_of_London_Imperial_Volunteers_memorial.jpg
https://upload.wikimedia.org/wikipedia/commons/thumb/c/cc/St_Pauls_Church%2C_Brentford%2C_City_of_London_Imperial_Volunteers_memorial.jpg/500px-St_Pauls_Church%2C_Brentford%2C_City_of_London_Imperial_Volunteers_memorial.jpg
https://upload.wikimedia.org/wikipedia/commons/c/cc/St_Pauls_Church%2C_Brentford%2C_City_of_London_Imperial_Volunteers_memorial.jpg
https://commons.wikimedia.org/wiki/File:St_Pauls_Church,_Brentford,_City_of_London_Imperial_Volunteers_memorial.jpg
https://commons.wikimedia.org/w/index.php?curid=174141939
https://commons.wikimedia.org/wiki/File:Finnish_Volunteers_memorial_-_Old_Church_Park_-_Helsinki_-_DSC03792.JPG
https://commons.wikimedia.org/w/index.php?title=File:Finnish_Volunteers_memorial_-_Old_Church_Park_-_Helsinki_-_DSC03792.JPG\u0026action=edit
https://commons.wikimedia.org/wiki/File:Finnish_Volunteers_memorial_-_Old_Church_Park_-_Helsinki_-_DSC03792.JPG
https://upload.wikimedia.org/wikipedia/commons/thumb/9/99/Finnish_Volunteers_memorial_-_Old_Church_Park_-_Helsinki_-_DSC03792.JPG/250px-Finnish_Volunteers_memorial_-_Old_Church_Park_-_Helsinki_-_DSC03792.JPG
https://upload.wikimedia.org/wikipedia/commons/thumb/9/99/Finnish_Volunteers_memorial_-_Old_Church_Park_-_Helsinki_-_DSC03792.JPG/330px-Finnish_Volunteers_memorial_-_Old_Church_Park_-_Helsinki_-_DSC03792.JPG
https://upload.wikimedia.org/wikipedia/commons/9/99/Finnish_Volunteers_memorial_-_Old_Church_Park_-_Helsinki_-_DSC03792.JPG
https://commons.wikimedia.org/wiki/File:Finnish_Volunteers_memorial_-_Old_Church_Park_-_Helsinki_-_DSC03792.JPG
https://commons.wikimedia.org/w/index.php?curid=22903183
https://commons.wikimedia.org/wiki/File:Finnish_Volunteers_memorial_-_Old_Church_Park_-_Helsinki_-_DSC03793.JPG
https://commons.wikimedia.org/w/index.php?title=File:Finnish_Volunteers_memorial_-_Old_Church_Park_-_Helsinki_-_DSC03793.JPG\u0026action=edit
https://commons.wikimedia.org/wiki/File:Finnish_Volunteers_memorial_-_Old_Church_Park_-_Helsinki_-_DSC03793.JPG
https://upload.wikimedia.org/wikipedia/commons/thumb/f/f3/Finnish_Volunteers_memorial_-_Old_Church_Park_-_Helsinki_-_DSC03793.JPG/250px-Finnish_Volunteers_memorial_-_Old_Church_Park_-_Helsinki_-_DSC03793.JPG
https://upload.wikimedia.org/wikipedia/commons/thumb/f/f3/Finnish_Volunteers_memorial_-_Old_Church_Park_-_Helsinki_-_DSC03793.JPG/330px-Finnish_Volunteers_memorial_-_Old_Church_Park_-_Helsinki_-_DSC03793.JPG
https://upload.wikimedia.org/wikipedia/commons/f/f3/Finnish_Volunteers_memorial_-_Old_Church_Park_-_Helsinki_-_DSC03793.JPG
https://commons.wikimedia.org/wiki/File:Finnish_Volunteers_memorial_-_Old_Church_Park_-_Helsinki_-_DSC03793.JPG
https://commons.wikimedia.org/w/index.php?curid=22903184
https://commons.wikimedia.org/wiki/File:Finnish_Volunteers_memorial_-_Old_Church_Park_-_Helsinki_-_DSC03794.JPG
https://commons.wikimedia.org/w/index.php?title=File:Finnish_Volunteers_memorial_-_Old_Church_Park_-_Helsinki_-_DSC03794.JPG\u0026action=edit
https://commons.wikimedia.org/wiki/File:Finnish_Volunteers_memorial_-_Old_Church_Park_-_Helsinki_-_DSC03794.JPG
https://upload.wikimedia.org/wikipedia/commons/thumb/b/b0/Finnish_Volunteers_memorial_-_Old_Church_Park_-_Helsinki_-_DSC03794.JPG/250px-Finnish_Volunteers_memorial_-_Old_Church_Park_-_Helsinki_-_DSC03794.JPG
https://upload.wikimedia.org/wikipedia/commons/thumb/b/b0/Finnish_Volunteers_memorial_-_Old_Church_Park_-_Helsinki_-_DSC03794.JPG/330px-Finnish_Volunteers_memorial_-_Old_Church_Park_-_Helsinki_-_DSC03794.JPG
https://upload.wikimedia.org/wikipedia/commons/b/b0/Finnish_Volunteers_memorial_-_Old_Church_Park_-_Helsinki_-_DSC03794.JPG
https://commons.wikimedia.org/wiki/File:Finnish_Volunteers_memorial_-_Old_Church_Park_-_Helsinki_-_DSC03794.JPG
https://commons.wikimedia.org/w/index.php?curid=22903190
https://commons.wikimedia.org/wiki/File:Dudley_Perring_Kingsford_City_of_London_Imperial_Volunteers_plaque_All_Saints%27_Church,_Oakleigh_Park.jpg
https://commons.wikimedia.org/w/index.php?title=File:Dudley_Perring_Kingsford_City_of_London_Imperial_Volunteers_plaque_All_Saints%27_Church,_Oakleigh_Park.jpg\u0026action=edit
https://commons.wikimedia.org/wiki/File:Dudley_Perring_Kingsford_City_of_London_Imperial_Volunteers_plaque_All_Saints%27_Church,_Oakleigh_Park.jpg
https://upload.wikimedia.org/wikipedia/commons/thumb/3/3b/Dudley_Perring_Kingsford_City_of_London_Imperial_Volunteers_plaque_All_Saints%27_Church%2C_Oakleigh_Park.jpg/250px-Dudley_Perring_Kingsford_City_of_London_Imperial_Volunteers_plaque_All_Saints%27_Church%2C_Oakleigh_Park.jpg
https://upload.wikimedia.org/wikipedia/commons/thumb/3/3b/Dudley_Perring_Kingsford_City_of_London_Imperial_Volunteers_plaque_All_Saints%27_Church%2C_Oakleigh_Park.jpg/500px-Dudley_Perring_Kingsford_City_of_London_Imperial_Volunteers_plaque_All_Saints%27_Church%2C_Oakleigh_Park.jpg
https://upload.wikimedia.org/wikipedia/commons/3/3b/Dudley_Perring_Kingsford_City_of_London_Imperial_Volunteers_plaque_All_Saints%27_Church%2C_Oakleigh_Park.jpg
https://commons.wikimedia.org/wiki/File:Dudley_Perring_Kingsford_City_of_London_Imperial_Volunteers_plaque_All_Saints%27_Church,_Oakleigh_Park.jpg
https://commons.wikimedia.org/w/index.php?curid=49125752
100  143k    0  143k    0     0  80319      0 --:--:--  0:00:01 --:--:-- 80317
curl: (23) Failure writing output to destination

codex
Search results from the usual free-photo sites are mostly bot-blocked from the shell, so I’m checking the local imports visually before I decide whether I need to pull a new asset from a different source path.
exec
/bin/bash -lc "for q in 'church greeter' 'church welcome table' 'church usher' 'church volunteers entrance'; do printf '\\n=== %s ===\\n' \""'$q"; curl -sG '"'https://commons.wikimedia.org/w/api.php' --data-urlencode 'action=query' --data-urlencode 'list=search' --data-urlencode \"srsearch="'$q" --data-urlencode '"'srnamespace=6' --data-urlencode 'srlimit=10' --data-urlencode 'format=json' | jq -r '.query.search[] | [.title,.snippet] | @tsv'; done" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "for q in 'church greeter photo' 'church hospitality volunteers photo' 'church ushers photo'; do printf '\\n=== %s ===\\n' \""'$q"; curl -sG '"'https://commons.wikimedia.org/w/api.php' --data-urlencode 'action=query' --data-urlencode 'generator=search' --data-urlencode \"gsrsearch="'$q" --data-urlencode '"'gsrnamespace=6' --data-urlencode 'gsrlimit=5' --data-urlencode 'prop=imageinfo' --data-urlencode 'iiprop=url|extmetadata' --data-urlencode 'iiurlwidth=1200' --data-urlencode 'format=json' | jq -r '.query.pages[]? | [.title, .imageinfo[0].thumburl, (.imageinfo[0].extmetadata.LicenseShortName.value // \"\"), (.imageinfo[0].extmetadata.Artist.value // \"\")] | @tsv'; done" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 2292ms:
File:Northeast View of the Greet Family Memorial.jpg	credit, provide a link <span class="searchmatch">to</span> the license, and indicate if changes were made. You may do so <span class="searchmatch">in</span> any reasonable manner, but not <span class="searchmatch">in</span> any way that suggests the
File:Southern Face of the Greet Family Memorial (II).jpg	credit, provide a link <span class="searchmatch">to</span> the license, and indicate if changes were made. You may do so <span class="searchmatch">in</span> any reasonable manner, but not <span class="searchmatch">in</span> any way that suggests the
File:Southern Face of the Greet Family Memorial (III).jpg	credit, provide a link <span class="searchmatch">to</span> the license, and indicate if changes were made. You may do so <span class="searchmatch">in</span> any reasonable manner, but not <span class="searchmatch">in</span> any way that suggests the
File:Southern Face of the Greet Family Memorial (I).jpg	credit, provide a link <span class="searchmatch">to</span> the license, and indicate if changes were made. You may do so <span class="searchmatch">in</span> any reasonable manner, but not <span class="searchmatch">in</span> any way that suggests the
File:War Memorial in Greete church - geograph.org.uk - 2532090.jpg	Attribution: War Memorial <span class="searchmatch">in</span> Greete <span class="searchmatch">church</span> by Philip Halling You are free: <span class="searchmatch">to</span> share – <span class="searchmatch">to</span> copy, distribute and transmit the work <span class="searchmatch">to</span> remix – <span class="searchmatch">to</span> adapt the work Under
File:Meet and Greet Centrepoint Church 240 Hamilton Rd Chermside P1040039.jpg	English Centrepoint <span class="searchmatch">Church</span> (formerly Chermside Assembly <span class="searchmatch">of</span> God) is at 240 Hamilton Road. It is part <span class="searchmatch">of</span> the Australian Christian <span class="searchmatch">Churches</span> network. author name
File:Meet and Greet Centrepoint Church 240 Hamilton Rd Chermside P1040034.jpg	English Centrepoint <span class="searchmatch">Church</span> (formerly Chermside Assembly <span class="searchmatch">of</span> God) is at 240 Hamilton Road. It is part <span class="searchmatch">of</span> the Australian Christian <span class="searchmatch">Churches</span> network. author name
File:Champion Forest Baptist Church greeter.jpg	credit, provide a link <span class="searchmatch">to</span> the license, and indicate if changes were made. You may do so <span class="searchmatch">in</span> any reasonable manner, but not <span class="searchmatch">in</span> any way that suggests the
File:Meet and Greet Centrepoint Church 240 Hamilton Rd Chermside P1040038.jpg	English Centrepoint <span class="searchmatch">Church</span> (formerly Chermside Assembly <span class="searchmatch">of</span> God) is at 240 Hamilton Road. It is part <span class="searchmatch">of</span> the Australian Christian <span class="searchmatch">Churches</span> network. author name
File:Meet and Greet Centrepoint Church 240 Hamilton Rd Chermside P1040037.jpg	English Centrepoint <span class="searchmatch">Church</span> (formerly Chermside Assembly <span class="searchmatch">of</span> God) is at 240 Hamilton Road. It is part <span class="searchmatch">of</span> the Australian Christian <span class="searchmatch">Churches</span> network. author name

=== church welcome table ===
File:Holy Table in Saint Nicholas' Parish Church - geograph.org.uk - 978457.jpg	Commons Attribution-Share Alike 2.0 truetrue English Holy <span class="searchmatch">Table</span> in Saint Nicholas&#039; Parish <span class="searchmatch">Church</span> object of statement has role: photographer URL: https://www
File:0557jfParish Church Halls Welcome Tortugas Rivas Balanga City Bataanfvf 29.JPG	Description0557jfParish <span class="searchmatch">Church</span> Halls <span class="searchmatch">Welcome</span> Tortugas Rivas Balanga City Bataanfvf 29.JPG English: Barangay Pto. Rivas Ibaba, Immaculate Conception Parish <span class="searchmatch">Church</span> Balanga
File:1346jfCalulut Welcome Parish SanFernando Pampangafvf 17.JPG	Description1346jfCalulut <span class="searchmatch">Welcome</span> Parish SanFernando Pampangafvf 17.JPG English: BarangayCalulut,City of San Fernando, Pampanga San Vicente Ferrer <span class="searchmatch">Church</span> (Calulut),
File:Around the tea-table (IA aroundteatable01talm).pdf	Around the tea-<span class="searchmatch">table</span>   (  ) Author Thomas De Witt Talmage (1832–1902)       Alternative names T. De Witt Talmage; Thomas DeWitt Talmage Description American
File:The "Breakfast-table" series (IA breakfastseries04holmrich).pdf	The &quot;Breakfast-<span class="searchmatch">table</span>&quot; series   (  ) Author Holmes, Oliver Wendell, 1809-1894 Title The &quot;Breakfast-<span class="searchmatch">table</span>&quot; series Volume 4 Publisher Boston, Jefferson Press
File:The professor at the breakfast table (IA professoratbreak00holmiala).pdf	professor at the breakfast <span class="searchmatch">table</span>   (  ) Author Holmes, Oliver Wendell, 1809-1894 Title The professor at the breakfast <span class="searchmatch">table</span> Publisher London : Chatto &amp;
File:The "Breakfast-table" series (IA breakfastseries03holmrich).pdf	The &quot;Breakfast-<span class="searchmatch">table</span>&quot; series   (  ) Author Holmes, Oliver Wendell, 1809-1894 Title The &quot;Breakfast-<span class="searchmatch">table</span>&quot; series Volume 3 Publisher Boston, Jefferson Press
File:The "Breakfast-table" series (IA breakfastseries02holmrich).pdf	The &quot;Breakfast-<span class="searchmatch">table</span>&quot; series   (  ) Author Holmes, Oliver Wendell, 1809-1894 Title The &quot;Breakfast-<span class="searchmatch">table</span>&quot; series Volume 2 Publisher Boston, Jefferson Press
File:The poet at the breakfast-table (IA poetbreakfasttab00holmiala).pdf	The poet at the breakfast-<span class="searchmatch">table</span>   (  ) Author Holmes, Oliver Wendell, 1809-1894 Title The poet at the breakfast-<span class="searchmatch">table</span> Publisher Houghton, Mifflin and
File:The Table book; (IA cu31924103708214).pdf	The <span class="searchmatch">Table</span> book;   (  ) Author Hone, William, 1780-1842 Wynne, Lewis Bingley. fmo St. John, Cynthia Morgan, 1852-1919. fmo Wordsworth Collection Title

=== church usher ===
File:St Columba's Usher Hall.png	1.0falsefalse English The laying of the foundation stone of the <span class="searchmatch">Usher</span> Hall, Edinburgh, in 1911, with St Columba&#039;s United Free <span class="searchmatch">Church</span> in the background
File:Ethel Watson Usher (1881-1967) obituary in the Portland Press Herald of Portland, Maine on September 16, 1967.jpg	Miss Ethel W. <span class="searchmatch">Usher</span>. Miss Ethel W. <span class="searchmatch">Usher</span> formerly of Portland a prominent pianist who once played personally for Prime Minister David Lloyd George at 10
File:Bazoline Usher (13269931405).jpg	DescriptionBazoline <span class="searchmatch">Usher</span> (13269931405).jpg English: Biography: Bazoline <span class="searchmatch">Usher</span> rose through the ranks of the Atlanta public school system to become supervisor
File:UFV Theatre Ushers (13475208983).jpg	DescriptionUFV Theatre <span class="searchmatch">Ushers</span> (13475208983).jpg English: Alumni Evening of Theater 2014 Date Taken on 21 March 2014, 19:07:48 Source https://www.flickr
File:A memorial sketch of Roland Greene Usher, 1823-1895 (IA memorialsketchof00usheiala).pdf	son) Description Subjects: <span class="searchmatch">Usher</span>, Roland Greene, 1823-1895; <span class="searchmatch">Usher</span> family (Hezekiah <span class="searchmatch">Usher</span>, 1615-1676); <span class="searchmatch">Usher</span> family (Robert <span class="searchmatch">Usher</span>, d. 1669) Language English
File:Usher collection tithe and offering.jpg	holder of this work, hereby publish it under the following license: English <span class="searchmatch">Usher</span> collection tithe and offering Bulawayo Zimbabwe determination method or
File:Second Baptist Church Usher Board - DPLA - 425f396e7e14105be82b430bbca1b8e1.jpg	Second Baptist <span class="searchmatch">Church</span> <span class="searchmatch">Usher</span> Board   (  ) Creator InfoField Pierce&#039;s Studio Title Second Baptist <span class="searchmatch">Church</span> <span class="searchmatch">Usher</span> Board Description Photograph of the Second
File:Usher uniform at Cinema Museum.jpg	Description<span class="searchmatch">Usher</span> uniform at Cinema Museum.jpg English: A cinema <span class="searchmatch">usher</span> uniform on display at the Cinema Museum. Date 11 October 2014, 13:47:23 Source Own
File:Pam Leath on Communion preparation Centrepoint Church 240 Hamilton Rd Chermside Centrepoint Church 240 Hamilton Rd Chermside P1080123.jpg	English Centrepoint <span class="searchmatch">Church</span> (formerly Chermside Assembly of God) is at 240 Hamilton Road. It is part of the Australian Christian <span class="searchmatch">Churches</span> network. author name
File:Communion distribution Centrepoint Church 240 Hamilton Rd Chermside P1080104.jpg	English Centrepoint <span class="searchmatch">Church</span> (formerly Chermside Assembly of God) is at 240 Hamilton Road. It is part of the Australian Christian <span class="searchmatch">Churches</span> network. author name

=== church volunteers entrance ===
File:Church of Saint John the Baptist (Sudice) Entrance Gate.jpg	Commons Attribution-Share Alike 4.0 truetrue English <span class="searchmatch">Church</span> of Saint John the Baptist (Sudice) <span class="searchmatch">Entrance</span> Gate Czech Vstupní brána ke kostelu svatého Jana Křtitele
File:Church of Saint John the Baptist (Sudice) Entrance Gate and Tomb.jpg	Commons Attribution-Share Alike 4.0 truetrue English <span class="searchmatch">Church</span> of Saint John the Baptist (Sudice) <span class="searchmatch">Entrance</span> Gate and Tomb Czech Vstupní brána a hrobka u kostela
File:St. Mary’s Church Entrance Door.tif	DescriptionSt. Mary’s <span class="searchmatch">Church</span> <span class="searchmatch">Entrance</span> Door.tif English: St. Mary&#039;s <span class="searchmatch">Church</span> is a historic Catholic <span class="searchmatch">church</span> in the eastern United States, at Fairfax Station
File:Church congregation at church entrance 1960s.tif	Description<span class="searchmatch">Church</span> congregation at <span class="searchmatch">church</span> <span class="searchmatch">entrance</span> 1960s.tif English: Chermside Assembly of God was established in 1922 at the corner of Hamilton Road and
File:St. Clare's Church entrance 1988 Stockholm.jpg	DescriptionSt. Clare&#039;s <span class="searchmatch">Church</span> <span class="searchmatch">entrance</span> 1988 Stockholm.jpg English: <span class="searchmatch">Entrance</span> to <span class="searchmatch">Church</span> of Saint Clare’s Klara kyrka, as released by image creator Ristesson
File:Church office and rear entrance, First Congregational United Church of Christ, Angola, New York - 20230402.jpg	Description<span class="searchmatch">Church</span> office and rear <span class="searchmatch">entrance</span>, First Congregational United <span class="searchmatch">Church</span> of Christ, Angola, New York - 20230402.jpg English: As seen on an April
File:ASC Leiden - Rietveld Collection - 20 - Entrance to the Church of the Good Shepherd - 2015.jpg	Description English: Robben Island. <span class="searchmatch">Entrance</span> to the <span class="searchmatch">Church</span> of the Good Shepherd on Robben Island. Nederlands: Ingang van de <span class="searchmatch">Church</span> of the Good Shepherd op Robben
File:History of the Fifteenth Regiment New Jersey Volunteers (IA cu31924030908358).pdf	Jersey <span class="searchmatch">Volunteers</span>   (  ) Author Haines, Alanson A. (Alanson Austin), 1830-1891 Title History of the Fifteenth Regiment New Jersey <span class="searchmatch">Volunteers</span> Publisher
File:Russia-Suzdal-Jerusalem Entrance Church.jpg	DescriptionRussia-Suzdal-Jerusalem <span class="searchmatch">Entrance</span> <span class="searchmatch">Church</span>.jpg English: Jerusalem <span class="searchmatch">Entrance</span> <span class="searchmatch">church</span>. Suzdal, Russia. Русский: Входо-Иерусалимская церковь. Суздаль
File:History of the Fifteenth Regiment New Jersey Volunteers (IA historyoffifteen00hain).pdf	Jersey <span class="searchmatch">Volunteers</span>   (  ) Author Haines, Alanson A. (Alanson Austin), 1830-1891 Title History of the Fifteenth Regiment New Jersey <span class="searchmatch">Volunteers</span> Publisher

 succeeded in 2518ms:
File:Caption- Otis greets an early comer at the church door. (7978065569).jpg	https://upload.wikimedia.org/wikipedia/commons/6/63/Caption-_Otis_greets_an_early_comer_at_the_church_door._%287978065569%29.jpg	No restrictions	<a rel="nofollow" class="external text" href="https://www.flickr.com/people/52529054@N06">Mennonite Church USA Archives</a>
File:Friends and relatives waiting to greet the newly weds on their emergence from church - geograph.org.uk - 2306144.jpg	https://upload.wikimedia.org/wikipedia/commons/b/bf/Friends_and_relatives_waiting_to_greet_the_newly_weds_on_their_emergence_from_church_-_geograph.org.uk_-_2306144.jpg	CC BY-SA 2.0	<a rel="nofollow" class="external text" href="https://www.geograph.org.uk/profile/7056">Eric Jones</a> <span class="mw-valign-text-top noprint" typeof="mw:File/Frameless"><a href="//commons.wikimedia.org/wiki/File:Friends_and_relatives_waiting_to_greet_the_newly_weds_on_their_emergence_from_church_-_geograph.org.uk_-_2306144.jpg#P170" title="Edit this at Structured Data on Commons"><img alt="Edit this at Structured Data on Commons" src="https://upload.wikimedia.org/wikipedia/commons/thumb/8/8a/OOjs_UI_icon_edit-ltr-progressive.svg/20px-OOjs_UI_icon_edit-ltr-progressive.svg.png" decoding="async" width="10" height="10" class="mw-file-element" data-file-width="20" data-file-height="20"></a></span>
File:Greeted by a saint - geograph.org.uk - 7901332.jpg	https://upload.wikimedia.org/wikipedia/commons/thumb/c/cc/Greeted_by_a_saint_-_geograph.org.uk_-_7901332.jpg/1280px-Greeted_by_a_saint_-_geograph.org.uk_-_7901332.jpg	CC BY-SA 2.0	<a rel="nofollow" class="external text" href="https://www.geograph.org.uk/profile/47623">Neil Owen</a> <span class="mw-valign-text-top noprint" typeof="mw:File/Frameless"><a href="//commons.wikimedia.org/wiki/File:Greeted_by_a_saint_-_geograph.org.uk_-_7901332.jpg#P170" title="Edit this at Structured Data on Commons"><img alt="Edit this at Structured Data on Commons" src="https://upload.wikimedia.org/wikipedia/commons/thumb/8/8a/OOjs_UI_icon_edit-ltr-progressive.svg/20px-OOjs_UI_icon_edit-ltr-progressive.svg.png" decoding="async" width="10" height="10" class="mw-file-element" data-file-width="20" data-file-height="20"></a></span>
File:Tin Tabernacle, Greet - geograph.org.uk - 195150.jpg	https://upload.wikimedia.org/wikipedia/commons/7/7a/Tin_Tabernacle%2C_Greet_-_geograph.org.uk_-_195150.jpg	CC BY-SA 2.0	<a rel="nofollow" class="external text" href="https://www.geograph.org.uk/profile/120">David Stowell</a>
File:War Memorial in Greete church - geograph.org.uk - 2532090.jpg	https://upload.wikimedia.org/wikipedia/commons/3/31/War_Memorial_in_Greete_church_-_geograph.org.uk_-_2532090.jpg	CC BY-SA 2.0	<a rel="nofollow" class="external text" href="https://www.geograph.org.uk/profile/1837">Philip Halling</a> <span class="mw-valign-text-top noprint" typeof="mw:File/Frameless"><a href="//commons.wikimedia.org/wiki/File:War_Memorial_in_Greete_church_-_geograph.org.uk_-_2532090.jpg#P170" title="Edit this at Structured Data on Commons"><img alt="Edit this at Structured Data on Commons" src="https://upload.wikimedia.org/wikipedia/commons/thumb/8/8a/OOjs_UI_icon_edit-ltr-progressive.svg/20px-OOjs_UI_icon_edit-ltr-progressive.svg.png" decoding="async" width="10" height="10" class="mw-file-element" data-file-width="20" data-file-height="20"></a></span>

=== church hospitality volunteers photo ===
File:Bishop Henry Benjamin Whipple - Crusader for Fair Treatment of Indians - Circa 1863.jpg	https://upload.wikimedia.org/wikipedia/commons/thumb/d/db/Bishop_Henry_Benjamin_Whipple_-_Crusader_for_Fair_Treatment_of_Indians_-_Circa_1863.jpg/1280px-Bishop_Henry_Benjamin_Whipple_-_Crusader_for_Fair_Treatment_of_Indians_-_Circa_1863.jpg	Public domain	Paul Taylor
File:Lending a helping hand, Marines and Sailors volunteer at local monastery 161206-M-ND733-254.jpg	https://upload.wikimedia.org/wikipedia/commons/thumb/4/4d/Lending_a_helping_hand%2C_Marines_and_Sailors_volunteer_at_local_monastery_161206-M-ND733-254.jpg/1280px-Lending_a_helping_hand%2C_Marines_and_Sailors_volunteer_at_local_monastery_161206-M-ND733-254.jpg	Public domain	Sgt. Jessika Braden
File:Our boys under fire, or, New Brunswick and Prince Edward Island volunteers in South Africa (microform) (IA cihm 10472).pdf	https://upload.wikimedia.org/wikipedia/commons/thumb/c/c0/Our_boys_under_fire%2C_or%2C_New_Brunswick_and_Prince_Edward_Island_volunteers_in_South_Africa_%28microform%29_%28IA_cihm_10472%29.pdf/page1-960px-Our_boys_under_fire%2C_or%2C_New_Brunswick_and_Prince_Edward_Island_volunteers_in_South_Africa_%28microform%29_%28IA_cihm_10472%29.pdf.jpg	Public domain	<div class="fn value">\nMellish, Annie Elizabeth</div>
File:The Detroit Light Guard - a complete record of this organization from its foundation to the present day - with full account of riot and complimentary duty, and the campaigns in the Civil and (14762730355).jpg	https://upload.wikimedia.org/wikipedia/commons/thumb/4/40/The_Detroit_Light_Guard_-_a_complete_record_of_this_organization_from_its_foundation_to_the_present_day_-_with_full_account_of_riot_and_complimentary_duty%2C_and_the_campaigns_in_the_Civil_and_%2814762730355%29.jpg/1280px-thumbnail.jpg	No restrictions	<a rel="nofollow" class="external text" href="https://www.flickr.com/people/126377022@N07">Internet Archive Book Images</a>
File:US Navy 070524-N-6525D-002 Electronic Technician Seaman Apprentice Christopher Clement, from Colorado Springs, Colo., a student at Naval Submarine School Groton, volunteers at The Holy Apostles Soup Kitchen.jpg	https://upload.wikimedia.org/wikipedia/commons/thumb/d/dc/US_Navy_070524-N-6525D-002_Electronic_Technician_Seaman_Apprentice_Christopher_Clement%2C_from_Colorado_Springs%2C_Colo.%2C_a_student_at_Naval_Submarine_School_Groton%2C_volunteers_at_The_Holy_Apostles_Soup_Kitchen.jpg/1280px-thumbnail.jpg	Public domain	U.S. Navy photo by Mass Communication Specialist 2nd Class Keith L. Darby

=== church ushers photo ===
File:Bazoline Usher (13269931405).jpg	https://upload.wikimedia.org/wikipedia/commons/thumb/0/04/Bazoline_Usher_%2813269931405%29.jpg/1280px-Bazoline_Usher_%2813269931405%29.jpg	No restrictions	<a rel="nofollow" class="external text" href="https://www.flickr.com/people/99902797@N03">Schlesinger Library, RIAS, Harvard University</a>
File:CQMS David Usher Leads the Cortege to the Garrison Church in the Curragh (4733218708).jpg	https://upload.wikimedia.org/wikipedia/commons/6/6c/CQMS_David_Usher_Leads_the_Cortege_to_the_Garrison_Church_in_the_Curragh_%284733218708%29.jpg	CC BY 2.0	<a rel="nofollow" class="external text" href="https://www.flickr.com/people/42787928@N06">Irish Defence Forces</a>
File:First Zion Missionary Baptist Church Reverend Fred Kitchen with ushers - Deerfield Beach (37885848525).jpg	https://upload.wikimedia.org/wikipedia/commons/6/6a/First_Zion_Missionary_Baptist_Church_Reverend_Fred_Kitchen_with_ushers_-_Deerfield_Beach_%2837885848525%29.jpg	No restrictions	<a rel="nofollow" class="external text" href="https://www.flickr.com/people/31846825@N04">Florida Memory</a>
File:The former St. James's Church, 121-122 St. James's Street, Dublin - geograph.org.uk - 2584521.jpg	https://upload.wikimedia.org/wikipedia/commons/6/65/The_former_St._James%27s_Church%2C_121-122_St._James%27s_Street%2C_Dublin_-_geograph.org.uk_-_2584521.jpg	CC BY-SA 2.0	<a rel="nofollow" class="external text" href="https://www.geograph.org.uk/profile/20846">P L Chadwick</a> <span class="mw-valign-text-top noprint" typeof="mw:File/Frameless"><a href="//commons.wikimedia.org/wiki/File:The_former_St._James%27s_Church,_121-122_St._James%27s_Street,_Dublin_-_geograph.org.uk_-_2584521.jpg#P170" title="Edit this at Structured Data on Commons"><img alt="Edit this at Structured Data on Commons" src="https://upload.wikimedia.org/wikipedia/commons/thumb/8/8a/OOjs_UI_icon_edit-ltr-progressive.svg/20px-OOjs_UI_icon_edit-ltr-progressive.svg.png" decoding="async" width="10" height="10" class="mw-file-element" data-file-width="20" data-file-height="20"></a></span>
File:The ushers of a negro church have their photograph taken to ... (3109751159).jpg	https://upload.wikimedia.org/wikipedia/commons/9/97/The_ushers_of_a_negro_church_have_their_photograph_taken_to_..._%283109751159%29.jpg	Public domain	<bdi><a href="https://en.wikipedia.org/wiki/en:Jack_Delano" class="extiw" title="w:en:Jack Delano"><span title="American photographer and composer (1914-1997)">Jack Delano</span></a></bdi>

exec
/bin/bash -lc "mkdir -p /home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/review-fix && cd /home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/review-fix && curl -L -o otis-greets.jpg 'https://upload.wikimedia.org/wikipedia/commons/6/63/Caption-_Otis_greets_an_early_comer_at_the_church_door._%287978065569%29.jpg' && file otis-greets.jpg && identify otis-greets.jpg 2>/dev/null || true" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "for title in 'File:Caption- Otis greets an early comer at the church door. (7978065569).jpg' 'File:Church congregation at church entrance 1960s.tif' 'File:Pam Leath on Communion preparation Centrepoint Church 240 Hamilton Rd Chermside Centrepoint Church 240 Hamilton Rd Chermside P1080123.jpg' 'File:Communion distribution Centrepoint Church 240 Hamilton Rd Chermside P1080104.jpg' 'File:Champion Forest Baptist Church greeter.jpg'; do printf '\\n=== %s ===\\n' \""'$title"; curl -sG '"'https://commons.wikimedia.org/w/api.php' --data-urlencode 'action=query' --data-urlencode 'prop=imageinfo' --data-urlencode \"titles="'$title" --data-urlencode '"'iiprop=url|extmetadata' --data-urlencode 'iiurlwidth=1600' --data-urlencode 'format=json' | jq -r '.query.pages[] | [.title, (.imageinfo[0].thumburl // .imageinfo[0].url // \"\"), (.imageinfo[0].extmetadata.LicenseShortName.value // \"\"), (.imageinfo[0].extmetadata.Artist.value // \"\"), (.imageinfo[0].extmetadata.ImageDescription.value // \"\")] | @tsv'; done" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "cd /home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/review-fix && curl -L -o church-entrance-1960s.tif 'https://upload.wikimedia.org/wikipedia/commons/0/03/Church_congregation_at_church_entrance_1960s.tif' && file church-entrance-1960s.tif && identify church-entrance-1960s.tif 2>/dev/null || true" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 313ms:
100 33262  100 33262    0     0  96432      0 --:--:-- --:--:-- --:--:-- 96691
otis-greets.jpg: JPEG image data, JFIF standard 1.01, resolution (DPI), density 200x200, segment length 16, Exif Standard: [TIFF image data, big-endian, direntries=6], baseline, precision 8, 179x233, components 3

 succeeded in 247ms:
100   115  100   115    0     0    417      0 --:--:-- --:--:-- --:--:--   416100   115  100   115    0     0    417      0 --:--:-- --:--:-- --:--:--   416
church-entrance-1960s.tif: ASCII text, with no line terminators

 exited 5 in 1561ms:
File:Caption- Otis greets an early comer at the church door. (7978065569).jpg	https://upload.wikimedia.org/wikipedia/commons/6/63/Caption-_Otis_greets_an_early_comer_at_the_church_door._%287978065569%29.jpg	No restrictions	<a rel="nofollow" class="external text" href="https://www.flickr.com/people/52529054@N06">Mennonite Church USA Archives</a>	Caption: Otis greets an early comer at the church door.<br>\nCitation: PAX Collection, 1945-2006. Isabel Gingrich Glanzer 1959 Scrapbook. HM1-927 Box 3 Folder 4 photo 63. Mennonite Church USA Archives - Goshen. Goshen, Indiana.

=== File:Church congregation at church entrance 1960s.tif ===
File:Church congregation at church entrance 1960s.tif	https://upload.wikimedia.org/wikipedia/commons/thumb/2/2d/Church_congregation_at_church_entrance_1960s.tif/lossy-page1-960px-Church_congregation_at_church_entrance_1960s.tif.jpg	CC BY-SA 4.0	<a href="//commons.wikimedia.org/wiki/User:John_Robert_McPherson" title="User:John Robert McPherson">John Robert McPherson</a>	Chermside Assembly of God was established in 1922 at the corner of Hamilton Road and Pfingst Road, <a href="https://en.wikipedia.org/wiki/Chermside,_Queensland" class="extiw" title="en:Chermside, Queensland">Chermside, Queensland</a>.  Meetings were held in a family home which was then located on the current church grounds until a church building was constructed by volunteers in 1947.

=== File:Pam Leath on Communion preparation Centrepoint Church 240 Hamilton Rd Chermside Centrepoint Church 240 Hamilton Rd Chermside P1080123.jpg ===
File:Pam Leath on Communion preparation Centrepoint Church 240 Hamilton Rd Chermside Centrepoint Church 240 Hamilton Rd Chermside P1080123.jpg	https://upload.wikimedia.org/wikipedia/commons/thumb/6/6d/Pam_Leath_on_Communion_preparation_Centrepoint_Church_240_Hamilton_Rd_Chermside_Centrepoint_Church_240_Hamilton_Rd_Chermside_P1080123.jpg/1920px-Pam_Leath_on_Communion_preparation_Centrepoint_Church_240_Hamilton_Rd_Chermside_Centrepoint_Church_240_Hamilton_Rd_Chermside_P1080123.jpg	CC BY-SA 4.0	<a href="//commons.wikimedia.org/wiki/User:John_Robert_McPherson" title="User:John Robert McPherson">John Robert McPherson</a>	Centrepoint Church (formerly Chermside Assembly of God) is at 240 Hamilton Road. It is part of the <a href="https://en.wikipedia.org/wiki/Australian_Christian_Churches" class="extiw" title="en:Australian Christian Churches">Australian Christian Churches</a> network.

=== File:Communion distribution Centrepoint Church 240 Hamilton Rd Chermside P1080104.jpg ===
jq: parse error: Invalid numeric literal at line 1, column 4

=== File:Champion Forest Baptist Church greeter.jpg ===
jq: parse error: Invalid numeric literal at line 1, column 4

codex
I found one clearly relevant Commons image already: a church greeter at the door. I’m still checking if there’s a stronger, higher-resolution candidate before I commit the swap, because I’d rather fix the review cleanly once than settle for a thin replacement.
exec
/bin/bash -lc "for q in 'Meet and Greet Centrepoint Church' 'Communion preparation Centrepoint Church' 'greets an early comer at the church door' 'church door greeting'; do printf '\\n=== %s ===\\n' \""'$q"; curl -sG '"'https://commons.wikimedia.org/w/api.php' --data-urlencode 'action=query' --data-urlencode 'generator=search' --data-urlencode \"gsrsearch="'$q" --data-urlencode '"'gsrnamespace=6' --data-urlencode 'gsrlimit=8' --data-urlencode 'prop=imageinfo' --data-urlencode 'iiprop=url|extmetadata' --data-urlencode 'iiurlwidth=1600' --data-urlencode 'format=json' | jq -r '.query.pages[]? | [.title, .imageinfo[0].thumburl, (.imageinfo[0].extmetadata.LicenseShortName.value // \"\"), (.imageinfo[0].extmetadata.ImageDescription.value // \"\")] | @tsv'; done" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "cd /home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/review-fix && curl -L -o pam-communion-prep.jpg 'https://upload.wikimedia.org/wikipedia/commons/thumb/6/6d/Pam_Leath_on_Communion_preparation_Centrepoint_Church_240_Hamilton_Rd_Chermside_Centrepoint_Church_240_Hamilton_Rd_Chermside_P1080123.jpg/1920px-Pam_Leath_on_Communion_preparation_Centrepoint_Church_240_Hamilton_Rd_Chermside_Centrepoint_Church_240_Hamilton_Rd_Chermside_P1080123.jpg' && file pam-communion-prep.jpg && identify pam-communion-prep.jpg 2>/dev/null || true" in /home/ubuntu/apps/ridgecrestchurch.com
 exited 5 in 732ms:
jq: parse error: Invalid numeric literal at line 1, column 4

=== Communion preparation Centrepoint Church ===
jq: parse error: Invalid numeric literal at line 1, column 4

=== greets an early comer at the church door ===
jq: parse error: Invalid numeric literal at line 1, column 4

=== church door greeting ===
jq: parse error: Invalid numeric literal at line 1, column 4

 succeeded in 2935ms:
  0     0    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0  0     0    0     0    0     0      0      0 --:--:--  0:00:02 --:--:--     0  0     0    0     0    0     0      0      0 --:--:--  0:00:02 --:--:--     0100 1092k  100 1092k    0     0   368k      0  0:00:02  0:00:02 --:--:--  367k
pam-communion-prep.jpg: JPEG image data, baseline, precision 8, 1920x2560, components 3

exec
/bin/bash -lc "for title in 'File:Meet and Greet Centrepoint Church 240 Hamilton Rd Chermside P1040039.jpg' 'File:Meet and Greet Centrepoint Church 240 Hamilton Rd Chermside P1040034.jpg' 'File:Meet and Greet Centrepoint Church 240 Hamilton Rd Chermside P1040038.jpg' 'File:Meet and Greet Centrepoint Church 240 Hamilton Rd Chermside P1040037.jpg'; do printf '\\n=== %s ===\\n' \""'$title"; curl -sG '"'https://commons.wikimedia.org/w/api.php' --data-urlencode 'action=query' --data-urlencode 'prop=imageinfo' --data-urlencode \"titles="'$title" --data-urlencode '"'iiprop=url|extmetadata' --data-urlencode 'iiurlwidth=1600' --data-urlencode 'format=json' | jq -r '.query.pages[] | [.title, (.imageinfo[0].thumburl // .imageinfo[0].url // \"\"), (.imageinfo[0].extmetadata.LicenseShortName.value // \"\"), (.imageinfo[0].extmetadata.ImageDescription.value // \"\")] | @tsv'; done" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "cd /home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/review-fix && for url in \\
'https://upload.wikimedia.org/wikipedia/commons/thumb/f/f3/Meet_and_Greet_Centrepoint_Church_240_Hamilton_Rd_Chermside_P1040039.jpg/1920px-Meet_and_Greet_Centrepoint_Church_240_Hamilton_Rd_Chermside_P1040039.jpg' \\
'https://upload.wikimedia.org/wikipedia/commons/thumb/2/26/Meet_and_Greet_Centrepoint_Church_240_Hamilton_Rd_Chermside_P1040034.jpg/1920px-Meet_and_Greet_Centrepoint_Church_240_Hamilton_Rd_Chermside_P1040034.jpg' \\
'https://upload.wikimedia.org/wikipedia/commons/thumb/8/84/Meet_and_Greet_Centrepoint_Church_240_Hamilton_Rd_Chermside_P1040038.jpg/1920px-Meet_and_Greet_Centrepoint_Church_240_Hamilton_Rd_Chermside_P1040038.jpg' \\
'https://upload.wikimedia.org/wikipedia/commons/thumb/3/31/Meet_and_Greet_Centrepoint_Church_240_Hamilton_Rd_Chermside_P1040037.jpg/1920px-Meet_and_Greet_Centrepoint_Church_240_Hamilton_Rd_Chermside_P1040037.jpg'; do f="'$(basename "$url"); curl -L -A '"'Mozilla/5.0' -o \""'$f" "$url"; file "$f"; done' in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 1303ms:
jq: parse error: Invalid numeric literal at line 1, column 4

=== File:Meet and Greet Centrepoint Church 240 Hamilton Rd Chermside P1040034.jpg ===
jq: parse error: Invalid numeric literal at line 1, column 4

=== File:Meet and Greet Centrepoint Church 240 Hamilton Rd Chermside P1040038.jpg ===
File:Meet and Greet Centrepoint Church 240 Hamilton Rd Chermside P1040038.jpg	https://upload.wikimedia.org/wikipedia/commons/thumb/8/87/Meet_and_Greet_Centrepoint_Church_240_Hamilton_Rd_Chermside_P1040038.jpg/1920px-Meet_and_Greet_Centrepoint_Church_240_Hamilton_Rd_Chermside_P1040038.jpg	CC BY-SA 4.0	Centrepoint Church (formerly Chermside Assembly of God) is at 240 Hamilton Road. It is part of the <a href="https://en.wikipedia.org/wiki/Australian_Christian_Churches" class="extiw" title="en:Australian Christian Churches">Australian Christian Churches</a> network.

=== File:Meet and Greet Centrepoint Church 240 Hamilton Rd Chermside P1040037.jpg ===
File:Meet and Greet Centrepoint Church 240 Hamilton Rd Chermside P1040037.jpg	https://upload.wikimedia.org/wikipedia/commons/thumb/a/a9/Meet_and_Greet_Centrepoint_Church_240_Hamilton_Rd_Chermside_P1040037.jpg/1920px-Meet_and_Greet_Centrepoint_Church_240_Hamilton_Rd_Chermside_P1040037.jpg	CC BY-SA 4.0	Centrepoint Church (formerly Chermside Assembly of God) is at 240 Hamilton Road. It is part of the <a href="https://en.wikipedia.org/wiki/Australian_Christian_Churches" class="extiw" title="en:Australian Christian Churches">Australian Christian Churches</a> network.

 succeeded in 1880ms:
100  1929  100  1929    0     0   4333      0 --:--:-- --:--:-- --:--:--  4325100  1929  100  1929    0     0   4332      0 --:--:-- --:--:-- --:--:--  4325
1920px-Meet_and_Greet_Centrepoint_Church_240_Hamilton_Rd_Chermside_P1040039.jpg: HTML document, ASCII text, with very long lines (403)
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0100  1929  100  1929    0     0   3693      0 --:--:-- --:--:-- --:--:--  3695
1920px-Meet_and_Greet_Centrepoint_Church_240_Hamilton_Rd_Chermside_P1040034.jpg: HTML document, ASCII text, with very long lines (403)
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0100  1929  100  1929    0     0   4534      0 --:--:-- --:--:-- --:--:--  4528100  1929  100  1929    0     0   4533      0 --:--:-- --:--:-- --:--:--  4528
1920px-Meet_and_Greet_Centrepoint_Church_240_Hamilton_Rd_Chermside_P1040038.jpg: HTML document, ASCII text, with very long lines (403)
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0100  1929  100  1929    0     0   4101      0 --:--:-- --:--:-- --:--:--  4104
1920px-Meet_and_Greet_Centrepoint_Church_240_Hamilton_Rd_Chermside_P1040037.jpg: HTML document, ASCII text, with very long lines (403)

exec
/bin/bash -lc "curl -sG 'https://commons.wikimedia.org/w/api.php' --data-urlencode 'action=query' --data-urlencode 'prop=imageinfo' --data-urlencode 'titles=File:Meet and Greet Centrepoint Church 240 Hamilton Rd Chermside P1040038.jpg' --data-urlencode 'iiprop=url|extmetadata' --data-urlencode 'iiurlwidth=1600' --data-urlencode 'format=json'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 187ms:
{"batchcomplete":"","query":{"pages":{"118786501":{"pageid":118786501,"ns":6,"title":"File:Meet and Greet Centrepoint Church 240 Hamilton Rd Chermside P1040038.jpg","imagerepository":"local","imageinfo":[{"thumburl":"https://upload.wikimedia.org/wikipedia/commons/thumb/8/87/Meet_and_Greet_Centrepoint_Church_240_Hamilton_Rd_Chermside_P1040038.jpg/1920px-Meet_and_Greet_Centrepoint_Church_240_Hamilton_Rd_Chermside_P1040038.jpg","thumbwidth":1600,"thumbheight":1200,"responsiveUrls":{"2":"https://upload.wikimedia.org/wikipedia/commons/thumb/8/87/Meet_and_Greet_Centrepoint_Church_240_Hamilton_Rd_Chermside_P1040038.jpg/3840px-Meet_and_Greet_Centrepoint_Church_240_Hamilton_Rd_Chermside_P1040038.jpg"},"url":"https://upload.wikimedia.org/wikipedia/commons/8/87/Meet_and_Greet_Centrepoint_Church_240_Hamilton_Rd_Chermside_P1040038.jpg","descriptionurl":"https://commons.wikimedia.org/wiki/File:Meet_and_Greet_Centrepoint_Church_240_Hamilton_Rd_Chermside_P1040038.jpg","descriptionshorturl":"https://commons.wikimedia.org/w/index.php?curid=118786501","extmetadata":{"DateTime":{"value":"2022-06-05 10:36:50","source":"mediawiki-metadata","hidden":""},"ObjectName":{"value":"Meet and Greet Centrepoint Church 240 Hamilton Rd Chermside P1040038","source":"mediawiki-metadata"},"CommonsMetadataExtension":{"value":1.2,"source":"extension","hidden":""},"Categories":{"value":"Self-published work|Centrepoint Church services","source":"commons-categories","hidden":""},"Assessments":{"value":"","source":"commons-categories","hidden":""},"ImageDescription":{"value":"Centrepoint Church (formerly Chermside Assembly of God) is at 240 Hamilton Road. It is part of the <a href=\"https://en.wikipedia.org/wiki/Australian_Christian_Churches\" class=\"extiw\" title=\"en:Australian Christian Churches\">Australian Christian Churches</a> network.","source":"commons-desc-page"},"DateTimeOriginal":{"value":"2014-01-19 09:47:56","source":"commons-desc-page"},"Credit":{"value":"<span class=\"int-own-work\" lang=\"en\">Own work</span>","source":"commons-desc-page"},"Artist":{"value":"<a href=\"//commons.wikimedia.org/wiki/User:John_Robert_McPherson\" title=\"User:John Robert McPherson\">John Robert McPherson</a>","source":"commons-desc-page"},"LicenseShortName":{"value":"CC BY-SA 4.0","source":"commons-desc-page","hidden":""},"UsageTerms":{"value":"Creative Commons Attribution-Share Alike 4.0","source":"commons-desc-page"},"AttributionRequired":{"value":"true","source":"commons-desc-page","hidden":""},"LicenseUrl":{"value":"https://creativecommons.org/licenses/by-sa/4.0","source":"commons-desc-page"},"Copyrighted":{"value":"True","source":"commons-desc-page","hidden":""},"Restrictions":{"value":"","source":"commons-desc-page","hidden":""},"License":{"value":"cc-by-sa-4.0","source":"commons-templates","hidden":""}}}]}}}}
exec
/bin/bash -lc "cd /home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/review-fix && curl -L -A 'Mozilla/5.0' -o meet-greet-0038.jpg 'https://upload.wikimedia.org/wikipedia/commons/thumb/8/87/Meet_and_Greet_Centrepoint_Church_240_Hamilton_Rd_Chermside_P1040038.jpg/1920px-Meet_and_Greet_Centrepoint_Church_240_Hamilton_Rd_Chermside_P1040038.jpg' && file meet-greet-0038.jpg && identify meet-greet-0038.jpg 2>/dev/null || true" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 2970ms:
  0     0    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0  0     0    0     0    0     0      0      0 --:--:--  0:00:02 --:--:--     0 28  725k   28  207k    0     0  73136      0  0:00:10  0:00:02  0:00:08 73120100  725k  100  725k    0     0   241k      0  0:00:03  0:00:03 --:--:--  241k
meet-greet-0038.jpg: JPEG image data, baseline, precision 8, 1920x1440, components 3

codex
I have a stronger replacement now: a rights-safe, high-resolution meet-and-greet church photo that matches the article’s Sunday-team angle much better than the generic worship shot. I’m importing it into the media library, swapping the inline figure and featured image, and then I’ll verify the public post HTML.
exec
/bin/bash -lc "wp media import wp-content/uploads/imports/review-fix/meet-greet-0038.jpg --title='Sunday Meet and Greet Volunteers' --alt='Church volunteers welcoming and greeting attendees before a Sunday service' --porcelain" in /home/ubuntu/apps/ridgecrestchurch.com
 exited 1 in 615ms:
Error: No support for generating images found. Please install the Imagick or GD PHP extensions.

exec
/bin/bash -lc "wp option get page_for_posts && printf '\\nBLOG_URL: ' && wp post url "'$(wp option get page_for_posts)' in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 1594ms:
23

BLOG_URL: https://ridgecrestchurch.com/blog/

codex
`wp media import` is blocked here by missing image-processing extensions, which the site instructions anticipated. I’m registering the downloaded file as a WordPress attachment manually instead, then I’ll attach it to the post and verify the rendered HTML.
exec
/bin/bash -lc "wp eval '
"'$path = ABSPATH . "wp-content/uploads/imports/review-fix/meet-greet-0038.jpg";
$url = site_url("/wp-content/uploads/imports/review-fix/meet-greet-0038.jpg");
$post_id = 113;
$existing = attachment_url_to_postid($url);
if ($existing) { echo $existing; return; }
$filetype = wp_check_filetype(basename($path), null);
$attachment = array(
  "guid" => $url,
  "post_mime_type" => $filetype["type"],
  "post_title" => "Sunday Meet and Greet Volunteers",
  "post_content" => "",
  "post_status" => "inherit",
  "post_parent" => $post_id,
);
$attach_id = wp_insert_attachment($attachment, $path, $post_id);
if (is_wp_error($attach_id)) { fwrite(STDERR, $attach_id->get_error_message()); exit(1); }
update_post_meta($attach_id, "_wp_attached_file", "imports/review-fix/meet-greet-0038.jpg");
update_post_meta($attach_id, "_wp_attachment_image_alt", "Church volunteers welcoming and greeting attendees before a Sunday service");
echo $attach_id;
'"'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 583ms:
114
exec
/bin/bash -lc "wp post get 113 --field=post_author && printf '\\n' && wp user get "'$(wp post get 113 --field=post_author) --fields=ID,user_login,display_name --format=table' in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 1720ms:
7

Field	Value
ID	7
user_login	nora-finch
display_name	Nora Finch

codex
I’ve registered the replacement image as attachment `114`. The remaining step is a clean content swap: replace the first figure block, set the new featured image, and then confirm the live article is using `wp-image-114` in the body.
exec
/bin/bash -lc "wp eval '
"'$post_id = 113;
$post = get_post($post_id);
$content = $post->post_content;
$new = <<<'"'HTML'
<figure class=\"wp-block-image size-large\">
  <img src=\"https://ridgecrestchurch.com/wp-content/uploads/imports/review-fix/meet-greet-0038.jpg\" alt=\"Church volunteers welcoming and greeting attendees before a Sunday service\" class=\"wp-image-114\" />
  <figcaption>A Sunday meet-and-greet scene shows the kind of welcome and conversation Sunday teams help create. Photo by John Robert McPherson via Wikimedia Commons, used under CC BY-SA 4.0.</figcaption>
</figure>
HTML;
"'$updated = preg_replace('"'/<figure class=\"wp-block-image size-large\">.*?<\\/figure>/s', "'$new, $content, 1, $count);
if ($count !== 1) { fwrite(STDERR, "Figure replacement failed'"\\n\"); exit(1); }
wp_update_post(array('ID' => "'$post_id, '"'post_content' => "'$updated));
set_post_thumbnail($post_id, 114);
echo "updated";
'"'" in /home/ubuntu/apps/ridgecrestchurch.com
 exited 1 in 0ms:
/bin/bash: line 1: figure: No such file or directory

exec
/bin/bash -lc "wp post meta get 114 _wp_attachment_image_alt && printf '\\nATTACH_URL: ' && wp eval 'echo wp_get_attachment_url(114);'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 1044ms:
Church volunteers welcoming and greeting attendees before a Sunday service

ATTACH_URL: https://ridgecrestchurch.com/wp-content/uploads/imports/review-fix/meet-greet-0038.jpg
codex
The first content update tripped over shell quoting, not WordPress. I’m rerunning the swap with a simpler `wp eval` payload and then I’ll verify the post body, featured image, and public HTML together.
exec
/bin/bash -lc "wp eval '"'$post_id=113; $post=get_post($post_id); $content=$post->post_content; $new="<figure class='"\\\"wp-block-image size-large\\\">\\n  <img src=\\\"https://ridgecrestchurch.com/wp-content/uploads/imports/review-fix/meet-greet-0038.jpg\\\" alt=\\\"Church volunteers welcoming and greeting attendees before a Sunday service\\\" class=\\\"wp-image-114\\\" />\\n  <figcaption>A Sunday meet-and-greet scene shows the kind of welcome and conversation Sunday teams help create. Photo by John Robert McPherson via Wikimedia Commons, used under CC BY-SA 4.0.</figcaption>\\n</figure>\"; "'$updated=preg_replace("/<figure class='"\\\"wp-block-image size-large\\\">.*?<\\\\/figure>/s\", "'$new, $content, 1, $count); if ($count !== 1) { fwrite(STDERR, "Figure replacement failed'"\\n\"); exit(1); } wp_update_post(array(\"ID\"=>"'$post_id,"post_content"=>$updated)); set_post_thumbnail($post_id, 114); echo "updated";'"'" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "wp post get 113 --field=post_content | sed -n '1,40p'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 531ms:
<p><strong><em>A welcoming Sunday rarely happens by accident. It usually happens because a few steady people are paying attention before you ever wonder where to sit, where your child should go, or whether it is okay to ask for help.</em></strong></p>

<p>If you have ever walked into a church and thought, “Do I just follow the crowd?” or “Who do I ask without feeling awkward?” this is the plain version first. At Ridgecrest Baptist Church, Sunday teams help remove little points of friction so worshippers can focus on the service instead of guessing their way through the morning.</p>

<p>This article gives a quick map of what greeters, ushers, and hospitality volunteers typically do, how families can find the right help, and what to do if you want to serve alongside them. If you want the bigger picture of the church’s mission, the <a href="https://ridgecrestchurch.com/about-us/">About Us page</a> is a good next stop. If you mainly want the “where do I go this Sunday?” version, keep reading.</p>

<figure class="wp-block-image size-large">
  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/review-fix/meet-greet-0038.jpg" alt="Church volunteers welcoming and greeting attendees before a Sunday service" class="wp-image-114" />
  <figcaption>A Sunday meet-and-greet scene shows the kind of welcome and conversation Sunday teams help create. Photo by John Robert McPherson via Wikimedia Commons, used under CC BY-SA 4.0.</figcaption>
</figure>

<h2>Why Sunday teams matter</h2>

<p>Sunday service teams do not exist to make the morning feel polished for its own sake. They exist to make the church easier to enter, easier to navigate, and easier to participate in. That matters for first-time guests, long-time members, parents carrying three things too many, and anyone who arrives needing a little extra guidance.</p>

<p>Ridgecrest’s <a href="https://ridgecrestchurch.com/">home page</a> and <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> help with the schedule ahead of time, but people still need in-person help once they arrive. That is where Sunday teams become visible in the best way: not as a performance, but as a calm presence.</p>

<p>That kind of welcome lines up with the spirit of <a href="https://www.biblegateway.com/passage/?search=Romans%2015%3A7&amp;version=NIV&amp;utm_source=ridgecrestchurch.com">Romans 15:7</a>, which points believers toward receiving one another with the same grace they have received. The short answer is simple: a church feels warmer when people are intentionally looking out for one another.</p>

<h2>Greeters: what to expect at the door</h2>

<p>Greeters are often the first faces you meet on a Sunday morning. Their job is not to corner anyone into a long conversation before coffee has done its work. Their job is to notice people, offer a welcome, and help newcomers take the next obvious step.</p>

<p>That can look very ordinary, which is usually a good sign. A greeter may point you toward the main entrance, answer a quick question about where to go, help you find the sanctuary, or direct you to the right page if you want details later on. If you are new, a greeter can also help you connect with the right ministry area, including the broader opportunities listed on the <a href="https://ridgecrestchurch.com/ministries/">Ministries page</a>.</p>

<p>For families, this first contact matters even more. A calm welcome at the door can save parents from the classic Sunday question: “Are we confidently walking in the right direction, or just walking briskly and hoping for the best?” If you have children with you, a greeter can usually point you toward the right next step and help you reach the church’s <a href="https://ridgecrestchurch.com/kids/">Kids ministry information</a> without making the morning feel complicated.</p>

<h2>Ushers: seating help, accessibility, and practical support</h2>

<p>Once you are inside, ushers help the room make sense. They assist with seating, help people find open spots, answer practical questions, and watch for needs that are easy to miss if everyone assumes someone else will handle them.</p>

<p>If you arrive late, are unsure where to sit, or need help finding a good place for your family, an usher is one of the best people to ask. Ushers can also be a helpful contact if you need directions to restrooms, classrooms, or the best path through the building. The goal is not formality. The goal is lowering the stress level by one or two clicks.</p>

<p>This also includes accessibility awareness. Someone may need a little more room, a simpler route, extra time getting seated, or help locating the most comfortable place to sit. Even when the request feels small, asking matters. An usher would generally rather help early than have someone spend the whole service quietly uncomfortable.</p>

<p>For anyone planning ahead, the <a href="https://ridgecrestchurch.com/contacts/">Contacts page</a> and <a href="https://ridgecrestchurch.com/resources/">Resources page</a> are useful places to start before Sunday. They make it easier to ask questions in advance rather than improvising once you are in the parking lot.</p>

<h2>Hospitality and communication: the people behind the smooth parts</h2>

<p>Hospitality is the broader layer that helps Sunday feel coordinated instead of scattered. This often includes welcome materials, answering basic questions, helping visitors know where to go next, and making sure people know where to look for current information.</p>

exec
/bin/bash -lc 'wp post meta get 113 _thumbnail_id' in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 821ms:
updated
 succeeded in 532ms:
114

codex
The database update is done. I’m on the verification pass now: attachment record, post metadata, direct URL response, inline image presence in stored content, and a quick `/blog/` check so the final report is based on what the site is actually serving.
exec
/bin/bash -lc "wp post get 113 --fields=ID,post_title,post_name,post_status,post_author --format=table && printf '\\nPOST_URL: ' && wp post url 113 && printf '\\nATTACHMENT:\\n' && wp post get 114 --fields=ID,post_title,post_status,post_mime_type,guid --format=table" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "curl -I -L https://ridgecrestchurch.com/ministry-spotlight-sunday-teams/ && printf '\\n--- BODY CHECK ---\\n' && curl -L https://ridgecrestchurch.com/ministry-spotlight-sunday-teams/ | rg -n 'wp-image-114|meet-greet-0038|Church volunteers welcoming and greeting attendees before a Sunday service|A Sunday meet-and-greet scene'" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "printf 'BLOG_PAGE_FOR_POSTS: '; wp option get page_for_posts && printf '\\nBLOG_HTTP:\\n' && curl -I -L https://ridgecrestchurch.com/blog/ && printf '\\n--- BLOG LINKS ---\\n' && curl -L https://ridgecrestchurch.com/blog/ | rg -n 'ministry-spotlight-sunday-teams|How Our Teams Serve on Sundays' | head" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 1190ms:
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
HTTP/2 200 
date: Sat, 20 Jun 2026 19:09:57 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/113>; rel="alternate"; title="JSON"; type="application/json", <https://ridgecrestchurch.com/?p=113>; 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=nowL45d8T03zLBndcAllkgQxeZdGzImtz1wOH8ecL%2FRSFiSUKZIagkwIKp7vBjFfnnOEq6WP7Ob98pDNQsP67yCxO28S7nWt5gBvC2u1bnbjsDnCthzkQz0sKXFZCPt4lJIymOaGBw%3D%3D"}]}
nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
cf-ray: a0ed121eda730178-WAW
alt-svc: h3=":443"; ma=86400


--- BODY CHECK ---
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0100 49440    0 49440    0     0  78374      0 --:--:-- --:--:-- --:--:-- 78476
33:	<script type="application/ld+json" class="yoast-schema-graph">{"@context":"https://schema.org","@graph":[{"@type":"Article","@id":"https://ridgecrestchurch.com/ministry-spotlight-sunday-teams/#article","isPartOf":{"@id":"https://ridgecrestchurch.com/ministry-spotlight-sunday-teams/"},"author":{"name":"Nora Finch","@id":"https://ridgecrestchurch.com/#/schema/person/4ded5caa8fe5cd34fc5623da1de8cdd8"},"headline":"Ministry Spotlight: How Our Teams Serve on Sundays (Greeters, Ushers, and Hospitality)","datePublished":"2026-06-20T19:06:44+00:00","dateModified":"2026-06-20T19:09:50+00:00","mainEntityOfPage":{"@id":"https://ridgecrestchurch.com/ministry-spotlight-sunday-teams/"},"wordCount":1698,"publisher":{"@id":"https://ridgecrestchurch.com/#organization"},"image":{"@id":"https://ridgecrestchurch.com/ministry-spotlight-sunday-teams/#primaryimage"},"thumbnailUrl":"https://ridgecrestchurch.com/wp-content/uploads/imports/review-fix/meet-greet-0038.jpg","inLanguage":"en-US"},{"@type":"WebPage","@id":"https://ridgecrestchurch.com/ministry-spotlight-sunday-teams/","url":"https://ridgecrestchurch.com/ministry-spotlight-sunday-teams/","name":"Ministry Spotlight: How Our Teams Serve on Sundays (Greeters, Ushers, and Hospitality) - Ridgecrest Baptist Church","isPartOf":{"@id":"https://ridgecrestchurch.com/#website"},"primaryImageOfPage":{"@id":"https://ridgecrestchurch.com/ministry-spotlight-sunday-teams/#primaryimage"},"image":{"@id":"https://ridgecrestchurch.com/ministry-spotlight-sunday-teams/#primaryimage"},"thumbnailUrl":"https://ridgecrestchurch.com/wp-content/uploads/imports/review-fix/meet-greet-0038.jpg","datePublished":"2026-06-20T19:06:44+00:00","dateModified":"2026-06-20T19:09:50+00:00","description":"Discover how Sunday service teams at Ridgecrest Baptist Church support worship through greeting, seating, hospitality, and practical help for guests and families.","breadcrumb":{"@id":"https://ridgecrestchurch.com/ministry-spotlight-sunday-teams/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https://ridgecrestchurch.com/ministry-spotlight-sunday-teams/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https://ridgecrestchurch.com/ministry-spotlight-sunday-teams/#primaryimage","url":"https://ridgecrestchurch.com/wp-content/uploads/imports/review-fix/meet-greet-0038.jpg","contentUrl":"https://ridgecrestchurch.com/wp-content/uploads/imports/review-fix/meet-greet-0038.jpg","caption":"Church volunteers welcoming and greeting attendees before a Sunday service"},{"@type":"BreadcrumbList","@id":"https://ridgecrestchurch.com/ministry-spotlight-sunday-teams/#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":"Ministry Spotlight: How Our Teams Serve on Sundays (Greeters, Ushers, and Hospitality)"}]},{"@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/4ded5caa8fe5cd34fc5623da1de8cdd8","name":"Nora Finch","description":"Nora turns unfamiliar topics into approachable guides, definitions, and resource articles for readers who want the plain version first.","url":"https://ridgecrestchurch.com/author/nora-finch/"}]}</script>
433:  <img decoding="async" data-src="https://ridgecrestchurch.com/wp-content/uploads/imports/review-fix/meet-greet-0038.jpg" alt="Church volunteers welcoming and greeting attendees before a Sunday service" class="wp-image-114 lazyload" src="data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==" style="--smush-placeholder-width: 1920px; --smush-placeholder-aspect-ratio: 1920/1440;" /><figcaption>A Sunday meet-and-greet scene shows the kind of welcome and conversation Sunday teams help create. Photo by John Robert McPherson via Wikimedia Commons, used under CC BY-SA 4.0.</figcaption></figure>

 succeeded in 1730ms:
Field	Value
ID	113
post_author	7
post_title	Ministry Spotlight: How Our Teams Serve on Sundays (Greeters, Ushers, and Hospitality)
post_status	publish
post_name	ministry-spotlight-sunday-teams

POST_URL: https://ridgecrestchurch.com/ministry-spotlight-sunday-teams/

ATTACHMENT:
Field	Value
ID	114
post_title	Sunday Meet and Greet Volunteers
post_status	inherit
guid	https://ridgecrestchurch.com/wp-content/uploads/imports/review-fix/meet-greet-0038.jpg
post_mime_type	image/jpeg

 succeeded in 1706ms:
23

BLOG_HTTP:
  % 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     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
HTTP/2 200 
date: Sat, 20 Jun 2026 19:09:58 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=ivF7cVMkie68%2F1G4a4Gn3%2FCAyn9zZqcXuHC4MgoLHalBIafbO2gExrzK4B8LOqnYL5jp%2B1H2gQsy3NTTYROwyCPMoVOZStjcXhE3bP37k%2F8tGY4CTdK6xuGYRRLehSTcxptCQFNN7w%3D%3D"}]}
nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
cf-ray: a0ed1225ebc83560-WAW
alt-svc: h3=":443"; ma=86400


--- BLOG LINKS ---
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0100 52264    0 52264    0     0  86407      0 --:--:-- --:--:-- --:--:-- 86529
414:			<header class="entry-header">	<h2 class="entry-title" itemprop="headline"><a href="https://ridgecrestchurch.com/ministry-spotlight-sunday-teams/" rel="bookmark">Ministry Spotlight: How Our Teams Serve on Sundays (Greeters, Ushers, and Hospitality)</a></h2>
420:<a href="https://ridgecrestchurch.com/ministry-spotlight-sunday-teams/" title="Ministry Spotlight: How Our Teams Serve on Sundays (Greeters, Ushers, and Hospitality)"><img data-src="https://ridgecrestchurch.com/wp-content/uploads/imports/review-fix/meet-greet-0038.jpg" class="wp-post-image lazyload" alt="Church volunteers welcoming and greeting attendees before a Sunday service" decoding="async" itemprop="image" src="data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==" style="--smush-placeholder-width: 1920px; --smush-placeholder-aspect-ratio: 1920/1440;" /></a><p>Discover how Sunday service teams at Ridgecrest Baptist Church support worship through greeting, seating, hospitality, and practical help for guests and families.</p>

codex
I updated post `113` by replacing the generic worship photo with a more relevant, rights-safe church meet-and-greet image and set that same attachment as the featured image. The article body otherwise stayed intact. Because this WordPress install lacks GD/Imagick, I registered the image manually as attachment `114` instead of using `wp media import`.

I verified the post record, public URL, featured image meta, inline `wp-image-114` figure in `post_content`, live HTML on the article page, and the `/blog/` index entry. Flatlogic/AppWizzy links were not used. Backlink restoration target `/` was unchanged and not part of this fix.

Remaining risk: the attachment is serving correctly now, but because no image metadata/intermediate sizes were generated, the theme is using the original uploaded file path directly.

WP_POST_ID: 113
WP_POST_STATUS: publish
WP_POST_URL: https://ridgecrestchurch.com/ministry-spotlight-sunday-teams/
WP_AUTHOR_USER: nora-finch / Nora Finch
FEATURED_IMAGE_ID: 114
INLINE_IMAGE_IDS: 114
BLOG_INDEX_STATUS: ready; https://ridgecrestchurch.com/blog/ returns 200 and page_for_posts=23
LINK_TARGETS_USED: none
tokens used
231,275
