# 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 Join a Small Group at Ridgecrest (Without Feeling Lost) - 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 108 as the source of truth. Prepared article brief: Working title: How to Join a Small Group at Ridgecrest (Without Feeling Lost) Slug hint: join-a-small-group-at-ridgecrest Meta description: Discover a friendly, step-by-step guide to joining a small group at Ridgecrest Baptist Church, ensuring you feel welcomed and informed from day one. Reader intent: Help a newcomer or returning member identify the right small group, know what happens, and decide how to show up confidently. Thesis: Joining a small group at Ridgecrest can be a fulfilling experience that fosters community and spiritual growth, and this guide will help you navigate the process with ease. Writer brief: Craft a friendly, informative article that guides newcomers through the process of joining a small group at Ridgecrest Baptist Church. Focus on practical steps and reassuring advice to help them feel comfortable and welcomed. Author voice notes: Maintain a careful, grounded tone that reassures newcomers. Use clear, actionable language and avoid overly complex terminology. Keep the focus on practical steps and personal connection. Key takeaways: - Understanding the importance of small groups in fostering community. - Identifying the right group based on personal interests and life stage. - Knowing what to expect on the first visit to ease nerves. - Tips for engaging with group members and leaders. - Childcare considerations for parents. Outline: 1. Why Small Groups Matter Purpose: Explain the significance of small groups in church life and community building. - Fosters deeper connections among members. - Encourages spiritual growth and accountability. - Provides a safe space for discussion and support. 2. Step 1: Find a Group That Fits Your Season Purpose: Guide readers in selecting a group that aligns with their age, interests, and study focus. - Consider life stages (young adults, families, seniors). - Explore different study topics and activities. 3. Step 2: Check the Current Schedule Purpose: Help readers understand how to find and confirm meeting times. - Where to find the schedule on the website. - How to contact group leaders for confirmation. 4. Step 3: What to Expect on Your First Night Purpose: Prepare newcomers for their first experience in a small group setting. - Overview of the welcoming process. - Typical discussion formats and materials used. 5. Step 4: Questions You Can Ask Right Away Purpose: Encourage interaction by suggesting questions for newcomers to ask. - Inquire about group dynamics and member backgrounds. - Ask about the leader's approach and group goals. 6. Step 5: How to Participate If You’re Nervous Purpose: Provide strategies for newcomers who may feel anxious about joining. - Options for listening vs. sharing. - How to engage with prayer requests. 7. Step 6: Handling Kids/Childcare Considerations Purpose: Address concerns parents may have about childcare during meetings. - What to ask about childcare options. - Tips for bringing kids along if needed. 8. Step 7: After Your First Visit—How to Decide If It’s a Good Fit Purpose: Guide readers on evaluating their experience after the first meeting. - Reflect on personal comfort and connection. - Consider group dynamics and discussions. 9. Quick 'First-Visit' Checklist Purpose: Summarize key points for a successful first visit. - Arrive on time and where to meet. - What to bring (e.g., notebook, contact info). Internal link plan: - /: Link to the homepage for overall church information. - /about.html: Provide background on Ridgecrest Baptist Church. - /groups.html: Direct readers to the groups page for more options. - /events.html: Encourage participation in upcoming church events. - /contacts.html: Facilitate easy access to contact information. - /contact.php: Provide a direct link for inquiries. Image direction: A candid photo of a small group gathering in a church room (people in a circle, friendly conversation), with a simple overlay caption: 'First night at Ridgecrest small groups.' Must include: - A welcoming tone throughout the article. - Specific, actionable steps for joining a small group. - Reassurance for newcomers about their feelings and experiences. Avoid: - Repeating the existing guide on getting involved in other church ministries. - Generic advice without specific actionable steps. - Claims about specific group names/times that aren't confirmed in the current schedule. - Commercial or promotional language. Quality checklist: - Ensure clarity in each step of the process. - Maintain a friendly and approachable tone throughout the article. - Double-check internal links for accuracy and relevance. - Verify that all advice is actionable and specific to Ridgecrest. Article kind: evergreen Research status: not_required Reader intent: Help a newcomer or returning member identify the right small group, know what happens, and decide how to show up confidently. Planned outline: Why small groups matter (in plain language) | Step 1: Find a group that fits your season (age, interests, study focus) | Step 2: Check the current schedule (and how to confirm meeting times) | Step 3: What to expect on your first night (welcoming, discussion format, materials) | Step 4: Questions you can ask right away (leader + members) | Step 5: How to participate if you’re nervous (listening, prayer requests, optional sharing) | Step 6: How to handle kids/childcare considerations (what to ask before you come) | Step 7: After your first visit—how to decide if it’s a good fit | Quick “first-visit” checklist (arrive time, what to bring, contact info) Image direction: A candid photo of a small group gathering in a church room (people in a circle, friendly conversation), with a simple overlay caption: “First night at Ridgecrest small groups.” Preferred internal links: /, /about.html, /groups.html, /events.html, /contacts.html, /contact.php Avoid: Repeating the existing “How to Get Involved at Ridgecrest: A First-Timer’s Guide to Ministries, Kids, and Youth”, Thin or generic advice without actionable steps, Any claims about specific group names/times that aren’t provided in the site’s current schedule, Commercial or promotional language ## Selected Article Content Plan Item - Plan item ID: 108 - Plan order: 18 - Article kind: evergreen - Planned title: How to Join a Small Group at Ridgecrest (Without Feeling Lost) - Slug hint: join-a-small-group-at-ridgecrest - Reader intent: Help a newcomer or returning member identify the right small group, know what happens, and decide how to show up confidently. - Angle: A friendly, step-by-step path for finding the right small group and what to expect in the first few weeks—focused on belonging and practical next steps. - Image direction: A candid photo of a small group gathering in a church room (people in a circle, friendly conversation), with a simple overlay caption: “First night at Ridgecrest small groups.” - Author hint: Use the selected virtual author. Research: - Research status: not required for this evergreen plan item. Outline: - Why small groups matter (in plain language) - Step 1: Find a group that fits your season (age, interests, study focus) - Step 2: Check the current schedule (and how to confirm meeting times) - Step 3: What to expect on your first night (welcoming, discussion format, materials) - Step 4: Questions you can ask right away (leader + members) - Step 5: How to participate if you’re nervous (listening, prayer requests, optional sharing) - Step 6: How to handle kids/childcare considerations (what to ask before you come) - Step 7: After your first visit—how to decide if it’s a good fit - Quick “first-visit” checklist (arrive time, what to bring, contact info) Preferred internal link targets: - / - /about.html - /groups.html - /events.html - /contacts.html - /contact.php Avoid: - Repeating the existing “How to Get Involved at Ridgecrest: A First-Timer’s Guide to Ministries, Kids, and Youth” - Thin or generic advice without actionable steps - Any claims about specific group names/times that aren’t provided in the site’s current schedule - Commercial or promotional language 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: WP_POST_STATUS: WP_POST_URL: WP_AUTHOR_USER: FEATURED_IMAGE_ID: INLINE_IMAGE_IDS: BLOG_INDEX_STATUS: 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.