vision page
What does this MR do and why?
This merge request implements a dynamic Vision Projects page in the Viswam website using Strapi CMS.
Previously, the Vision page content was static and hardcoded in the frontend. This change restructures the page to fetch all content from Strapi, including:
Hero section
Image Understanding project cards
Performance Metrics (Model Efficiency & Quality Metrics)
Core Technologies
This improves maintainability, scalability, and content management by allowing admins to update page content directly from the CMS without modifying frontend code.
References
Feature: Vision Page CMS Integration
Strapi Single Type: vision-page
Strapi Components:
project_card
metric_box
metric_item
technology_card
list_item
Strapi API:
GET /api/vision-page?populate=deep
Screenshots or screen recordings
Before

After
How to set up and validate locally
Checkout the feature branch:
git checkout feature/vision-page-cms
Install dependencies:
npm install
Start Strapi:
npm run develop
Start frontend:
npm run dev
Verify:
Vision page loads successfully
Hero content is fetched from CMS
Image Understanding cards render dynamically
Performance Metrics display correct values
Core Technologies section loads from Strapi
No hardcoded content remains
MR acceptance checklist
Code follows project structure guidelines
Strapi Single Type and Components properly configured
API tested with populate=deep
No schema conflicts or 400 errors
Frontend renders dynamic CMS content correctly
No breaking changes introduced
Documentation updated if require