Team dependency roadmap

Legal-e From Zero

Target: Student beta in 4-6 months Launch the student learning platform first. Community and services expand after the beta.
Done / approved
Next immediate work
Build phase
Decision / dependency
Later phase
Approved direction
Planning foundation
Product foundation
Core student experience
Launch hardening
Later growth lanes
Input ADone

Brand System

The interface must feel serious, modern, legal, and student-friendly.

  • Official logo usage
  • Brand color system
  • Light and dark study modes
Input BDone

Product Direction

LEGAL-E is a legal learning engine, not a generic course website.

  • Student-first learning flow
  • Law workspace by article
  • Case-based reasoning
Input CDone

Learning Method

The learning experience is based on depth, recall, application, and mastery.

  • Quick revision path
  • Deep mastery path
  • Structured review cycle
Prerequisite 1Done

Product Blueprint

Defines launch scope and what is delayed.

  • Private alpha before beta
  • Launch language: English
  • Services visible, operations later
Prerequisite 2Done

IA and Routes

Defines the main areas users and the team will navigate.

  • Clear navigation
  • Member-only product areas
  • Controlled community surfaces
Prerequisite 3Done

Data Model

Defines the information the platform needs to store and connect.

  • Learners and roles
  • Legal content and progress
  • Reviews and checkpoints
Build 1Done

Product Foundation

Create the base experience that every product area depends on.

  • Product shell and active navigation
  • Brand UI and light/dark theme system
  • GitHub and Netlify deployment flow
Prerequisite: approved product direction, brand system, and route map.
Build 2In progress

Accounts and Data

Create accounts, learner profiles, roles, and secure member access.

  • Supabase schema and RLS applied
  • Supabase signup/login connected
  • Next: learner profile read/edit
Prerequisite: data foundation and access rules.
Build 3Core

Learning Engine

The daily student habit loop.

  • Quick Mode
  • Four depth levels
  • Day 1, 2, 4, 7 reviews
Prerequisite: auth, course tables, progress tables.
Build 4Core

Law Workspace

Article-level legal study surface.

  • Law library
  • Code and chapter context
  • Article notes and practice
Prerequisite: legal content tables and first CPC slice.
Build 5Core

Cases and Reasoning

Turns law study into application.

  • Case exercise detail
  • IRAC submissions
  • Compare-your-reasoning
Prerequisite: article workspace and Level 3 application.
Build 6Core

Profile and Admin

Make progress visible and content manageable.

  • Learning identity
  • Mistakes and notes archive
  • CMS-lite admin
Prerequisite: learning progress, notes, content state.
LaunchBeta

Student Beta

Polished release for students after alpha testing.

  • Responsive QA
  • Content seed
  • Analytics and feedback
Prerequisite: core flows stable and legal content reviewed.
DependencyDecision

External Coordination

Confirm ownership for the referenced coordination stream before dependent work begins.

  • Owner
  • Scope
  • Timeline and deliverables
Blocks only the work that depends on external input.
Later laneLater

Community Growth

Community expands after controlled learning participation works.

  • Curated reasoning answers
  • Case of the Week participation
  • Peer challenges
Later laneLater

Services and Commerce

Services can be presented early, then become operational after the learning beta.

  • Legal interpretation
  • Translation
  • Drafting and exam support

Critical Path

Product foundation, accounts and data, learning engine, law workspace, cases, profile/admin, then student beta.

Deferred Scope

Service intake, payments, full multilingual interface, public leaderboards, open discussion spaces, and advanced automated feedback.

Team Rule

Every downstream feature depends on clean content models, reviewed legal content, and a serious student-first interface.

Implementation Checklist

This section tracks execution without replacing the roadmap above. Done items stay visible, in-progress items stay marked, and future scope remains listed.

1. Project Foundation

Repository, deployment, brand shell, and public team visibility.

  • ✓GitHub repository connected.Remote repo is active and Netlify builds from the main branch.
  • ✓Netlify deployment connected with no Vercel dependency.Project uses Netlify runtime and deploys from GitHub commits.
  • ✓Public rebuild roadmap available for the team.The graph remains public while the app product routes remain protected.
  • ✓Redirect loop fixed.Root and Netlify's pretty checklist route resolve without bouncing between paths.
  • ✓Product shell and active navigation created.Logged-in product areas use a shared shell with sticky top bar, active route states, and responsive navigation.
  • ✓Brand UI and theme system created.Official logo assets and brand colors are used, with semantic tokens for headings, accents, surfaces, and primary actions.
  • ✓Light mode set as default.Dark mode is optional through the toggle, but the product opens in light mode first.
  • ✓Primary button contrast corrected.Primary actions use enforced brand button CSS with white text on LEGAL-E navy/blue backgrounds.
  • ✓No fake product data rule applied.Early product surfaces use empty-state hints instead of dummy learner progress or fake content.

2. Accounts and Data

Supabase, authentication, profiles, roles, and protected areas.

  • ✓Supabase project connected.Project ref mteaumaaxexxczbxekkf is linked and environment variables are ready for Netlify.
  • ✓Supabase CLI installed locally.The repo includes Supabase CLI scripts for login, link, and db push.
  • ✓Initial schema pushed.Profiles, laws, sections, articles, courses, modules, lessons, progress, reviews, and notes tables exist.
  • ✓Row level security enabled.Student-owned records are private; published content can be read; staff can manage content.
  • ✓Automatic profile creation added.New Supabase auth users get matching profile rows through the database trigger.
  • ✓Temporary Justin-only login replaced.The app now uses Supabase email/password auth instead of the old static username/password gate.
  • ✓Signup connected.Signup creates a Supabase user and stores onboarding fields in the profile.
  • ✓Login, logout, and protected routes connected.Product routes check the real Supabase user session.
  • ✓Profile read/edit connected.Profile displays real account data and saves full name, learner type, preferred mode, goal, and target date.
  • ✓Live signup/login QA on Netlify.Real account flow, session, profile save, logout, and re-login were confirmed.
  • ✓Promote Justin's account to admin.Justin's profile role is now admin in Supabase.
  • ✓Add admin/editor role checks in the interface.Admin surfaces now check profile role before showing content tools.
  • □Email confirmation UX.If Supabase email confirmation is enabled, show a clear confirmation-needed state after signup.

3. Content Admin

Internal tools for reviewed legal content and course structure.

  • ✓Admin dashboard authorization.Admin page checks the logged-in profile role before showing content tools.
  • ✓Laws admin list.Shows laws from Supabase with title, short title, jurisdiction, status, and updated date.
  • ✓Law create/edit form.Creates and updates slug, title, short title, jurisdiction, summary, and content status.
  • ✓Law sections admin.Creates sections, connects them to a law, and controls ordering.
  • ~Article editor.Next item: edit article number, title, official text, plain-English explanation, study notes, section, order, and status.
  • □Content status workflow.Support draft, review, published, and archived states without exposing draft content to students.
  • □Courses admin.Create courses with slug, title, description, and status.
  • □Modules admin.Create modules inside courses with ordering and review status.
  • □Lessons admin.Create article-linked lessons with level, body, order, and status.
  • □Empty-state and error handling.Every admin list needs clear empty states, save errors, and permission errors.

4. Learning Engine

Student study flow, review rhythm, and mastery signals.

  • □Learning hub reads real courses.Show published courses from Supabase with empty-state hints when none exist.
  • □Course detail reads modules.Display ordered modules and lessons for the selected course.
  • □Lesson page supports Level 1 exposure.Show article-linked teaching content, explanation, and basic checks.
  • □Lesson page supports Level 2 recall.Hide content and ask memory prompts before revealing the answer.
  • □Lesson page supports Level 3 application.Ask the learner to apply the rule to a short scenario using structured reasoning.
  • □Lesson page supports Level 4 mastery.Use mixed prompts, variations, and confidence checks before marking mastery.
  • □Progress write actions.Lesson completion creates or updates learner_progress for the logged-in user.
  • □Review generation.Completion creates scheduled review_items for the review rhythm.
  • □Review calendar reads due reviews.Show upcoming and overdue reviews from real learner data.
  • □Profile learning data.Profile should show real progress, due reviews, notes, and weak areas after study exists.

5. Law Workspace

Article-level legal study experience.

  • □Law library reads published laws.Replace static hints with published law records from Supabase.
  • □Law detail reads sections.Show section order, descriptions, and connected article groups.
  • □Section page reads articles.Display articles under the selected law section with status-safe visibility.
  • □Article page shows official text.Render reviewed official legal text, article number, title, and law context.
  • □Article page shows explanation and notes.Render plain-English explanation, study notes, and related learning prompts.
  • □Personal article notes.Logged-in learners can create, edit, and view their own notes.
  • □Related learning and case links.Article pages link into lessons, review prompts, and case exercises when available.
  • □Content-empty states.Unpublished or missing content should show calm team-facing hints, not fake article data.

6. Cases and Beta

Application, QA, and student beta readiness.

  • □Case content model.Add or extend schema for facts, linked articles, prompts, expected reasoning, and status if needed.
  • □Cases list reads approved cases.Show only reviewed or published cases to learners.
  • □Case detail page.Display facts, linked articles, issue prompts, and answer instructions.
  • □Student answer submission.Save each learner's issue, rule, analysis, and conclusion securely.
  • □Compare-your-reasoning reveal.Show model reasoning only after participation or after the case closes.
  • □Case of the Week flow.Curated weekly case surface without opening a full forum yet.
  • □Responsive QA.Check mobile, tablet, desktop, dark mode, light mode, and protected-route behavior.
  • □Analytics and feedback.Add basic event tracking and learner feedback capture before beta.
  • □Student beta readiness.Confirm account flow, content quality, learning loop, profile state, and support path before launch.