System Requirements Document

Impact Health Africa — Public Website & Content Management System

1. Introduction

1.1 Purpose

This System Requirements Document (SRD) defines the requirements for the Impact Health Africa (IHA) public website and its accompanying content management system. The system is the primary digital property of IHA and must present the organisation as a serious African public health consulting and innovation firm — not a generic NGO, hospital, charity, or marketing agency.

1.2 Scope

The system covers:

• A publicly accessible, dynamic, database-driven website built on PHP 8+, MySQL 8+, HTML5, CSS3, and JavaScript.
• A secure administrative content management area (/admin) for managing all site content.
• A normalized MySQL data layer supporting all content types.
• Security, SEO, performance, responsive design, and accessibility controls.

The deliverable is a real dynamic PHP/MySQL website with a working CMS — not a static mockup and not a visual prototype. No fake buttons and no fake functionality may be shipped.

1.3 Intended Audience

This document is intended for the IHA project owner, the implementation team (developers, designers, content administrators), and any reviewer verifying that the delivered system meets the agreed functional, technical, and brand requirements.

1.4 Source Basis

Requirements in this document are derived from the IHA Brand Strategy Document and the explicit direction supplied by the IHA project owner. The supplied Pinterest image is a visual reference only — its text, logo, images, branding, and business content must not be copied; only the design language is adapted.

1.5 Reference Directives

1.6 Source Content Inventory

The following IHA brand-strategy facts are authoritative source content and must be reproduced faithfully wherever the corresponding requirement applies. Facts not supplied by the source are marked unverified and must not be invented.

Identity

• Name: Impact Health Africa (IHA)
• Tagline: Strengthening Health Systems. Transforming Lives.
• Positioning: A public health consulting and innovation firm dedicated to strengthening health systems through evidence-based consulting, capacity building, digital innovation, advocacy, and strategic partnerships that improve health outcomes across Africa.

Mission

To strengthen health systems and improve health outcomes by delivering evidence-based public health consulting, capacity building, digital health innovation, advocacy, and strategic partnerships that empower healthcare professionals, organizations, governments, and communities to make informed decisions and achieve lasting impact.

Purpose

To empower healthier communities by transforming knowledge into action and strengthening health systems through innovation, evidence, and strategic partnerships.

Vision

To become Africa's leading public health consulting and innovation firm, transforming lives by advancing equitable, data-driven, and sustainable health solutions that strengthen communities and contribute to healthier populations.

Core Values

• Excellence
• Integrity
• Innovation
• Equity
• Collaboration
• Impact

Strategic Pillars

• Consulting — providing technical expertise and advisory services.
• Capacity Building — training healthcare professionals and organizations.
• Research — generating evidence that informs decisions.
• Advocacy — influencing policy and promoting health equity.
• Digital Innovation — leveraging technology to improve healthcare delivery.
• Partnerships — building collaborative relationships that drive sustainable impact.

Why Partners Choose Impact Health Africa (verified principles)

• Evidence-Based
• Systems-Focused
• Innovation-Driven
• Equity-Centered
• Partnership-Led
• Impact-Oriented

Core Services (15)

1. Public Health Consulting
2. Health Systems Strengthening
3. Public Health Advocacy
4. Capacity Building & Professional Training
5. Healthcare Leadership Development
6. Health Research & Evidence Synthesis
7. Monitoring, Evaluation, Accountability & Learning (MEAL)
8. Data Analytics & Health Information Management
9. Digital Health Innovation
10. Health Programme Design & Implementation
11. Health Policy & Strategy Development
12. Community Health Interventions
13. Keynote Speaking & Conference Facilitation
14. Technical Assistance for Governments, NGOs & Development Partners
15. Project Management for Health Programmes

Primary Client Groups (12)

1. Federal and State Ministries of Health
2. Local Government Health Authorities
3. Primary Healthcare Centres
4. International Development Partners
5. Non-Governmental Organizations (NGOs)
6. Healthcare Facilities
7. Universities and Research Institutions
8. Corporate Organizations
9. Professional Associations
10. Foundations
11. Community-Based Organizations
12. Schools and Faith-Based Organizations

Year One Targets (ambitions, never achievements)

• 10,000+ people reached through health education and advocacy
• 500+ healthcare professionals and community members targeted for training
• 24 community outreach programmes
• 20 training workshops
• 10 consulting projects
• 15 strategic partnerships
• 15 speaking engagements
• 1 Annual Impact Report
• 1 policy brief or research report

SDG Alignment

• SDG 3 – Good Health and Well-being (primary contribution)
• SDG 4 – Quality Education (additional contribution)
• SDG 5 – Gender Equality (additional contribution)
• SDG 10 – Reduced Inequalities (additional contribution)
• SDG 17 – Partnerships for the Goals (additional contribution)

Social Channels

• LinkedIn (priority professional platform)
• X
• YouTube
• Facebook
• Instagram
• TikTok

Unverified / not supplied by the source

• Named clients, partners, projects, case studies, testimonials, awards, staff profiles, qualifications, years of experience, and completed impact statistics — unverified; must not be invented.
• Contact details, physical address, registration numbers, and legal entity details — unverified; must not be invented.

2. System Overview

2.1 Product Summary

Impact Health Africa requires a production-ready consulting-institution website that communicates credibility, evidence, modernity, humanity, innovation, and trustworthiness. The site functions as a marketing, thought-leadership, and engagement platform for IHA's public health consulting, capacity building, research, advocacy, digital innovation, and partnership work.

The system is composed of two surfaces:

2.2 Brand Frame

• Name: Impact Health Africa
• Tagline: Strengthening Health Systems. Transforming Lives.
• Positioning: A public health consulting and innovation firm dedicated to strengthening health systems through evidence-based consulting, capacity building, digital innovation, advocacy, and strategic partnerships that improve health outcomes across Africa.
• Mission: To strengthen health systems and improve health outcomes by delivering evidence-based public health consulting, capacity building, digital health innovation, advocacy, and strategic partnerships that empower healthcare professionals, organizations, governments, and communities to make informed decisions and achieve lasting impact.
• Purpose: To empower healthier communities by transforming knowledge into action and strengthening health systems through innovation, evidence, and strategic partnerships.
• Vision: To become Africa's leading public health consulting and innovation firm, transforming lives by advancing equitable, data-driven, and sustainable health solutions that strengthen communities and contribute to healthier populations.

2.3 Delivery Shape

Server-rendered dynamic PHP application with an MVC-inspired custom architecture, a MySQL persistence layer accessed through PDO, server-rendered HTML5 views, CSS3 styling, and progressive JavaScript enhancement. No proprietary framework, no page-builder, and no static export.

2.4 Content Integrity Principle

The system must never fabricate clients, partners, projects, case studies, testimonials, awards, staff, qualifications, years of experience, or completed impact statistics. Where real content has not been supplied, the system must display tasteful "Coming soon" or empty states, or clearly labelled demo content. Strategy targets must never be presented as historical achievements.

3. Functional Requirements

Functional requirements are expressed as user stories.

3.1 Global Site Structure and Page Templates

3.2 Homepage Sequence

The homepage must present the following sections in this order.

3.3 Service Catalogue

Each service must be a distinct, individually addressable offering with its own detail page and listing presence.

3.4 Strategic Pillars

3.5 Why Partners Choose Impact Health Africa

These six principles must be presented only as verified principles — they must not be embellished with unverified claims.

3.6 Primary Client Groups ("Who We Work With")

3.7 Sustainable Development Goal Alignment

3.8 Brand Content Requirements

3.9 Year One Ambitions (Targets, Not Achievements)

All nine items must appear on the site as targets/ambitions and must never be rendered as completed achievements or historical statistics.

3.10 Content Integrity and Empty States

3.11 Public Engagement Features

3.12 Administrative CMS

3.12.1 Access and Dashboard

3.12.2 Content Management (CRUD)

3.12.3 Content Management Tooling

3.13 Content and Programme Operations Support

These requirements reflect the organisation's one-year activity roadmap to the extent that the website supports them.

3.14 Security Functional Controls

4. User Personas

Only personas with materially distinct workflows are listed. Public personas are anonymous visitors and require no authentication; only administrative personas authenticate.

4.1 Prospective Client / Partner Decision-Maker

Represents Federal and State Ministries of Health, Local Government Health Authorities, Primary Healthcare Centres, International Development Partners, NGOs, Healthcare Facilities, Universities and Research Institutions, Corporate Organizations, Professional Associations, Foundations, Community-Based Organizations, and Schools and Faith-Based Organizations.

• Goal: Assess whether IHA can deliver credible public health consulting, capacity building, research, or programme support.
• Visits: Home, About, Services, Individual Service, Our Work, Case Studies, Partners, Contact.
• Needs: Clear service definitions, evidence of capability, credible positioning, and a direct way to start a conversation.

4.2 Health Professional and Learner

Represents healthcare workers, community members, and professionals seeking skills and development.

• Goal: Find training programmes, workshops, and events that build professional capability.
• Visits: Training, Events, Research & Insights, Individual Article, Contact.
• Needs: Training listings, upcoming/past event visibility, and newsletter signup to stay informed.

4.3 Research and Policy Audience

Represents researchers, policy actors, and development professionals consuming IHA's evidence output.

• Goal: Access reports, policy briefs, and articles to inform decisions.
• Visits: Research & Insights, Individual Article, Publications, Search.
• Needs: Reliable article pages, downloadable publication PDFs, and effective search.

4.4 Editorial / Content Administrator

Represents the person responsible for publishing and maintaining site content.

• Goal: Create, edit, organise, and publish content without developer involvement.
• Uses: /admin — Pages, Services, Projects, Case Studies, Articles, Categories, Publications, Training Programmes, Events, Team, Partners, Media, SEO Settings.

4.5 Site Administrator / Owner

Represents the person accountable for the site's operation and access.

• Goal: Keep the site secure, correctly configured, and properly indexed.
• Uses: /admin — Users, Site Settings, SEO Settings, Contact Enquiries, Newsletter Subscribers, Media; monitors dashboard counts and recent activity.

No separate persona is created for integration systems: there are no inbound integration systems described in the source material. Search engines are treated as external recipients/crawlers of sitemap.xml, robots.txt, and structured data, not as a persona.

5. Core User Flows

5.1 Prospective Client Evaluates and Enquires

1. Visitor lands on the Home page and sees the hero headline "Strengthening Health Systems. Transforming Lives." with CTAs "Work With Us" and "Explore Our Services".
2. Visitor scrolls the animated service marquee to scan the service range.
3. Visitor reads "How We Create Impact" (six strategic pillars) and "Why Partners Choose Impact Health Africa" (six principles).
4. Visitor opens the Services page and selects an individual service, which is rendered dynamically from the database.
5. Visitor reviews Our Work and Case Studies; where no real case studies exist, a "Coming soon" state is shown.
6. Visitor reviews Partner evidence; where no real partners exist, an appropriate empty state is shown.
7. Visitor opens the Contact page, completes the enquiry form, and submits it.
8. System validates the submission server-side, applies CSRF protection, and stores the enquiry in MySQL.
9. Administrator views the enquiry in /admin and responds.

5.2 Health Professional Finds Training and Subscribes

1. Visitor opens the Training page and reviews training programme listings.
2. Visitor opens the Events page and reviews upcoming and past events.
3. Visitor reads a related article from Research & Insights, rendered dynamically from the database.
4. Visitor submits the newsletter signup form.
5. System checks for duplication, stores the subscriber in MySQL, and confirms success.
6. Visitor returns when new events or training programmes are published.

5.3 Research and Policy Audience Accesses Evidence

1. Visitor opens Research & Insights and browses articles.
2. Visitor opens an individual article page rendered dynamically from the database.
3. Visitor opens Publications and selects a publication.
4. Visitor downloads the publication PDF.
5. If the publication is not yet available, a "Coming soon" state is shown rather than fabricated content.

5.4 Site-Wide Search

1. Visitor enters a keyword in site search.
2. System queries articles, publications, services, projects, events, and training.
3. System returns paginated, relevant results.
4. Visitor opens a result and continues to a dynamically rendered article, service, project, event, training, or publication page.

5.5 Editorial Administrator Publishes an Article

1. Administrator authenticates at /admin with secure login (rate-limited, session-protected).
2. Administrator opens Articles and creates a new article.
3. Administrator enters title, body content with rich text editing, assigns a category, sets a slug, sets status, and uploads a featured image.
4. System validates all input server-side, validates upload MIME type/size, and stores a safe filename.
5. Administrator previews and publishes the article.
6. System makes the article available on the public Research & Insights page and on its dynamic individual article page, with Article schema and Open Graph/Twitter metadata.

5.6 Editorial Administrator Manages a Publication

1. Administrator opens Publications in /admin.
2. Administrator creates a publication record with title, description, slug, status, and an uploaded PDF.
3. System validates the upload and stores the file with a safe filename.
4. Publication appears on the public Publications page with a working download link.

5.7 Editorial Administrator Manages Projects and Services

1. Administrator opens Projects or Services in /admin.
2. Administrator creates or updates a record with title, description, slug, status, ordering, and associated media.
3. System validates input server-side and persists the record.
4. The corresponding dynamic project page or dynamic service page renders the updated content on the public site.

5.8 Site Administrator Manages Access and Configuration

1. Administrator authenticates at /admin.
2. Administrator reviews dashboard counts and recent activity.
3. Administrator opens Users to create or update a CMS user; passwords are handled with password_hash.
4. Administrator opens Site Settings to update global configuration.
5. Administrator opens SEO Settings to update metadata defaults.
6. Administrator reviews Contact Enquiries and Newsletter Subscribers, using search, filtering, and pagination.
7. Authorization checks are enforced server-side on every action.

6. Visuals, Colors and Theme

6.1 Visual Direction

The visual system must recreate a premium modern consulting aesthetic adapted specifically for IHA: deep green and lime accents, off-white and white sections, large typography, grayscale professional photography, rounded cards, layered image compositions, editorial layouts, horizontal marquee strips, bold CTAs, statistics, alternating light/dark sections, and subtle animation.

The reference image's text, logo, images, branding, and business content must not be copied — only the design language is adapted for Impact Health Africa.

6.2 Palette

6.3 Typography

Modern typeface from Inter, Manrope, or DM Sans. Large responsive headings, generous whitespace, restrained animation, and a clear editorial hierarchy.

6.4 Imagery

Professional African healthcare and public-health imagery with a grayscale treatment where used in editorial compositions. Imagery must avoid poverty stereotypes and graphic medical imagery. Layered image compositions are used to create depth in hero and feature sections.

7. Signature Design Concept

"Evidence in Layers."

The site's signature is the deliberate stacking of structured content layers over deep green and off-white fields:

• Layered image compositions in hero and feature areas, building depth without stock-photo genericism.
• Alternating light/dark sections that create editorial rhythm across long pages.
• Horizontal marquee strips that carry the service range as a continuous, moving band of typography and lime accents.
• Oversized editorial typography anchoring each section with a strong headline and generous whitespace.
• Rounded cards containing services, pillars, principles, ambitions, and content previews.
• Bold CTAs and statistics bands that convert attention into action while never misrepresenting targets as achievements.
• Grayscale professional photography accented by lime and deep green, signalling seriousness, humanity, and modernity.

The result must feel like a premium African public health consulting institution: credible, evidence-driven, modern, human, innovative, and trustworthy.

8. Interaction Model & Motion Direction

8.1 Interaction Model

• Persistent global navigation with a working mobile menu on small screens.
• Card-based navigation into services, articles, projects, events, training, publications, team, and partners.
• Clear primary CTAs ("Work With Us", "Explore Our Services") available from the hero and repeated at the close of key pages.
• Forms (contact enquiry, newsletter signup, admin forms) with inline validation feedback and server-side validation enforcement.
• Filtering, pagination, and search on listing pages and in the admin.
• Download actions for publication PDFs.
• No fake buttons and no non-functional controls.

8.2 Motion Direction

• Motion is restrained and purposeful throughout.
• The service marquee animates as a continuous horizontal strip.
• Subtle entrance, hover, and transition effects support hierarchy and feedback.
• prefers-reduced-motion must be respected, disabling or simplifying non-essential motion.
• Motion must never block content access or hinder performance.

9. Non-Functional Requirements

9.1 Performance

• Excellent experience on desktop, tablet, and mobile.
• Lazy loading for images and heavy media.
• Responsive and WebP image delivery where possible.
• Efficient database queries.
• Pagination on listing pages and admin record lists.
• Minimal dependencies.

9.2 Responsiveness

• Full support for desktop, tablet, and mobile layouts.
• Mobile navigation must be complete and usable.
• Typography and layout must scale responsively.

9.3 Accessibility

• prefers-reduced-motion support for all animation.
• Sufficient text contrast against the defined palette.
• Semantic HTML5 structure.

9.4 Security

• Security controls as specified in Section 3.14 are mandatory, not optional.
• No credentials exposed in code, repository, or rendered output.

9.5 SEO

• SEO-friendly URLs.
• sitemap.xml and robots.txt.
• Open Graph and Twitter metadata.
• Organization, Article, Event, Service, and Breadcrumb schema where relevant.

9.6 Maintainability

• Reusable PHP components and partials.
• MVC-inspired separation of concerns.
• No duplicated database logic.
• No giant monolithic PHP files.

9.7 Content Integrity

• No invented clients, partners, projects, case studies, testimonials, awards, staff, qualifications, years of experience, or completed impact statistics.
• Targets are always presented as targets, never as achievements.

10. Tech Stack

10.1 Core Platform

No additional framework is specified; the application must be implemented directly in PHP 8+ with PDO.

10.2 Project Structure

/app/config
/app/controllers
/app/models
/app/views
/app/helpers
/public/assets
/admin
/database
/routes
/includes

10.3 Database Schema (Normalized)

Required tables:

users, roles, pages, services, service_categories, projects, case_studies, articles, article_categories, publications, training_programmes, events, team_members, partners, media, contact_enquiries, newsletter_subscribers, site_settings, seo_meta

Schema requirements:

• InnoDB storage engine.
• utf8mb4 character set.
• Primary keys and foreign keys defining relationships.
• Indexes on frequently queried columns.
• Timestamps on records.
• Slugs for URL-addressed content.

10.4 Frontend Assets

• HTML5, CSS3, and JavaScript delivered from /public/assets.
• Modern web font from Inter, Manrope, or DM Sans.
• Minimal third-party dependencies.

11. Assumptions and Constraints

11.1 Delivery Constraints

• The deliverable is a real dynamic PHP/MySQL website with a working CMS — not a static mockup and not a visual prototype.
• No fake buttons and no fake functionality may be shipped.
• The application must be built in logical phases, testing CRUD, authentication, forms, routing, responsiveness, and security.

11.2 Required Pre-Build Artefacts

The following must be produced and shown before application build begins, in this order:

1. Sitemap
2. Database schema and relationships
3. PHP folder architecture
4. Component architecture
5. Homepage structure
6. Design system

11.3 Content Constraints

• No invented clients, partners, projects, case studies, testimonials, awards, staff, qualifications, years of experience, or completed impact statistics.
• Where real content has not been supplied, tasteful "Coming soon" or empty states, or clearly labelled demo content, must be used.
• Strategy targets must never be presented as historical achievements.

11.4 Brand and Reference Constraints

• The supplied Pinterest image is a visual reference only; its text, logo, images, branding, and business content must not be copied.
• IHA's visual system must be an adaptation for IHA, not a reproduction of the reference.
• IHA must be positioned as a serious African public health consulting and innovation firm — not a generic NGO, hospital, charity, or marketing agency.

11.5 Organisational Context Assumptions

• IHA's stated one-year strategic goal is to establish itself as a recognised and trusted public health consulting and advocacy organisation in Nigeria, with a reputation for excellence, innovation, and measurable impact.
• The organisation's stated longer-term aspiration is to become a trusted African institution influencing public health policy, strengthening health systems, developing healthcare leaders, advancing digital health innovation, and improving health outcomes; the five-year vision includes national recognition, expansion to multiple African countries, proprietary digital health solutions, an Impact Health Africa Academy for professional training, annual flagship reports on health systems in Africa, influence on national and regional health policies through research and advocacy, and a multidisciplinary team of public health experts, researchers, trainers, and consultants.
• The one-year activity roadmap (foundation building, community presence, partnership expansion, national impact demonstration) informs the content and events the CMS must support; the website itself is not the mechanism by which legal registration, brand identity production, or social media account creation is performed.

11.6 Technical Constraints

• Server-side rendering with PHP 8+; no static site generation.
• MySQL 8+ with InnoDB and utf8mb4.
• All database access via PDO prepared statements.
• Reusable components and MVC-inspired structure; no duplicated database logic and no giant PHP files.
• Uploads restricted by MIME type, file type, and size, with safe filenames.
• Credentials stored outside public web root and never committed or rendered.

12. Glossary