# Article Generation Task

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

## Required Runtime

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

## Site Contract

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

## Backlink Targets To Respect

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

## Required Flatlogic/AppWizzy Body Link Target

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

Link placement requirement:

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

## Article Request

- Topic: How to Find the Right Sunday School Class (and Feel at Home Fast)
- 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 97 as the source of truth. Prepared article brief: Working title: How to Find the Right Sunday School Class (and Feel at Home Fast)
Slug hint: how-to-find-right-sunday-school-class
Meta description: A practical guide for choosing a Sunday School class by age, life stage, and interests—plus a first-time checklist to help you feel comfortable at Ridgecrest Baptist Church.

Reader intent:
Help me choose the best Sunday School option and know what to expect so I can attend confidently.

Thesis:
Sunday School feels welcoming fastest when you choose a class that matches your life stage and learning preferences—and when you know what to do before, during, and after your first visit.

Writer brief:
Write an evergreen, visitor-friendly decision guide for Ridgecrest Baptist Church newcomers. Keep the tone calm, practical, and non-promotional: the goal is confidence and clarity, not persuasion. Use the article outline as the backbone, and ensure each section ends with a usable takeaway (a question to ask, a step to try, or a “what to expect” note). Avoid making promises about outcomes (attendance, friendships, spiritual results). Where you reference Ridgecrest-specific navigation, point readers to the site pages (Home, About Us, Ministries, Kids, Youth, Events Calendar/Events, News, Contacts, Church Map, Resources) and suggest what to look for rather than inventing class names or schedules. Include a short mini-decision guide near the end that helps readers pick a next step based on their situation (age/life stage, whether they’re new to church, and whether they prefer discussion vs. teaching).

Author voice notes:
Write in a careful, grounded, visitor-friendly tone. Use first-person sparingly for editorial framing only (e.g., “Here’s a simple way to choose”). Avoid false certainty and avoid invented details about specific classes, attendance, or outcomes. Prefer practical language: “what to look for,” “what to ask,” “what to expect.” Keep the ending usable: a short decision mini-guide and clear next steps to the site’s navigation/contact pages. Light, dry humor is optional but should never undermine seriousness for newcomers.

Key takeaways:
- Start by matching your age/life stage and learning preference, not by trying to “know the right answer.”
- Use the church website navigation to find where Sunday School details live, then ask a simple orientation question.
- First-time comfort comes from small logistics: arrive early, bring a Bible if you have one, and introduce yourself to a leader.
- A typical class includes teaching, discussion or interaction, and prayer—expect a welcoming rhythm rather than a performance.
- If you’re nervous or unsure, you can visit first and choose later; the “next step” is what matters.

Outline:
1. Why Sunday School matters (in plain terms)
   Purpose: Set expectations and reduce anxiety by explaining the purpose of Sunday School in accessible language.
  - Define Sunday School as a regular time for learning Scripture together and building community.
  - Emphasize that it’s designed for real people at different starting points (not only “Bible experts”).
  - Clarify that classes vary in age groups and teaching style, so “right class” = best fit for the person.
2. Start with your “fit”: age group, life stage, and learning preference
   Purpose: Give a simple framework readers can use immediately.
  - Age group: children, youth, adults (use wording that matches the site’s Kids/Youth/Ministries structure).
  - Life stage: new to church, returning, parenting, single/adult, etc. (keep examples general; don’t invent class categories).
  - Learning preference: more discussion vs. more teaching, quieter vs. more interactive (present as “what to look for,” not guarantees).
  - Encourage readers to choose what helps them participate comfortably.
3. How to check what’s available: where to look on the site and what to ask
   Purpose: Direct readers to Ridgecrest navigation and provide concrete questions to ask staff/volunteers.
  - Where to look: point to relevant site pages (Ministries, Kids, Youth, Events Calendar/Events, News).
  - Explain what information readers should scan for: age group, meeting time, location, and whether it’s a discussion-based format.
  - Provide a short list of questions to ask when contacting the church (e.g., “Which class is best for my age group?” “Is there a first-time orientation?” “Where do I go when I arrive?”).
  - Include a gentle reminder that schedules can change—confirm details via Contacts.
4. First-time checklist: what to bring, when to arrive, and how to introduce yourself
   Purpose: Reduce friction for first-time visitors with a practical, non-overlapping checklist.
  - What to bring: Bible if you have one, notebook optional, and any materials your class may request (avoid claiming specific materials).
  - When to arrive: arrive a few minutes early to get oriented (tie to the image caption).
  - How to introduce yourself: a simple opener, asking where to sit/go, and letting leaders know you’re new.
  - Include a “no pressure” note: you can observe first and ask questions later.
5. What happens during a typical class (overview, not a scripted promise)
   Purpose: Set realistic expectations without inventing a specific curriculum or claiming uniform structure.
  - Typical flow: welcome, teaching/lesson time, discussion or guided interaction, and prayer.
  - Explain that class dynamics differ by age group and teacher/leader style.
  - Reassure readers that participating can be as simple as listening and asking one question.
6. Common questions
   Purpose: Answer anxieties directly with careful, non-absolute language.
  - “Do I need to know the Bible already?” → emphasize learning together; no prior knowledge requirement implied.
  - “Can I just visit?” → explain that visiting is normal; encourage confirming where to go.
  - “What if I’m nervous?” → normalize nerves; suggest arriving early and asking an orientation question.
7. How to connect after class: meeting leaders, prayer requests, and next steps
   Purpose: Provide a clear follow-through path that doesn’t overlap with a generic “get involved” guide.
  - Meet the leader/teacher after class; ask what the class focuses on and how to plug in comfortably.
  - Prayer requests: instruct readers to use Contacts or the church’s designated method (do not invent a specific form unless it exists on the site).
  - Next steps: attend again, try a different class if needed, or ask about upcoming events (tie to Events Calendar/News).
8. Quick FAQ + choose-your-next-step mini-guide
   Purpose: Wrap with a decision tool and a final CTA to the site’s navigation/contact points.
  - Mini-guide (bulleted): If you’re a parent of kids → check Kids; if youth → check Youth; if adult/new → check Ministries; if you want to see what’s happening → Events Calendar/News.
  - End with a short “next step” recommendation: visit, ask orientation questions, and confirm details via Contacts.

Internal link plan:
- /: Primary entry point for newcomers; helps readers find the latest navigation and any top-level Sunday School pointers.
- /about/: Supports context and trust by explaining the church’s mission and approach before readers choose a class.
- /ministires/: Use as the main hub for adult/overall ministries discovery (note: confirm the correct slug spelling on-site; the brief lists /ministires/).
- /kids/: Directs parents to the Kids pathway for age-appropriate Sunday School options.
- /youth/: Directs teens/parents to the Youth pathway for age-appropriate Sunday School options.
- /events-calendar/: Lets readers connect Sunday School timing with broader church events; if the site uses /events instead, use that canonical link.

Image direction:
Use a credible real photo from Ridgecrest Baptist Church showing a Sunday School classroom or fellowship area with people in the background (no identifiable minors). Add a simple caption-style overlay: “Arrive a few minutes early—someone will help you get oriented.”

Must include:
- A practical decision framework (age/life stage + learning preference).
- Clear guidance on where to look on the Ridgecrest site (Kids, Youth, Ministries, Events Calendar/News).
- A first-time comfort checklist that does not duplicate a Sunday service planning checklist.
- A section addressing common newcomer questions (Bible knowledge, visiting, nervousness).
- A brief “choose-your-next-step” mini-guide near the end.
- At least one CTA to Contacts (via the site) for confirming class details and orientation.

Avoid:
- Inventing specific Sunday School class names, teachers, locations, or schedules that are not provided on the site.
- Promises about outcomes (e.g., “you will make friends,” “you will feel at home immediately,” “everyone participates”).
- Generic “how to get involved” content that overlaps with a separate first-timer ministries guide.
- Repeating a Sunday service checklist (parking, worship order, communion specifics, etc.).
- Unverifiable claims or fake citations.
- Linking to unrelated commercial sites.

Quality checklist:
- Every major section ends with a usable takeaway (question, step, or expectation).
- No fabricated Ridgecrest-specific details (class lists, times, formats) unless present in the site content.
- Tone is welcoming, calm, and non-commercial/informational.
- Internal links match the required navigation structure and use correct slugs (verify /ministires/ spelling and whether /events-calendar/ or /events is canonical).
- Image direction is feasible: real photo, no identifiable minors, caption overlay included.
- CTA points to Contacts and relevant navigation pages for next steps. Article kind: evergreen Research status: not_required Reader intent: Help me choose the best Sunday School option and know what to expect so I can attend confidently. Planned outline: Why Sunday School matters (in plain terms) | Start with your “fit”: age group, life stage, and learning preference | How to check what’s available: where to look on the site and what to ask | First-time checklist: what to bring, when to arrive, and how to introduce yourself | What happens during a typical class (overview, not a scripted promise) | Common questions: “Do I need to know the Bible already?” “Can I just visit?” “What if I’m nervous?” | How to connect after class: meeting leaders, prayer requests, and next steps | Quick FAQ and a short “choose-your-next-step” decision mini-guide Image direction: A real photo of a church Sunday School classroom or fellowship area (people in the background, no identifiable minors), with a simple caption-style overlay: “Arrive a few minutes early—someone will help you get oriented.” Preferred internal links: /, /about/, /ministires/, /kids/, /youth/, /events-calendar/ (or /events) Avoid: Repeating the existing checklist for planning a Sunday service, Generic ‘how to get involved’ content that overlaps with the first-timer ministries guide, Posting any unverifiable claims about specific class attendance or outcomes, Linking to unrelated commercial sites

## Selected Article Content Plan Item

- Plan item ID: 97
- Plan order: 7
- Article kind: evergreen
- Planned title: How to Find the Right Sunday School Class (and Feel at Home Fast)
- Slug hint: how-to-find-right-sunday-school-class
- Reader intent: Help me choose the best Sunday School option and know what to expect so I can attend confidently.
- Angle: Practical, visitor-friendly decision guide that helps newcomers choose a class based on age, interests, and schedule—plus tips for first-time comfort at Ridgecrest Baptist Church.
- Image direction: A real photo of a church Sunday School classroom or fellowship area (people in the background, no identifiable minors), with a simple caption-style overlay: “Arrive a few minutes early—someone will help you get oriented.”
- Author hint: Use the selected virtual author.

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

Outline:
- Why Sunday School matters (in plain terms)
- Start with your “fit”: age group, life stage, and learning preference
- How to check what’s available: where to look on the site and what to ask
- First-time checklist: what to bring, when to arrive, and how to introduce yourself
- What happens during a typical class (overview, not a scripted promise)
- Common questions: “Do I need to know the Bible already?” “Can I just visit?” “What if I’m nervous?”
- How to connect after class: meeting leaders, prayer requests, and next steps
- Quick FAQ and a short “choose-your-next-step” decision mini-guide

Preferred internal link targets:
- /
- /about/
- /ministires/
- /kids/
- /youth/
- /events-calendar/ (or /events)

Avoid:
- Repeating the existing checklist for planning a Sunday service
- Generic ‘how to get involved’ content that overlaps with the first-timer ministries guide
- Posting any unverifiable claims about specific class attendance or outcomes
- Linking to unrelated commercial sites

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

## Final Report Requirements

End your final message with these machine-readable lines:

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

Also briefly mention what you verified and any limitations.