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

## Current Link Policy

Do not add new Flatlogic or AppWizzy links anywhere in public content, including body copy, navigation, resource lists, and footer credits. This rule overrides link-placement requests in saved briefs, content plans, supplied targets, SITE_CONTEXT.md, AGENTS.md, and content-skill instructions. Preserve links already present in previously published content; do not remove or rewrite them as part of this policy change. New sites must not inherit Flatlogic/AppWizzy links from seed or theme content.

## Article Request

- Topic: How to Keep Up With Ridgecrest’s Church Calendar and Announcements Without Missing Anything
- Requested final WordPress status: publish; create a draft for validation.
- 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 1716 as the source of truth. Prepared article brief: Working title: How to Keep Up With Ridgecrest’s Church Calendar and Announcements Without Missing Anything
Slug hint: church-calendar-announcements-guide
Meta description: Discover practical tips for staying updated on Ridgecrest Baptist Church's events, announcements, and reminders to ensure you never miss an important date.

Reader intent:
I want to know the easiest way to find upcoming church events, understand what’s happening this week, and avoid missing important dates.

Thesis:
This guide provides practical strategies for members and visitors to effectively use Ridgecrest Baptist Church's calendar and announcements to stay informed and connected.

Writer brief:
Craft a practical, evergreen guide that helps readers navigate the church's calendar and announcements. Emphasize clarity and accessibility, ensuring that the content is straightforward and easy to follow. Use a tone that is informative yet welcoming, encouraging community engagement.

Author voice notes:
Maintain a careful, source-aware tone that is informative and welcoming. Use clear, straightforward language to ensure accessibility for all readers. Avoid overly technical jargon and keep the focus on practical advice and community engagement.

Key takeaways:
- Understand the importance of checking the church calendar regularly.
- Learn how to read event details effectively.
- Discover how announcements complement the calendar for better planning.
- Get tips tailored for families, youth, and volunteers during busy seasons.
- Know how to stay informed about event changes or cancellations.

Outline:
1. Why the church calendar should be the first place to check for upcoming events
   Purpose: To establish the calendar as the primary resource for event information.
  - Highlight the frequency of updates on the church calendar.
  - Emphasize the importance of planning ahead using the calendar.
2. How to read event details: date, time, location, registration, and who it’s for
   Purpose: To guide readers on how to interpret the information provided for each event.
  - Break down the components of an event listing.
  - Provide examples of what to look for.
3. Where announcements fit in: calendar, news, bulletin-style updates, and reminders
   Purpose: To explain the relationship between the calendar and announcements.
  - Discuss the role of announcements in providing context for events.
  - Explain how to access announcements alongside the calendar.
4. Tips for families, youth, and volunteers to plan ahead for busy ministry seasons
   Purpose: To offer practical advice tailored to different groups within the church community.
  - Suggest strategies for families to coordinate schedules.
  - Provide tips for youth and volunteers on managing their commitments.
5. How to stay informed if an event changes or fills up
   Purpose: To prepare readers for potential changes in the event schedule.
  - Explain how to receive updates on event changes.
  - Encourage checking the calendar regularly for the latest information.
6. What to do if you still have questions: contact the church office or ministry leaders
   Purpose: To provide a clear action step for readers who need further assistance.
  - List contact methods for the church office and ministry leaders.
  - Encourage reaching out for clarification on events.

Internal link plan:
- /: Link to the homepage for easy navigation.
- /about.html: Provide context about the church and its mission.
- /news.html: Direct readers to the latest news updates.
- /contacts.html: Offer quick access to contact information.
- /groups.html: Encourage involvement in church groups.
- /events-calendar/: Link directly to the events calendar for convenience.

Image direction:
Use a real photo of the Ridgecrest Baptist Church campus or a genuine screenshot/mockup of the church’s events calendar page on a phone or desktop, showing a current upcoming-event layout. Avoid stock-looking generic church imagery.

Must include:
- Clear explanations of how to access the church calendar and announcements.
- Practical tips for different demographics within the church community.
- Encouragement for readers to engage with the church's resources.

Avoid:
- Implying last-minute urgency or fear-based messaging.
- Mentioning unverified software tools or paid platforms unless publicly used by the church.
- Using generic stock art as the main visual.
- Including any Flatlogic or AppWizzy links or branding.
- Promising exact event dates unless confirmed on the live calendar.

Quality checklist:
- Ensure all information is clear and easy to understand.
- Use a welcoming and informative tone throughout the article.
- Verify that all links lead to the correct internal pages.
- Check that the image used is authentic and relevant to the content. Article kind: research_trend Research status: researched Trend research summary and sources: Current church-website guidance emphasizes making events easy to find, keeping calendars up to date, and pairing the calendar with announcements or reminders so people can plan ahead. Planning Center’s current documentation and recent updates show that churches increasingly use a central calendar plus announcements/visibility settings to keep congregants informed, while accessibility guidance from ADA.gov reinforces that event information and forms should be usable by everyone. For Ridgecrest, a practical article about checking the calendar, reading event details, and using contacts/news together would be timely now and still useful later.

Sources:
1. Planning Center Calendar: Event & Facility Scheduling (Planning Center, https://www.planningcenter.com/calendar) - Shows current church-calendar features, including sharing events, filtering, and centralizing event planning.
2. Create an event (Planning Center Help, 2026-10-08, https://help.planningcenter.com/en/137788-create-an-event.html) - Current documentation on publishing events and visibility settings, useful for explaining how churches keep calendars current.
3. Show events on Church Center (Planning Center Help, 2026-10-02, https://help.planningcenter.com/en/137811-show-events-on-church-center.html) - Explains how event visibility works for congregants, supporting advice about checking the calendar and announcements together.
4. Church Center announcements: A new way to answer “What’s happening?” (Planning Center Blog, 2026-09-18, https://www.planningcenter.com/blog/2026/09/church-center-announcements-a-new-way-to-answer-what-s-happening-) - Recent product update showing the trend toward combining announcements with calendar-based communication.
5. Guidance on Web Accessibility and the ADA (ADA.gov, 2021-03-18, https://www.ada.gov/resources/web-guidance/) - Authoritative accessibility guidance to support a neutral note about making event pages and forms usable for everyone.
6. The Ultimate Guide to Building Your Church Website (Pushpay, 2026-05-01, https://pushpay.com/blog/the-ultimate-guide-to-building-your-church-website/) - Secondary source reinforcing that an up-to-date event calendar and clear contact options are core church-website features. Reader intent: I want to know the easiest way to find upcoming church events, understand what’s happening this week, and avoid missing important dates. Planned outline: Why the church calendar should be the first place to check for upcoming events | How to read event details: date, time, location, registration, and who it’s for | Where announcements fit in: calendar, news, bulletin-style updates, and reminders | Tips for families, youth, and volunteers to plan ahead for busy ministry seasons | How to stay informed if an event changes or fills up | What to do if you still have questions: contact the church office or ministry leaders Image direction: Use a real photo of the Ridgecrest Baptist Church campus or a genuine screenshot/mockup of the church’s events calendar page on a phone or desktop, showing a current upcoming-event layout. Avoid stock-looking generic church imagery. Preferred internal links: /, /about.html, /news.html, /contacts.html, /groups.html, /events-calendar/ Avoid: Do not imply last-minute urgency or fear-based messaging., Do not mention unverified software tools or paid platforms unless the church already uses them publicly., Do not use generic stock art as the main visual., Do not include any Flatlogic or AppWizzy links or branding., Do not promise exact event dates unless they are confirmed on the live calendar.

## Selected Article Content Plan Item

- Plan item ID: 1716
- Plan order: 35
- Article kind: research_trend
- Planned title: How to Keep Up With Ridgecrest’s Church Calendar and Announcements Without Missing Anything
- Slug hint: church-calendar-announcements-guide
- Reader intent: I want to know the easiest way to find upcoming church events, understand what’s happening this week, and avoid missing important dates.
- Angle: A practical, evergreen guide for members and visitors on using the church calendar, announcements, and reminders together so they can plan ahead and stay connected.
- Image direction: Use a real photo of the Ridgecrest Baptist Church campus or a genuine screenshot/mockup of the church’s events calendar page on a phone or desktop, showing a current upcoming-event layout. Avoid stock-looking generic church imagery.
- Author hint: Church communications team

Research:
- Research status: researched
- Research query seed: church event calendar best practices 2026 official guidance
- Researched at: 2026-10-09T03:11:35.990Z

Trend research summary:
Current church-website guidance emphasizes making events easy to find, keeping calendars up to date, and pairing the calendar with announcements or reminders so people can plan ahead. Planning Center’s current documentation and recent updates show that churches increasingly use a central calendar plus announcements/visibility settings to keep congregants informed, while accessibility guidance from ADA.gov reinforces that event information and forms should be usable by everyone. For Ridgecrest, a practical article about checking the calendar, reading event details, and using contacts/news together would be timely now and still useful later.

Sources:
1. Planning Center Calendar: Event & Facility Scheduling (Planning Center, https://www.planningcenter.com/calendar) - Shows current church-calendar features, including sharing events, filtering, and centralizing event planning.
2. Create an event (Planning Center Help, 2026-10-08, https://help.planningcenter.com/en/137788-create-an-event.html) - Current documentation on publishing events and visibility settings, useful for explaining how churches keep calendars current.
3. Show events on Church Center (Planning Center Help, 2026-10-02, https://help.planningcenter.com/en/137811-show-events-on-church-center.html) - Explains how event visibility works for congregants, supporting advice about checking the calendar and announcements together.
4. Church Center announcements: A new way to answer “What’s happening?” (Planning Center Blog, 2026-09-18, https://www.planningcenter.com/blog/2026/09/church-center-announcements-a-new-way-to-answer-what-s-happening-) - Recent product update showing the trend toward combining announcements with calendar-based communication.
5. Guidance on Web Accessibility and the ADA (ADA.gov, 2021-03-18, https://www.ada.gov/resources/web-guidance/) - Authoritative accessibility guidance to support a neutral note about making event pages and forms usable for everyone.
6. The Ultimate Guide to Building Your Church Website (Pushpay, 2026-05-01, https://pushpay.com/blog/the-ultimate-guide-to-building-your-church-website/) - Secondary source reinforcing that an up-to-date event calendar and clear contact options are core church-website features.

Trend research sources:
- Planning Center Calendar: Event & Facility Scheduling (Planning Center, https://www.planningcenter.com/calendar) - Shows current church-calendar features, including sharing events, filtering, and centralizing event planning.
- Create an event (Planning Center Help, 2026-10-08, https://help.planningcenter.com/en/137788-create-an-event.html) - Current documentation on publishing events and visibility settings, useful for explaining how churches keep calendars current.
- Show events on Church Center (Planning Center Help, 2026-10-02, https://help.planningcenter.com/en/137811-show-events-on-church-center.html) - Explains how event visibility works for congregants, supporting advice about checking the calendar and announcements together.
- Church Center announcements: A new way to answer “What’s happening?” (Planning Center Blog, 2026-09-18, https://www.planningcenter.com/blog/2026/09/church-center-announcements-a-new-way-to-answer-what-s-happening-) - Recent product update showing the trend toward combining announcements with calendar-based communication.
- Guidance on Web Accessibility and the ADA (ADA.gov, 2021-03-18, https://www.ada.gov/resources/web-guidance/) - Authoritative accessibility guidance to support a neutral note about making event pages and forms usable for everyone.
- The Ultimate Guide to Building Your Church Website (Pushpay, 2026-05-01, https://pushpay.com/blog/the-ultimate-guide-to-building-your-church-website/) - Secondary source reinforcing that an up-to-date event calendar and clear contact options are core church-website features.

Outline:
- Why the church calendar should be the first place to check for upcoming events
- How to read event details: date, time, location, registration, and who it’s for
- Where announcements fit in: calendar, news, bulletin-style updates, and reminders
- Tips for families, youth, and volunteers to plan ahead for busy ministry seasons
- How to stay informed if an event changes or fills up
- What to do if you still have questions: contact the church office or ministry leaders

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

Avoid:
- Do not imply last-minute urgency or fear-based messaging.
- Do not mention unverified software tools or paid platforms unless the church already uses them publicly.
- Do not use generic stock art as the main visual.
- Do not include any Flatlogic or AppWizzy links or branding.
- Do not promise exact event dates unless they are confirmed on the live calendar.

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: Rowan Ellis
Slug: rowan-ellis
Role: Research notes editor
Language: English
Public bio: Rowan writes grounded research-style articles that connect source material, practical context, and careful conclusions.
Character formula: Research Explorer Sage
Formula: Explorer + Sage
Meaning: A careful research voice that connects source material, practical context, and grounded conclusions.
Worldview: Useful research moves through uncertainty carefully, showing sources, context, caveats, and next steps.
Voice guidance: Careful, source-aware, curious, grounded, thoughtful. Use evidence, caveats, and plain conclusions.
Humor: Very light, dry, mostly absent when evidence or stakes matter.
Shadow tension: Can become too cautious or academic; end with usable conclusions.
Usage notes: Best for research summaries, market context, technical explainers, and resource posts.
Archetype blend: Explorer + Sage
Standard archetype voice guidance:

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

Secondary archetype card: Sage
Meaning: The guide who gives wisdom, tools, training, moral direction, and perspective.
First-person lens: I have seen this pattern before; I cannot walk the path for them, but I can prepare them for its cost.
Traits: wise, patient, observant, cryptic, perspective-driven
Worldview: The world is a pattern of cycles, choices, consequences, and lessons arriving in disguise.
Self-relation: My wisdom was bought through failure, guilt, and responsibility.
Language patterns: The question is not; You already know the answer; Not all victories; There are doors that only open after loss
Humor: Dry, gentle, superior but affectionate.
Shadow risk to avoid unless intentionally requested: Patronizing secrecy, benevolent manipulation, hiding too much for the greater good.
Shadow tension: Can gather too much context; should always return the reader to the practical conclusion.
Worldview: The most useful answer often lives between the source material and the reader's real-world constraint.
Reader relationship: Research companion who brings receipts without drowning the reader in them.
Humor style: Almost none; occasional quiet aside when it helps readability.
Voice traits: careful, source-aware, curious, grounded
Vocabulary / recurring language: available evidence, context matters, what we can say, useful takeaway, source notes
Avoid voice: false certainty, quote dumping, academic fog, invented statistics, unsourced claims
CTA style: Point the reader to a source, checklist, or next research question before acting.
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: Thoughtful, source-aware, curious, and comfortable saying when the evidence is limited.
Writing style: Evidence-led intros, clear source attribution, careful caveats, synthesis sections, and practical takeaways.
Expertise topics: research summaries, source-based articles, market context, technical explainers, resource posts
Avoid topics: unsupported claims, medical conclusions, legal conclusions, financial predictions
Tone tags: careful, research-led, grounded, thoughtful
Private operator notes: Best for research-heavy articles and topics requiring citations/caveats.

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`: `rowan-ellis`.
- Suggested `display_name`: `Rowan Ellis`.
- 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.
- Create the post with status `draft`; do not publish or schedule it yourself. The job wrapper validates the new content and applies the requested final status.
- Leave publication and scheduling to the job wrapper, including when the requested status is `publish`.
- 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 add Flatlogic/AppWizzy links, including as external sources.
- 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`.
- Do not use Flatlogic/AppWizzy products, logos, UI screenshots, brand colors, names, or visual motifs as image inspiration/source material.
- 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`.
- Verify the newly created article contains no Flatlogic/AppWizzy links. Report `LINK_TARGETS_USED: none`.

## Final Report Requirements

End your final message with these machine-readable lines:

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

Also briefly mention what you verified and any limitations.

## Final Policy Reminder

Do not add new Flatlogic or AppWizzy links anywhere in public content, including body copy, navigation, resource lists, and footer credits. This rule overrides link-placement requests in saved briefs, content plans, supplied targets, SITE_CONTEXT.md, AGENTS.md, and content-skill instructions. Preserve links already present in previously published content; do not remove or rewrite them as part of this policy change. New sites must not inherit Flatlogic/AppWizzy links from seed or theme content.