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: 019e18a0-21fe-7bd2-b973-6b99c3f9538e
--------
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-36/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)

## Article Request

- Topic: How to Plan a Great Sunday: A Simple Church Service Checklist
- 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 91 as the source of truth. Planner angle: Practical, ministry-focused guide for volunteers and staff to coordinate worship, announcements, kids/youth handoffs, and follow-up Article kind: evergreen Research status: not_required Reader intent: Help church leaders and volunteers organize a smooth Sunday service with clear steps and roles Planned 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) 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). Preferred internal links: /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

## Selected Article Content Plan Item

- Plan item ID: 91
- Plan order: 1
- Article kind: evergreen
- Planned title: How to Plan a Great Sunday: A Simple Church Service Checklist
- 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: Use the selected virtual author.

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

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)

Preferred 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

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: Grant Vale
Slug: grant-vale
Role: Infrastructure reliability writer
Language: English
Public bio: Grant covers website reliability, backups, domains, security basics, and the operational habits that keep online services steady.
Character formula: Reliability Guardian Ruler
Formula: Guardian + Ruler
Meaning: A disciplined protector voice focused on risk, continuity, backups, domains, SSL, and operational control.
Worldview: Websites stay trustworthy when people respect systems, ownership, backups, and failure modes.
Voice guidance: Steady, methodical, risk-aware, direct, protective. Use checklists, priority order, and consequence-aware language.
Humor: Minimal dry operational humor; never jokey around safety or security.
Shadow tension: Can become rigid or alarmist; keep risk concrete rather than fear-driven.
Usage notes: Best for security basics, uptime, DNS, SSL, backups, and incident-prevention articles.
Archetype blend: Guardian + Ruler
Standard archetype voice guidance:

Primary archetype card: Guardian
Meaning: The defender who protects a person, place, secret, oath, or boundary.
First-person lens: While I stand, they do not pass; I do not need songs, only the line held.
Traits: loyal, watchful, disciplined, brave, stubborn
Worldview: The world is full of threats, and someone must face the door.
Self-relation: If I fail to protect, I may not know what I am.
Language patterns: Behind me; Not another step; I gave my word; Stay close
Humor: Dry, understated, sometimes grim.
Shadow risk to avoid unless intentionally requested: Rigidity, overprotection, preventing growth.

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 sound too stern if the topic becomes simple; should stay protective rather than alarmist.
Worldview: Most digital problems are easier to prevent than to recover from, but panic is not a plan.
Reader relationship: Protective operations lead helping the reader reduce risk without feeling foolish.
Humor style: Minimal dry humor, mostly around preventable messes and backup discipline.
Voice traits: steady, risk-aware, direct, methodical
Vocabulary / recurring language: failure mode, baseline, rollback, recovery path, minimum safe setup
Avoid voice: fearmongering, military cosplay, absolute guarantees, patronizing warnings
CTA style: Invite the reader to verify their current setup, document one recovery path, or ask for help before a risky change.
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: Steady, protective, systems-minded, and allergic to preventable chaos.
Writing style: Structured risk-first articles with priorities, failure modes, maintenance steps, and clear escalation points.
Expertise topics: website backups, DNS, SSL, hosting reliability, basic web security, incident prevention
Avoid topics: advanced exploit instructions, unverified security claims, legal compliance guarantees
Tone tags: protective, disciplined, clear, trustworthy
Private operator notes: Good for security/backups/domains/DNS/reliability posts.

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`: `grant-vale`.
- Suggested `display_name`: `Grant Vale`.
- 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`.

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

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

codex
I’m reading the site and article instructions first, then I’ll inspect the WordPress setup and implement the post directly with `wp-cli`.
exec
/bin/bash -lc "printf '--- TASK ---\\n' && sed -n '1,260p' wp-content/uploads/flatlogic-article-tasks/job-36/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 \\( -iname '*.md' -o -iname '*.markdown' \\) | sort" in /home/ubuntu/apps/ridgecrestchurch.com
 exited 2 in 0ms:
/bin/bash: line 1: printf: --: invalid option
printf: usage: printf [-v var] format [arguments]

exec
/bin/bash -lc "pwd && ls -la && printf '\\n--- SITE_CONTEXT.md ---\\n' && sed -n '1,220p' SITE_CONTEXT.md && printf '\\n--- AGENTS.md ---\\n' && sed -n '1,220p' AGENTS.md && printf '\\n--- ARTICLE_CONTENT_PLAN.md ---\\n' && sed -n '1,260p' ARTICLE_CONTENT_PLAN.md" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
/home/ubuntu/apps/ridgecrestchurch.com
total 380
drwxrwsr-x  6 ubuntu www-data  4096 May  8 18:10 .
drwxrwsr-x 13 ubuntu www-data  4096 May 11 09:51 ..
-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 11 20:00 AGENTS.md
-rw-rw-r--  1 ubuntu www-data 66138 May 11 20:00 ARTICLE_CONTENT_PLAN.md
-rw-rw-r--  1 ubuntu www-data 46551 May 11 20: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

--- SITE_CONTEXT.md ---
# 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

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

--- ARTICLE_CONTENT_PLAN.md ---

# 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: 29
- Queued/running/scheduled: 1
- Published: 0
- Failed: 0
- 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: queued
- 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: none
- WordPress post URL: none
- 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: planned
- 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: none
- Article job ID: none
- WordPress post URL: none
- 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: planned
- 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: none
- Article job ID: none
- WordPress post URL: none
- 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: planned
- 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: none
- Article job ID: none
- WordPress post URL: none
- 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: planned
- Article kind: research_trend
- Research status: pending
- 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



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: planned
- 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: none
- Article job ID: none
- WordPress post URL: none
- Researched at: none



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

codex
The site plan matches the requested article. I still need the post-creator plugin instructions and context markdown before I touch WordPress content or media.
exec
/bin/bash -lc "sed -n '1,260p' wp-content/uploads/flatlogic-article-tasks/job-36/task.md" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
# Article Generation Task

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

## Required Runtime

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

## Site Contract

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

## Backlink Targets To Respect

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

## Article Request

- Topic: How to Plan a Great Sunday: A Simple Church Service Checklist
- 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 91 as the source of truth. Planner angle: Practical, ministry-focused guide for volunteers and staff to coordinate worship, announcements, kids/youth handoffs, and follow-up Article kind: evergreen Research status: not_required Reader intent: Help church leaders and volunteers organize a smooth Sunday service with clear steps and roles Planned 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) 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). Preferred internal links: /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

## Selected Article Content Plan Item

- Plan item ID: 91
- Plan order: 1
- Article kind: evergreen
- Planned title: How to Plan a Great Sunday: A Simple Church Service Checklist
- 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: Use the selected virtual author.

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

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)

Preferred 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

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: Grant Vale
Slug: grant-vale
Role: Infrastructure reliability writer
Language: English
Public bio: Grant covers website reliability, backups, domains, security basics, and the operational habits that keep online services steady.
Character formula: Reliability Guardian Ruler
Formula: Guardian + Ruler
Meaning: A disciplined protector voice focused on risk, continuity, backups, domains, SSL, and operational control.
Worldview: Websites stay trustworthy when people respect systems, ownership, backups, and failure modes.
Voice guidance: Steady, methodical, risk-aware, direct, protective. Use checklists, priority order, and consequence-aware language.
Humor: Minimal dry operational humor; never jokey around safety or security.
Shadow tension: Can become rigid or alarmist; keep risk concrete rather than fear-driven.
Usage notes: Best for security basics, uptime, DNS, SSL, backups, and incident-prevention articles.
Archetype blend: Guardian + Ruler
Standard archetype voice guidance:

Primary archetype card: Guardian
Meaning: The defender who protects a person, place, secret, oath, or boundary.
First-person lens: While I stand, they do not pass; I do not need songs, only the line held.
Traits: loyal, watchful, disciplined, brave, stubborn
Worldview: The world is full of threats, and someone must face the door.
Self-relation: If I fail to protect, I may not know what I am.
Language patterns: Behind me; Not another step; I gave my word; Stay close
Humor: Dry, understated, sometimes grim.
Shadow risk to avoid unless intentionally requested: Rigidity, overprotection, preventing growth.

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 sound too stern if the topic becomes simple; should stay protective rather than alarmist.
Worldview: Most digital problems are easier to prevent than to recover from, but panic is not a plan.
Reader relationship: Protective operations lead helping the reader reduce risk without feeling foolish.
Humor style: Minimal dry humor, mostly around preventable messes and backup discipline.
Voice traits: steady, risk-aware, direct, methodical
Vocabulary / recurring language: failure mode, baseline, rollback, recovery path, minimum safe setup
Avoid voice: fearmongering, military cosplay, absolute guarantees, patronizing warnings
CTA style: Invite the reader to verify their current setup, document one recovery path, or ask for help before a risky change.
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: Steady, protective, systems-minded, and allergic to preventable chaos.
Writing style: Structured risk-first articles with priorities, failure modes, maintenance steps, and clear escalation points.
Expertise topics: website backups, DNS, SSL, hosting reliability, basic web security, incident prevention
Avoid topics: advanced exploit instructions, unverified security claims, legal compliance guarantees
Tone tags: protective, disciplined, clear, trustworthy
Private operator notes: Good for security/backups/domains/DNS/reliability posts.

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`: `grant-vale`.
- Suggested `display_name`: `Grant Vale`.
- 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`.

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

Also briefly mention what you verified and any limitations.
exec
/bin/bash -lc "sed -n '1,260p' wp-content/plugins/flatlogic-post-creator/INSTRUCTIONS.MD" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
# Flatlogic Post Creator

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

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

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

## Required Reading

Before changing anything:

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

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

## Target Contract

Identify each target post before writing:

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

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

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

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

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

## Content Rules

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

## WordPress Implementation

Use `wp-cli` where practical.

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

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

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

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

Minimum checks:

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

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

Recommended commands:

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

For legacy/backlink URLs:

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

## Images

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

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

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

## Links

- Use useful internal links to related pages and posts.
- Use provided link targets naturally and sparingly.
- Keep provided Flatlogic target URLs exactly as rendered, including `utm_source`.
- Do not place Flatlogic or AppWizzy links in the footer.
- 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.

exec
/bin/bash -lc "find wp-content/plugins/flatlogic-post-creator/context -maxdepth 1 -type f \\( -iname '*.md' -o -iname '*.markdown' \\) | sort" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
wp-content/plugins/flatlogic-post-creator/context/FINAL_REQUIREMENTS.MD
wp-content/plugins/flatlogic-post-creator/context/PRINCIPLES.md

codex
I have the task contract and plugin rules. Next I’m loading the post-creator principles and then checking the live WordPress state, page slugs, authors, and existing media so the post can be created with the right links and image.
exec
/bin/bash -lc "sed -n '1,240p' wp-content/plugins/flatlogic-post-creator/context/PRINCIPLES.md && printf '\\n---\\n' && sed -n '1,240p' wp-content/plugins/flatlogic-post-creator/context/FINAL_REQUIREMENTS.MD" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
Here’s the writer SOP I’d hand to someone who has to produce a serious, quotable article.

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

## Operating definitions

Use these before you write a word.

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

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

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

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

My recommended floor for a serious non-breaking article:

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

That is my operating minimum, not a universal law.

---

## 1. Why this story exists

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

### 1.1 Ask

Write down answers to these, in one sentence each:

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

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

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

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

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

### 1.2 Write

Create a 5-line assignment brief:

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

### 1.3 Produce

A one-sentence story brief:

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

### 1.4 Gate

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

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

Kill or reframe.

---

## 2. Convert the topic into a question tree

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

### 2.1 Ask

Turn the topic into a precise question.

Bad:

* “AI code editors vs traditional IDEs”

Better:

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

### 2.2 Build the tree

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

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

### 2.3 Write two counterweights

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

Example:

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

### 2.4 Gate

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

---

## 3. Build the evidence matrix before collecting facts

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

### 3.1 Create a matrix

Make a table or spreadsheet with these columns:

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

### 3.2 Use a source hierarchy

Rank sources like this:

**Tier A — primary**

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

**Tier B — on-record participants**

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

**Tier C — independent interpreters**

* analysts
* academics
* domain experts
* critics

**Tier D — secondary synthesis**

* other articles
* industry reports
* commentary

### 3.3 Use a support rule

My recommended rule for each material claim:

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

### 3.4 Gate

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

---

## 4. Scan the field and locate the gap

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

### 4.1 Search in this order

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

### 4.2 For each existing article, extract

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

### 4.3 Produce a “gap memo”

Write 5 bullets:

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

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

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

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

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

2. Table of contents
   *Generated automatically

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

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

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

2. Item description – obligatory

Describe the item in 1-3 paragraphs.

____________

One of the options below is obligatory

Option 1

3.1.1 Item pros:

Describe the item’s pros in 2-4 sentences

3.1.2 Item cons:

Describe the item’s cons in 2-4 sentences

Option 2

3.2 Key features:

Feature 1
Feature 2
Feature 3
etc
__________

Additional

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

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

exec
/bin/bash -lc "wp core is-installed && printf '\\nHOME=' && wp option get home && printf '\\nSITEURL=' && wp option get siteurl && printf '\\nSHOW_ON_FRONT=' && wp option get show_on_front && printf '\\nPAGE_ON_FRONT=' && wp option get page_on_front && printf '\\nPAGE_FOR_POSTS=' && wp option get page_for_posts && printf '\\n\\nACTIVE THEME\\n' && wp theme list --status=active && printf '\\nDB PREFIX=' && wp db prefix && printf '\\n\\nPAGES\\n' && wp post list --post_type=page --fields=ID,post_title,post_name,post_status --format=table && printf '\\n\\nPOSTS\\n' && wp post list --post_type=post --fields=ID,post_title,post_name,post_status --format=table" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "printf 'USERS\\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,post_date --format=table | sed -n '1,120p'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 1073ms:
ID	user_login	display_name	user_email	roles
1	admin	admin	admin@ridgecrestchurch.com	administrator
2	lena-ortiz	Lena Ortiz	lena-ortiz@ridgecrestchurch.com	author

ATTACHMENTS
ID	post_title	post_mime_type	post_date
1	Ridgecrest Baptist Church Logo	image/gif	2026-05-07 04:47:01
2	Ridgecrest Service Times	image/gif	2026-05-07 04:47:01
3	Ridgecrest Events Calendar	image/gif	2026-05-07 04:47:01
4	Ridgecrest Connection Graphic	image/gif	2026-05-07 04:47:01
5	Ridgecrest Sermons Graphic	image/gif	2026-05-07 04:47:01
6	Ridgecrest Contact Graphic	image/gif	2026-05-07 04:47:01
7	Ridgecrest Map Graphic	image/gif	2026-05-07 04:47:01
8	Ridgecrest Community Illustration	image/jpeg	2026-05-07 04:47:01
9	Church Exterior	image/jpeg	2026-05-07 04:47:01
10	Worship Service	image/jpeg	2026-05-07 04:47:01
11	Children Ministry	image/jpeg	2026-05-07 04:47:01
12	Youth Worship	image/jpeg	2026-05-07 04:47:01

codex
The plugin context includes some generic article boilerplate, but the stricter site/task contract still governs. I’m using only the parts that fit this church site: clear structure, useful headings/lists, and a real inline image.
 succeeded in 9691ms:

HOME=https://ridgecrestchurch.com

SITEURL=https://ridgecrestchurch.com

SHOW_ON_FRONT=page

PAGE_ON_FRONT=13

PAGE_FOR_POSTS=23


ACTIVE THEME
name	status	update	version	update_version	auto_update
church	active	none	0.7.7		off

DB PREFIX=flbg_


PAGES
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


POSTS
ID	post_title	post_name	post_status
74	How to Plan Your First Visit to Ridgecrest Baptist Church	first-visit-ridgecrest-baptist-church	publish
51	Welcome to Ridgecrest News	welcome-to-ridgecrest-news	publish

codex
I’ve confirmed `/blog/` already exists and is set as the posts index, so this stays a contained post-and-media change. I’m checking actual page URLs and media assets now to decide whether an existing site photo is good enough or whether I need to import a better checklist photo.
exec
/bin/bash -lc "find wp-content/uploads -maxdepth 3 -type f | sed -n '1,200p'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
wp-content/uploads/imports/contact-info.gif
wp-content/uploads/imports/service-times.gif
wp-content/uploads/imports/youth-worship.jpg
wp-content/uploads/imports/youth-group.jpg
wp-content/uploads/imports/events.gif
wp-content/uploads/imports/map-directions.gif
wp-content/uploads/imports/sermons.gif
wp-content/uploads/imports/logo.gif
wp-content/uploads/imports/groups.jpg
wp-content/uploads/imports/church-exterior.jpg
wp-content/uploads/imports/children-ministry.jpg
wp-content/uploads/imports/connect.gif
wp-content/uploads/imports/worship-service.jpg
wp-content/uploads/flatlogic-article-tasks/job-25/check-article-image.php
wp-content/uploads/flatlogic-article-tasks/job-25/task.md
wp-content/uploads/flatlogic-article-tasks/job-25/first-visit-post.html
wp-content/uploads/flatlogic-article-tasks/job-36/task.md
wp-content/uploads/flatlogic-page-tasks/job-44/task.md
wp-content/uploads/flatlogic-page-tasks/job-44/build_site.php
wp-content/uploads/flatlogic-site-polish-tasks/job-44/task.md

exec
/bin/bash -lc "wp eval '
"'$ids = [8,9,10,11,12];
foreach ($ids as $id) {
  $path = get_attached_file($id);
  $url = wp_get_attachment_url($id);
  $alt = get_post_meta($id, "_wp_attachment_image_alt", true);
  echo "ID:$id'"\\nURL:"'$url'"\\nPATH:"'$path'"\\nALT:"'$alt'"\\nTITLE:\" . get_the_title("'$id) . "'"\\n---\\n\";
}
'" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "for id in 14 16 17 18 19 20 23 10 11 12; do printf 'ID %s\\n' \""'$id"; wp post url "$id"; done' in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 572ms:
ID:8
URL:https://ridgecrestchurch.com/wp-content/uploads/imports/groups.jpg
PATH:/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/groups.jpg
ALT:Illustration representing gathered church community
TITLE:Ridgecrest Community Illustration
---
ID:9
URL:https://ridgecrestchurch.com/wp-content/uploads/imports/church-exterior.jpg
PATH:/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/church-exterior.jpg
ALT:Exterior view of Ridgecrest Baptist Church in Blanchard, Oklahoma
TITLE:Church Exterior
---
ID:10
URL:https://ridgecrestchurch.com/wp-content/uploads/imports/worship-service.jpg
PATH:/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/worship-service.jpg
ALT:Church worship service
TITLE:Worship Service
---
ID:11
URL:https://ridgecrestchurch.com/wp-content/uploads/imports/children-ministry.jpg
PATH:/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/children-ministry.jpg
ALT:Children participating in ministry activities at Ridgecrest Baptist Church
TITLE:Children Ministry
---
ID:12
URL:https://ridgecrestchurch.com/wp-content/uploads/imports/youth-worship.jpg
PATH:/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/imports/youth-worship.jpg
ALT:Students gathered for youth worship
TITLE:Youth Worship
---

 succeeded in 5260ms:
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/
ID 10
https://ridgecrestchurch.com/worship-service/
ID 11
https://ridgecrestchurch.com/children-ministry/
ID 12
https://ridgecrestchurch.com/youth-worship/

codex
Existing site photos are usable, but they don’t match the planned checklist angle very well. I’m making a real search for a better permissive photo before I settle; if I can’t find a credible fit quickly, I’ll fall back to the strongest existing church image and note that limitation.
exec
/bin/bash -lc "curl -L --silent 'https://api.openverse.org/v1/images/?q=clipboard%20checklist%20calendar%20smartphone&license_type=commercial&extension=jpg' | sed -n '1,120p'" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "curl -L --silent 'https://api.openverse.org/v1/images/?q=church%20clipboard%20checklist&license_type=commercial&extension=jpg' | sed -n '1,120p'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 701ms:
{"result_count":0,"page_count":0,"page_size":20,"page":1,"results":[]}
 succeeded in 724ms:
{"result_count":0,"page_count":0,"page_size":20,"page":1,"results":[]}
exec
/bin/bash -lc "curl -L --silent 'https://api.openverse.org/v1/images/?q=clipboard%20checklist&license_type=commercial&extension=jpg' | sed -n '1,180p'" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "curl -L --silent 'https://api.openverse.org/v1/images/?q=calendar%20clipboard%20phone&license_type=commercial&extension=jpg' | sed -n '1,180p'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 610ms:
{"result_count":0,"page_count":0,"page_size":20,"page":1,"results":[]}
 succeeded in 858ms:
{"result_count":30,"page_count":1,"page_size":20,"page":1,"results":[{"id":"dc3522f3-a976-49eb-a2c8-9e891896f980","title":"Black Clipboard","indexed_on":"2018-09-11T14:50:30.013406Z","foreign_landing_url":"https://www.flickr.com/photos/60141638@N06/9207097102","url":"https://live.staticflickr.com/2839/9207097102_0de3c758bc_m.jpg","creator":"One Way Stock","creator_url":"https://www.flickr.com/photos/60141638@N06","license":"by-nd","license_version":"2.0","license_url":"https://creativecommons.org/licenses/by-nd/2.0/","provider":"flickr","source":"flickr","category":null,"filesize":null,"filetype":null,"tags":[{"name":"business","accuracy":null,"unstable__provider":"flickr"},{"name":"checklist","accuracy":null,"unstable__provider":"flickr"},{"name":"clipboard","accuracy":null,"unstable__provider":"flickr"},{"name":"decisions","accuracy":null,"unstable__provider":"flickr"},{"name":"dropcap","accuracy":null,"unstable__provider":"flickr"},{"name":"leadership","accuracy":null,"unstable__provider":"flickr"},{"name":"list","accuracy":null,"unstable__provider":"flickr"},{"name":"organization","accuracy":null,"unstable__provider":"flickr"},{"name":"sport","accuracy":null,"unstable__provider":"flickr"},{"name":"todo","accuracy":null,"unstable__provider":"flickr"},{"name":"illustration","accuracy":0.98287,"unstable__provider":"clarifai"},{"name":"isolated","accuracy":0.92947,"unstable__provider":"clarifai"},{"name":"signalise","accuracy":0.92606,"unstable__provider":"clarifai"},{"name":"symbol","accuracy":0.97795,"unstable__provider":"clarifai"},{"name":"technology","accuracy":0.93643,"unstable__provider":"clarifai"}],"attribution":"\"Black Clipboard\" by One Way Stock is licensed under CC BY-ND 2.0. To view a copy of this license, visit https://creativecommons.org/licenses/by-nd/2.0/.","fields_matched":["title","tags.name"],"mature":false,"height":135,"width":180,"thumbnail":"https://api.openverse.org/v1/images/dc3522f3-a976-49eb-a2c8-9e891896f980/thumb/","detail_url":"https://api.openverse.org/v1/images/dc3522f3-a976-49eb-a2c8-9e891896f980/","related_url":"https://api.openverse.org/v1/images/dc3522f3-a976-49eb-a2c8-9e891896f980/related/","unstable__sensitivity":[]},{"id":"a1e3312b-53fc-413a-8360-3635b68e65ee","title":"Clipboard Hand","indexed_on":"2021-11-01T23:12:09.897557Z","foreign_landing_url":"https://stocksnap.io/photo/clipboard-hand-TRKNLIGFAJ","url":"https://cdn.stocksnap.io/img-thumbs/960w/TRKNLIGFAJ.jpg","creator":"Kristin Hardwick","creator_url":"https://www.kristinhardwick.com","license":"cc0","license_version":"1.0","license_url":"https://creativecommons.org/publicdomain/zero/1.0/","provider":"stocksnap","source":"stocksnap","category":"photograph","filesize":520960,"filetype":"jpg","tags":[{"name":"box","accuracy":null,"unstable__provider":"stocksnap"},{"name":"checklist","accuracy":null,"unstable__provider":"stocksnap"},{"name":"clipboard","accuracy":null,"unstable__provider":"stocksnap"},{"name":"female","accuracy":null,"unstable__provider":"stocksnap"},{"name":"hand","accuracy":null,"unstable__provider":"stocksnap"},{"name":"office","accuracy":null,"unstable__provider":"stocksnap"},{"name":"package","accuracy":null,"unstable__provider":"stocksnap"},{"name":"pen","accuracy":null,"unstable__provider":"stocksnap"},{"name":"person","accuracy":null,"unstable__provider":"stocksnap"},{"name":"professional","accuracy":null,"unstable__provider":"stocksnap"},{"name":"shipping","accuracy":null,"unstable__provider":"stocksnap"},{"name":"table","accuracy":null,"unstable__provider":"stocksnap"},{"name":"worker","accuracy":null,"unstable__provider":"stocksnap"}],"attribution":"\"Clipboard Hand\" by Kristin Hardwick is marked with CC0 1.0. To view the terms, visit https://creativecommons.org/publicdomain/zero/1.0/.","fields_matched":["title","tags.name"],"mature":false,"height":3840,"width":5760,"thumbnail":"https://api.openverse.org/v1/images/a1e3312b-53fc-413a-8360-3635b68e65ee/thumb/","detail_url":"https://api.openverse.org/v1/images/a1e3312b-53fc-413a-8360-3635b68e65ee/","related_url":"https://api.openverse.org/v1/images/a1e3312b-53fc-413a-8360-3635b68e65ee/related/","unstable__sensitivity":[]},{"id":"ea55a40c-6754-4214-afd7-79f09d1a8989","title":"Authoritarian Overreach, Far Side-style cartoon scenes depicting absurd government bureaucracy and over-control","indexed_on":"2025-07-03T00:07:52.098393Z","foreign_landing_url":"https://www.flickr.com/photos/28826830@N00/54627934724","url":"https://live.staticflickr.com/65535/54627934724_44a579934f_b.jpg","creator":"exit78","creator_url":"https://www.flickr.com/photos/28826830@N00","license":"cc0","license_version":"1.0","license_url":"https://creativecommons.org/publicdomain/zero/1.0/","provider":"flickr","source":"flickr","category":"photograph","filesize":null,"filetype":"jpg","tags":[],"attribution":"\"Authoritarian Overreach, Far Side-style cartoon scenes depicting absurd government bureaucracy and over-control\" by exit78 is marked with CC0 1.0. To view the terms, visit https://creativecommons.org/publicdomain/zero/1.0/.","fields_matched":["description"],"mature":false,"height":683,"width":1024,"thumbnail":"https://api.openverse.org/v1/images/ea55a40c-6754-4214-afd7-79f09d1a8989/thumb/","detail_url":"https://api.openverse.org/v1/images/ea55a40c-6754-4214-afd7-79f09d1a8989/","related_url":"https://api.openverse.org/v1/images/ea55a40c-6754-4214-afd7-79f09d1a8989/related/","unstable__sensitivity":[]},{"id":"b6a087c5-7f08-4434-bc3f-3f820fccea53","title":"Authoritarian Overreach, Far Side-style cartoon scenes depicting absurd government bureaucracy and over-control","indexed_on":"2025-07-03T00:07:52.098393Z","foreign_landing_url":"https://www.flickr.com/photos/28826830@N00/54626853567","url":"https://live.staticflickr.com/65535/54626853567_8335e5b2ec_b.jpg","creator":"exit78","creator_url":"https://www.flickr.com/photos/28826830@N00","license":"cc0","license_version":"1.0","license_url":"https://creativecommons.org/publicdomain/zero/1.0/","provider":"flickr","source":"flickr","category":"photograph","filesize":null,"filetype":"jpg","tags":[],"attribution":"\"Authoritarian Overreach, Far Side-style cartoon scenes depicting absurd government bureaucracy and over-control\" by exit78 is marked with CC0 1.0. To view the terms, visit https://creativecommons.org/publicdomain/zero/1.0/.","fields_matched":["description"],"mature":false,"height":683,"width":1024,"thumbnail":"https://api.openverse.org/v1/images/b6a087c5-7f08-4434-bc3f-3f820fccea53/thumb/","detail_url":"https://api.openverse.org/v1/images/b6a087c5-7f08-4434-bc3f-3f820fccea53/","related_url":"https://api.openverse.org/v1/images/b6a087c5-7f08-4434-bc3f-3f820fccea53/related/","unstable__sensitivity":[]},{"id":"c7f5fc63-674e-4088-b219-d71db17acd77","title":"Examiner filling in driver's license road test form","indexed_on":"2025-12-23T00:04:41.511194Z","foreign_landing_url":"https://www.flickr.com/photos/203928447@N02/54999169448","url":"https://live.staticflickr.com/65535/54999169448_e92afe9dbe_b.jpg","creator":"f0976531950157","creator_url":"https://www.flickr.com/photos/203928447@N02","license":"pdm","license_version":"1.0","license_url":"https://creativecommons.org/publicdomain/mark/1.0/","provider":"flickr","source":"flickr","category":"photograph","filesize":null,"filetype":"jpg","tags":[{"name":"auto","accuracy":null,"unstable__provider":"flickr"},{"name":"automobile","accuracy":null,"unstable__provider":"flickr"},{"name":"car","accuracy":null,"unstable__provider":"flickr"},{"name":"casual","accuracy":null,"unstable__provider":"flickr"},{"name":"caucasian","accuracy":null,"unstable__provider":"flickr"},{"name":"checklist","accuracy":null,"unstable__provider":"flickr"},{"name":"clipboard","accuracy":null,"unstable__provider":"flickr"},{"name":"clippad","accuracy":null,"unstable__provider":"flickr"},{"name":"closeup","accuracy":null,"unstable__provider":"flickr"},{"name":"concept","accuracy":null,"unstable__provider":"flickr"},{"name":"dashboard","accuracy":null,"unstable__provider":"flickr"},{"name":"drive","accuracy":null,"unstable__provider":"flickr"},{"name":"driver","accuracy":null,"unstable__provider":"flickr"},{"name":"driverslicense","accuracy":null,"unstable__provider":"flickr"},{"name":"driving","accuracy":null,"unstable__provider":"flickr"},{"name":"exam","accuracy":null,"unstable__provider":"flickr"},{"name":"examination","accuracy":null,"unstable__provider":"flickr"},{"name":"female","accuracy":null,"unstable__provider":"flickr"},{"name":"form","accuracy":null,"unstable__provider":"flickr"},{"name":"hands","accuracy":null,"unstable__provider":"flickr"},{"name":"instructor","accuracy":null,"unstable__provider":"flickr"},{"name":"learn","accuracy":null,"unstable__provider":"flickr"},{"name":"learner","accuracy":null,"unstable__provider":"flickr"},{"name":"lesson","accuracy":null,"unstable__provider":"flickr"},{"name":"license","accuracy":null,"unstable__provider":"flickr"},{"name":"notepad","accuracy":null,"unstable__provider":"flickr"},{"name":"outdoors","accuracy":null,"unstable__provider":"flickr"},{"name":"pen","accuracy":null,"unstable__provider":"flickr"},{"name":"people","accuracy":null,"unstable__provider":"flickr"},{"name":"road","accuracy":null,"unstable__provider":"flickr"},{"name":"roadtest","accuracy":null,"unstable__provider":"flickr"},{"name":"roadway","accuracy":null,"unstable__provider":"flickr"},{"name":"rules","accuracy":null,"unstable__provider":"flickr"},{"name":"safety","accuracy":null,"unstable__provider":"flickr"},{"name":"school","accuracy":null,"unstable__provider":"flickr"},{"name":"sitting","accuracy":null,"unstable__provider":"flickr"},{"name":"speed","accuracy":null,"unstable__provider":"flickr"},{"name":"steering","accuracy":null,"unstable__provider":"flickr"},{"name":"street","accuracy":null,"unstable__provider":"flickr"},{"name":"student","accuracy":null,"unstable__provider":"flickr"},{"name":"teacher","accuracy":null,"unstable__provider":"flickr"},{"name":"teaching","accuracy":null,"unstable__provider":"flickr"},{"name":"test","accuracy":null,"unstable__provider":"flickr"},{"name":"traffic","accuracy":null,"unstable__provider":"flickr"},{"name":"training","accuracy":null,"unstable__provider":"flickr"},{"name":"transport","accuracy":null,"unstable__provider":"flickr"},{"name":"transportation","accuracy":null,"unstable__provider":"flickr"},{"name":"vehicle","accuracy":null,"unstable__provider":"flickr"},{"name":"wheel","accuracy":null,"unstable__provider":"flickr"},{"name":"woman","accuracy":null,"unstable__provider":"flickr"}],"attribution":"\"Examiner filling in driver's license road test form\" by f0976531950157 is marked with Public Domain Mark 1.0. To view the terms, visit https://creativecommons.org/publicdomain/mark/1.0/.","fields_matched":["tags.name"],"mature":false,"height":667,"width":1000,"thumbnail":"https://api.openverse.org/v1/images/c7f5fc63-674e-4088-b219-d71db17acd77/thumb/","detail_url":"https://api.openverse.org/v1/images/c7f5fc63-674e-4088-b219-d71db17acd77/","related_url":"https://api.openverse.org/v1/images/c7f5fc63-674e-4088-b219-d71db17acd77/related/","unstable__sensitivity":[]},{"id":"104e2594-d689-469d-8798-9448ff905c98","title":"Gokart checklist, vintage drawing illustration","indexed_on":"2024-03-29T01:59:00.599666Z","foreign_landing_url":"https://www.rawpixel.com/image/6811903/image-vintage-public-domain-icon","url":"https://images.rawpixel.com/editor_1024/cHJpdmF0ZS9sci9pbWFnZXMvd2Vic2l0ZS8yMDIyLTA1L2pvYjcxOS0xMTYteC5qcGc.jpg","creator":null,"creator_url":null,"license":"cc0","license_version":"1.0","license_url":"https://creativecommons.org/publicdomain/zero/1.0/","provider":"rawpixel","source":"rawpixel","category":"illustration","filesize":null,"filetype":"jpg","tags":[{"name":"antique","accuracy":null,"unstable__provider":"rawpixel"},{"name":"athlete","accuracy":null,"unstable__provider":"rawpixel"},{"name":"black","accuracy":null,"unstable__provider":"rawpixel"},{"name":"black and white","accuracy":null,"unstable__provider":"rawpixel"},{"name":"boy","accuracy":null,"unstable__provider":"rawpixel"},{"name":"bw","accuracy":null,"unstable__provider":"rawpixel"},{"name":"checklist","accuracy":null,"unstable__provider":"rawpixel"},{"name":"clip art","accuracy":null,"unstable__provider":"rawpixel"},{"name":"clipart","accuracy":null,"unstable__provider":"rawpixel"},{"name":"clipboard","accuracy":null,"unstable__provider":"rawpixel"},{"name":"kart","accuracy":null,"unstable__provider":"rawpixel"}],"attribution":"\"Gokart checklist, vintage drawing illustration\" is marked with CC0 1.0. To view the terms, visit https://creativecommons.org/publicdomain/zero/1.0/.","fields_matched":["description","title","tags.name"],"mature":false,"height":2667,"width":4000,"thumbnail":"https://api.openverse.org/v1/images/104e2594-d689-469d-8798-9448ff905c98/thumb/","detail_url":"https://api.openverse.org/v1/images/104e2594-d689-469d-8798-9448ff905c98/","related_url":"https://api.openverse.org/v1/images/104e2594-d689-469d-8798-9448ff905c98/related/","unstable__sensitivity":[]}]}
exec
/bin/bash -lc "curl -L --silent 'https://api.openverse.org/v1/images/?q=planner%20calendar%20phone%20desk&license=cc0&extension=jpg' | sed -n '1,160p'" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "curl -L --silent 'https://api.openverse.org/v1/images/?q=checklist%20phone%20desk&license=cc0&extension=jpg' | sed -n '1,160p'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 594ms:
{"result_count":0,"page_count":0,"page_size":20,"page":1,"results":[]}
 succeeded in 669ms:
{"result_count":1,"page_count":1,"page_size":20,"page":1,"results":[{"id":"f3dad07d-1e84-4f74-8c2e-478da5a3b271","title":"Some accessories on a white desk","indexed_on":"2020-03-20T03:21:48.133401Z","foreign_landing_url":"https://www.flickr.com/photos/135396164@N05/33572876081","url":"https://live.staticflickr.com/2837/33572876081_7618124453_b.jpg","creator":"freestocks.org","creator_url":"https://www.flickr.com/photos/135396164@N05","license":"cc0","license_version":"1.0","license_url":"https://creativecommons.org/publicdomain/zero/1.0/","provider":"flickr","source":"flickr","category":null,"filesize":null,"filetype":null,"tags":[{"name":"accessories","accuracy":null,"unstable__provider":"flickr"},{"name":"business","accuracy":null,"unstable__provider":"flickr"},{"name":"calendar","accuracy":null,"unstable__provider":"flickr"},{"name":"cell","accuracy":null,"unstable__provider":"flickr"},{"name":"clock","accuracy":null,"unstable__provider":"flickr"},{"name":"communication","accuracy":null,"unstable__provider":"flickr"},{"name":"connected","accuracy":null,"unstable__provider":"flickr"},{"name":"copy","accuracy":null,"unstable__provider":"flickr"},{"name":"design","accuracy":null,"unstable__provider":"flickr"},{"name":"desk","accuracy":null,"unstable__provider":"flickr"},{"name":"device","accuracy":null,"unstable__provider":"flickr"},{"name":"digital","accuracy":null,"unstable__provider":"flickr"},{"name":"electronic","accuracy":null,"unstable__provider":"flickr"},{"name":"equipment","accuracy":null,"unstable__provider":"flickr"},{"name":"journal","accuracy":null,"unstable__provider":"flickr"},{"name":"mobile","accuracy":null,"unstable__provider":"flickr"},{"name":"mobility","accuracy":null,"unstable__provider":"flickr"},{"name":"modern","accuracy":null,"unstable__provider":"flickr"},{"name":"neat","accuracy":null,"unstable__provider":"flickr"},{"name":"office","accuracy":null,"unstable__provider":"flickr"},{"name":"order","accuracy":null,"unstable__provider":"flickr"},{"name":"organizer","accuracy":null,"unstable__provider":"flickr"},{"name":"pencil","accuracy":null,"unstable__provider":"flickr"},{"name":"phone","accuracy":null,"unstable__provider":"flickr"},{"name":"plain","accuracy":null,"unstable__provider":"flickr"},{"name":"planner","accuracy":null,"unstable__provider":"flickr"},{"name":"smart","accuracy":null,"unstable__provider":"flickr"},{"name":"smartphone","accuracy":null,"unstable__provider":"flickr"},{"name":"space","accuracy":null,"unstable__provider":"flickr"},{"name":"table","accuracy":null,"unstable__provider":"flickr"},{"name":"tech","accuracy":null,"unstable__provider":"flickr"},{"name":"technology","accuracy":null,"unstable__provider":"flickr"},{"name":"time","accuracy":null,"unstable__provider":"flickr"},{"name":"tool","accuracy":null,"unstable__provider":"flickr"},{"name":"white","accuracy":null,"unstable__provider":"flickr"}],"attribution":"\"Some accessories on a white desk\" by freestocks.org is marked with CC0 1.0. To view the terms, visit https://creativecommons.org/publicdomain/zero/1.0/.","fields_matched":["title","tags.name"],"mature":false,"height":683,"width":1024,"thumbnail":"https://api.openverse.org/v1/images/f3dad07d-1e84-4f74-8c2e-478da5a3b271/thumb/","detail_url":"https://api.openverse.org/v1/images/f3dad07d-1e84-4f74-8c2e-478da5a3b271/","related_url":"https://api.openverse.org/v1/images/f3dad07d-1e84-4f74-8c2e-478da5a3b271/related/","unstable__sensitivity":[]}]}
exec
/bin/bash -lc "curl -L --silent 'https://api.openverse.org/v1/images/?q=notebook%20phone%20clipboard%20desk&license=cc0&extension=jpg' | sed -n '1,180p'" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "curl -L --silent 'https://api.openverse.org/v1/images/?q=service%20checklist%20clipboard%20desk&license=cc0&extension=jpg' | sed -n '1,180p'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 221ms:
{"result_count":0,"page_count":0,"page_size":20,"page":1,"results":[]}
 succeeded in 577ms:
{"result_count":0,"page_count":0,"page_size":20,"page":1,"results":[]}
codex
Plan:
1. Import or choose the article image and create the `Grant Vale` author account if it doesn’t exist.
2. Build the article HTML with the required headings, checklist table, and internal links to the existing site pages.
3. Create the post in WordPress, set author/slug/status/featured image, and verify the post URL, `/blog/` index, and inline image presence.
  → Import or select a credible article image and create/reuse the Grant Vale author account
  • Draft the article HTML with required structure and internal links
  • Create and verify the published WordPress post and blog index settings
codex
I’m moving from inspection to implementation now: importing the image asset, creating the requested author identity, and then I’ll write the post HTML into the workspace for `wp post create`.
exec
/bin/bash -lc "if wp user get grant-vale >/dev/null 2>&1; then wp user update grant-vale --display_name='Grant Vale' --user_email='grant-vale@ridgecrestchurch.com' --role=author >/dev/null && echo 'reused grant-vale'; else wp user create grant-vale grant-vale@ridgecrestchurch.com --role=author --display_name='Grant Vale' --user_pass='GrantVale"'!2026-temp'"' >/dev/null && echo 'created grant-vale'; fi
wp user meta update grant-vale description 'Grant covers website reliability, backups, domains, security basics, and the operational habits that keep online services steady.' >/dev/null
wp user get grant-vale --fields=ID,user_login,display_name,user_email,roles --format=json" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "mkdir -p wp-content/uploads/imports && curl -L --fail --silent --show-error 'https://live.staticflickr.com/2837/33572876081_7618124453_b.jpg' -o wp-content/uploads/imports/sunday-service-planning-desk.jpg && file wp-content/uploads/imports/sunday-service-planning-desk.jpg && wp media import wp-content/uploads/imports/sunday-service-planning-desk.jpg --title='Sunday Service Planning Desk' --alt='Planning materials on a desk with a calendar and smartphone for Sunday service coordination' --porcelain" in /home/ubuntu/apps/ridgecrestchurch.com
 exited 1 in 721ms:
wp-content/uploads/imports/sunday-service-planning-desk.jpg: JPEG image data, Exif standard: [TIFF image data, big-endian, direntries=1], baseline, precision 8, 1024x683, components 3
Error: No support for generating images found. Please install the Imagick or GD PHP extensions.

 succeeded in 2177ms:
created grant-vale
{"ID":"3","user_login":"grant-vale","user_email":"grant-vale@ridgecrestchurch.com","display_name":"Grant Vale","roles":"author"}

codex
`wp media import` failed because this WordPress install has neither GD nor Imagick. That’s recoverable; I’m registering the downloaded JPEG as an attachment through WordPress APIs instead of depending on image processing.
exec
/bin/bash -lc "wp eval '
"'$file = ABSPATH . "wp-content/uploads/imports/sunday-service-planning-desk.jpg";
$url = content_url("uploads/imports/sunday-service-planning-desk.jpg");
$existing = attachment_url_to_postid($url);
if ($existing) {
  $id = $existing;
} else {
  $type = wp_check_filetype(basename($file), null);
  $id = wp_insert_attachment([
    "guid" => $url,
    "post_mime_type" => $type["type"],
    "post_title" => "Sunday Service Planning Desk",
    "post_content" => "",
    "post_status" => "inherit"
  ], $file);
}
if (!is_wp_error($id)) {
  update_post_meta($id, "_wp_attachment_image_alt", "Planning materials on a desk with a calendar and smartphone for Sunday service coordination");
  echo $id;
}
'"'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 496ms:
76
codex
I have the attachment registered. I’m writing the article body now with the required checklist structure, a visible inline image, and links to the site’s existing `About Us`, `Kids`, `Youth`, `Events Calendar`, `News`, and `Contacts` pages.
apply patch
patch: completed
/home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-36/how-to-plan-a-great-sunday-checklist.html
diff --git a//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-36/how-to-plan-a-great-sunday-checklist.html b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-36/how-to-plan-a-great-sunday-checklist.html
new file mode 100644
index 0000000000000000000000000000000000000000..ddcb6ed3321dea7fe2be10451aef92ad57550d76
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-36/how-to-plan-a-great-sunday-checklist.html
@@ -0,0 +1,199 @@
+<p><strong><em>A calm Sunday service is rarely accidental. It usually comes from a short, repeatable checklist that keeps worship, hospitality, kids ministry, youth transitions, and follow-up from drifting into preventable confusion.</em></strong></p>
+
+<p>If your team has ever asked, "Who is opening the building?" "Did the slides get updated?" "Who is covering kids check-in?" or "How will we follow up with first-time guests?" this article is for you. A healthy Sunday plan does not need to be complicated. It needs to be clear, shared, and easy to run when the morning gets busy.</p>
+
+<figure class="wp-block-image size-large"><img src="https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg" alt="Planning materials on a desk with a calendar and smartphone for Sunday service coordination" class="wp-image-76" /><figcaption>A simple planning rhythm helps each Sunday start with fewer last-minute surprises.</figcaption></figure>
+
+<p>At <a href="https://ridgecrestchurch.com/about-us/">Ridgecrest Baptist Church</a>, Sunday ministry touches more than the order of service. It includes worship preparation, guest welcome, prayer, children and student handoffs, building readiness, and timely communication. When those parts are aligned, people can focus on worship and connection instead of chasing missing details.</p>
+
+<h2>Why a simple checklist matters</h2>
+
+<p>A checklist creates a baseline. It protects the team from relying on memory, and it lowers the odds that one missed handoff will affect the whole morning. The goal is not to make ministry mechanical. The goal is to remove avoidable friction so volunteers and staff can serve people well.</p>
+
+<p><strong>A good Sunday checklist does four jobs:</strong></p>
+
+<ul>
+<li>It gives each team a clear role before people arrive.</li>
+<li>It reduces last-minute surprises around sound, slides, seating, and room setup.</li>
+<li>It protects kids and student ministry transitions with documented handoff steps.</li>
+<li>It creates a consistent follow-up path for guests, prayer needs, and event reminders.</li>
+</ul>
+
+<p>If your church already publishes updates through the <a href="https://ridgecrestchurch.com/news/">News</a> page and upcoming schedules through the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>, your checklist should point teams back to those same sources. One source of truth beats four versions of the plan every time.</p>
+
+<h2>The Sunday timeline</h2>
+
+<p>Most service-day problems start before Sunday. The easiest fix is to divide preparation into three windows: the week before, the day before, and the final 30 minutes.</p>
+
+<table>
+<thead>
+<tr>
+<th>When</th>
+<th>What to confirm</th>
+<th>Primary owner</th>
+<th>Why it matters</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>Week before</td>
+<td>Order of service, volunteer schedule, kids/youth staffing, announcements, and event updates</td>
+<td>Staff lead or Sunday coordinator</td>
+<td>Prevents avoidable gaps before the weekend starts</td>
+</tr>
+<tr>
+<td>Day before</td>
+<td>Slides, song order, microphones, printed notes, room setup, and supply restock</td>
+<td>Worship, tech, facilities, and ministry leaders</td>
+<td>Catches errors while there is still time to correct them calmly</td>
+</tr>
+<tr>
+<td>30 minutes before service</td>
+<td>Doors unlocked, greeters in place, kids check-in ready, livestream/audio tested, and platform teams present</td>
+<td>On-site team leads</td>
+<td>Keeps the final handoff from turning into a scramble</td>
+</tr>
+</tbody>
+</table>
+
+<h3>What to prepare the week before</h3>
+
+<ul>
+<li>Finalize the order of service and distribute it to worship, tech, and platform leaders.</li>
+<li>Confirm which announcements need to be said live and which belong on the <a href="https://ridgecrestchurch.com/news/">News</a> page or <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>.</li>
+<li>Review volunteer assignments for greeters, ushers, kids check-in, nursery, student leaders, and security-minded building coverage.</li>
+<li>Make sure contact details for key leaders are current on the <a href="https://ridgecrestchurch.com/contacts/">Contacts</a> page so volunteers know where to direct questions.</li>
+</ul>
+
+<h3>What to prepare the day before</h3>
+
+<ul>
+<li>Load final slides, lyrics, Scripture references, and announcement screens.</li>
+<li>Test microphones, playback sources, batteries, and any livestream or recording workflow.</li>
+<li>Walk through classrooms, restrooms, entryways, and seating areas for cleanliness, signage, and accessibility.</li>
+<li>Check that kids ministry labels, sign-in materials, and emergency contacts are available where needed.</li>
+</ul>
+
+<h3>What to confirm 30 minutes before service</h3>
+
+<ul>
+<li>Greeters are at doors and know how to guide visitors.</li>
+<li>The worship team and tech team have completed sound check and cue review.</li>
+<li>Kids ministry volunteers are ready to receive families on time.</li>
+<li>Youth leaders know whether students begin in the main service, move later, or stay together for the full morning.</li>
+<li>Someone is assigned to receive guest questions and route them to the right ministry leader.</li>
+</ul>
+
+<h2>Worship and music: keep the platform steady</h2>
+
+<p>The worship portion of the morning needs an agreed sequence, not assumptions. Use one shared service order and make sure everyone on platform has the same version.</p>
+
+<ul>
+<li>Confirm the opening song, transitions, prayer moments, offering, message, and closing response.</li>
+<li>Verify lyric slides, lower thirds, and any Scripture references before rehearsal ends.</li>
+<li>Check microphones individually, not in theory. A muted channel is still a failure mode even if everything looked fine on Saturday.</li>
+<li>Assign one person to call audible changes only if needed. Too many live decision-makers create noise.</li>
+</ul>
+
+<p>If your team uses printed bulletins, make sure they match the final service plan. If you use screens only, confirm the projection operator has the right sequence and a backup copy of key items.</p>
+
+<h2>Welcome and connection: make guest follow-up clear</h2>
+
+<p>Hospitality is not filler around the service. It is part of the ministry of the morning. Greeters should know where to stand, what information they can answer, and when to hand a question to someone else.</p>
+
+<p><strong>Minimum safe setup for guest welcome:</strong></p>
+
+<ul>
+<li>Greeters at visible entrances 15 to 20 minutes before the service starts.</li>
+<li>A simple plan for directing families to <a href="https://ridgecrestchurch.com/kids/">Kids</a> or students to <a href="https://ridgecrestchurch.com/youth/">Youth</a>.</li>
+<li>A connection method that asks only for the information you actually need for follow-up.</li>
+<li>A same-day owner for guest cards, digital forms, or text-based responses.</li>
+</ul>
+
+<p>When you collect contact information, keep it responsible and plain: request only essential details, explain how the information will be used, and limit access to the people who need it for ministry follow-up. A church does not need operational fog around guest data.</p>
+
+<h2>Announcements and prayer: brief, accurate, and timely</h2>
+
+<p>Announcements should help people act. They should not become a second sermon or a rolling list of half-confirmed details. Choose the two or three items that matter most this week, state them clearly, and point people to the right page for details.</p>
+
+<ul>
+<li>Use the live service for timely, high-priority items.</li>
+<li>Use the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for dates, times, and logistics.</li>
+<li>Use the <a href="https://ridgecrestchurch.com/news/">News</a> page for fuller updates, ministry notes, or reminders people may revisit later.</li>
+<li>Keep prayer transitions intentional by deciding in advance who will lead and what the time boundary is.</li>
+</ul>
+
+<p>A short prayer can still be thoughtful. A short announcement can still be useful. Precision serves the room.</p>
+
+<h2>Kids ministry flow: protect check-in and handoff timing</h2>
+
+<p>Children's ministry is one of the clearest places where a written checklist pays off. Families feel it immediately when check-in is organized and volunteers are prepared.</p>
+
+<ul>
+<li>Open check-in early enough to prevent a line from forming at service start.</li>
+<li>Verify classroom coverage, allergy notes, bathroom procedures, and pickup expectations before families arrive.</li>
+<li>Keep parent pickup instructions simple and consistent each week.</li>
+<li>Make sure the route from the main entrance to the <a href="https://ridgecrestchurch.com/kids/">Kids</a> area is obvious for first-time visitors.</li>
+</ul>
+
+<p>If kids begin in the sanctuary and transition later, mark the timing in the service order so volunteers are in place before the handoff begins. A late handoff creates confusion for parents, teachers, and the platform team at the same time.</p>
+
+<h2>Youth ministry flow: decide the student plan in advance</h2>
+
+<p>Not every church handles student ministry the same way on Sunday morning. Some students stay in the full service. Some move after worship. Some alternate by week. The important point is not the format. It is the clarity.</p>
+
+<ul>
+<li>Confirm whether students attend the full service or transition at a set point.</li>
+<li>Make sure leaders know where students should gather, who is responsible for them, and what pickup or dismissal looks like.</li>
+<li>Share schedule changes through the <a href="https://ridgecrestchurch.com/youth/">Youth</a> page, <a href="https://ridgecrestchurch.com/news/">News</a>, or direct volunteer communication before Sunday morning.</li>
+</ul>
+
+<p>A good student plan removes guesswork for parents and leaders alike.</p>
+
+<h2>Tech and facilities: prepare the room people will actually experience</h2>
+
+<p>People notice the room before they notice your process. Tech and facility checks should cover what a first-time guest and a regular volunteer will both encounter.</p>
+
+<ul>
+<li>Slides, presentation computer, confidence monitor, and backup files</li>
+<li>Microphones, batteries, audio routing, and livestream or recording checks</li>
+<li>Restrooms stocked and clearly marked</li>
+<li>Seating ready for expected attendance and accessible entry routes open</li>
+<li>Heating, cooling, lighting, and any rooms needed after the service</li>
+</ul>
+
+<p>Walk the building with fresh eyes. If a hallway is unclear, a restroom is out of supplies, or a sign is missing, Sunday morning will magnify it.</p>
+
+<h2>Communication: decide who sends what to whom</h2>
+
+<p>Most Sunday chaos is not a values problem. It is a communication problem. The easiest way to fix that is to assign owners for each update.</p>
+
+<p><strong>Keep the communication chain simple:</strong></p>
+
+<ul>
+<li>The service coordinator sends the final order to worship, tech, and platform leaders.</li>
+<li>Kids and youth leaders confirm volunteer coverage and any room or schedule changes with their teams.</li>
+<li>The person handling public updates posts changes in the right place, usually the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for schedules and the <a href="https://ridgecrestchurch.com/news/">News</a> page for broader updates.</li>
+<li>Guest follow-up and ministry questions are routed to the right staff contact through the <a href="https://ridgecrestchurch.com/contacts/">Contacts</a> page.</li>
+</ul>
+
+<p>If a change matters enough to mention from the platform, it matters enough to send to the people serving that morning.</p>
+
+<h2>A simple Sunday service checklist to reuse each week</h2>
+
+<ol>
+<li>Finalize the order of service and confirm who owns each segment.</li>
+<li>Review volunteer coverage for hospitality, kids, youth, worship, tech, and facilities.</li>
+<li>Update slides, lyrics, announcement notes, and backup files.</li>
+<li>Prepare guest follow-up materials and identify who collects them.</li>
+<li>Open kids check-in and confirm safety basics before families arrive.</li>
+<li>Confirm the youth ministry plan and any service-time transitions.</li>
+<li>Test microphones, audio, presentation screens, and livestream workflow.</li>
+<li>Walk the building for restrooms, signage, seating, and accessibility.</li>
+<li>Post final public-facing updates in the right channel: calendar, news, or direct contact.</li>
+<li>Hold a short final check-in with the leaders on site before service begins.</li>
+</ol>
+
+<p>A stable Sunday does not require a complicated system. It requires one documented plan, clear ownership, and the discipline to review the same handoffs every week. If your current process feels reactive, start with the list above, trim it to what your church actually needs, and keep it where every team can reach it. Order is expensive in small ways. Chaos is expensive all at once.</p>
+
+<p>If you need to confirm service details, event timing, or the right ministry contact before the week begins, use the church’s <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>, <a href="https://ridgecrestchurch.com/news/">News</a>, and <a href="https://ridgecrestchurch.com/contacts/">Contacts</a> pages as your baseline.</p>

diff --git a//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-36/how-to-plan-a-great-sunday-checklist.html b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-36/how-to-plan-a-great-sunday-checklist.html
new file mode 100644
index 0000000000000000000000000000000000000000..ddcb6ed3321dea7fe2be10451aef92ad57550d76
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-36/how-to-plan-a-great-sunday-checklist.html
@@ -0,0 +1,199 @@
+<p><strong><em>A calm Sunday service is rarely accidental. It usually comes from a short, repeatable checklist that keeps worship, hospitality, kids ministry, youth transitions, and follow-up from drifting into preventable confusion.</em></strong></p>
+
+<p>If your team has ever asked, "Who is opening the building?" "Did the slides get updated?" "Who is covering kids check-in?" or "How will we follow up with first-time guests?" this article is for you. A healthy Sunday plan does not need to be complicated. It needs to be clear, shared, and easy to run when the morning gets busy.</p>
+
+<figure class="wp-block-image size-large"><img src="https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg" alt="Planning materials on a desk with a calendar and smartphone for Sunday service coordination" class="wp-image-76" /><figcaption>A simple planning rhythm helps each Sunday start with fewer last-minute surprises.</figcaption></figure>
+
+<p>At <a href="https://ridgecrestchurch.com/about-us/">Ridgecrest Baptist Church</a>, Sunday ministry touches more than the order of service. It includes worship preparation, guest welcome, prayer, children and student handoffs, building readiness, and timely communication. When those parts are aligned, people can focus on worship and connection instead of chasing missing details.</p>
+
+<h2>Why a simple checklist matters</h2>
+
+<p>A checklist creates a baseline. It protects the team from relying on memory, and it lowers the odds that one missed handoff will affect the whole morning. The goal is not to make ministry mechanical. The goal is to remove avoidable friction so volunteers and staff can serve people well.</p>
+
+<p><strong>A good Sunday checklist does four jobs:</strong></p>
+
+<ul>
+<li>It gives each team a clear role before people arrive.</li>
+<li>It reduces last-minute surprises around sound, slides, seating, and room setup.</li>
+<li>It protects kids and student ministry transitions with documented handoff steps.</li>
+<li>It creates a consistent follow-up path for guests, prayer needs, and event reminders.</li>
+</ul>
+
+<p>If your church already publishes updates through the <a href="https://ridgecrestchurch.com/news/">News</a> page and upcoming schedules through the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>, your checklist should point teams back to those same sources. One source of truth beats four versions of the plan every time.</p>
+
+<h2>The Sunday timeline</h2>
+
+<p>Most service-day problems start before Sunday. The easiest fix is to divide preparation into three windows: the week before, the day before, and the final 30 minutes.</p>
+
+<table>
+<thead>
+<tr>
+<th>When</th>
+<th>What to confirm</th>
+<th>Primary owner</th>
+<th>Why it matters</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>Week before</td>
+<td>Order of service, volunteer schedule, kids/youth staffing, announcements, and event updates</td>
+<td>Staff lead or Sunday coordinator</td>
+<td>Prevents avoidable gaps before the weekend starts</td>
+</tr>
+<tr>
+<td>Day before</td>
+<td>Slides, song order, microphones, printed notes, room setup, and supply restock</td>
+<td>Worship, tech, facilities, and ministry leaders</td>
+<td>Catches errors while there is still time to correct them calmly</td>
+</tr>
+<tr>
+<td>30 minutes before service</td>
+<td>Doors unlocked, greeters in place, kids check-in ready, livestream/audio tested, and platform teams present</td>
+<td>On-site team leads</td>
+<td>Keeps the final handoff from turning into a scramble</td>
+</tr>
+</tbody>
+</table>
+
+<h3>What to prepare the week before</h3>
+
+<ul>
+<li>Finalize the order of service and distribute it to worship, tech, and platform leaders.</li>
+<li>Confirm which announcements need to be said live and which belong on the <a href="https://ridgecrestchurch.com/news/">News</a> page or <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>.</li>
+<li>Review volunteer assignments for greeters, ushers, kids check-in, nursery, student leaders, and security-minded building coverage.</li>
+<li>Make sure contact details for key leaders are current on the <a href="https://ridgecrestchurch.com/contacts/">Contacts</a> page so volunteers know where to direct questions.</li>
+</ul>
+
+<h3>What to prepare the day before</h3>
+
+<ul>
+<li>Load final slides, lyrics, Scripture references, and announcement screens.</li>
+<li>Test microphones, playback sources, batteries, and any livestream or recording workflow.</li>
+<li>Walk through classrooms, restrooms, entryways, and seating areas for cleanliness, signage, and accessibility.</li>
+<li>Check that kids ministry labels, sign-in materials, and emergency contacts are available where needed.</li>
+</ul>
+
+<h3>What to confirm 30 minutes before service</h3>
+
+<ul>
+<li>Greeters are at doors and know how to guide visitors.</li>
+<li>The worship team and tech team have completed sound check and cue review.</li>
+<li>Kids ministry volunteers are ready to receive families on time.</li>
+<li>Youth leaders know whether students begin in the main service, move later, or stay together for the full morning.</li>
+<li>Someone is assigned to receive guest questions and route them to the right ministry leader.</li>
+</ul>
+
+<h2>Worship and music: keep the platform steady</h2>
+
+<p>The worship portion of the morning needs an agreed sequence, not assumptions. Use one shared service order and make sure everyone on platform has the same version.</p>
+
+<ul>
+<li>Confirm the opening song, transitions, prayer moments, offering, message, and closing response.</li>
+<li>Verify lyric slides, lower thirds, and any Scripture references before rehearsal ends.</li>
+<li>Check microphones individually, not in theory. A muted channel is still a failure mode even if everything looked fine on Saturday.</li>
+<li>Assign one person to call audible changes only if needed. Too many live decision-makers create noise.</li>
+</ul>
+
+<p>If your team uses printed bulletins, make sure they match the final service plan. If you use screens only, confirm the projection operator has the right sequence and a backup copy of key items.</p>
+
+<h2>Welcome and connection: make guest follow-up clear</h2>
+
+<p>Hospitality is not filler around the service. It is part of the ministry of the morning. Greeters should know where to stand, what information they can answer, and when to hand a question to someone else.</p>
+
+<p><strong>Minimum safe setup for guest welcome:</strong></p>
+
+<ul>
+<li>Greeters at visible entrances 15 to 20 minutes before the service starts.</li>
+<li>A simple plan for directing families to <a href="https://ridgecrestchurch.com/kids/">Kids</a> or students to <a href="https://ridgecrestchurch.com/youth/">Youth</a>.</li>
+<li>A connection method that asks only for the information you actually need for follow-up.</li>
+<li>A same-day owner for guest cards, digital forms, or text-based responses.</li>
+</ul>
+
+<p>When you collect contact information, keep it responsible and plain: request only essential details, explain how the information will be used, and limit access to the people who need it for ministry follow-up. A church does not need operational fog around guest data.</p>
+
+<h2>Announcements and prayer: brief, accurate, and timely</h2>
+
+<p>Announcements should help people act. They should not become a second sermon or a rolling list of half-confirmed details. Choose the two or three items that matter most this week, state them clearly, and point people to the right page for details.</p>
+
+<ul>
+<li>Use the live service for timely, high-priority items.</li>
+<li>Use the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for dates, times, and logistics.</li>
+<li>Use the <a href="https://ridgecrestchurch.com/news/">News</a> page for fuller updates, ministry notes, or reminders people may revisit later.</li>
+<li>Keep prayer transitions intentional by deciding in advance who will lead and what the time boundary is.</li>
+</ul>
+
+<p>A short prayer can still be thoughtful. A short announcement can still be useful. Precision serves the room.</p>
+
+<h2>Kids ministry flow: protect check-in and handoff timing</h2>
+
+<p>Children's ministry is one of the clearest places where a written checklist pays off. Families feel it immediately when check-in is organized and volunteers are prepared.</p>
+
+<ul>
+<li>Open check-in early enough to prevent a line from forming at service start.</li>
+<li>Verify classroom coverage, allergy notes, bathroom procedures, and pickup expectations before families arrive.</li>
+<li>Keep parent pickup instructions simple and consistent each week.</li>
+<li>Make sure the route from the main entrance to the <a href="https://ridgecrestchurch.com/kids/">Kids</a> area is obvious for first-time visitors.</li>
+</ul>
+
+<p>If kids begin in the sanctuary and transition later, mark the timing in the service order so volunteers are in place before the handoff begins. A late handoff creates confusion for parents, teachers, and the platform team at the same time.</p>
+
+<h2>Youth ministry flow: decide the student plan in advance</h2>
+
+<p>Not every church handles student ministry the same way on Sunday morning. Some students stay in the full service. Some move after worship. Some alternate by week. The important point is not the format. It is the clarity.</p>
+
+<ul>
+<li>Confirm whether students attend the full service or transition at a set point.</li>
+<li>Make sure leaders know where students should gather, who is responsible for them, and what pickup or dismissal looks like.</li>
+<li>Share schedule changes through the <a href="https://ridgecrestchurch.com/youth/">Youth</a> page, <a href="https://ridgecrestchurch.com/news/">News</a>, or direct volunteer communication before Sunday morning.</li>
+</ul>
+
+<p>A good student plan removes guesswork for parents and leaders alike.</p>
+
+<h2>Tech and facilities: prepare the room people will actually experience</h2>
+
+<p>People notice the room before they notice your process. Tech and facility checks should cover what a first-time guest and a regular volunteer will both encounter.</p>
+
+<ul>
+<li>Slides, presentation computer, confidence monitor, and backup files</li>
+<li>Microphones, batteries, audio routing, and livestream or recording checks</li>
+<li>Restrooms stocked and clearly marked</li>
+<li>Seating ready for expected attendance and accessible entry routes open</li>
+<li>Heating, cooling, lighting, and any rooms needed after the service</li>
+</ul>
+
+<p>Walk the building with fresh eyes. If a hallway is unclear, a restroom is out of supplies, or a sign is missing, Sunday morning will magnify it.</p>
+
+<h2>Communication: decide who sends what to whom</h2>
+
+<p>Most Sunday chaos is not a values problem. It is a communication problem. The easiest way to fix that is to assign owners for each update.</p>
+
+<p><strong>Keep the communication chain simple:</strong></p>
+
+<ul>
+<li>The service coordinator sends the final order to worship, tech, and platform leaders.</li>
+<li>Kids and youth leaders confirm volunteer coverage and any room or schedule changes with their teams.</li>
+<li>The person handling public updates posts changes in the right place, usually the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for schedules and the <a href="https://ridgecrestchurch.com/news/">News</a> page for broader updates.</li>
+<li>Guest follow-up and ministry questions are routed to the right staff contact through the <a href="https://ridgecrestchurch.com/contacts/">Contacts</a> page.</li>
+</ul>
+
+<p>If a change matters enough to mention from the platform, it matters enough to send to the people serving that morning.</p>
+
+<h2>A simple Sunday service checklist to reuse each week</h2>
+
+<ol>
+<li>Finalize the order of service and confirm who owns each segment.</li>
+<li>Review volunteer coverage for hospitality, kids, youth, worship, tech, and facilities.</li>
+<li>Update slides, lyrics, announcement notes, and backup files.</li>
+<li>Prepare guest follow-up materials and identify who collects them.</li>
+<li>Open kids check-in and confirm safety basics before families arrive.</li>
+<li>Confirm the youth ministry plan and any service-time transitions.</li>
+<li>Test microphones, audio, presentation screens, and livestream workflow.</li>
+<li>Walk the building for restrooms, signage, seating, and accessibility.</li>
+<li>Post final public-facing updates in the right channel: calendar, news, or direct contact.</li>
+<li>Hold a short final check-in with the leaders on site before service begins.</li>
+</ol>
+
+<p>A stable Sunday does not require a complicated system. It requires one documented plan, clear ownership, and the discipline to review the same handoffs every week. If your current process feels reactive, start with the list above, trim it to what your church actually needs, and keep it where every team can reach it. Order is expensive in small ways. Chaos is expensive all at once.</p>
+
+<p>If you need to confirm service details, event timing, or the right ministry contact before the week begins, use the church’s <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>, <a href="https://ridgecrestchurch.com/news/">News</a>, and <a href="https://ridgecrestchurch.com/contacts/">Contacts</a> pages as your baseline.</p>

codex
The article body is in place. I’m publishing the post now with the planned slug, assigning it to `Grant Vale`, and setting the imported image as featured before I run the required verification checks.
exec
/bin/bash -lc 'post_id=$(wp post create --post_type=post --post_status=publish --post_title='"'How to Plan a Great Sunday: A Simple Church Service Checklist' --post_name='how-to-plan-a-great-sunday-checklist' --post_author=3 --post_excerpt='A practical church service checklist for worship, announcements, kids and youth handoffs, guest follow-up, and Sunday morning communication.' --post_content=\""'$(cat wp-content/uploads/flatlogic-article-tasks/job-36/how-to-plan-a-great-sunday-checklist.html)" --porcelain) && wp post meta update "$post_id" _thumbnail_id 76 >/dev/null && echo "$post_id"' in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "wp option get page_for_posts && wp post url 23 && curl -I -L --silent https://ridgecrestchurch.com/blog/ | sed -n '1,20p'" in /home/ubuntu/apps/ridgecrestchurch.com
diff --git a//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-36/how-to-plan-a-great-sunday-checklist.html b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-36/how-to-plan-a-great-sunday-checklist.html
new file mode 100644
index 0000000000000000000000000000000000000000..ddcb6ed3321dea7fe2be10451aef92ad57550d76
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-36/how-to-plan-a-great-sunday-checklist.html
@@ -0,0 +1,199 @@
+<p><strong><em>A calm Sunday service is rarely accidental. It usually comes from a short, repeatable checklist that keeps worship, hospitality, kids ministry, youth transitions, and follow-up from drifting into preventable confusion.</em></strong></p>
+
+<p>If your team has ever asked, "Who is opening the building?" "Did the slides get updated?" "Who is covering kids check-in?" or "How will we follow up with first-time guests?" this article is for you. A healthy Sunday plan does not need to be complicated. It needs to be clear, shared, and easy to run when the morning gets busy.</p>
+
+<figure class="wp-block-image size-large"><img src="https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg" alt="Planning materials on a desk with a calendar and smartphone for Sunday service coordination" class="wp-image-76" /><figcaption>A simple planning rhythm helps each Sunday start with fewer last-minute surprises.</figcaption></figure>
+
+<p>At <a href="https://ridgecrestchurch.com/about-us/">Ridgecrest Baptist Church</a>, Sunday ministry touches more than the order of service. It includes worship preparation, guest welcome, prayer, children and student handoffs, building readiness, and timely communication. When those parts are aligned, people can focus on worship and connection instead of chasing missing details.</p>
+
+<h2>Why a simple checklist matters</h2>
+
+<p>A checklist creates a baseline. It protects the team from relying on memory, and it lowers the odds that one missed handoff will affect the whole morning. The goal is not to make ministry mechanical. The goal is to remove avoidable friction so volunteers and staff can serve people well.</p>
+
+<p><strong>A good Sunday checklist does four jobs:</strong></p>
+
+<ul>
+<li>It gives each team a clear role before people arrive.</li>
+<li>It reduces last-minute surprises around sound, slides, seating, and room setup.</li>
+<li>It protects kids and student ministry transitions with documented handoff steps.</li>
+<li>It creates a consistent follow-up path for guests, prayer needs, and event reminders.</li>
+</ul>
+
+<p>If your church already publishes updates through the <a href="https://ridgecrestchurch.com/news/">News</a> page and upcoming schedules through the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>, your checklist should point teams back to those same sources. One source of truth beats four versions of the plan every time.</p>
+
+<h2>The Sunday timeline</h2>
+
+<p>Most service-day problems start before Sunday. The easiest fix is to divide preparation into three windows: the week before, the day before, and the final 30 minutes.</p>
+
+<table>
+<thead>
+<tr>
+<th>When</th>
+<th>What to confirm</th>
+<th>Primary owner</th>
+<th>Why it matters</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>Week before</td>
+<td>Order of service, volunteer schedule, kids/youth staffing, announcements, and event updates</td>
+<td>Staff lead or Sunday coordinator</td>
+<td>Prevents avoidable gaps before the weekend starts</td>
+</tr>
+<tr>
+<td>Day before</td>
+<td>Slides, song order, microphones, printed notes, room setup, and supply restock</td>
+<td>Worship, tech, facilities, and ministry leaders</td>
+<td>Catches errors while there is still time to correct them calmly</td>
+</tr>
+<tr>
+<td>30 minutes before service</td>
+<td>Doors unlocked, greeters in place, kids check-in ready, livestream/audio tested, and platform teams present</td>
+<td>On-site team leads</td>
+<td>Keeps the final handoff from turning into a scramble</td>
+</tr>
+</tbody>
+</table>
+
+<h3>What to prepare the week before</h3>
+
+<ul>
+<li>Finalize the order of service and distribute it to worship, tech, and platform leaders.</li>
+<li>Confirm which announcements need to be said live and which belong on the <a href="https://ridgecrestchurch.com/news/">News</a> page or <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>.</li>
+<li>Review volunteer assignments for greeters, ushers, kids check-in, nursery, student leaders, and security-minded building coverage.</li>
+<li>Make sure contact details for key leaders are current on the <a href="https://ridgecrestchurch.com/contacts/">Contacts</a> page so volunteers know where to direct questions.</li>
+</ul>
+
+<h3>What to prepare the day before</h3>
+
+<ul>
+<li>Load final slides, lyrics, Scripture references, and announcement screens.</li>
+<li>Test microphones, playback sources, batteries, and any livestream or recording workflow.</li>
+<li>Walk through classrooms, restrooms, entryways, and seating areas for cleanliness, signage, and accessibility.</li>
+<li>Check that kids ministry labels, sign-in materials, and emergency contacts are available where needed.</li>
+</ul>
+
+<h3>What to confirm 30 minutes before service</h3>
+
+<ul>
+<li>Greeters are at doors and know how to guide visitors.</li>
+<li>The worship team and tech team have completed sound check and cue review.</li>
+<li>Kids ministry volunteers are ready to receive families on time.</li>
+<li>Youth leaders know whether students begin in the main service, move later, or stay together for the full morning.</li>
+<li>Someone is assigned to receive guest questions and route them to the right ministry leader.</li>
+</ul>
+
+<h2>Worship and music: keep the platform steady</h2>
+
+<p>The worship portion of the morning needs an agreed sequence, not assumptions. Use one shared service order and make sure everyone on platform has the same version.</p>
+
+<ul>
+<li>Confirm the opening song, transitions, prayer moments, offering, message, and closing response.</li>
+<li>Verify lyric slides, lower thirds, and any Scripture references before rehearsal ends.</li>
+<li>Check microphones individually, not in theory. A muted channel is still a failure mode even if everything looked fine on Saturday.</li>
+<li>Assign one person to call audible changes only if needed. Too many live decision-makers create noise.</li>
+</ul>
+
+<p>If your team uses printed bulletins, make sure they match the final service plan. If you use screens only, confirm the projection operator has the right sequence and a backup copy of key items.</p>
+
+<h2>Welcome and connection: make guest follow-up clear</h2>
+
+<p>Hospitality is not filler around the service. It is part of the ministry of the morning. Greeters should know where to stand, what information they can answer, and when to hand a question to someone else.</p>
+
+<p><strong>Minimum safe setup for guest welcome:</strong></p>
+
+<ul>
+<li>Greeters at visible entrances 15 to 20 minutes before the service starts.</li>
+<li>A simple plan for directing families to <a href="https://ridgecrestchurch.com/kids/">Kids</a> or students to <a href="https://ridgecrestchurch.com/youth/">Youth</a>.</li>
+<li>A connection method that asks only for the information you actually need for follow-up.</li>
+<li>A same-day owner for guest cards, digital forms, or text-based responses.</li>
+</ul>
+
+<p>When you collect contact information, keep it responsible and plain: request only essential details, explain how the information will be used, and limit access to the people who need it for ministry follow-up. A church does not need operational fog around guest data.</p>
+
+<h2>Announcements and prayer: brief, accurate, and timely</h2>
+
+<p>Announcements should help people act. They should not become a second sermon or a rolling list of half-confirmed details. Choose the two or three items that matter most this week, state them clearly, and point people to the right page for details.</p>
+
+<ul>
+<li>Use the live service for timely, high-priority items.</li>
+<li>Use the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for dates, times, and logistics.</li>
+<li>Use the <a href="https://ridgecrestchurch.com/news/">News</a> page for fuller updates, ministry notes, or reminders people may revisit later.</li>
+<li>Keep prayer transitions intentional by deciding in advance who will lead and what the time boundary is.</li>
+</ul>
+
+<p>A short prayer can still be thoughtful. A short announcement can still be useful. Precision serves the room.</p>
+
+<h2>Kids ministry flow: protect check-in and handoff timing</h2>
+
+<p>Children's ministry is one of the clearest places where a written checklist pays off. Families feel it immediately when check-in is organized and volunteers are prepared.</p>
+
+<ul>
+<li>Open check-in early enough to prevent a line from forming at service start.</li>
+<li>Verify classroom coverage, allergy notes, bathroom procedures, and pickup expectations before families arrive.</li>
+<li>Keep parent pickup instructions simple and consistent each week.</li>
+<li>Make sure the route from the main entrance to the <a href="https://ridgecrestchurch.com/kids/">Kids</a> area is obvious for first-time visitors.</li>
+</ul>
+
+<p>If kids begin in the sanctuary and transition later, mark the timing in the service order so volunteers are in place before the handoff begins. A late handoff creates confusion for parents, teachers, and the platform team at the same time.</p>
+
+<h2>Youth ministry flow: decide the student plan in advance</h2>
+
+<p>Not every church handles student ministry the same way on Sunday morning. Some students stay in the full service. Some move after worship. Some alternate by week. The important point is not the format. It is the clarity.</p>
+
+<ul>
+<li>Confirm whether students attend the full service or transition at a set point.</li>
+<li>Make sure leaders know where students should gather, who is responsible for them, and what pickup or dismissal looks like.</li>
+<li>Share schedule changes through the <a href="https://ridgecrestchurch.com/youth/">Youth</a> page, <a href="https://ridgecrestchurch.com/news/">News</a>, or direct volunteer communication before Sunday morning.</li>
+</ul>
+
+<p>A good student plan removes guesswork for parents and leaders alike.</p>
+
+<h2>Tech and facilities: prepare the room people will actually experience</h2>
+
+<p>People notice the room before they notice your process. Tech and facility checks should cover what a first-time guest and a regular volunteer will both encounter.</p>
+
+<ul>
+<li>Slides, presentation computer, confidence monitor, and backup files</li>
+<li>Microphones, batteries, audio routing, and livestream or recording checks</li>
+<li>Restrooms stocked and clearly marked</li>
+<li>Seating ready for expected attendance and accessible entry routes open</li>
+<li>Heating, cooling, lighting, and any rooms needed after the service</li>
+</ul>
+
+<p>Walk the building with fresh eyes. If a hallway is unclear, a restroom is out of supplies, or a sign is missing, Sunday morning will magnify it.</p>
+
+<h2>Communication: decide who sends what to whom</h2>
+
+<p>Most Sunday chaos is not a values problem. It is a communication problem. The easiest way to fix that is to assign owners for each update.</p>
+
+<p><strong>Keep the communication chain simple:</strong></p>
+
+<ul>
+<li>The service coordinator sends the final order to worship, tech, and platform leaders.</li>
+<li>Kids and youth leaders confirm volunteer coverage and any room or schedule changes with their teams.</li>
+<li>The person handling public updates posts changes in the right place, usually the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for schedules and the <a href="https://ridgecrestchurch.com/news/">News</a> page for broader updates.</li>
+<li>Guest follow-up and ministry questions are routed to the right staff contact through the <a href="https://ridgecrestchurch.com/contacts/">Contacts</a> page.</li>
+</ul>
+
+<p>If a change matters enough to mention from the platform, it matters enough to send to the people serving that morning.</p>
+
+<h2>A simple Sunday service checklist to reuse each week</h2>
+
+<ol>
+<li>Finalize the order of service and confirm who owns each segment.</li>
+<li>Review volunteer coverage for hospitality, kids, youth, worship, tech, and facilities.</li>
+<li>Update slides, lyrics, announcement notes, and backup files.</li>
+<li>Prepare guest follow-up materials and identify who collects them.</li>
+<li>Open kids check-in and confirm safety basics before families arrive.</li>
+<li>Confirm the youth ministry plan and any service-time transitions.</li>
+<li>Test microphones, audio, presentation screens, and livestream workflow.</li>
+<li>Walk the building for restrooms, signage, seating, and accessibility.</li>
+<li>Post final public-facing updates in the right channel: calendar, news, or direct contact.</li>
+<li>Hold a short final check-in with the leaders on site before service begins.</li>
+</ol>
+
+<p>A stable Sunday does not require a complicated system. It requires one documented plan, clear ownership, and the discipline to review the same handoffs every week. If your current process feels reactive, start with the list above, trim it to what your church actually needs, and keep it where every team can reach it. Order is expensive in small ways. Chaos is expensive all at once.</p>
+
+<p>If you need to confirm service details, event timing, or the right ministry contact before the week begins, use the church’s <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>, <a href="https://ridgecrestchurch.com/news/">News</a>, and <a href="https://ridgecrestchurch.com/contacts/">Contacts</a> pages as your baseline.</p>

 succeeded in 1393ms:
77

 succeeded in 1543ms:
23
https://ridgecrestchurch.com/blog/
HTTP/2 200 
date: Mon, 11 May 2026 20:03:15 GMT
content-type: text/html; charset=UTF-8
link: <https://ridgecrestchurch.com/wp-json/>; rel="https://api.w.org/"
server: cloudflare
cf-cache-status: DYNAMIC
report-to: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=o802a%2BSU4BIwcgH7FBBzrVbB5TM1e3GrPqfksgPL6eRjBBkwwSdaItu%2FM%2BkSDjOsgzw5RLSP%2BNGgZlSRS4TXjZ5JW3t9uTY74pMplbAORnc8Ufl%2BCQ2hkhxa17JZ41zb17CeH6muvA%3D%3D"}]}
nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
cf-ray: 9fa3c930d8f001fa-WAW
alt-svc: h3=":443"; ma=86400


diff --git a//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-36/how-to-plan-a-great-sunday-checklist.html b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-36/how-to-plan-a-great-sunday-checklist.html
new file mode 100644
index 0000000000000000000000000000000000000000..ddcb6ed3321dea7fe2be10451aef92ad57550d76
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-36/how-to-plan-a-great-sunday-checklist.html
@@ -0,0 +1,199 @@
+<p><strong><em>A calm Sunday service is rarely accidental. It usually comes from a short, repeatable checklist that keeps worship, hospitality, kids ministry, youth transitions, and follow-up from drifting into preventable confusion.</em></strong></p>
+
+<p>If your team has ever asked, "Who is opening the building?" "Did the slides get updated?" "Who is covering kids check-in?" or "How will we follow up with first-time guests?" this article is for you. A healthy Sunday plan does not need to be complicated. It needs to be clear, shared, and easy to run when the morning gets busy.</p>
+
+<figure class="wp-block-image size-large"><img src="https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg" alt="Planning materials on a desk with a calendar and smartphone for Sunday service coordination" class="wp-image-76" /><figcaption>A simple planning rhythm helps each Sunday start with fewer last-minute surprises.</figcaption></figure>
+
+<p>At <a href="https://ridgecrestchurch.com/about-us/">Ridgecrest Baptist Church</a>, Sunday ministry touches more than the order of service. It includes worship preparation, guest welcome, prayer, children and student handoffs, building readiness, and timely communication. When those parts are aligned, people can focus on worship and connection instead of chasing missing details.</p>
+
+<h2>Why a simple checklist matters</h2>
+
+<p>A checklist creates a baseline. It protects the team from relying on memory, and it lowers the odds that one missed handoff will affect the whole morning. The goal is not to make ministry mechanical. The goal is to remove avoidable friction so volunteers and staff can serve people well.</p>
+
+<p><strong>A good Sunday checklist does four jobs:</strong></p>
+
+<ul>
+<li>It gives each team a clear role before people arrive.</li>
+<li>It reduces last-minute surprises around sound, slides, seating, and room setup.</li>
+<li>It protects kids and student ministry transitions with documented handoff steps.</li>
+<li>It creates a consistent follow-up path for guests, prayer needs, and event reminders.</li>
+</ul>
+
+<p>If your church already publishes updates through the <a href="https://ridgecrestchurch.com/news/">News</a> page and upcoming schedules through the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>, your checklist should point teams back to those same sources. One source of truth beats four versions of the plan every time.</p>
+
+<h2>The Sunday timeline</h2>
+
+<p>Most service-day problems start before Sunday. The easiest fix is to divide preparation into three windows: the week before, the day before, and the final 30 minutes.</p>
+
+<table>
+<thead>
+<tr>
+<th>When</th>
+<th>What to confirm</th>
+<th>Primary owner</th>
+<th>Why it matters</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>Week before</td>
+<td>Order of service, volunteer schedule, kids/youth staffing, announcements, and event updates</td>
+<td>Staff lead or Sunday coordinator</td>
+<td>Prevents avoidable gaps before the weekend starts</td>
+</tr>
+<tr>
+<td>Day before</td>
+<td>Slides, song order, microphones, printed notes, room setup, and supply restock</td>
+<td>Worship, tech, facilities, and ministry leaders</td>
+<td>Catches errors while there is still time to correct them calmly</td>
+</tr>
+<tr>
+<td>30 minutes before service</td>
+<td>Doors unlocked, greeters in place, kids check-in ready, livestream/audio tested, and platform teams present</td>
+<td>On-site team leads</td>
+<td>Keeps the final handoff from turning into a scramble</td>
+</tr>
+</tbody>
+</table>
+
+<h3>What to prepare the week before</h3>
+
+<ul>
+<li>Finalize the order of service and distribute it to worship, tech, and platform leaders.</li>
+<li>Confirm which announcements need to be said live and which belong on the <a href="https://ridgecrestchurch.com/news/">News</a> page or <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>.</li>
+<li>Review volunteer assignments for greeters, ushers, kids check-in, nursery, student leaders, and security-minded building coverage.</li>
+<li>Make sure contact details for key leaders are current on the <a href="https://ridgecrestchurch.com/contacts/">Contacts</a> page so volunteers know where to direct questions.</li>
+</ul>
+
+<h3>What to prepare the day before</h3>
+
+<ul>
+<li>Load final slides, lyrics, Scripture references, and announcement screens.</li>
+<li>Test microphones, playback sources, batteries, and any livestream or recording workflow.</li>
+<li>Walk through classrooms, restrooms, entryways, and seating areas for cleanliness, signage, and accessibility.</li>
+<li>Check that kids ministry labels, sign-in materials, and emergency contacts are available where needed.</li>
+</ul>
+
+<h3>What to confirm 30 minutes before service</h3>
+
+<ul>
+<li>Greeters are at doors and know how to guide visitors.</li>
+<li>The worship team and tech team have completed sound check and cue review.</li>
+<li>Kids ministry volunteers are ready to receive families on time.</li>
+<li>Youth leaders know whether students begin in the main service, move later, or stay together for the full morning.</li>
+<li>Someone is assigned to receive guest questions and route them to the right ministry leader.</li>
+</ul>
+
+<h2>Worship and music: keep the platform steady</h2>
+
+<p>The worship portion of the morning needs an agreed sequence, not assumptions. Use one shared service order and make sure everyone on platform has the same version.</p>
+
+<ul>
+<li>Confirm the opening song, transitions, prayer moments, offering, message, and closing response.</li>
+<li>Verify lyric slides, lower thirds, and any Scripture references before rehearsal ends.</li>
+<li>Check microphones individually, not in theory. A muted channel is still a failure mode even if everything looked fine on Saturday.</li>
+<li>Assign one person to call audible changes only if needed. Too many live decision-makers create noise.</li>
+</ul>
+
+<p>If your team uses printed bulletins, make sure they match the final service plan. If you use screens only, confirm the projection operator has the right sequence and a backup copy of key items.</p>
+
+<h2>Welcome and connection: make guest follow-up clear</h2>
+
+<p>Hospitality is not filler around the service. It is part of the ministry of the morning. Greeters should know where to stand, what information they can answer, and when to hand a question to someone else.</p>
+
+<p><strong>Minimum safe setup for guest welcome:</strong></p>
+
+<ul>
+<li>Greeters at visible entrances 15 to 20 minutes before the service starts.</li>
+<li>A simple plan for directing families to <a href="https://ridgecrestchurch.com/kids/">Kids</a> or students to <a href="https://ridgecrestchurch.com/youth/">Youth</a>.</li>
+<li>A connection method that asks only for the information you actually need for follow-up.</li>
+<li>A same-day owner for guest cards, digital forms, or text-based responses.</li>
+</ul>
+
+<p>When you collect contact information, keep it responsible and plain: request only essential details, explain how the information will be used, and limit access to the people who need it for ministry follow-up. A church does not need operational fog around guest data.</p>
+
+<h2>Announcements and prayer: brief, accurate, and timely</h2>
+
+<p>Announcements should help people act. They should not become a second sermon or a rolling list of half-confirmed details. Choose the two or three items that matter most this week, state them clearly, and point people to the right page for details.</p>
+
+<ul>
+<li>Use the live service for timely, high-priority items.</li>
+<li>Use the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for dates, times, and logistics.</li>
+<li>Use the <a href="https://ridgecrestchurch.com/news/">News</a> page for fuller updates, ministry notes, or reminders people may revisit later.</li>
+<li>Keep prayer transitions intentional by deciding in advance who will lead and what the time boundary is.</li>
+</ul>
+
+<p>A short prayer can still be thoughtful. A short announcement can still be useful. Precision serves the room.</p>
+
+<h2>Kids ministry flow: protect check-in and handoff timing</h2>
+
+<p>Children's ministry is one of the clearest places where a written checklist pays off. Families feel it immediately when check-in is organized and volunteers are prepared.</p>
+
+<ul>
+<li>Open check-in early enough to prevent a line from forming at service start.</li>
+<li>Verify classroom coverage, allergy notes, bathroom procedures, and pickup expectations before families arrive.</li>
+<li>Keep parent pickup instructions simple and consistent each week.</li>
+<li>Make sure the route from the main entrance to the <a href="https://ridgecrestchurch.com/kids/">Kids</a> area is obvious for first-time visitors.</li>
+</ul>
+
+<p>If kids begin in the sanctuary and transition later, mark the timing in the service order so volunteers are in place before the handoff begins. A late handoff creates confusion for parents, teachers, and the platform team at the same time.</p>
+
+<h2>Youth ministry flow: decide the student plan in advance</h2>
+
+<p>Not every church handles student ministry the same way on Sunday morning. Some students stay in the full service. Some move after worship. Some alternate by week. The important point is not the format. It is the clarity.</p>
+
+<ul>
+<li>Confirm whether students attend the full service or transition at a set point.</li>
+<li>Make sure leaders know where students should gather, who is responsible for them, and what pickup or dismissal looks like.</li>
+<li>Share schedule changes through the <a href="https://ridgecrestchurch.com/youth/">Youth</a> page, <a href="https://ridgecrestchurch.com/news/">News</a>, or direct volunteer communication before Sunday morning.</li>
+</ul>
+
+<p>A good student plan removes guesswork for parents and leaders alike.</p>
+
+<h2>Tech and facilities: prepare the room people will actually experience</h2>
+
+<p>People notice the room before they notice your process. Tech and facility checks should cover what a first-time guest and a regular volunteer will both encounter.</p>
+
+<ul>
+<li>Slides, presentation computer, confidence monitor, and backup files</li>
+<li>Microphones, batteries, audio routing, and livestream or recording checks</li>
+<li>Restrooms stocked and clearly marked</li>
+<li>Seating ready for expected attendance and accessible entry routes open</li>
+<li>Heating, cooling, lighting, and any rooms needed after the service</li>
+</ul>
+
+<p>Walk the building with fresh eyes. If a hallway is unclear, a restroom is out of supplies, or a sign is missing, Sunday morning will magnify it.</p>
+
+<h2>Communication: decide who sends what to whom</h2>
+
+<p>Most Sunday chaos is not a values problem. It is a communication problem. The easiest way to fix that is to assign owners for each update.</p>
+
+<p><strong>Keep the communication chain simple:</strong></p>
+
+<ul>
+<li>The service coordinator sends the final order to worship, tech, and platform leaders.</li>
+<li>Kids and youth leaders confirm volunteer coverage and any room or schedule changes with their teams.</li>
+<li>The person handling public updates posts changes in the right place, usually the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for schedules and the <a href="https://ridgecrestchurch.com/news/">News</a> page for broader updates.</li>
+<li>Guest follow-up and ministry questions are routed to the right staff contact through the <a href="https://ridgecrestchurch.com/contacts/">Contacts</a> page.</li>
+</ul>
+
+<p>If a change matters enough to mention from the platform, it matters enough to send to the people serving that morning.</p>
+
+<h2>A simple Sunday service checklist to reuse each week</h2>
+
+<ol>
+<li>Finalize the order of service and confirm who owns each segment.</li>
+<li>Review volunteer coverage for hospitality, kids, youth, worship, tech, and facilities.</li>
+<li>Update slides, lyrics, announcement notes, and backup files.</li>
+<li>Prepare guest follow-up materials and identify who collects them.</li>
+<li>Open kids check-in and confirm safety basics before families arrive.</li>
+<li>Confirm the youth ministry plan and any service-time transitions.</li>
+<li>Test microphones, audio, presentation screens, and livestream workflow.</li>
+<li>Walk the building for restrooms, signage, seating, and accessibility.</li>
+<li>Post final public-facing updates in the right channel: calendar, news, or direct contact.</li>
+<li>Hold a short final check-in with the leaders on site before service begins.</li>
+</ol>
+
+<p>A stable Sunday does not require a complicated system. It requires one documented plan, clear ownership, and the discipline to review the same handoffs every week. If your current process feels reactive, start with the list above, trim it to what your church actually needs, and keep it where every team can reach it. Order is expensive in small ways. Chaos is expensive all at once.</p>
+
+<p>If you need to confirm service details, event timing, or the right ministry contact before the week begins, use the church’s <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>, <a href="https://ridgecrestchurch.com/news/">News</a>, and <a href="https://ridgecrestchurch.com/contacts/">Contacts</a> pages as your baseline.</p>

codex
The post is published. I’m on the final verification pass now: checking the stored post fields, the public URL response, whether `/blog/` surfaces it, and whether the article body includes the registered inline image attachment.
exec
/bin/bash -lc "wp post get 77 --fields=ID,post_title,post_name,post_status,post_author,post_date,post_excerpt --format=json && printf '\\nURL\\n' && wp post url 77" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc 'post_url=$(wp post url 77) && printf '"'POST HEADERS\\n' && curl -I -L --silent \""'$post_url" | sed -n '"'1,20p' && printf '\\nBLOG MATCHES\\n' && curl -L --silent https://ridgecrestchurch.com/blog/ | rg -n 'How to Plan a Great Sunday|how-to-plan-a-great-sunday-checklist' -n || true" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "wp eval '
"'$post = get_post(77);
$content = $post ? $post->post_content : "";
preg_match_all("/wp-image-('"\\\\d+)/\", "'$content, $m);
$ids = array_values(array_unique($m[1] ?? []));
echo "INLINE_IMAGE_IDS=" . ($ids ? implode(",", $ids) : "none") . "'"\\n\";
echo \"HAS_FIGURE=\" . (strpos("'$content, "<figure") !== false ? "yes" : "no") . "'"\\n\";
echo \"THUMBNAIL_ID=\" . get_post_thumbnail_id(77) . \"\\n\";
'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 513ms:
INLINE_IMAGE_IDS=76
HAS_FIGURE=yes
THUMBNAIL_ID=76

 succeeded in 1049ms:
{"ID":77,"post_author":"3","post_date":"2026-05-11 15:03:13","post_title":"How to Plan a Great Sunday: A Simple Church Service Checklist","post_excerpt":"A practical church service checklist for worship, announcements, kids and youth handoffs, guest follow-up, and Sunday morning communication.","post_status":"publish","post_name":"how-to-plan-a-great-sunday-checklist"}

URL
https://ridgecrestchurch.com/how-to-plan-a-great-sunday-checklist/

diff --git a//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-36/how-to-plan-a-great-sunday-checklist.html b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-36/how-to-plan-a-great-sunday-checklist.html
new file mode 100644
index 0000000000000000000000000000000000000000..ddcb6ed3321dea7fe2be10451aef92ad57550d76
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-36/how-to-plan-a-great-sunday-checklist.html
@@ -0,0 +1,199 @@
+<p><strong><em>A calm Sunday service is rarely accidental. It usually comes from a short, repeatable checklist that keeps worship, hospitality, kids ministry, youth transitions, and follow-up from drifting into preventable confusion.</em></strong></p>
+
+<p>If your team has ever asked, "Who is opening the building?" "Did the slides get updated?" "Who is covering kids check-in?" or "How will we follow up with first-time guests?" this article is for you. A healthy Sunday plan does not need to be complicated. It needs to be clear, shared, and easy to run when the morning gets busy.</p>
+
+<figure class="wp-block-image size-large"><img src="https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg" alt="Planning materials on a desk with a calendar and smartphone for Sunday service coordination" class="wp-image-76" /><figcaption>A simple planning rhythm helps each Sunday start with fewer last-minute surprises.</figcaption></figure>
+
+<p>At <a href="https://ridgecrestchurch.com/about-us/">Ridgecrest Baptist Church</a>, Sunday ministry touches more than the order of service. It includes worship preparation, guest welcome, prayer, children and student handoffs, building readiness, and timely communication. When those parts are aligned, people can focus on worship and connection instead of chasing missing details.</p>
+
+<h2>Why a simple checklist matters</h2>
+
+<p>A checklist creates a baseline. It protects the team from relying on memory, and it lowers the odds that one missed handoff will affect the whole morning. The goal is not to make ministry mechanical. The goal is to remove avoidable friction so volunteers and staff can serve people well.</p>
+
+<p><strong>A good Sunday checklist does four jobs:</strong></p>
+
+<ul>
+<li>It gives each team a clear role before people arrive.</li>
+<li>It reduces last-minute surprises around sound, slides, seating, and room setup.</li>
+<li>It protects kids and student ministry transitions with documented handoff steps.</li>
+<li>It creates a consistent follow-up path for guests, prayer needs, and event reminders.</li>
+</ul>
+
+<p>If your church already publishes updates through the <a href="https://ridgecrestchurch.com/news/">News</a> page and upcoming schedules through the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>, your checklist should point teams back to those same sources. One source of truth beats four versions of the plan every time.</p>
+
+<h2>The Sunday timeline</h2>
+
+<p>Most service-day problems start before Sunday. The easiest fix is to divide preparation into three windows: the week before, the day before, and the final 30 minutes.</p>
+
+<table>
+<thead>
+<tr>
+<th>When</th>
+<th>What to confirm</th>
+<th>Primary owner</th>
+<th>Why it matters</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>Week before</td>
+<td>Order of service, volunteer schedule, kids/youth staffing, announcements, and event updates</td>
+<td>Staff lead or Sunday coordinator</td>
+<td>Prevents avoidable gaps before the weekend starts</td>
+</tr>
+<tr>
+<td>Day before</td>
+<td>Slides, song order, microphones, printed notes, room setup, and supply restock</td>
+<td>Worship, tech, facilities, and ministry leaders</td>
+<td>Catches errors while there is still time to correct them calmly</td>
+</tr>
+<tr>
+<td>30 minutes before service</td>
+<td>Doors unlocked, greeters in place, kids check-in ready, livestream/audio tested, and platform teams present</td>
+<td>On-site team leads</td>
+<td>Keeps the final handoff from turning into a scramble</td>
+</tr>
+</tbody>
+</table>
+
+<h3>What to prepare the week before</h3>
+
+<ul>
+<li>Finalize the order of service and distribute it to worship, tech, and platform leaders.</li>
+<li>Confirm which announcements need to be said live and which belong on the <a href="https://ridgecrestchurch.com/news/">News</a> page or <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>.</li>
+<li>Review volunteer assignments for greeters, ushers, kids check-in, nursery, student leaders, and security-minded building coverage.</li>
+<li>Make sure contact details for key leaders are current on the <a href="https://ridgecrestchurch.com/contacts/">Contacts</a> page so volunteers know where to direct questions.</li>
+</ul>
+
+<h3>What to prepare the day before</h3>
+
+<ul>
+<li>Load final slides, lyrics, Scripture references, and announcement screens.</li>
+<li>Test microphones, playback sources, batteries, and any livestream or recording workflow.</li>
+<li>Walk through classrooms, restrooms, entryways, and seating areas for cleanliness, signage, and accessibility.</li>
+<li>Check that kids ministry labels, sign-in materials, and emergency contacts are available where needed.</li>
+</ul>
+
+<h3>What to confirm 30 minutes before service</h3>
+
+<ul>
+<li>Greeters are at doors and know how to guide visitors.</li>
+<li>The worship team and tech team have completed sound check and cue review.</li>
+<li>Kids ministry volunteers are ready to receive families on time.</li>
+<li>Youth leaders know whether students begin in the main service, move later, or stay together for the full morning.</li>
+<li>Someone is assigned to receive guest questions and route them to the right ministry leader.</li>
+</ul>
+
+<h2>Worship and music: keep the platform steady</h2>
+
+<p>The worship portion of the morning needs an agreed sequence, not assumptions. Use one shared service order and make sure everyone on platform has the same version.</p>
+
+<ul>
+<li>Confirm the opening song, transitions, prayer moments, offering, message, and closing response.</li>
+<li>Verify lyric slides, lower thirds, and any Scripture references before rehearsal ends.</li>
+<li>Check microphones individually, not in theory. A muted channel is still a failure mode even if everything looked fine on Saturday.</li>
+<li>Assign one person to call audible changes only if needed. Too many live decision-makers create noise.</li>
+</ul>
+
+<p>If your team uses printed bulletins, make sure they match the final service plan. If you use screens only, confirm the projection operator has the right sequence and a backup copy of key items.</p>
+
+<h2>Welcome and connection: make guest follow-up clear</h2>
+
+<p>Hospitality is not filler around the service. It is part of the ministry of the morning. Greeters should know where to stand, what information they can answer, and when to hand a question to someone else.</p>
+
+<p><strong>Minimum safe setup for guest welcome:</strong></p>
+
+<ul>
+<li>Greeters at visible entrances 15 to 20 minutes before the service starts.</li>
+<li>A simple plan for directing families to <a href="https://ridgecrestchurch.com/kids/">Kids</a> or students to <a href="https://ridgecrestchurch.com/youth/">Youth</a>.</li>
+<li>A connection method that asks only for the information you actually need for follow-up.</li>
+<li>A same-day owner for guest cards, digital forms, or text-based responses.</li>
+</ul>
+
+<p>When you collect contact information, keep it responsible and plain: request only essential details, explain how the information will be used, and limit access to the people who need it for ministry follow-up. A church does not need operational fog around guest data.</p>
+
+<h2>Announcements and prayer: brief, accurate, and timely</h2>
+
+<p>Announcements should help people act. They should not become a second sermon or a rolling list of half-confirmed details. Choose the two or three items that matter most this week, state them clearly, and point people to the right page for details.</p>
+
+<ul>
+<li>Use the live service for timely, high-priority items.</li>
+<li>Use the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for dates, times, and logistics.</li>
+<li>Use the <a href="https://ridgecrestchurch.com/news/">News</a> page for fuller updates, ministry notes, or reminders people may revisit later.</li>
+<li>Keep prayer transitions intentional by deciding in advance who will lead and what the time boundary is.</li>
+</ul>
+
+<p>A short prayer can still be thoughtful. A short announcement can still be useful. Precision serves the room.</p>
+
+<h2>Kids ministry flow: protect check-in and handoff timing</h2>
+
+<p>Children's ministry is one of the clearest places where a written checklist pays off. Families feel it immediately when check-in is organized and volunteers are prepared.</p>
+
+<ul>
+<li>Open check-in early enough to prevent a line from forming at service start.</li>
+<li>Verify classroom coverage, allergy notes, bathroom procedures, and pickup expectations before families arrive.</li>
+<li>Keep parent pickup instructions simple and consistent each week.</li>
+<li>Make sure the route from the main entrance to the <a href="https://ridgecrestchurch.com/kids/">Kids</a> area is obvious for first-time visitors.</li>
+</ul>
+
+<p>If kids begin in the sanctuary and transition later, mark the timing in the service order so volunteers are in place before the handoff begins. A late handoff creates confusion for parents, teachers, and the platform team at the same time.</p>
+
+<h2>Youth ministry flow: decide the student plan in advance</h2>
+
+<p>Not every church handles student ministry the same way on Sunday morning. Some students stay in the full service. Some move after worship. Some alternate by week. The important point is not the format. It is the clarity.</p>
+
+<ul>
+<li>Confirm whether students attend the full service or transition at a set point.</li>
+<li>Make sure leaders know where students should gather, who is responsible for them, and what pickup or dismissal looks like.</li>
+<li>Share schedule changes through the <a href="https://ridgecrestchurch.com/youth/">Youth</a> page, <a href="https://ridgecrestchurch.com/news/">News</a>, or direct volunteer communication before Sunday morning.</li>
+</ul>
+
+<p>A good student plan removes guesswork for parents and leaders alike.</p>
+
+<h2>Tech and facilities: prepare the room people will actually experience</h2>
+
+<p>People notice the room before they notice your process. Tech and facility checks should cover what a first-time guest and a regular volunteer will both encounter.</p>
+
+<ul>
+<li>Slides, presentation computer, confidence monitor, and backup files</li>
+<li>Microphones, batteries, audio routing, and livestream or recording checks</li>
+<li>Restrooms stocked and clearly marked</li>
+<li>Seating ready for expected attendance and accessible entry routes open</li>
+<li>Heating, cooling, lighting, and any rooms needed after the service</li>
+</ul>
+
+<p>Walk the building with fresh eyes. If a hallway is unclear, a restroom is out of supplies, or a sign is missing, Sunday morning will magnify it.</p>
+
+<h2>Communication: decide who sends what to whom</h2>
+
+<p>Most Sunday chaos is not a values problem. It is a communication problem. The easiest way to fix that is to assign owners for each update.</p>
+
+<p><strong>Keep the communication chain simple:</strong></p>
+
+<ul>
+<li>The service coordinator sends the final order to worship, tech, and platform leaders.</li>
+<li>Kids and youth leaders confirm volunteer coverage and any room or schedule changes with their teams.</li>
+<li>The person handling public updates posts changes in the right place, usually the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for schedules and the <a href="https://ridgecrestchurch.com/news/">News</a> page for broader updates.</li>
+<li>Guest follow-up and ministry questions are routed to the right staff contact through the <a href="https://ridgecrestchurch.com/contacts/">Contacts</a> page.</li>
+</ul>
+
+<p>If a change matters enough to mention from the platform, it matters enough to send to the people serving that morning.</p>
+
+<h2>A simple Sunday service checklist to reuse each week</h2>
+
+<ol>
+<li>Finalize the order of service and confirm who owns each segment.</li>
+<li>Review volunteer coverage for hospitality, kids, youth, worship, tech, and facilities.</li>
+<li>Update slides, lyrics, announcement notes, and backup files.</li>
+<li>Prepare guest follow-up materials and identify who collects them.</li>
+<li>Open kids check-in and confirm safety basics before families arrive.</li>
+<li>Confirm the youth ministry plan and any service-time transitions.</li>
+<li>Test microphones, audio, presentation screens, and livestream workflow.</li>
+<li>Walk the building for restrooms, signage, seating, and accessibility.</li>
+<li>Post final public-facing updates in the right channel: calendar, news, or direct contact.</li>
+<li>Hold a short final check-in with the leaders on site before service begins.</li>
+</ol>
+
+<p>A stable Sunday does not require a complicated system. It requires one documented plan, clear ownership, and the discipline to review the same handoffs every week. If your current process feels reactive, start with the list above, trim it to what your church actually needs, and keep it where every team can reach it. Order is expensive in small ways. Chaos is expensive all at once.</p>
+
+<p>If you need to confirm service details, event timing, or the right ministry contact before the week begins, use the church’s <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>, <a href="https://ridgecrestchurch.com/news/">News</a>, and <a href="https://ridgecrestchurch.com/contacts/">Contacts</a> pages as your baseline.</p>

 succeeded in 1450ms:
POST HEADERS
HTTP/2 200 
date: Mon, 11 May 2026 20:03:25 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/77>; rel="alternate"; title="JSON"; type="application/json", <https://ridgecrestchurch.com/?p=77>; 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=EvabVD4q1IOiC%2F9bZ5Nibf0D8Yo0E54%2BAcwXUYj%2BV%2FB9ZqsojtZ8Rs2l7GEcC%2BIsLV%2F9YBv53ztObGU87f2J9HY5ajaPUo3zlM0NE4S3QdApXl3jCCFG05GJE7thPiZ%2Fy2gl2lw2%2Fg%3D%3D"}]}
nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
cf-ray: 9fa3c972ea303463-WAW
alt-svc: h3=":443"; ma=86400


BLOG MATCHES
409:			<header class="entry-header">	<h2 class="entry-title" itemprop="headline"><a href="https://ridgecrestchurch.com/how-to-plan-a-great-sunday-checklist/" rel="bookmark">How to Plan a Great Sunday: A Simple Church Service Checklist</a></h2>
415:<a href="https://ridgecrestchurch.com/how-to-plan-a-great-sunday-checklist/" title="How to Plan a Great Sunday: A Simple Church Service Checklist"><img data-src="https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg" class="wp-post-image lazyload" alt="Planning materials on a desk with a calendar and smartphone for Sunday service coordination" decoding="async" itemprop="image" src="data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==" style="--smush-placeholder-width: 1024px; --smush-placeholder-aspect-ratio: 1024/683;" /></a><p>A practical church service checklist for worship, announcements, kids and youth handoffs, guest follow-up, and Sunday morning communication.</p>

diff --git a//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-36/how-to-plan-a-great-sunday-checklist.html b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-36/how-to-plan-a-great-sunday-checklist.html
new file mode 100644
index 0000000000000000000000000000000000000000..ddcb6ed3321dea7fe2be10451aef92ad57550d76
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-36/how-to-plan-a-great-sunday-checklist.html
@@ -0,0 +1,199 @@
+<p><strong><em>A calm Sunday service is rarely accidental. It usually comes from a short, repeatable checklist that keeps worship, hospitality, kids ministry, youth transitions, and follow-up from drifting into preventable confusion.</em></strong></p>
+
+<p>If your team has ever asked, "Who is opening the building?" "Did the slides get updated?" "Who is covering kids check-in?" or "How will we follow up with first-time guests?" this article is for you. A healthy Sunday plan does not need to be complicated. It needs to be clear, shared, and easy to run when the morning gets busy.</p>
+
+<figure class="wp-block-image size-large"><img src="https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg" alt="Planning materials on a desk with a calendar and smartphone for Sunday service coordination" class="wp-image-76" /><figcaption>A simple planning rhythm helps each Sunday start with fewer last-minute surprises.</figcaption></figure>
+
+<p>At <a href="https://ridgecrestchurch.com/about-us/">Ridgecrest Baptist Church</a>, Sunday ministry touches more than the order of service. It includes worship preparation, guest welcome, prayer, children and student handoffs, building readiness, and timely communication. When those parts are aligned, people can focus on worship and connection instead of chasing missing details.</p>
+
+<h2>Why a simple checklist matters</h2>
+
+<p>A checklist creates a baseline. It protects the team from relying on memory, and it lowers the odds that one missed handoff will affect the whole morning. The goal is not to make ministry mechanical. The goal is to remove avoidable friction so volunteers and staff can serve people well.</p>
+
+<p><strong>A good Sunday checklist does four jobs:</strong></p>
+
+<ul>
+<li>It gives each team a clear role before people arrive.</li>
+<li>It reduces last-minute surprises around sound, slides, seating, and room setup.</li>
+<li>It protects kids and student ministry transitions with documented handoff steps.</li>
+<li>It creates a consistent follow-up path for guests, prayer needs, and event reminders.</li>
+</ul>
+
+<p>If your church already publishes updates through the <a href="https://ridgecrestchurch.com/news/">News</a> page and upcoming schedules through the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>, your checklist should point teams back to those same sources. One source of truth beats four versions of the plan every time.</p>
+
+<h2>The Sunday timeline</h2>
+
+<p>Most service-day problems start before Sunday. The easiest fix is to divide preparation into three windows: the week before, the day before, and the final 30 minutes.</p>
+
+<table>
+<thead>
+<tr>
+<th>When</th>
+<th>What to confirm</th>
+<th>Primary owner</th>
+<th>Why it matters</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>Week before</td>
+<td>Order of service, volunteer schedule, kids/youth staffing, announcements, and event updates</td>
+<td>Staff lead or Sunday coordinator</td>
+<td>Prevents avoidable gaps before the weekend starts</td>
+</tr>
+<tr>
+<td>Day before</td>
+<td>Slides, song order, microphones, printed notes, room setup, and supply restock</td>
+<td>Worship, tech, facilities, and ministry leaders</td>
+<td>Catches errors while there is still time to correct them calmly</td>
+</tr>
+<tr>
+<td>30 minutes before service</td>
+<td>Doors unlocked, greeters in place, kids check-in ready, livestream/audio tested, and platform teams present</td>
+<td>On-site team leads</td>
+<td>Keeps the final handoff from turning into a scramble</td>
+</tr>
+</tbody>
+</table>
+
+<h3>What to prepare the week before</h3>
+
+<ul>
+<li>Finalize the order of service and distribute it to worship, tech, and platform leaders.</li>
+<li>Confirm which announcements need to be said live and which belong on the <a href="https://ridgecrestchurch.com/news/">News</a> page or <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>.</li>
+<li>Review volunteer assignments for greeters, ushers, kids check-in, nursery, student leaders, and security-minded building coverage.</li>
+<li>Make sure contact details for key leaders are current on the <a href="https://ridgecrestchurch.com/contacts/">Contacts</a> page so volunteers know where to direct questions.</li>
+</ul>
+
+<h3>What to prepare the day before</h3>
+
+<ul>
+<li>Load final slides, lyrics, Scripture references, and announcement screens.</li>
+<li>Test microphones, playback sources, batteries, and any livestream or recording workflow.</li>
+<li>Walk through classrooms, restrooms, entryways, and seating areas for cleanliness, signage, and accessibility.</li>
+<li>Check that kids ministry labels, sign-in materials, and emergency contacts are available where needed.</li>
+</ul>
+
+<h3>What to confirm 30 minutes before service</h3>
+
+<ul>
+<li>Greeters are at doors and know how to guide visitors.</li>
+<li>The worship team and tech team have completed sound check and cue review.</li>
+<li>Kids ministry volunteers are ready to receive families on time.</li>
+<li>Youth leaders know whether students begin in the main service, move later, or stay together for the full morning.</li>
+<li>Someone is assigned to receive guest questions and route them to the right ministry leader.</li>
+</ul>
+
+<h2>Worship and music: keep the platform steady</h2>
+
+<p>The worship portion of the morning needs an agreed sequence, not assumptions. Use one shared service order and make sure everyone on platform has the same version.</p>
+
+<ul>
+<li>Confirm the opening song, transitions, prayer moments, offering, message, and closing response.</li>
+<li>Verify lyric slides, lower thirds, and any Scripture references before rehearsal ends.</li>
+<li>Check microphones individually, not in theory. A muted channel is still a failure mode even if everything looked fine on Saturday.</li>
+<li>Assign one person to call audible changes only if needed. Too many live decision-makers create noise.</li>
+</ul>
+
+<p>If your team uses printed bulletins, make sure they match the final service plan. If you use screens only, confirm the projection operator has the right sequence and a backup copy of key items.</p>
+
+<h2>Welcome and connection: make guest follow-up clear</h2>
+
+<p>Hospitality is not filler around the service. It is part of the ministry of the morning. Greeters should know where to stand, what information they can answer, and when to hand a question to someone else.</p>
+
+<p><strong>Minimum safe setup for guest welcome:</strong></p>
+
+<ul>
+<li>Greeters at visible entrances 15 to 20 minutes before the service starts.</li>
+<li>A simple plan for directing families to <a href="https://ridgecrestchurch.com/kids/">Kids</a> or students to <a href="https://ridgecrestchurch.com/youth/">Youth</a>.</li>
+<li>A connection method that asks only for the information you actually need for follow-up.</li>
+<li>A same-day owner for guest cards, digital forms, or text-based responses.</li>
+</ul>
+
+<p>When you collect contact information, keep it responsible and plain: request only essential details, explain how the information will be used, and limit access to the people who need it for ministry follow-up. A church does not need operational fog around guest data.</p>
+
+<h2>Announcements and prayer: brief, accurate, and timely</h2>
+
+<p>Announcements should help people act. They should not become a second sermon or a rolling list of half-confirmed details. Choose the two or three items that matter most this week, state them clearly, and point people to the right page for details.</p>
+
+<ul>
+<li>Use the live service for timely, high-priority items.</li>
+<li>Use the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for dates, times, and logistics.</li>
+<li>Use the <a href="https://ridgecrestchurch.com/news/">News</a> page for fuller updates, ministry notes, or reminders people may revisit later.</li>
+<li>Keep prayer transitions intentional by deciding in advance who will lead and what the time boundary is.</li>
+</ul>
+
+<p>A short prayer can still be thoughtful. A short announcement can still be useful. Precision serves the room.</p>
+
+<h2>Kids ministry flow: protect check-in and handoff timing</h2>
+
+<p>Children's ministry is one of the clearest places where a written checklist pays off. Families feel it immediately when check-in is organized and volunteers are prepared.</p>
+
+<ul>
+<li>Open check-in early enough to prevent a line from forming at service start.</li>
+<li>Verify classroom coverage, allergy notes, bathroom procedures, and pickup expectations before families arrive.</li>
+<li>Keep parent pickup instructions simple and consistent each week.</li>
+<li>Make sure the route from the main entrance to the <a href="https://ridgecrestchurch.com/kids/">Kids</a> area is obvious for first-time visitors.</li>
+</ul>
+
+<p>If kids begin in the sanctuary and transition later, mark the timing in the service order so volunteers are in place before the handoff begins. A late handoff creates confusion for parents, teachers, and the platform team at the same time.</p>
+
+<h2>Youth ministry flow: decide the student plan in advance</h2>
+
+<p>Not every church handles student ministry the same way on Sunday morning. Some students stay in the full service. Some move after worship. Some alternate by week. The important point is not the format. It is the clarity.</p>
+
+<ul>
+<li>Confirm whether students attend the full service or transition at a set point.</li>
+<li>Make sure leaders know where students should gather, who is responsible for them, and what pickup or dismissal looks like.</li>
+<li>Share schedule changes through the <a href="https://ridgecrestchurch.com/youth/">Youth</a> page, <a href="https://ridgecrestchurch.com/news/">News</a>, or direct volunteer communication before Sunday morning.</li>
+</ul>
+
+<p>A good student plan removes guesswork for parents and leaders alike.</p>
+
+<h2>Tech and facilities: prepare the room people will actually experience</h2>
+
+<p>People notice the room before they notice your process. Tech and facility checks should cover what a first-time guest and a regular volunteer will both encounter.</p>
+
+<ul>
+<li>Slides, presentation computer, confidence monitor, and backup files</li>
+<li>Microphones, batteries, audio routing, and livestream or recording checks</li>
+<li>Restrooms stocked and clearly marked</li>
+<li>Seating ready for expected attendance and accessible entry routes open</li>
+<li>Heating, cooling, lighting, and any rooms needed after the service</li>
+</ul>
+
+<p>Walk the building with fresh eyes. If a hallway is unclear, a restroom is out of supplies, or a sign is missing, Sunday morning will magnify it.</p>
+
+<h2>Communication: decide who sends what to whom</h2>
+
+<p>Most Sunday chaos is not a values problem. It is a communication problem. The easiest way to fix that is to assign owners for each update.</p>
+
+<p><strong>Keep the communication chain simple:</strong></p>
+
+<ul>
+<li>The service coordinator sends the final order to worship, tech, and platform leaders.</li>
+<li>Kids and youth leaders confirm volunteer coverage and any room or schedule changes with their teams.</li>
+<li>The person handling public updates posts changes in the right place, usually the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for schedules and the <a href="https://ridgecrestchurch.com/news/">News</a> page for broader updates.</li>
+<li>Guest follow-up and ministry questions are routed to the right staff contact through the <a href="https://ridgecrestchurch.com/contacts/">Contacts</a> page.</li>
+</ul>
+
+<p>If a change matters enough to mention from the platform, it matters enough to send to the people serving that morning.</p>
+
+<h2>A simple Sunday service checklist to reuse each week</h2>
+
+<ol>
+<li>Finalize the order of service and confirm who owns each segment.</li>
+<li>Review volunteer coverage for hospitality, kids, youth, worship, tech, and facilities.</li>
+<li>Update slides, lyrics, announcement notes, and backup files.</li>
+<li>Prepare guest follow-up materials and identify who collects them.</li>
+<li>Open kids check-in and confirm safety basics before families arrive.</li>
+<li>Confirm the youth ministry plan and any service-time transitions.</li>
+<li>Test microphones, audio, presentation screens, and livestream workflow.</li>
+<li>Walk the building for restrooms, signage, seating, and accessibility.</li>
+<li>Post final public-facing updates in the right channel: calendar, news, or direct contact.</li>
+<li>Hold a short final check-in with the leaders on site before service begins.</li>
+</ol>
+
+<p>A stable Sunday does not require a complicated system. It requires one documented plan, clear ownership, and the discipline to review the same handoffs every week. If your current process feels reactive, start with the list above, trim it to what your church actually needs, and keep it where every team can reach it. Order is expensive in small ways. Chaos is expensive all at once.</p>
+
+<p>If you need to confirm service details, event timing, or the right ministry contact before the week begins, use the church’s <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>, <a href="https://ridgecrestchurch.com/news/">News</a>, and <a href="https://ridgecrestchurch.com/contacts/">Contacts</a> pages as your baseline.</p>

The author account, image asset, article HTML, published post, and verification checks are complete.
  ✓ Import or select a credible article image and create/reuse the Grant Vale author account
  ✓ Draft the article HTML with required structure and internal links
  ✓ Create and verify the published WordPress post and blog index settings
diff --git a//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-36/how-to-plan-a-great-sunday-checklist.html b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-36/how-to-plan-a-great-sunday-checklist.html
new file mode 100644
index 0000000000000000000000000000000000000000..ddcb6ed3321dea7fe2be10451aef92ad57550d76
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-36/how-to-plan-a-great-sunday-checklist.html
@@ -0,0 +1,199 @@
+<p><strong><em>A calm Sunday service is rarely accidental. It usually comes from a short, repeatable checklist that keeps worship, hospitality, kids ministry, youth transitions, and follow-up from drifting into preventable confusion.</em></strong></p>
+
+<p>If your team has ever asked, "Who is opening the building?" "Did the slides get updated?" "Who is covering kids check-in?" or "How will we follow up with first-time guests?" this article is for you. A healthy Sunday plan does not need to be complicated. It needs to be clear, shared, and easy to run when the morning gets busy.</p>
+
+<figure class="wp-block-image size-large"><img src="https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg" alt="Planning materials on a desk with a calendar and smartphone for Sunday service coordination" class="wp-image-76" /><figcaption>A simple planning rhythm helps each Sunday start with fewer last-minute surprises.</figcaption></figure>
+
+<p>At <a href="https://ridgecrestchurch.com/about-us/">Ridgecrest Baptist Church</a>, Sunday ministry touches more than the order of service. It includes worship preparation, guest welcome, prayer, children and student handoffs, building readiness, and timely communication. When those parts are aligned, people can focus on worship and connection instead of chasing missing details.</p>
+
+<h2>Why a simple checklist matters</h2>
+
+<p>A checklist creates a baseline. It protects the team from relying on memory, and it lowers the odds that one missed handoff will affect the whole morning. The goal is not to make ministry mechanical. The goal is to remove avoidable friction so volunteers and staff can serve people well.</p>
+
+<p><strong>A good Sunday checklist does four jobs:</strong></p>
+
+<ul>
+<li>It gives each team a clear role before people arrive.</li>
+<li>It reduces last-minute surprises around sound, slides, seating, and room setup.</li>
+<li>It protects kids and student ministry transitions with documented handoff steps.</li>
+<li>It creates a consistent follow-up path for guests, prayer needs, and event reminders.</li>
+</ul>
+
+<p>If your church already publishes updates through the <a href="https://ridgecrestchurch.com/news/">News</a> page and upcoming schedules through the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>, your checklist should point teams back to those same sources. One source of truth beats four versions of the plan every time.</p>
+
+<h2>The Sunday timeline</h2>
+
+<p>Most service-day problems start before Sunday. The easiest fix is to divide preparation into three windows: the week before, the day before, and the final 30 minutes.</p>
+
+<table>
+<thead>
+<tr>
+<th>When</th>
+<th>What to confirm</th>
+<th>Primary owner</th>
+<th>Why it matters</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>Week before</td>
+<td>Order of service, volunteer schedule, kids/youth staffing, announcements, and event updates</td>
+<td>Staff lead or Sunday coordinator</td>
+<td>Prevents avoidable gaps before the weekend starts</td>
+</tr>
+<tr>
+<td>Day before</td>
+<td>Slides, song order, microphones, printed notes, room setup, and supply restock</td>
+<td>Worship, tech, facilities, and ministry leaders</td>
+<td>Catches errors while there is still time to correct them calmly</td>
+</tr>
+<tr>
+<td>30 minutes before service</td>
+<td>Doors unlocked, greeters in place, kids check-in ready, livestream/audio tested, and platform teams present</td>
+<td>On-site team leads</td>
+<td>Keeps the final handoff from turning into a scramble</td>
+</tr>
+</tbody>
+</table>
+
+<h3>What to prepare the week before</h3>
+
+<ul>
+<li>Finalize the order of service and distribute it to worship, tech, and platform leaders.</li>
+<li>Confirm which announcements need to be said live and which belong on the <a href="https://ridgecrestchurch.com/news/">News</a> page or <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>.</li>
+<li>Review volunteer assignments for greeters, ushers, kids check-in, nursery, student leaders, and security-minded building coverage.</li>
+<li>Make sure contact details for key leaders are current on the <a href="https://ridgecrestchurch.com/contacts/">Contacts</a> page so volunteers know where to direct questions.</li>
+</ul>
+
+<h3>What to prepare the day before</h3>
+
+<ul>
+<li>Load final slides, lyrics, Scripture references, and announcement screens.</li>
+<li>Test microphones, playback sources, batteries, and any livestream or recording workflow.</li>
+<li>Walk through classrooms, restrooms, entryways, and seating areas for cleanliness, signage, and accessibility.</li>
+<li>Check that kids ministry labels, sign-in materials, and emergency contacts are available where needed.</li>
+</ul>
+
+<h3>What to confirm 30 minutes before service</h3>
+
+<ul>
+<li>Greeters are at doors and know how to guide visitors.</li>
+<li>The worship team and tech team have completed sound check and cue review.</li>
+<li>Kids ministry volunteers are ready to receive families on time.</li>
+<li>Youth leaders know whether students begin in the main service, move later, or stay together for the full morning.</li>
+<li>Someone is assigned to receive guest questions and route them to the right ministry leader.</li>
+</ul>
+
+<h2>Worship and music: keep the platform steady</h2>
+
+<p>The worship portion of the morning needs an agreed sequence, not assumptions. Use one shared service order and make sure everyone on platform has the same version.</p>
+
+<ul>
+<li>Confirm the opening song, transitions, prayer moments, offering, message, and closing response.</li>
+<li>Verify lyric slides, lower thirds, and any Scripture references before rehearsal ends.</li>
+<li>Check microphones individually, not in theory. A muted channel is still a failure mode even if everything looked fine on Saturday.</li>
+<li>Assign one person to call audible changes only if needed. Too many live decision-makers create noise.</li>
+</ul>
+
+<p>If your team uses printed bulletins, make sure they match the final service plan. If you use screens only, confirm the projection operator has the right sequence and a backup copy of key items.</p>
+
+<h2>Welcome and connection: make guest follow-up clear</h2>
+
+<p>Hospitality is not filler around the service. It is part of the ministry of the morning. Greeters should know where to stand, what information they can answer, and when to hand a question to someone else.</p>
+
+<p><strong>Minimum safe setup for guest welcome:</strong></p>
+
+<ul>
+<li>Greeters at visible entrances 15 to 20 minutes before the service starts.</li>
+<li>A simple plan for directing families to <a href="https://ridgecrestchurch.com/kids/">Kids</a> or students to <a href="https://ridgecrestchurch.com/youth/">Youth</a>.</li>
+<li>A connection method that asks only for the information you actually need for follow-up.</li>
+<li>A same-day owner for guest cards, digital forms, or text-based responses.</li>
+</ul>
+
+<p>When you collect contact information, keep it responsible and plain: request only essential details, explain how the information will be used, and limit access to the people who need it for ministry follow-up. A church does not need operational fog around guest data.</p>
+
+<h2>Announcements and prayer: brief, accurate, and timely</h2>
+
+<p>Announcements should help people act. They should not become a second sermon or a rolling list of half-confirmed details. Choose the two or three items that matter most this week, state them clearly, and point people to the right page for details.</p>
+
+<ul>
+<li>Use the live service for timely, high-priority items.</li>
+<li>Use the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for dates, times, and logistics.</li>
+<li>Use the <a href="https://ridgecrestchurch.com/news/">News</a> page for fuller updates, ministry notes, or reminders people may revisit later.</li>
+<li>Keep prayer transitions intentional by deciding in advance who will lead and what the time boundary is.</li>
+</ul>
+
+<p>A short prayer can still be thoughtful. A short announcement can still be useful. Precision serves the room.</p>
+
+<h2>Kids ministry flow: protect check-in and handoff timing</h2>
+
+<p>Children's ministry is one of the clearest places where a written checklist pays off. Families feel it immediately when check-in is organized and volunteers are prepared.</p>
+
+<ul>
+<li>Open check-in early enough to prevent a line from forming at service start.</li>
+<li>Verify classroom coverage, allergy notes, bathroom procedures, and pickup expectations before families arrive.</li>
+<li>Keep parent pickup instructions simple and consistent each week.</li>
+<li>Make sure the route from the main entrance to the <a href="https://ridgecrestchurch.com/kids/">Kids</a> area is obvious for first-time visitors.</li>
+</ul>
+
+<p>If kids begin in the sanctuary and transition later, mark the timing in the service order so volunteers are in place before the handoff begins. A late handoff creates confusion for parents, teachers, and the platform team at the same time.</p>
+
+<h2>Youth ministry flow: decide the student plan in advance</h2>
+
+<p>Not every church handles student ministry the same way on Sunday morning. Some students stay in the full service. Some move after worship. Some alternate by week. The important point is not the format. It is the clarity.</p>
+
+<ul>
+<li>Confirm whether students attend the full service or transition at a set point.</li>
+<li>Make sure leaders know where students should gather, who is responsible for them, and what pickup or dismissal looks like.</li>
+<li>Share schedule changes through the <a href="https://ridgecrestchurch.com/youth/">Youth</a> page, <a href="https://ridgecrestchurch.com/news/">News</a>, or direct volunteer communication before Sunday morning.</li>
+</ul>
+
+<p>A good student plan removes guesswork for parents and leaders alike.</p>
+
+<h2>Tech and facilities: prepare the room people will actually experience</h2>
+
+<p>People notice the room before they notice your process. Tech and facility checks should cover what a first-time guest and a regular volunteer will both encounter.</p>
+
+<ul>
+<li>Slides, presentation computer, confidence monitor, and backup files</li>
+<li>Microphones, batteries, audio routing, and livestream or recording checks</li>
+<li>Restrooms stocked and clearly marked</li>
+<li>Seating ready for expected attendance and accessible entry routes open</li>
+<li>Heating, cooling, lighting, and any rooms needed after the service</li>
+</ul>
+
+<p>Walk the building with fresh eyes. If a hallway is unclear, a restroom is out of supplies, or a sign is missing, Sunday morning will magnify it.</p>
+
+<h2>Communication: decide who sends what to whom</h2>
+
+<p>Most Sunday chaos is not a values problem. It is a communication problem. The easiest way to fix that is to assign owners for each update.</p>
+
+<p><strong>Keep the communication chain simple:</strong></p>
+
+<ul>
+<li>The service coordinator sends the final order to worship, tech, and platform leaders.</li>
+<li>Kids and youth leaders confirm volunteer coverage and any room or schedule changes with their teams.</li>
+<li>The person handling public updates posts changes in the right place, usually the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for schedules and the <a href="https://ridgecrestchurch.com/news/">News</a> page for broader updates.</li>
+<li>Guest follow-up and ministry questions are routed to the right staff contact through the <a href="https://ridgecrestchurch.com/contacts/">Contacts</a> page.</li>
+</ul>
+
+<p>If a change matters enough to mention from the platform, it matters enough to send to the people serving that morning.</p>
+
+<h2>A simple Sunday service checklist to reuse each week</h2>
+
+<ol>
+<li>Finalize the order of service and confirm who owns each segment.</li>
+<li>Review volunteer coverage for hospitality, kids, youth, worship, tech, and facilities.</li>
+<li>Update slides, lyrics, announcement notes, and backup files.</li>
+<li>Prepare guest follow-up materials and identify who collects them.</li>
+<li>Open kids check-in and confirm safety basics before families arrive.</li>
+<li>Confirm the youth ministry plan and any service-time transitions.</li>
+<li>Test microphones, audio, presentation screens, and livestream workflow.</li>
+<li>Walk the building for restrooms, signage, seating, and accessibility.</li>
+<li>Post final public-facing updates in the right channel: calendar, news, or direct contact.</li>
+<li>Hold a short final check-in with the leaders on site before service begins.</li>
+</ol>
+
+<p>A stable Sunday does not require a complicated system. It requires one documented plan, clear ownership, and the discipline to review the same handoffs every week. If your current process feels reactive, start with the list above, trim it to what your church actually needs, and keep it where every team can reach it. Order is expensive in small ways. Chaos is expensive all at once.</p>
+
+<p>If you need to confirm service details, event timing, or the right ministry contact before the week begins, use the church’s <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>, <a href="https://ridgecrestchurch.com/news/">News</a>, and <a href="https://ridgecrestchurch.com/contacts/">Contacts</a> pages as your baseline.</p>

codex
Published the new post “How to Plan a Great Sunday: A Simple Church Service Checklist” and assigned it to the new author account `Grant Vale`. The article includes the required inline image, a reusable Sunday timeline table, practical ministry checklists, and natural internal links to `About Us`, `Kids`, `Youth`, `Events Calendar`, `News`, and `Contacts`.

Verified `wp post get`, `wp post url`, public `200` responses for the post and `/blog/`, blog index visibility, featured image assignment, and inline image presence in `post_content`. Remaining limitation: this WordPress install has no GD/Imagick, so the image had to be registered manually as an attachment without generated intermediate sizes; it renders publicly, but only the original JPEG is available. The imported image is a credible planning-desk photo rather than a church-specific bulletin clipboard scene. Backlink target `/` was unchanged in this run. No Flatlogic link targets were available or used.

LEGACY_PATH_STATUS: not_applicable
LINK_TARGETS_USED: none
VERIFICATION: `wp post get` and `wp post url` succeeded; public post URL and `/blog/` returned HTTP 200; `/blog/` surfaces the post; inline image attachment `76` and featured image `76` confirmed.

WP_POST_ID: 77
WP_POST_STATUS: publish
WP_POST_URL: https://ridgecrestchurch.com/how-to-plan-a-great-sunday-checklist/
WP_AUTHOR_USER: grant-vale/Grant Vale
FEATURED_IMAGE_ID: 76
INLINE_IMAGE_IDS: 76
BLOG_INDEX_STATUS: ready; https://ridgecrestchurch.com/blog/ with page_for_posts=23
diff --git a//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-36/how-to-plan-a-great-sunday-checklist.html b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-36/how-to-plan-a-great-sunday-checklist.html
new file mode 100644
index 0000000000000000000000000000000000000000..ddcb6ed3321dea7fe2be10451aef92ad57550d76
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-36/how-to-plan-a-great-sunday-checklist.html
@@ -0,0 +1,199 @@
+<p><strong><em>A calm Sunday service is rarely accidental. It usually comes from a short, repeatable checklist that keeps worship, hospitality, kids ministry, youth transitions, and follow-up from drifting into preventable confusion.</em></strong></p>
+
+<p>If your team has ever asked, "Who is opening the building?" "Did the slides get updated?" "Who is covering kids check-in?" or "How will we follow up with first-time guests?" this article is for you. A healthy Sunday plan does not need to be complicated. It needs to be clear, shared, and easy to run when the morning gets busy.</p>
+
+<figure class="wp-block-image size-large"><img src="https://ridgecrestchurch.com/wp-content/uploads/imports/sunday-service-planning-desk.jpg" alt="Planning materials on a desk with a calendar and smartphone for Sunday service coordination" class="wp-image-76" /><figcaption>A simple planning rhythm helps each Sunday start with fewer last-minute surprises.</figcaption></figure>
+
+<p>At <a href="https://ridgecrestchurch.com/about-us/">Ridgecrest Baptist Church</a>, Sunday ministry touches more than the order of service. It includes worship preparation, guest welcome, prayer, children and student handoffs, building readiness, and timely communication. When those parts are aligned, people can focus on worship and connection instead of chasing missing details.</p>
+
+<h2>Why a simple checklist matters</h2>
+
+<p>A checklist creates a baseline. It protects the team from relying on memory, and it lowers the odds that one missed handoff will affect the whole morning. The goal is not to make ministry mechanical. The goal is to remove avoidable friction so volunteers and staff can serve people well.</p>
+
+<p><strong>A good Sunday checklist does four jobs:</strong></p>
+
+<ul>
+<li>It gives each team a clear role before people arrive.</li>
+<li>It reduces last-minute surprises around sound, slides, seating, and room setup.</li>
+<li>It protects kids and student ministry transitions with documented handoff steps.</li>
+<li>It creates a consistent follow-up path for guests, prayer needs, and event reminders.</li>
+</ul>
+
+<p>If your church already publishes updates through the <a href="https://ridgecrestchurch.com/news/">News</a> page and upcoming schedules through the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>, your checklist should point teams back to those same sources. One source of truth beats four versions of the plan every time.</p>
+
+<h2>The Sunday timeline</h2>
+
+<p>Most service-day problems start before Sunday. The easiest fix is to divide preparation into three windows: the week before, the day before, and the final 30 minutes.</p>
+
+<table>
+<thead>
+<tr>
+<th>When</th>
+<th>What to confirm</th>
+<th>Primary owner</th>
+<th>Why it matters</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>Week before</td>
+<td>Order of service, volunteer schedule, kids/youth staffing, announcements, and event updates</td>
+<td>Staff lead or Sunday coordinator</td>
+<td>Prevents avoidable gaps before the weekend starts</td>
+</tr>
+<tr>
+<td>Day before</td>
+<td>Slides, song order, microphones, printed notes, room setup, and supply restock</td>
+<td>Worship, tech, facilities, and ministry leaders</td>
+<td>Catches errors while there is still time to correct them calmly</td>
+</tr>
+<tr>
+<td>30 minutes before service</td>
+<td>Doors unlocked, greeters in place, kids check-in ready, livestream/audio tested, and platform teams present</td>
+<td>On-site team leads</td>
+<td>Keeps the final handoff from turning into a scramble</td>
+</tr>
+</tbody>
+</table>
+
+<h3>What to prepare the week before</h3>
+
+<ul>
+<li>Finalize the order of service and distribute it to worship, tech, and platform leaders.</li>
+<li>Confirm which announcements need to be said live and which belong on the <a href="https://ridgecrestchurch.com/news/">News</a> page or <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>.</li>
+<li>Review volunteer assignments for greeters, ushers, kids check-in, nursery, student leaders, and security-minded building coverage.</li>
+<li>Make sure contact details for key leaders are current on the <a href="https://ridgecrestchurch.com/contacts/">Contacts</a> page so volunteers know where to direct questions.</li>
+</ul>
+
+<h3>What to prepare the day before</h3>
+
+<ul>
+<li>Load final slides, lyrics, Scripture references, and announcement screens.</li>
+<li>Test microphones, playback sources, batteries, and any livestream or recording workflow.</li>
+<li>Walk through classrooms, restrooms, entryways, and seating areas for cleanliness, signage, and accessibility.</li>
+<li>Check that kids ministry labels, sign-in materials, and emergency contacts are available where needed.</li>
+</ul>
+
+<h3>What to confirm 30 minutes before service</h3>
+
+<ul>
+<li>Greeters are at doors and know how to guide visitors.</li>
+<li>The worship team and tech team have completed sound check and cue review.</li>
+<li>Kids ministry volunteers are ready to receive families on time.</li>
+<li>Youth leaders know whether students begin in the main service, move later, or stay together for the full morning.</li>
+<li>Someone is assigned to receive guest questions and route them to the right ministry leader.</li>
+</ul>
+
+<h2>Worship and music: keep the platform steady</h2>
+
+<p>The worship portion of the morning needs an agreed sequence, not assumptions. Use one shared service order and make sure everyone on platform has the same version.</p>
+
+<ul>
+<li>Confirm the opening song, transitions, prayer moments, offering, message, and closing response.</li>
+<li>Verify lyric slides, lower thirds, and any Scripture references before rehearsal ends.</li>
+<li>Check microphones individually, not in theory. A muted channel is still a failure mode even if everything looked fine on Saturday.</li>
+<li>Assign one person to call audible changes only if needed. Too many live decision-makers create noise.</li>
+</ul>
+
+<p>If your team uses printed bulletins, make sure they match the final service plan. If you use screens only, confirm the projection operator has the right sequence and a backup copy of key items.</p>
+
+<h2>Welcome and connection: make guest follow-up clear</h2>
+
+<p>Hospitality is not filler around the service. It is part of the ministry of the morning. Greeters should know where to stand, what information they can answer, and when to hand a question to someone else.</p>
+
+<p><strong>Minimum safe setup for guest welcome:</strong></p>
+
+<ul>
+<li>Greeters at visible entrances 15 to 20 minutes before the service starts.</li>
+<li>A simple plan for directing families to <a href="https://ridgecrestchurch.com/kids/">Kids</a> or students to <a href="https://ridgecrestchurch.com/youth/">Youth</a>.</li>
+<li>A connection method that asks only for the information you actually need for follow-up.</li>
+<li>A same-day owner for guest cards, digital forms, or text-based responses.</li>
+</ul>
+
+<p>When you collect contact information, keep it responsible and plain: request only essential details, explain how the information will be used, and limit access to the people who need it for ministry follow-up. A church does not need operational fog around guest data.</p>
+
+<h2>Announcements and prayer: brief, accurate, and timely</h2>
+
+<p>Announcements should help people act. They should not become a second sermon or a rolling list of half-confirmed details. Choose the two or three items that matter most this week, state them clearly, and point people to the right page for details.</p>
+
+<ul>
+<li>Use the live service for timely, high-priority items.</li>
+<li>Use the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for dates, times, and logistics.</li>
+<li>Use the <a href="https://ridgecrestchurch.com/news/">News</a> page for fuller updates, ministry notes, or reminders people may revisit later.</li>
+<li>Keep prayer transitions intentional by deciding in advance who will lead and what the time boundary is.</li>
+</ul>
+
+<p>A short prayer can still be thoughtful. A short announcement can still be useful. Precision serves the room.</p>
+
+<h2>Kids ministry flow: protect check-in and handoff timing</h2>
+
+<p>Children's ministry is one of the clearest places where a written checklist pays off. Families feel it immediately when check-in is organized and volunteers are prepared.</p>
+
+<ul>
+<li>Open check-in early enough to prevent a line from forming at service start.</li>
+<li>Verify classroom coverage, allergy notes, bathroom procedures, and pickup expectations before families arrive.</li>
+<li>Keep parent pickup instructions simple and consistent each week.</li>
+<li>Make sure the route from the main entrance to the <a href="https://ridgecrestchurch.com/kids/">Kids</a> area is obvious for first-time visitors.</li>
+</ul>
+
+<p>If kids begin in the sanctuary and transition later, mark the timing in the service order so volunteers are in place before the handoff begins. A late handoff creates confusion for parents, teachers, and the platform team at the same time.</p>
+
+<h2>Youth ministry flow: decide the student plan in advance</h2>
+
+<p>Not every church handles student ministry the same way on Sunday morning. Some students stay in the full service. Some move after worship. Some alternate by week. The important point is not the format. It is the clarity.</p>
+
+<ul>
+<li>Confirm whether students attend the full service or transition at a set point.</li>
+<li>Make sure leaders know where students should gather, who is responsible for them, and what pickup or dismissal looks like.</li>
+<li>Share schedule changes through the <a href="https://ridgecrestchurch.com/youth/">Youth</a> page, <a href="https://ridgecrestchurch.com/news/">News</a>, or direct volunteer communication before Sunday morning.</li>
+</ul>
+
+<p>A good student plan removes guesswork for parents and leaders alike.</p>
+
+<h2>Tech and facilities: prepare the room people will actually experience</h2>
+
+<p>People notice the room before they notice your process. Tech and facility checks should cover what a first-time guest and a regular volunteer will both encounter.</p>
+
+<ul>
+<li>Slides, presentation computer, confidence monitor, and backup files</li>
+<li>Microphones, batteries, audio routing, and livestream or recording checks</li>
+<li>Restrooms stocked and clearly marked</li>
+<li>Seating ready for expected attendance and accessible entry routes open</li>
+<li>Heating, cooling, lighting, and any rooms needed after the service</li>
+</ul>
+
+<p>Walk the building with fresh eyes. If a hallway is unclear, a restroom is out of supplies, or a sign is missing, Sunday morning will magnify it.</p>
+
+<h2>Communication: decide who sends what to whom</h2>
+
+<p>Most Sunday chaos is not a values problem. It is a communication problem. The easiest way to fix that is to assign owners for each update.</p>
+
+<p><strong>Keep the communication chain simple:</strong></p>
+
+<ul>
+<li>The service coordinator sends the final order to worship, tech, and platform leaders.</li>
+<li>Kids and youth leaders confirm volunteer coverage and any room or schedule changes with their teams.</li>
+<li>The person handling public updates posts changes in the right place, usually the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for schedules and the <a href="https://ridgecrestchurch.com/news/">News</a> page for broader updates.</li>
+<li>Guest follow-up and ministry questions are routed to the right staff contact through the <a href="https://ridgecrestchurch.com/contacts/">Contacts</a> page.</li>
+</ul>
+
+<p>If a change matters enough to mention from the platform, it matters enough to send to the people serving that morning.</p>
+
+<h2>A simple Sunday service checklist to reuse each week</h2>
+
+<ol>
+<li>Finalize the order of service and confirm who owns each segment.</li>
+<li>Review volunteer coverage for hospitality, kids, youth, worship, tech, and facilities.</li>
+<li>Update slides, lyrics, announcement notes, and backup files.</li>
+<li>Prepare guest follow-up materials and identify who collects them.</li>
+<li>Open kids check-in and confirm safety basics before families arrive.</li>
+<li>Confirm the youth ministry plan and any service-time transitions.</li>
+<li>Test microphones, audio, presentation screens, and livestream workflow.</li>
+<li>Walk the building for restrooms, signage, seating, and accessibility.</li>
+<li>Post final public-facing updates in the right channel: calendar, news, or direct contact.</li>
+<li>Hold a short final check-in with the leaders on site before service begins.</li>
+</ol>
+
+<p>A stable Sunday does not require a complicated system. It requires one documented plan, clear ownership, and the discipline to review the same handoffs every week. If your current process feels reactive, start with the list above, trim it to what your church actually needs, and keep it where every team can reach it. Order is expensive in small ways. Chaos is expensive all at once.</p>
+
+<p>If you need to confirm service details, event timing, or the right ministry contact before the week begins, use the church’s <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>, <a href="https://ridgecrestchurch.com/news/">News</a>, and <a href="https://ridgecrestchurch.com/contacts/">Contacts</a> pages as your baseline.</p>

tokens used
104,332
