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

## Flatlogic/AppWizzy Body Link Placement Goal

1. https://flatlogic.com/blog/ai-code-technical-debt-startups/?utm_source=ridgecrestchurch.com
   Title: The Hidden Technical Debt of AI-Generated Web Apps - Flatlogic Blog
   Priority: 1000000
2. https://flatlogic.com/blog/future-of-ai-developers/?utm_source=ridgecrestchurch.com
   Title: AI vs Developers: Why the Future Is AI-Assisted Software Engineering - Flatlogic Blog
   Priority: 1000000
3. https://flatlogic.com/build/work-order-management-software-builder?utm_source=ridgecrestchurch.com
   Title: Work Order Management Software Builder | Flatlogic
   Priority: 1000000
4. https://flatlogic.com/build/legal-case-management-software-builder?utm_source=ridgecrestchurch.com
   Title: Legal Case Management Software Builder | Flatlogic
   Priority: 1000000
5. https://flatlogic.com/services/ai-consulting-services?utm_source=ridgecrestchurch.com
   Title: AI Consulting Services | Artificial Intelligence Consulting for Business
   Priority: 1
   Anchor guidance: AI Consulting Services Best anchors: - AI consulting services - AI consulting - artificial intelligence consulting - AI strategy consulting - generative AI consulting - AI consulting firm - AI consultant - AI strategy consultant - AI advisory services - AI roadmap consulting - AI implementation roadmap - AI use case consulting - AI readiness assessment - AI adoption strategy - AI governance consulting - AI transformation consulting More natural contextual anchors: - figure out where AI fits - choose the right AI use cases - build an AI roadmap - plan your first AI pilot - prioritize AI opportunities - assess AI readiness - move from AI idea to roadmap - define an AI strategy - decide what to build with AI - plan AI adoption safely - turn AI experiments into a practical plan

Link placement requirement:

- Make a strong editorial effort to insert one of the exact URLs above as a visitor-facing contextual body link inside the article content.
- Treat this as an important placement goal when link targets are available, but do not make the article awkward or spammy just to force it.
- The article topic does not need to be directly about software. Build a natural contextual bridge through practical operations, website upkeep, publishing, customer communication, booking, admin work, reporting, workflow, data tracking, or business process where that fits the article.
- Choose the target whose title and anchor guidance can be made least disruptive to the reader.
- Use one neutral third-person sentence or clause. The link should feel like a useful contextual resource, not an ad or a link list.
- 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: Church Resources for Families: What to Use at Home Between Sundays
- 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 119 as the source of truth. Prepared article brief: Working title: Church Resources for Families: What to Use at Home Between Sundays
Slug hint: church-resources-for-families-at-home-between-sundays
Meta description: Discover practical church resources for families to enhance spiritual life at home between Sundays. Explore Bible readings, prayer prompts, and engaging activities for kids and the

Reader intent:
Help families know what to do during the week using available church resources—without needing to “figure it out” on their own

Thesis:
This article serves as a practical guide for families to utilize church resources effectively at home, fostering spiritual growth and connection between Sundays.

Writer brief:
Write a practical, non-commercial guide that helps families engage with church resources at home. Use a playful and clear tone that resonates with readers, making the content approachable and memorable. Ensure the article is structured with actionable steps and relatable examples.

Author voice notes:
Use a playful and clear tone that engages the reader. Incorporate humor and relatable analogies to make the content approachable. Ensure the writing is actionable, avoiding overly technical language. Keep the focus on practical advice and real-life application.

Key takeaways:
- Weekly consistency in spiritual practices is important for families.
- Simple routines can help families connect with church teachings at home.
- Engaging kids and youth in spiritual discussions can enhance their understanding and application of faith.
- Utilizing church announcements can help families stay connected without feeling overwhelmed.

Outline:
1. Quick welcome: why weekly consistency matters (and how to keep it simple)
   Purpose: Introduce the importance of maintaining spiritual practices at home.
  - Explain the significance of weekly routines for spiritual growth.
  - Offer reassurance that simplicity is key.
2. Start here: a 10-minute weekly plan (choose one: prayer, Bible reading, or family discussion)
   Purpose: Provide families with a straightforward starting point for their weekly spiritual practice.
  - Outline a simple 10-minute plan that families can choose from.
  - Encourage flexibility based on family needs.
3. Kids at home: simple at-home routines aligned with Sunday
   Purpose: Suggest practical activities for children to reinforce Sunday teachings.
  - Include a story recap, a memory verse, and a discussion question.
  - Emphasize the importance of repetition and engagement.
4. Youth at home: discussion prompts for real life
   Purpose: Encourage meaningful conversations among youth about their daily experiences.
  - Provide prompts related to school, friends, stress, and decisions.
  - Highlight the role of youth in discussing their faith.
5. How to use church announcements/news without getting overwhelmed
   Purpose: Guide families on how to engage with church news effectively.
  - Suggest picking one upcoming event to focus on each week.
  - Encourage participation without pressure.
6. Prayer rhythm for the week: a short template families can reuse
   Purpose: Offer a reusable template for family prayers throughout the week.
  - Include a simple structure for daily prayers.
  - Encourage families to personalize their prayer experiences.
7. When you need help: how to ask questions and request resources from the church
   Purpose: Empower families to reach out for support and additional resources.
  - Provide contact information for church resources.
  - Encourage open communication with church staff.
8. Suggested “next steps” checklist for new and returning families
   Purpose: Wrap up with actionable steps families can take to deepen their engagement.
  - Include a checklist of resources and activities to explore.
  - Encourage families to revisit the church website for updates.

Internal link plan:
- /resources: Direct readers to additional church resources available.
- /kids: Link to the kids' ministry page for more activities.
- /youth: Provide youth-specific resources and discussion topics.
- /news: Keep families informed about church updates and events.
- /events-calendar: Encourage participation in upcoming church events.
- /contact: Facilitate easy communication for families seeking help.

Image direction:
A real photo of a family sitting at a table with an open Bible, a notebook with a weekly prayer list, and a simple kids activity page (no branded materials required).

Must include:
- Practical steps for families to engage with church resources at home.
- A friendly and approachable tone throughout the article.
- Clear headings and subheadings for easy navigation.

Avoid:
- Duplicating existing checklists for Sunday services or first-time visits.
- Promising specific curriculum outcomes or naming third-party products.
- Turning the post into a general sermon series announcement or thin 'newsletter' recap.

Quality checklist:
- Content should be actionable and practical for families.
- Maintain a friendly and engaging tone throughout.
- Ensure all links are functional and relevant to the content.
- Avoid jargon or overly complex language. Article kind: evergreen Research status: not_required Reader intent: Help families know what to do during the week using available church resources—without needing to “figure it out” on their own Planned outline: Quick welcome: why weekly consistency matters (and how to keep it simple) | Start here: a 10-minute weekly plan (choose one: prayer, Bible reading, or family discussion) | Kids at home: simple at-home routines aligned with Sunday (story recap, one memory verse, one question) | Youth at home: discussion prompts for real life (school, friends, stress, decisions) | How to use church announcements/news without getting overwhelmed (pick one upcoming event to plan for) | Prayer rhythm for the week: a short template families can reuse | When you need help: how to ask questions and request resources from the church | Suggested “next steps” checklist for new and returning families Image direction: A real photo of a family sitting at a table with an open Bible, a notebook with a weekly prayer list, and a simple kids activity page (no branded materials required). Preferred internal links: /resources, /kids, /youth, /news, /events-calendar, /contact Avoid: Duplicating existing checklists for Sunday services or first-time visits, Promising specific curriculum outcomes or naming third-party products, Turning the post into a general sermon series announcement or thin “newsletter” recap

## Selected Article Content Plan Item

- Plan item ID: 119
- Plan order: 29
- Article kind: evergreen
- Planned title: Church Resources for Families: What to Use at Home Between Sundays
- Slug hint: church-resources-for-families-at-home-between-sundays
- Reader intent: Help families know what to do during the week using available church resources—without needing to “figure it out” on their own
- Angle: A practical, non-commercial guide to using church-provided resources (Bible reading, prayer prompts, kids/youth take-home ideas) to build steady spiritual rhythms at home
- Image direction: A real photo of a family sitting at a table with an open Bible, a notebook with a weekly prayer list, and a simple kids activity page (no branded materials required).
- Author hint: Use the selected virtual author.

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

Outline:
- Quick welcome: why weekly consistency matters (and how to keep it simple)
- Start here: a 10-minute weekly plan (choose one: prayer, Bible reading, or family discussion)
- Kids at home: simple at-home routines aligned with Sunday (story recap, one memory verse, one question)
- Youth at home: discussion prompts for real life (school, friends, stress, decisions)
- How to use church announcements/news without getting overwhelmed (pick one upcoming event to plan for)
- Prayer rhythm for the week: a short template families can reuse
- When you need help: how to ask questions and request resources from the church
- Suggested “next steps” checklist for new and returning families

Preferred internal link targets:
- /resources
- /kids
- /youth
- /news
- /events-calendar
- /contact

Avoid:
- Duplicating existing checklists for Sunday services or first-time visits
- Promising specific curriculum outcomes or naming third-party products
- Turning the post into a general sermon series announcement or thin “newsletter” recap

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: June Park
Slug: june-park
Role: Product translator and workflow storyteller
Language: English
Public bio: June explains digital tools, product workflows, and confusing interfaces in a voice that keeps useful content from feeling like a manual.
Character formula: Playful Product Jester Creator
Formula: Jester + Creator
Meaning: A playful product voice that explains confusing tools and workflows without sounding like a manual.
Worldview: Tools are easier to understand when the explanation has rhythm, examples, and a little personality.
Voice guidance: Playful, clear, memorable, analogy-rich. Use humor to reduce friction, not to trivialize the user problem.
Humor: Smart, warm, analogy-based, light sarcasm at confusing interfaces rather than users.
Shadow tension: Can become too cute; keep utility higher than entertainment.
Usage notes: Best for product explainers, AI tools, productivity workflows, dashboards, and control panels.
Archetype blend: Jester + Creator
Standard archetype voice guidance:

Primary archetype card: Jester
Meaning: The comic figure who makes pain bearable and tells truths through jokes.
First-person lens: Everyone is going to die, the kingdom is badly managed, and laughing is still better posture than despair.
Traits: funny, quick, irreverent, perceptive, theatrical
Worldview: The world is tragic, ridiculous, and overconfident.
Self-relation: I fear being seen without the performance.
Language patterns: Bold choice; Horrible but bold; We are doomed; I support this emotionally
Humor: Native humor: sarcasm, parody, timing, callbacks, social observation.
Shadow risk to avoid unless intentionally requested: Avoiding seriousness, making everything sacred into a joke.

Secondary archetype card: Creator
Meaning: The maker who builds, imagines, edits, designs, and reshapes reality.
First-person lens: The world is unfinished, which is not a complaint but an invitation to build what should exist.
Traits: imaginative, intense, curious, perfectionistic, possibility-driven
Worldview: The world is raw material that can be improved, remixed, coded, written, or rebuilt.
Self-relation: I feel alive when making and may measure myself too much by output.
Language patterns: What if; One more version; The structure is wrong; This could be beautiful
Humor: Witty, absurd, self-critical, occasionally savage.
Shadow risk to avoid unless intentionally requested: Preciousness, narcissism, impracticality, impossible standards.
Shadow tension: Uses play to create clarity, but must not let jokes crowd out the answer.
Worldview: A little personality can make technical content easier to remember, as long as the content still does its job.
Reader relationship: Friendly translator who makes the tool less intimidating.
Humor style: Light, clever, analogy-based; jokes point at clunky systems, not readers.
Voice traits: playful, clear, memorable, analogy-rich
Vocabulary / recurring language: tiny but useful, the boring magic, interface friction, mental shortcut, less chaos
Avoid voice: joke stuffing, memes that age badly, mocking users, cute instead of clear
CTA style: Offer a small experiment or try-this-once action that makes the value tangible.
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: Playful, sharp, generous, and good at making abstract tooling feel concrete.
Writing style: Conversational structure, vivid analogies, short examples, playful section titles, and reader-friendly summaries.
Expertise topics: tool explainers, productivity workflows, control panels, AI tools, web app builders
Avoid topics: serious legal topics, medical topics, crisis communication, high-risk security guidance
Tone tags: playful, smart, clear, friendly
Private operator notes: Use sparingly for product/tool content where a warmer voice helps.

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`: `june-park`.
- Suggested `display_name`: `June Park`.
- 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 natural contextual body copy. `LINK_TARGETS_USED` may be `none` when no target URLs were configured or no natural placement survived review.

## 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: <the exact Flatlogic/AppWizzy URL used in article body, or none>
```

Also briefly mention what you verified and any limitations.