System Requirements Document for wholemanmission

1. Introduction

THE WHOLE MAN is a professional, scalable Christian ministry and whole-person wellness platform serving adults, couples, parents, children, singles, believers, and people exploring Christian resources.

The platform exists to help individuals and families experience lasting transformation in spirit, soul, and body through Christ-centred biblical teaching, practical wellness guidance, healthy lifestyle resources, family-focused content, and future wholesome-food experiences through Real Meals.

The brand identity is:

• Brand name: THE WHOLE MAN
• Tagline: Spirit • Soul • Body
• Primary message / vision: Restoring Families. Equipping the Body of Christ.
• Mission: To equip individuals and families to live whole and purposeful lives in Christ by providing biblical teaching, practical wellness guidance, healthy lifestyle resources, and wholesome food through Real Meals—strengthening the spirit, soul, and body.
• Overall goal: Help people experience lasting transformation in spirit, soul, and body by strengthening faith, restoring families, promoting healthy living, and providing wholesome food through Real Meals.

Jesus Christ shall remain central to the platform’s identity, language, and message.

2. System Overview

THE WHOLE MAN shall be delivered as a responsive first-party website with public access to all current destinations. It shall provide a welcoming ministry presence and clearly separated pathways for Faith, Health, Healthy Living, Family, Children, Resources, Real Meals, Shop, and Cart.

The current platform shall support discovery and browsing of ministry information, teaching-oriented content areas, resource categories, and future-ready shopping surfaces without inventing unsupplied content, products, outcomes, or claims.

The website shall:

• Present THE WHOLE MAN as an established, genuine Christian ministry and resource platform rather than a generic AI-generated landing page.
• Keep Jesus Christ central to the platform’s ministry identity and message.
• Support adults, couples, parents, children, singles, believers, and people exploring Christian resources.
• Keep navigation simple despite multiple content pathways.
• Preserve separate destinations for Faith, Health, Healthy Living, Family, Children, Resources, Real Meals, and Shop.
• Use reusable interface components and modular content structures.
• Remain publicly accessible in the current scope; no member account, role-based access control, or protected destination is currently required.
• Use professional placeholders where authoritative content has not been supplied.

2a. Product Interpretation and Delivery Boundary

THE WHOLE MAN is currently a public ministry, teaching, wellness, family, resource-discovery, and future-commerce-ready website.

The current implementation shall provide public content destinations and reusable components for presenting ministry pathways, browsing resources, presenting Real Meals and Shop areas, and collecting cart selections. The site shall not invent books, products, events, testimonials, founder history, credentials, statistics, ministry achievements, scripture quotations, medical claims, or shopping checkout details that have not been supplied.

Real Meals and Shop shall remain visually and structurally distinct. Real Meals shall represent the wholesome-food offering, while Shop shall be a separate browse destination for future shop offerings. Cart shall support the selected-item experience and clearly communicate when ordering or checkout information has not yet been supplied.

The following items are explicitly future-facing and shall not be implemented as current product capabilities unless later requirements specifically request them:

• Member accounts
• Mobile application
• Full resource library platform
• Audio/video library platform
• Courses
• School of Marriage
• Expanded children-learning product
• Events
• Community
• Newsletter operations
• E-commerce checkout
• Real Meals ordering fulfilment

The architecture shall remain modular so future requirements can be added without removing, replacing, or collapsing current destinations.

2b. Page Content and Component Coverage

Landing

• Information and state
  • Present THE WHOLE MAN, the tagline “Spirit • Soul • Body,” and the primary message “Restoring Families. Equipping the Body of Christ.”
  • Present the mission and overall goal in concise ministry-oriented copy.
  • Keep Jesus Christ central to the identity and message.
  • Introduce distinct pathways to Faith, Health, Healthy Living, Family, Children, Resources, Real Meals, and Shop.
• Primary actions
  • Navigate to the ministry pathways and About page.
  • Explore public resources and offerings.
• Supporting components
  • Header, desktop navigation, mobile navigation, pathway rail, hero section, section heading, CTA section, service/category cards, scripture-block placeholder, and footer.
• States and recovery
  • Use professional placeholders where mission-supporting material has not been supplied.
  • Provide accessible fallback text if hero imagery cannot load.

About

• Information and state
  • Present the ministry identity, vision, mission, and whole-person focus.
  • Present a founder section for Pastor Precious Ogbogoh.
  • Use a clearly labelled professional placeholder portrait panel until approved photography is supplied.
• Primary actions
  • Return to ministry pathways or explore Faith, Family, Resources, Real Meals, and Shop.
• Supporting components
  • Breadcrumbs, founder section, mission section, image placeholder panel, CTA section, and footer.
• States and recovery
  • The founder image shall not imply an actual photograph or fabricate a likeness.
  • Missing personal history, credentials, ministry experiences, or achievements shall remain absent or appear only as professional placeholders.

Faith

• Information and state
  • Present Christ-centred biblical teaching content and open scripture-block presentation areas.
  • Preserve a distinct Faith destination separate from Health, Healthy Living, Family, Children, Resources, Real Meals, and Shop.
• Primary actions
  • Browse Faith-oriented content and navigate to Resources.
• Supporting components
  • Breadcrumbs, hero section, scripture blocks, resource cards, article cards, video cards, audio cards, and CTA section.
• States and recovery
  • Scripture quotations shall not be invented.
  • Where no approved scripture content is available, show an attribution-ready professional placeholder rather than fabricated text.

Health

• Information and state
  • Present the practical wellness guidance pathway.
  • Maintain a clearly separate purpose from Healthy Living.
• Primary actions
  • Browse available wellness guidance and continue to Resources.
• Supporting components
  • Breadcrumbs, section heading, resource cards, article cards, video cards, audio cards, and CTA section.
• States and recovery
  • Do not present unsupported medical claims, health outcomes, or treatment claims.
  • Unavailable content shall use a professional placeholder or clear empty state.

Healthy Living

• Information and state
  • Present healthy lifestyle resources as a destination distinct from Health.
  • Support practical whole-person lifestyle exploration without medical claims.
• Primary actions
  • Browse healthy-living materials and continue to Resources.
• Supporting components
  • Breadcrumbs, section heading, resource cards, article cards, video cards, audio cards, and CTA section.
• States and recovery
  • Do not represent lifestyle information as disease prevention, treatment, or cure.
  • Empty category states shall clearly communicate that content is forthcoming without inventing resources.

Family

• Information and state
  • Present family-focused ministry content supporting the vision of restoring families.
  • Support adults, couples, parents, singles, and families without inventing counselling, programmes, events, or credentials.
• Primary actions
  • Browse family and marriage-oriented content and continue to Resources.
• Supporting components
  • Breadcrumbs, hero section, marriage content cards, resource cards, article cards, video cards, audio cards, and CTA section.
• States and recovery
  • Use placeholders for absent marriage content rather than invented books, teachings, testimonials, or events.

Children

• Information and state
  • Present a child- and parent-understandable ministry content pathway.
  • Keep content presentation family-friendly and suitable for children.
• Primary actions
  • Browse children-oriented content and return to family or resource pathways.
• Supporting components
  • Breadcrumbs, section heading, children content cards, resource cards, article cards, video cards, and CTA section.
• States and recovery
  • Content labels, controls, and language shall remain understandable to both children and parents.
  • Missing children’s content shall use professional placeholders.

Resources

• Information and state
  • Provide the central browsing destination for distinguishable resource types: general resources, articles, videos, audio, books, children content, and marriage content.
  • Present resource metadata only where supplied.
• Primary actions
  • Search available resources.
  • Filter available resources by supported type or category.
  • Open a selected resource destination where one is available.
• Supporting components
  • Breadcrumbs, search/filter interface, resource cards, article cards, video cards, audio cards, book cards, children content cards, marriage content cards, modal/dialog components, and footer.
• States and recovery
  • Search results shall communicate loading, available results, no results, and recoverable error states.
  • Books and other resource content shall not be invented; unavailable results shall use a professional empty state.
  • Search and filters shall be keyboard accessible and understandable by screen-reader users.

Real Meals

• Information and state
  • Present the Real Meals wholesome-food offering as a destination distinct from Shop.
  • Support future-ready product and service/category presentation.
  • Make no unsupported claim that any food product cures, treats, or prevents disease.
• Primary actions
  • Browse currently supplied Real Meals offering information.
  • Add available, explicitly supplied selections to Cart where applicable.
• Supporting components
  • Breadcrumbs, hero section, product cards, service/category cards, cart controls, modal/dialog components, CTA section, and footer.
• States and recovery
  • Do not invent food products, ingredients, prices, availability, nutritional claims, medical outcomes, or ordering terms.
  • If offerings are not supplied, display an appropriate professional placeholder or unavailable state.
  • Cart-addition confirmation shall be observable and recoverable.

Shop

• Information and state
  • Present Shop as a destination distinct from Real Meals.
  • Support future product browsing using product cards and service/category cards.
• Primary actions
  • Browse currently supplied Shop offerings.
  • Add available, explicitly supplied selections to Cart where applicable.
• Supporting components
  • Breadcrumbs, product cards, service/category cards, cart controls, modal/dialog components, CTA section, and footer.
• States and recovery
  • Do not invent products, prices, availability, books, merchandise, or purchasing terms.
  • If no approved offerings are available, show a professional empty state.
  • Cart interactions shall provide clear success, quantity-update, removal, and error feedback.

Cart

• Information and state
  • Display selected Real Meals and Shop items, if any are available and selected.
  • Preserve selected-item quantity and removal controls during the public browsing session.
  • Clearly distinguish Cart from an implemented checkout or fulfilment process.
• Primary actions
  • Review selections.
  • Adjust quantities.
  • Remove selections.
  • Return to the originating Real Meals or Shop destination.
• Supporting components
  • Cart components, product summary rows, quantity controls, remove controls, modal/dialog components, breadcrumb or return navigation, and footer.
• States and recovery
  • Display a clear empty-cart state when no selections exist.
  • Confirm quantity changes and removals.
  • Communicate recoverable cart-update errors and retain the last confirmed cart state.
  • If checkout or ordering details have not been supplied, clearly indicate that ordering fulfilment is not yet available rather than inventing a purchase flow.

3. Functional Requirements

FR-01 — Present ministry identity

As a Ministry Visitor / Seeker, I should be able to understand THE WHOLE MAN’s identity so that I can determine whether the ministry is relevant to me and my family.

• Provenance: explicit
• Access: Public.
• Trigger/input: The visitor opens Landing or About.
• Requirement: The system shall present the brand name THE WHOLE MAN, the tagline “Spirit • Soul • Body,” the primary message and vision “Restoring Families. Equipping the Body of Christ.,” the mission, and the overall goal.
• Observable result: The visitor can identify the ministry’s Christ-centred spirit, soul, and body focus.
• Failure/recovery: Missing approved supporting content shall use professional placeholders rather than invented information.
• Continuation: The visitor can continue to About or any ministry pathway.

FR-02 — Keep Christ central

As a Ministry Visitor / Seeker, I should encounter a clearly Christ-centred ministry message so that the platform’s faith foundation is unambiguous.

• Provenance: explicit
• Access: Public.
• Trigger/input: The visitor views brand, mission, Faith, or pathway content.
• Requirement: The system shall keep Jesus Christ central to the identity and message of the platform.
• Observable result: Ministry presentation consistently frames whole-person growth within Christian faith.
• Failure/recovery: The system shall not substitute secularly generic, contradictory, or value-conflicting messaging.
• Continuation: The visitor can explore Faith and related public pathways.

FR-03 — Browse distinct ministry pathways

As a Ministry Visitor / Seeker, I should be able to navigate distinct Faith, Health, Healthy Living, Family, Children, Resources, Real Meals, and Shop destinations so that I can locate the area relevant to my needs.

• Provenance: explicit
• Access: Public.
• Trigger/input: The visitor selects a navigation item, pathway rail tab, card, or contextual link.
• Requirement: The system shall preserve the stated pathways as separate destinations and shall not collapse them into one generic content area.
• Observable result: The selected destination opens with its own relevant content scope.
• Failure/recovery: Unavailable or unpopulated content shall show an understandable placeholder or empty state while retaining navigation to other pathways.
• Continuation: The visitor can browse another pathway or use Resources.

FR-04 — Present founder content truthfully

As a Ministry Visitor / Seeker, I should be able to view the founder section so that I can understand the ministry’s founder context without being shown fabricated information.

• Provenance: explicit
• Access: Public.
• Trigger/input: The visitor opens About.
• Requirement: The system shall provide a founder section for Pastor Precious Ogbogoh and shall use a clearly identifiable professional placeholder where actual photographs are not supplied.
• Observable result: The visitor sees a refined, clearly labelled placeholder portrait panel rather than an invented likeness.
• Failure/recovery: The system shall not invent personal history, ministry experiences, achievements, or credentials.
• Continuation: The visitor can return to ministry pathways.

FR-05 — Browse Christ-centred faith content

As a Resource Consumer / Learner, I should be able to browse Faith-oriented teaching content so that I can pursue spiritual growth through a Christ-centred ministry pathway.

• Provenance: explicit
• Access: Public.
• Trigger/input: The learner opens Faith or selects Faith content from navigation or Resources.
• Requirement: The system shall provide Faith content presentation using scripture blocks and reusable learning-content components.
• Observable result: The learner can distinguish Faith teaching from Health, Healthy Living, Family, Children, and resource browsing.
• Failure/recovery: Scripture quotations shall not be invented; unavailable approved scripture content shall use an attribution-ready placeholder.
• Continuation: The learner can explore related public resources.

FR-06 — Browse practical wellness guidance

As a Resource Consumer / Learner, I should be able to browse Health guidance so that I can explore practical wellness information separately from healthy lifestyle resources.

• Provenance: explicit
• Access: Public.
• Trigger/input: The learner opens Health.
• Requirement: The system shall present Health as a distinct practical wellness guidance destination.
• Observable result: The learner can browse available Health material and recognise that it is not the Healthy Living destination.
• Failure/recovery: The system shall not publish unsupported medical claims or treatment assertions; unavailable content shall use a professional placeholder.
• Continuation: The learner can continue to Healthy Living or Resources.

FR-07 — Browse healthy lifestyle resources

As a Resource Consumer / Learner, I should be able to browse Healthy Living resources so that I can explore practical lifestyle material separately from Health guidance.

• Provenance: explicit
• Access: Public.
• Trigger/input: The learner opens Healthy Living.
• Requirement: The system shall present Healthy Living as its own healthy lifestyle resource destination.
• Observable result: The learner can identify and browse available lifestyle-focused content.
• Failure/recovery: The system shall not make unsupported medical, prevention, treatment, or cure claims.
• Continuation: The learner can explore Resources or another pathway.

FR-08 — Browse family and marriage-oriented content

As a Resource Consumer / Learner, I should be able to browse Family content so that I can find ministry material relevant to family life and marriage.

• Provenance: explicit
• Access: Public.
• Trigger/input: The learner opens Family.
• Requirement: The system shall provide a family-focused destination supporting the vision of restoring families and may present approved marriage-oriented material through reusable marriage content cards.
• Observable result: The learner can locate family-focused material without treating it as the general Resources destination.
• Failure/recovery: The system shall not invent counselling programmes, books, testimonials, events, or outcomes.
• Continuation: The learner can use Resources to refine discovery.

FR-09 — Browse child- and parent-understandable content

As a Resource Consumer / Learner, I should be able to browse the Children destination so that I can locate family-friendly material understandable to children and parents.

• Provenance: explicit
• Access: Public.
• Trigger/input: The learner or visitor opens Children.
• Requirement: The system shall provide a Children destination using reusable children content cards and age-considerate, family-friendly presentation.
• Observable result: Children and parents can understand the page’s navigation and available content cues.
• Failure/recovery: Missing content shall use professional placeholders rather than invented children’s materials.
• Continuation: The visitor can return to Family, Resources, or another pathway.

FR-10 — Search and filter resources

As a Resource Consumer / Learner, I should be able to search and filter available resources so that I can find relevant articles, videos, audio, books, children content, marriage content, and general resources.

• Provenance: explicit
• Access: Public.
• Trigger/input: The learner enters a search term or selects an available filter on Resources.
• Requirement: The system shall provide a search/filter interface for the listed resource types.
• Observable result: The results view updates to show matching available resource cards or a no-results state.
• Failure/recovery: The system shall show loading, error, and no-results states, preserve or permit adjustment of the search/filter input, and support keyboard operation.
• Continuation: The learner can open an available item or adjust the search/filter criteria.

FR-11 — Browse Real Meals responsibly

As a Real Meals Customer / Shopper, I should be able to browse the Real Meals destination so that I can understand available wholesome-food offerings without misleading health claims.

• Provenance: explicit
• Access: Public.
• Trigger/input: The shopper opens Real Meals.
• Requirement: The system shall present Real Meals through reusable product and service/category cards when approved offering information is available.
• Observable result: The shopper can distinguish Real Meals from Shop.
• Failure/recovery: The system shall never state or imply that a food product cures, treats, or prevents disease. Unsupplied products, prices, nutrition details, and availability shall not be invented.
• Continuation: The shopper can return to pathways, browse Shop, or add explicitly available selections to Cart.

FR-12 — Browse Shop separately from Real Meals

As a Real Meals Customer / Shopper, I should be able to browse Shop separately from Real Meals so that I can explore the appropriate offering area.

• Provenance: explicit
• Access: Public.
• Trigger/input: The shopper opens Shop.
• Requirement: The system shall provide Shop as a separate destination using reusable product and service/category cards.
• Observable result: The shopper can browse approved Shop offerings where supplied.
• Failure/recovery: If no approved offerings exist, the system shall show a professional unavailable or empty state rather than invented products.
• Continuation: The shopper can add explicitly available selections to Cart or return to Real Meals.

FR-13 — Manage cart selections

As a Real Meals Customer / Shopper, I should be able to manage my selected items in Cart so that I can review, change, or remove selections during my browsing session.

• Provenance: required_inference
• Access: Public; session-based continuity only.
• Trigger/input: The shopper adds an explicitly available item from Real Meals or Shop, or opens Cart.
• Requirement: The system shall show selected items, quantity controls, removal controls, and an empty-cart state.
• Observable result: The cart visibly reflects confirmed additions, quantity changes, and removals.
• Failure/recovery: The system shall communicate cart-update errors, retain the last confirmed state, and enable the shopper to retry or return to the source destination.
• Continuation: The shopper can continue browsing or retain their cart selections during the current session. Checkout and fulfilment shall not be invented.

FR-14 — Deliver reusable responsive components

As a Ministry Visitor / Seeker, Resource Consumer / Learner, or Real Meals Customer / Shopper, I should experience consistent reusable interface patterns so that the website is easy to understand across destinations and devices.

• Provenance: explicit
• Access: Public.
• Trigger/input: A user visits any current page.
• Requirement: The system shall use reusable Header, desktop navigation, mobile navigation, Footer, hero sections, section headings, CTA sections, scripture blocks, resource cards, product cards, service/category cards, founder sections, article cards, video cards, audio cards, book cards, children content cards, marriage content cards, newsletter/signup section, breadcrumbs, search/filter interface, modal/dialog components, and cart components.
• Observable result: Components use consistent spacing, typography, buttons, card styles, borders, shadows, icons, hover states, and responsive behaviour.
• Failure/recovery: Components shall preserve usable states at narrow viewport widths and with keyboard-only interaction.
• Continuation: Users can continue browsing through persistent navigation and contextual links.

FR-15 — Preserve content integrity

As a Ministry Visitor / Seeker, I should receive trustworthy presentation so that I am not misled by fabricated ministry, wellness, or commercial information.

• Provenance: explicit
• Access: Public.
• Trigger/input: A user views any platform content.
• Requirement: The system shall not invent books, testimonials, ministry achievements, credentials, statistics, medical claims, events, products, scripture quotations, personal history, or ministry experiences unless supplied.
• Observable result: Missing information is absent or represented through a professional placeholder.
• Failure/recovery: Content without authoritative support shall not be published as factual.
• Continuation: Users can continue to approved content or other available pathways.

4. User Personas

Ministry Visitor / Seeker

Product context: A public visitor who may be an adult, couple, single, believer, parent, or person exploring Christian resources. This person arrives to understand THE WHOLE MAN and its ministry focus on spirit, soul, and body.

Primary goal: Understand the ministry’s identity, Christ-centred purpose, and available pathways before exploring a relevant area.

Distinct responsibilities and decisions:

• Interprets the ministry’s brand, vision, mission, and overall goal.
• Chooses among Faith, Health, Healthy Living, Family, Children, Resources, Real Meals, and Shop.
• Reviews About content and founder presentation.
• Assesses whether the platform appears trustworthy, welcoming, family-oriented, and aligned with Christian values.

Relevant interactions: Uses public navigation, hero calls to action, pathway bands, breadcrumbs, content cards, and About content.

Observable success: The visitor can clearly understand that THE WHOLE MAN exists to restore families and equip the Body of Christ through Christ-centred whole-person resources, and can locate an appropriate pathway.

Provenance: required_inference from the accepted public ministry and resource-discovery experience.

Resource Consumer / Learner

Product context: A believer, parent, couple, or learner seeking public teaching and whole-person wellness resources.

Primary goal: Find and engage available Faith, Health, Healthy Living, Family, Children, marriage, article, video, audio, book, or general resource material.

Distinct responsibilities and decisions:

• Selects a content pathway based on spiritual, family, wellness, lifestyle, or children-related interests.
• Uses the Resources search and filter interface to narrow available content.
• Chooses a resource type that best fits a personal or family need.
• Understands content boundaries, including the absence of unsupplied medical claims or invented scripture quotations.

Relevant interactions: Uses Faith, Health, Healthy Living, Family, Children, and Resources; interacts with resource cards, article cards, video cards, audio cards, book cards, children content cards, marriage content cards, search, and filters.

Observable success: The learner can identify and access available content relevant to their needs without confusion between the distinct ministry pathways.

Provenance: required_inference from the accepted teaching, wellness, lifestyle, family, children, and resource-discovery requirements.

Real Meals Customer / Shopper

Product context: A public visitor interested in wholesome-food offerings through Real Meals or future Shop offerings.

Primary goal: Browse approved Real Meals or Shop information, distinguish the two destinations, and manage available selections in Cart without encountering misleading health claims or invented purchase information.

Distinct responsibilities and decisions:

• Chooses whether to browse Real Meals or Shop.
• Reviews supplied product or category information where available.
• Adds explicitly available selections to Cart.
• Adjusts quantities, removes selections, or returns to browse more offerings.
• Understands when checkout and fulfilment are not yet implemented.

Relevant interactions: Uses Real Meals, Shop, Cart, product cards, service/category cards, cart controls, and modal/dialog feedback.

Observable success: The shopper can manage a clear selected-item state and understand the current boundary between browsing/cart functionality and unimplemented checkout or fulfilment.

Provenance: required_inference from the accepted Real Meals, Shop, Cart, product-card, and content-integrity requirements.

5. Core User Flows

Flow 1 — Understand the ministry and choose a pathway

Persona: Ministry Visitor / Seeker

1. The visitor arrives at Landing.
2. The visitor sees THE WHOLE MAN, “Spirit • Soul • Body,” and “Restoring Families. Equipping the Body of Christ.”
3. The visitor reads the concise mission and whole-person ministry framing.
4. The visitor chooses a pathway from the main navigation, pathway rail, hero action, or content section.
5. The system opens the selected public destination: About, Faith, Health, Healthy Living, Family, Children, Resources, Real Meals, or Shop.
6. The visitor reviews available content or a professional placeholder where approved information is not yet supplied.
7. The visitor continues