In architecture / design phase

Your whole semester, on one screen.

Student Dashboard is a widget board for university life. Pull your timetable, deadlines, grades and notes into a single grid you arrange yourself — instead of juggling six portals that never talk to each other.

Capstone side-project. No sign-up, no pricing, no launch countdown.

Problem

Student tools are shaped like databases, not like weeks.

Every system holds a piece of your semester. None of them holds the whole picture, and none of them lets you decide what deserves the top-left corner.

Six tabs, one deadline

University IS, LMS, calendar, notes app, grade spreadsheet, group chat. All open, none of them talking to each other.

Static portals

The school system shows you data. It never lets you arrange it the way your week actually works.

Context-switching tax

Finding out what is due tomorrow takes longer than starting it. That is the whole problem.

How it works

Three steps. No onboarding funnel.

  1. 01

    Connect your sources

    Sign in or point the app at an ICS feed. Read-only — no write access to your university systems.

  2. 02

    Arrange your board

    Drag widgets around, resize them, save the layout. Next Monday it still looks the way you left it.

  3. 03

    Glance, don't dig

    One screen answers two questions: what is next, and what is late. Close the other six tabs.

Widgets

The board is the product.

Widgets are small, single-purpose and replaceable. Add the ones you need, delete the rest, and the dashboard stays yours.

Timetable

daily driver

This week, next week, room numbers, cancellations.

Deadlines

daily driver

Merged from every course, sorted by what actually hurts.

Grades & GPA

planned

Credits, weighted average, what you need on the final.

Notes

planned

Markdown scratchpad bound to a course, not to a folder tree.

Focus timer

idea

Pomodoro tied to a task, not to a separate app.

Group projects

idea

Who is doing what, and who has not replied yet.

Tech stack

Boring, documented, hireable.

The stack is chosen so a reader of the repo can follow it, and so the project survives being handed over.

  • Next.js 14 (App Router)
  • React Server Components
  • TypeScript strict
  • Tailwind CSS
  • shadcn/ui + Radix UI
  • lucide-react
  • react-hook-form + zod
  • PostgreSQL + Prisma
  • pnpm

Roadmap

Where it is, where it is going.

  1. Now

    Architecture & design

    Domain model, data sources, widget contract and the layout grid. No product code shipped yet.

  2. Next

    Design system

    Tokens, dark-first UI kit and the drag-and-drop board skeleton.

  3. Then

    MVP widgets

    Timetable and deadlines. If those two work, the concept works.

  4. Later

    Grades, notes, calendar sync

    More sources, more widgets, one shared board.

  5. Someday

    Public widget API

    So anyone can write a widget without touching the core.

Read the code, not the pitch.

The repository is public and the design phase is visible in it. Issues, ideas and pull requests are welcome.

GeraltOfRiviaa/Student-Dashboard