vivid-multimodal

byJanvi shah

Create this multimodal app for the same

LandingQuizCanvasContentProfileOffline
Landing

Comments (0)

No comments yet. Be the first!

Authenticated role is Content Manager or Lecturer/Admin with content management permission; Student is denied admin/content operations.
Content has reached the approved state in the draft → review → approved → published workflow.
Content is not approved; return to editing.
Publishing fails or a correction is needed.
Rollback to a prior version to correct and re-edit.
Landing: View the public entry surface with the seven-day course index, language toggle हिन्दी | English , and offline-pack status.
Landing: Select Hindi or English from the language toggle; the client records the preference and applies it to subsequent content surfaces.
Landing: Proceed from the public entry to the identity access surface to authenticate as Content Manager.
Login: Authenticate with the agreed launch method guest, email, Google, Apple, and/or phone OTP — exact methods pending confirmation and establish a session.
Login: Check the authenticated role against RBAC: only Content Manager or Lecturer/Admin may proceed to content management; Student cannot perform admin or content operations.
Content: 1. View the content management workspace with course CRUD and ordering, day/lesson CRUD, section/content-block management, Hindi/English variants, media asset management, and quiz/question management.
Content: 1. Create or edit lesson content, media assets, and quizzes, including Hindi/English variants, as permitted.
Content: 2. Manage media assets audio, image, document and their variants for the lesson content.
Content: 3. Manage quiz questions and options for the lesson content.
Content: 4. Preview the content before publishing.
Content: 5. Submit the content into the draft → review → approved → published workflow as permitted.
Content: 6. Check that the content has reached the approved state in the workflow before publishing; content approval and publishing ownership is pending confirmation.
Content: 7. Publish the approved content, making it available to learner clients.
Content: 8. Use versioning and rollback to revert to a prior version if publishing fails or a correction is needed.
Content: 2. Review learner activity via the user list and learner drill-down.
Landing design preview
Authenticated role is Content Manager or Lecturer/Admin with content management permission; Student is denied admin/content operations.
Content has reached the approved state in the draft → review → approved → published workflow.
Content is not approved; return to editing.
Publishing fails or a correction is needed.
Rollback to a prior version to correct and re-edit.
Landing: View the public entry surface with the seven-day course index, language toggle हिन्दी | English , and offline-pack status.
Landing: Select Hindi or English from the language toggle; the client records the preference and applies it to subsequent content surfaces.
Landing: Proceed from the public entry to the identity access surface to authenticate as Content Manager.
Login: Authenticate with the agreed launch method guest, email, Google, Apple, and/or phone OTP — exact methods pending confirmation and establish a session.
Login: Check the authenticated role against RBAC: only Content Manager or Lecturer/Admin may proceed to content management; Student cannot perform admin or content operations.
Content: 1. View the content management workspace with course CRUD and ordering, day/lesson CRUD, section/content-block management, Hindi/English variants, media asset management, and quiz/question management.
Content: 1. Create or edit lesson content, media assets, and quizzes, including Hindi/English variants, as permitted.
Content: 2. Manage media assets audio, image, document and their variants for the lesson content.
Content: 3. Manage quiz questions and options for the lesson content.
Content: 4. Preview the content before publishing.
Content: 5. Submit the content into the draft → review → approved → published workflow as permitted.
Content: 6. Check that the content has reached the approved state in the workflow before publishing; content approval and publishing ownership is pending confirmation.
Content: 7. Publish the approved content, making it available to learner clients.
Content: 8. Use versioning and rollback to revert to a prior version if publishing fails or a correction is needed.
Content: 2. Review learner activity via the user list and learner drill-down.