This is a large, ambitious transformation. Let me set up a task plan and gather full context on the current codebase before building.

Let me gather full context on the current design system and shared components before making changes.

I have a clear picture of the design system: primary blue #4f87ee, warm off-white background #f9f7f4, beige muted #e1d9cb, white cards, Inter font. I'll keep these colors exactly and focus on structure, depth, and polish. Let me start by building the shared design system — animation utilities plus reusable components for page headers, resource cards, and a newsletter section.

Now let me create the reusable components: a polished page header, a rich resource card, a section heading, and a newsletter signup.

Now let me create a centralized data file for all curated resources across subjects, so subject pages and the Resources Library stay consistent.

The shared design system is in place. Now let me move to the task and rebuild the homepage with all the requested sections.

Now let me rebuild the homepage with all the requested sections.

The homepage is rebuilt. Now let me move to the Learn hub and subject pages. I'll use a clean dynamic route driven by the resource data library. Let me check the existing Learn files first.

There are leftover pages from the old structure. I'll replace all individual subject pages with one clean dynamic route driven by the data library, delete the obsolete pages, and build the Learn hub.

Now let me build the Learn hub page and the dynamic subject route.

Now I can overwrite the Learn hub page with the new version.

Learn hub and subject pages are done. Now let me build the Study Paths, IB Hub, and University Hub. Let me move to the next task and check the existing files.

Now let me build the Study Paths page with interactive roadmaps. I'll create a client component for the expandable path stages.

Study Paths is done with interactive expandable stages. Now let me build the IB Hub and University Hub.

Let me build the IB Hub page with a serious, comprehensive structure.

Now I can write the new IB Hub page.

Now the University Hub. Let me read the existing file first.

IB Hub and University Hub are done. Now the Wellbeing page (with Spain/Europe support) and Resources Library.

Let me rebuild the Wellbeing page with deeper content and expanded Europe-wide support, keeping the Spain section.

This is a major upgrade brief. Let me reset my task plan to reflect the new priorities — finishing the in-flight pages plus adding the signature product features (dashboard, study system builder, search/filter, roadmap).

Let me gather context on the current data library, components, and the pages I still need to touch.

I have full context on the data model and components. Let me build the Resources Library with live search and filters. I'll create a client component driven by the existing allResources data.

Now let me update the Resources Library page to use this client component and the shared page header.

The Resources Library now has a live search bar plus subject/level/cost filter pills, a results counter, an empty state, and clear-all behavior — all driven by the shared curated data so it stays in sync with subject pages. Now let me build the signature Study System Builder.

Now I'll build Lumindora's signature feature — the Study System Builder. It's a guided multi-step planner that generates a personalized roadmap, weekly structure, and curated resources from the existing data library.

The Study System Builder is Lumindora's signature feature: a four-step guided flow (subject → level → goal → weekly time) that generates a phased learning roadmap, a realistic weekly hour breakdown, and curated resources matched to the student's level — all pulled live from the data library. Now let me build the student Dashboard mockup.

Now I'll build a realistic student Dashboard mockup — a product preview showing how Lumindora works once a student is using it daily.

I left an unused variable in the study path map. Let me clean that up.

The Dashboard preview shows a Notion/Linear-style interface with a streak, weekly hours, goals met, continue-learning card, an active study path with completed phases, per-subject progress bars, upcoming tasks, and saved resources — clearly labeled as a product preview. Now let me add deeper intellectual content to the subject pages by extending the data model with misconceptions, common mistakes, and learning strategies.

I'll add the deep content as a separate keyed map appended to the data file (cleaner than editing all 7 objects), then render it on the subject page. Let me read the current subject page first.

Now let me append the deep insights map to the data file, keyed by slug.

Now let me update the subject page to render this deep content.

Subject pages now have authoritative depth: why students struggle, common misconceptions, typical mistakes, learning strategies, the best topic order, and a CTA into the builder. Now let me rebuild the Home page with concrete How It Works, who it's for, the signature feature, and a roadmap.

Let me read the current homepage and footer to rebuild consistently.

Now I'll rebuild the homepage with the signature feature, concrete How It Works, a "who it's for" section replacing fake testimonials, restructured stats, and a future roadmap.

The homepage now leads with the signature Study System Builder (with a visual mock), has concrete three-step How It Works, replaces fake testimonials with a "Who Lumindora is built for" section, removes the underwhelming stats, and adds a 2026–2028 future roadmap. Now let me rebuild the About page with an authentic founder narrative.

Now I'll rebuild the About page with an authentic, founder-driven narrative (no emojis), clear principles, and a future roadmap.

The About page now opens with an authentic, first-person founder narrative about living the guidance gap, a pull quote, three honest principles, and the future roadmap. Now let me wire navigation and footer to all the new pages (Study Builder, Dashboard).

I'll add the Study Builder as a highlighted CTA button and fold Resources Library + Dashboard into the Learn submenu to avoid an overcrowded nav. Let me also fix the footer's outdated "Mindora" social handles.

Now let me update the footer — add the new pages and fix the outdated "Mindora" social handles.

All pages and components are now wired together. Let me mark the work complete.

I've transformed Lumindora from a static concept into a credible, operational EdTech product while preserving its exact color palette and branding. The biggest additions are its signature feature — the Study System Builder, a four-step guided flow that generates a personalized roadmap, weekly structure, and level-matched resources — plus a Resources Library with live search and subject/level/cost filters, and a Notion-style Dashboard preview showing streaks, study paths, and progress. I also gave each subject page real intellectual depth (why students struggle, misconceptions, common mistakes, learning strategies, and the best topic order), rebuilt the Home page with a concrete "Explore → Build → Grow" flow, a "Who Lumindora is built for" section replacing the artificial testimonials, and a 2026–2028 roadmap, and rewrote About as an honest first-person founder narrative. Everything is wired through the navigation (Study Builder is now a highlighted CTA) and footer, with the outdated "Mindora" handles corrected.

One note: the published site still won't open until you disable Vercel Deployment Protection in your project settings — that's separate from the code and unchanged by this work.