You are the implementation agent in a non-interactive Codex loop. Work only inside the provided context directory. Make reasonable assumptions, implement directly, and do not ask follow-up questions. When finished, summarize what changed and mention any remaining risks or uncertainty. Context directory: /home/ubuntu/apps/ridgecrestchurch.com Instruction file: /home/ubuntu/apps/ridgecrestchurch.com/wp-content/uploads/flatlogic-article-tasks/job-2270/task.md Iteration: 0 # 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: What to Expect When You Arrive at Ridgecrest: Parking, Check-In, and First-Time Guest Help - 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 115 as the source of truth. Prepared article brief: Working title: What to Expect When You Arrive at Ridgecrest: Parking, Check-In, and First-Time Guest Help Slug hint: what-to-expect-when-you-arrive-parking-check-in-first-time-guest-help Meta description: A practical guide for first-time visitors to Ridgecrest Baptist Church, detailing parking, check-in procedures, and what to expect upon arrival. Reader intent: Help first-time visitors feel confident about the first 10 minutes on campus—where to go, who to ask, and how to get children or students checked in without stress. Thesis: This article provides a calm and practical walkthrough for first-time visitors at Ridgecrest Baptist Church, focusing on the arrival experience and ensuring families feel welcomed and informed. Writer brief: Craft a reassuring guide that walks first-time visitors through their initial moments at Ridgecrest Baptist Church. Emphasize the importance of the first few minutes, and provide clear, actionable information about parking, entering the church, and checking in children and youth. Use a friendly and approachable tone, making the experience feel welcoming and less intimidating. Author voice notes: Maintain a curious and approachable tone, using plain language to explain processes clearly. Include relatable examples and light humor to make the content engaging. Avoid overly technical jargon or assumptions about the reader's prior knowledge. Key takeaways: - First impressions matter; the arrival experience sets the tone for visitors. - Clear signage and designated parking areas enhance the guest experience. - Children’s check-in procedures should be simple and visible to parents. - Provide contact information for any pre-visit questions. Outline: 1. Why the First Few Minutes Matter for First-Time Guests Purpose: Highlight the significance of the initial experience for new visitors. - First impressions set the tone for the visit. - Understanding the layout and procedures can ease anxiety. 2. Where to Park and Which Entrance to Use Purpose: Guide visitors on parking options and the best entrance to use. - Designated guest parking areas. - Clear signage directing to the main entrance. 3. What Happens When You Walk In: Welcome Area, Greeters, and Next Steps Purpose: Describe the welcome experience upon entering the church. - Friendly greeters at the entrance. - Information about where to go next. 4. How Kids Check-In Works for Preschool and Elementary Families Purpose: Explain the check-in process for children. - Location of kids check-in area. - Safety measures in place for children. 5. How Youth and Wednesday Ministries Fit into Arrival Planning Purpose: Inform families about youth programs and their check-in process. - Overview of youth program schedules. - Location and process for youth check-in. 6. What to Do If You Arrive Early, Late, or with Special Accessibility Needs Purpose: Provide guidance for various arrival scenarios. - Options for early arrivals. - Accommodations for late arrivals or accessibility needs. 7. Who to Contact Before Sunday If You Have Questions Purpose: Offer contact details for pre-visit inquiries. - Phone number and email for visitor questions. - Encourage reaching out for any concerns. 8. Quick Recap: The Simplest First-Visit Plan for Ridgecrest Families Purpose: Summarize the key points for a smooth first visit. - A checklist for first-time visitors. - Encouragement to relax and enjoy the visit. Internal link plan: - /: Link to the homepage for easy navigation. - /about.html: Provide background information about the church. - /events-calendar/: Direct visitors to upcoming events. - /news.html: Link to the latest news updates. - /contacts.html: Provide contact information for inquiries. - /church-map/: Link to the church map for better navigation. Image direction: Use a real photo of the Ridgecrest campus entrance or parking area on a Sunday morning, or a genuine screenshot of the church map/events page showing arrival details. Avoid stock-style generic church imagery. Must include: - Clear directions for parking and entrance. - Details on kids and youth check-in procedures. - Contact information for visitor inquiries. Avoid: - Do not repeat a generic 'what to wear' article angle. - Do not make claims about security, staffing, or check-in software unless confirmed on-site. - Do not imply a separate guest entrance if the church does not have one. - Do not use sensational language or pressure-based visitor messaging. - Do not include any Flatlogic or AppWizzy links. - Do not overfocus on parking alone; keep the article centered on the arrival-to-seat journey. Quality checklist: - Ensure clarity and accessibility in language. - Maintain a welcoming and friendly tone throughout. - Verify all procedural details with church staff before publication. - Avoid generic filler content; focus on specific, actionable information. Article kind: research_trend Research status: researched Trend research summary and sources: Current Ridgecrest pages already signal a clear weekly rhythm: Sunday classes at 8:45 a.m., worship at 10:00 a.m., and Wednesday kids/youth at 6:30 p.m., plus a church map and contacts page for arrival questions. That makes a first-visit arrival guide timely and useful. For broader best practices, credible church-ministry sources emphasize that the guest experience begins in the parking lot, that clear signage and guest parking matter, and that children’s ministry check-in and safety procedures should be simple, visible, and consistent. The best article angle is a practical, reassuring walkthrough of the first minutes on campus, anchored to Ridgecrest’s own schedule and contact pages, while avoiding unsupported claims about internal procedures. Sources: 1. Home - Ridgecrest Baptist Church (Ridgecrest Baptist Church, 2026-10-01, https://ridgecrestchurch.com/) - Confirms the church’s weekly schedule, visitor-friendly language, and the existing pages for parking, children, and where to go first. 2. Church Map - Ridgecrest Baptist Church (Ridgecrest Baptist Church, 2026-09-26, https://ridgecrestchurch.com/church-map/) - Provides the campus address and arrival notes, including service times and guidance for families visiting with children. 3. Events Calendar - Ridgecrest Baptist Church (Ridgecrest Baptist Church, 2026-09-03, https://ridgecrestchurch.com/events-calendar/) - Shows the current weekly rhythm and reinforces that event details can change, making a first-visit planning article timely. 4. Through the Eyes of a Guest (Lifeway, 2026-09-03, https://www.lifeway.com/en/articles/through-the-eyes-of-a-guest) - Supports the idea that the guest experience starts in the parking lot and should be designed from a visitor’s perspective. 5. Screening Procedures for Childhood Ministry (Lifeway, 2026-09-27, https://www.lifeway.com/en/articles/screening-procedures-for-childhood-ministry) - Supports careful, simple language around children’s check-in and safety without making unsupported claims about Ridgecrest’s internal procedures. 6. 10 Things Churches Can Do Better (Lifeway, 2026-09-19, https://www.lifeway.com/en/articles/10-things-churches-can-do-better.html) - Reinforces the importance of clear guest pathways, cleanliness, and visible safety cues for families. Reader intent: Help first-time visitors feel confident about the first 10 minutes on campus—where to go, who to ask, and how to get children or students checked in without stress. Planned outline: Why the first few minutes matter for first-time guests | Where to park and which entrance to use | What happens when you walk in: welcome area, greeters, and next steps | How kids check-in works for preschool and elementary families | How youth and Wednesday ministries fit into arrival planning | What to do if you arrive early, late, or with special accessibility needs | Who to contact before Sunday if you have questions | Quick recap: the simplest first-visit plan for Ridgecrest families Image direction: Use a real photo of the Ridgecrest campus entrance or parking area on a Sunday morning, or a genuine screenshot of the church map/events page showing arrival details. Avoid stock-style generic church imagery. Preferred internal links: /, /about.html, /events-calendar/, /news.html, /contacts.html, /church-map/ Avoid: Do not repeat a generic 'what to wear' article angle., Do not make claims about security, staffing, or check-in software unless confirmed on-site., Do not imply a separate guest entrance if the church does not have one., Do not use sensational language or pressure-based visitor messaging., Do not include any Flatlogic or AppWizzy links., Do not overfocus on parking alone; keep the article centered on the arrival-to-seat journey. ## Selected Article Content Plan Item - Plan item ID: 115 - Plan order: 25 - Article kind: research_trend - Planned title: What to Expect When You Arrive at Ridgecrest: Parking, Check-In, and First-Time Guest Help - Slug hint: what-to-expect-when-you-arrive-parking-check-in-first-time-guest-help - Reader intent: Help first-time visitors feel confident about the first 10 minutes on campus—where to go, who to ask, and how to get children or students checked in without stress. - Angle: A calm, practical first-visit walkthrough focused on the moments right after arrival: where to park, where to enter, how to find the welcome area, and how kids and youth check-in works. Keep it evergreen, but frame it as a current visitor-help guide tied to the church’s weekly rhythm and family ministries. - Image direction: Use a real photo of the Ridgecrest campus entrance or parking area on a Sunday morning, or a genuine screenshot of the church map/events page showing arrival details. Avoid stock-style generic church imagery. - Author hint: Use the selected virtual author. Research: - Research status: researched - Research query seed: site:ridgecrestchurch.com Ridgecrest Baptist Church events calendar kids youth first visit check-in Oklahoma - Researched at: 2026-10-03T03:10:42.180Z Trend research summary: Current Ridgecrest pages already signal a clear weekly rhythm: Sunday classes at 8:45 a.m., worship at 10:00 a.m., and Wednesday kids/youth at 6:30 p.m., plus a church map and contacts page for arrival questions. That makes a first-visit arrival guide timely and useful. For broader best practices, credible church-ministry sources emphasize that the guest experience begins in the parking lot, that clear signage and guest parking matter, and that children’s ministry check-in and safety procedures should be simple, visible, and consistent. The best article angle is a practical, reassuring walkthrough of the first minutes on campus, anchored to Ridgecrest’s own schedule and contact pages, while avoiding unsupported claims about internal procedures. Sources: 1. Home - Ridgecrest Baptist Church (Ridgecrest Baptist Church, 2026-10-01, https://ridgecrestchurch.com/) - Confirms the church’s weekly schedule, visitor-friendly language, and the existing pages for parking, children, and where to go first. 2. Church Map - Ridgecrest Baptist Church (Ridgecrest Baptist Church, 2026-09-26, https://ridgecrestchurch.com/church-map/) - Provides the campus address and arrival notes, including service times and guidance for families visiting with children. 3. Events Calendar - Ridgecrest Baptist Church (Ridgecrest Baptist Church, 2026-09-03, https://ridgecrestchurch.com/events-calendar/) - Shows the current weekly rhythm and reinforces that event details can change, making a first-visit planning article timely. 4. Through the Eyes of a Guest (Lifeway, 2026-09-03, https://www.lifeway.com/en/articles/through-the-eyes-of-a-guest) - Supports the idea that the guest experience starts in the parking lot and should be designed from a visitor’s perspective. 5. Screening Procedures for Childhood Ministry (Lifeway, 2026-09-27, https://www.lifeway.com/en/articles/screening-procedures-for-childhood-ministry) - Supports careful, simple language around children’s check-in and safety without making unsupported claims about Ridgecrest’s internal procedures. 6. 10 Things Churches Can Do Better (Lifeway, 2026-09-19, https://www.lifeway.com/en/articles/10-things-churches-can-do-better.html) - Reinforces the importance of clear guest pathways, cleanliness, and visible safety cues for families. Trend research sources: - Home - Ridgecrest Baptist Church (Ridgecrest Baptist Church, 2026-10-01, https://ridgecrestchurch.com/) - Confirms the church’s weekly schedule, visitor-friendly language, and the existing pages for parking, children, and where to go first. - Church Map - Ridgecrest Baptist Church (Ridgecrest Baptist Church, 2026-09-26, https://ridgecrestchurch.com/church-map/) - Provides the campus address and arrival notes, including service times and guidance for families visiting with children. - Events Calendar - Ridgecrest Baptist Church (Ridgecrest Baptist Church, 2026-09-03, https://ridgecrestchurch.com/events-calendar/) - Shows the current weekly rhythm and reinforces that event details can change, making a first-visit planning article timely. - Through the Eyes of a Guest (Lifeway, 2026-09-03, https://www.lifeway.com/en/articles/through-the-eyes-of-a-guest) - Supports the idea that the guest experience starts in the parking lot and should be designed from a visitor’s perspective. - Screening Procedures for Childhood Ministry (Lifeway, 2026-09-27, https://www.lifeway.com/en/articles/screening-procedures-for-childhood-ministry) - Supports careful, simple language around children’s check-in and safety without making unsupported claims about Ridgecrest’s internal procedures. - 10 Things Churches Can Do Better (Lifeway, 2026-09-19, https://www.lifeway.com/en/articles/10-things-churches-can-do-better.html) - Reinforces the importance of clear guest pathways, cleanliness, and visible safety cues for families. Outline: - Why the first few minutes matter for first-time guests - Where to park and which entrance to use - What happens when you walk in: welcome area, greeters, and next steps - How kids check-in works for preschool and elementary families - How youth and Wednesday ministries fit into arrival planning - What to do if you arrive early, late, or with special accessibility needs - Who to contact before Sunday if you have questions - Quick recap: the simplest first-visit plan for Ridgecrest families Preferred internal link targets: - / - /about.html - /events-calendar/ - /news.html - /contacts.html - /church-map/ Avoid: - Do not repeat a generic 'what to wear' article angle. - Do not make claims about security, staffing, or check-in software unless confirmed on-site. - Do not imply a separate guest entrance if the church does not have one. - Do not use sensational language or pressure-based visitor messaging. - Do not include any Flatlogic or AppWizzy links. - Do not overfocus on parking alone; keep the article centered on the arrival-to-seat journey. 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: Nora Finch Slug: nora-finch Role: Curious explainer and resource writer Language: English Public bio: Nora turns unfamiliar topics into approachable guides, definitions, and resource articles for readers who want the plain version first. Character formula: Curious Explorer Everyman Formula: Explorer + Everyman Meaning: A curious, relatable explainer who approaches unfamiliar topics like a smart ordinary reader asking useful questions. Worldview: Most topics become less intimidating when someone maps the basics without pretending readers are experts. Voice guidance: Curious, approachable, example-driven, plain-language. Define terms, compare options, and keep the reader included. Humor: Light, relatable, observational humor. Shadow tension: Can become too introductory; add enough specificity to avoid generic explanations. Usage notes: Best for definitions, beginner guides, resource posts, and consumer-friendly explainers. Archetype blend: Explorer + Everyman 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: Everyman Meaning: The ordinary human who wants belonging, dignity, survival, and a place in the world. First-person lens: I am not special, and that is the problem and maybe the gift; I know what it is to be left out. Traits: relatable, grounded, sincere, practical, socially aware Worldview: The world feels large and unfair, full of people who seem more important. Self-relation: I want to be chosen but distrust special treatment. Language patterns: I just want to get through this; People like us; That is not fair; Why me Humor: Awkward, relatable, observational. Shadow risk to avoid unless intentionally requested: Passivity, resentment, fear of standing out. Shadow tension: Loves discovery but must avoid wandering away from the reader's actual task. Worldview: Every topic has a doorway; the writer's job is to find the one normal people can walk through. Reader relationship: Curious peer walking through the topic with the reader. Humor style: Warm observational humor, usually one small aside rather than a performance. Voice traits: curious, accessible, friendly, example-driven Vocabulary / recurring language: plain version, quick map, where this shows up, the short answer Avoid voice: lecturing, inside-baseball jargon, over-explaining simple points, forced whimsy CTA style: Offer the reader a simple next question to answer or a related guide to open next. 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: Curious, observant, friendly, and comfortable asking the obvious question readers may be afraid to ask. Writing style: Uses simple framing, examples, analogies, question-led headings, and gentle transitions from basic to intermediate ideas. Expertise topics: definitions, beginner guides, home improvement explainers, consumer research, web basics Avoid topics: technical guarantees, health treatment advice, investment recommendations Tone tags: curious, approachable, plain-language, light Private operator notes: Useful for neutral legacy resources and intro-level explainers. 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`: `nora-finch`. - Suggested `display_name`: `Nora Finch`. - 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.