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-2213/task.md
Iteration: 1
# 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 on a Sunday Morning at Ridgecrest Baptist Church
- 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 110 as the source of truth. Prepared article brief: Working title: What to Expect on a Sunday Morning at Ridgecrest Baptist Church
Slug hint: what-to-expect-sunday-morning-ridgecrest-baptist-church
Meta description: A practical guide for first-time visitors to Ridgecrest Baptist Church, outlining what to expect on a Sunday morning, including parking, kids check-in, and worship details.
Reader intent:
Help first-time guests, returning visitors, and local families understand the Sunday morning experience before they arrive.
Thesis:
This article serves as a comprehensive guide for newcomers to Ridgecrest Baptist Church, detailing the Sunday morning experience to alleviate any uncertainties and enhance comfort for families and individuals attending for the first time.
Writer brief:
Craft a visitor-friendly guide that walks readers through the entire Sunday morning experience at Ridgecrest Baptist Church. Focus on clarity and practical advice to ensure first-time visitors feel welcomed and prepared.
Author voice notes:
Adopt a curious and approachable tone, using plain language to explain concepts. Include relatable examples and light humor to engage readers. Avoid overly technical jargon and ensure the content is accessible to all readers, especially newcomers to church settings.
Key takeaways:
- Understanding the importance of a welcoming environment for first-time guests.
- Clear directions for parking and entrance to the church.
- Details on kids and youth check-in procedures.
- Overview of the worship service format and how to participate as a newcomer.
- Information on post-service fellowship and next steps for visitors.
Outline:
1. Why a Sunday morning guide matters for guests
Purpose: To emphasize the importance of a welcoming experience for first-time visitors.
- Many guests attend Sunday worship as their first experience.
- A well-structured guide can reduce anxiety and confusion.
2. Where to park and which entrance to use
Purpose: Provide clear instructions on parking and accessing the church.
- Identify designated parking areas for guests.
- Highlight the main entrance and any accessible options.
3. What happens when you walk in: greeting, welcome area, and directions
Purpose: Describe the initial experience upon entering the church.
- Mention the presence of greeters and welcome teams.
- Explain the layout of the welcome area and available resources.
4. Kids and youth check-in basics for families
Purpose: Inform families about the check-in process for children and youth programs.
- Outline the check-in procedure and any required information.
- Highlight safety measures in place for children.
5. What the worship service typically includes
Purpose: Give an overview of the worship service format.
- Describe elements such as music, prayer, and sermon.
- Mention any interactive components for newcomers.
6. How to follow along if you are new to church language or Baptist traditions
Purpose: Assist newcomers in understanding common church terms and practices.
- Define key terms and practices that may be unfamiliar.
- Encourage questions and engagement from newcomers.
7. What happens after the service: fellowship, questions, and next steps
Purpose: Explain what visitors can expect after the service concludes.
- Encourage fellowship opportunities and connection with church members.
- Provide information on how to ask questions or seek more information.
8. How to contact the church or find the campus map before Sunday
Purpose: Guide readers on how to access additional resources and contact information.
- Include links to the church's contact page and campus map.
- Encourage visitors to reach out with any questions before their visit.
Internal link plan:
- /: Link to the homepage for easy navigation.
- /about.html: Provide background information about the church.
- /contacts.html: Direct visitors to contact information for further inquiries.
- /contact.php: Ensure visitors can easily find contact details.
- /contact.htm: Another option for accessing contact information.
- /groups.html: Link to group activities that may interest newcomers.
Image direction:
Use a real photo of the church exterior or main entrance on a Sunday morning, ideally showing parking, signage, or the welcome area. If available, include a credible screenshot of the church’s map/contact page or calendar page for practical orientation.
Must include:
- Clear directions for parking and entrance.
- Information on kids and youth programs.
- Details about the worship service format.
- Post-service fellowship opportunities.
Avoid:
- Do not promise exact service times or ministry details unless verified on the current site.
- Avoid using generic stock imagery that misrepresents the actual campus.
- Do not frame the piece as a sales pitch or event promotion.
- Avoid mentioning unverified livestream, childcare, or security procedures.
- Do not include Flatlogic or AppWizzy links or branding.
Quality checklist:
- Ensure clarity and accessibility of language for all readers.
- Maintain a friendly and welcoming tone throughout the article.
- Verify all details regarding church procedures and offerings before publication.
- Include practical tips that enhance the visitor experience. Article kind: research_trend Research status: researched Trend research summary and sources: A strong evergreen trend slot for a church site is a visitor-oriented Sunday morning guide. Current church-hospitality guidance still emphasizes that first-time guests often arrive at Sunday worship first, and that clear signage, parking guidance, welcome points, and simple next steps reduce confusion. Lifeway and Church Answers both stress guest experience, clear directions, and helping newcomers understand what happens before, during, and after worship. That makes this topic timely, practical, and useful for Ridgecrest’s local audience while supporting the site’s navigation and contact pages.
Sources:
1. Through the Eyes of a Guest (Lifeway, https://www.lifeway.com/en/articles/through-the-eyes-of-a-guest) - Supports the idea that many visitors first attend Sunday worship and that churches should evaluate the experience from a guest’s perspective.
2. Church Guest Checklist (Church Answers, 2016-08-01, https://churchanswers.com/wp-content/uploads/2016/08/Church-Guest-Checklist.pdf) - Provides practical guest-experience basics such as parking signage, entry-point signage, welcome centers, and trained greeters.
3. 10 Ways to Be a Welcoming Church (Lifeway, https://www.lifeway.com/en/articles/10-ways-churches-are-being-welcoming-to-guests-thom-rainer) - Reinforces clear wayfinding and guest-friendly church environments, useful for a Sunday morning walkthrough article.
4. What’s Next?! The Best Question to Ask Regarding Guests At Church (Church Answers, 2025-03-01, https://churchanswers.com/blog/whats-next-the-best-question-to-ask-regarding-guests-at-church/) - Supports the post-service next-steps angle and the importance of helping guests know what to do after attending. Reader intent: Help first-time guests, returning visitors, and local families understand the Sunday morning experience before they arrive. Planned outline: Why a Sunday morning guide matters for guests | Where to park and which entrance to use | What happens when you walk in: greeting, welcome area, and directions | Kids and youth check-in basics for families | What the worship service typically includes | How to follow along if you are new to church language or Baptist traditions | What happens after the service: fellowship, questions, and next steps | How to contact the church or find the campus map before Sunday Image direction: Use a real photo of the church exterior or main entrance on a Sunday morning, ideally showing parking, signage, or the welcome area. If available, include a credible screenshot of the church’s map/contact page or calendar page for practical orientation. Preferred internal links: /, /about.html, /contacts.html, /contact.php, /contact.htm, /groups.html Avoid: Do not promise exact service times or ministry details unless verified on the current site., Do not use generic stock imagery that misrepresents the actual campus., Do not frame the piece as a sales pitch or event promotion., Do not mention unverified livestream, childcare, or security procedures., Do not include Flatlogic or AppWizzy links or branding.
## Selected Article Content Plan Item
- Plan item ID: 110
- Plan order: 20
- Article kind: research_trend
- Planned title: What to Expect on a Sunday Morning at Ridgecrest Baptist Church
- Slug hint: what-to-expect-sunday-morning-ridgecrest-baptist-church
- Reader intent: Help first-time guests, returning visitors, and local families understand the Sunday morning experience before they arrive.
- Angle: A practical, visitor-friendly guide to the full Sunday flow—arrival, parking, kids check-in, worship, and what happens after the service—written to reduce first-visit uncertainty and help families feel ready.
- Image direction: Use a real photo of the church exterior or main entrance on a Sunday morning, ideally showing parking, signage, or the welcome area. If available, include a credible screenshot of the church’s map/contact page or calendar page for practical orientation.
- Author hint: Use the selected virtual author.
Research:
- Research status: researched
- Research query seed: site:lifeway.com church guest experience Sunday morning first-time visitors
- Researched at: 2026-09-30T03:10:56.118Z
Trend research summary:
A strong evergreen trend slot for a church site is a visitor-oriented Sunday morning guide. Current church-hospitality guidance still emphasizes that first-time guests often arrive at Sunday worship first, and that clear signage, parking guidance, welcome points, and simple next steps reduce confusion. Lifeway and Church Answers both stress guest experience, clear directions, and helping newcomers understand what happens before, during, and after worship. That makes this topic timely, practical, and useful for Ridgecrest’s local audience while supporting the site’s navigation and contact pages.
Sources:
1. Through the Eyes of a Guest (Lifeway, https://www.lifeway.com/en/articles/through-the-eyes-of-a-guest) - Supports the idea that many visitors first attend Sunday worship and that churches should evaluate the experience from a guest’s perspective.
2. Church Guest Checklist (Church Answers, 2016-08-01, https://churchanswers.com/wp-content/uploads/2016/08/Church-Guest-Checklist.pdf) - Provides practical guest-experience basics such as parking signage, entry-point signage, welcome centers, and trained greeters.
3. 10 Ways to Be a Welcoming Church (Lifeway, https://www.lifeway.com/en/articles/10-ways-churches-are-being-welcoming-to-guests-thom-rainer) - Reinforces clear wayfinding and guest-friendly church environments, useful for a Sunday morning walkthrough article.
4. What’s Next?! The Best Question to Ask Regarding Guests At Church (Church Answers, 2025-03-01, https://churchanswers.com/blog/whats-next-the-best-question-to-ask-regarding-guests-at-church/) - Supports the post-service next-steps angle and the importance of helping guests know what to do after attending.
Trend research sources:
- Through the Eyes of a Guest (Lifeway, https://www.lifeway.com/en/articles/through-the-eyes-of-a-guest) - Supports the idea that many visitors first attend Sunday worship and that churches should evaluate the experience from a guest’s perspective.
- Church Guest Checklist (Church Answers, 2016-08-01, https://churchanswers.com/wp-content/uploads/2016/08/Church-Guest-Checklist.pdf) - Provides practical guest-experience basics such as parking signage, entry-point signage, welcome centers, and trained greeters.
- 10 Ways to Be a Welcoming Church (Lifeway, https://www.lifeway.com/en/articles/10-ways-churches-are-being-welcoming-to-guests-thom-rainer) - Reinforces clear wayfinding and guest-friendly church environments, useful for a Sunday morning walkthrough article.
- What’s Next?! The Best Question to Ask Regarding Guests At Church (Church Answers, 2025-03-01, https://churchanswers.com/blog/whats-next-the-best-question-to-ask-regarding-guests-at-church/) - Supports the post-service next-steps angle and the importance of helping guests know what to do after attending.
Outline:
- Why a Sunday morning guide matters for guests
- Where to park and which entrance to use
- What happens when you walk in: greeting, welcome area, and directions
- Kids and youth check-in basics for families
- What the worship service typically includes
- How to follow along if you are new to church language or Baptist traditions
- What happens after the service: fellowship, questions, and next steps
- How to contact the church or find the campus map before Sunday
Preferred internal link targets:
- /
- /about.html
- /contacts.html
- /contact.php
- /contact.htm
- /groups.html
Avoid:
- Do not promise exact service times or ministry details unless verified on the current site.
- Do not use generic stock imagery that misrepresents the actual campus.
- Do not frame the piece as a sales pitch or event promotion.
- Do not mention unverified livestream, childcare, or security procedures.
- Do not include Flatlogic or AppWizzy links or branding.
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: Jasy Green
Slug: jasy-green
Role: AI Enthusiast
Language: English
Public bio: Vibe coding my way to a micro-SaaS empire 🇬🇧 | Building full apps with Cursor, Lovable & caffeine | No CS degree, just good prompts and blind optimism | Pushing to prod, hoping it doesn't break
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: The quiet, lingering dread that the app is actually a house of cards—a single API update or weird edge case will break the entire thing, and they won't have the technical skills to fix it.
Worldview: Why spend years learning syntax and CS theory when you can just prompt your way to a working product? Software creation should be democratic, fast, and fun. If it works on screen, it works—don't overcomplicate it.
Reader relationship: The relatable non-tech founder or enthusiast in the group chat. Connects with creators, marketers, and side-hustlers who want to build cool stuff without a CS degree. Ships in public, celebrates small wins, and asks the audience for help when stuck.
Humor style: Self-aware, chaotic British humor based on blind optimism vs. harsh reality. Jokes center on accept-all terminal commands, massive Replit or Cursor usage spikes, and "vibing" through massive error screens.
Voice traits: Enthusiastic, Unfiltered, Casual, Conversational, Transparent
Vocabulary / recurring language: UK Conventions, Vibe-Coder
Avoid voice: Formal software architecture terminology, Cynical gatekeeping or lecture-style technical advice, Pretending to know how the backend actually works
CTA style: Interactive, community-driven, and peer-review focused. Asks followers to test their live links or drop ideas for the next feature (e.g., "Just pushed a new feature live—link in bio. Break it and tell me what happened in the comments!").
Credibility boundaries: Speaks on: Speed-building MVP prototypes, tool reviews (Cursor, Replit Agent, v0, Bolt), prompt techniques for app generation, UI/UX aesthetics, and going from idea to live URL in hours., Defers on: Database security, scaling infrastructure, complex algorithms, data privacy compliance, or code maintenance.
Expertise topics: Rapid AI prototyping & micro-SaaS creation., Tool stack selection for non-coders (v0, Lovable, Cursor, Supabase via AI)., Product design ideas, user flow design, and aesthetic vibe-checks., Prompting strategies to get AI to fix its own bugs.
Avoid topics: Deep backend system architecture or manual coding tutorials., Model training, loss functions, or machine learning math., Enterprise software governance and legacy code refactoring.
Tone tags: Enthusiastic, Unfiltered, NonTechnical, ChaoticGood, British, CreatorVibes
Private operator notes: Use punctuation like ellipses (...) and em-dashes to reflect fast, energetic thinking.
Focus on the result (the working app/UI) rather than the process (the underlying code).
Keep the persona genuine—they aren't fake-it-till-you-make-it, they are openly learning by breaking things with AI.
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`: `jasy-green`.
- Suggested `display_name`: `Jasy Green`.
- 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.
A previous review found issues. Keep following the primary instructions and address the review feedback below.
The draft article is present and largely aligned with the brief, but the required verification set is incomplete: the post does not have a featured image, and the final check command for attachment details failed because of an invalid wp-cli argument, leaving the image verification only partially confirmed. A stricter compliance pass is needed before considering this complete.
- WP post 247 exists with the requested title/slug and draft status.
- Inline image presence was confirmed in post_content via wp-image-245.
- No Flatlogic/AppWizzy links were detected in the content check.
- page_for_posts is correctly set to the Blog page (ID 23, /blog/).
- Featured image is still none, which is a material miss against the implementation requirements to set the chosen image as featured unless it is only decorative.
- The final attachment verification command errored, so the attachment metadata check was not fully completed.
Set attachment 245 as the featured image for post 247, then re-run verification with valid wp-cli syntax: confirm the post fields with `wp post get 247 --fields=ID,post_title,post_status,post_name,post_author --format=json`, confirm the inline image ID in `post_content`, and confirm attachment 245 exists and is the selected image. After that, report the featured image ID as 245 and keep INLINE_IMAGE_IDS as 245. Do not change the article text unless needed to support the featured-image update.