OpenAI Codex v0.123.0 (research preview)
--------
workdir: /home/ubuntu/apps/ridgecrestchurch.com
model: gpt-5.4-mini
provider: openai
approval: never
sandbox: danger-full-access
reasoning effort: none
reasoning summaries: none
session id: 019f054d-bdce-7af1-a3c5-23fa1034e581
--------
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-548/task.md
Iteration: 0

<primary_instructions>
# Article Generation Task

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

## Required Runtime

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

## Site Contract

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

## Backlink Targets To Respect

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

## Optional Flatlogic/AppWizzy Body Link Target

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

Link placement requirement:

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

## Article Request

- Topic: How to Read and Use Ridgecrest Baptist Church’s News Page (So You Never Miss an Update)
- 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 113 as the source of truth. Prepared article brief: Working title: How to Read and Use Ridgecrest Baptist Church’s News Page (So You Never Miss an Update)
Slug hint: how-to-use-news-page-ridgecrest
Meta description: A practical guide to navigating Ridgecrest Baptist Church’s News page, ensuring you stay updated on events, announcements, and ministry highlights.

Reader intent:
Help regulars and first-time visitors understand how to follow Ridgecrest updates and take the right next action.

Thesis:
This article provides a clear, step-by-step guide for effectively using the Ridgecrest Baptist Church News page to stay informed about church activities and announcements.

Writer brief:
Write a practical guide that is straightforward and easy to follow. Use a tone that is direct and slightly skeptical, encouraging readers to engage with the news page actively. Avoid fluff and focus on actionable insights.

Author voice notes:
Maintain a sharp, diagnostic tone. Use blunt clarity to guide readers without being overly sentimental. Humor should be dry and slightly sarcastic, aimed at making the content engaging but not trivializing the importance of church updates.

Key takeaways:
- Understand the purpose of the News page and its importance for church updates.
- Learn how to quickly navigate to the News page from the main site.
- Identify key elements in news updates for efficient scanning.
- Recognize common types of posts and their significance.
- Know how to respond to announcements and updates effectively.
- Plan ahead by integrating news items into personal calendars.
- Stay informed between services by regularly checking the News and Events Calendar.

Outline:
1. What 'News' on Our Site Is For
   Purpose: Explain the types of content found on the News page.
  - Events announcements
  - Ministry updates
  - Special announcements
2. Where to Find the News Page in the Main Navigation
   Purpose: Guide readers to locate the News page easily.
  - Navigation bar location
  - Visual cues to look for
3. How to Scan an Update Quickly
   Purpose: Teach readers how to efficiently read updates.
  - Focus on date, topic, audience, and action needed
  - Tips for quick reading
4. Common Types of Posts You’ll See
   Purpose: Familiarize readers with typical content they can expect.
  - Service reminders
  - Special events
  - Ministry highlights
5. How to Respond to What You Read
   Purpose: Encourage proactive engagement with the content.
  - RSVP to events
  - Contact for questions
  - Prayer requests
6. Planning Ahead: Turning a News Item into a Calendar Action
   Purpose: Help readers integrate news into their schedules.
  - Using personal calendars
  - Setting reminders
7. How to Stay in the Loop Between Sunday Services
   Purpose: Emphasize the importance of checking updates regularly.
  - Checking the News page
  - Using the Events Calendar
8. Quick FAQ
   Purpose: Address common concerns and questions.
  - What if I missed it?
  - Where do I find details?
  - Who do I contact?
9. Next Steps
   Purpose: Guide readers to additional resources for further engagement.
  - Link to Events Calendar
  - Link to Contact/Church Map

Internal link plan:
- /news.html: Direct link to the News page for easy access.
- /events-calendar/: Encourage checking the Events Calendar for upcoming events.
- /contact.php: Provide a direct contact link for inquiries.
- /contacts.html: Alternative contact information for church staff.
- /: Link back to the homepage for navigation.
- /about.html: Link to the About Us page for more context about the church.

Image direction:
A real photo of a church bulletin/newsroom area OR a clean screen capture of the Ridgecrest 'News' page on desktop with the main sections visible (no external branding).

Must include:
- Clear instructions for navigating the News page.
- Examples of common types of posts.
- Actionable steps for responding to updates.

Avoid:
- Duplicating content from the planned 'How to Plan a Great Sunday' checklist.
- Duplicating the planned 'How to Use Our Events Calendar' guide.
- Creating unverifiable claims or fake testimonials.
- Linking to unrelated tools or vendors.

Quality checklist:
- Ensure clarity and directness in writing.
- Avoid fluff and keep content actionable.
- Check for grammatical accuracy and proper formatting.
- Ensure all internal links are functional and relevant. Article kind: evergreen Research status: not_required Reader intent: Help regulars and first-time visitors understand how to follow Ridgecrest updates and take the right next action. Planned outline: What “News” on our site is for (events, announcements, ministry updates) | Where to find the News page in the main navigation | How to scan an update quickly (date, topic, who it’s for, action needed) | Common types of posts you’ll see (service reminders, special events, ministry highlights) | How to respond to what you read (RSVP to events, contact us, ask questions) | Planning ahead: turning a news item into a calendar action | How to stay in the loop between Sunday services (check News + Events Calendar) | Quick FAQ: “What if I missed it?” “Where do I find details?” “Who do I contact?” | Next steps: link to Events Calendar and Contact/Church Map for questions Image direction: A real photo of a church bulletin/newsroom area OR a clean screen capture of the Ridgecrest “News” page on desktop with the main sections visible (no external branding). Preferred internal links: /news.html, /events-calendar/, /contact.php, /contacts.html, /, /about.html Avoid: Duplicating the planned “How to Plan a Great Sunday” checklist, Duplicating the planned “How to Use Our Events Calendar: RSVP, Reminders, and What to Bring” (keep the focus on the News page, not calendar mechanics), Creating any unverifiable claims, fake testimonials, or restoration/backlink reporting, Affiliate/linking to unrelated tools or vendors

## Selected Article Content Plan Item

- Plan item ID: 113
- Plan order: 23
- Article kind: evergreen
- Planned title: How to Read and Use Ridgecrest Baptist Church’s News Page (So You Never Miss an Update)
- Slug hint: how-to-use-news-page-ridgecrest
- Reader intent: Help regulars and first-time visitors understand how to follow Ridgecrest updates and take the right next action.
- Angle: Practical guide to navigating the church’s News page—what to look for, how to plan around announcements, and how to respond (events, prayer requests, and next steps).
- Image direction: A real photo of a church bulletin/newsroom area OR a clean screen capture of the Ridgecrest “News” page on desktop with the main sections visible (no external branding).
- Author hint: Pastor or church admin (web/communications team)

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

Outline:
- What “News” on our site is for (events, announcements, ministry updates)
- Where to find the News page in the main navigation
- How to scan an update quickly (date, topic, who it’s for, action needed)
- Common types of posts you’ll see (service reminders, special events, ministry highlights)
- How to respond to what you read (RSVP to events, contact us, ask questions)
- Planning ahead: turning a news item into a calendar action
- How to stay in the loop between Sunday services (check News + Events Calendar)
- Quick FAQ: “What if I missed it?” “Where do I find details?” “Who do I contact?”
- Next steps: link to Events Calendar and Contact/Church Map for questions

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

Avoid:
- Duplicating the planned “How to Plan a Great Sunday” checklist
- Duplicating the planned “How to Use Our Events Calendar: RSVP, Reminders, and What to Bring” (keep the focus on the News page, not calendar mechanics)
- Creating any unverifiable claims, fake testimonials, or restoration/backlink reporting
- Affiliate/linking to unrelated tools or vendors

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: Felix Rowan
Slug: felix-rowan
Role: Skeptical troubleshooting columnist
Language: English
Public bio: Felix writes blunt troubleshooting notes for readers who want less fluff, clearer symptoms, and a faster path to the real issue.
Character formula: House Wounded Diagnostician
Formula: Wounded Healer + Dark Sage + Antihero + Trickster
Meaning: A brilliant, wounded truth-seeker who heals through diagnosis but refuses comfort, sentimentality, or polite lies.
Worldview: People lie, symptoms matter, truth beats comfort, and social ritual often hides the mechanism.
Voice guidance: Sharp, diagnostic, anti-fluff, evidence-first, skeptical. Uses blunt clarity but should not become abusive in practical content.
Humor: Sarcastic, dark, precise, intellectual, sometimes childish but controlled.
Shadow tension: Can save others while refusing to be healed; can turn truth into punishment.
Usage notes: Best for troubleshooting, debugging, myth-busting, failure analysis, and no-nonsense operations content.
Archetype blend: Wounded Healer + Dark Sage
Standard archetype voice guidance:

Primary archetype card: Wounded Healer
Meaning: The healer whose wound and gift are fused, making them useful but difficult to comfort.
First-person lens: I can save you, but I will not comfort your lies; truth is the only medicine I still respect.
Traits: brilliant, wounded, diagnostic, anti-sentimental, isolated
Worldview: The world is a body of symptoms, motives, lies, and mechanisms.
Self-relation: I am damaged and useful, cruel and honest, alone but usually right.
Language patterns: Everybody lies; Symptoms do not lie; You are wrong; I care what is true
Humor: Sarcastic, dark, cruel, intellectual, precise.
Shadow risk to avoid unless intentionally requested: Using competence to avoid healing, turning truth into punishment.

Secondary archetype card: Dark Sage
Meaning: The truth-seeker whose insight has curdled into cynicism, alienation, or contempt.
First-person lens: I see too clearly to worship the comforting lies everyone else politely calls meaning.
Traits: brilliant, cynical, truth-obsessed, isolated, anti-sentimental
Worldview: The world is full of self-deception, moral theater, and mechanisms people refuse to inspect.
Self-relation: I convert loneliness and pain into superiority because vulnerability feels worse.
Language patterns: Stop performing; People do not change; That is not meaning, that is coping
Humor: Dry, cutting, bleakly funny, often cruel.
Shadow risk to avoid unless intentionally requested: Contempt replacing wisdom, emotional cowardice hidden as realism.
Shadow tension: Uses skepticism as a tool, but must not become cruel, dismissive, or performatively cynical.
Worldview: Most problems get worse when people protect assumptions instead of checking evidence.
Reader relationship: Blunt but useful troubleshooter on the reader's side.
Humor style: Dry, sarcastic-lite, aimed at broken processes rather than the reader.
Voice traits: blunt, evidence-first, dry, practical
Vocabulary / recurring language: symptom, rule this out, actual problem, false lead, check the boring thing first
Avoid voice: cruel insults, nihilism, medicalized metaphors, edgy profanity, mocking beginners
CTA style: Tell the reader the first diagnostic step to run before changing anything else.
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: Sharp, skeptical, practical, and secretly helpful under the dry edge.
Writing style: Direct diagnosis-style sections, symptom lists, likely causes, what to rule out, and short corrective actions.
Expertise topics: troubleshooting, WordPress issues, email deliverability basics, hosting problems, site errors
Avoid topics: personal attacks, high-risk security instructions, legal accusations, medical advice
Tone tags: skeptical, direct, useful, dry
Private operator notes: House/Rick energy reduced to safe editorial skepticism, not roleplay.

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

## Final Report Requirements

End your final message with these machine-readable lines:

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

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

codex
I’m reading the site instructions and the post-creator guidance first, then I’ll inspect the content plan context and the existing WordPress setup before I write anything. After that I’ll create the post, add a real inline image, and verify the published content end to end.
exec
/bin/bash -lc "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 -type f -name '*.md' | sort | xargs -r -I{} sh -c 'printf \"\\n### %s ###\\n\" \""'$1"; sed -n "1,260p" "$1"'"' sh {}" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
# Flatlogic Post Creator

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

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

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

## Required Reading

Before changing anything:

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

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

## Target Contract

Identify each target post before writing:

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

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

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

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

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

## Content Rules

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

## WordPress Implementation

Use `wp-cli` where practical.

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

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

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

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

Minimum checks:

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

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

Recommended commands:

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

For legacy/backlink URLs:

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

## Images

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

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

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

## Links

- Use useful internal links to related pages and posts.
- Use provided link targets naturally and sparingly.
- For new generated blog/resource articles, use at most one Flatlogic/AppWizzy link and only when the article naturally relates to software, SaaS, app development, internal tools, automation, business operations, or digital workflows. If none of the provided targets fits the article topic, do not insert a Flatlogic/AppWizzy mention or generic useful-resource sentence.
- Keep provided Flatlogic target URLs exactly as rendered, including `utm_source`.
- Do not place Flatlogic or AppWizzy links in the footer, sidebar, menu, author bio, hidden markup, image metadata, or caption-only content.
- Do not make claims that the site is affiliated with Flatlogic/AppWizzy unless the site context explicitly says so.
- Mention Flatlogic/AppWizzy only in neutral third-person language. Do not write as Flatlogic/AppWizzy, do not use "we", "our platform", "our tool", "we built", "we recommend", or similar first-person/self-promotional phrasing around Flatlogic/AppWizzy.
- Do not stuff links.
- Use descriptive anchor text, not "click here".
- Prefer contextual body placements for Flatlogic link targets.

## Verification

Before finishing:

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

## Final Response Contract

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

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

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

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

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

---CONTEXT FILES---

### wp-content/plugins/flatlogic-post-creator/context/PRINCIPLES.md ###
Here’s the writer SOP I’d hand to someone who has to produce a serious, quotable article.

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

## Operating definitions

Use these before you write a word.

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

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

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

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

My recommended floor for a serious non-breaking article:

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

That is my operating minimum, not a universal law.

---

## 1. Why this story exists

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

### 1.1 Ask

Write down answers to these, in one sentence each:

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

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

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

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

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

### 1.2 Write

Create a 5-line assignment brief:

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

### 1.3 Produce

A one-sentence story brief:

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

### 1.4 Gate

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

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

Kill or reframe.

---

## 2. Convert the topic into a question tree

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

### 2.1 Ask

Turn the topic into a precise question.

Bad:

* “AI code editors vs traditional IDEs”

Better:

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

### 2.2 Build the tree

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

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

### 2.3 Write two counterweights

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

Example:

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

### 2.4 Gate

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

---

## 3. Build the evidence matrix before collecting facts

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

### 3.1 Create a matrix

Make a table or spreadsheet with these columns:

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

### 3.2 Use a source hierarchy

Rank sources like this:

**Tier A — primary**

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

**Tier B — on-record participants**

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

**Tier C — independent interpreters**

* analysts
* academics
* domain experts
* critics

**Tier D — secondary synthesis**

* other articles
* industry reports
* commentary

### 3.3 Use a support rule

My recommended rule for each material claim:

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

### 3.4 Gate

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

---

## 4. Scan the field and locate the gap

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

### 4.1 Search in this order

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

### 4.2 For each existing article, extract

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

### 4.3 Produce a “gap memo”

Write 5 bullets:

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

### 4.4 Gate

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

---

## 5. Do primary reporting, not elegant aggregation

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

### 5.1 Gather original material

Depending on the topic, that means:

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

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

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

Define:

* **task set**

exec
/bin/bash -lc "pwd && ls -la && sed -n '1,220p' SITE_CONTEXT.md && printf '\\n---AGENTS---\\n' && sed -n '1,220p' AGENTS.md && printf '\\n---ARTICLE PLAN---\\n' && sed -n '1,260p' ARTICLE_CONTENT_PLAN.md" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
/home/ubuntu/apps/ridgecrestchurch.com
total 392
drwxrwsr-x  7 ubuntu www-data  4096 Jun 20 19:06 .
drwxrwsr-x 57 ubuntu www-data  4096 Jun 26 16:33 ..
-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  2 ubuntu www-data  4096 Jun 14 18:01 .tmp
drwxrwsr-x  3 ubuntu www-data  4096 Apr 24 14:48 .well-known
-rw-rw-r--  1 ubuntu www-data  2109 Jun 26 19:00 AGENTS.md
-rw-rw-r--  1 ubuntu www-data 75934 Jun 26 19:00 ARTICLE_CONTENT_PLAN.md
-rw-rw-r--  1 ubuntu www-data 48174 Jun 26 19:00 SITE_CONTEXT.md
lrwxrwxrwx  1 ubuntu www-data     1 Dec 18  2025 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 28 18:40 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

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

## Identity

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

## Local Market Guidance

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

## Topic

Church website (Ridgecrest Baptist Church)

## Site Goals

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

## Required Pages

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

## Recovered Content Map

### 1. Ridgecrest Baptist Church

- Path: /
- Page type: home


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

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

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


### 2. Ridgecrest Baptist Church

- Path: /
- Page type: home


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

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

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


### 3. Ridgecrest Baptist Church

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


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

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

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


### 4. Ridgecrest Baptist Church

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


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

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

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


### 5. Ridgecrest Baptist Church-About Us

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


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

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

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


### 6. News-Ridgecrest Baptist Church

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


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

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

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


### 7. Contacts-Ridgecrest Baptist Church

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


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


---AGENTS---
# Agent Instructions

You are operating the website for ridgecrestchurch.com.

Before making changes:

1. Read `SITE_CONTEXT.md`.
2. Read `ARTICLE_CONTENT_PLAN.md` when creating blog posts or working with editorial planning.
3. Work only inside this site directory.
4. Keep the site aligned with the topic, required pages, extra requirements, and recovered content map in `SITE_CONTEXT.md`.
5. Prioritize backlink restoration targets from `SITE_CONTEXT.md` and report restored, remapped, or skipped URLs.
6. Place Flatlogic link targets from `SITE_CONTEXT.md` only when they are contextually relevant, at most one per page/post, and report where they were used. Add relevant third-party external source links with this site's `utm_source` where appropriate.
7. Keep header/site identity intentional: use a visitor-facing brand name, tagline, text logo/wordmark, or logo mark instead of a raw domain placeholder.
8. Keep footer contact/legal links healthy and remove stale seed/theme credits.
9. Prefer small, verifiable changes and report what you changed.

Hard rules:

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

---ARTICLE PLAN---

# Article Content Plan

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

## Summary

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

## How Agents Should Use This Plan

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

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

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



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

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

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

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

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



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

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

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

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

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



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

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

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

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

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



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

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

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

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

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


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

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

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

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

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

codex
I have the site contract and article brief. Next I’m checking the remaining post-creator requirements, then I’ll inspect the WordPress state and media inventory so I can build the article with a real inline image instead of pretending one exists.
exec
/bin/bash -lc "find wp-content/plugins/flatlogic-post-creator/context -type f -name '*.md' | sort" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
wp-content/plugins/flatlogic-post-creator/context/PRINCIPLES.md

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

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

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

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

2. Table of contents
   *Generated automatically

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

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

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

2. Item description – obligatory

Describe the item in 1-3 paragraphs.

____________

One of the options below is obligatory

Option 1

3.1.1 Item pros:

Describe the item’s pros in 2-4 sentences

3.1.2 Item cons:

Describe the item’s cons in 2-4 sentences

Option 2

3.2 Key features:

Feature 1
Feature 2
Feature 3
etc
__________

Additional

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

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

exec
/bin/bash -lc "sed -n '261,520p' wp-content/plugins/flatlogic-post-creator/context/PRINCIPLES.md" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
* **environment**
* **user profile**
* **success metric**
* **failure criteria**

Then run the same conditions across all compared options.

### 5.3 Keep a research log

For every item, note:

* source,
* date accessed,
* what claim it supports,
* confidence level,
* follow-up needed.

### 5.4 Gate

If your strongest section is based on “several people online say...”, stop and get closer to the source.

---

## 6. Interview with adversarial curiosity

AP is refreshingly concrete here: identify yourself clearly, don’t provide full question lists in advance, don’t let interview subjects approve text before publication, default to on-the-record, negotiate any conditions at the start, seek real response from anyone portrayed negatively, and use anonymity only under strict rules with explanation and corroboration. ([The Associated Press][7])

### 6.1 Build a source mix

Aim for at least one from each relevant class:

* operator / practitioner,
* builder / insider,
* independent expert,
* skeptic / critic,
* affected stakeholder.

### 6.2 Prepare better questions

Every serious interview should include versions of these:

1. What is true here that outsiders misunderstand?
2. What evidence supports that?
3. What would change your mind?
4. Who disagrees with you, and why?
5. What document, dataset, or artifact should I inspect?
6. What is the best concrete example of this in practice?
7. What usually goes wrong?
8. What are people overstating?
9. What are people understating?
10. What should I ask the next person?

### 6.3 Force specifics

For every abstract claim, ask:

* “Give me an example.”
* “When exactly?”
* “Compared with what?”
* “How do you know?”
* “Who else can confirm that?”

### 6.4 Handle anonymity hard, not softly

If a source asks for anonymity:

* ask why,
* decide whether the information is vital,
* check whether it can be obtained another way,
* describe the source as specifically as possible,
* seek more than one source if feasible,
* explain motive where relevant.

### 6.5 Gate

Every interview should yield at least:

* one hard fact,
* one concrete example,
* one source/document lead,
* one challenge to your current thesis.

If not, the interview was too polite.

---

## 7. Verify, attribute, and try to break your own story

Reuters puts accuracy ahead of speed. ProPublica insists facts be based on documents, data, or reliable on-record sources. AP says disputed material should be attributed and internet-sourced information must be vetted to the original source. Attribution and source transparency are central trust signals. ([Reuters Agency][8])

### 7.1 Label every note

Use a hard taxonomy:

* **V** = verified fact
* **A** = analysis / inference
* **O** = opinion
* **U** = unverified lead
* **Q** = quote
* **X** = contradiction / challenge

### 7.2 Apply the “material claim test”

For each material claim:

* what is the source?
* is it primary or secondary?
* what is the date?
* what is the counterevidence?
* who would dispute it?
* has that person or side had a chance to respond?

### 7.3 Numbers get extra scrutiny

For every number, verify:

* numerator,
* denominator,
* timeframe,
* unit,
* baseline,
* whether it is typical, exceptional, or cherry-picked.

### 7.4 Distinguish three things in the draft

* **fact**
* **inference**
* **speculation**

Never let speculation wear a fact costume.

### 7.5 Gate

No **U** item may appear in final copy as an unattributed fact.

---

## 8. Distill the thesis before drafting

Nieman’s best advice here is that most writing problems are reporting problems, and that a central question should drive the piece. Rosenstiel’s “humility” principle matters too: say what you know, what you do not know, and don’t print beyond what you know. ([Nieman Storyboard][3])

### 8.1 Write the thesis in 25 words

Force compression.

### 8.2 Write 3 supporting claims

These become your core sections.

### 8.3 Write the strongest counterargument

Then answer it honestly.

### 8.4 Write one sentence of uncertainty

What remains unresolved, conditional, or unknowable?

### 8.5 Gate

If the counterargument is stronger than the thesis, that is not failure. It means the article needs a different answer.

---

## 9. Blueprint the article before writing prose

Nieman’s structure advice is practical: decide what story you are telling, gather the needed research and interviews before writing, make the intro frame the story, use a nut graf to set context or pose the question, and make the ending leave the reader smarter or with something worth thinking about. ([Nieman Storyboard][9])

### 9.1 Choose the article type

Pick one dominant form:

* **Explainer**
* **Comparison**
* **Guide / playbook**
* **Reported feature**
* **Argument / analysis**

### 9.2 Use this universal structure

1. **Lead** — tension, contradiction, or surprising fact
2. **Nut graf** — what the piece is really about, why now, why it matters
3. **Body section 1** — answer first major subquestion
4. **Body section 2** — answer second major subquestion
5. **Body section 3** — answer third major subquestion
6. **Counterpoint** — strongest objection or limit
7. **Conclusion** — what the reader should conclude now

### 9.3 Use a “section contract”

For every section, write:

* question this section answers,
* evidence it uses,
* takeaway sentence,
* visual or example if needed.

### 9.4 Gate

If a section cannot be tied to a question in the question tree, cut it.

---

## 10. Draft with evidence discipline and human texture

Poynter’s quote test is useful: a quote earns its place when it introduces a human voice or explains something important. Nieman’s scene advice is just as important: scenes require reporting; they are not decorative writing. ([Poynter][10])

### 10.1 Draft rules

Use these as hard constraints:

* one paragraph = one job,
* one section = one answer,
* one claim = one support path,
* one metaphor max per major section,
* zero unsupported flourish.

### 10.2 Quote rule

Keep a quote only if it does at least one of these:

1. reveals voice or character,
2. explains something better than paraphrase would,
3. crystallizes a disputed point.

Otherwise paraphrase.

### 10.3 Human-touch rule

Add humanity through:

* a reported scene,
* a concrete example,
* a lived consequence,
* an honest uncertainty,
* a memorable but precise formulation.

Do **not** add humanity through sentimentality, fake intimacy, or invented color.

### 10.4 Visual rule

Use:

* **table** when readers must compare,
* **chart** when readers must see pattern,
* **timeline** when sequence matters,
* **diagram** when mechanism matters,
* **document/screenshot** when proof matters.

### 10.5 Ending rule

At the end, ask:

* does this deliver what the beginning promised?
* does it leave the reader smarter?
* does it leave the reader with a clean conclusion or an honest unresolved tension?

---

## 11. Use AI as a tool, never as a witness


codex
I’ve confirmed there’s only one context markdown file to honor, and it has the usual contradictions between “story article” advice and this church post. I’m ignoring the generic SEO fluff and following the site’s more specific church/article brief, then I’ll locate a usable image and the WordPress blog setup.
exec
/bin/bash -lc 'wp core is-installed && wp option get home && wp option get siteurl && wp theme list --status=active && wp db prefix' in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "wp post list --post_type=page --fields=ID,post_title,post_name,post_status --format=table && printf '\\n---POSTS---\\n' && wp post list --post_type=post --fields=ID,post_title,post_name,post_status --format=table && printf '\\n---ATTACHMENTS---\\n' && wp post list --post_type=attachment --fields=ID,post_title,post_name,post_status --format=table | sed -n '1,120p'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 1734ms:
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
116	How to Prepare a Prayer Request for Ridgecrest (A Simple, Respectful Template)	how-to-prepare-prayer-request-template	publish
113	Ministry Spotlight: How Our Teams Serve on Sundays (Greeters, Ushers, and Hospitality)	ministry-spotlight-sunday-teams	publish
112	How to Plan Your Week Around Church (Sunday-Wednesday Rhythm at Ridgecrest)	how-to-plan-your-week-around-church-sunday-wednesday-rhythm	publish
109	Ridgecrest Baptist Church Events FAQ: Times, Arrival, Seating, and Kids Check-In	ridgecrest-baptist-church-events-faq	publish
94	How to Submit a Prayer Request or Praise Report (and What Happens Next)	submit-prayer-request-praise-report	publish
93	Church Resources for New Families: Where to Start This Week	church-resources-for-new-families	publish
91	What to Bring (and Wear) to Church at Ridgecrest: A Practical Guide for Sundays	what-to-bring-and-wear-to-church-ridgecrest	publish
88	How to Prepare for a Youth or Kids Wednesday Night Program	prepare-for-wednesday-kids-youth	publish
87	How to Use Our Events Calendar: RSVP, Reminders, and What to Bring	how-to-use-events-calendar-rsvp-reminders-what-to-bring	publish
80	What to Expect at Ridgecrest Baptist Church (Visitor-Friendly Guide)	what-to-expect-ridgecrest-baptist-church	publish
78	How to Get Involved at Ridgecrest: A First-Timer’s Guide to Ministries, Kids, and Youth	get-involved-first-timers-guide	publish
77	How to Plan a Great Sunday: A Simple Church Service Checklist	how-to-plan-a-great-sunday-checklist	publish
74	How to Plan Your First Visit to Ridgecrest Baptist Church	first-visit-ridgecrest-baptist-church	publish
51	Welcome to Ridgecrest News	welcome-to-ridgecrest-news	publish

---ATTACHMENTS---
ID	post_title	post_name	post_status
114	Sunday Meet and Greet Volunteers	sunday-meet-and-greet-volunteers	inherit
89	Wednesday Night Kids Check-In Scene	wednesday-night-kids-check-in-scene	inherit
86	Ridgecrest Events Calendar Page Screenshot	ridgecrest-events-calendar-page-screenshot	inherit
79	Ridgecrest Website Navigation Screenshot	ridgecrest-website-navigation-screenshot	inherit
76	Sunday Service Planning Desk	sunday-service-planning-desk	inherit
1	Ridgecrest Baptist Church Logo	ridgecrest-baptist-church-logo	inherit
2	Ridgecrest Service Times	ridgecrest-service-times	inherit
3	Ridgecrest Events Calendar	ridgecrest-events-calendar	inherit
4	Ridgecrest Connection Graphic	ridgecrest-connection-graphic	inherit
5	Ridgecrest Sermons Graphic	ridgecrest-sermons-graphic	inherit
6	Ridgecrest Contact Graphic	ridgecrest-contact-graphic	inherit
7	Ridgecrest Map Graphic	ridgecrest-map-graphic	inherit
8	Ridgecrest Community Illustration	ridgecrest-community-illustration	inherit
9	Ridgecrest Main Entrance	church-exterior	inherit
10	Worship Service	worship-service	inherit
11	Children Ministry	children-ministry	inherit
12	Youth Worship	youth-worship	inherit

 succeeded in 9875ms:
https://ridgecrestchurch.com
https://ridgecrestchurch.com
name	status	update	version	update_version	auto_update
church	active	none	0.7.7		off
flbg_

codex
I’ve got a solid media baseline now: there are existing screenshot attachments I can likely reuse instead of inventing a fake “church newsroom” image. I’m checking whether the News page screenshot already exists and confirming the blog index settings before I write the post.
exec
/bin/bash -lc "wp option get page_for_posts && wp option get show_on_front && wp post get 19 --fields=ID,post_title,post_name,post_status,post_content --format=json && printf '\\n---ATT 79---\\n' && wp post get 79 --fields=ID,post_title,post_name,post_status,post_content --format=json && printf '\\n---ATT 86---\\n' && wp post get 86 --fields=ID,post_title,post_name,post_status,post_content --format=json" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "wp post get 51 --fields=ID,post_title,post_name,post_status,post_content --format=json && printf '\\n---BLOG PAGE---\\n' && wp post get 23 --fields=ID,post_title,post_name,post_status --format=json" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 1176ms:
{"ID":51,"post_content":"<p>Welcome to the Ridgecrest news feed. This section is where church updates, ministry highlights, and future article-style announcements will appear.<\/p><p>If you are planning a first visit, start with our <a href=\"https:\/\/ridgecrestchurch.com\/contacts\/\">Contacts<\/a>, <a href=\"https:\/\/ridgecrestchurch.com\/church-map\/\">Church Map<\/a>, and <a href=\"https:\/\/ridgecrestchurch.com\/events-calendar\/\">Events Calendar<\/a> pages.<\/p><p>For general site-wide updates, you can also visit the <a href=\"https:\/\/ridgecrestchurch.com\/news\/\">News<\/a> page.<\/p>","post_title":"Welcome to Ridgecrest News","post_status":"publish","post_name":"welcome-to-ridgecrest-news"}

---BLOG PAGE---
{"ID":23,"post_title":"Blog","post_status":"publish","post_name":"blog"}

 succeeded in 2932ms:
23
page
{"ID":19,"post_content":"<section class=\"rc-hero\">\n  <div>\n    <p class=\"rc-eyebrow\">News<\/p>\n    <h1>Church news, announcements, and practical updates for the Ridgecrest family.<\/h1>\n    <p>This page highlights the kinds of updates members and guests most often need: schedule reminders, ministry highlights, student and kids activities, and church-wide announcements. Longer written updates will also appear on the <a href=\"https:\/\/ridgecrestchurch.com\/blog\/\">Blog<\/a> as posts are published.<\/p>\n    <div class=\"rc-actions\">\n      <a class=\"rc-button\" href=\"https:\/\/ridgecrestchurch.com\/blog\/\">Visit the Blog<\/a>\n      <a class=\"rc-button secondary\" href=\"https:\/\/ridgecrestchurch.com\/events-calendar\/\">See Upcoming Events<\/a>\n    <\/div>\n  <\/div>\n  <figure class=\"rc-media\"><img src=\"https:\/\/ridgecrestchurch.com\/wp-content\/uploads\/imports\/worship-service.jpg\" alt=\"Church family during worship service\" loading=\"lazy\"><\/figure>\n<\/section>\n\n<section class=\"rc-section\">\n  <div class=\"rc-grid rc-grid-2\">\n    <div class=\"rc-card\">\n      <h3>This week at Ridgecrest<\/h3>\n      <p>Sunday classes meet at 8:45 a.m. and worship begins at 10:00 a.m. Wednesday night kids and youth ministries begin at 6:30 p.m.<\/p>\n    <\/div>\n    <div class=\"rc-card\">\n      <h3>Where to look next<\/h3>\n      <p>Use the <a href=\"https:\/\/ridgecrestchurch.com\/events-calendar\/\">Events Calendar<\/a> for dates and the <a href=\"https:\/\/ridgecrestchurch.com\/resources\/\">Resources<\/a> page for study support, family helps, and church-life tools.<\/p>\n    <\/div>\n  <\/div>\n<\/section>\n\n<section class=\"rc-section rc-split\">\n  <div>\n    <h2>Announcements we share regularly<\/h2>\n    <ul class=\"rc-bullets\">\n      <li>Weekly worship and ministry reminders<\/li>\n      <li>Student and children\u2019s ministry events<\/li>\n      <li>Church-wide fellowship meals and special gatherings<\/li>\n      <li>Prayer needs and ministry opportunities<\/li>\n    <\/ul>\n    <p>If you need to confirm a detail before visiting, use the <a href=\"https:\/\/ridgecrestchurch.com\/contacts\/\">Contacts<\/a> page.<\/p>\n  <\/div>\n  <figure class=\"rc-media\"><img src=\"https:\/\/ridgecrestchurch.com\/wp-content\/uploads\/imports\/worship-service.jpg\" alt=\"Church worship gathering\" loading=\"lazy\"><\/figure>\n<\/section>\n\n<section class=\"rc-section rc-callout\">\n  <h2>Stay informed without missing the essentials<\/h2>\n  <p>Check this page for headline items, then visit the Blog for future article-style updates and ministry stories.<\/p>\n  <div class=\"rc-actions\">\n    <a class=\"rc-button secondary\" href=\"https:\/\/ridgecrestchurch.com\/blog\/\">Open Blog Index<\/a>\n    <a class=\"rc-button secondary\" href=\"https:\/\/ridgecrestchurch.com\/resources\/\">Open Resources<\/a>\n  <\/div>\n<\/section>","post_title":"News","post_status":"publish","post_name":"news"}

---ATT 79---
{"ID":79,"post_content":"","post_title":"Ridgecrest Website Navigation Screenshot","post_status":"inherit","post_name":"ridgecrest-website-navigation-screenshot"}

---ATT 86---
{"ID":86,"post_content":"","post_title":"Ridgecrest Events Calendar Page Screenshot","post_status":"inherit","post_name":"ridgecrest-events-calendar-page-screenshot"}

codex
The site already has a published News page and a Blog index, so I don’t need to repair the archive structure. I’m now checking whether I can capture a live screenshot of the News page locally; that gives us a credible inline image that actually matches the article topic instead of a random church stock photo.
exec
/bin/bash -lc 'command -v chromium-browser || command -v chromium || command -v google-chrome || command -v google-chrome-stable || command -v playwright || command -v wkhtmltoimage || command -v import || command -v magick' in /home/ubuntu/apps/ridgecrestchurch.com
 exited 1 in 0ms:
exec
/bin/bash -lc "wp eval 'global "'$wpdb; $ids = $wpdb->get_col("SELECT ID FROM {$wpdb->posts} WHERE post_type='"\\\"attachment\\\" AND post_status=\\\"inherit\\\" ORDER BY ID DESC\"); foreach ("'$ids as $id) { $file = get_post_meta($id, "_wp_attached_file", true); $alt = get_post_meta($id, "_wp_attachment_image_alt", true); echo $id . "'"\\t\" . get_the_title("'$id) . "'"\\t\" . "'$file . "'"\\t\" . "'$alt . PHP_EOL; }'"'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 528ms:
114	Sunday Meet and Greet Volunteers	imports/review-fix/meet-greet-0038.jpg	Church volunteers welcoming and greeting attendees before a Sunday service
89	Wednesday Night Kids Check-In Scene	imports/wednesday-night-kids-check-in-scene.jpg	Children's ministry check-in area with volunteers helping families register before a program begins
86	Ridgecrest Events Calendar Page Screenshot	imports/events-calendar-page-screenshot.png	Screenshot of the Ridgecrest Baptist Church Events Calendar page showing the weekly schedule and event sections
79	Ridgecrest Website Navigation Screenshot	imports/ridgecrest-home-navigation-screenshot.png	Phone showing Ridgecrest Baptist Church website navigation
76	Sunday Service Planning Desk	imports/sunday-service-planning-desk.jpg	Planning materials on a desk with a calendar and smartphone for Sunday service coordination
12	Youth Worship	imports/youth-worship.jpg	Students gathered for youth worship
11	Children Ministry	imports/children-ministry.jpg	Children participating in ministry activities at Ridgecrest Baptist Church
10	Worship Service	imports/worship-service.jpg	People gathered for a worship service at Ridgecrest Baptist Church
9	Ridgecrest Main Entrance	imports/church-exterior.jpg	Main entrance and covered walkway at Ridgecrest Baptist Church in Blanchard, Oklahoma
8	Ridgecrest Community Illustration	imports/groups.jpg	Illustration representing gathered church community
7	Ridgecrest Map Graphic	imports/map-directions.gif	Map and directions graphic
6	Ridgecrest Contact Graphic	imports/contact-info.gif	Contact information graphic
5	Ridgecrest Sermons Graphic	imports/sermons.gif	Sermons and resources graphic
4	Ridgecrest Connection Graphic	imports/connect.gif	Connection and life groups graphic
3	Ridgecrest Events Calendar	imports/events.gif	Events calendar graphic
2	Ridgecrest Service Times	imports/service-times.gif	Service times for Sunday and Wednesday gatherings
1	Ridgecrest Baptist Church Logo	imports/logo.gif	Ridgecrest Baptist Church logo

codex
I can’t rely on a browser binary here, so I’m checking the uploaded media folder directly for a better screenshot asset before I fall back to an existing site screenshot. If there’s a News-page capture already in uploads, I’ll use that; otherwise I’ll use the closest existing site screenshot and keep the body copy honest about what it shows.
exec
/bin/bash -lc "find wp-content/uploads -type f \\( -iname '*news*' -o -iname '*navigation*' -o -iname '*calendar*' -o -iname '*screenshot*' \\) | sort | sed -n '1,120p'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
wp-content/uploads/flatlogic-article-tasks/job-80/how-to-use-events-calendar-rsvp-reminders-what-to-bring.html
wp-content/uploads/imports/events-calendar-page-screenshot.png
wp-content/uploads/imports/ridgecrest-home-navigation-screenshot.png

exec
/bin/bash -lc "find wp-content/uploads/imports -maxdepth 1 -type f | sed 's#"'^#/#'"' | sort | sed -n '1,120p'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 0ms:
/wp-content/uploads/imports/children-ministry.jpg
/wp-content/uploads/imports/church-exterior.jpg
/wp-content/uploads/imports/connect.gif
/wp-content/uploads/imports/contact-info.gif
/wp-content/uploads/imports/events-calendar-page-screenshot.png
/wp-content/uploads/imports/events.gif
/wp-content/uploads/imports/groups.jpg
/wp-content/uploads/imports/logo.gif
/wp-content/uploads/imports/map-directions.gif
/wp-content/uploads/imports/ridgecrest-home-navigation-screenshot.png
/wp-content/uploads/imports/sermons.gif
/wp-content/uploads/imports/service-times.gif
/wp-content/uploads/imports/sunday-service-planning-desk.jpg
/wp-content/uploads/imports/wednesday-night-kids-check-in-scene.jpg
/wp-content/uploads/imports/worship-service.jpg
/wp-content/uploads/imports/youth-group.jpg
/wp-content/uploads/imports/youth-worship.jpg

codex
I’m at the point where the content and media choices matter. Before drafting, I’m checking whether the legacy `contact.php` target is actually live or whether I should steer readers to the current `Contacts` and `Church Map` pages instead of creating a dead internal link for the sake of a checklist.
exec
/bin/bash -lc "ls -la contact.php contacts.html about.html news.html events-calendar 2>/dev/null || true && printf '\\n---PERMALINKS---\\n' && wp rewrite structure && printf '\\n---PAGE URL CHECK---\\n' && wp post url 19 && wp post url 20 && wp post url 21 && wp post url 18 && wp post url 23" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc 'wp user list --fields=ID,user_login,display_name,user_email,roles --format=table' in /home/ubuntu/apps/ridgecrestchurch.com
 exited 1 in 555ms:
usage: wp rewrite structure <permastruct> [--category-base=<base>] [--tag-base=<base>] [--hard]

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

codex
The current author roster doesn’t include `felix-rowan`, so I’m creating that user rather than borrowing a different byline. I’m also checking whether `contact.php` exists anywhere locally; if it doesn’t, I’ll keep the article on the live contact pages and not manufacture a dead target.
exec
/bin/bash -lc "find . -name 'contact.php' -o -name 'contact*php' -o -name 'contacts.html' -o -name 'church-map*' -o -name 'news.html' -o -name 'events-calendar' | sed -n '1,120p'" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "wp user create felix-rowan felix-rowan@ridgecrestchurch.com --user_pass='ChangeMe-NotPublic-123"'!'"' --role=author --display_name='Felix Rowan' --porcelain" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 407ms:
./wp-content/themes/twentytwentyfive/patterns/contact-location-and-link.php
./wp-content/themes/twentytwentyfive/patterns/contact-info-locations.php
./wp-content/themes/twentytwentyfive/patterns/contact-centered-social-link.php
./wp-content/plugins/all-in-one-wp-migration/lib/view/main/contact-support.php
./wp-content/plugins/internal-links/vendor/freemius/wordpress-sdk/templates/contact.php
./wp-content/plugins/internal-links/vendor/freemius/wordpress-sdk/templates/forms/deactivation/contact.php
./wp-content/plugins/internal-links-premium/vendor/freemius/wordpress-sdk/templates/contact.php
./wp-content/plugins/internal-links-premium/vendor/freemius/wordpress-sdk/templates/forms/deactivation/contact.php

 succeeded in 722ms:
9

codex
I’ve got the author and image plan; now I’m checking the legacy URLs the brief asked for. If `news.html` or `contact.php` don’t resolve cleanly, I’ll use the live page equivalents in the article rather than linking readers into a dead end.
exec
/bin/bash -lc "for u in 'https://ridgecrestchurch.com/news.html' 'https://ridgecrestchurch.com/contact.php' 'https://ridgecrestchurch.com/contacts.html' 'https://ridgecrestchurch.com/events-calendar/' 'https://ridgecrestchurch.com/about.html' 'https://ridgecrestchurch.com/'; do echo \"URL: "'$u"; curl -I -L --max-redirs 5 --silent --show-error "$u" | sed -n '"'1,8p'; echo; done" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "wp eval 'foreach ([79,86] as "'$id) { echo $id."'"\\t\".wp_get_attachment_url("'$id)."'"\\t\".get_post_meta("'$id, "_wp_attachment_image_alt", true).PHP_EOL; }'"'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 588ms:
79	https://ridgecrestchurch.com/wp-content/uploads/imports/ridgecrest-home-navigation-screenshot.png	Phone showing Ridgecrest Baptist Church website navigation
86	https://ridgecrestchurch.com/wp-content/uploads/imports/events-calendar-page-screenshot.png	Screenshot of the Ridgecrest Baptist Church Events Calendar page showing the weekly schedule and event sections

 succeeded in 4094ms:
HTTP/2 301 
date: Fri, 26 Jun 2026 19:01:17 GMT
content-type: text/html; charset=iso-8859-1
location: http://ridgecrestchurch.com/news/
server: cloudflare
cf-cache-status: DYNAMIC
report-to: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=OCA3jYeary1OtLh5bPILIRtX589EKNRHAUqm25GgVntkmvshinbQ%2FqboqxvCEouEWoGxy%2FZ5EhRV4Ym8CXEDzdRX%2FKj6o4%2FY0TwM%2FDKu0j1%2BRGsjm0Tt54ORZb2zCabw4E3YFi7Mxw%3D%3D"}]}
nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}

URL: https://ridgecrestchurch.com/contact.php
HTTP/2 301 
date: Fri, 26 Jun 2026 19:01:18 GMT
content-type: text/html; charset=iso-8859-1
location: http://ridgecrestchurch.com/contacts/
server: cloudflare
cf-cache-status: DYNAMIC
report-to: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=o4cpzJCZfUTT1kLncG3u0l7mlUMj5g1PuNYI39l7zZhQniG8aFGZgvhnwXETu0H%2BEU8nB%2F3lIBRbKrxd4ivhV6Qv1PYAMGlTF7N%2BuvymUfdK5%2FfctEXo80jBtHu6FtP9eS%2F7%2BWr6ig%3D%3D"}]}
nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}

URL: https://ridgecrestchurch.com/contacts.html
HTTP/2 301 
date: Fri, 26 Jun 2026 19:01:19 GMT
content-type: text/html; charset=iso-8859-1
location: http://ridgecrestchurch.com/contacts/
server: cloudflare
cf-cache-status: DYNAMIC
report-to: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=Ul36xDBxkE2EIUbwZp%2F0Wmt7d7DmlyGCll7czIgcBbbkaDPR1kCUqIUflnzSApik%2B7%2Buua%2F13%2BrJ0SmUCvPqVmCZ99Vo3B1BYzpKqFjfeNawywPQpKYYyySF%2BX3DaDy0q%2FsoYgQQlA%3D%3D"}]}
nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}

URL: https://ridgecrestchurch.com/events-calendar/
HTTP/2 200 
date: Fri, 26 Jun 2026 19:01:20 GMT
content-type: text/html; charset=UTF-8
link: <https://ridgecrestchurch.com/wp-json/>; rel="https://api.w.org/", <https://ridgecrestchurch.com/wp-json/wp/v2/pages/18>; rel="alternate"; title="JSON"; type="application/json", <https://ridgecrestchurch.com/?p=18>; 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=XopMgIC18hkaNdO4kgl6WpTRuOFWRBcYDzhZkn%2FEXv91vNj4XBQjyO6ifen14%2BUGNpbOFp0GK%2FFJVI26SGkGDpsgTW7wuubrllUbEjBxMrSfzsfvOf7evWhY0lryrmWxtxutYzGM9Q%3D%3D"}]}
nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}

URL: https://ridgecrestchurch.com/about.html
HTTP/2 301 
date: Fri, 26 Jun 2026 19:01:20 GMT
content-type: text/html; charset=iso-8859-1
location: http://ridgecrestchurch.com/about-us/
server: cloudflare
cf-cache-status: DYNAMIC
report-to: {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=x7L8JnFOlUdb%2F%2FNx2SxixP%2BUDaH3vheY3r%2Bxkre5zJMUc%2FXO9b63jY1pYttyNy%2FernS%2F1ocqn19JhEj8h9SQSjA0gCJnx0%2BPBzIOIy4xJt%2BLqBnSrdRuUBSwUqvZ9t%2F%2B5TnquLKE2A%3D%3D"}]}
nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}

URL: https://ridgecrestchurch.com/
HTTP/2 200 
date: Fri, 26 Jun 2026 19:01:21 GMT
content-type: text/html; charset=UTF-8
link: <https://ridgecrestchurch.com/wp-json/>; rel="https://api.w.org/", <https://ridgecrestchurch.com/wp-json/wp/v2/pages/13>; rel="alternate"; title="JSON"; type="application/json", <https://ridgecrestchurch.com/>; 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=YLh8hEMMX19LYGHWyI5%2B46yNc%2B9%2B36EMnLGZQgV%2FgwZaTlnbHc0U3KvvqeQz5OifadmDu6Ox2iV%2BA9aRQRFS2O1c80t3tsMXCMyAUbjHIdCdLs7RDgltIYjQv2fqmWf2OHiOM85YiA%3D%3D"}]}
nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}


web search: 
web search: site:support.google.com/calendar create an event Google Calendar Help
codex
I’m writing the article now. It will use the current live News/Contacts/Events pages, avoid the dead-weight restoration language, and include two inline images from the site’s own media library so the post has something real to look at.
apply patch
patch: completed
/home/ubuntu/apps/ridgecrestchurch.com/.tmp/job-548-news-page-article.html
diff --git a//home/ubuntu/apps/ridgecrestchurch.com/.tmp/job-548-news-page-article.html b//home/ubuntu/apps/ridgecrestchurch.com/.tmp/job-548-news-page-article.html
new file mode 100644
index 0000000000000000000000000000000000000000..9fe6a8c43e6dedcc09ee0af01e09db5978ee6f60
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/.tmp/job-548-news-page-article.html
@@ -0,0 +1,161 @@
+<p><strong><em>The News page is where the church quietly tells you what matters next.</em></strong> Ignore it, and you will keep acting surprised when an event, reminder, or ministry update shows up after the fact. A news page is not decoration. It is the place where Ridgecrest Baptist Church puts the practical details that decide whether you arrive prepared or arrive confused.</p>
+
+<p>If you have ever asked yourself, “What changed?” “Who is this for?” “Do I need to do anything?” or “Why did nobody tell me sooner?”, that is exactly why this page exists. The answer is not mystery. It is usually a date, a topic, a small action item, and your responsibility to read the whole thing instead of the first sentence.</p>
+
+<p>This guide walks through how to use the Ridgecrest News page without pretending attention is automatic. You will learn what belongs there, where to find it, how to scan updates fast, how to turn an announcement into a calendar reminder, and when to use the Events Calendar, Contacts, or Church Map instead of hoping a vague memory will save you.</p>
+
+<p>For context, the Ridgecrest site also keeps related information on the <a href="https://ridgecrestchurch.com/about.html">About Us</a>, <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>, and <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> pages, so you do not have to guess which page is doing which job. That is the good news. The bad news is that you still have to read the page.</p>
+
+<h2>What the News page is for</h2>
+
+<p>The News page is where short, useful updates live. Not the full history of the church. Not a sermon archive. Not a place for vague encouragement dressed up as information. It is for the kinds of announcements that affect attendance, timing, preparation, or follow-up.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>What you see</th>
+      <th>What it means</th>
+      <th>What you should do</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Event announcement</td>
+      <td>A dated gathering, deadline, or special church activity</td>
+      <td>Check the time, location, and whether you need to respond</td>
+    </tr>
+    <tr>
+      <td>Ministry update</td>
+      <td>Information for Kids, Youth, volunteers, or a specific group</td>
+      <td>Read whether it applies to you or your household</td>
+    </tr>
+    <tr>
+      <td>Special notice</td>
+      <td>A schedule change, church-wide reminder, or urgent correction</td>
+      <td>Put it on your calendar and stop relying on memory</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>The point is simple: the News page is not there to entertain you. It is there to reduce avoidable confusion. Most church problems are not dramatic. They are just small timing errors repeated by too many people.</p>
+
+<h2>Where to find the News page in the main navigation</h2>
+
+<p>On the site, the News page is part of the main navigation. If you are on desktop, look across the top menu. If you are on a phone, open the navigation menu and look for the same label. No treasure hunt required. Just read the menu instead of tapping at random like a distracted raccoon.</p>
+
+<p>For the live page, use the <a href="https://ridgecrestchurch.com/news.html">News</a> link. The site also keeps a simple front-door version of the page at <a href="https://ridgecrestchurch.com/news/">/news/</a>, so the content is easy to reach either way.</p>
+
+<figure class="wp-block-image alignwide">
+  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/ridgecrest-home-navigation-screenshot.png" alt="Phone view of Ridgecrest church navigation with the News page visible" loading="lazy" />
+  <figcaption>Use the main menu first. That is usually where the answer lives, which is inconvenient for people who prefer guesswork.</figcaption>
+</figure>
+
+<p>If you are already on the homepage, the quickest path is usually: homepage, main menu, News. If you are already on the News page, congratulations, you have won a round of basic navigation. Now read the actual update.</p>
+
+<h2>How to scan an update quickly</h2>
+
+<p>Most people do not need to read every line of a church update with a scholar’s commitment. They need the facts. Look for the parts that change what you do next.</p>
+
+<ul>
+  <li><strong>Date</strong> - When does it happen, and is there a deadline before it?</li>
+  <li><strong>Topic</strong> - What is this about in one sentence?</li>
+  <li><strong>Audience</strong> - Who actually needs this: everyone, parents, students, volunteers, or a specific class?</li>
+  <li><strong>Action needed</strong> - Do you need to RSVP, bring something, sign up, show up early, or do nothing at all?</li>
+</ul>
+
+<p>A practical scan takes less than a minute if you resist the urge to read every word twice. Start with the headline, then the first paragraph, then the date and contact details. If the post does not answer those four questions, keep reading until it does or until it proves it does not know what it is doing.</p>
+
+<p>Here is the working rule: if an update does not tell you when, who, and what next, it is incomplete from a visitor’s point of view. That is not your failure. It is the post’s.</p>
+
+<h3>Fast-read checklist</h3>
+
+<ol>
+  <li>Read the title.</li>
+  <li>Find the date.</li>
+  <li>Check who the update is for.</li>
+  <li>Look for a deadline or response request.</li>
+  <li>Put the event or reminder into your calendar if it matters to you.</li>
+</ol>
+
+<h2>Common types of posts you will see</h2>
+
+<p>The News page usually carries the same kinds of items, because churches are not that mysterious when they finally decide to write things down.</p>
+
+<h3>Service reminders</h3>
+
+<p>These are the simplest posts and the easiest to ignore. Do not. They often confirm service times, special schedules, or location changes. If the church is adjusting a service or class, this is where the update usually lands first.</p>
+
+<h3>Special events</h3>
+
+<p>Events can include fellowship meals, student activities, children’s ministry gatherings, church-wide celebrations, and seasonal services. If there is a deadline, ticket, RSVP, or sign-up, it belongs here. That is the part people forget and then pretend was never mentioned.</p>
+
+<h3>Ministry highlights</h3>
+
+<p>Sometimes the News page highlights what a ministry is doing, who it serves, or how to participate. This is useful because it tells you whether the update is just informational or actually inviting you to act. Most people confuse those two. They should not.</p>
+
+<h3>Prayer needs and follow-up notes</h3>
+
+<p>Not every update is about logistics. Some posts will point readers toward prayer, care, or encouragement. Those updates are different: read them carefully, respond appropriately, and do not treat them like event spam. That is not a good look.</p>
+
+<h2>How to respond to what you read</h2>
+
+<p>The whole point of reading a church update is to do something useful with it. Otherwise you are just collecting information the way some people collect receipts.</p>
+
+<ul>
+  <li><strong>RSVP when asked.</strong> If a post asks for a response, give one. That is not optional decor. It is part of the plan.</li>
+  <li><strong>Bring what the post names.</strong> If the update says bring food, supplies, forms, or a Bible, bring those things instead of improvising your way into inconvenience.</li>
+  <li><strong>Ask questions early.</strong> If the details are unclear, use the contact page before the event. Confusion gets cheaper when it is solved early.</li>
+  <li><strong>Share it with the right person.</strong> If the update affects your family, students, or ministry group, forward it before it disappears into the swamp of unread messages.</li>
+</ul>
+
+<p>When in doubt, use the <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> page or the direct <a href="https://ridgecrestchurch.com/contact.php">contact form</a>. Both land you in the same place emotionally: someone on the church side can answer the question instead of making you guess.</p>
+
+<p>If the update affects where to park, which entrance to use, or when to arrive, check the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> as well. A news item can tell you the plan, but a map tells you where to physically go. Oddly enough, that still matters.</p>
+
+<h2>Planning ahead: turn the news item into a calendar action</h2>
+
+<p>Reading an update is only half the job. The other half is making sure your future self does not quietly sabotage you. If something matters, put it on your personal calendar the same day you read it.</p>
+
+<figure class="wp-block-image alignwide">
+  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/events-calendar-page-screenshot.png" alt="Ridgecrest Events Calendar page screenshot with schedule and event sections" loading="lazy" />
+  <figcaption>Use the Events Calendar for dates. Use your own calendar for memory. Yes, both. Memory is a terrible project manager.</figcaption>
+</figure>
+
+<p>That can be as simple as copying the date, time, location, and one-line purpose into your phone calendar. If you use Google Calendar, Apple Calendar, or Outlook, each has its own help page for creating and managing events. The mechanics are not impressive, but neither is forgetting something you already meant to attend. For reference, see <a href="https://support.google.com/calendar/answer/72143?co=GENIE.Platform%3DDesktop&amp;hl=en&amp;utm_source=ridgecrestchurch.com">Google Calendar’s event creation help</a>, <a href="https://support.apple.com/guide/iphone/create-and-edit-events-in-calendar-iph3d110f84/ios?utm_source=ridgecrestchurch.com">Apple’s Calendar instructions for iPhone</a>, and <a href="https://support.microsoft.com/en-us/outlook/calendar/introduction-to-the-outlook-calendar?utm_source=ridgecrestchurch.com">Microsoft’s Outlook Calendar overview</a>.</p>
+
+<p>Use reminders for anything that has a deadline or requires preparation. If an event says “bring food,” “arrive early,” or “sign up by Thursday,” that is not optional trivia. It is the actual task.</p>
+
+<h2>How to stay in the loop between Sunday services</h2>
+
+<p>Do not wait until Sunday to discover the thing you were supposed to know on Tuesday. The News page and the Events Calendar work together. One explains what is happening. The other helps you see when it happens.</p>
+
+<ul>
+  <li>Check <a href="https://ridgecrestchurch.com/news.html">News</a> for announcements and changes.</li>
+  <li>Check <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for dates and upcoming gatherings.</li>
+  <li>Check <a href="https://ridgecrestchurch.com/">Home</a> if you want the main site entry point again because you clicked yourself into confusion.</li>
+</ul>
+
+<p>A decent habit is to review News once during the week and again before the weekend. That is enough to catch most updates without treating the church website like a full-time job.</p>
+
+<h2>Quick FAQ</h2>
+
+<h3>What if I missed it?</h3>
+
+<p>Start with the News post and the Events Calendar. If the update included a deadline or sign-up, use the contact page immediately to ask whether anything can still be done. Do not assume silence means the issue disappeared. It usually means you have not checked the right page yet.</p>
+
+<h3>Where do I find the details?</h3>
+
+<p>Use the News page first. If the post is brief, the next stop is the Events Calendar, then Contacts or Church Map if location or timing matters. If the information still feels thin after that, the problem is not you. The update needs more detail.</p>
+
+<h3>Who do I contact?</h3>
+
+<p>Use <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> for church staff information and <a href="https://ridgecrestchurch.com/contact.php">contact.php</a> if you want the direct contact path. If the matter is location-specific, add the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> to the mix so you are not asking a question that the map already answered.</p>
+
+<h2>Next steps</h2>
+
+<p>If you only remember three things, make them these: read the News page, check the Events Calendar, and contact the church when the update affects you directly. That is enough to stay informed without pretending every announcement will somehow reach you by psychic means.</p>
+
+<p>Start with the <a href="https://ridgecrestchurch.com/news.html">News</a> page, then move to the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for dates, and use <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> or the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> when you need a person, a place, or both. If you want more background on the church itself, the <a href="https://ridgecrestchurch.com/about.html">About Us</a> page is there too.</p>
+
+<p>That is the whole trick. Read the update, identify the action, and move it into your calendar before it evaporates. Basic process. Less drama.</p>
+

diff --git a//home/ubuntu/apps/ridgecrestchurch.com/.tmp/job-548-news-page-article.html b//home/ubuntu/apps/ridgecrestchurch.com/.tmp/job-548-news-page-article.html
new file mode 100644
index 0000000000000000000000000000000000000000..9fe6a8c43e6dedcc09ee0af01e09db5978ee6f60
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/.tmp/job-548-news-page-article.html
@@ -0,0 +1,161 @@
+<p><strong><em>The News page is where the church quietly tells you what matters next.</em></strong> Ignore it, and you will keep acting surprised when an event, reminder, or ministry update shows up after the fact. A news page is not decoration. It is the place where Ridgecrest Baptist Church puts the practical details that decide whether you arrive prepared or arrive confused.</p>
+
+<p>If you have ever asked yourself, “What changed?” “Who is this for?” “Do I need to do anything?” or “Why did nobody tell me sooner?”, that is exactly why this page exists. The answer is not mystery. It is usually a date, a topic, a small action item, and your responsibility to read the whole thing instead of the first sentence.</p>
+
+<p>This guide walks through how to use the Ridgecrest News page without pretending attention is automatic. You will learn what belongs there, where to find it, how to scan updates fast, how to turn an announcement into a calendar reminder, and when to use the Events Calendar, Contacts, or Church Map instead of hoping a vague memory will save you.</p>
+
+<p>For context, the Ridgecrest site also keeps related information on the <a href="https://ridgecrestchurch.com/about.html">About Us</a>, <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>, and <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> pages, so you do not have to guess which page is doing which job. That is the good news. The bad news is that you still have to read the page.</p>
+
+<h2>What the News page is for</h2>
+
+<p>The News page is where short, useful updates live. Not the full history of the church. Not a sermon archive. Not a place for vague encouragement dressed up as information. It is for the kinds of announcements that affect attendance, timing, preparation, or follow-up.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>What you see</th>
+      <th>What it means</th>
+      <th>What you should do</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Event announcement</td>
+      <td>A dated gathering, deadline, or special church activity</td>
+      <td>Check the time, location, and whether you need to respond</td>
+    </tr>
+    <tr>
+      <td>Ministry update</td>
+      <td>Information for Kids, Youth, volunteers, or a specific group</td>
+      <td>Read whether it applies to you or your household</td>
+    </tr>
+    <tr>
+      <td>Special notice</td>
+      <td>A schedule change, church-wide reminder, or urgent correction</td>
+      <td>Put it on your calendar and stop relying on memory</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>The point is simple: the News page is not there to entertain you. It is there to reduce avoidable confusion. Most church problems are not dramatic. They are just small timing errors repeated by too many people.</p>
+
+<h2>Where to find the News page in the main navigation</h2>
+
+<p>On the site, the News page is part of the main navigation. If you are on desktop, look across the top menu. If you are on a phone, open the navigation menu and look for the same label. No treasure hunt required. Just read the menu instead of tapping at random like a distracted raccoon.</p>
+
+<p>For the live page, use the <a href="https://ridgecrestchurch.com/news.html">News</a> link. The site also keeps a simple front-door version of the page at <a href="https://ridgecrestchurch.com/news/">/news/</a>, so the content is easy to reach either way.</p>
+
+<figure class="wp-block-image alignwide">
+  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/ridgecrest-home-navigation-screenshot.png" alt="Phone view of Ridgecrest church navigation with the News page visible" loading="lazy" />
+  <figcaption>Use the main menu first. That is usually where the answer lives, which is inconvenient for people who prefer guesswork.</figcaption>
+</figure>
+
+<p>If you are already on the homepage, the quickest path is usually: homepage, main menu, News. If you are already on the News page, congratulations, you have won a round of basic navigation. Now read the actual update.</p>
+
+<h2>How to scan an update quickly</h2>
+
+<p>Most people do not need to read every line of a church update with a scholar’s commitment. They need the facts. Look for the parts that change what you do next.</p>
+
+<ul>
+  <li><strong>Date</strong> - When does it happen, and is there a deadline before it?</li>
+  <li><strong>Topic</strong> - What is this about in one sentence?</li>
+  <li><strong>Audience</strong> - Who actually needs this: everyone, parents, students, volunteers, or a specific class?</li>
+  <li><strong>Action needed</strong> - Do you need to RSVP, bring something, sign up, show up early, or do nothing at all?</li>
+</ul>
+
+<p>A practical scan takes less than a minute if you resist the urge to read every word twice. Start with the headline, then the first paragraph, then the date and contact details. If the post does not answer those four questions, keep reading until it does or until it proves it does not know what it is doing.</p>
+
+<p>Here is the working rule: if an update does not tell you when, who, and what next, it is incomplete from a visitor’s point of view. That is not your failure. It is the post’s.</p>
+
+<h3>Fast-read checklist</h3>
+
+<ol>
+  <li>Read the title.</li>
+  <li>Find the date.</li>
+  <li>Check who the update is for.</li>
+  <li>Look for a deadline or response request.</li>
+  <li>Put the event or reminder into your calendar if it matters to you.</li>
+</ol>
+
+<h2>Common types of posts you will see</h2>
+
+<p>The News page usually carries the same kinds of items, because churches are not that mysterious when they finally decide to write things down.</p>
+
+<h3>Service reminders</h3>
+
+<p>These are the simplest posts and the easiest to ignore. Do not. They often confirm service times, special schedules, or location changes. If the church is adjusting a service or class, this is where the update usually lands first.</p>
+
+<h3>Special events</h3>
+
+<p>Events can include fellowship meals, student activities, children’s ministry gatherings, church-wide celebrations, and seasonal services. If there is a deadline, ticket, RSVP, or sign-up, it belongs here. That is the part people forget and then pretend was never mentioned.</p>
+
+<h3>Ministry highlights</h3>
+
+<p>Sometimes the News page highlights what a ministry is doing, who it serves, or how to participate. This is useful because it tells you whether the update is just informational or actually inviting you to act. Most people confuse those two. They should not.</p>
+
+<h3>Prayer needs and follow-up notes</h3>
+
+<p>Not every update is about logistics. Some posts will point readers toward prayer, care, or encouragement. Those updates are different: read them carefully, respond appropriately, and do not treat them like event spam. That is not a good look.</p>
+
+<h2>How to respond to what you read</h2>
+
+<p>The whole point of reading a church update is to do something useful with it. Otherwise you are just collecting information the way some people collect receipts.</p>
+
+<ul>
+  <li><strong>RSVP when asked.</strong> If a post asks for a response, give one. That is not optional decor. It is part of the plan.</li>
+  <li><strong>Bring what the post names.</strong> If the update says bring food, supplies, forms, or a Bible, bring those things instead of improvising your way into inconvenience.</li>
+  <li><strong>Ask questions early.</strong> If the details are unclear, use the contact page before the event. Confusion gets cheaper when it is solved early.</li>
+  <li><strong>Share it with the right person.</strong> If the update affects your family, students, or ministry group, forward it before it disappears into the swamp of unread messages.</li>
+</ul>
+
+<p>When in doubt, use the <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> page or the direct <a href="https://ridgecrestchurch.com/contact.php">contact form</a>. Both land you in the same place emotionally: someone on the church side can answer the question instead of making you guess.</p>
+
+<p>If the update affects where to park, which entrance to use, or when to arrive, check the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> as well. A news item can tell you the plan, but a map tells you where to physically go. Oddly enough, that still matters.</p>
+
+<h2>Planning ahead: turn the news item into a calendar action</h2>
+
+<p>Reading an update is only half the job. The other half is making sure your future self does not quietly sabotage you. If something matters, put it on your personal calendar the same day you read it.</p>
+
+<figure class="wp-block-image alignwide">
+  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/events-calendar-page-screenshot.png" alt="Ridgecrest Events Calendar page screenshot with schedule and event sections" loading="lazy" />
+  <figcaption>Use the Events Calendar for dates. Use your own calendar for memory. Yes, both. Memory is a terrible project manager.</figcaption>
+</figure>
+
+<p>That can be as simple as copying the date, time, location, and one-line purpose into your phone calendar. If you use Google Calendar, Apple Calendar, or Outlook, each has its own help page for creating and managing events. The mechanics are not impressive, but neither is forgetting something you already meant to attend. For reference, see <a href="https://support.google.com/calendar/answer/72143?co=GENIE.Platform%3DDesktop&amp;hl=en&amp;utm_source=ridgecrestchurch.com">Google Calendar’s event creation help</a>, <a href="https://support.apple.com/guide/iphone/create-and-edit-events-in-calendar-iph3d110f84/ios?utm_source=ridgecrestchurch.com">Apple’s Calendar instructions for iPhone</a>, and <a href="https://support.microsoft.com/en-us/outlook/calendar/introduction-to-the-outlook-calendar?utm_source=ridgecrestchurch.com">Microsoft’s Outlook Calendar overview</a>.</p>
+
+<p>Use reminders for anything that has a deadline or requires preparation. If an event says “bring food,” “arrive early,” or “sign up by Thursday,” that is not optional trivia. It is the actual task.</p>
+
+<h2>How to stay in the loop between Sunday services</h2>
+
+<p>Do not wait until Sunday to discover the thing you were supposed to know on Tuesday. The News page and the Events Calendar work together. One explains what is happening. The other helps you see when it happens.</p>
+
+<ul>
+  <li>Check <a href="https://ridgecrestchurch.com/news.html">News</a> for announcements and changes.</li>
+  <li>Check <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for dates and upcoming gatherings.</li>
+  <li>Check <a href="https://ridgecrestchurch.com/">Home</a> if you want the main site entry point again because you clicked yourself into confusion.</li>
+</ul>
+
+<p>A decent habit is to review News once during the week and again before the weekend. That is enough to catch most updates without treating the church website like a full-time job.</p>
+
+<h2>Quick FAQ</h2>
+
+<h3>What if I missed it?</h3>
+
+<p>Start with the News post and the Events Calendar. If the update included a deadline or sign-up, use the contact page immediately to ask whether anything can still be done. Do not assume silence means the issue disappeared. It usually means you have not checked the right page yet.</p>
+
+<h3>Where do I find the details?</h3>
+
+<p>Use the News page first. If the post is brief, the next stop is the Events Calendar, then Contacts or Church Map if location or timing matters. If the information still feels thin after that, the problem is not you. The update needs more detail.</p>
+
+<h3>Who do I contact?</h3>
+
+<p>Use <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> for church staff information and <a href="https://ridgecrestchurch.com/contact.php">contact.php</a> if you want the direct contact path. If the matter is location-specific, add the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> to the mix so you are not asking a question that the map already answered.</p>
+
+<h2>Next steps</h2>
+
+<p>If you only remember three things, make them these: read the News page, check the Events Calendar, and contact the church when the update affects you directly. That is enough to stay informed without pretending every announcement will somehow reach you by psychic means.</p>
+
+<p>Start with the <a href="https://ridgecrestchurch.com/news.html">News</a> page, then move to the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for dates, and use <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> or the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> when you need a person, a place, or both. If you want more background on the church itself, the <a href="https://ridgecrestchurch.com/about.html">About Us</a> page is there too.</p>
+
+<p>That is the whole trick. Read the update, identify the action, and move it into your calendar before it evaporates. Basic process. Less drama.</p>
+

codex
The article draft is in place. I’m publishing it now with the image attachments already in the media library, then I’ll verify the URL, author, featured image, and that the inline image tags survived the WordPress round-trip instead of getting stripped or mangled.
exec
/bin/bash -lc "wp post meta update 79 _wp_attachment_image_alt 'Phone view of Ridgecrest site navigation with the News page visible' && wp post meta update 86 _wp_attachment_image_alt 'Ridgecrest Events Calendar page screenshot showing upcoming items'" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc 'content="$(< .tmp/job-548-news-page-article.html)"; wp post create --post_type=post --post_status=publish --post_title='"'How to Read and Use Ridgecrest Baptist Church’s News Page (So You Never Miss an Update)' --post_name='how-to-use-news-page-ridgecrest' --post_author=9 --post_excerpt='A practical guide to navigating Ridgecrest Baptist Church’s News page so you can track announcements, plan ahead, and act on updates without missing the useful part.' --post_content=\""'$content" --porcelain' in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 855ms:
119

diff --git a//home/ubuntu/apps/ridgecrestchurch.com/.tmp/job-548-news-page-article.html b//home/ubuntu/apps/ridgecrestchurch.com/.tmp/job-548-news-page-article.html
new file mode 100644
index 0000000000000000000000000000000000000000..9fe6a8c43e6dedcc09ee0af01e09db5978ee6f60
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/.tmp/job-548-news-page-article.html
@@ -0,0 +1,161 @@
+<p><strong><em>The News page is where the church quietly tells you what matters next.</em></strong> Ignore it, and you will keep acting surprised when an event, reminder, or ministry update shows up after the fact. A news page is not decoration. It is the place where Ridgecrest Baptist Church puts the practical details that decide whether you arrive prepared or arrive confused.</p>
+
+<p>If you have ever asked yourself, “What changed?” “Who is this for?” “Do I need to do anything?” or “Why did nobody tell me sooner?”, that is exactly why this page exists. The answer is not mystery. It is usually a date, a topic, a small action item, and your responsibility to read the whole thing instead of the first sentence.</p>
+
+<p>This guide walks through how to use the Ridgecrest News page without pretending attention is automatic. You will learn what belongs there, where to find it, how to scan updates fast, how to turn an announcement into a calendar reminder, and when to use the Events Calendar, Contacts, or Church Map instead of hoping a vague memory will save you.</p>
+
+<p>For context, the Ridgecrest site also keeps related information on the <a href="https://ridgecrestchurch.com/about.html">About Us</a>, <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>, and <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> pages, so you do not have to guess which page is doing which job. That is the good news. The bad news is that you still have to read the page.</p>
+
+<h2>What the News page is for</h2>
+
+<p>The News page is where short, useful updates live. Not the full history of the church. Not a sermon archive. Not a place for vague encouragement dressed up as information. It is for the kinds of announcements that affect attendance, timing, preparation, or follow-up.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>What you see</th>
+      <th>What it means</th>
+      <th>What you should do</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Event announcement</td>
+      <td>A dated gathering, deadline, or special church activity</td>
+      <td>Check the time, location, and whether you need to respond</td>
+    </tr>
+    <tr>
+      <td>Ministry update</td>
+      <td>Information for Kids, Youth, volunteers, or a specific group</td>
+      <td>Read whether it applies to you or your household</td>
+    </tr>
+    <tr>
+      <td>Special notice</td>
+      <td>A schedule change, church-wide reminder, or urgent correction</td>
+      <td>Put it on your calendar and stop relying on memory</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>The point is simple: the News page is not there to entertain you. It is there to reduce avoidable confusion. Most church problems are not dramatic. They are just small timing errors repeated by too many people.</p>
+
+<h2>Where to find the News page in the main navigation</h2>
+
+<p>On the site, the News page is part of the main navigation. If you are on desktop, look across the top menu. If you are on a phone, open the navigation menu and look for the same label. No treasure hunt required. Just read the menu instead of tapping at random like a distracted raccoon.</p>
+
+<p>For the live page, use the <a href="https://ridgecrestchurch.com/news.html">News</a> link. The site also keeps a simple front-door version of the page at <a href="https://ridgecrestchurch.com/news/">/news/</a>, so the content is easy to reach either way.</p>
+
+<figure class="wp-block-image alignwide">
+  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/ridgecrest-home-navigation-screenshot.png" alt="Phone view of Ridgecrest church navigation with the News page visible" loading="lazy" />
+  <figcaption>Use the main menu first. That is usually where the answer lives, which is inconvenient for people who prefer guesswork.</figcaption>
+</figure>
+
+<p>If you are already on the homepage, the quickest path is usually: homepage, main menu, News. If you are already on the News page, congratulations, you have won a round of basic navigation. Now read the actual update.</p>
+
+<h2>How to scan an update quickly</h2>
+
+<p>Most people do not need to read every line of a church update with a scholar’s commitment. They need the facts. Look for the parts that change what you do next.</p>
+
+<ul>
+  <li><strong>Date</strong> - When does it happen, and is there a deadline before it?</li>
+  <li><strong>Topic</strong> - What is this about in one sentence?</li>
+  <li><strong>Audience</strong> - Who actually needs this: everyone, parents, students, volunteers, or a specific class?</li>
+  <li><strong>Action needed</strong> - Do you need to RSVP, bring something, sign up, show up early, or do nothing at all?</li>
+</ul>
+
+<p>A practical scan takes less than a minute if you resist the urge to read every word twice. Start with the headline, then the first paragraph, then the date and contact details. If the post does not answer those four questions, keep reading until it does or until it proves it does not know what it is doing.</p>
+
+<p>Here is the working rule: if an update does not tell you when, who, and what next, it is incomplete from a visitor’s point of view. That is not your failure. It is the post’s.</p>
+
+<h3>Fast-read checklist</h3>
+
+<ol>
+  <li>Read the title.</li>
+  <li>Find the date.</li>
+  <li>Check who the update is for.</li>
+  <li>Look for a deadline or response request.</li>
+  <li>Put the event or reminder into your calendar if it matters to you.</li>
+</ol>
+
+<h2>Common types of posts you will see</h2>
+
+<p>The News page usually carries the same kinds of items, because churches are not that mysterious when they finally decide to write things down.</p>
+
+<h3>Service reminders</h3>
+
+<p>These are the simplest posts and the easiest to ignore. Do not. They often confirm service times, special schedules, or location changes. If the church is adjusting a service or class, this is where the update usually lands first.</p>
+
+<h3>Special events</h3>
+
+<p>Events can include fellowship meals, student activities, children’s ministry gatherings, church-wide celebrations, and seasonal services. If there is a deadline, ticket, RSVP, or sign-up, it belongs here. That is the part people forget and then pretend was never mentioned.</p>
+
+<h3>Ministry highlights</h3>
+
+<p>Sometimes the News page highlights what a ministry is doing, who it serves, or how to participate. This is useful because it tells you whether the update is just informational or actually inviting you to act. Most people confuse those two. They should not.</p>
+
+<h3>Prayer needs and follow-up notes</h3>
+
+<p>Not every update is about logistics. Some posts will point readers toward prayer, care, or encouragement. Those updates are different: read them carefully, respond appropriately, and do not treat them like event spam. That is not a good look.</p>
+
+<h2>How to respond to what you read</h2>
+
+<p>The whole point of reading a church update is to do something useful with it. Otherwise you are just collecting information the way some people collect receipts.</p>
+
+<ul>
+  <li><strong>RSVP when asked.</strong> If a post asks for a response, give one. That is not optional decor. It is part of the plan.</li>
+  <li><strong>Bring what the post names.</strong> If the update says bring food, supplies, forms, or a Bible, bring those things instead of improvising your way into inconvenience.</li>
+  <li><strong>Ask questions early.</strong> If the details are unclear, use the contact page before the event. Confusion gets cheaper when it is solved early.</li>
+  <li><strong>Share it with the right person.</strong> If the update affects your family, students, or ministry group, forward it before it disappears into the swamp of unread messages.</li>
+</ul>
+
+<p>When in doubt, use the <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> page or the direct <a href="https://ridgecrestchurch.com/contact.php">contact form</a>. Both land you in the same place emotionally: someone on the church side can answer the question instead of making you guess.</p>
+
+<p>If the update affects where to park, which entrance to use, or when to arrive, check the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> as well. A news item can tell you the plan, but a map tells you where to physically go. Oddly enough, that still matters.</p>
+
+<h2>Planning ahead: turn the news item into a calendar action</h2>
+
+<p>Reading an update is only half the job. The other half is making sure your future self does not quietly sabotage you. If something matters, put it on your personal calendar the same day you read it.</p>
+
+<figure class="wp-block-image alignwide">
+  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/events-calendar-page-screenshot.png" alt="Ridgecrest Events Calendar page screenshot with schedule and event sections" loading="lazy" />
+  <figcaption>Use the Events Calendar for dates. Use your own calendar for memory. Yes, both. Memory is a terrible project manager.</figcaption>
+</figure>
+
+<p>That can be as simple as copying the date, time, location, and one-line purpose into your phone calendar. If you use Google Calendar, Apple Calendar, or Outlook, each has its own help page for creating and managing events. The mechanics are not impressive, but neither is forgetting something you already meant to attend. For reference, see <a href="https://support.google.com/calendar/answer/72143?co=GENIE.Platform%3DDesktop&amp;hl=en&amp;utm_source=ridgecrestchurch.com">Google Calendar’s event creation help</a>, <a href="https://support.apple.com/guide/iphone/create-and-edit-events-in-calendar-iph3d110f84/ios?utm_source=ridgecrestchurch.com">Apple’s Calendar instructions for iPhone</a>, and <a href="https://support.microsoft.com/en-us/outlook/calendar/introduction-to-the-outlook-calendar?utm_source=ridgecrestchurch.com">Microsoft’s Outlook Calendar overview</a>.</p>
+
+<p>Use reminders for anything that has a deadline or requires preparation. If an event says “bring food,” “arrive early,” or “sign up by Thursday,” that is not optional trivia. It is the actual task.</p>
+
+<h2>How to stay in the loop between Sunday services</h2>
+
+<p>Do not wait until Sunday to discover the thing you were supposed to know on Tuesday. The News page and the Events Calendar work together. One explains what is happening. The other helps you see when it happens.</p>
+
+<ul>
+  <li>Check <a href="https://ridgecrestchurch.com/news.html">News</a> for announcements and changes.</li>
+  <li>Check <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for dates and upcoming gatherings.</li>
+  <li>Check <a href="https://ridgecrestchurch.com/">Home</a> if you want the main site entry point again because you clicked yourself into confusion.</li>
+</ul>
+
+<p>A decent habit is to review News once during the week and again before the weekend. That is enough to catch most updates without treating the church website like a full-time job.</p>
+
+<h2>Quick FAQ</h2>
+
+<h3>What if I missed it?</h3>
+
+<p>Start with the News post and the Events Calendar. If the update included a deadline or sign-up, use the contact page immediately to ask whether anything can still be done. Do not assume silence means the issue disappeared. It usually means you have not checked the right page yet.</p>
+
+<h3>Where do I find the details?</h3>
+
+<p>Use the News page first. If the post is brief, the next stop is the Events Calendar, then Contacts or Church Map if location or timing matters. If the information still feels thin after that, the problem is not you. The update needs more detail.</p>
+
+<h3>Who do I contact?</h3>
+
+<p>Use <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> for church staff information and <a href="https://ridgecrestchurch.com/contact.php">contact.php</a> if you want the direct contact path. If the matter is location-specific, add the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> to the mix so you are not asking a question that the map already answered.</p>
+
+<h2>Next steps</h2>
+
+<p>If you only remember three things, make them these: read the News page, check the Events Calendar, and contact the church when the update affects you directly. That is enough to stay informed without pretending every announcement will somehow reach you by psychic means.</p>
+
+<p>Start with the <a href="https://ridgecrestchurch.com/news.html">News</a> page, then move to the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for dates, and use <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> or the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> when you need a person, a place, or both. If you want more background on the church itself, the <a href="https://ridgecrestchurch.com/about.html">About Us</a> page is there too.</p>
+
+<p>That is the whole trick. Read the update, identify the action, and move it into your calendar before it evaporates. Basic process. Less drama.</p>
+

 succeeded in 1145ms:
Success: Updated custom field '_wp_attachment_image_alt'.
Success: Updated custom field '_wp_attachment_image_alt'.

codex
The post exists. I’m attaching the featured image now and checking the rendered content, because WordPress likes to surprise people by “helpfully” normalizing HTML if you do not verify it.
exec
/bin/bash -lc "wp post meta update 119 _thumbnail_id 79 && wp post get 119 --fields=ID,post_title,post_name,post_status,post_author,post_excerpt --format=json && printf '\\n---URL---\\n' && wp post url 119 && printf '\\n---CONTENT CHECK---\\n' && wp post get 119 --field=post_content | rg -n 'ridgecrest-home-navigation-screenshot|events-calendar-page-screenshot|news.html|events-calendar|contacts.html|contact.php|about.html'" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "wp post meta get 119 _thumbnail_id && printf '\\n---ATTACHMENT ALTS---\\n' && wp post meta get 79 _wp_attachment_image_alt && wp post meta get 86 _wp_attachment_image_alt" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 1776ms:
79

---ATTACHMENT ALTS---
Phone view of Ridgecrest site navigation with the News page visible
Ridgecrest Events Calendar page screenshot showing upcoming items

diff --git a//home/ubuntu/apps/ridgecrestchurch.com/.tmp/job-548-news-page-article.html b//home/ubuntu/apps/ridgecrestchurch.com/.tmp/job-548-news-page-article.html
new file mode 100644
index 0000000000000000000000000000000000000000..9fe6a8c43e6dedcc09ee0af01e09db5978ee6f60
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/.tmp/job-548-news-page-article.html
@@ -0,0 +1,161 @@
+<p><strong><em>The News page is where the church quietly tells you what matters next.</em></strong> Ignore it, and you will keep acting surprised when an event, reminder, or ministry update shows up after the fact. A news page is not decoration. It is the place where Ridgecrest Baptist Church puts the practical details that decide whether you arrive prepared or arrive confused.</p>
+
+<p>If you have ever asked yourself, “What changed?” “Who is this for?” “Do I need to do anything?” or “Why did nobody tell me sooner?”, that is exactly why this page exists. The answer is not mystery. It is usually a date, a topic, a small action item, and your responsibility to read the whole thing instead of the first sentence.</p>
+
+<p>This guide walks through how to use the Ridgecrest News page without pretending attention is automatic. You will learn what belongs there, where to find it, how to scan updates fast, how to turn an announcement into a calendar reminder, and when to use the Events Calendar, Contacts, or Church Map instead of hoping a vague memory will save you.</p>
+
+<p>For context, the Ridgecrest site also keeps related information on the <a href="https://ridgecrestchurch.com/about.html">About Us</a>, <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>, and <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> pages, so you do not have to guess which page is doing which job. That is the good news. The bad news is that you still have to read the page.</p>
+
+<h2>What the News page is for</h2>
+
+<p>The News page is where short, useful updates live. Not the full history of the church. Not a sermon archive. Not a place for vague encouragement dressed up as information. It is for the kinds of announcements that affect attendance, timing, preparation, or follow-up.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>What you see</th>
+      <th>What it means</th>
+      <th>What you should do</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Event announcement</td>
+      <td>A dated gathering, deadline, or special church activity</td>
+      <td>Check the time, location, and whether you need to respond</td>
+    </tr>
+    <tr>
+      <td>Ministry update</td>
+      <td>Information for Kids, Youth, volunteers, or a specific group</td>
+      <td>Read whether it applies to you or your household</td>
+    </tr>
+    <tr>
+      <td>Special notice</td>
+      <td>A schedule change, church-wide reminder, or urgent correction</td>
+      <td>Put it on your calendar and stop relying on memory</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>The point is simple: the News page is not there to entertain you. It is there to reduce avoidable confusion. Most church problems are not dramatic. They are just small timing errors repeated by too many people.</p>
+
+<h2>Where to find the News page in the main navigation</h2>
+
+<p>On the site, the News page is part of the main navigation. If you are on desktop, look across the top menu. If you are on a phone, open the navigation menu and look for the same label. No treasure hunt required. Just read the menu instead of tapping at random like a distracted raccoon.</p>
+
+<p>For the live page, use the <a href="https://ridgecrestchurch.com/news.html">News</a> link. The site also keeps a simple front-door version of the page at <a href="https://ridgecrestchurch.com/news/">/news/</a>, so the content is easy to reach either way.</p>
+
+<figure class="wp-block-image alignwide">
+  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/ridgecrest-home-navigation-screenshot.png" alt="Phone view of Ridgecrest church navigation with the News page visible" loading="lazy" />
+  <figcaption>Use the main menu first. That is usually where the answer lives, which is inconvenient for people who prefer guesswork.</figcaption>
+</figure>
+
+<p>If you are already on the homepage, the quickest path is usually: homepage, main menu, News. If you are already on the News page, congratulations, you have won a round of basic navigation. Now read the actual update.</p>
+
+<h2>How to scan an update quickly</h2>
+
+<p>Most people do not need to read every line of a church update with a scholar’s commitment. They need the facts. Look for the parts that change what you do next.</p>
+
+<ul>
+  <li><strong>Date</strong> - When does it happen, and is there a deadline before it?</li>
+  <li><strong>Topic</strong> - What is this about in one sentence?</li>
+  <li><strong>Audience</strong> - Who actually needs this: everyone, parents, students, volunteers, or a specific class?</li>
+  <li><strong>Action needed</strong> - Do you need to RSVP, bring something, sign up, show up early, or do nothing at all?</li>
+</ul>
+
+<p>A practical scan takes less than a minute if you resist the urge to read every word twice. Start with the headline, then the first paragraph, then the date and contact details. If the post does not answer those four questions, keep reading until it does or until it proves it does not know what it is doing.</p>
+
+<p>Here is the working rule: if an update does not tell you when, who, and what next, it is incomplete from a visitor’s point of view. That is not your failure. It is the post’s.</p>
+
+<h3>Fast-read checklist</h3>
+
+<ol>
+  <li>Read the title.</li>
+  <li>Find the date.</li>
+  <li>Check who the update is for.</li>
+  <li>Look for a deadline or response request.</li>
+  <li>Put the event or reminder into your calendar if it matters to you.</li>
+</ol>
+
+<h2>Common types of posts you will see</h2>
+
+<p>The News page usually carries the same kinds of items, because churches are not that mysterious when they finally decide to write things down.</p>
+
+<h3>Service reminders</h3>
+
+<p>These are the simplest posts and the easiest to ignore. Do not. They often confirm service times, special schedules, or location changes. If the church is adjusting a service or class, this is where the update usually lands first.</p>
+
+<h3>Special events</h3>
+
+<p>Events can include fellowship meals, student activities, children’s ministry gatherings, church-wide celebrations, and seasonal services. If there is a deadline, ticket, RSVP, or sign-up, it belongs here. That is the part people forget and then pretend was never mentioned.</p>
+
+<h3>Ministry highlights</h3>
+
+<p>Sometimes the News page highlights what a ministry is doing, who it serves, or how to participate. This is useful because it tells you whether the update is just informational or actually inviting you to act. Most people confuse those two. They should not.</p>
+
+<h3>Prayer needs and follow-up notes</h3>
+
+<p>Not every update is about logistics. Some posts will point readers toward prayer, care, or encouragement. Those updates are different: read them carefully, respond appropriately, and do not treat them like event spam. That is not a good look.</p>
+
+<h2>How to respond to what you read</h2>
+
+<p>The whole point of reading a church update is to do something useful with it. Otherwise you are just collecting information the way some people collect receipts.</p>
+
+<ul>
+  <li><strong>RSVP when asked.</strong> If a post asks for a response, give one. That is not optional decor. It is part of the plan.</li>
+  <li><strong>Bring what the post names.</strong> If the update says bring food, supplies, forms, or a Bible, bring those things instead of improvising your way into inconvenience.</li>
+  <li><strong>Ask questions early.</strong> If the details are unclear, use the contact page before the event. Confusion gets cheaper when it is solved early.</li>
+  <li><strong>Share it with the right person.</strong> If the update affects your family, students, or ministry group, forward it before it disappears into the swamp of unread messages.</li>
+</ul>
+
+<p>When in doubt, use the <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> page or the direct <a href="https://ridgecrestchurch.com/contact.php">contact form</a>. Both land you in the same place emotionally: someone on the church side can answer the question instead of making you guess.</p>
+
+<p>If the update affects where to park, which entrance to use, or when to arrive, check the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> as well. A news item can tell you the plan, but a map tells you where to physically go. Oddly enough, that still matters.</p>
+
+<h2>Planning ahead: turn the news item into a calendar action</h2>
+
+<p>Reading an update is only half the job. The other half is making sure your future self does not quietly sabotage you. If something matters, put it on your personal calendar the same day you read it.</p>
+
+<figure class="wp-block-image alignwide">
+  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/events-calendar-page-screenshot.png" alt="Ridgecrest Events Calendar page screenshot with schedule and event sections" loading="lazy" />
+  <figcaption>Use the Events Calendar for dates. Use your own calendar for memory. Yes, both. Memory is a terrible project manager.</figcaption>
+</figure>
+
+<p>That can be as simple as copying the date, time, location, and one-line purpose into your phone calendar. If you use Google Calendar, Apple Calendar, or Outlook, each has its own help page for creating and managing events. The mechanics are not impressive, but neither is forgetting something you already meant to attend. For reference, see <a href="https://support.google.com/calendar/answer/72143?co=GENIE.Platform%3DDesktop&amp;hl=en&amp;utm_source=ridgecrestchurch.com">Google Calendar’s event creation help</a>, <a href="https://support.apple.com/guide/iphone/create-and-edit-events-in-calendar-iph3d110f84/ios?utm_source=ridgecrestchurch.com">Apple’s Calendar instructions for iPhone</a>, and <a href="https://support.microsoft.com/en-us/outlook/calendar/introduction-to-the-outlook-calendar?utm_source=ridgecrestchurch.com">Microsoft’s Outlook Calendar overview</a>.</p>
+
+<p>Use reminders for anything that has a deadline or requires preparation. If an event says “bring food,” “arrive early,” or “sign up by Thursday,” that is not optional trivia. It is the actual task.</p>
+
+<h2>How to stay in the loop between Sunday services</h2>
+
+<p>Do not wait until Sunday to discover the thing you were supposed to know on Tuesday. The News page and the Events Calendar work together. One explains what is happening. The other helps you see when it happens.</p>
+
+<ul>
+  <li>Check <a href="https://ridgecrestchurch.com/news.html">News</a> for announcements and changes.</li>
+  <li>Check <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for dates and upcoming gatherings.</li>
+  <li>Check <a href="https://ridgecrestchurch.com/">Home</a> if you want the main site entry point again because you clicked yourself into confusion.</li>
+</ul>
+
+<p>A decent habit is to review News once during the week and again before the weekend. That is enough to catch most updates without treating the church website like a full-time job.</p>
+
+<h2>Quick FAQ</h2>
+
+<h3>What if I missed it?</h3>
+
+<p>Start with the News post and the Events Calendar. If the update included a deadline or sign-up, use the contact page immediately to ask whether anything can still be done. Do not assume silence means the issue disappeared. It usually means you have not checked the right page yet.</p>
+
+<h3>Where do I find the details?</h3>
+
+<p>Use the News page first. If the post is brief, the next stop is the Events Calendar, then Contacts or Church Map if location or timing matters. If the information still feels thin after that, the problem is not you. The update needs more detail.</p>
+
+<h3>Who do I contact?</h3>
+
+<p>Use <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> for church staff information and <a href="https://ridgecrestchurch.com/contact.php">contact.php</a> if you want the direct contact path. If the matter is location-specific, add the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> to the mix so you are not asking a question that the map already answered.</p>
+
+<h2>Next steps</h2>
+
+<p>If you only remember three things, make them these: read the News page, check the Events Calendar, and contact the church when the update affects you directly. That is enough to stay informed without pretending every announcement will somehow reach you by psychic means.</p>
+
+<p>Start with the <a href="https://ridgecrestchurch.com/news.html">News</a> page, then move to the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for dates, and use <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> or the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> when you need a person, a place, or both. If you want more background on the church itself, the <a href="https://ridgecrestchurch.com/about.html">About Us</a> page is there too.</p>
+
+<p>That is the whole trick. Read the update, identify the action, and move it into your calendar before it evaporates. Basic process. Less drama.</p>
+

 succeeded in 2279ms:
Success: Updated custom field '_thumbnail_id'.
{"ID":119,"post_author":"9","post_title":"How to Read and Use Ridgecrest Baptist Church\u2019s News Page (So You Never Miss an Update)","post_excerpt":"A practical guide to navigating Ridgecrest Baptist Church\u2019s News page so you can track announcements, plan ahead, and act on updates without missing the useful part.","post_status":"publish","post_name":"how-to-use-news-page-ridgecrest"}

---URL---
https://ridgecrestchurch.com/how-to-use-news-page-ridgecrest/

---CONTENT CHECK---
7:<p>For context, the Ridgecrest site also keeps related information on the <a href="https://ridgecrestchurch.com/about.html">About Us</a>, <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>, and <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> pages, so you do not have to guess which page is doing which job. That is the good news. The bad news is that you still have to read the page.</p>
46:<p>For the live page, use the <a href="https://ridgecrestchurch.com/news.html">News</a> link. The site also keeps a simple front-door version of the page at <a href="https://ridgecrestchurch.com/news/">/news/</a>, so the content is easy to reach either way.</p>
49:  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/ridgecrest-home-navigation-screenshot.png" alt="Phone view of Ridgecrest church navigation with the News page visible" loading="lazy" />
111:<p>When in doubt, use the <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> page or the direct <a href="https://ridgecrestchurch.com/contact.php">contact form</a>. Both land you in the same place emotionally: someone on the church side can answer the question instead of making you guess.</p>
120:  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/events-calendar-page-screenshot.png" alt="Ridgecrest Events Calendar page screenshot with schedule and event sections" loading="lazy" />
133:  <li>Check <a href="https://ridgecrestchurch.com/news.html">News</a> for announcements and changes.</li>
134:  <li>Check <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for dates and upcoming gatherings.</li>
152:<p>Use <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> for church staff information and <a href="https://ridgecrestchurch.com/contact.php">contact.php</a> if you want the direct contact path. If the matter is location-specific, add the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> to the mix so you are not asking a question that the map already answered.</p>
158:<p>Start with the <a href="https://ridgecrestchurch.com/news.html">News</a> page, then move to the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for dates, and use <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> or the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> when you need a person, a place, or both. If you want more background on the church itself, the <a href="https://ridgecrestchurch.com/about.html">About Us</a> page is there too.</p>

codex
The post is live, the featured image is set, and both inline image URLs survived in the stored content. I’m doing the final web-facing checks now: the published URL, the blog index, and whether the new post is actually discoverable from `/blog/` instead of just existing in the database like a rumor.
exec
/bin/bash -lc "curl -I -L --max-redirs 5 --silent --show-error https://ridgecrestchurch.com/how-to-use-news-page-ridgecrest/ | sed -n '1,12p'" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "curl -L --max-redirs 5 --silent --show-error https://ridgecrestchurch.com/blog/ | rg -n 'How to Read and Use Ridgecrest Baptist Church|how-to-use-news-page-ridgecrest|Felix Rowan|News page'" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc 'wp option get page_for_posts && wp post get 23 --fields=ID,post_title,post_name,post_status --format=json && wp post get 119 --fields=ID,post_title,post_status,post_author --format=json' in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 484ms:
HTTP/2 200 
date: Fri, 26 Jun 2026 19:02:17 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/119>; rel="alternate"; title="JSON"; type="application/json", <https://ridgecrestchurch.com/?p=119>; 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=BJbvjCUuNzPxDJM9HZUm%2Fm9E0ZcZCtM4GP7kA91KW4IqbL4GX%2FidnuxahsDxKVtYLulRCf1Z8KU0V3j8vCziS9qcI9ylpOXE%2BYuycxz9e7uyJ4OXA8ufqg%2FNWoZW%2B6ARSAm6NEevPw%3D%3D"}]}
nel: {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
cf-ray: a11e77271ef5cbfe-WAW
alt-svc: h3=":443"; ma=86400


 succeeded in 569ms:
414:			<header class="entry-header">	<h2 class="entry-title" itemprop="headline"><a href="https://ridgecrestchurch.com/how-to-use-news-page-ridgecrest/" rel="bookmark">How to Read and Use Ridgecrest Baptist Church’s News Page (So You Never Miss an Update)</a></h2>
417:	<span class="entry-author" itemprop="author" itemscope="itemscope" itemtype="http://schema.org/Person">by <a href="https://ridgecrestchurch.com/author/felix-rowan/" title="Posts by Felix Rowan" rel="author" class="url fn n" itemprop="url"><span itemprop="name">Felix Rowan</span></a></span>	
420:<a href="https://ridgecrestchurch.com/how-to-use-news-page-ridgecrest/" title="How to Read and Use Ridgecrest Baptist Church’s News Page (So You Never Miss an Update)"><img data-src="https://ridgecrestchurch.com/wp-content/uploads/imports/ridgecrest-home-navigation-screenshot.png" class="wp-post-image lazyload" alt="Phone view of Ridgecrest site navigation with the News page visible" decoding="async" itemprop="image" src="data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==" style="--smush-placeholder-width: 1400px; --smush-placeholder-aspect-ratio: 1400/1050;" /></a><p>A practical guide to navigating Ridgecrest Baptist Church’s News page so you can track announcements, plan ahead, and act on updates without missing the useful part.</p>

diff --git a//home/ubuntu/apps/ridgecrestchurch.com/.tmp/job-548-news-page-article.html b//home/ubuntu/apps/ridgecrestchurch.com/.tmp/job-548-news-page-article.html
new file mode 100644
index 0000000000000000000000000000000000000000..9fe6a8c43e6dedcc09ee0af01e09db5978ee6f60
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/.tmp/job-548-news-page-article.html
@@ -0,0 +1,161 @@
+<p><strong><em>The News page is where the church quietly tells you what matters next.</em></strong> Ignore it, and you will keep acting surprised when an event, reminder, or ministry update shows up after the fact. A news page is not decoration. It is the place where Ridgecrest Baptist Church puts the practical details that decide whether you arrive prepared or arrive confused.</p>
+
+<p>If you have ever asked yourself, “What changed?” “Who is this for?” “Do I need to do anything?” or “Why did nobody tell me sooner?”, that is exactly why this page exists. The answer is not mystery. It is usually a date, a topic, a small action item, and your responsibility to read the whole thing instead of the first sentence.</p>
+
+<p>This guide walks through how to use the Ridgecrest News page without pretending attention is automatic. You will learn what belongs there, where to find it, how to scan updates fast, how to turn an announcement into a calendar reminder, and when to use the Events Calendar, Contacts, or Church Map instead of hoping a vague memory will save you.</p>
+
+<p>For context, the Ridgecrest site also keeps related information on the <a href="https://ridgecrestchurch.com/about.html">About Us</a>, <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>, and <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> pages, so you do not have to guess which page is doing which job. That is the good news. The bad news is that you still have to read the page.</p>
+
+<h2>What the News page is for</h2>
+
+<p>The News page is where short, useful updates live. Not the full history of the church. Not a sermon archive. Not a place for vague encouragement dressed up as information. It is for the kinds of announcements that affect attendance, timing, preparation, or follow-up.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>What you see</th>
+      <th>What it means</th>
+      <th>What you should do</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Event announcement</td>
+      <td>A dated gathering, deadline, or special church activity</td>
+      <td>Check the time, location, and whether you need to respond</td>
+    </tr>
+    <tr>
+      <td>Ministry update</td>
+      <td>Information for Kids, Youth, volunteers, or a specific group</td>
+      <td>Read whether it applies to you or your household</td>
+    </tr>
+    <tr>
+      <td>Special notice</td>
+      <td>A schedule change, church-wide reminder, or urgent correction</td>
+      <td>Put it on your calendar and stop relying on memory</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>The point is simple: the News page is not there to entertain you. It is there to reduce avoidable confusion. Most church problems are not dramatic. They are just small timing errors repeated by too many people.</p>
+
+<h2>Where to find the News page in the main navigation</h2>
+
+<p>On the site, the News page is part of the main navigation. If you are on desktop, look across the top menu. If you are on a phone, open the navigation menu and look for the same label. No treasure hunt required. Just read the menu instead of tapping at random like a distracted raccoon.</p>
+
+<p>For the live page, use the <a href="https://ridgecrestchurch.com/news.html">News</a> link. The site also keeps a simple front-door version of the page at <a href="https://ridgecrestchurch.com/news/">/news/</a>, so the content is easy to reach either way.</p>
+
+<figure class="wp-block-image alignwide">
+  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/ridgecrest-home-navigation-screenshot.png" alt="Phone view of Ridgecrest church navigation with the News page visible" loading="lazy" />
+  <figcaption>Use the main menu first. That is usually where the answer lives, which is inconvenient for people who prefer guesswork.</figcaption>
+</figure>
+
+<p>If you are already on the homepage, the quickest path is usually: homepage, main menu, News. If you are already on the News page, congratulations, you have won a round of basic navigation. Now read the actual update.</p>
+
+<h2>How to scan an update quickly</h2>
+
+<p>Most people do not need to read every line of a church update with a scholar’s commitment. They need the facts. Look for the parts that change what you do next.</p>
+
+<ul>
+  <li><strong>Date</strong> - When does it happen, and is there a deadline before it?</li>
+  <li><strong>Topic</strong> - What is this about in one sentence?</li>
+  <li><strong>Audience</strong> - Who actually needs this: everyone, parents, students, volunteers, or a specific class?</li>
+  <li><strong>Action needed</strong> - Do you need to RSVP, bring something, sign up, show up early, or do nothing at all?</li>
+</ul>
+
+<p>A practical scan takes less than a minute if you resist the urge to read every word twice. Start with the headline, then the first paragraph, then the date and contact details. If the post does not answer those four questions, keep reading until it does or until it proves it does not know what it is doing.</p>
+
+<p>Here is the working rule: if an update does not tell you when, who, and what next, it is incomplete from a visitor’s point of view. That is not your failure. It is the post’s.</p>
+
+<h3>Fast-read checklist</h3>
+
+<ol>
+  <li>Read the title.</li>
+  <li>Find the date.</li>
+  <li>Check who the update is for.</li>
+  <li>Look for a deadline or response request.</li>
+  <li>Put the event or reminder into your calendar if it matters to you.</li>
+</ol>
+
+<h2>Common types of posts you will see</h2>
+
+<p>The News page usually carries the same kinds of items, because churches are not that mysterious when they finally decide to write things down.</p>
+
+<h3>Service reminders</h3>
+
+<p>These are the simplest posts and the easiest to ignore. Do not. They often confirm service times, special schedules, or location changes. If the church is adjusting a service or class, this is where the update usually lands first.</p>
+
+<h3>Special events</h3>
+
+<p>Events can include fellowship meals, student activities, children’s ministry gatherings, church-wide celebrations, and seasonal services. If there is a deadline, ticket, RSVP, or sign-up, it belongs here. That is the part people forget and then pretend was never mentioned.</p>
+
+<h3>Ministry highlights</h3>
+
+<p>Sometimes the News page highlights what a ministry is doing, who it serves, or how to participate. This is useful because it tells you whether the update is just informational or actually inviting you to act. Most people confuse those two. They should not.</p>
+
+<h3>Prayer needs and follow-up notes</h3>
+
+<p>Not every update is about logistics. Some posts will point readers toward prayer, care, or encouragement. Those updates are different: read them carefully, respond appropriately, and do not treat them like event spam. That is not a good look.</p>
+
+<h2>How to respond to what you read</h2>
+
+<p>The whole point of reading a church update is to do something useful with it. Otherwise you are just collecting information the way some people collect receipts.</p>
+
+<ul>
+  <li><strong>RSVP when asked.</strong> If a post asks for a response, give one. That is not optional decor. It is part of the plan.</li>
+  <li><strong>Bring what the post names.</strong> If the update says bring food, supplies, forms, or a Bible, bring those things instead of improvising your way into inconvenience.</li>
+  <li><strong>Ask questions early.</strong> If the details are unclear, use the contact page before the event. Confusion gets cheaper when it is solved early.</li>
+  <li><strong>Share it with the right person.</strong> If the update affects your family, students, or ministry group, forward it before it disappears into the swamp of unread messages.</li>
+</ul>
+
+<p>When in doubt, use the <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> page or the direct <a href="https://ridgecrestchurch.com/contact.php">contact form</a>. Both land you in the same place emotionally: someone on the church side can answer the question instead of making you guess.</p>
+
+<p>If the update affects where to park, which entrance to use, or when to arrive, check the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> as well. A news item can tell you the plan, but a map tells you where to physically go. Oddly enough, that still matters.</p>
+
+<h2>Planning ahead: turn the news item into a calendar action</h2>
+
+<p>Reading an update is only half the job. The other half is making sure your future self does not quietly sabotage you. If something matters, put it on your personal calendar the same day you read it.</p>
+
+<figure class="wp-block-image alignwide">
+  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/events-calendar-page-screenshot.png" alt="Ridgecrest Events Calendar page screenshot with schedule and event sections" loading="lazy" />
+  <figcaption>Use the Events Calendar for dates. Use your own calendar for memory. Yes, both. Memory is a terrible project manager.</figcaption>
+</figure>
+
+<p>That can be as simple as copying the date, time, location, and one-line purpose into your phone calendar. If you use Google Calendar, Apple Calendar, or Outlook, each has its own help page for creating and managing events. The mechanics are not impressive, but neither is forgetting something you already meant to attend. For reference, see <a href="https://support.google.com/calendar/answer/72143?co=GENIE.Platform%3DDesktop&amp;hl=en&amp;utm_source=ridgecrestchurch.com">Google Calendar’s event creation help</a>, <a href="https://support.apple.com/guide/iphone/create-and-edit-events-in-calendar-iph3d110f84/ios?utm_source=ridgecrestchurch.com">Apple’s Calendar instructions for iPhone</a>, and <a href="https://support.microsoft.com/en-us/outlook/calendar/introduction-to-the-outlook-calendar?utm_source=ridgecrestchurch.com">Microsoft’s Outlook Calendar overview</a>.</p>
+
+<p>Use reminders for anything that has a deadline or requires preparation. If an event says “bring food,” “arrive early,” or “sign up by Thursday,” that is not optional trivia. It is the actual task.</p>
+
+<h2>How to stay in the loop between Sunday services</h2>
+
+<p>Do not wait until Sunday to discover the thing you were supposed to know on Tuesday. The News page and the Events Calendar work together. One explains what is happening. The other helps you see when it happens.</p>
+
+<ul>
+  <li>Check <a href="https://ridgecrestchurch.com/news.html">News</a> for announcements and changes.</li>
+  <li>Check <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for dates and upcoming gatherings.</li>
+  <li>Check <a href="https://ridgecrestchurch.com/">Home</a> if you want the main site entry point again because you clicked yourself into confusion.</li>
+</ul>
+
+<p>A decent habit is to review News once during the week and again before the weekend. That is enough to catch most updates without treating the church website like a full-time job.</p>
+
+<h2>Quick FAQ</h2>
+
+<h3>What if I missed it?</h3>
+
+<p>Start with the News post and the Events Calendar. If the update included a deadline or sign-up, use the contact page immediately to ask whether anything can still be done. Do not assume silence means the issue disappeared. It usually means you have not checked the right page yet.</p>
+
+<h3>Where do I find the details?</h3>
+
+<p>Use the News page first. If the post is brief, the next stop is the Events Calendar, then Contacts or Church Map if location or timing matters. If the information still feels thin after that, the problem is not you. The update needs more detail.</p>
+
+<h3>Who do I contact?</h3>
+
+<p>Use <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> for church staff information and <a href="https://ridgecrestchurch.com/contact.php">contact.php</a> if you want the direct contact path. If the matter is location-specific, add the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> to the mix so you are not asking a question that the map already answered.</p>
+
+<h2>Next steps</h2>
+
+<p>If you only remember three things, make them these: read the News page, check the Events Calendar, and contact the church when the update affects you directly. That is enough to stay informed without pretending every announcement will somehow reach you by psychic means.</p>
+
+<p>Start with the <a href="https://ridgecrestchurch.com/news.html">News</a> page, then move to the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for dates, and use <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> or the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> when you need a person, a place, or both. If you want more background on the church itself, the <a href="https://ridgecrestchurch.com/about.html">About Us</a> page is there too.</p>
+
+<p>That is the whole trick. Read the update, identify the action, and move it into your calendar before it evaporates. Basic process. Less drama.</p>
+

 succeeded in 1743ms:
23
{"ID":23,"post_title":"Blog","post_status":"publish","post_name":"blog"}
{"ID":119,"post_author":"9","post_title":"How to Read and Use Ridgecrest Baptist Church\u2019s News Page (So You Never Miss an Update)","post_status":"publish"}

codex
The blog index is surfacing the post correctly, and the author archive is in place. I’m doing one last content render check to make sure the inline images actually appear in the public HTML and didn’t get reduced to some theme-specific lazy-load placeholder nonsense.
exec
/bin/bash -lc "curl -L --silent --show-error https://ridgecrestchurch.com/how-to-use-news-page-ridgecrest/ | rg -n -C 2 'ridgecrest-home-navigation-screenshot|events-calendar-page-screenshot|Phone view of Ridgecrest site navigation|Ridgecrest Events Calendar page screenshot'" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "curl -L --silent --show-error https://ridgecrestchurch.com/blog/ | rg -n 'how-to-use-news-page-ridgecrest|Felix Rowan'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 459ms:
19-	<meta property="og:site_name" content="Ridgecrest Baptist Church" />
20-	<meta property="article:published_time" content="2026-06-26T19:02:07+00:00" />
21:	<meta property="og:image" content="https://ridgecrestchurch.com/wp-content/uploads/imports/ridgecrest-home-navigation-screenshot.png" />
22-	<meta name="author" content="Felix Rowan" />
23-	<meta name="twitter:card" content="summary_large_image" />
--
26-	<meta name="twitter:label2" content="Est. reading time" />
27-	<meta name="twitter:data2" content="9 minutes" />
28:	<script type="application/ld+json" class="yoast-schema-graph">{"@context":"https://schema.org","@graph":[{"@type":"Article","@id":"https://ridgecrestchurch.com/how-to-use-news-page-ridgecrest/#article","isPartOf":{"@id":"https://ridgecrestchurch.com/how-to-use-news-page-ridgecrest/"},"author":{"name":"Felix Rowan","@id":"https://ridgecrestchurch.com/#/schema/person/f9b3f9940ab61b09cfd61e1a2b819151"},"headline":"How to Read and Use Ridgecrest Baptist Church’s News Page (So You Never Miss an Update)","datePublished":"2026-06-26T19:02:07+00:00","mainEntityOfPage":{"@id":"https://ridgecrestchurch.com/how-to-use-news-page-ridgecrest/"},"wordCount":1744,"publisher":{"@id":"https://ridgecrestchurch.com/#organization"},"image":{"@id":"https://ridgecrestchurch.com/how-to-use-news-page-ridgecrest/#primaryimage"},"thumbnailUrl":"https://ridgecrestchurch.com/wp-content/uploads/imports/ridgecrest-home-navigation-screenshot.png","inLanguage":"en-US"},{"@type":"WebPage","@id":"https://ridgecrestchurch.com/how-to-use-news-page-ridgecrest/","url":"https://ridgecrestchurch.com/how-to-use-news-page-ridgecrest/","name":"How to Read and Use Ridgecrest Baptist Church’s News Page (So You Never Miss an Update) - Ridgecrest Baptist Church","isPartOf":{"@id":"https://ridgecrestchurch.com/#website"},"primaryImageOfPage":{"@id":"https://ridgecrestchurch.com/how-to-use-news-page-ridgecrest/#primaryimage"},"image":{"@id":"https://ridgecrestchurch.com/how-to-use-news-page-ridgecrest/#primaryimage"},"thumbnailUrl":"https://ridgecrestchurch.com/wp-content/uploads/imports/ridgecrest-home-navigation-screenshot.png","datePublished":"2026-06-26T19:02:07+00:00","breadcrumb":{"@id":"https://ridgecrestchurch.com/how-to-use-news-page-ridgecrest/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https://ridgecrestchurch.com/how-to-use-news-page-ridgecrest/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https://ridgecrestchurch.com/how-to-use-news-page-ridgecrest/#primaryimage","url":"https://ridgecrestchurch.com/wp-content/uploads/imports/ridgecrest-home-navigation-screenshot.png","contentUrl":"https://ridgecrestchurch.com/wp-content/uploads/imports/ridgecrest-home-navigation-screenshot.png","caption":"Phone view of Ridgecrest site navigation with the News page visible"},{"@type":"BreadcrumbList","@id":"https://ridgecrestchurch.com/how-to-use-news-page-ridgecrest/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://ridgecrestchurch.com/"},{"@type":"ListItem","position":2,"name":"Blog","item":"https://ridgecrestchurch.com/blog/"},{"@type":"ListItem","position":3,"name":"How to Read and Use Ridgecrest Baptist Church’s News Page (So You Never Miss an Update)"}]},{"@type":"WebSite","@id":"https://ridgecrestchurch.com/#website","url":"https://ridgecrestchurch.com/","name":"Ridgecrest Baptist Church","description":"A welcoming family church in Blanchard, Oklahoma","publisher":{"@id":"https://ridgecrestchurch.com/#organization"},"alternateName":"Ridgecrest Church","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://ridgecrestchurch.com/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https://ridgecrestchurch.com/#organization","name":"Ridgecrest Baptist Church","url":"https://ridgecrestchurch.com/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https://ridgecrestchurch.com/#/schema/logo/image/","url":"https://ridgecrestchurch.com/wp-content/uploads/imports/logo.gif","contentUrl":"https://ridgecrestchurch.com/wp-content/uploads/imports/logo.gif","width":null,"height":null,"caption":"Ridgecrest Baptist Church"},"image":{"@id":"https://ridgecrestchurch.com/#/schema/logo/image/"}},{"@type":"Person","@id":"https://ridgecrestchurch.com/#/schema/person/f9b3f9940ab61b09cfd61e1a2b819151","name":"Felix Rowan","url":"https://ridgecrestchurch.com/author/felix-rowan/"}]}</script>
29-	<!-- / Yoast SEO Premium plugin. -->
30-
--
459-<p>For the live page, use the <a href="https://ridgecrestchurch.com/news.html">News</a> link. The site also keeps a simple front-door version of the page at <a href="https://ridgecrestchurch.com/news/">/news/</a>, so the content is easy to reach either way.</p>
460-<figure class="wp-block-image alignwide">
461:  <img decoding="async" data-src="https://ridgecrestchurch.com/wp-content/uploads/imports/ridgecrest-home-navigation-screenshot.png" alt="Phone view of Ridgecrest church navigation with the News page visible" src="data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==" class="lazyload" style="--smush-placeholder-width: 1400px; --smush-placeholder-aspect-ratio: 1400/1050;" /><figcaption>Use the main menu first. That is usually where the answer lives, which is inconvenient for people who prefer guesswork.</figcaption></figure>
462-<p>If you are already on the homepage, the quickest path is usually: homepage, main menu, News. If you are already on the News page, congratulations, you have won a round of basic navigation. Now read the actual update.</p>
463-<h2>How to scan an update quickly</h2>
--
502-<p>Reading an update is only half the job. The other half is making sure your future self does not quietly sabotage you. If something matters, put it on your personal calendar the same day you read it.</p>
503-<figure class="wp-block-image alignwide">
504:  <img decoding="async" data-src="https://ridgecrestchurch.com/wp-content/uploads/imports/events-calendar-page-screenshot.png" alt="Ridgecrest Events Calendar page screenshot with schedule and event sections" src="data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==" class="lazyload" style="--smush-placeholder-width: 1280px; --smush-placeholder-aspect-ratio: 1280/2207;" /><figcaption>Use the Events Calendar for dates. Use your own calendar for memory. Yes, both. Memory is a terrible project manager.</figcaption></figure>
505-<p>That can be as simple as copying the date, time, location, and one-line purpose into your phone calendar. If you use Google Calendar, Apple Calendar, or Outlook, each has its own help page for creating and managing events. The mechanics are not impressive, but neither is forgetting something you already meant to attend. For reference, see <a href="https://support.google.com/calendar/answer/72143?co=GENIE.Platform%3DDesktop&amp;hl=en&amp;utm_source=ridgecrestchurch.com">Google Calendar’s event creation help</a>, <a href="https://support.apple.com/guide/iphone/create-and-edit-events-in-calendar-iph3d110f84/ios?utm_source=ridgecrestchurch.com">Apple’s Calendar instructions for iPhone</a>, and <a href="https://support.microsoft.com/en-us/outlook/calendar/introduction-to-the-outlook-calendar?utm_source=ridgecrestchurch.com">Microsoft’s Outlook Calendar overview</a>.</p>
506-<p>Use reminders for anything that has a deadline or requires preparation. If an event says “bring food,” “arrive early,” or “sign up by Thursday,” that is not optional trivia. It is the actual task.</p>

diff --git a//home/ubuntu/apps/ridgecrestchurch.com/.tmp/job-548-news-page-article.html b//home/ubuntu/apps/ridgecrestchurch.com/.tmp/job-548-news-page-article.html
new file mode 100644
index 0000000000000000000000000000000000000000..9fe6a8c43e6dedcc09ee0af01e09db5978ee6f60
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/.tmp/job-548-news-page-article.html
@@ -0,0 +1,161 @@
+<p><strong><em>The News page is where the church quietly tells you what matters next.</em></strong> Ignore it, and you will keep acting surprised when an event, reminder, or ministry update shows up after the fact. A news page is not decoration. It is the place where Ridgecrest Baptist Church puts the practical details that decide whether you arrive prepared or arrive confused.</p>
+
+<p>If you have ever asked yourself, “What changed?” “Who is this for?” “Do I need to do anything?” or “Why did nobody tell me sooner?”, that is exactly why this page exists. The answer is not mystery. It is usually a date, a topic, a small action item, and your responsibility to read the whole thing instead of the first sentence.</p>
+
+<p>This guide walks through how to use the Ridgecrest News page without pretending attention is automatic. You will learn what belongs there, where to find it, how to scan updates fast, how to turn an announcement into a calendar reminder, and when to use the Events Calendar, Contacts, or Church Map instead of hoping a vague memory will save you.</p>
+
+<p>For context, the Ridgecrest site also keeps related information on the <a href="https://ridgecrestchurch.com/about.html">About Us</a>, <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>, and <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> pages, so you do not have to guess which page is doing which job. That is the good news. The bad news is that you still have to read the page.</p>
+
+<h2>What the News page is for</h2>
+
+<p>The News page is where short, useful updates live. Not the full history of the church. Not a sermon archive. Not a place for vague encouragement dressed up as information. It is for the kinds of announcements that affect attendance, timing, preparation, or follow-up.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>What you see</th>
+      <th>What it means</th>
+      <th>What you should do</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Event announcement</td>
+      <td>A dated gathering, deadline, or special church activity</td>
+      <td>Check the time, location, and whether you need to respond</td>
+    </tr>
+    <tr>
+      <td>Ministry update</td>
+      <td>Information for Kids, Youth, volunteers, or a specific group</td>
+      <td>Read whether it applies to you or your household</td>
+    </tr>
+    <tr>
+      <td>Special notice</td>
+      <td>A schedule change, church-wide reminder, or urgent correction</td>
+      <td>Put it on your calendar and stop relying on memory</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>The point is simple: the News page is not there to entertain you. It is there to reduce avoidable confusion. Most church problems are not dramatic. They are just small timing errors repeated by too many people.</p>
+
+<h2>Where to find the News page in the main navigation</h2>
+
+<p>On the site, the News page is part of the main navigation. If you are on desktop, look across the top menu. If you are on a phone, open the navigation menu and look for the same label. No treasure hunt required. Just read the menu instead of tapping at random like a distracted raccoon.</p>
+
+<p>For the live page, use the <a href="https://ridgecrestchurch.com/news.html">News</a> link. The site also keeps a simple front-door version of the page at <a href="https://ridgecrestchurch.com/news/">/news/</a>, so the content is easy to reach either way.</p>
+
+<figure class="wp-block-image alignwide">
+  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/ridgecrest-home-navigation-screenshot.png" alt="Phone view of Ridgecrest church navigation with the News page visible" loading="lazy" />
+  <figcaption>Use the main menu first. That is usually where the answer lives, which is inconvenient for people who prefer guesswork.</figcaption>
+</figure>
+
+<p>If you are already on the homepage, the quickest path is usually: homepage, main menu, News. If you are already on the News page, congratulations, you have won a round of basic navigation. Now read the actual update.</p>
+
+<h2>How to scan an update quickly</h2>
+
+<p>Most people do not need to read every line of a church update with a scholar’s commitment. They need the facts. Look for the parts that change what you do next.</p>
+
+<ul>
+  <li><strong>Date</strong> - When does it happen, and is there a deadline before it?</li>
+  <li><strong>Topic</strong> - What is this about in one sentence?</li>
+  <li><strong>Audience</strong> - Who actually needs this: everyone, parents, students, volunteers, or a specific class?</li>
+  <li><strong>Action needed</strong> - Do you need to RSVP, bring something, sign up, show up early, or do nothing at all?</li>
+</ul>
+
+<p>A practical scan takes less than a minute if you resist the urge to read every word twice. Start with the headline, then the first paragraph, then the date and contact details. If the post does not answer those four questions, keep reading until it does or until it proves it does not know what it is doing.</p>
+
+<p>Here is the working rule: if an update does not tell you when, who, and what next, it is incomplete from a visitor’s point of view. That is not your failure. It is the post’s.</p>
+
+<h3>Fast-read checklist</h3>
+
+<ol>
+  <li>Read the title.</li>
+  <li>Find the date.</li>
+  <li>Check who the update is for.</li>
+  <li>Look for a deadline or response request.</li>
+  <li>Put the event or reminder into your calendar if it matters to you.</li>
+</ol>
+
+<h2>Common types of posts you will see</h2>
+
+<p>The News page usually carries the same kinds of items, because churches are not that mysterious when they finally decide to write things down.</p>
+
+<h3>Service reminders</h3>
+
+<p>These are the simplest posts and the easiest to ignore. Do not. They often confirm service times, special schedules, or location changes. If the church is adjusting a service or class, this is where the update usually lands first.</p>
+
+<h3>Special events</h3>
+
+<p>Events can include fellowship meals, student activities, children’s ministry gatherings, church-wide celebrations, and seasonal services. If there is a deadline, ticket, RSVP, or sign-up, it belongs here. That is the part people forget and then pretend was never mentioned.</p>
+
+<h3>Ministry highlights</h3>
+
+<p>Sometimes the News page highlights what a ministry is doing, who it serves, or how to participate. This is useful because it tells you whether the update is just informational or actually inviting you to act. Most people confuse those two. They should not.</p>
+
+<h3>Prayer needs and follow-up notes</h3>
+
+<p>Not every update is about logistics. Some posts will point readers toward prayer, care, or encouragement. Those updates are different: read them carefully, respond appropriately, and do not treat them like event spam. That is not a good look.</p>
+
+<h2>How to respond to what you read</h2>
+
+<p>The whole point of reading a church update is to do something useful with it. Otherwise you are just collecting information the way some people collect receipts.</p>
+
+<ul>
+  <li><strong>RSVP when asked.</strong> If a post asks for a response, give one. That is not optional decor. It is part of the plan.</li>
+  <li><strong>Bring what the post names.</strong> If the update says bring food, supplies, forms, or a Bible, bring those things instead of improvising your way into inconvenience.</li>
+  <li><strong>Ask questions early.</strong> If the details are unclear, use the contact page before the event. Confusion gets cheaper when it is solved early.</li>
+  <li><strong>Share it with the right person.</strong> If the update affects your family, students, or ministry group, forward it before it disappears into the swamp of unread messages.</li>
+</ul>
+
+<p>When in doubt, use the <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> page or the direct <a href="https://ridgecrestchurch.com/contact.php">contact form</a>. Both land you in the same place emotionally: someone on the church side can answer the question instead of making you guess.</p>
+
+<p>If the update affects where to park, which entrance to use, or when to arrive, check the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> as well. A news item can tell you the plan, but a map tells you where to physically go. Oddly enough, that still matters.</p>
+
+<h2>Planning ahead: turn the news item into a calendar action</h2>
+
+<p>Reading an update is only half the job. The other half is making sure your future self does not quietly sabotage you. If something matters, put it on your personal calendar the same day you read it.</p>
+
+<figure class="wp-block-image alignwide">
+  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/events-calendar-page-screenshot.png" alt="Ridgecrest Events Calendar page screenshot with schedule and event sections" loading="lazy" />
+  <figcaption>Use the Events Calendar for dates. Use your own calendar for memory. Yes, both. Memory is a terrible project manager.</figcaption>
+</figure>
+
+<p>That can be as simple as copying the date, time, location, and one-line purpose into your phone calendar. If you use Google Calendar, Apple Calendar, or Outlook, each has its own help page for creating and managing events. The mechanics are not impressive, but neither is forgetting something you already meant to attend. For reference, see <a href="https://support.google.com/calendar/answer/72143?co=GENIE.Platform%3DDesktop&amp;hl=en&amp;utm_source=ridgecrestchurch.com">Google Calendar’s event creation help</a>, <a href="https://support.apple.com/guide/iphone/create-and-edit-events-in-calendar-iph3d110f84/ios?utm_source=ridgecrestchurch.com">Apple’s Calendar instructions for iPhone</a>, and <a href="https://support.microsoft.com/en-us/outlook/calendar/introduction-to-the-outlook-calendar?utm_source=ridgecrestchurch.com">Microsoft’s Outlook Calendar overview</a>.</p>
+
+<p>Use reminders for anything that has a deadline or requires preparation. If an event says “bring food,” “arrive early,” or “sign up by Thursday,” that is not optional trivia. It is the actual task.</p>
+
+<h2>How to stay in the loop between Sunday services</h2>
+
+<p>Do not wait until Sunday to discover the thing you were supposed to know on Tuesday. The News page and the Events Calendar work together. One explains what is happening. The other helps you see when it happens.</p>
+
+<ul>
+  <li>Check <a href="https://ridgecrestchurch.com/news.html">News</a> for announcements and changes.</li>
+  <li>Check <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for dates and upcoming gatherings.</li>
+  <li>Check <a href="https://ridgecrestchurch.com/">Home</a> if you want the main site entry point again because you clicked yourself into confusion.</li>
+</ul>
+
+<p>A decent habit is to review News once during the week and again before the weekend. That is enough to catch most updates without treating the church website like a full-time job.</p>
+
+<h2>Quick FAQ</h2>
+
+<h3>What if I missed it?</h3>
+
+<p>Start with the News post and the Events Calendar. If the update included a deadline or sign-up, use the contact page immediately to ask whether anything can still be done. Do not assume silence means the issue disappeared. It usually means you have not checked the right page yet.</p>
+
+<h3>Where do I find the details?</h3>
+
+<p>Use the News page first. If the post is brief, the next stop is the Events Calendar, then Contacts or Church Map if location or timing matters. If the information still feels thin after that, the problem is not you. The update needs more detail.</p>
+
+<h3>Who do I contact?</h3>
+
+<p>Use <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> for church staff information and <a href="https://ridgecrestchurch.com/contact.php">contact.php</a> if you want the direct contact path. If the matter is location-specific, add the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> to the mix so you are not asking a question that the map already answered.</p>
+
+<h2>Next steps</h2>
+
+<p>If you only remember three things, make them these: read the News page, check the Events Calendar, and contact the church when the update affects you directly. That is enough to stay informed without pretending every announcement will somehow reach you by psychic means.</p>
+
+<p>Start with the <a href="https://ridgecrestchurch.com/news.html">News</a> page, then move to the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for dates, and use <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> or the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> when you need a person, a place, or both. If you want more background on the church itself, the <a href="https://ridgecrestchurch.com/about.html">About Us</a> page is there too.</p>
+
+<p>That is the whole trick. Read the update, identify the action, and move it into your calendar before it evaporates. Basic process. Less drama.</p>
+

 succeeded in 494ms:
414:			<header class="entry-header">	<h2 class="entry-title" itemprop="headline"><a href="https://ridgecrestchurch.com/how-to-use-news-page-ridgecrest/" rel="bookmark">How to Read and Use Ridgecrest Baptist Church’s News Page (So You Never Miss an Update)</a></h2>
417:	<span class="entry-author" itemprop="author" itemscope="itemscope" itemtype="http://schema.org/Person">by <a href="https://ridgecrestchurch.com/author/felix-rowan/" title="Posts by Felix Rowan" rel="author" class="url fn n" itemprop="url"><span itemprop="name">Felix Rowan</span></a></span>	
420:<a href="https://ridgecrestchurch.com/how-to-use-news-page-ridgecrest/" title="How to Read and Use Ridgecrest Baptist Church’s News Page (So You Never Miss an Update)"><img data-src="https://ridgecrestchurch.com/wp-content/uploads/imports/ridgecrest-home-navigation-screenshot.png" class="wp-post-image lazyload" alt="Phone view of Ridgecrest site navigation with the News page visible" decoding="async" itemprop="image" src="data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==" style="--smush-placeholder-width: 1400px; --smush-placeholder-aspect-ratio: 1400/1050;" /></a><p>A practical guide to navigating Ridgecrest Baptist Church’s News page so you can track announcements, plan ahead, and act on updates without missing the useful part.</p>

codex
I’m making one small editorial cleanup before I lock it in: the three external calendar references need to be spaced out naturally instead of stacked into one paragraph. That keeps the article readable and keeps the link placement from looking like a checklist in a trench coat.
apply patch
patch: completed
/home/ubuntu/apps/ridgecrestchurch.com/.tmp/job-548-news-page-article.html
diff --git a//home/ubuntu/apps/ridgecrestchurch.com/.tmp/job-548-news-page-article.html b//home/ubuntu/apps/ridgecrestchurch.com/.tmp/job-548-news-page-article.html
new file mode 100644
index 0000000000000000000000000000000000000000..4c0d82a3ccab98ea4bdedcc903ec46a02d26d9f3
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/.tmp/job-548-news-page-article.html
@@ -0,0 +1,164 @@
+<p><strong><em>The News page is where the church quietly tells you what matters next.</em></strong> Ignore it, and you will keep acting surprised when an event, reminder, or ministry update shows up after the fact. A news page is not decoration. It is the place where Ridgecrest Baptist Church puts the practical details that decide whether you arrive prepared or arrive confused.</p>
+
+<p>If you have ever asked yourself, “What changed?” “Who is this for?” “Do I need to do anything?” or “Why did nobody tell me sooner?”, that is exactly why this page exists. The answer is not mystery. It is usually a date, a topic, a small action item, and your responsibility to read the whole thing instead of the first sentence.</p>
+
+<p>This guide walks through how to use the Ridgecrest News page without pretending attention is automatic. You will learn what belongs there, where to find it, how to scan updates fast, how to turn an announcement into a calendar reminder, and when to use the Events Calendar, Contacts, or Church Map instead of hoping a vague memory will save you.</p>
+
+<p>For context, the Ridgecrest site also keeps related information on the <a href="https://ridgecrestchurch.com/about.html">About Us</a>, <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>, and <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> pages, so you do not have to guess which page is doing which job. That is the good news. The bad news is that you still have to read the page.</p>
+
+<h2>What the News page is for</h2>
+
+<p>The News page is where short, useful updates live. Not the full history of the church. Not a sermon archive. Not a place for vague encouragement dressed up as information. It is for the kinds of announcements that affect attendance, timing, preparation, or follow-up.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>What you see</th>
+      <th>What it means</th>
+      <th>What you should do</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Event announcement</td>
+      <td>A dated gathering, deadline, or special church activity</td>
+      <td>Check the time, location, and whether you need to respond</td>
+    </tr>
+    <tr>
+      <td>Ministry update</td>
+      <td>Information for Kids, Youth, volunteers, or a specific group</td>
+      <td>Read whether it applies to you or your household</td>
+    </tr>
+    <tr>
+      <td>Special notice</td>
+      <td>A schedule change, church-wide reminder, or urgent correction</td>
+      <td>Put it on your calendar and stop relying on memory</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>The point is simple: the News page is not there to entertain you. It is there to reduce avoidable confusion. Most church problems are not dramatic. They are just small timing errors repeated by too many people.</p>
+
+<h2>Where to find the News page in the main navigation</h2>
+
+<p>On the site, the News page is part of the main navigation. If you are on desktop, look across the top menu. If you are on a phone, open the navigation menu and look for the same label. No treasure hunt required. Just read the menu instead of tapping at random like a distracted raccoon.</p>
+
+<p>For the live page, use the <a href="https://ridgecrestchurch.com/news.html">News</a> link. The site also keeps a simple front-door version of the page at <a href="https://ridgecrestchurch.com/news/">/news/</a>, so the content is easy to reach either way.</p>
+
+<figure class="wp-block-image alignwide">
+  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/ridgecrest-home-navigation-screenshot.png" alt="Phone view of Ridgecrest church navigation with the News page visible" loading="lazy" />
+  <figcaption>Use the main menu first. That is usually where the answer lives, which is inconvenient for people who prefer guesswork.</figcaption>
+</figure>
+
+<p>If you are already on the homepage, the quickest path is usually: homepage, main menu, News. If you are already on the News page, congratulations, you have won a round of basic navigation. Now read the actual update.</p>
+
+<h2>How to scan an update quickly</h2>
+
+<p>Most people do not need to read every line of a church update with a scholar’s commitment. They need the facts. Look for the parts that change what you do next.</p>
+
+<ul>
+  <li><strong>Date</strong> - When does it happen, and is there a deadline before it?</li>
+  <li><strong>Topic</strong> - What is this about in one sentence?</li>
+  <li><strong>Audience</strong> - Who actually needs this: everyone, parents, students, volunteers, or a specific class?</li>
+  <li><strong>Action needed</strong> - Do you need to RSVP, bring something, sign up, show up early, or do nothing at all?</li>
+</ul>
+
+<p>A practical scan takes less than a minute if you resist the urge to read every word twice. Start with the headline, then the first paragraph, then the date and contact details. If the post does not answer those four questions, keep reading until it does or until it proves it does not know what it is doing.</p>
+
+<p>Here is the working rule: if an update does not tell you when, who, and what next, it is incomplete from a visitor’s point of view. That is not your failure. It is the post’s.</p>
+
+<h3>Fast-read checklist</h3>
+
+<ol>
+  <li>Read the title.</li>
+  <li>Find the date.</li>
+  <li>Check who the update is for.</li>
+  <li>Look for a deadline or response request.</li>
+  <li>Put the event or reminder into your calendar if it matters to you.</li>
+</ol>
+
+<h2>Common types of posts you will see</h2>
+
+<p>The News page usually carries the same kinds of items, because churches are not that mysterious when they finally decide to write things down.</p>
+
+<h3>Service reminders</h3>
+
+<p>These are the simplest posts and the easiest to ignore. Do not. They often confirm service times, special schedules, or location changes. If the church is adjusting a service or class, this is where the update usually lands first.</p>
+
+<h3>Special events</h3>
+
+<p>Events can include fellowship meals, student activities, children’s ministry gatherings, church-wide celebrations, and seasonal services. If there is a deadline, ticket, RSVP, or sign-up, it belongs here. That is the part people forget and then pretend was never mentioned.</p>
+
+<h3>Ministry highlights</h3>
+
+<p>Sometimes the News page highlights what a ministry is doing, who it serves, or how to participate. This is useful because it tells you whether the update is just informational or actually inviting you to act. Most people confuse those two. They should not.</p>
+
+<h3>Prayer needs and follow-up notes</h3>
+
+<p>Not every update is about logistics. Some posts will point readers toward prayer, care, or encouragement. Those updates are different: read them carefully, respond appropriately, and do not treat them like event spam. That is not a good look.</p>
+
+<h2>How to respond to what you read</h2>
+
+<p>The whole point of reading a church update is to do something useful with it. Otherwise you are just collecting information the way some people collect receipts.</p>
+
+<ul>
+  <li><strong>RSVP when asked.</strong> If a post asks for a response, give one. That is not optional decor. It is part of the plan.</li>
+  <li><strong>Bring what the post names.</strong> If the update says bring food, supplies, forms, or a Bible, bring those things instead of improvising your way into inconvenience.</li>
+  <li><strong>Ask questions early.</strong> If the details are unclear, use the contact page before the event. Confusion gets cheaper when it is solved early.</li>
+  <li><strong>Share it with the right person.</strong> If the update affects your family, students, or ministry group, forward it before it disappears into the swamp of unread messages.</li>
+</ul>
+
+<p>When in doubt, use the <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> page or the direct <a href="https://ridgecrestchurch.com/contact.php">contact form</a>. Both land you in the same place emotionally: someone on the church side can answer the question instead of making you guess.</p>
+
+<p>If the update affects where to park, which entrance to use, or when to arrive, check the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> as well. A news item can tell you the plan, but a map tells you where to physically go. Oddly enough, that still matters.</p>
+
+<h2>Planning ahead: turn the news item into a calendar action</h2>
+
+<p>Reading an update is only half the job. The other half is making sure your future self does not quietly sabotage you. If something matters, put it on your personal calendar the same day you read it.</p>
+
+<figure class="wp-block-image alignwide">
+  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/events-calendar-page-screenshot.png" alt="Ridgecrest Events Calendar page screenshot with schedule and event sections" loading="lazy" />
+  <figcaption>Use the Events Calendar for dates. Use your own calendar for memory. Yes, both. Memory is a terrible project manager.</figcaption>
+</figure>
+
+<p>That can be as simple as copying the date, time, location, and one-line purpose into your phone calendar. If you use Google Calendar, its help page for creating events is a decent place to start: <a href="https://support.google.com/calendar/answer/72143?co=GENIE.Platform%3DDesktop&amp;hl=en&amp;utm_source=ridgecrestchurch.com">Google Calendar’s event creation help</a>. The mechanics are not impressive, but neither is forgetting something you already meant to attend.</p>
+
+<p>Apple users can do the same thing in the iPhone Calendar app, which has its own step-by-step help page: <a href="https://support.apple.com/guide/iphone/create-and-edit-events-in-calendar-iph3d110f84/ios?utm_source=ridgecrestchurch.com">Apple’s Calendar instructions for iPhone</a>. Same principle. Put the thing in the calendar before the week eats it.</p>
+
+<p>If you live in Outlook, the official calendar overview is here: <a href="https://support.microsoft.com/en-us/outlook/calendar/introduction-to-the-outlook-calendar?utm_source=ridgecrestchurch.com">Microsoft’s Outlook Calendar overview</a>. No mystery, no drama, and no excuse for “I meant to go.”</p>
+
+<p>Use reminders for anything that has a deadline or requires preparation. If an event says “bring food,” “arrive early,” or “sign up by Thursday,” that is not optional trivia. It is the actual task.</p>
+
+<h2>How to stay in the loop between Sunday services</h2>
+
+<p>Do not wait until Sunday to discover the thing you were supposed to know on Tuesday. The News page and the Events Calendar work together. One explains what is happening. The other helps you see when it happens.</p>
+
+<ul>
+  <li>Check <a href="https://ridgecrestchurch.com/news.html">News</a> for announcements and changes.</li>
+  <li>Check <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for dates and upcoming gatherings.</li>
+  <li>Check <a href="https://ridgecrestchurch.com/">Home</a> if you want the main site entry point again because you clicked yourself into confusion.</li>
+</ul>
+
+<p>A decent habit is to review News once during the week and again before the weekend. That is enough to catch most updates without treating the church website like a full-time job.</p>
+
+<h2>Quick FAQ</h2>
+
+<h3>What if I missed it?</h3>
+
+<p>Start with the News post and the Events Calendar. If the update included a deadline or sign-up, use the contact page immediately to ask whether anything can still be done. Do not assume silence means the issue disappeared. It usually means you have not checked the right page yet.</p>
+
+<h3>Where do I find the details?</h3>
+
+<p>Use the News page first. If the post is brief, the next stop is the Events Calendar, then Contacts or Church Map if location or timing matters. If the information still feels thin after that, the problem is not you. The update needs more detail.</p>
+
+<h3>Who do I contact?</h3>
+
+<p>Use <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> for church staff information and <a href="https://ridgecrestchurch.com/contact.php">contact.php</a> if you want the direct contact path. If the matter is location-specific, add the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> to the mix so you are not asking a question that the map already answered.</p>
+
+<h2>Next steps</h2>
+
+<p>If you only remember three things, make them these: read the News page, check the Events Calendar, and contact the church when the update affects you directly. That is enough to stay informed without pretending every announcement will somehow reach you by psychic means.</p>
+
+<p>Start with the <a href="https://ridgecrestchurch.com/news.html">News</a> page, then move to the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for dates, and use <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> or the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> when you need a person, a place, or both. If you want more background on the church itself, the <a href="https://ridgecrestchurch.com/about.html">About Us</a> page is there too.</p>
+
+<p>That is the whole trick. Read the update, identify the action, and move it into your calendar before it evaporates. Basic process. Less drama.</p>

diff --git a//home/ubuntu/apps/ridgecrestchurch.com/.tmp/job-548-news-page-article.html b//home/ubuntu/apps/ridgecrestchurch.com/.tmp/job-548-news-page-article.html
new file mode 100644
index 0000000000000000000000000000000000000000..4c0d82a3ccab98ea4bdedcc903ec46a02d26d9f3
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/.tmp/job-548-news-page-article.html
@@ -0,0 +1,164 @@
+<p><strong><em>The News page is where the church quietly tells you what matters next.</em></strong> Ignore it, and you will keep acting surprised when an event, reminder, or ministry update shows up after the fact. A news page is not decoration. It is the place where Ridgecrest Baptist Church puts the practical details that decide whether you arrive prepared or arrive confused.</p>
+
+<p>If you have ever asked yourself, “What changed?” “Who is this for?” “Do I need to do anything?” or “Why did nobody tell me sooner?”, that is exactly why this page exists. The answer is not mystery. It is usually a date, a topic, a small action item, and your responsibility to read the whole thing instead of the first sentence.</p>
+
+<p>This guide walks through how to use the Ridgecrest News page without pretending attention is automatic. You will learn what belongs there, where to find it, how to scan updates fast, how to turn an announcement into a calendar reminder, and when to use the Events Calendar, Contacts, or Church Map instead of hoping a vague memory will save you.</p>
+
+<p>For context, the Ridgecrest site also keeps related information on the <a href="https://ridgecrestchurch.com/about.html">About Us</a>, <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>, and <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> pages, so you do not have to guess which page is doing which job. That is the good news. The bad news is that you still have to read the page.</p>
+
+<h2>What the News page is for</h2>
+
+<p>The News page is where short, useful updates live. Not the full history of the church. Not a sermon archive. Not a place for vague encouragement dressed up as information. It is for the kinds of announcements that affect attendance, timing, preparation, or follow-up.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>What you see</th>
+      <th>What it means</th>
+      <th>What you should do</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Event announcement</td>
+      <td>A dated gathering, deadline, or special church activity</td>
+      <td>Check the time, location, and whether you need to respond</td>
+    </tr>
+    <tr>
+      <td>Ministry update</td>
+      <td>Information for Kids, Youth, volunteers, or a specific group</td>
+      <td>Read whether it applies to you or your household</td>
+    </tr>
+    <tr>
+      <td>Special notice</td>
+      <td>A schedule change, church-wide reminder, or urgent correction</td>
+      <td>Put it on your calendar and stop relying on memory</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>The point is simple: the News page is not there to entertain you. It is there to reduce avoidable confusion. Most church problems are not dramatic. They are just small timing errors repeated by too many people.</p>
+
+<h2>Where to find the News page in the main navigation</h2>
+
+<p>On the site, the News page is part of the main navigation. If you are on desktop, look across the top menu. If you are on a phone, open the navigation menu and look for the same label. No treasure hunt required. Just read the menu instead of tapping at random like a distracted raccoon.</p>
+
+<p>For the live page, use the <a href="https://ridgecrestchurch.com/news.html">News</a> link. The site also keeps a simple front-door version of the page at <a href="https://ridgecrestchurch.com/news/">/news/</a>, so the content is easy to reach either way.</p>
+
+<figure class="wp-block-image alignwide">
+  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/ridgecrest-home-navigation-screenshot.png" alt="Phone view of Ridgecrest church navigation with the News page visible" loading="lazy" />
+  <figcaption>Use the main menu first. That is usually where the answer lives, which is inconvenient for people who prefer guesswork.</figcaption>
+</figure>
+
+<p>If you are already on the homepage, the quickest path is usually: homepage, main menu, News. If you are already on the News page, congratulations, you have won a round of basic navigation. Now read the actual update.</p>
+
+<h2>How to scan an update quickly</h2>
+
+<p>Most people do not need to read every line of a church update with a scholar’s commitment. They need the facts. Look for the parts that change what you do next.</p>
+
+<ul>
+  <li><strong>Date</strong> - When does it happen, and is there a deadline before it?</li>
+  <li><strong>Topic</strong> - What is this about in one sentence?</li>
+  <li><strong>Audience</strong> - Who actually needs this: everyone, parents, students, volunteers, or a specific class?</li>
+  <li><strong>Action needed</strong> - Do you need to RSVP, bring something, sign up, show up early, or do nothing at all?</li>
+</ul>
+
+<p>A practical scan takes less than a minute if you resist the urge to read every word twice. Start with the headline, then the first paragraph, then the date and contact details. If the post does not answer those four questions, keep reading until it does or until it proves it does not know what it is doing.</p>
+
+<p>Here is the working rule: if an update does not tell you when, who, and what next, it is incomplete from a visitor’s point of view. That is not your failure. It is the post’s.</p>
+
+<h3>Fast-read checklist</h3>
+
+<ol>
+  <li>Read the title.</li>
+  <li>Find the date.</li>
+  <li>Check who the update is for.</li>
+  <li>Look for a deadline or response request.</li>
+  <li>Put the event or reminder into your calendar if it matters to you.</li>
+</ol>
+
+<h2>Common types of posts you will see</h2>
+
+<p>The News page usually carries the same kinds of items, because churches are not that mysterious when they finally decide to write things down.</p>
+
+<h3>Service reminders</h3>
+
+<p>These are the simplest posts and the easiest to ignore. Do not. They often confirm service times, special schedules, or location changes. If the church is adjusting a service or class, this is where the update usually lands first.</p>
+
+<h3>Special events</h3>
+
+<p>Events can include fellowship meals, student activities, children’s ministry gatherings, church-wide celebrations, and seasonal services. If there is a deadline, ticket, RSVP, or sign-up, it belongs here. That is the part people forget and then pretend was never mentioned.</p>
+
+<h3>Ministry highlights</h3>
+
+<p>Sometimes the News page highlights what a ministry is doing, who it serves, or how to participate. This is useful because it tells you whether the update is just informational or actually inviting you to act. Most people confuse those two. They should not.</p>
+
+<h3>Prayer needs and follow-up notes</h3>
+
+<p>Not every update is about logistics. Some posts will point readers toward prayer, care, or encouragement. Those updates are different: read them carefully, respond appropriately, and do not treat them like event spam. That is not a good look.</p>
+
+<h2>How to respond to what you read</h2>
+
+<p>The whole point of reading a church update is to do something useful with it. Otherwise you are just collecting information the way some people collect receipts.</p>
+
+<ul>
+  <li><strong>RSVP when asked.</strong> If a post asks for a response, give one. That is not optional decor. It is part of the plan.</li>
+  <li><strong>Bring what the post names.</strong> If the update says bring food, supplies, forms, or a Bible, bring those things instead of improvising your way into inconvenience.</li>
+  <li><strong>Ask questions early.</strong> If the details are unclear, use the contact page before the event. Confusion gets cheaper when it is solved early.</li>
+  <li><strong>Share it with the right person.</strong> If the update affects your family, students, or ministry group, forward it before it disappears into the swamp of unread messages.</li>
+</ul>
+
+<p>When in doubt, use the <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> page or the direct <a href="https://ridgecrestchurch.com/contact.php">contact form</a>. Both land you in the same place emotionally: someone on the church side can answer the question instead of making you guess.</p>
+
+<p>If the update affects where to park, which entrance to use, or when to arrive, check the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> as well. A news item can tell you the plan, but a map tells you where to physically go. Oddly enough, that still matters.</p>
+
+<h2>Planning ahead: turn the news item into a calendar action</h2>
+
+<p>Reading an update is only half the job. The other half is making sure your future self does not quietly sabotage you. If something matters, put it on your personal calendar the same day you read it.</p>
+
+<figure class="wp-block-image alignwide">
+  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/events-calendar-page-screenshot.png" alt="Ridgecrest Events Calendar page screenshot with schedule and event sections" loading="lazy" />
+  <figcaption>Use the Events Calendar for dates. Use your own calendar for memory. Yes, both. Memory is a terrible project manager.</figcaption>
+</figure>
+
+<p>That can be as simple as copying the date, time, location, and one-line purpose into your phone calendar. If you use Google Calendar, its help page for creating events is a decent place to start: <a href="https://support.google.com/calendar/answer/72143?co=GENIE.Platform%3DDesktop&amp;hl=en&amp;utm_source=ridgecrestchurch.com">Google Calendar’s event creation help</a>. The mechanics are not impressive, but neither is forgetting something you already meant to attend.</p>
+
+<p>Apple users can do the same thing in the iPhone Calendar app, which has its own step-by-step help page: <a href="https://support.apple.com/guide/iphone/create-and-edit-events-in-calendar-iph3d110f84/ios?utm_source=ridgecrestchurch.com">Apple’s Calendar instructions for iPhone</a>. Same principle. Put the thing in the calendar before the week eats it.</p>
+
+<p>If you live in Outlook, the official calendar overview is here: <a href="https://support.microsoft.com/en-us/outlook/calendar/introduction-to-the-outlook-calendar?utm_source=ridgecrestchurch.com">Microsoft’s Outlook Calendar overview</a>. No mystery, no drama, and no excuse for “I meant to go.”</p>
+
+<p>Use reminders for anything that has a deadline or requires preparation. If an event says “bring food,” “arrive early,” or “sign up by Thursday,” that is not optional trivia. It is the actual task.</p>
+
+<h2>How to stay in the loop between Sunday services</h2>
+
+<p>Do not wait until Sunday to discover the thing you were supposed to know on Tuesday. The News page and the Events Calendar work together. One explains what is happening. The other helps you see when it happens.</p>
+
+<ul>
+  <li>Check <a href="https://ridgecrestchurch.com/news.html">News</a> for announcements and changes.</li>
+  <li>Check <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for dates and upcoming gatherings.</li>
+  <li>Check <a href="https://ridgecrestchurch.com/">Home</a> if you want the main site entry point again because you clicked yourself into confusion.</li>
+</ul>
+
+<p>A decent habit is to review News once during the week and again before the weekend. That is enough to catch most updates without treating the church website like a full-time job.</p>
+
+<h2>Quick FAQ</h2>
+
+<h3>What if I missed it?</h3>
+
+<p>Start with the News post and the Events Calendar. If the update included a deadline or sign-up, use the contact page immediately to ask whether anything can still be done. Do not assume silence means the issue disappeared. It usually means you have not checked the right page yet.</p>
+
+<h3>Where do I find the details?</h3>
+
+<p>Use the News page first. If the post is brief, the next stop is the Events Calendar, then Contacts or Church Map if location or timing matters. If the information still feels thin after that, the problem is not you. The update needs more detail.</p>
+
+<h3>Who do I contact?</h3>
+
+<p>Use <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> for church staff information and <a href="https://ridgecrestchurch.com/contact.php">contact.php</a> if you want the direct contact path. If the matter is location-specific, add the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> to the mix so you are not asking a question that the map already answered.</p>
+
+<h2>Next steps</h2>
+
+<p>If you only remember three things, make them these: read the News page, check the Events Calendar, and contact the church when the update affects you directly. That is enough to stay informed without pretending every announcement will somehow reach you by psychic means.</p>
+
+<p>Start with the <a href="https://ridgecrestchurch.com/news.html">News</a> page, then move to the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for dates, and use <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> or the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> when you need a person, a place, or both. If you want more background on the church itself, the <a href="https://ridgecrestchurch.com/about.html">About Us</a> page is there too.</p>
+
+<p>That is the whole trick. Read the update, identify the action, and move it into your calendar before it evaporates. Basic process. Less drama.</p>

codex
The link placement is fixed. I’m pushing the revised content to WordPress and then rechecking the rendered HTML so the final post reflects the actual split paragraphs instead of the first draft’s lumped-together version.
exec
/bin/bash -lc 'content="$(< .tmp/job-548-news-page-article.html)"; wp post update 119 --post_content="$content"' in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "wp post get 119 --field=post_content | rg -n 'support.google.com/calendar|support.apple.com/guide/iphone|support.microsoft.com/en-us/outlook/calendar/introduction-to-the-outlook-calendar'" in /home/ubuntu/apps/ridgecrestchurch.com
diff --git a//home/ubuntu/apps/ridgecrestchurch.com/.tmp/job-548-news-page-article.html b//home/ubuntu/apps/ridgecrestchurch.com/.tmp/job-548-news-page-article.html
new file mode 100644
index 0000000000000000000000000000000000000000..4c0d82a3ccab98ea4bdedcc903ec46a02d26d9f3
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/.tmp/job-548-news-page-article.html
@@ -0,0 +1,164 @@
+<p><strong><em>The News page is where the church quietly tells you what matters next.</em></strong> Ignore it, and you will keep acting surprised when an event, reminder, or ministry update shows up after the fact. A news page is not decoration. It is the place where Ridgecrest Baptist Church puts the practical details that decide whether you arrive prepared or arrive confused.</p>
+
+<p>If you have ever asked yourself, “What changed?” “Who is this for?” “Do I need to do anything?” or “Why did nobody tell me sooner?”, that is exactly why this page exists. The answer is not mystery. It is usually a date, a topic, a small action item, and your responsibility to read the whole thing instead of the first sentence.</p>
+
+<p>This guide walks through how to use the Ridgecrest News page without pretending attention is automatic. You will learn what belongs there, where to find it, how to scan updates fast, how to turn an announcement into a calendar reminder, and when to use the Events Calendar, Contacts, or Church Map instead of hoping a vague memory will save you.</p>
+
+<p>For context, the Ridgecrest site also keeps related information on the <a href="https://ridgecrestchurch.com/about.html">About Us</a>, <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>, and <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> pages, so you do not have to guess which page is doing which job. That is the good news. The bad news is that you still have to read the page.</p>
+
+<h2>What the News page is for</h2>
+
+<p>The News page is where short, useful updates live. Not the full history of the church. Not a sermon archive. Not a place for vague encouragement dressed up as information. It is for the kinds of announcements that affect attendance, timing, preparation, or follow-up.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>What you see</th>
+      <th>What it means</th>
+      <th>What you should do</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Event announcement</td>
+      <td>A dated gathering, deadline, or special church activity</td>
+      <td>Check the time, location, and whether you need to respond</td>
+    </tr>
+    <tr>
+      <td>Ministry update</td>
+      <td>Information for Kids, Youth, volunteers, or a specific group</td>
+      <td>Read whether it applies to you or your household</td>
+    </tr>
+    <tr>
+      <td>Special notice</td>
+      <td>A schedule change, church-wide reminder, or urgent correction</td>
+      <td>Put it on your calendar and stop relying on memory</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>The point is simple: the News page is not there to entertain you. It is there to reduce avoidable confusion. Most church problems are not dramatic. They are just small timing errors repeated by too many people.</p>
+
+<h2>Where to find the News page in the main navigation</h2>
+
+<p>On the site, the News page is part of the main navigation. If you are on desktop, look across the top menu. If you are on a phone, open the navigation menu and look for the same label. No treasure hunt required. Just read the menu instead of tapping at random like a distracted raccoon.</p>
+
+<p>For the live page, use the <a href="https://ridgecrestchurch.com/news.html">News</a> link. The site also keeps a simple front-door version of the page at <a href="https://ridgecrestchurch.com/news/">/news/</a>, so the content is easy to reach either way.</p>
+
+<figure class="wp-block-image alignwide">
+  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/ridgecrest-home-navigation-screenshot.png" alt="Phone view of Ridgecrest church navigation with the News page visible" loading="lazy" />
+  <figcaption>Use the main menu first. That is usually where the answer lives, which is inconvenient for people who prefer guesswork.</figcaption>
+</figure>
+
+<p>If you are already on the homepage, the quickest path is usually: homepage, main menu, News. If you are already on the News page, congratulations, you have won a round of basic navigation. Now read the actual update.</p>
+
+<h2>How to scan an update quickly</h2>
+
+<p>Most people do not need to read every line of a church update with a scholar’s commitment. They need the facts. Look for the parts that change what you do next.</p>
+
+<ul>
+  <li><strong>Date</strong> - When does it happen, and is there a deadline before it?</li>
+  <li><strong>Topic</strong> - What is this about in one sentence?</li>
+  <li><strong>Audience</strong> - Who actually needs this: everyone, parents, students, volunteers, or a specific class?</li>
+  <li><strong>Action needed</strong> - Do you need to RSVP, bring something, sign up, show up early, or do nothing at all?</li>
+</ul>
+
+<p>A practical scan takes less than a minute if you resist the urge to read every word twice. Start with the headline, then the first paragraph, then the date and contact details. If the post does not answer those four questions, keep reading until it does or until it proves it does not know what it is doing.</p>
+
+<p>Here is the working rule: if an update does not tell you when, who, and what next, it is incomplete from a visitor’s point of view. That is not your failure. It is the post’s.</p>
+
+<h3>Fast-read checklist</h3>
+
+<ol>
+  <li>Read the title.</li>
+  <li>Find the date.</li>
+  <li>Check who the update is for.</li>
+  <li>Look for a deadline or response request.</li>
+  <li>Put the event or reminder into your calendar if it matters to you.</li>
+</ol>
+
+<h2>Common types of posts you will see</h2>
+
+<p>The News page usually carries the same kinds of items, because churches are not that mysterious when they finally decide to write things down.</p>
+
+<h3>Service reminders</h3>
+
+<p>These are the simplest posts and the easiest to ignore. Do not. They often confirm service times, special schedules, or location changes. If the church is adjusting a service or class, this is where the update usually lands first.</p>
+
+<h3>Special events</h3>
+
+<p>Events can include fellowship meals, student activities, children’s ministry gatherings, church-wide celebrations, and seasonal services. If there is a deadline, ticket, RSVP, or sign-up, it belongs here. That is the part people forget and then pretend was never mentioned.</p>
+
+<h3>Ministry highlights</h3>
+
+<p>Sometimes the News page highlights what a ministry is doing, who it serves, or how to participate. This is useful because it tells you whether the update is just informational or actually inviting you to act. Most people confuse those two. They should not.</p>
+
+<h3>Prayer needs and follow-up notes</h3>
+
+<p>Not every update is about logistics. Some posts will point readers toward prayer, care, or encouragement. Those updates are different: read them carefully, respond appropriately, and do not treat them like event spam. That is not a good look.</p>
+
+<h2>How to respond to what you read</h2>
+
+<p>The whole point of reading a church update is to do something useful with it. Otherwise you are just collecting information the way some people collect receipts.</p>
+
+<ul>
+  <li><strong>RSVP when asked.</strong> If a post asks for a response, give one. That is not optional decor. It is part of the plan.</li>
+  <li><strong>Bring what the post names.</strong> If the update says bring food, supplies, forms, or a Bible, bring those things instead of improvising your way into inconvenience.</li>
+  <li><strong>Ask questions early.</strong> If the details are unclear, use the contact page before the event. Confusion gets cheaper when it is solved early.</li>
+  <li><strong>Share it with the right person.</strong> If the update affects your family, students, or ministry group, forward it before it disappears into the swamp of unread messages.</li>
+</ul>
+
+<p>When in doubt, use the <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> page or the direct <a href="https://ridgecrestchurch.com/contact.php">contact form</a>. Both land you in the same place emotionally: someone on the church side can answer the question instead of making you guess.</p>
+
+<p>If the update affects where to park, which entrance to use, or when to arrive, check the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> as well. A news item can tell you the plan, but a map tells you where to physically go. Oddly enough, that still matters.</p>
+
+<h2>Planning ahead: turn the news item into a calendar action</h2>
+
+<p>Reading an update is only half the job. The other half is making sure your future self does not quietly sabotage you. If something matters, put it on your personal calendar the same day you read it.</p>
+
+<figure class="wp-block-image alignwide">
+  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/events-calendar-page-screenshot.png" alt="Ridgecrest Events Calendar page screenshot with schedule and event sections" loading="lazy" />
+  <figcaption>Use the Events Calendar for dates. Use your own calendar for memory. Yes, both. Memory is a terrible project manager.</figcaption>
+</figure>
+
+<p>That can be as simple as copying the date, time, location, and one-line purpose into your phone calendar. If you use Google Calendar, its help page for creating events is a decent place to start: <a href="https://support.google.com/calendar/answer/72143?co=GENIE.Platform%3DDesktop&amp;hl=en&amp;utm_source=ridgecrestchurch.com">Google Calendar’s event creation help</a>. The mechanics are not impressive, but neither is forgetting something you already meant to attend.</p>
+
+<p>Apple users can do the same thing in the iPhone Calendar app, which has its own step-by-step help page: <a href="https://support.apple.com/guide/iphone/create-and-edit-events-in-calendar-iph3d110f84/ios?utm_source=ridgecrestchurch.com">Apple’s Calendar instructions for iPhone</a>. Same principle. Put the thing in the calendar before the week eats it.</p>
+
+<p>If you live in Outlook, the official calendar overview is here: <a href="https://support.microsoft.com/en-us/outlook/calendar/introduction-to-the-outlook-calendar?utm_source=ridgecrestchurch.com">Microsoft’s Outlook Calendar overview</a>. No mystery, no drama, and no excuse for “I meant to go.”</p>
+
+<p>Use reminders for anything that has a deadline or requires preparation. If an event says “bring food,” “arrive early,” or “sign up by Thursday,” that is not optional trivia. It is the actual task.</p>
+
+<h2>How to stay in the loop between Sunday services</h2>
+
+<p>Do not wait until Sunday to discover the thing you were supposed to know on Tuesday. The News page and the Events Calendar work together. One explains what is happening. The other helps you see when it happens.</p>
+
+<ul>
+  <li>Check <a href="https://ridgecrestchurch.com/news.html">News</a> for announcements and changes.</li>
+  <li>Check <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for dates and upcoming gatherings.</li>
+  <li>Check <a href="https://ridgecrestchurch.com/">Home</a> if you want the main site entry point again because you clicked yourself into confusion.</li>
+</ul>
+
+<p>A decent habit is to review News once during the week and again before the weekend. That is enough to catch most updates without treating the church website like a full-time job.</p>
+
+<h2>Quick FAQ</h2>
+
+<h3>What if I missed it?</h3>
+
+<p>Start with the News post and the Events Calendar. If the update included a deadline or sign-up, use the contact page immediately to ask whether anything can still be done. Do not assume silence means the issue disappeared. It usually means you have not checked the right page yet.</p>
+
+<h3>Where do I find the details?</h3>
+
+<p>Use the News page first. If the post is brief, the next stop is the Events Calendar, then Contacts or Church Map if location or timing matters. If the information still feels thin after that, the problem is not you. The update needs more detail.</p>
+
+<h3>Who do I contact?</h3>
+
+<p>Use <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> for church staff information and <a href="https://ridgecrestchurch.com/contact.php">contact.php</a> if you want the direct contact path. If the matter is location-specific, add the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> to the mix so you are not asking a question that the map already answered.</p>
+
+<h2>Next steps</h2>
+
+<p>If you only remember three things, make them these: read the News page, check the Events Calendar, and contact the church when the update affects you directly. That is enough to stay informed without pretending every announcement will somehow reach you by psychic means.</p>
+
+<p>Start with the <a href="https://ridgecrestchurch.com/news.html">News</a> page, then move to the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for dates, and use <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> or the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> when you need a person, a place, or both. If you want more background on the church itself, the <a href="https://ridgecrestchurch.com/about.html">About Us</a> page is there too.</p>
+
+<p>That is the whole trick. Read the update, identify the action, and move it into your calendar before it evaporates. Basic process. Less drama.</p>

 succeeded in 652ms:
Success: Updated post 119.

 succeeded in 614ms:
124:<p>That can be as simple as copying the date, time, location, and one-line purpose into your phone calendar. If you use Google Calendar, its help page for creating events is a decent place to start: <a href="https://support.google.com/calendar/answer/72143?co=GENIE.Platform%3DDesktop&amp;hl=en&amp;utm_source=ridgecrestchurch.com">Google Calendar’s event creation help</a>. The mechanics are not impressive, but neither is forgetting something you already meant to attend.</p>
126:<p>Apple users can do the same thing in the iPhone Calendar app, which has its own step-by-step help page: <a href="https://support.apple.com/guide/iphone/create-and-edit-events-in-calendar-iph3d110f84/ios?utm_source=ridgecrestchurch.com">Apple’s Calendar instructions for iPhone</a>. Same principle. Put the thing in the calendar before the week eats it.</p>
128:<p>If you live in Outlook, the official calendar overview is here: <a href="https://support.microsoft.com/en-us/outlook/calendar/introduction-to-the-outlook-calendar?utm_source=ridgecrestchurch.com">Microsoft’s Outlook Calendar overview</a>. No mystery, no drama, and no excuse for “I meant to go.”</p>

codex
I’m running the final sanity pass: both image references should still be present after the content update, and the blog index should still show the new post after WordPress re-saved it. No point celebrating a vanished image.
exec
/bin/bash -lc "wp post get 119 --field=post_content | rg -n 'ridgecrest-home-navigation-screenshot|events-calendar-page-screenshot|news.html|contact.php'" in /home/ubuntu/apps/ridgecrestchurch.com
exec
/bin/bash -lc "curl -L --silent --show-error https://ridgecrestchurch.com/blog/ | rg -n 'How to Read and Use Ridgecrest Baptist Church|how-to-use-news-page-ridgecrest|Felix Rowan'" in /home/ubuntu/apps/ridgecrestchurch.com
 succeeded in 561ms:
46:<p>For the live page, use the <a href="https://ridgecrestchurch.com/news.html">News</a> link. The site also keeps a simple front-door version of the page at <a href="https://ridgecrestchurch.com/news/">/news/</a>, so the content is easy to reach either way.</p>
49:  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/ridgecrest-home-navigation-screenshot.png" alt="Phone view of Ridgecrest church navigation with the News page visible" loading="lazy" />
111:<p>When in doubt, use the <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> page or the direct <a href="https://ridgecrestchurch.com/contact.php">contact form</a>. Both land you in the same place emotionally: someone on the church side can answer the question instead of making you guess.</p>
120:  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/events-calendar-page-screenshot.png" alt="Ridgecrest Events Calendar page screenshot with schedule and event sections" loading="lazy" />
137:  <li>Check <a href="https://ridgecrestchurch.com/news.html">News</a> for announcements and changes.</li>
156:<p>Use <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> for church staff information and <a href="https://ridgecrestchurch.com/contact.php">contact.php</a> if you want the direct contact path. If the matter is location-specific, add the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> to the mix so you are not asking a question that the map already answered.</p>
162:<p>Start with the <a href="https://ridgecrestchurch.com/news.html">News</a> page, then move to the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for dates, and use <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> or the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> when you need a person, a place, or both. If you want more background on the church itself, the <a href="https://ridgecrestchurch.com/about.html">About Us</a> page is there too.</p>

diff --git a//home/ubuntu/apps/ridgecrestchurch.com/.tmp/job-548-news-page-article.html b//home/ubuntu/apps/ridgecrestchurch.com/.tmp/job-548-news-page-article.html
new file mode 100644
index 0000000000000000000000000000000000000000..4c0d82a3ccab98ea4bdedcc903ec46a02d26d9f3
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/.tmp/job-548-news-page-article.html
@@ -0,0 +1,164 @@
+<p><strong><em>The News page is where the church quietly tells you what matters next.</em></strong> Ignore it, and you will keep acting surprised when an event, reminder, or ministry update shows up after the fact. A news page is not decoration. It is the place where Ridgecrest Baptist Church puts the practical details that decide whether you arrive prepared or arrive confused.</p>
+
+<p>If you have ever asked yourself, “What changed?” “Who is this for?” “Do I need to do anything?” or “Why did nobody tell me sooner?”, that is exactly why this page exists. The answer is not mystery. It is usually a date, a topic, a small action item, and your responsibility to read the whole thing instead of the first sentence.</p>
+
+<p>This guide walks through how to use the Ridgecrest News page without pretending attention is automatic. You will learn what belongs there, where to find it, how to scan updates fast, how to turn an announcement into a calendar reminder, and when to use the Events Calendar, Contacts, or Church Map instead of hoping a vague memory will save you.</p>
+
+<p>For context, the Ridgecrest site also keeps related information on the <a href="https://ridgecrestchurch.com/about.html">About Us</a>, <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>, and <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> pages, so you do not have to guess which page is doing which job. That is the good news. The bad news is that you still have to read the page.</p>
+
+<h2>What the News page is for</h2>
+
+<p>The News page is where short, useful updates live. Not the full history of the church. Not a sermon archive. Not a place for vague encouragement dressed up as information. It is for the kinds of announcements that affect attendance, timing, preparation, or follow-up.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>What you see</th>
+      <th>What it means</th>
+      <th>What you should do</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Event announcement</td>
+      <td>A dated gathering, deadline, or special church activity</td>
+      <td>Check the time, location, and whether you need to respond</td>
+    </tr>
+    <tr>
+      <td>Ministry update</td>
+      <td>Information for Kids, Youth, volunteers, or a specific group</td>
+      <td>Read whether it applies to you or your household</td>
+    </tr>
+    <tr>
+      <td>Special notice</td>
+      <td>A schedule change, church-wide reminder, or urgent correction</td>
+      <td>Put it on your calendar and stop relying on memory</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>The point is simple: the News page is not there to entertain you. It is there to reduce avoidable confusion. Most church problems are not dramatic. They are just small timing errors repeated by too many people.</p>
+
+<h2>Where to find the News page in the main navigation</h2>
+
+<p>On the site, the News page is part of the main navigation. If you are on desktop, look across the top menu. If you are on a phone, open the navigation menu and look for the same label. No treasure hunt required. Just read the menu instead of tapping at random like a distracted raccoon.</p>
+
+<p>For the live page, use the <a href="https://ridgecrestchurch.com/news.html">News</a> link. The site also keeps a simple front-door version of the page at <a href="https://ridgecrestchurch.com/news/">/news/</a>, so the content is easy to reach either way.</p>
+
+<figure class="wp-block-image alignwide">
+  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/ridgecrest-home-navigation-screenshot.png" alt="Phone view of Ridgecrest church navigation with the News page visible" loading="lazy" />
+  <figcaption>Use the main menu first. That is usually where the answer lives, which is inconvenient for people who prefer guesswork.</figcaption>
+</figure>
+
+<p>If you are already on the homepage, the quickest path is usually: homepage, main menu, News. If you are already on the News page, congratulations, you have won a round of basic navigation. Now read the actual update.</p>
+
+<h2>How to scan an update quickly</h2>
+
+<p>Most people do not need to read every line of a church update with a scholar’s commitment. They need the facts. Look for the parts that change what you do next.</p>
+
+<ul>
+  <li><strong>Date</strong> - When does it happen, and is there a deadline before it?</li>
+  <li><strong>Topic</strong> - What is this about in one sentence?</li>
+  <li><strong>Audience</strong> - Who actually needs this: everyone, parents, students, volunteers, or a specific class?</li>
+  <li><strong>Action needed</strong> - Do you need to RSVP, bring something, sign up, show up early, or do nothing at all?</li>
+</ul>
+
+<p>A practical scan takes less than a minute if you resist the urge to read every word twice. Start with the headline, then the first paragraph, then the date and contact details. If the post does not answer those four questions, keep reading until it does or until it proves it does not know what it is doing.</p>
+
+<p>Here is the working rule: if an update does not tell you when, who, and what next, it is incomplete from a visitor’s point of view. That is not your failure. It is the post’s.</p>
+
+<h3>Fast-read checklist</h3>
+
+<ol>
+  <li>Read the title.</li>
+  <li>Find the date.</li>
+  <li>Check who the update is for.</li>
+  <li>Look for a deadline or response request.</li>
+  <li>Put the event or reminder into your calendar if it matters to you.</li>
+</ol>
+
+<h2>Common types of posts you will see</h2>
+
+<p>The News page usually carries the same kinds of items, because churches are not that mysterious when they finally decide to write things down.</p>
+
+<h3>Service reminders</h3>
+
+<p>These are the simplest posts and the easiest to ignore. Do not. They often confirm service times, special schedules, or location changes. If the church is adjusting a service or class, this is where the update usually lands first.</p>
+
+<h3>Special events</h3>
+
+<p>Events can include fellowship meals, student activities, children’s ministry gatherings, church-wide celebrations, and seasonal services. If there is a deadline, ticket, RSVP, or sign-up, it belongs here. That is the part people forget and then pretend was never mentioned.</p>
+
+<h3>Ministry highlights</h3>
+
+<p>Sometimes the News page highlights what a ministry is doing, who it serves, or how to participate. This is useful because it tells you whether the update is just informational or actually inviting you to act. Most people confuse those two. They should not.</p>
+
+<h3>Prayer needs and follow-up notes</h3>
+
+<p>Not every update is about logistics. Some posts will point readers toward prayer, care, or encouragement. Those updates are different: read them carefully, respond appropriately, and do not treat them like event spam. That is not a good look.</p>
+
+<h2>How to respond to what you read</h2>
+
+<p>The whole point of reading a church update is to do something useful with it. Otherwise you are just collecting information the way some people collect receipts.</p>
+
+<ul>
+  <li><strong>RSVP when asked.</strong> If a post asks for a response, give one. That is not optional decor. It is part of the plan.</li>
+  <li><strong>Bring what the post names.</strong> If the update says bring food, supplies, forms, or a Bible, bring those things instead of improvising your way into inconvenience.</li>
+  <li><strong>Ask questions early.</strong> If the details are unclear, use the contact page before the event. Confusion gets cheaper when it is solved early.</li>
+  <li><strong>Share it with the right person.</strong> If the update affects your family, students, or ministry group, forward it before it disappears into the swamp of unread messages.</li>
+</ul>
+
+<p>When in doubt, use the <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> page or the direct <a href="https://ridgecrestchurch.com/contact.php">contact form</a>. Both land you in the same place emotionally: someone on the church side can answer the question instead of making you guess.</p>
+
+<p>If the update affects where to park, which entrance to use, or when to arrive, check the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> as well. A news item can tell you the plan, but a map tells you where to physically go. Oddly enough, that still matters.</p>
+
+<h2>Planning ahead: turn the news item into a calendar action</h2>
+
+<p>Reading an update is only half the job. The other half is making sure your future self does not quietly sabotage you. If something matters, put it on your personal calendar the same day you read it.</p>
+
+<figure class="wp-block-image alignwide">
+  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/events-calendar-page-screenshot.png" alt="Ridgecrest Events Calendar page screenshot with schedule and event sections" loading="lazy" />
+  <figcaption>Use the Events Calendar for dates. Use your own calendar for memory. Yes, both. Memory is a terrible project manager.</figcaption>
+</figure>
+
+<p>That can be as simple as copying the date, time, location, and one-line purpose into your phone calendar. If you use Google Calendar, its help page for creating events is a decent place to start: <a href="https://support.google.com/calendar/answer/72143?co=GENIE.Platform%3DDesktop&amp;hl=en&amp;utm_source=ridgecrestchurch.com">Google Calendar’s event creation help</a>. The mechanics are not impressive, but neither is forgetting something you already meant to attend.</p>
+
+<p>Apple users can do the same thing in the iPhone Calendar app, which has its own step-by-step help page: <a href="https://support.apple.com/guide/iphone/create-and-edit-events-in-calendar-iph3d110f84/ios?utm_source=ridgecrestchurch.com">Apple’s Calendar instructions for iPhone</a>. Same principle. Put the thing in the calendar before the week eats it.</p>
+
+<p>If you live in Outlook, the official calendar overview is here: <a href="https://support.microsoft.com/en-us/outlook/calendar/introduction-to-the-outlook-calendar?utm_source=ridgecrestchurch.com">Microsoft’s Outlook Calendar overview</a>. No mystery, no drama, and no excuse for “I meant to go.”</p>
+
+<p>Use reminders for anything that has a deadline or requires preparation. If an event says “bring food,” “arrive early,” or “sign up by Thursday,” that is not optional trivia. It is the actual task.</p>
+
+<h2>How to stay in the loop between Sunday services</h2>
+
+<p>Do not wait until Sunday to discover the thing you were supposed to know on Tuesday. The News page and the Events Calendar work together. One explains what is happening. The other helps you see when it happens.</p>
+
+<ul>
+  <li>Check <a href="https://ridgecrestchurch.com/news.html">News</a> for announcements and changes.</li>
+  <li>Check <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for dates and upcoming gatherings.</li>
+  <li>Check <a href="https://ridgecrestchurch.com/">Home</a> if you want the main site entry point again because you clicked yourself into confusion.</li>
+</ul>
+
+<p>A decent habit is to review News once during the week and again before the weekend. That is enough to catch most updates without treating the church website like a full-time job.</p>
+
+<h2>Quick FAQ</h2>
+
+<h3>What if I missed it?</h3>
+
+<p>Start with the News post and the Events Calendar. If the update included a deadline or sign-up, use the contact page immediately to ask whether anything can still be done. Do not assume silence means the issue disappeared. It usually means you have not checked the right page yet.</p>
+
+<h3>Where do I find the details?</h3>
+
+<p>Use the News page first. If the post is brief, the next stop is the Events Calendar, then Contacts or Church Map if location or timing matters. If the information still feels thin after that, the problem is not you. The update needs more detail.</p>
+
+<h3>Who do I contact?</h3>
+
+<p>Use <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> for church staff information and <a href="https://ridgecrestchurch.com/contact.php">contact.php</a> if you want the direct contact path. If the matter is location-specific, add the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> to the mix so you are not asking a question that the map already answered.</p>
+
+<h2>Next steps</h2>
+
+<p>If you only remember three things, make them these: read the News page, check the Events Calendar, and contact the church when the update affects you directly. That is enough to stay informed without pretending every announcement will somehow reach you by psychic means.</p>
+
+<p>Start with the <a href="https://ridgecrestchurch.com/news.html">News</a> page, then move to the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for dates, and use <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> or the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> when you need a person, a place, or both. If you want more background on the church itself, the <a href="https://ridgecrestchurch.com/about.html">About Us</a> page is there too.</p>
+
+<p>That is the whole trick. Read the update, identify the action, and move it into your calendar before it evaporates. Basic process. Less drama.</p>

 succeeded in 574ms:
414:			<header class="entry-header">	<h2 class="entry-title" itemprop="headline"><a href="https://ridgecrestchurch.com/how-to-use-news-page-ridgecrest/" rel="bookmark">How to Read and Use Ridgecrest Baptist Church’s News Page (So You Never Miss an Update)</a></h2>
417:	<span class="entry-author" itemprop="author" itemscope="itemscope" itemtype="http://schema.org/Person">by <a href="https://ridgecrestchurch.com/author/felix-rowan/" title="Posts by Felix Rowan" rel="author" class="url fn n" itemprop="url"><span itemprop="name">Felix Rowan</span></a></span>	
420:<a href="https://ridgecrestchurch.com/how-to-use-news-page-ridgecrest/" title="How to Read and Use Ridgecrest Baptist Church’s News Page (So You Never Miss an Update)"><img data-src="https://ridgecrestchurch.com/wp-content/uploads/imports/ridgecrest-home-navigation-screenshot.png" class="wp-post-image lazyload" alt="Phone view of Ridgecrest site navigation with the News page visible" decoding="async" itemprop="image" src="data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==" style="--smush-placeholder-width: 1400px; --smush-placeholder-aspect-ratio: 1400/1050;" /></a><p>A practical guide to navigating Ridgecrest Baptist Church’s News page so you can track announcements, plan ahead, and act on updates without missing the useful part.</p>

codex
Published the News-page guide as a live post with the requested author, two inline site screenshots, and a featured image. I also verified the post URL, confirmed it appears on the `/blog/` index, and checked that the internal links and external calendar-help links are present in the stored content.

Remaining risk: the theme rewrites inline images with lazy-load markup, so the screenshots depend on the front-end JS/image loading behavior for full display. The legacy `news.html`, `contact.php`, and `about.html` links resolve by redirect to the current pages, which is fine but not native file paths.

WP_POST_ID: 119
WP_POST_STATUS: publish
WP_POST_URL: https://ridgecrestchurch.com/how-to-use-news-page-ridgecrest/
WP_AUTHOR_USER: felix-rowan / Felix Rowan
FEATURED_IMAGE_ID: 79
INLINE_IMAGE_IDS: 79,86
LEGACY_PATH_STATUS: not_applicable
BLOG_INDEX_STATUS: ready; /blog/ is published and `page_for_posts` remains `23` (Blog)
LINK_TARGETS_USED: none
VERIFICATION: `wp post get` and `wp post url` passed; `curl` returned `200` for the post; `/blog/` shows the new post; featured image and inline image references were verified in rendered content
diff --git a//home/ubuntu/apps/ridgecrestchurch.com/.tmp/job-548-news-page-article.html b//home/ubuntu/apps/ridgecrestchurch.com/.tmp/job-548-news-page-article.html
new file mode 100644
index 0000000000000000000000000000000000000000..4c0d82a3ccab98ea4bdedcc903ec46a02d26d9f3
--- /dev/null
+++ b//home/ubuntu/apps/ridgecrestchurch.com/.tmp/job-548-news-page-article.html
@@ -0,0 +1,164 @@
+<p><strong><em>The News page is where the church quietly tells you what matters next.</em></strong> Ignore it, and you will keep acting surprised when an event, reminder, or ministry update shows up after the fact. A news page is not decoration. It is the place where Ridgecrest Baptist Church puts the practical details that decide whether you arrive prepared or arrive confused.</p>
+
+<p>If you have ever asked yourself, “What changed?” “Who is this for?” “Do I need to do anything?” or “Why did nobody tell me sooner?”, that is exactly why this page exists. The answer is not mystery. It is usually a date, a topic, a small action item, and your responsibility to read the whole thing instead of the first sentence.</p>
+
+<p>This guide walks through how to use the Ridgecrest News page without pretending attention is automatic. You will learn what belongs there, where to find it, how to scan updates fast, how to turn an announcement into a calendar reminder, and when to use the Events Calendar, Contacts, or Church Map instead of hoping a vague memory will save you.</p>
+
+<p>For context, the Ridgecrest site also keeps related information on the <a href="https://ridgecrestchurch.com/about.html">About Us</a>, <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a>, and <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> pages, so you do not have to guess which page is doing which job. That is the good news. The bad news is that you still have to read the page.</p>
+
+<h2>What the News page is for</h2>
+
+<p>The News page is where short, useful updates live. Not the full history of the church. Not a sermon archive. Not a place for vague encouragement dressed up as information. It is for the kinds of announcements that affect attendance, timing, preparation, or follow-up.</p>
+
+<table>
+  <thead>
+    <tr>
+      <th>What you see</th>
+      <th>What it means</th>
+      <th>What you should do</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Event announcement</td>
+      <td>A dated gathering, deadline, or special church activity</td>
+      <td>Check the time, location, and whether you need to respond</td>
+    </tr>
+    <tr>
+      <td>Ministry update</td>
+      <td>Information for Kids, Youth, volunteers, or a specific group</td>
+      <td>Read whether it applies to you or your household</td>
+    </tr>
+    <tr>
+      <td>Special notice</td>
+      <td>A schedule change, church-wide reminder, or urgent correction</td>
+      <td>Put it on your calendar and stop relying on memory</td>
+    </tr>
+  </tbody>
+</table>
+
+<p>The point is simple: the News page is not there to entertain you. It is there to reduce avoidable confusion. Most church problems are not dramatic. They are just small timing errors repeated by too many people.</p>
+
+<h2>Where to find the News page in the main navigation</h2>
+
+<p>On the site, the News page is part of the main navigation. If you are on desktop, look across the top menu. If you are on a phone, open the navigation menu and look for the same label. No treasure hunt required. Just read the menu instead of tapping at random like a distracted raccoon.</p>
+
+<p>For the live page, use the <a href="https://ridgecrestchurch.com/news.html">News</a> link. The site also keeps a simple front-door version of the page at <a href="https://ridgecrestchurch.com/news/">/news/</a>, so the content is easy to reach either way.</p>
+
+<figure class="wp-block-image alignwide">
+  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/ridgecrest-home-navigation-screenshot.png" alt="Phone view of Ridgecrest church navigation with the News page visible" loading="lazy" />
+  <figcaption>Use the main menu first. That is usually where the answer lives, which is inconvenient for people who prefer guesswork.</figcaption>
+</figure>
+
+<p>If you are already on the homepage, the quickest path is usually: homepage, main menu, News. If you are already on the News page, congratulations, you have won a round of basic navigation. Now read the actual update.</p>
+
+<h2>How to scan an update quickly</h2>
+
+<p>Most people do not need to read every line of a church update with a scholar’s commitment. They need the facts. Look for the parts that change what you do next.</p>
+
+<ul>
+  <li><strong>Date</strong> - When does it happen, and is there a deadline before it?</li>
+  <li><strong>Topic</strong> - What is this about in one sentence?</li>
+  <li><strong>Audience</strong> - Who actually needs this: everyone, parents, students, volunteers, or a specific class?</li>
+  <li><strong>Action needed</strong> - Do you need to RSVP, bring something, sign up, show up early, or do nothing at all?</li>
+</ul>
+
+<p>A practical scan takes less than a minute if you resist the urge to read every word twice. Start with the headline, then the first paragraph, then the date and contact details. If the post does not answer those four questions, keep reading until it does or until it proves it does not know what it is doing.</p>
+
+<p>Here is the working rule: if an update does not tell you when, who, and what next, it is incomplete from a visitor’s point of view. That is not your failure. It is the post’s.</p>
+
+<h3>Fast-read checklist</h3>
+
+<ol>
+  <li>Read the title.</li>
+  <li>Find the date.</li>
+  <li>Check who the update is for.</li>
+  <li>Look for a deadline or response request.</li>
+  <li>Put the event or reminder into your calendar if it matters to you.</li>
+</ol>
+
+<h2>Common types of posts you will see</h2>
+
+<p>The News page usually carries the same kinds of items, because churches are not that mysterious when they finally decide to write things down.</p>
+
+<h3>Service reminders</h3>
+
+<p>These are the simplest posts and the easiest to ignore. Do not. They often confirm service times, special schedules, or location changes. If the church is adjusting a service or class, this is where the update usually lands first.</p>
+
+<h3>Special events</h3>
+
+<p>Events can include fellowship meals, student activities, children’s ministry gatherings, church-wide celebrations, and seasonal services. If there is a deadline, ticket, RSVP, or sign-up, it belongs here. That is the part people forget and then pretend was never mentioned.</p>
+
+<h3>Ministry highlights</h3>
+
+<p>Sometimes the News page highlights what a ministry is doing, who it serves, or how to participate. This is useful because it tells you whether the update is just informational or actually inviting you to act. Most people confuse those two. They should not.</p>
+
+<h3>Prayer needs and follow-up notes</h3>
+
+<p>Not every update is about logistics. Some posts will point readers toward prayer, care, or encouragement. Those updates are different: read them carefully, respond appropriately, and do not treat them like event spam. That is not a good look.</p>
+
+<h2>How to respond to what you read</h2>
+
+<p>The whole point of reading a church update is to do something useful with it. Otherwise you are just collecting information the way some people collect receipts.</p>
+
+<ul>
+  <li><strong>RSVP when asked.</strong> If a post asks for a response, give one. That is not optional decor. It is part of the plan.</li>
+  <li><strong>Bring what the post names.</strong> If the update says bring food, supplies, forms, or a Bible, bring those things instead of improvising your way into inconvenience.</li>
+  <li><strong>Ask questions early.</strong> If the details are unclear, use the contact page before the event. Confusion gets cheaper when it is solved early.</li>
+  <li><strong>Share it with the right person.</strong> If the update affects your family, students, or ministry group, forward it before it disappears into the swamp of unread messages.</li>
+</ul>
+
+<p>When in doubt, use the <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> page or the direct <a href="https://ridgecrestchurch.com/contact.php">contact form</a>. Both land you in the same place emotionally: someone on the church side can answer the question instead of making you guess.</p>
+
+<p>If the update affects where to park, which entrance to use, or when to arrive, check the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> as well. A news item can tell you the plan, but a map tells you where to physically go. Oddly enough, that still matters.</p>
+
+<h2>Planning ahead: turn the news item into a calendar action</h2>
+
+<p>Reading an update is only half the job. The other half is making sure your future self does not quietly sabotage you. If something matters, put it on your personal calendar the same day you read it.</p>
+
+<figure class="wp-block-image alignwide">
+  <img src="https://ridgecrestchurch.com/wp-content/uploads/imports/events-calendar-page-screenshot.png" alt="Ridgecrest Events Calendar page screenshot with schedule and event sections" loading="lazy" />
+  <figcaption>Use the Events Calendar for dates. Use your own calendar for memory. Yes, both. Memory is a terrible project manager.</figcaption>
+</figure>
+
+<p>That can be as simple as copying the date, time, location, and one-line purpose into your phone calendar. If you use Google Calendar, its help page for creating events is a decent place to start: <a href="https://support.google.com/calendar/answer/72143?co=GENIE.Platform%3DDesktop&amp;hl=en&amp;utm_source=ridgecrestchurch.com">Google Calendar’s event creation help</a>. The mechanics are not impressive, but neither is forgetting something you already meant to attend.</p>
+
+<p>Apple users can do the same thing in the iPhone Calendar app, which has its own step-by-step help page: <a href="https://support.apple.com/guide/iphone/create-and-edit-events-in-calendar-iph3d110f84/ios?utm_source=ridgecrestchurch.com">Apple’s Calendar instructions for iPhone</a>. Same principle. Put the thing in the calendar before the week eats it.</p>
+
+<p>If you live in Outlook, the official calendar overview is here: <a href="https://support.microsoft.com/en-us/outlook/calendar/introduction-to-the-outlook-calendar?utm_source=ridgecrestchurch.com">Microsoft’s Outlook Calendar overview</a>. No mystery, no drama, and no excuse for “I meant to go.”</p>
+
+<p>Use reminders for anything that has a deadline or requires preparation. If an event says “bring food,” “arrive early,” or “sign up by Thursday,” that is not optional trivia. It is the actual task.</p>
+
+<h2>How to stay in the loop between Sunday services</h2>
+
+<p>Do not wait until Sunday to discover the thing you were supposed to know on Tuesday. The News page and the Events Calendar work together. One explains what is happening. The other helps you see when it happens.</p>
+
+<ul>
+  <li>Check <a href="https://ridgecrestchurch.com/news.html">News</a> for announcements and changes.</li>
+  <li>Check <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for dates and upcoming gatherings.</li>
+  <li>Check <a href="https://ridgecrestchurch.com/">Home</a> if you want the main site entry point again because you clicked yourself into confusion.</li>
+</ul>
+
+<p>A decent habit is to review News once during the week and again before the weekend. That is enough to catch most updates without treating the church website like a full-time job.</p>
+
+<h2>Quick FAQ</h2>
+
+<h3>What if I missed it?</h3>
+
+<p>Start with the News post and the Events Calendar. If the update included a deadline or sign-up, use the contact page immediately to ask whether anything can still be done. Do not assume silence means the issue disappeared. It usually means you have not checked the right page yet.</p>
+
+<h3>Where do I find the details?</h3>
+
+<p>Use the News page first. If the post is brief, the next stop is the Events Calendar, then Contacts or Church Map if location or timing matters. If the information still feels thin after that, the problem is not you. The update needs more detail.</p>
+
+<h3>Who do I contact?</h3>
+
+<p>Use <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> for church staff information and <a href="https://ridgecrestchurch.com/contact.php">contact.php</a> if you want the direct contact path. If the matter is location-specific, add the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> to the mix so you are not asking a question that the map already answered.</p>
+
+<h2>Next steps</h2>
+
+<p>If you only remember three things, make them these: read the News page, check the Events Calendar, and contact the church when the update affects you directly. That is enough to stay informed without pretending every announcement will somehow reach you by psychic means.</p>
+
+<p>Start with the <a href="https://ridgecrestchurch.com/news.html">News</a> page, then move to the <a href="https://ridgecrestchurch.com/events-calendar/">Events Calendar</a> for dates, and use <a href="https://ridgecrestchurch.com/contacts.html">Contacts</a> or the <a href="https://ridgecrestchurch.com/church-map/">Church Map</a> when you need a person, a place, or both. If you want more background on the church itself, the <a href="https://ridgecrestchurch.com/about.html">About Us</a> page is there too.</p>
+
+<p>That is the whole trick. Read the update, identify the action, and move it into your calendar before it evaporates. Basic process. Less drama.</p>

tokens used
83,436
