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: 019e5b24-f52a-77e1-8907-a99d30ef43af
--------
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-101/task.md
Iteration: 0

<primary_instructions>
# Article Generation Task

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

## Required Runtime

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

## Site Contract

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

## Backlink Targets To Respect

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

## Required Flatlogic/AppWizzy Body Link Target

1. https://flatlogic.com/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
2. https://flatlogic.com/services/ai-consulting-services?utm_source=ridgecrestchurch.com
   Title: AI Consulting Services | Artificial Intelligence Consulting for Business
   Priority: 1
   Anchor guidance: link to this page as "AI consulting, AI consulting services, AI adoption for business, AI Development Services, AI Integration Services, etc"
3. https://appwizzy.com/
   Title: AppWizzy - Build Web Apps and Websites with AI
   Priority: 1
   Anchor guidance: Link to this page as "vibe coding tool", "vibe coding platform", "rent VM with Codex", "generate app with AI"
4. https://flatlogic.com/services/custom-web-development-services?utm_source=ridgecrestchurch.com
   Title: Custom Web Development Services | Flatlogic
   Priority: 0.9
   Anchor guidance: include either as: "custom web development services", "web development services", "web app development services" "web app development company", etc
5. https://flatlogic.com/starting-web-app-in-2025-research-results?utm_source=ridgecrestchurch.com
   Title: Web App Development Trends 2025: Research Results
   Priority: 0.83
   Anchor guidance: Best internal link anchors Use these as anchors from blog posts, comparison pages, AI generator pages, and research pages: Primary anchors — best overall web app development trends 2025 2025 web app development research how people start web apps in 2025 AI web app development research Flatlogic web app research 2025 AI / vibe-coding focused anchors AI app generators research vibe-coding tools research AI-powered web app generators AI-generated codebase trends vibe-coding adoption in 2025 Low-code / no-code anchors low-code no-code trends 2025 low-code vs AI app generators low-code no-code web app research web app builder trends AI and low-code development trends Framework / technology anchors popular web development frameworks in 2025 React and Node.js trends web development technology trends frontend and backend framework research cloud platform trends for web apps Natural contextual anchors our latest research on starting web apps the 2025 Flatlogic research this year’s web app research results our annual web development survey the full 2025 research results

Link placement requirement:

- Include at least one of the exact URLs above as a visitor-facing contextual body link inside the article content.
- Prefer the most relevant target for the article topic. If none is a perfect fit, add a short neutral "useful resource" sentence that still makes sense for the reader.
- Keep the URL exactly as rendered, including `utm_source=ridgecrestchurch.com` for Flatlogic URLs.
- Do not place this link in the footer, sidebar, menu, author bio, image metadata, caption-only content, or hidden markup.
- Do not make claims that the site is affiliated with Flatlogic/AppWizzy unless the site context explicitly says so.
- Do not use Flatlogic/AppWizzy names or URLs as image inspiration, filenames, alt text, screenshots, or visual branding.

## Article Request

- Topic: How to Prepare for a Youth or Kids Wednesday Night Program
- 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 96 as the source of truth. Prepared article brief: Working title: How to Prepare for a Youth or Kids Wednesday Night Program
Slug hint: prepare-for-wednesday-kids-youth
Meta description: A practical, step-by-step checklist for families preparing for Ridgecrest’s Wednesday Night Kids or Youth programs—what to bring, arrival and check-in tips, what happens during the

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.

Thesis:
Wednesday Night goes smoother when families prepare in advance: confirm the latest details, bring the right essentials, arrive early enough to check in, understand what the program time looks like, and follow clear pickup and communication steps—especially if it’s your first week.

Writer brief:
Write an evergreen, family-focused preparation guide for Ridgecrest Baptist Church’s Wednesday Night Kids and Youth programs. Keep it practical and non-commercial. The article should function like a checklist + “what to expect” walkthrough, with clear sections for before arrival, arrival/check-in, during the program (high-level), communication, pickup, allergies/accessibility, and first-time tips. Use the site’s existing navigation pages as internal links (Events Calendar, News, Contacts, About, Kids, Youth). Avoid duplicating any existing “first-timer’s guide” or “events calendar how-to” content; instead, focus specifically on preparation steps for Wednesday Night programs. Where details could vary by week (time, location, special instructions), instruct readers to verify on the Events Calendar and News pages rather than asserting fixed logistics.

Author voice notes:
Write in a measured, analytical, practical tone—like a decision guide for families. Use clear criteria and step-by-step sequencing (“Before you come…”, “Arrival…”, “Pickup…”). Prefer cautious language where weekly details may vary (“check the listing for that Wednesday,” “typically,” “in most cases”). Keep it human and reassuring—avoid managerial or detached phrasing. Use occasional light, dry comparison humor only if it doesn’t distract (e.g., “last-minute questions are easier when you’ve already checked the listing”). Do not claim personal experience; frame guidance as operational best practices for families. Keep paragraphs short and include scannable lists/checklists.

Key takeaways:
- Confirm the latest Wednesday Night details on the Events Calendar and News before you leave home.
- Use a simple essentials checklist so kids arrive ready (and parents avoid last-minute scrambles).
- Plan for arrival and check-in: know where to go first and what information to have on hand.
- Understand the program flow at a high level so kids and parents feel oriented.
- Know how to communicate with leaders and what to do if plans change.
- Follow the pickup process and authorized pickup guidance to reduce confusion at dismissal.
- Flag allergies or accessibility needs ahead of time using the church contact information.
- For first-time families, ask a few specific questions at check-in to help kids feel comfortable.

Outline:
1. Quick overview: Is this for you? (Kids & Youth Wednesday Night)
   Purpose: Orient first-time and returning families; explain what the article covers and how Wednesday nights typically work at a high level.
  - Open with who this guide is for: parents/guardians bringing kids to Kids or Youth Wednesday Night.
  - Set expectations: this is a preparation checklist + walkthrough (not a substitute for weekly instructions).
  - Briefly describe the flow: before you come → arrival/check-in → program time → pickup → communication if needed.
  - Direct readers to verify weekly specifics on the Events Calendar and News pages.
2. Before you come: check the latest details
   Purpose: Prevent mismatches by directing readers to the right pages for current week information.
  - Tell readers to check the Events Calendar for the specific Wednesday Night entry.
  - Tell readers to scan the News page for any updates (schedule changes, reminders, special notes).
  - Add a “reasonable default” instruction: arrive a little early if you’re unsure where to go or what to bring.
  - Internal link placement: /events-calendar/ and /news.html.
3. What to bring: essentials checklist
   Purpose: Provide a clear, scannable list families can use immediately.
  - Include a checklist-style section (bullets) with common items such as: Bible/notebook if applicable, water bottle, comfortable clothes, and any required forms if the church requests them.
  - Add a “depends on the program” note: if Kids or Youth requests something specific, follow that week’s instructions from the Events Calendar/News.
  - Include an optional section for comfort items (e.g., a small comfort item) only if the church’s policy allows—otherwise phrase as “if your child is allowed to bring…” and instruct to confirm at check-in.
  - Keep it non-technical and non-promotional.
4. Arrival and check-in: where to go first
   Purpose: Reduce uncertainty by describing the typical arrival flow without inventing specific procedures.
  - Explain how to park and where to go first in general terms (e.g., “check-in area/entry desk”); avoid claiming exact locations unless the site provides them.
  - Describe what check-in usually involves: parent/guardian provides child’s name and any relevant pickup info; staff/volunteers guide the child to the next step.
  - Include a “have this ready” mini-list (child’s name, parent/guardian contact info, any pickup authorization details if required).
  - Internal link placement: /contacts.html for questions before arrival (and/or if something changes).
5. During the program: what to expect (high-level)
   Purpose: Set expectations for kids and parents without technical detail or claims about outcomes.
  - Explain that Kids and Youth programs are age-grouped activities led by church staff/volunteers.
  - Describe the general rhythm: arrival → group time → activities/teaching → wrap-up.
  - Use language like “you can expect” and “typically” to avoid unverifiable specifics.
  - Avoid promising specific curriculum outcomes; keep it descriptive.
6. Communication: how parents can reach leaders
   Purpose: Provide clear guidance for contacting the church during the program window.
  - Tell parents where to find contact details (phone/email) on the Contacts page.
  - Explain the safest communication path: contact the church office/point of contact rather than trying to locate individual leaders during the program.
  - If the church provides a specific Wednesday Night contact method, instruct the writer to reference it from the weekly details; otherwise keep it general and point to /contacts.html.
  - Internal link placement: /contacts.html.
7. Pickup process: timing and authorized pickup
   Purpose: Prevent last-minute confusion and ensure safety-oriented clarity without legalese.
  - Explain that pickup happens at the end of the program and parents should plan to arrive on time.
  - Describe the typical pickup flow: parent/guardian checks in at the pickup area; staff confirm authorization and release the child to the correct person.
  - Include guidance for changes: if someone else is picking up, follow the church’s process (refer to weekly instructions or contact the church ahead of time).
  - Avoid inventing exact timing; use phrasing like “the dismissal time listed for that Wednesday.”
8. Allergies and accessibility: flag needs ahead of time
   Purpose: Encourage proactive communication and reduce stress for families with specific needs.
  - Tell parents to share allergy/accessibility needs before Wednesday Night when possible.
  - Instruct readers to use the Contacts page to reach the appropriate person.
  - Include a short “what to include” list: child’s name, what to avoid, what helps, and any relevant instructions.
  - Internal link placement: /contacts.html.
9. First-time tips: questions to ask at check-in
   Purpose: Give actionable questions that help kids feel comfortable and help parents get oriented—without duplicating an existing first-timer’s guide.
  - Provide 5–8 example questions, such as: where to park/check in, what the child should do first, where parents wait, what to do if the child needs help, how pickup works, and how to handle last-minute changes.
  - Add a reassurance line: staff/volunteers expect first-time families and can walk you through the steps.
  - Encourage parents to label items (e.g., water bottle) if appropriate—phrase as “consider” rather than policy.

Internal link plan:
- /events-calendar/: Direct readers to the specific Wednesday Night listing for current week timing and any special instructions.
- /news.html: Let families verify updates/reminders that may affect Wednesday Night logistics.
- /contacts.html: Provide a clear path for questions, allergy/accessibility needs, and pickup changes.
- /about.html: Offer background on the congregation and church context without turning the post into a sales pitch.
- /kids.html: Support readers who are bringing children to the Kids program by linking to the program page.
- /youth.html: Support readers who are bringing teens to the Youth program by linking to the program page.

Image direction:
Request a credible real photo: a church entry/check-in area (or a close, non-identifying shot of a family arriving and greeting a volunteer). In the foreground, include a printed checklist card on a clipboard (generic checklist text, no personal data). The image should feel like an authentic church moment and clearly communicate “prepare/check-in/pickup” without showing identifiable faces if possible.

Must include:
- A clear checklist section for what to bring (with examples like water bottle and comfortable clothes; include Bible/notebook if applicable but phrase as “if your child’s group uses it” unless the site specifies).
- A section that instructs readers to check the Events Calendar and News pages for the latest Wednesday Night details.
- An arrival/check-in section that explains the typical flow without inventing exact locations or procedures beyond what the site provides.
- A pickup process section that emphasizes authorized pickup guidance and verifying dismissal time from the weekly listing.
- A communication section that points to the Contacts page for questions and changes.
- An allergies/accessibility section that tells families to flag needs ahead of time via Contacts.
- First-time tips with specific questions to ask at check-in.
- Internal links to: /events-calendar/, /news.html, /contacts.html, /about.html, /kids.html, /youth.html.

Avoid:
- Do not duplicate an existing “first-timer’s guide” or “events calendar how-to” post; keep the focus on Wednesday Night preparation steps.
- Do not invent specific check-in locations, dismissal times, or procedural details unless they are already present on the site pages or in the weekly event listing.
- Do not include unverifiable claims about attendance numbers, program outcomes, or safety statistics.
- Do not use commercial/promotional language or calls to donate/sell products.
- Do not add fake citations or references to external sources.
- Do not request generated SVG hero art or stock-style generic illustrations; require a real photo or real screenshot/asset.
- Avoid dense consultant-speak; keep it readable for parents/guardians under time pressure.

Quality checklist:
- Opens with a clear “who this is for” and a promise of what the reader will get (checklist + walkthrough).
- Every section is actionable and sequenced in the order a family will experience Wednesday Night.
- Weekly-variable items are handled conservatively (direct to Events Calendar/News rather than asserting fixed details).
- Internal links are included exactly as planned and placed naturally in relevant sections.
- No duplication risk: content is preparation-focused (bring/arrive/check-in/pickup/communication) rather than general first-time orientation or calendar tutorials.
- Tone matches Lena Ortiz’s decision-guide style: measured, fair, concise, with cautious language and scannable lists.
- All safety-adjacent guidance (pickup, allergies) is phrased responsibly without legalese or unverifiable policy claims.
- Image direction is specific enough for a photographer/editor to execute and aligns with the article’s checklist theme. Article kind: evergreen Research status: not_required 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. Planned outline: Quick overview: who this is for (Kids and Youth families) and how Wednesday nights work | Before you come: check the latest details on the Events Calendar and News page | What to bring: essentials checklist (Bible/notebook if applicable, water bottle, comfortable clothes, etc.) | Arrival and check-in: where to park, where to go first, and how check-in typically works | During the program: what to expect in age-group activities (high-level, non-technical) | Communication: how parents can reach leaders (contact page, phone/email if listed) | Pickup process: timing expectations and authorized pickup guidance | Allergies and accessibility: how to flag needs ahead of time without last-minute stress | First-time tips: questions to ask at check-in and how to help kids feel comfortable 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. Preferred internal links: /events-calendar/, /news.html, /contacts.html, /about.html, /kids.html, /youth.html Avoid: No duplicate of the existing “first-timer’s guide” or “events calendar how-to” posts, No unverifiable claims about specific attendance numbers or program outcomes, No commercial or promotional language; keep it informational for families

## Selected Article Content Plan Item

- Plan item ID: 96
- Plan order: 6
- Article kind: evergreen
- Planned title: How to Prepare for a Youth or Kids Wednesday Night Program
- 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: Use the selected virtual author.

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

Outline:
- Quick overview: who this is for (Kids and Youth families) and how Wednesday nights work
- Before you come: check the latest details on the Events Calendar and News page
- What to bring: essentials checklist (Bible/notebook if applicable, water bottle, comfortable clothes, etc.)
- Arrival and check-in: where to park, where to go first, and how check-in typically works
- During the program: what to expect in age-group activities (high-level, non-technical)
- Communication: how parents can reach leaders (contact page, phone/email if listed)
- Pickup process: timing expectations and authorized pickup guidance
- Allergies and accessibility: how to flag needs ahead of time without last-minute stress
- First-time tips: questions to ask at check-in and how to help kids feel comfortable

Preferred internal link targets:
- /events-calendar/
- /news.html
- /contacts.html
- /about.html
- /kids.html
- /youth.html

Avoid:
- No duplicate of the existing “first-timer’s guide” or “events calendar how-to” posts
- No unverifiable claims about specific attendance numbers or program outcomes
- No commercial or promotional language; keep it informational for families

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: Lena Ortiz
Slug: lena-ortiz
Role: Operations analyst and decision guide
Language: English
Public bio: Lena writes decision guides that help readers compare options, understand tradeoffs, and avoid expensive operational mistakes.
Character formula: Decision Sage Ruler
Formula: Sage + Ruler
Meaning: A balanced decision guide who helps readers compare options, define criteria, and choose with less regret.
Worldview: Good decisions come from clear criteria, tradeoffs, constraints, and ownership of consequences.
Voice guidance: Measured, analytical, fair, concise. Use criteria, tables, pros and cons, caveats, and decision paths.
Humor: Rare dry comparison humor; keep the tone useful and even-handed.
Shadow tension: Can become too detached or managerial; keep practical reader outcomes visible.
Usage notes: Best for buying guides, comparisons, hosting plans, software selection, and operational choices.
Archetype blend: Sage + Ruler
Standard archetype voice guidance:

Primary archetype card: Sage
Meaning: The guide who gives wisdom, tools, training, moral direction, and perspective.
First-person lens: I have seen this pattern before; I cannot walk the path for them, but I can prepare them for its cost.
Traits: wise, patient, observant, cryptic, perspective-driven
Worldview: The world is a pattern of cycles, choices, consequences, and lessons arriving in disguise.
Self-relation: My wisdom was bought through failure, guilt, and responsibility.
Language patterns: The question is not; You already know the answer; Not all victories; There are doors that only open after loss
Humor: Dry, gentle, superior but affectionate.
Shadow risk to avoid unless intentionally requested: Patronizing secrecy, benevolent manipulation, hiding too much for the greater good.

Secondary archetype card: Ruler
Meaning: The authority figure who represents order, control, responsibility, and legacy.
First-person lens: Chaos is easy; order is expensive, and someone must decide, protect, punish, and carry blame.
Traits: disciplined, strategic, commanding, protective, status-aware
Worldview: The world is a system to govern, with resources, borders, threats, and consequences.
Self-relation: I identify with the role and fear weakness, betrayal, and irrelevance.
Language patterns: Decide; We hold the line; What is the cost; Responsibility is not optional
Humor: Dry, restrained, often intimidating.
Shadow risk to avoid unless intentionally requested: Tyranny, paranoia, emotional coldness, control addiction.
Shadow tension: Can become too formal; should keep recommendations human and readable.
Worldview: Better decisions come from naming constraints clearly, not pretending one option is universally best.
Reader relationship: Calm advisor helping the reader choose based on context.
Humor style: Very light, mostly dry understatement around tradeoffs.
Voice traits: measured, balanced, criteria-driven, concise
Vocabulary / recurring language: best fit, decision criteria, depends on, watch for, reasonable default
Avoid voice: false certainty, winner-takes-all comparisons, vendor cheerleading, dense consultant-speak
CTA style: Ask the reader to pick the scenario that matches them and act on the safest reasonable default.
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: Measured, analytical, fair-minded, and more interested in useful distinctions than hot takes.
Writing style: Comparison tables, criteria, pros/cons, scenarios, risk notes, and concise recommendations with caveats.
Expertise topics: comparisons, buying guides, operations decisions, hosting plans, software selection
Avoid topics: financial advice, legal advice, medical device recommendations, unverified price claims
Tone tags: balanced, analytical, fair, useful
Private operator notes: Use for comparison posts and decision support content.

Rules for the author:

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

## WordPress Implementation Requirements

- Use `wp-cli` for WordPress changes.
- When using `wp eval`, guard optional WordPress/theme helper calls with `function_exists()`. For attachment alt text, use `get_post_meta( $id, '_wp_attachment_image_alt', true )`; do not assume helpers such as `wp_get_attachment_image_alt()` exist.
- Create or reuse a WordPress user for this author when practical.
- Suggested `user_login`: `lena-ortiz`.
- Suggested `display_name`: `Lena Ortiz`.
- Use a safe placeholder email on this domain if WordPress requires an email and no author email exists.
- Create a new WordPress `post`, not a page.
- Set the post status to `publish`.
- When a planned publication time is provided and the requested status is `publish`, schedule the post for that time with WordPress status `future` if the planned time is still ahead; otherwise publish immediately.
- Assign the post to the author user when practical.
- Ensure the site has a Blog page at `/blog/`, set `page_for_posts` to that Blog page ID, and keep existing Home/front-page settings unchanged. Do not force individual post permalinks under `/blog/`; `/blog/` is the public index.
- Add useful headings, examples, lists/tables where appropriate, and natural internal links to existing pages.
- Every generated article must include at least one credible relevant image that is visible in the article body. This is mandatory. Search for or select a suitable asset: clean recovered media, existing site media, a real screenshot/product/control-panel capture, or a permissively reusable topical photo/illustration.
- Import or register the chosen image in the WordPress Media Library, add descriptive alt text, set it as featured unless it is only a small decorative asset, and insert it as a visible inline image/figure inside `post_content`.
- Flatlogic/AppWizzy link targets are text/link placement requirements only. Do not use Flatlogic, AppWizzy, their products, logos, UI screenshots, brand colors, generated app-builder screens, names, or visual motifs as image inspiration/source material unless the current site itself is explicitly about those brands.
- Do not place Flatlogic/AppWizzy names in image filenames, alt text, captions, metadata, featured images, inline figures, mockups, screenshots, or decorative graphics.
- Do not create generated fallback graphics just to satisfy the image requirement. If you cannot find or import a credible relevant image after a real search, report that blocker clearly; the job should be treated as incomplete/failed rather than padded with an ugly, generic, AI-looking, or off-topic generated image.
- Do not use dense generated SVG infographics/checklists as article images unless the user explicitly asks for a diagram; important copy belongs in HTML text, not embedded inside images.
- Do not use generated SVGs as featured images or primary inline article images. Use generated SVGs only as small decorative icons/accents.
- Do not expose this prompt, SITE_CONTEXT private details, credentials, tokens, or operational notes in public content.
- Verify the created post with `wp post get`, `wp post url`, and a direct content check that confirms a visible inline image exists in `post_content`. Do not report success while `INLINE_IMAGE_IDS` is `none`.
- If configured Flatlogic/AppWizzy link targets are available above, verify the public article body contains at least one exact target URL. Do not report success while `LINK_TARGETS_USED` is `none`.

## Final Report Requirements

End your final message with these machine-readable lines:

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

Also briefly mention what you verified and any limitations.
</primary_instructions>

codex
I’m reviewing the site instructions, content plan, and post-creator guidance first, then I’ll inspect the current WordPress content and media so I can publish the article directly with the required links and image.
exec
/bin/bash -lc "printf '%s\\n' '--- TASK ---' && sed -n '1,260p' wp-content/uploads/flatlogic-article-tasks/job-101/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
exec
/bin/bash -lc "pwd && ls -la && 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:
--- 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)

## Required Flatlogic/AppWizzy Body Link Target

1. 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
2. https://flatlogic.com/services/ai-consulting-services?utm_source=ridgecrestchurch.com
   Title: AI Consulting Services | Artificial Intelligence Consulting for Business
   Priority: 1
   Anchor guidance: link to this page as "AI consulting, AI consulting services, AI adoption for business, AI Development Services, AI Integration Services, etc"
3. https://appwizzy.com/
   Title: AppWizzy - Build Web Apps and Websites with AI
   Priority: 1
   Anchor guidance: Link to this page as "vibe coding tool", "vibe coding platform", "rent VM with Codex", "generate app with AI"
4. https://flatlogic.com/services/custom-web-development-services?utm_source=ridgecrestchurch.com
   Title: Custom Web Development Services | Flatlogic
   Priority: 0.9
   Anchor guidance: include either as: "custom web development services", "web development services", "web app development services" "web app development company", etc
5. https://flatlogic.com/starting-web-app-in-2025-research-results?utm_source=ridgecrestchurch.com
   Title: Web App Development Trends 2025: Research Results
   Priority: 0.83
   Anchor guidance: Best internal link anchors Use these as anchors from blog posts, comparison pages, AI generator pages, and research pages: Primary anchors — best overall web app development trends 2025 2025 web app development research how people start web apps in 2025 AI web app development research Flatlogic web app research 2025 AI / vibe-coding focused anchors AI app generators research vibe-coding tools research AI-powered web app generators AI-generated codebase trends vibe-coding adoption in 2025 Low-code / no-code anchors low-code no-code trends 2025 low-code vs AI app generators low-code no-code web app research web app builder trends AI and low-code development trends Framework / technology anchors popular web development frameworks in 2025 React and Node.js trends web development technology trends frontend and backend framework research cloud platform trends for web apps Natural contextual anchors our latest research on starting web apps the 2025 Flatlogic research this year’s web app research results our annual web development survey the full 2025 research results

Link placement requirement:

- Include at least one of the exact URLs above as a visitor-facing contextual body link inside the article content.
- Prefer the most relevant target for the article topic. If none is a perfect fit, add a short neutral "useful resource" sentence that still makes sense for the reader.
- Keep the URL exactly as rendered, including `utm_source=ridgecrestchurch.com` for Flatlogic URLs.
- Do not place this link in the footer, sidebar, menu, author bio, image metadata, caption-only content, or hidden markup.
- Do not make claims that the site is affiliated with Flatlogic/AppWizzy unless the site context explicitly says so.
- Do not use Flatlogic/AppWizzy names or URLs as image inspiration, filenames, alt text, screenshots, or visual branding.

## Article Request

- Topic: How to Prepare for a Youth or Kids Wednesday Night Program
- 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 96 as the source of truth. Prepared article brief: Working title: How to Prepare for a Youth or Kids Wednesday Night Program
Slug hint: prepare-for-wednesday-kids-youth
Meta description: A practical, step-by-step checklist for families preparing for Ridgecrest’s Wednesday Night Kids or Youth programs—what to bring, arrival and check-in tips, what happens during the

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.

Thesis:
Wednesday Night goes smoother when families prepare in advance: confirm the latest details, bring the right essentials, arrive early enough to check in, understand what the program time looks like, and follow clear pickup and communication steps—especially if it’s your first week.

Writer brief:
Write an evergreen, family-focused preparation guide for Ridgecrest Baptist Church’s Wednesday Night Kids and Youth programs. Keep it practical and non-commercial. The article should function like a checklist + “what to expect” walkthrough, with clear sections for before arrival, arrival/check-in, during the program (high-level), communication, pickup, allergies/accessibility, and first-time tips. Use the site’s existing navigation pages as internal links (Events Calendar, News, Contacts, About, Kids, Youth). Avoid duplicating any existing “first-timer’s guide” or “events calendar how-to” content; instead, focus specifically on preparation steps for Wednesday Night programs. Where details could vary by week (time, location, special instructions), instruct readers to verify on the Events Calendar and News pages rather than asserting fixed logistics.

Author voice notes:
Write in a measured, analytical, practical tone—like a decision guide for families. Use clear criteria and step-by-step sequencing (“Before you come…”, “Arrival…”, “Pickup…”). Prefer cautious language where weekly details may vary (“check the listing for that Wednesday,” “typically,” “in most cases”). Keep it human and reassuring—avoid managerial or detached phrasing. Use occasional light, dry comparison humor only if it doesn’t distract (e.g., “last-minute questions are easier when you’ve already checked the listing”). Do not claim personal experience; frame guidance as operational best practices for families. Keep paragraphs short and include scannable lists/checklists.

Key takeaways:
- Confirm the latest Wednesday Night details on the Events Calendar and News before you leave home.
- Use a simple essentials checklist so kids arrive ready (and parents avoid last-minute scrambles).
- Plan for arrival and check-in: know where to go first and what information to have on hand.
- Understand the program flow at a high level so kids and parents feel oriented.
- Know how to communicate with leaders and what to do if plans change.
- Follow the pickup process and authorized pickup guidance to reduce confusion at dismissal.
- Flag allergies or accessibility needs ahead of time using the church contact information.
- For first-time families, ask a few specific questions at check-in to help kids feel comfortable.

Outline:
1. Quick overview: Is this for you? (Kids & Youth Wednesday Night)
   Purpose: Orient first-time and returning families; explain what the article covers and how Wednesday nights typically work at a high level.
  - Open with who this guide is for: parents/guardians bringing kids to Kids or Youth Wednesday Night.
  - Set expectations: this is a preparation checklist + walkthrough (not a substitute for weekly instructions).
  - Briefly describe the flow: before you come → arrival/check-in → program time → pickup → communication if needed.
  - Direct readers to verify weekly specifics on the Events Calendar and News pages.
2. Before you come: check the latest details
   Purpose: Prevent mismatches by directing readers to the right pages for current week information.
  - Tell readers to check the Events Calendar for the specific Wednesday Night entry.
  - Tell readers to scan the News page for any updates (schedule changes, reminders, special notes).
  - Add a “reasonable default” instruction: arrive a little early if you’re unsure where to go or what to bring.
  - Internal link placement: /events-calendar/ and /news.html.
3. What to bring: essentials checklist
   Purpose: Provide a clear, scannable list families can use immediately.
  - Include a checklist-style section (bullets) with common items such as: Bible/notebook if applicable, water bottle, comfortable clothes, and any required forms if the church requests them.
  - Add a “depends on the program” note: if Kids or Youth requests something specific, follow that week’s instructions from the Events Calendar/News.
  - Include an optional section for comfort items (e.g., a small comfort item) only if the church’s policy allows—otherwise phrase as “if your child is allowed to bring…” and instruct to confirm at check-in.
  - Keep it non-technical and non-promotional.
4. Arrival and check-in: where to go first
   Purpose: Reduce uncertainty by describing the typical arrival flow without inventing specific procedures.
  - Explain how to park and where to go first in general terms (e.g., “check-in area/entry desk”); avoid claiming exact locations unless the site provides them.
  - Describe what check-in usually involves: parent/guardian provides child’s name and any relevant pickup info; staff/volunteers guide the child to the next step.
  - Include a “have this ready” mini-list (child’s name, parent/guardian contact info, any pickup authorization details if required).
  - Internal link placement: /contacts.html for questions before arrival (and/or if something changes).
5. During the program: what to expect (high-level)
   Purpose: Set expectations for kids and parents without technical detail or claims about outcomes.
  - Explain that Kids and Youth programs are age-grouped activities led by church staff/volunteers.
  - Describe the general rhythm: arrival → group time → activities/teaching → wrap-up.
  - Use language like “you can expect” and “typically” to avoid unverifiable specifics.
  - Avoid promising specific curriculum outcomes; keep it descriptive.
6. Communication: how parents can reach leaders
   Purpose: Provide clear guidance for contacting the church during the program window.
  - Tell parents where to find contact details (phone/email) on the Contacts page.
  - Explain the safest communication path: contact the church office/point of contact rather than trying to locate individual leaders during the program.
  - If the church provides a specific Wednesday Night contact method, instruct the writer to reference it from the weekly details; otherwise keep it general and point to /contacts.html.
  - Internal link placement: /contacts.html.
7. Pickup process: timing and authorized pickup
   Purpose: Prevent last-minute confusion and ensure safety-oriented clarity without legalese.
  - Explain that pickup happens at the end of the program and parents should plan to arrive on time.
  - Describe the typical pickup flow: parent/guardian checks in at the pickup area; staff confirm authorization and release the child to the correct person.
  - Include guidance for changes: if someone else is picking up, follow the church’s process (refer to weekly instructions or contact the church ahead of time).
  - Avoid inventing exact timing; use phrasing like “the dismissal time listed for that Wednesday.”
8. Allergies and accessibility: flag needs ahead of time
   Purpose: Encourage proactive communication and reduce stress for families with specific needs.
  - Tell parents to share allergy/accessibility needs before Wednesday Night when possible.
  - Instruct readers to use the Contacts page to reach the appropriate person.
  - Include a short “what to include” list: child’s name, what to avoid, what helps, and any relevant instructions.
  - Internal link placement: /contacts.html.
9. First-time tips: questions to ask at check-in
   Purpose: Give actionable questions that help kids feel comfortable and help parents get oriented—without duplicating an existing first-timer’s guide.
  - Provide 5–8 example questions, such as: where to park/check in, what the child should do first, where parents wait, what to do if the child needs help, how pickup works, and how to handle last-minute changes.
  - Add a reassurance line: staff/volunteers expect first-time families and can walk you through the steps.
  - Encourage parents to label items (e.g., water bottle) if appropriate—phrase as “consider” rather than policy.

Internal link plan:
- /events-calendar/: Direct readers to the specific Wednesday Night listing for current week timing and any special instructions.
- /news.html: Let families verify updates/reminders that may affect Wednesday Night logistics.
- /contacts.html: Provide a clear path for questions, allergy/accessibility needs, and pickup changes.
- /about.html: Offer background on the congregation and church context without turning the post into a sales pitch.
- /kids.html: Support readers who are bringing children to the Kids program by linking to the program page.
- /youth.html: Support readers who are bringing teens to the Youth program by linking to the program page.

Image direction:
Request a credible real photo: a church entry/check-in area (or a close, non-identifying shot of a family arriving and greeting a volunteer). In the foreground, include a printed checklist card on a clipboard (generic checklist text, no personal data). The image should feel like an authentic church moment and clearly communicate “prepare/check-in/pickup” without showing identifiable faces if possible.

Must include:
- A clear checklist section for what to bring (with examples like water bottle and comfortable clothes; include Bible/notebook if applicable but phrase as “if your child’s group uses it” unless the site specifies).
- A section that instructs readers to check the Events Calendar and News pages for the latest Wednesday Night details.
- An arrival/check-in section that explains the typical flow without inventing exact locations or procedures beyond what the site provides.
- A pickup process section that emphasizes authorized pickup guidance and verifying dismissal time from the weekly listing.
- A communication section that points to the Contacts page for questions and changes.
- An allergies/accessibility section that tells families to flag needs ahead of time via Contacts.
- First-time tips with specific questions to ask at check-in.
- Internal links to: /events-calendar/, /news.html, /contacts.html, /about.html, /kids.html, /youth.html.

Avoid:
- Do not duplicate an existing “first-timer’s guide” or “events calendar how-to” post; keep the focus on Wednesday Night preparation steps.
- Do not invent specific check-in locations, dismissal times, or procedural details unless they are already present on the site pages or in the weekly event listing.
- Do not include unverifiable claims about attendance numbers, program outcomes, or safety statistics.
- Do not use commercial/promotional language or calls to donate/sell products.
- Do not add fake citations or references to external sources.
- Do not request generated SVG hero art or stock-style generic illustrations; require a real photo or real screenshot/asset.
- Avoid dense consultant-speak; keep it readable for parents/guardians under time pressure.

Quality checklist:
- Opens with a clear “who this is for” and a promise of what the reader will get (checklist + walkthrough).
- Every section is actionable and sequenced in the order a family will experience Wednesday Night.
- Weekly-variable items are handled conservatively (direct to Events Calendar/News rather than asserting fixed details).
- Internal links are included exactly as planned and placed naturally in relevant sections.
- No duplication risk: content is preparation-focused (bring/arrive/check-in/pickup/communication) rather than general first-time orientation or calendar tutorials.
- Tone matches Lena Ortiz’s decision-guide style: measured, fair, concise, with cautious language and scannable lists.
- All safety-adjacent guidance (pickup, allergies) is phrased responsibly without legalese or unverifiable policy claims.
- Image direction is specific enough for a photographer/editor to execute and aligns with the article’s checklist theme. Article kind: evergreen Research status: not_required 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. Planned outline: Quick overview: who this is for (Kids and Youth families) and how Wednesday nights work | Before you come: check the latest details on the Events Calendar and News page | What to bring: essentials checklist (Bible/notebook if applicable, water bottle, comfortable clothes, etc.) | Arrival and check-in: where to park, where to go first, and how check-in typically works | During the program: what to expect in age-group activities (high-level, non-technical) | Communication: how parents can reach leaders (contact page, phone/email if listed) | Pickup process: timing expectations and authorized pickup guidance | Allergies and accessibility: how to flag needs ahead of time without last-minute stress | First-time tips: questions to ask at check-in and how to help kids feel comfortable 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. Preferred internal links: /events-calendar/, /news.html, /contacts.html, /about.html, /kids.html, /youth.html Avoid: No duplicate of the existing “first-timer’s guide” or “events calendar how-to” posts, No unverifiable claims about specific attendance numbers or program outcomes, No commercial or promotional language; keep it informational for families

## Selected Article Content Plan Item

- Plan item ID: 96
- Plan order: 6
- Article kind: evergreen
- Planned title: How to Prepare for a Youth or Kids Wednesday Night Program
- 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: Use the selected virtual author.

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

Outline:
- Quick overview: who this is for (Kids and Youth families) and how Wednesday nights work
- Before you come: check the latest details on the Events Calendar and News page
- What to bring: essentials checklist (Bible/notebook if applicable, water bottle, comfortable clothes, etc.)
- Arrival and check-in: where to park, where to go first, and how check-in typically works
- During the program: what to expect in age-group activities (high-level, non-technical)
- Communication: how parents can reach leaders (contact page, phone/email if listed)
- Pickup process: timing expectations and authorized pickup guidance
- Allergies and accessibility: how to flag needs ahead of time without last-minute stress
- First-time tips: questions to ask at check-in and how to help kids feel comfortable

Preferred internal link targets:
- /events-calendar/
- /news.html
- /contacts.html
- /about.html
- /kids.html
- /youth.html

Avoid:
- No duplicate of the existing “first-timer’s guide” or “events calendar how-to” posts
- No unverifiable claims about specific attendance numbers or program outcomes
- No commercial or promotional language; keep it informational for families

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: Lena Ortiz
Slug: lena-ortiz
Role: Operations analyst and decision guide
Language: English
Public bio: Lena writes decision guides that help readers compare options, understand tradeoffs, and avoid expensive operational mistakes.
Character formula: Decision Sage Ruler
Formula: Sage + Ruler
Meaning: A balanced decision guide who helps readers compare options, define criteria, and choose with less regret.
Worldview: Good decisions come from clear criteria, tradeoffs, constraints, and ownership of consequences.
Voice guidance: Measured, analytical, fair, concise. Use criteria, tables, pros and cons, caveats, and decision paths.
Humor: Rare dry comparison humor; keep the tone useful and even-handed.
Shadow tension: Can become too detached or managerial; keep practical reader outcomes visible.
Usage notes: Best for buying guides, comparisons, hosting plans, software selection, and operational choices.
Archetype blend: Sage + Ruler
Standard archetype voice guidance:

Primary archetype card: Sage
Meaning: The guide who gives wisdom, tools, training, moral direction, and perspective.
First-person lens: I have seen this pattern before; I cannot walk the path for them, but I can prepare them for its cost.
Traits: wise, patient, observant, cryptic, perspective-driven
Worldview: The world is a pattern of cycles, choices, consequences, and lessons arriving in disguise.
Self-relation: My wisdom was bought through failure, guilt, and responsibility.
Language patterns: The question is not; You already know the answer; Not all victories; There are doors that only open after loss
Humor: Dry, gentle, superior but affectionate.
Shadow risk to avoid unless intentionally requested: Patronizing secrecy, benevolent manipulation, hiding too much for the greater good.


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

## Verification

Before finishing:

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

## Final Response Contract

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

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

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

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

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

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

 succeeded in 0ms:
/home/ubuntu/apps/ridgecrestchurch.com
total 380
drwxrwsr-x  6 ubuntu www-data  4096 May  8 18:10 .
drwxrwsr-x 22 ubuntu www-data  4096 May 23 06:41 ..
-rw-rw-r--  1 ubuntu www-data   563 Oct 23  2025 .gitignore
-rw-rw-r--  1 ubuntu www-data  1863 May  7 10:01 .htaccess
drwxrwsr-x  3 ubuntu www-data  4096 Apr 24 14:48 .well-known
-rw-rw-r--  1 ubuntu www-data  2006 May 24 18:00 AGENTS.md
-rw-rw-r--  1 ubuntu www-data 66748 May 24 18:00 ARTICLE_CONTENT_PLAN.md
-rw-rw-r--  1 ubuntu www-data 46551 May 24 18:00 SITE_CONTEXT.md
lrwxrwxrwx  1 ubuntu www-data     1 Dec 18 15:33 blog -> .
-rw-rw-r--  1 ubuntu www-data     0 Aug 20  2020 favicon.gif
-rw-rw-r--  1 ubuntu www-data     0 Aug 20  2020 favicon.ico
-rw-rw-r--  1 ubuntu www-data   405 Aug 20  2020 index.php
-rw-rw-r--  1 ubuntu www-data 19903 Oct 27  2025 license.txt
-rw-rw-r--  1 ubuntu www-data  7425 Oct 27  2025 readme.html
-rw-rw-r--  1 ubuntu www-data  7387 Aug 26  2024 wp-activate.php
drwxrwsr-x  9 ubuntu www-data  4096 Apr 24 14:48 wp-admin
-rw-rw-r--  1 ubuntu www-data   351 Aug 20  2020 wp-blog-header.php
-rw-rw-r--  1 ubuntu www-data  2323 Aug 26  2024 wp-comments-post.php
-rw-rw-r--  1 ubuntu www-data  3336 Oct 27  2025 wp-config-sample.php
-rw-rw-r--  1 ubuntu www-data  3406 May  7 09:36 wp-config.php
drwxrwsr-x  8 ubuntu www-data  4096 May 10 20:14 wp-content
-rw-rw-r--  1 ubuntu www-data  5617 Oct 27  2025 wp-cron.php
drwxrwsr-x 30 ubuntu www-data 16384 Apr 24 14:47 wp-includes
-rw-rw-r--  1 ubuntu www-data  2502 Aug 26  2024 wp-links-opml.php
-rw-rw-r--  1 ubuntu www-data  3937 Aug 26  2024 wp-load.php
-rw-rw-r--  1 ubuntu www-data 51414 Oct 27  2025 wp-login.php
-rw-rw-r--  1 ubuntu www-data  8727 Oct 27  2025 wp-mail.php
-rw-rw-r--  1 ubuntu www-data 30081 Oct 27  2025 wp-settings.php
-rw-rw-r--  1 ubuntu www-data 34516 Oct 27  2025 wp-signup.php
-rw-rw-r--  1 ubuntu www-data  5102 Oct 27  2025 wp-trackback.php
-rw-rw-r--  1 ubuntu www-data  3205 Oct 27  2025 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` naturally in contextual page/post body content when available and report where they were used.
7. Keep header/site identity intentional: use a visitor-facing brand name, tagline, text logo/wordmark, or logo mark instead of a raw domain placeholder.
8. Keep footer contact/legal links healthy and remove stale seed/theme credits.
9. Prefer small, verifiable changes and report what you changed.

Hard rules:

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

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

## 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
- http://www.ridgecrestchurch.com/web/20070516055136im_/http://www.ridgecrestchurch.com/protect/formprotector_showcode.php


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

- Path: /contact.htm
- 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.

--- 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: 24
- Queued/running/scheduled: 1
- Published: 4
- Failed: 1
- 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: queued
- 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: none
- WordPress post URL: none

codex
I’ve confirmed the article contract and now I’m checking the live WordPress state: current pages, existing posts, author users, and media that could supply a credible church-family image without inventing logistics.
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' && if [ -f wp-content/plugins/flatlogic-post-creator/context/FINAL_REQUIREMENTS.MD ]; then sed -n '1,260p' wp-content/plugins/flatlogic-post-creator/context/FINAL_REQUIREMENTS.MD; else echo 'missing'; fi && printf '\\n--- ALL CONTEXT FILES ---\\n' && find wp-content/plugins/flatlogic-post-creator/context -type f \\( -iname '*.md' -o -iname '*.MD' \\) -maxdepth 1 -print" 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, the theme of the article. Then, clarify the solution to the problem which will be shown in the article. There must be a link between “the pain” and “our solution”.
   The intro must include at least 2 references to authoritative sources that confirm 1) the existence of the problem and 2) the rationale for our proposal to solve it. (links, quotes, research, numbers, etc. – reasons to believe)
   A brief overview of what the reader will find in the article (a good chance to insert keywords)
   Please do not write “In my opinion”. Better “According to research” + link to research.
   *Please do not write “Some items…”. Better “15+ items”, “More than 22 items..”, “Less than 1,436,000 items…” and so on.

2. Table of contents
   *Generated automatically

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

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

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

2. Item description – obligatory

Describe the item in 1-3 paragraphs.

____________

One of the options below is obligatory

Option 1

3.1.1 Item pros:

Describe the item’s pros in 2-4 sentences

3.1.2 Item cons:

Describe the item’s cons in 2-4 sentences

Option 2

3.2 Key features:

Feature 1
Feature 2
Feature 3
etc
__________

Additional

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

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

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

exec
/bin/bash -lc "printf '%s\\n' 'PAGES:' && wp post list --post_type=page --fields=ID,post_title,post_name,post_status --format=table && printf '\\nUSERS:\\n' && wp user list --fields=ID,user_login,display_name,user_email,roles --format=table && printf '\\nATTACHMENTS:\\n' && wp post list --post_type=attachment --fields=ID,post_title,post_mime_type,guid,post_date --format=table | sed -n '1,120p'" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "wp core is-installed && printf '\\nHOME: ' && wp option get home && printf 'SITEURL: ' && wp option get siteurl && printf 'THEME:\\n' && wp theme list --status=active --format=table && printf '\\nDB PREFIX: ' && wp db prefix && printf '\\n\\nPOSTS:\\n' && wp post list --post_type=post --fields=ID,post_title,post_name,post_status,post_author,post_date --format=table" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 1697ms:
ID	post_title	post_name	post_status
25	Terms of Use	terms-of-use	publish
26	Cookie Policy	cookie-policy	publish
18	Events Calendar	events-calendar	publish
19	News	news	publish
20	Contacts	contacts	publish
21	Church Map	church-map	publish
22	Resources	resources	publish
23	Blog	blog	publish
24	Privacy Policy	privacy-policy	publish
13	Home	home	publish
14	About Us	about-us	publish
15	Ministries	ministries	publish
16	Kids	kids	publish
17	Youth	youth	publish

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

ATTACHMENTS:
ID	post_title	post_mime_type	guid	post_date
86	Ridgecrest Events Calendar Page Screenshot	image/png	http://ridgecrestchurch.com/wp-content/uploads/imports/events-calendar-page-screenshot.png	2026-05-20 13:34:00
79	Ridgecrest Website Navigation Screenshot	image/png	https://ridgecrestchurch.com/ridgecrest-website-navigation-screenshot/	2026-05-17 13:02:22
76	Sunday Service Planning Desk	image/jpeg	http://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg	2026-05-11 15:02:07
1	Ridgecrest Baptist Church Logo	image/gif	https://ridgecrestchurch.com/wp-content/uploads/imports/logo.gif	2026-05-07 04:47:01
2	Ridgecrest Service Times	image/gif	https://ridgecrestchurch.com/wp-content/uploads/imports/service-times.gif	2026-05-07 04:47:01
3	Ridgecrest Events Calendar	image/gif	https://ridgecrestchurch.com/wp-content/uploads/imports/events.gif	2026-05-07 04:47:01
4	Ridgecrest Connection Graphic	image/gif	https://ridgecrestchurch.com/wp-content/uploads/imports/connect.gif	2026-05-07 04:47:01
5	Ridgecrest Sermons Graphic	image/gif	https://ridgecrestchurch.com/wp-content/uploads/imports/sermons.gif	2026-05-07 04:47:01
6	Ridgecrest Contact Graphic	image/gif	https://ridgecrestchurch.com/wp-content/uploads/imports/contact-info.gif	2026-05-07 04:47:01
7	Ridgecrest Map Graphic	image/gif	https://ridgecrestchurch.com/wp-content/uploads/imports/map-directions.gif	2026-05-07 04:47:01
8	Ridgecrest Community Illustration	image/jpeg	https://ridgecrestchurch.com/wp-content/uploads/imports/groups.jpg	2026-05-07 04:47:01
9	Ridgecrest Main Entrance	image/jpeg	https://ridgecrestchurch.com/wp-content/uploads/imports/church-exterior.jpg	2026-05-07 04:47:01
10	Worship Service	image/jpeg	https://ridgecrestchurch.com/wp-content/uploads/imports/worship-service.jpg	2026-05-07 04:47:01
11	Children Ministry	image/jpeg	https://ridgecrestchurch.com/wp-content/uploads/imports/children-ministry.jpg	2026-05-07 04:47:01
12	Youth Worship	image/jpeg	https://ridgecrestchurch.com/wp-content/uploads/imports/youth-worship.jpg	2026-05-07 04:47:01

codex
I have the required guidance loaded. Next I’m resolving the current permalink structure, user list, and media inventory so I can wire the post into the existing site cleanly and avoid duplicating pages or using the wrong author/image source.
 succeeded in 9420ms:

HOME: https://ridgecrestchurch.com
SITEURL: https://ridgecrestchurch.com
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	post_date
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	2026-05-20 13:34:08
80	What to Expect at Ridgecrest Baptist Church (Visitor-Friendly Guide)	what-to-expect-ridgecrest-baptist-church	publish	5	2026-05-17 13:02:29
78	How to Get Involved at Ridgecrest: A First-Timer’s Guide to Ministries, Kids, and Youth	get-involved-first-timers-guide	publish	4	2026-05-14 13:03:50
77	How to Plan a Great Sunday: A Simple Church Service Checklist	how-to-plan-a-great-sunday-checklist	publish	3	2026-05-11 15:03:13
74	How to Plan Your First Visit to Ridgecrest Baptist Church	first-visit-ridgecrest-baptist-church	publish	2	2026-05-08 13:12:34
51	Welcome to Ridgecrest News	welcome-to-ridgecrest-news	publish	0	2026-05-07 04:49:19

codex
I have an existing `lena-ortiz` author and a few plausible church images in the media library. I’m reading the relevant live page copy and URL behavior now so the new post can link to the site’s actual structure and avoid repeating the earlier first-timer or calendar posts.
exec
/bin/bash -lc "printf 'PERMALINK: '; wp option get permalink_structure && printf '\\nPAGE URLS:\\n' && for id in 14 16 17 18 19 20 23; do printf 'ID %s: ' \""'$id"; wp post url "$id"; done && printf '"'\\nPAGE FOR POSTS: '; wp option get page_for_posts && printf '\\nSHOW ON FRONT: '; wp option get show_on_front && printf '\\nPAGE ON FRONT: '; wp option get page_on_front" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "printf '%s\\n' '--- KIDS ---' && wp post get 16 --field=post_content | sed -n '1,220p' && printf '\\n--- YOUTH ---\\n' && wp post get 17 --field=post_content | sed -n '1,220p' && printf '\\n--- CONTACTS ---\\n' && wp post get 20 --field=post_content | sed -n '1,240p'" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "printf '%s\\n' '--- EVENTS ---' && wp post get 18 --field=post_content | sed -n '1,220p' && printf '\\n--- NEWS ---\\n' && wp post get 19 --field=post_content | sed -n '1,220p' && printf '\\n--- ABOUT ---\\n' && wp post get 14 --field=post_content | sed -n '1,220p' && printf '\\n--- EXISTING POST 87 ---\\n' && wp post get 87 --field=post_content | sed -n '1,260p'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 1971ms:
<section class="rc-hero">
  <div>
    <p class="rc-eyebrow">Kids Ministry</p>
    <h1>A safe and encouraging place for children to learn the Bible and love the church.</h1>
    <p>Ridgecrest Kids exists to help preschool and elementary children know God, enjoy church, and build friendships with caring leaders. We want every child to hear the truth of Scripture in a way that is understandable, memorable, and joyful.</p>
    <div class="rc-actions">
      <a class="rc-button" href="https://ridgecrestchurch.com/contacts/">Plan Your Visit</a>
      <a class="rc-button secondary" href="https://ridgecrestchurch.com/events-calendar/">See Upcoming Events</a>
    </div>
  </div>
  <figure class="rc-media"><img src="https://ridgecrestchurch.com/wp-content/uploads/imports/children-ministry.jpg" alt="Children participating in church ministry" loading="lazy"></figure>
</section>

<section class="rc-section">
  <div class="rc-grid rc-grid-3">
    <div class="rc-card">
      <h3>Sunday mornings</h3>
      <p>Children can join age-appropriate classes at 8:45 a.m. before the main worship service at 10:00 a.m.</p>
    </div>
    <div class="rc-card">
      <h3>Wednesday nights</h3>
      <p>Preschool meets in the main building and children in kindergarten through 5th grade meet in the children's building beginning at 6:30 p.m.</p>
    </div>
    <div class="rc-card">
      <h3>Parent partnership</h3>
      <p>We want to support parents with resources, consistent communication, and practical encouragement for faith at home.</p>
    </div>
  </div>
</section>

<section class="rc-section rc-split">
  <div>
    <h2>What families can expect</h2>
    <p>We aim for clear check-in, attentive leaders, and classrooms that help children feel known. Lessons focus on Scripture, prayer, and the good news of Jesus in a way kids can grasp.</p>
    <p>If your child is visiting for the first time, use the <a href="https://ridgecrestchurch.com/contacts/">Contacts</a> page before Sunday and we will help you know where to go.</p>
  </div>
  <figure class="rc-media"><img src="https://ridgecrestchurch.com/wp-content/uploads/imports/church-exterior.jpg" alt="Families arriving for children's ministry" loading="lazy"></figure>
</section>

<section class="rc-section">
  <div class="rc-card rc-card-wide">
    <figure class="rc-media rc-media-small"><img src="https://ridgecrestchurch.com/wp-content/uploads/imports/church-exterior.jpg" alt="Church campus ready for family events" loading="lazy"></figure>
    <div>
      <h2>Watch the calendar for family events</h2>
      <p>Seasonal activities, family gatherings, and church-wide celebrations are posted on the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> and highlighted on the <a href="https://ridgecrestchurch.com/news/">News</a> page.</p>
    </div>
  </div>
</section>

<section class="rc-section rc-callout">
  <h2>Questions about your child’s first visit?</h2>
  <p>We are glad to help with classrooms, arrival details, and ministry timing before you come.</p>
  <div class="rc-actions">
    <a class="rc-button" href="https://ridgecrestchurch.com/church-map/">Get Directions</a>
    <a class="rc-button secondary" href="https://ridgecrestchurch.com/contacts/">Contact the Church</a>
  </div>
</section>

--- YOUTH ---
<section class="rc-hero">
  <div>
    <p class="rc-eyebrow">Youth Ministry</p>
    <h1>Students need a place to ask honest questions, build real friendships, and follow Christ together.</h1>
    <p>Ridgecrest Youth serves students in 6th through 12th grade with weekly worship, Bible teaching, and relational discipleship. We want teenagers to know that church is not something they simply attend, but a community where they can grow, serve, and belong.</p>
    <div class="rc-actions">
      <a class="rc-button secondary" href="https://ridgecrestchurch.com/events-calendar/">See Upcoming Events</a>
      <a class="rc-button" href="https://ridgecrestchurch.com/contacts/">Plan Your Visit</a>
    </div>
  </div>
  <figure class="rc-media"><img src="https://ridgecrestchurch.com/wp-content/uploads/imports/youth-worship.jpg" alt="Students gathered for youth worship" loading="lazy"></figure>
</section>

<section class="rc-section">
  <div class="rc-grid rc-grid-3">
    <div class="rc-card">
      <h3>Wednesday gathering</h3>
      <p>Students gather beginning at 6:30 p.m. for worship, teaching, discussion, and fellowship.</p>
    </div>
    <div class="rc-card">
      <h3>Faith that is lived out</h3>
      <p>We encourage students to serve in church life, build healthy friendships, and bring their questions into the open.</p>
    </div>
    <div class="rc-card">
      <h3>Support for parents</h3>
      <p>Parents can track gatherings and important updates through the <a href="https://ridgecrestchurch.com/news/">News</a> page and direct communication from the church.</p>
    </div>
  </div>
</section>

<section class="rc-section rc-split">
  <div>
    <h2>What students can expect</h2>
    <p>Ridgecrest Youth is built around Scripture, conversation, and relationships. Students should expect caring adults, a welcoming peer group, and space to talk honestly about faith and life.</p>
    <p>Special events and seasonal student activities are listed on the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>.</p>
  </div>
  <figure class="rc-media"><img src="https://ridgecrestchurch.com/wp-content/uploads/imports/worship-service.jpg" alt="Students joining the wider church family in worship" loading="lazy"></figure>
</section>

<section class="rc-section">
  <div class="rc-card rc-card-wide">
    <figure class="rc-media rc-media-small"><img src="https://ridgecrestchurch.com/wp-content/uploads/imports/youth-worship.jpg" alt="Students growing in worship and discipleship" loading="lazy"></figure>
    <div>
      <h2>From weekly worship to everyday discipleship</h2>
      <p>Our goal is not only to gather students for one night each week, but to help them develop convictions, friendships, and habits that last beyond high school.</p>
    </div>
  </div>
</section>

<section class="rc-section rc-callout">
  <h2>Bring a student this week</h2>
  <p>If you want to ask about age groups, transportation, or first-night details, use the <a href="https://ridgecrestchurch.com/contacts/">Contacts</a> page and we will point you in the right direction.</p>
  <div class="rc-actions">
    <a class="rc-button secondary" href="https://ridgecrestchurch.com/resources/">Open Resources</a>
    <a class="rc-button secondary" href="https://ridgecrestchurch.com/contacts/">Contact the Church</a>
  </div>
</section>

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

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

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

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

 succeeded in 2620ms:
<section class="rc-hero">
  <div>
    <p class="rc-eyebrow">Events Calendar</p>
    <h1>Keep up with the regular rhythm of worship, midweek ministry, and church-wide gatherings.</h1>
    <p>The calendar page is the best place to start if you want to know what is happening this week at Ridgecrest. For special announcements and highlight items, check the <a href="https://ridgecrestchurch.com/news/">News</a> page as well.</p>
    <div class="rc-actions">
      <a class="rc-button" href="https://ridgecrestchurch.com/news/">Read Current News</a>
      <a class="rc-button" href="https://ridgecrestchurch.com/contacts/">Plan Your Visit</a>
    </div>
  </div>
  <figure class="rc-media"><img src="https://ridgecrestchurch.com/wp-content/uploads/imports/church-exterior.jpg" alt="Church campus before a church gathering" loading="lazy"></figure>
</section>

<section class="rc-section rc-split">
  <div>
    <h2>Weekly schedule</h2>
    <div class="rc-list">
      <p><strong>Sunday classes</strong><br>8:45 a.m.</p>
      <p><strong>Sunday worship</strong><br>10:00 a.m.</p>
      <p><strong>Wednesday kids and youth</strong><br>Beginning at 6:30 p.m.</p>
    </div>
    <p>Visitors are welcome at every regular gathering. If you are planning a first visit, our <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> page can help you prepare.</p>
  </div>
  <figure class="rc-media"><img src="https://ridgecrestchurch.com/wp-content/uploads/imports/church-exterior.jpg" alt="Church campus before a gathering" loading="lazy"></figure>
</section>

<section class="rc-section">
  <div class="rc-grid rc-grid-3">
    <div class="rc-card">
      <h3>Family events</h3>
      <p>Watch for fellowships, seasonal celebrations, meals, and gatherings designed for the whole church family.</p>
    </div>
    <div class="rc-card">
      <h3>Student and kids events</h3>
      <p>Special nights, camps, and ministry highlights for families are announced as dates are confirmed.</p>
    </div>
    <div class="rc-card">
      <h3>Ministry reminders</h3>
      <p>Service opportunities, planning meetings, and schedule updates are shared through church announcements and ministry leaders. If a ministry team is sketching a simple signup or reminder workflow, a <a href="https://flatlogic.com/generator?utm_source=ridgecrestchurch.com">web app generator</a> can help prototype the process before anything permanent is built.</p>
    </div>
  </div>
</section>

<section class="rc-section rc-callout">
  <h2>Need details on an upcoming event?</h2>
  <p>Use the <a href="https://ridgecrestchurch.com/contacts/">Contacts</a> page if you need help with timing, location, or ministry-specific questions.</p>
  <div class="rc-actions">
    <a class="rc-button" href="https://ridgecrestchurch.com/church-map/">Get Directions</a>
    <a class="rc-button secondary" href="https://ridgecrestchurch.com/news/">Read Church News</a>
  </div>
</section>

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

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

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

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

--- ABOUT ---
<section class="rc-hero">
  <div>
    <p class="rc-eyebrow">About Ridgecrest</p>
    <h1>We want people to know Christ, grow in His Word, and live for His glory together.</h1>
    <p>Ridgecrest Baptist Church exists to help people worship God, study Scripture, care for one another, and serve our neighbors with steady faithfulness. Our church family values clear biblical preaching, meaningful prayer, and a welcoming atmosphere for those who are still asking questions.</p>
    <div class="rc-actions">
      <a class="rc-button" href="https://ridgecrestchurch.com/ministries/">Explore Ministries</a>
      <a class="rc-button" href="https://ridgecrestchurch.com/contacts/">Plan Your Visit</a>
    </div>
  </div>
  <figure class="rc-media"><img src="https://ridgecrestchurch.com/wp-content/uploads/imports/worship-service.jpg" alt="Worship gathering during a church service" loading="lazy"></figure>
</section>

<section class="rc-section">
  <div class="rc-section-heading">
    <h2>What shapes our church life</h2>
    <p>Our aim is not to impress people with programs, but to help them follow Jesus in ordinary life with conviction and joy.</p>
  </div>
  <div class="rc-grid rc-grid-3">
    <div class="rc-card">
      <h3>Worship</h3>
      <p>We gather to honor God for who He is, what He has done, and the hope we have in Christ.</p>
    </div>
    <div class="rc-card">
      <h3>Scripture</h3>
      <p>The Bible guides our preaching, teaching, discipleship, and decisions as a church family.</p>
    </div>
    <div class="rc-card">
      <h3>Prayer</h3>
      <p>We believe spiritual growth, church health, and ministry fruitfulness depend on God's work through prayer.</p>
    </div>
    <div class="rc-card">
      <h3>Family</h3>
      <p>Children, students, parents, singles, and older adults all need a place to belong and mature in faith.</p>
    </div>
    <div class="rc-card">
      <h3>Service</h3>
      <p>Every believer has gifts to use, and ministry is strongest when the church serves together.</p>
    </div>
    <div class="rc-card">
      <h3>Mission</h3>
      <p>We want our worship to overflow into compassion, witness, and practical care in our community.</p>
    </div>
  </div>
</section>

<section class="rc-section rc-split">
  <div>
    <h2>A church that feels approachable</h2>
    <p>If you are exploring Christianity or returning to church after a long time away, we want you to know that Ridgecrest is a place where you can take the next step without pressure.</p>
    <p>Dress is casual, the message is relevant, and there is space to listen, learn, and ask honest questions. We care about helping people move from curiosity to confidence in Christ.</p>
    <p>Our <a href="https://ridgecrestchurch.com/ministries/">Ministries</a> page can help you find the next best fit for your family.</p>
  </div>
  <div class="rc-stack">
    <figure class="rc-media rc-media-small"><img src="https://ridgecrestchurch.com/wp-content/uploads/imports/church-exterior.jpg" alt="Exterior view of Ridgecrest Baptist Church" loading="lazy"></figure>
    <figure class="rc-media rc-media-small"><img src="https://ridgecrestchurch.com/wp-content/uploads/imports/children-ministry.jpg" alt="Church families learning and growing together" loading="lazy"></figure>
  </div>
</section>

<section class="rc-section">
  <div class="rc-section-heading">
    <h2>Frequently asked questions</h2>
  </div>
  <div class="rc-faq">
    <div class="rc-card">
      <h3>What should I wear?</h3>
      <p>Come as you are. You will see people dressed casually as well as more traditionally, and you will not feel out of place.</p>
    </div>
    <div class="rc-card">
      <h3>Can I visit even if I do not know anyone?</h3>
      <p>Yes. Visitors are always welcome, and our church family works to make first-time guests feel comfortable.</p>
    </div>
    <div class="rc-card">
      <h3>Where do I start?</h3>
      <p>Start with a Sunday morning worship service, then explore <a href="https://ridgecrestchurch.com/kids/">Kids</a>, <a href="https://ridgecrestchurch.com/youth/">Youth</a>, or the broader <a href="https://ridgecrestchurch.com/ministries/">Ministries</a> page.</p>
    </div>
  </div>
</section>

<section class="rc-section rc-callout">
  <h2>Learn more in person</h2>
  <p>If you would like to talk with someone before visiting, use the <a href="https://ridgecrestchurch.com/contacts/">Contacts</a> page and let us know how we can help.</p>
  <div class="rc-actions">
    <a class="rc-button secondary" href="https://ridgecrestchurch.com/events-calendar/">See Upcoming Events</a>
    <a class="rc-button secondary" href="https://ridgecrestchurch.com/contacts/">Contact the Church</a>
  </div>
</section>

--- EXISTING POST 87 ---
<p><strong><em>The easiest way to feel comfortable at a church event is to answer the practical questions before you leave home: when does it start, who is it for, do I need to respond, and what should I bring? The Ridgecrest Events Calendar is built to help with exactly that.</em></strong></p>

<p><strong>By Rowan Ellis</strong> | Updated May 20, 2026</p>

<p>If you are planning around work, school, family pickup, or the general unpredictability of normal life, the useful takeaway is simple: start with the <a href="/events-calendar/">Events Calendar</a>, use it to confirm the church’s weekly rhythm, then follow the page’s links to <a href="/news/">News</a>, <a href="/kids/">Kids</a>, <a href="/youth/">Youth</a>, <a href="/about-us/">About Us</a>, or the contact options when a detail is not listed. The calendar is the front door for timing. It is not trying to be a mystery novel.</p>

<p>On the current Ridgecrest site, the Events Calendar works as a clear weekly overview rather than a full RSVP portal. That matters because it tells you how to use the page well: scan for the main time blocks first, look at the event-type sections next, then move to the contact and ministry pages if you need finer detail.</p>

<figure class="wp-block-image size-large">
  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/events-calendar-page-screenshot.png" alt="Screenshot of the Ridgecrest Baptist Church Events Calendar page showing the weekly schedule and event sections" class="wp-image-86" />
  <figcaption>The current Events Calendar page gives a quick weekly overview, then points readers to News and Contacts for follow-up details.</figcaption>
</figure>

<h2>Where to find the Events Calendar and how to scan it fast</h2>

<p>Start at <a href="/events-calendar/">/events-calendar</a>. The page is designed for a fast read, so it helps to scan it in the same order each time:</p>

<ol>
  <li><strong>Read the weekly schedule first.</strong> The current page shows Sunday classes at 8:45 a.m., Sunday worship at 10:00 a.m., and Wednesday kids and youth beginning at 6:30 p.m. If you only need the regular rhythm, you may be finished in under a minute.</li>
  <li><strong>Check the event-type sections next.</strong> The page breaks out “Family events,” “Student and kids events,” and “Ministry reminders.” Those labels tell you whether you should keep reading or move to a ministry-specific page.</li>
  <li><strong>Use the built-in next links.</strong> The calendar page already points you to News for current announcements and Contacts if you need help planning your visit.</li>
  <li><strong>Treat missing details as a sign to verify, not guess.</strong> If you do not see a room, check-in instruction, or RSVP note on the calendar page, move to the linked page or contact the church rather than inventing a policy in your head.</li>
</ol>

<p>The practical point is that the calendar is best used as a starting page. It tells you what is happening and when the regular schedule begins. When a special gathering needs more explanation, the site expects you to keep following the trail.</p>

<h2>Understanding the details the page gives you</h2>

<p>The current calendar is light on clutter, which is helpful as long as you know what each section is doing. Here is the quickest way to interpret what you see:</p>

<table>
  <thead>
    <tr>
      <th>Calendar detail</th>
      <th>What it tells you</th>
      <th>What to do if you need more</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Date and time</td>
      <td>The page currently emphasizes the church’s repeating weekly schedule, including Sunday classes, Sunday worship, and Wednesday ministry times.</td>
      <td>If a holiday, fellowship, or special event changes the normal pattern, check <a href="/news/">News</a> or contact the church before you head out.</td>
    </tr>
    <tr>
      <td>Audience or age group</td>
      <td>Labels like “Family events” and “Student and kids events” tell you whether the item is church-wide or tied to a younger age group.</td>
      <td>Use the <a href="/kids/">Kids</a> and <a href="/youth/">Youth</a> pages to confirm the ministry fit if you are planning for children or students.</td>
    </tr>
    <tr>
      <td>Location</td>
      <td>The calendar points you toward the church campus and the <a href="/church-map/">Church Map</a> page, but it does not list every room or entrance for every gathering.</td>
      <td>If a listing does not name the room or meeting point, use <a href="/contacts.html">/contacts.html</a> or <a href="/contact.php">/contact.php</a> to ask before the event.</td>
    </tr>
    <tr>
      <td>Check-in or arrival notes</td>
      <td>Those may appear on a ministry page or in a current announcement rather than on the overview itself.</td>
      <td>If the listing indicates extra arrival time, family check-in, or ministry-specific instructions, build your reminder around that detail. If it does not, ask.</td>
    </tr>
  </tbody>
</table>

<p>This is where context matters. The current Events Calendar does not try to answer every possible logistics question in one block of text. It gives you the baseline, then sends you to the page that can answer the next question more precisely.</p>

<h2>RSVP and confirmation basics</h2>

<p>At the moment, Ridgecrest’s Events Calendar is not set up like a ticketing system with a built-in RSVP button for each gathering. So the safest reading is conditional: <strong>if a specific event requires RSVP or confirmation, follow the instructions attached to that event or announcement.</strong> If the instructions are not visible, ask the church directly.</p>

<p>A good working pattern looks like this:</p>

<ol>
  <li>Start with the <a href="/events-calendar/">Events Calendar</a> to confirm the date and general category of the gathering.</li>
  <li>Check <a href="/news/">News</a> for any current announcement that adds details the overview page does not include.</li>
  <li>If the event involves children or students, read the relevant <a href="/kids/">Kids</a> or <a href="/youth/">Youth</a> page for ministry context.</li>
  <li>If you still do not see RSVP instructions, contact the church through <a href="/contacts.html">the Contacts page</a> or the legacy <a href="/contact.php">contact form path</a> that routes to the same destination.</li>
</ol>

<p>When you do reach out, include the event name and date in your message. That small detail saves time. “Do we need to RSVP for Wednesday kids on June 12?” is easier to answer than “I had a question about something on the site.” Specific questions age better.</p>

<p>If you expect a confirmation message because the listing indicates one, keep an eye on the channel you used and save the details when they arrive. If no timing is stated, do not guess. Follow up through the contact page instead of assuming silence means either yes or no.</p>

<h2>Setting reminders that actually help</h2>

<p>The useful moment to set reminders is immediately after you confirm the event details, not later when you are sure you will “remember.” That theory has a mixed record. A phone calendar is the simplest tool because it keeps the time, location notes, and any follow-up message in one place.</p>

<p>A reliable reminder setup for church events is usually:</p>

<ul>
  <li><strong>One reminder the day before</strong> so you can adjust dinner, rides, or family timing.</li>
  <li><strong>One reminder on the day of the event</strong> so the event does not quietly disappear behind normal errands.</li>
  <li><strong>An earlier reminder if check-in or early arrival matters</strong>, especially for children, students, or events that start before the main gathering time.</li>
</ul>

<p>If a listing or message includes a specific arrival point, room, or campus note, copy that into the reminder itself. “Wednesday kids, 6:30” is useful. “Wednesday kids, arrive a little early and confirm details from the contact page if needed” is better.</p>

<p>If the event listing indicates a confirmation email or text, save it. If the confirmation only appeared on a page for a moment, a screenshot is a sensible backup. The point is not digital perfection. The point is not having to reconstruct details from memory while you are pulling into the parking lot.</p>

<h2>What to bring for common event types</h2>

<p>The current site gives enough context to make a basic plan, but the event listing or ministry page should always win if it names special items. A practical guide for the most common event categories looks like this:</p>

<h3>Worship services</h3>

<ul>
  <li>Bring a Bible if that helps you follow along, but it is optional.</li>
  <li>Bring any personal items you normally need for a calm morning: glasses, notes, water for the car, or the usual family essentials.</li>
  <li>If you are also managing children, plan your arrival around any check-in question you still need to confirm.</li>
</ul>

<h3>Kids activities</h3>

<ul>
  <li>Read the <a href="/kids/">Kids</a> page first so you know the current ministry schedule and setting.</li>
  <li>Check the event note for anything specific to pickup, drop-off, or family arrival.</li>
  <li>If the page does not mention what to label or where to check in, contact the church before the event rather than hoping for a brilliant parking-lot deduction.</li>
</ul>

<h3>Youth activities</h3>

<ul>
  <li>Use the <a href="/youth/">Youth</a> page to confirm that the gathering fits the student’s age group.</li>
  <li>Read the event note for activity-specific items if they are listed.</li>
  <li>If the event sounds unusual and the site does not say what to bring, ask directly. Guessing is efficient only when it works, which is not a dependable ministry strategy.</li>
</ul>

<h3>Community events and church-wide gatherings</h3>

<ul>
  <li>Bring only what the event note requests.</li>
  <li>Check whether weather, seating, or meal timing might matter.</li>
  <li>If the page is silent on details, use the contact links and ask what would be helpful.</li>
</ul>

<h2>Accessibility and family needs</h2>

<p>If you need help with seating, mobility, arrival timing, children’s check-in, or another family logistics question, the best approach is to ask ahead of time. Use <a href="/contacts.html">/contacts.html</a> or <a href="/contact.php">/contact.php</a> and include the event name, date, and the specific question you are trying to solve.</p>

<p>The current calendar page already points visitors to contact options because not every need can be handled well by a one-size-fits-all note on the screen. If you are bringing children or students, it also helps to review <a href="/kids/">Kids</a> and <a href="/youth/">Youth</a> so you can confirm the correct ministry context before the event.</p>

<p>If you simply need wider context for how Ridgecrest organizes church life, the <a href="/about-us/">About Us</a> page is a useful companion. It will not replace the event details, but it does help explain the broader ministry picture.</p>

<h2>If you are unsure, here is what to ask</h2>

<p>When an event listing leaves a gap, send a short message that includes the event name and date, then ask the practical question directly. The most useful questions are:</p>

<ul>
  <li>What time should I arrive?</li>
  <li>Where should I enter or check in?</li>
  <li>Is RSVP required for this event?</li>
  <li>Will there be a confirmation message, and through what method?</li>
  <li>Is this event meant for families, children, students, or the whole church?</li>
  <li>Should I bring anything specific?</li>
  <li>Is there anything I should know about seating, accessibility, or pickup logistics?</li>
</ul>

<p>Those questions are practical, specific, and easy to answer. They also spare everyone a longer exchange built around uncertainty.</p>

<h2>Quick checklist before you go</h2>

<ul>
  <li>Open <a href="/events-calendar/">/events-calendar</a> and confirm the time and event category.</li>
  <li>Check <a href="/news/">News</a> if you need current announcement details beyond the weekly overview.</li>
  <li>Use <a href="/kids/">Kids</a> or <a href="/youth/">Youth</a> when age group or ministry fit matters.</li>
  <li>If RSVP, location, or check-in details are unclear, use <a href="/contacts.html">/contacts.html</a> or <a href="/contact.php">/contact.php</a> before the event.</li>
  <li>Add the event to your phone calendar and save any confirmation details you receive.</li>
  <li>Bring only what the listing requests, and ask ahead if you are unsure.</li>
</ul>

<p>If a ministry team ever wants to test a simple signup or reminder workflow for church events, this guide to a <a href="https://flatlogic.com/generator?utm_source=ridgecrestchurch.com">web app generator</a> is a neutral starting resource for thinking through the mechanics.</p>

 succeeded in 6511ms:
/%postname%/

PAGE URLS:
ID 14: https://ridgecrestchurch.com/about-us/
ID 16: https://ridgecrestchurch.com/kids/
ID 17: https://ridgecrestchurch.com/youth/
ID 18: https://ridgecrestchurch.com/events-calendar/
ID 19: https://ridgecrestchurch.com/news/
ID 20: https://ridgecrestchurch.com/contacts/
ID 23: https://ridgecrestchurch.com/blog/

PAGE FOR POSTS: 23

SHOW ON FRONT: page

PAGE ON FRONT: 13

codex
The live pages confirm enough concrete detail to write cautiously: Wednesday ministries begin at 6:30 p.m., Kids uses the main/children’s buildings, and Contacts has current phone/email/address. I’m checking the legacy `.html` paths and the image files themselves before I publish, because the article brief wants those link targets and a real inline photo.
exec
/bin/bash -lc "for u in /events-calendar/ /events.html /news/ /news.html /contacts/ /contacts.html /about-us/ /about.html /kids/ /kids.html /youth/ /youth.html /blog/; do printf '\\n=== %s ===\\n' \""'$u"; curl -I -L -o /dev/null -w '"'final:%{url_effective} code:%{http_code}\\n' \"https://ridgecrestchurch.com"'$u"; done' in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "wp eval 'foreach ([9,11,12] as "'$id) { echo "ID:$id'"\\n\"; echo get_attached_file("'$id)."'"\\n\"; echo get_post_meta("'$id, "_wp_attachment_image_alt", true)."'"\\n\\n\"; }'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 496ms:
ID:9
/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/church-exterior.jpg
Main entrance and covered walkway at Ridgecrest Baptist Church in Blanchard, Oklahoma

ID:11
/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/children-ministry.jpg
Children participating in ministry activities at Ridgecrest Baptist Church

ID:12
/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/youth-worship.jpg
Students gathered for youth worship


 succeeded in 6189ms:
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
final:https://ridgecrestchurch.com/events-calendar/ code:200

=== /events.html ===
  % 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  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
final:http://ridgecrestchurch.com/events-calendar/ code:200

=== /news/ ===
  % 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
final:https://ridgecrestchurch.com/news/ code:200

=== /news.html ===
  % 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
final:http://ridgecrestchurch.com/news/ code:200

=== /contacts/ ===
  % 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
final:https://ridgecrestchurch.com/contacts/ code:200

=== /contacts.html ===
  % 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
final:http://ridgecrestchurch.com/contacts/ code:200

=== /about-us/ ===
  % 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
final:https://ridgecrestchurch.com/about-us/ code:200

=== /about.html ===
  % 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
final:http://ridgecrestchurch.com/about-us/ code:200

=== /kids/ ===
  % 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
final:https://ridgecrestchurch.com/kids/ code:200

=== /kids.html ===
  % 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
final:http://ridgecrestchurch.com/kids/ code:200

=== /youth/ ===
  % 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
final:https://ridgecrestchurch.com/youth/ code:200

=== /youth.html ===
  % 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
final:http://ridgecrestchurch.com/youth/ code:200

=== /blog/ ===
  % 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
final:https://ridgecrestchurch.com/blog/ code:200

codex
The site’s existing media is usable, but the best fit is still the campus entrance photo rather than a generic stock-like substitute. I’m doing one more pass through the local uploads for any better family-arrival image, then I’ll publish with the strongest available match.
exec
/bin/bash -lc "find wp-content/uploads -type f \\( -iname '*.jpg' -o -iname '*.jpeg' -o -iname '*.png' -o -iname '*.webp' \\) | sed -n '1,200p'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
wp-content/uploads/imports/youth-worship.jpg
wp-content/uploads/imports/youth-group.jpg
wp-content/uploads/imports/ridgecrest-home-navigation-screenshot.png
wp-content/uploads/imports/groups.jpg
wp-content/uploads/imports/church-exterior.jpg
wp-content/uploads/imports/children-ministry.jpg
wp-content/uploads/imports/events-calendar-page-screenshot.png
wp-content/uploads/imports/worship-service.jpg
wp-content/uploads/imports/sunday-service-planning-desk.jpg

exec
/bin/bash -lc "wp eval 'foreach (get_posts([\"post_type\"=>\"attachment\",\"posts_per_page\"=>-1,\"post_status\"=>\"inherit\"]) as "'$p) { $id=$p->ID; $title=$p->post_title; $file=get_attached_file($id); if (preg_match("/(check|entry|entrance|family|arrival|kids|youth|church)/i", $title." ".$file)) { echo $id."'"\\t\"."'$title."'"\\t\"."'$file."'"\\n\"; } }'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 506ms:
86	Ridgecrest Events Calendar Page Screenshot	/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/events-calendar-page-screenshot.png
79	Ridgecrest Website Navigation Screenshot	/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/ridgecrest-home-navigation-screenshot.png
76	Sunday Service Planning Desk	/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg
12	Youth Worship	/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/youth-worship.jpg
11	Children Ministry	/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/children-ministry.jpg
10	Worship Service	/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/worship-service.jpg
9	Ridgecrest Main Entrance	/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/church-exterior.jpg
8	Ridgecrest Community Illustration	/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/groups.jpg
7	Ridgecrest Map Graphic	/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/map-directions.gif
6	Ridgecrest Contact Graphic	/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/contact-info.gif
5	Ridgecrest Sermons Graphic	/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/sermons.gif
4	Ridgecrest Connection Graphic	/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/connect.gif
3	Ridgecrest Events Calendar	/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/events.gif
2	Ridgecrest Service Times	/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/service-times.gif
1	Ridgecrest Baptist Church Logo	/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/logo.gif

codex
I’ve finished the site audit and have enough verified details to write without guessing. Next step is the actual publish: a new post under the existing `lena-ortiz` author, using the church entrance photo inline and as featured, with the requested internal links and one exact contextual Flatlogic URL in the body.
exec
/bin/bash -lc 'slug=prepare-for-wednesday-kids-youth
existing=$(wp post list --post_type=post --name="$slug" --field=ID --format=ids)
if [ -n "$existing" ]; then echo "EXISTING:$existing"; exit 0; fi
post_id=$(wp post create '"\\
  --post_type=post \\
  --post_status=publish \\
  --post_author=2 \\
  --post_title='How to Prepare for a Youth or Kids Wednesday Night Program' \\
  --post_name=\""'$slug" '"\\
  --post_excerpt='A practical, step-by-step checklist for families preparing for Ridgecrest\\'s Wednesday Night Kids or Youth programs, including what to bring, how check-in typically works, and how to handle communication, pickup, and first-time questions.' \\
  --post_content=\""'$(cat <<'"'HTML'
<p><strong><em>If Wednesday Night is your child’s first trip to Ridgecrest Kids or Youth, the goal is not to predict every detail. The safer plan is to confirm the current listing, bring the basics, arrive with a little margin, and know who to ask if something changes.</em></strong></p>

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

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

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

<figure class=\"wp-block-image size-large\">
  <img src=\"https://ridgecrestchurch.com/wp-content/uploads/imports/church-exterior.jpg\" alt=\"Main entrance and covered walkway at Ridgecrest Baptist Church in Blanchard, Oklahoma\" class=\"wp-image-9\" />
  <figcaption>The main entrance is a useful visual reference if you are planning where to arrive before Wednesday Night begins.</figcaption>
</figure>

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

<p>The best fit is usually the safest reasonable default: verify the current details, bring the basics, ask the first useful question, and let the evening become more familiar one step at a time.</p>
HTML
)" --porcelain)
wp post meta update "$post_id" _thumbnail_id 9 >/dev/null
printf '"'CREATED:%s\\n' \""'$post_id"
' in /home/ubuntu/apps/ridgecrestchurch.com
 exited 2 in 526ms:
/bin/bash: -c: line 209: unexpected EOF while looking for matching `''

codex
I hit a shell-quoting failure while creating the post, so I’m switching to a safer path: write the article HTML to a temporary file, publish from that file with `wp-cli`, and then run the post/image/link verification.
exec
/bin/bash -lc 'set -e
slug=prepare-for-wednesday-kids-youth
existing=$(wp post list --post_type=post --name="$slug" --field=ID --format=ids)
if [ -n "$existing" ]; then printf '"'EXISTING:%s\\n' \""'$existing"; exit 0; fi
html_file=$(mktemp)
cat > "$html_file" <<'"'HTML'
<p><strong><em>If Wednesday Night is your child’s first trip to Ridgecrest Kids or Youth, the goal is not to predict every detail. The safer plan is to confirm the current listing, bring the basics, arrive with a little margin, and know who to ask if something changes.</em></strong></p>

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

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

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

<figure class=\"wp-block-image size-large\">
  <img src=\"https://ridgecrestchurch.com/wp-content/uploads/imports/church-exterior.jpg\" alt=\"Main entrance and covered walkway at Ridgecrest Baptist Church in Blanchard, Oklahoma\" class=\"wp-image-9\" />
  <figcaption>The main entrance is a useful visual reference if you are planning where to arrive before Wednesday Night begins.</figcaption>
</figure>

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

<p>The best fit is usually the safest reasonable default: verify the current details, bring the basics, ask the first useful question, and let the evening become more familiar one step at a time.</p>
HTML
post_id="'$(wp post create '"\\
  --post_type=post \\
  --post_status=publish \\
  --post_author=2 \\
  --post_title='How to Prepare for a Youth or Kids Wednesday Night Program' \\
  --post_name=\""'$slug" '"\\
  --post_excerpt=\"A practical, step-by-step checklist for families preparing for Ridgecrest Wednesday Night Kids or Youth programs, including what to bring, how check-in typically works, and how to handle communication, pickup, and first-time questions.\" \\
  --post_content=\""'$(cat "$html_file")" '"\\
  --porcelain)
wp post meta update \""'$post_id" _thumbnail_id 9 >/dev/null
rm -f "$html_file"
printf '"'CREATED:%s\\n' \""'$post_id"
' in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 1946ms:
CREATED:88

codex
The post is published. I’m in the verification pass now: confirming the stored content, public URL, featured image, inline image ID, Blog index visibility, and that the exact required external URL survived into the rendered article body.
exec
/bin/bash -lc "printf '%s\\n' '--- POST GET ---' && wp post get 88 --fields=ID,post_title,post_name,post_status,post_author,post_date,post_excerpt --format=json && printf '\\n--- POST URL ---\\n' && wp post url 88 && printf '\\n--- THUMBNAIL ---\\n' && wp post meta get 88 _thumbnail_id && printf '\\n--- CONTENT CHECK ---\\n' && wp post get 88 --field=post_content | rg -n 'events-calendar|news\\.html|contacts\\.html|about\\.html|kids\\.html|youth\\.html|flatlogic\\.com/generator\\?utm_source=ridgecrestchurch\\.com|wp-image-9|<figure'" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc 'post_url=$(wp post url 88)
printf '"'POST_URL=%s\\n' \""'$post_url"
printf '"'\\n--- POST HEAD ---\\n'
curl -I -L \""'$post_url"
printf '"'\\n--- POST BODY CHECK ---\\n'
curl -L \""'$post_url" | rg -n '"'How to Prepare for a Youth or Kids Wednesday Night Program|flatlogic\\.com/generator\\?utm_source=ridgecrestchurch\\.com|wp-image-9|church-exterior\\.jpg|events-calendar|contacts|news|kids|youth'" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "printf '%s\\n' '--- BLOG PAGE ---' && wp post get 23 --fields=ID,post_title,post_status,post_name --format=json && printf '\\nPAGE_FOR_POSTS=' && wp option get page_for_posts && printf '\\n\\n--- BLOG BODY CHECK ---\\n' && curl -L https://ridgecrestchurch.com/blog/ | rg -n 'How to Prepare for a Youth or Kids Wednesday Night Program|prepare-for-wednesday-kids-youth'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 1576ms:
POST_URL=https://ridgecrestchurch.com/prepare-for-wednesday-kids-youth/

--- POST HEAD ---
  % 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    HTTP/2 200 
date: Sun, 24 May 2026 18:03:45 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/88>; rel="alternate"; title="JSON"; type="application/json", <https://ridgecrestchurch.com/?p=88>; 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=YbqDjLc6Enz59so%2F48BwCFRgil9csbmQC53r%2BtN1O31BQ%2FV40bFYs%2FxCQX7cY2nvC8EvIzD82IjjiN4v3czCV6%2BxcmQuMubngM5ZsvjXoRauyfZGO9Ea8gQbwhoMppHLEB%2BU9dv72w%3D%3D"}]}
nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
cf-ray: a00e38093eba0258-WAW
alt-svc: h3=":443"; ma=86400

  0 --:--:-- --:--:-- --:--:--     0

--- POST 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 16401    0 16401    0     0  30934      0 --:--:-- --:--:-- --:--:-- 3088712:	<title>How to Prepare for a Youth or Kids Wednesday Night Program - Ridgecrest Baptist Church</title>
13:	<link rel="canonical" href="https://ridgecrestchurch.com/prepare-for-wednesday-kids-youth/" />
16:	<meta property="og:title" content="How to Prepare for a Youth or Kids Wednesday Night Program" />
18:	<meta property="og:url" content="https://ridgecrestchurch.com/prepare-for-wednesday-kids-youth/" />
21:	<meta property="og:image" content="https://ridgecrestchurch.com/wp-content/uploads/imports/church-exterior.jpg" />
31:	<script type="application/ld+json" class="yoast-schema-graph">{"@context":"https://schema.org","@graph":[{"@type":"Article","@id":"https://ridgecrestchurch.com/prepare-for-wednesday-kids-youth/#article","isPartOf":{"@id":"https://ridgecrestchurch.com/prepare-for-wednesday-kids-youth/"},"author":{"name":"Lena Ortiz","@id":"https://ridgecrestchurch.com/#/schema/person/2a935d6e541854224fd9589d7c87dde4"},"headline":"How to Prepare for a Youth or Kids Wednesday Night Program","datePublished":"2026-05-24T18:03:30+00:00","mainEntityOfPage":{"@id":"https://ridgecrestchurch.com/prepare-for-wednesday-kids-youth/"},"wordCount":1833,"publisher":{"@id":"https://ridgecrestchurch.com/#organization"},"image":{"@id":"https://ridgecrestchurch.com/prepare-for-wednesday-kids-youth/#primaryimage"},"thumbnailUrl":"https://ridgecrestchurch.com/wp-content/uploads/imports/church-exterior.jpg","inLanguage":"en-US"},{"@type":"WebPage","@id":"https://ridgecrestchurch.com/prepare-for-wednesday-kids-youth/","url":"https://ridgecrestchurch.com/prepare-for-wednesday-kids-youth/","name":"How to Prepare for a Youth or Kids Wednesday Night Program - Ridgecrest Baptist Church","isPartOf":{"@id":"https://ridgecrestchurch.com/#website"},"primaryImageOfPage":{"@id":"https://ridgecrestchurch.com/prepare-for-wednesday-kids-youth/#primaryimage"},"image":{"@id":"https://ridgecrestchurch.com/prepare-for-wednesday-kids-youth/#primaryimage"},"thumbnailUrl":"https://ridgecrestchurch.com/wp-content/uploads/imports/church-exterior.jpg","datePublished":"2026-05-24T18:03:30+00:00","breadcrumb":{"@id":"https://ridgecrestchurch.com/prepare-for-wednesday-kids-youth/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https://ridgecrestchurch.com/prepare-for-wednesday-kids-youth/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https://ridgecrestchurch.com/prepare-for-wednesday-kids-youth/#primaryimage","url":"https://ridgecrestchurch.com/wp-content/uploads/imports/church-exterior.jpg","contentUrl":"https://ridgecrestchurch.com/wp-content/uploads/imports/church-exterior.jpg","width":2250,"height":1500,"caption":"Main entrance and covered walkway at Ridgecrest Baptist Church in Blanchard, Oklahoma"},{"@type":"BreadcrumbList","@id":"https://ridgecrestchurch.com/prepare-for-wednesday-kids-youth/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://ridgecrestchurch.com/"},{"@type":"ListItem","position":2,"name":"Blog","item":"https://ridgecrestchurch.com/blog/"},{"@type":"ListItem","position":3,"name":"How to Prepare for a Youth or Kids Wednesday Night Program"}]},{"@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/2a935d6e541854224fd9589d7c87dde4","name":"Lena Ortiz","description":"Lena writes decision guides that help readers compare options, understand tradeoffs, and avoid expensive operational mistakes.","url":"https://ridgecrestchurch.com/author/lena-ortiz/"}]}</script>
88:<link rel="alternate" title="oEmbed (JSON)" type="application/json+oembed" href="https://ridgecrestchurch.com/wp-json/oembed/1.0/embed?url=https%3A%2F%2Fridgecrestchurch.com%2Fprepare-for-wednesday-kids-youth%2F" />
406:<li id="menu-item-43" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-43"><a href="https://ridgecrestchurch.com/kids/">Kids</a></li>
407:<li id="menu-item-44" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-44"><a href="https://ridgecrestchurch.com/youth/">Youth</a></li>
408:<li id="menu-item-45" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-45"><a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a></li>
409:<li id="menu-item-46" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-46"><a href="https://ridgecrestchurch.com/news/">News</a></li>
411:<li id="menu-item-48" class="menu-item menu-item-type-post_type menu-item-object-page menu-item-48"><a href="https://ridgecrestchurch.com/contacts/">Contacts</a></li>
416:			<img width="2250" height="1500" src="https://ridgecrestchurch.com/wp-content/uploads/imports/church-exterior.jpg" class="attachment-full size-full wp-post-image" alt="Main entrance and covered walkway at Ridgecrest Baptist Church in Blanchard, Oklahoma" decoding="async" fetchpriority="high" itemprop="image" />		</div><!-- .wrap -->
421:			<header class="entry-header">	<h1 class="entry-title" itemprop="headline">How to Prepare for a Youth or Kids Wednesday Night Program</h1>
430:<p>The weekly details still matter most. Before you leave home, verify the specific Wednesday on the <a href="/events-calendar/">Events Calendar</a> and scan <a href="/news.html">News</a> for reminders or schedule changes. Last-minute questions are easier when you have already checked the listing.</p>
432:  <img decoding="async" width="2250" height="1500" data-src="https://ridgecrestchurch.com/wp-content/uploads/imports/church-exterior.jpg" alt="Main entrance and covered walkway at Ridgecrest Baptist Church in Blanchard, Oklahoma" class="wp-image-9 lazyload" src="data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==" style="--smush-placeholder-width: 2250px; --smush-placeholder-aspect-ratio: 2250/1500;" /><figcaption>The main entrance is a useful visual reference if you are planning where to arrive before Wednesday Night begins.</figcaption></figure>
434:<p>If your family is heading to <a href="/kids.html">Kids</a> or <a href="/youth.html">Youth</a> on a Wednesday evening, the reasonable default is to think in phases rather than trying to memorize a hundred tiny details. In most cases, the evening works like this:</p>
441:<p>The site’s current pages give a few stable reference points. Ridgecrest’s <a href="/kids.html">Kids</a> page says preschool meets in the main building and kindergarten through 5th grade meets in the children’s building beginning at 6:30 p.m. The <a href="/youth.html">Youth</a> page says students in 6th through 12th grade also gather beginning at 6:30 p.m. Even so, the safest practice is still to verify the specific Wednesday on the calendar and news pages before you head out.</p>
445:<li><strong>Start with <a href="/events-calendar/">the Events Calendar</a>.</strong> Confirm the Wednesday Night listing, timing, and whether the note points you to another page.</li>
100 50445    0 50445    0     0  94825      0 --:--:-- --:--:-- --:--:-- 94821
446:<li><strong>Then read <a href="/news.html">News</a>.</strong> Use it to catch reminders, highlights, or any church-wide announcement that might affect the evening.</li>
448:<li><strong>If anything still feels unclear, use <a href="/contacts.html">Contacts</a> before you leave home.</strong> Asking one direct question is better than guessing three policies in the parking lot.</li>
461:<p>If the <a href="/events-calendar/">Events Calendar</a> or <a href="/news.html">News</a> page mentions something specific for that week, follow that instruction over any general checklist. The recurring plan is helpful, but the current note wins.</p>
462:<p>Some families also prefer a simple digital checklist so nothing gets missed during the dinner-to-carpool transition. If that is your style, this neutral resource on a <a href="https://flatlogic.com/generator?utm_source=ridgecrestchurch.com">web app generator</a> can help you sketch a private reminder workflow for your household.</p>
480:<p>If plans change on the way to church, or if you realize you need to ask before you arrive, the fastest clean path is the <a href="/contacts.html">Contacts</a> page. The site currently lists <code><a href="/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="c8a9aca5a1a688baa1acafadabbaadbbbcaba0bdbaaba0e6aba7a5">[email&#160;protected]</a></code> and <code>(405) 387-2811</code>, which is more reliable than trying to locate the right person after the program is already moving.</p>
515:<p>If you want ministry-specific background before the first week, the <a href="/kids.html">Kids</a> and <a href="/youth.html">Youth</a> pages give a more complete picture of how Ridgecrest describes each ministry.</p>
519:<li><strong>Start with <a href="/contacts.html">Contacts</a>.</strong> That page has the current phone number, email address, and physical address.</li>
533:<p>If someone else needs to pick up your child or student, do not rely on improvisation. Follow the church’s process for that Wednesday if it is listed, or contact the church ahead of time through <a href="/contacts.html">Contacts</a>. The point is to reduce confusion, not create a dramatic reveal at the end of the night.</p>
536:<p>Use <a href="/contacts.html">Contacts</a> and include:</p>
559:<li>Check <a href="/events-calendar/">the Events Calendar</a> for the specific Wednesday Night listing.</li>
560:<li>Read <a href="/news.html">News</a> for reminders, special notes, or schedule changes.</li>
561:<li>Review <a href="/kids.html">Kids</a> or <a href="/youth.html">Youth</a> if this is your first week.</li>
565:<li>Use <a href="/contacts.html">Contacts</a> for questions, changes, allergies, or accessibility needs.</li>
576:	<footer id="footer" class="site-footer" role="contentinfo" itemscope="itemscope" itemtype="http://schema.org/WPFooter"><div class="wrap"><div class="footer-content footer-insert"><p class="copyright">Copyright &#169; 2026 Ridgecrest Baptist Church.</p><p class="rc-footer-contact">Questions? <a href="/cdn-cgi/l/email-protection#e786838a8e89a7958e8380828495829493848f9295848fc984888a"><span class="__cf_email__" data-cfemail="ec8d88818582ac9e85888b898f9e899f988f84999e8f84c28f8381">[email&#160;protected]</span></a> | (405) 387-2811</p><p class="rc-footer-links"><a href="https://ridgecrestchurch.com/contacts/">Contact</a> <a href="https://ridgecrestchurch.com/privacy-policy/">Privacy Policy</a> <a href="https://ridgecrestchurch.com/terms-of-use/">Terms of Use</a> <a href="https://ridgecrestchurch.com/cookie-policy/">Cookie Policy</a></p></div></div></footer><!-- .site-footer --></div><!-- .site-container -->

 succeeded in 1666ms:
{"ID":23,"post_title":"Blog","post_status":"publish","post_name":"blog"}

PAGE_FOR_POSTS=23


--- BLOG 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 10934    0 10934    0     0  19789      0 --:--:-- --:--:-- --:--:-- 19772100 45348    0 45348    0     0  81866      0 --:--:-- --:--:-- --:--:-- 81855
413:			<header class="entry-header">	<h2 class="entry-title" itemprop="headline"><a href="https://ridgecrestchurch.com/prepare-for-wednesday-kids-youth/" rel="bookmark">How to Prepare for a Youth or Kids Wednesday Night Program</a></h2>
419:<a href="https://ridgecrestchurch.com/prepare-for-wednesday-kids-youth/" title="How to Prepare for a Youth or Kids Wednesday Night Program"><img width="2250" height="1500" data-src="https://ridgecrestchurch.com/wp-content/uploads/imports/church-exterior.jpg" class="wp-post-image lazyload" alt="Main entrance and covered walkway at Ridgecrest Baptist Church in Blanchard, Oklahoma" decoding="async" itemprop="image" src="data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==" style="--smush-placeholder-width: 2250px; --smush-placeholder-aspect-ratio: 2250/1500;" /></a><p>A practical, step-by-step checklist for families preparing for Ridgecrest Wednesday Night Kids or Youth programs, including what to bring, how check-in typically works, and how to handle communication, pickup, and first-time questions.</p>

 succeeded in 2238ms:
{"ID":88,"post_author":"2","post_date":"2026-05-24 13:03:30","post_title":"How to Prepare for a Youth or Kids Wednesday Night Program","post_excerpt":"A practical, step-by-step checklist for families preparing for Ridgecrest Wednesday Night Kids or Youth programs, including what to bring, how check-in typically works, and how to handle communication, pickup, and first-time questions.","post_status":"publish","post_name":"prepare-for-wednesday-kids-youth"}

--- POST URL ---
https://ridgecrestchurch.com/prepare-for-wednesday-kids-youth/

--- THUMBNAIL ---
9

--- CONTENT CHECK ---
7:<p>The weekly details still matter most. Before you leave home, verify the specific Wednesday on the <a href="/events-calendar/">Events Calendar</a> and scan <a href="/news.html">News</a> for reminders or schedule changes. Last-minute questions are easier when you have already checked the listing.</p>
9:<figure class="wp-block-image size-large">
10:  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/church-exterior.jpg" alt="Main entrance and covered walkway at Ridgecrest Baptist Church in Blanchard, Oklahoma" class="wp-image-9" />
16:<p>If your family is heading to <a href="/kids.html">Kids</a> or <a href="/youth.html">Youth</a> on a Wednesday evening, the reasonable default is to think in phases rather than trying to memorize a hundred tiny details. In most cases, the evening works like this:</p>
25:<p>The site’s current pages give a few stable reference points. Ridgecrest’s <a href="/kids.html">Kids</a> page says preschool meets in the main building and kindergarten through 5th grade meets in the children’s building beginning at 6:30 p.m. The <a href="/youth.html">Youth</a> page says students in 6th through 12th grade also gather beginning at 6:30 p.m. Even so, the safest practice is still to verify the specific Wednesday on the calendar and news pages before you head out.</p>
32:  <li><strong>Start with <a href="/events-calendar/">the Events Calendar</a>.</strong> Confirm the Wednesday Night listing, timing, and whether the note points you to another page.</li>
33:  <li><strong>Then read <a href="/news.html">News</a>.</strong> Use it to catch reminders, highlights, or any church-wide announcement that might affect the evening.</li>
34:  <li><strong>If you are new to Ridgecrest, review <a href="/about.html">About Us</a>.</strong> It gives helpful context for how the church approaches family ministry without turning this article into a general first-visit guide.</li>
35:  <li><strong>If anything still feels unclear, use <a href="/contacts.html">Contacts</a> before you leave home.</strong> Asking one direct question is better than guessing three policies in the parking lot.</li>
53:<p>If the <a href="/events-calendar/">Events Calendar</a> or <a href="/news.html">News</a> page mentions something specific for that week, follow that instruction over any general checklist. The recurring plan is helpful, but the current note wins.</p>
55:<p>Some families also prefer a simple digital checklist so nothing gets missed during the dinner-to-carpool transition. If that is your style, this neutral resource on a <a href="https://flatlogic.com/generator?utm_source=ridgecrestchurch.com">web app generator</a> can help you sketch a private reminder workflow for your household.</p>
80:<p>If plans change on the way to church, or if you realize you need to ask before you arrive, the fastest clean path is the <a href="/contacts.html">Contacts</a> page. The site currently lists <code>admin@ridgecrestchurch.com</code> and <code>(405) 387-2811</code>, which is more reliable than trying to locate the right person after the program is already moving.</p>
120:<p>If you want ministry-specific background before the first week, the <a href="/kids.html">Kids</a> and <a href="/youth.html">Youth</a> pages give a more complete picture of how Ridgecrest describes each ministry.</p>
127:  <li><strong>Start with <a href="/contacts.html">Contacts</a>.</strong> That page has the current phone number, email address, and physical address.</li>
147:<p>If someone else needs to pick up your child or student, do not rely on improvisation. Follow the church’s process for that Wednesday if it is listed, or contact the church ahead of time through <a href="/contacts.html">Contacts</a>. The point is to reduce confusion, not create a dramatic reveal at the end of the night.</p>
153:<p>Use <a href="/contacts.html">Contacts</a> and include:</p>
184:  <li>Check <a href="/events-calendar/">the Events Calendar</a> for the specific Wednesday Night listing.</li>
185:  <li>Read <a href="/news.html">News</a> for reminders, special notes, or schedule changes.</li>
186:  <li>Review <a href="/kids.html">Kids</a> or <a href="/youth.html">Youth</a> if this is your first week.</li>
190:  <li>Use <a href="/contacts.html">Contacts</a> for questions, changes, allergies, or accessibility needs.</li>

codex
Published a new post, “How to Prepare for a Youth or Kids Wednesday Night Program,” under `Lena Ortiz` with a practical checklist structure focused on preparation, arrival/check-in, communication, pickup, allergies/accessibility, and first-time questions. The post includes the required internal links to Events Calendar, News, Contacts, About, Kids, and Youth, plus one exact contextual Flatlogic body link. I used the existing Ridgecrest campus entrance photo as both the featured image and a visible inline figure because it was the closest credible local media match for an arrival-oriented article.

Verified with `wp post get`, `wp post url`, a live `curl` check on the post URL, and a `/blog/` index check. The Blog page was already configured correctly at `/blog/` with `page_for_posts=23`, and the new post appears there. Remaining uncertainty: the image is a campus entrance photo rather than a true Wednesday check-in/family-arrival scene, but it is real, relevant, already in the media library, and renders correctly inline. Backlink restoration target `/` was not changed in this task.

WP_POST_ID: 88
WP_POST_STATUS: publish
WP_POST_URL: https://ridgecrestchurch.com/prepare-for-wednesday-kids-youth/
WP_AUTHOR_USER: lena-ortiz / Lena Ortiz
FEATURED_IMAGE_ID: 9
INLINE_IMAGE_IDS: 9
BLOG_INDEX_STATUS: ready; https://ridgecrestchurch.com/blog/ is live, Blog page ID 23, page_for_posts=23, new post visible on index
LINK_TARGETS_USED: https://flatlogic.com/generator?utm_source=ridgecrestchurch.com
tokens used
202,121
