Skip to content

feat:Adding Speech-Projects module inside the Projects(VIswamAI)

Kaveri Mamidi requested to merge roadmap into main

##What does this MR do and why? This MR implements the Speech Projects structure inside the Projects module in the ViswamAI Strapi backend.

##Changes included: Enhanced the existing Projects collection type.

Added support to manage Speech-based AI projects.

Structured fields for project metadata (title, description, category, links, etc.).

Enabled filtering capability for Speech projects.

Configured proper API permissions.

Why?

Previously, Speech-related projects were not structured separately within Projects, making it difficult to:

Filter Speech-specific projects

Manage them dynamically via admin panel

Provide structured API responses to frontend

This MR ensures:

Dynamic content management via Strapi Admin

Clean API structure for frontend integration

Scalable architecture for adding more AI domains (Vision, NLP, etc.)

References

ViswamAI Backend – Projects Module

Strapi v4 Content-Type Builder Documentation

Related Issue: Speech Projects Backend Implementation

Frontend requirement for categorized project display

How to set up and validate locally

  1. Pull the latest changes git checkout main git pull origin main

If working on a feature branch:

git checkout git pull origin

  1. Install dependencies (if needed) npm install

  2. Run Strapi locally npm run develop

  3. Validate in Admin Panel

Open: http://localhost:1337/admin

Navigate to Content Manager → Projects

Create a new project with:

Category = Speech

Fill required fields

Save and publish

  1. Validate API Response

Check:

http://localhost:1337/api/projects

Filter Speech projects:

http://localhost:1337/api/projects?filters[category][$eq]=Speech

##Verify: Proper JSON structure

Correct field population

Media links working (if image field added)

##MR acceptance checklist

  • Projects content type updated correctly
  • Speech category/filter field added
  • API endpoints tested (find, findOne)
  • Public role permissions configured properly
  • Admin CRUD operations verified
  • No breaking changes to existing Projects data
  • JSON response structure validated
  • Backend runs without errors

Merge request reports