Skip to content

swechaap/internship2026

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

823 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Teams and Project Topics sheet :

https://docs.google.com/spreadsheets/d/1TS8a53XdPvk5vya1-R2iQQWykr4JaaSpVTEP_3kInZs/edit?usp=sharing

5-6Week Schedule

Team_Task

Deadline: 17th June,2026

1. End users
2. UseCases (Features)
3. High Level User Flow 

Project Development and Deployment using Vibe Coding & LLM's

Deadline: 20th June,2026

4. Modules & Workflows - Distribute the task and create issues in github repo.
5. Schema (DB Structure)
6. E2E Design (Wireframe) 
7. Development (Vibe Coding,Maintain the project repo) - Web Projects
8. Test Strategy
9. Deployment (Explore tools to deploy)

Pre-requisite Technologies : React, Node, Python, MongoDB,SQL

Plan after 20th June

After Web Project Completion - Learning Agents and Integrating AI Use cases into it.

======================================================================================

internship2026 (4 Week Project Flow)

Topic-> Problem Statement (HMW) → User → Requirement → Story Boarding → Development → Prototype → Testing

Phase 1 — Topic Selection & User Persona (Primary Research)

Phase 2 — Requirement Gathering

Functional Requirements

What should the simulation do?

Example: Electric Circuit

Student should:

✅ Connect wires ✅ Turn switch ON/OFF ✅ Check bulb glowing ✅ See wrong connection

Non-Functional Requirements

How should it feel?

✅ Easy to use ✅ Mobile friendly ✅ Works in low internet ✅ Fun and engaging ✅ Clear visuals

Learning Requirements

What learning outcome should happen? After using simulation, student should be able to:

✅ Explain circuit flow ✅ Identify open/closed circuit ✅ Predict outcomes

Phase 3 — Problem Statement - HMW Method (How Might We)

Eg : How might we help Class 7 students visually understand force through interaction instead of memorization?

Phase 4 — Storyboard (Before Coding)

Phase 5 — Task Division

Minimum Roles (can be add based on works) :

  1. Research Lead: Gather and analyzes information needed for the project.
  2. UX / Learning Designer: Designs user experience and how users will learn/interact.
  3. Storyboard Designer: creates visual flow and structure of the content or app.
  4. Frontend Developer: builds the user interface using code (UI implementation).
  5. Documentation Lead : Documenting the entire project workflow (maintaining Readme.md)
  6. Testing Lead: checks the product for bugs and ensures quality before release.

Phase 6 — Code Development & Define MVP (Minimum Viable Simulation)

Project Structure to be maintained :

  • index.html (Mandatory - Main file)
  • HTML Files (Keep in folder if multiple)
  • CSS Files (Keep in folder if multiple)
  • JS Files (Keep in folder if multiple)
  • Images (Keep in folder if multiple)
  • requirements.txt (Mandatory-for team to maintain) - Get it from ## Phase 2 — Requirement Gathering
  • storyboard file (PNG/JPEG/PDF)
  • Userpersona
  • About my team (teams.txt) - should also include details of ## Phase 5 — Task Division
  • Readme.md - Documentation of simulation

Process of MVP (Minimum Viable Simulation) Example:

❌ Full Science Lab

✅ One concept only: “Bulb glows when circuit completes.”

Build small → test → improve.

Phase 7 — Usability Testing

Ask school students:

  • Was it fun?
  • Did you understand?
  • Where did you get confused?
  • What should improve?

Note :

  • GitHub Issues created
  • Tasks assigned to team members

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages