Skip to content

Feature Request: Integrate Strapi CMS for Dynamic Summer of AI Page

✨ Feature Request: Integrate Strapi CMS for Dynamic Summer of AI Page

What feature would you like to see added to viswam.ai?
I would like to add dynamic content integration using Strapi CMS for the “Summer of AI” page, replacing the current hardcoded data in the Astro frontend.

Describe the feature in detail. Be clear about the use case and who it helps.
Currently, the Summer of AI page content (hero section, feature cards, FAQs) is hardcoded in the frontend. This makes it difficult for non-developers to update content.

The proposed feature is to connect the frontend with a Strapi backend, where all page content is managed through a CMS. The frontend will fetch and render this data dynamically.

This will help:

  • Content managers to update text without code changes
  • Developers to maintain cleaner and scalable code
  • The organization to quickly update program details

Why is this feature important or useful?

  • Eliminates hardcoded content
  • Enables real-time content updates
  • Improves maintainability and scalability
  • Aligns with modern CMS-driven architecture
  • Reduces dependency on developers for content changes

Any suggestions for how it could work or look?

  • Use Strapi REST API:
    • /api/pages?filters[slug][$eq]=summer-of-ai&populate=deep
    • /api/faq-items?filters[page][slug][$eq]=summer-of-ai
  • Fetch data inside existing Astro page using frontmatter
  • Map API response to UI components:
    • Hero section → dynamic fields
    • Feature cards → loop through features array
    • FAQ → loop through FAQ items

No UI changes are required — only data binding updates.

Add diagrams, examples, or references if possible.

Architecture Flow:

Strapi CMS → API → Astro Frontend → UI Render

Example Data Flow:

hero_section.heading → Display in Hero Title features_section.features → Render as cards faq_items → Render as accordion

Additional context or notes

  • No new frontend files are required
  • Existing Astro components will be reused
  • Backend is already structured with:
    • hero_section
    • features_section
    • faq-items

This feature has already been partially implemented in backend and only requires frontend integration.