Skip to content

Strapi Backend: Implement About & Contact Page Content Structure and Data Entry

Pavani Pothuganti requested to merge pavani into viswam/website

## What does this MR do and why?

This merge request implements the complete backend content structure for the About and Contact pages using Strapi v5 (Headless CMS).

The changes include creating structured content models, reusable components, and populating the required content data for dynamic frontend consumption.

Previously, the website content was static. This update enables dynamic content management through Strapi, allowing non-developers to update page content without modifying frontend code.

This improves maintainability, scalability, and flexibility of the website.

🔑 Key Changes

  • Created About Page (Single Type) in Strapi

  • Implemented structured sections:

    • Journey (Timeline)
    • Leadership
    • Achievements
    • Impact
    • Focus Areas

  • Added footer information (Pronunciation, Full Form, Initiative Line)

  • Created Contact Page (Single Type) with dynamic fields

  • Implemented repeatable Ways to Get Involved component

  • Created contact-message Collection Type for form submissions

  • Configured Public API permissions (create, find where required)

  • Populated and published all content entries

## References

  • Strapi v5 Documentation
  • REST API configuration for Public role
  • Dynamic content modeling best practices

## Screenshots

Before After
Contact Message CollectionWhatsApp_Image_2026-02-13_at_2.18.54_PM Screenshot_from_2026-02-13_14-34-42Content Manager → contact-message

## How to Set Up and Validate Locally

1️⃣ Checkout branch:

git checkout feature/strapi-about-contact

2️⃣ Install dependencies:

npm install

3️⃣ Run Strapi:

npm run develop

4️⃣ Open Admin Panel:

http://localhost:1337/admin

5️⃣ Verify:

  • About page content available at:

    /api/about?populate=*

  • Contact page content available at:

    /api/contact-page?populate=*

  • Contact form submission stores data in:

    Content Manager → contact-message

## MR Acceptance Checklist

  • ✔ Content types created correctly
  • ✔ Reusable components implemented
  • ✔ Public API permissions configured
  • ✔ Data populated and published
  • ✔ API tested successfully
  • ✔ No schema conflicts
  • ✔ Backend runs without errors

Merge request reports