EDUCATIONOverviewStudentsTeachersSchoolsCurriculumProject Library
EDUCATION · CURRICULUM

Concepts unlock because you need them.

Traditional curricula are linear: Python → variables → functions → classes, whether or not you care yet. Cartara organizes knowledge around projects — you meet each concept at the exact moment your build demands it, which is when it actually sticks.

EXAMPLE PROJECT

Build a Website — what it unlocks

One project, seven concepts — each introduced by a real need, not a chapter number.

  1. 01HTMLStructure the page you can already picture
  2. 02CSSMake it look the way you imagined
  3. 03LayoutArrange real content, responsively
  4. 04ComponentsStop repeating yourself
  5. 05APIsPull in live data your site needs
  6. 06AuthenticationLet users sign in — because yours want to
  7. 07DeploymentPut it on the internet for real people
THE KNOWLEDGE GRAPH

Learning that's visual and interconnected

Every concept a project touches becomes a node on the student's knowledge graph, linked to guides, related projects, and resources. Build an AI application and its neighborhood lights up:

APIsAuthenticationDatabasesUIAgentsPrompt engineeringDeploymentTesting

The same graph powers assessment: comprehension checks attach evidence to each node, so “what a student knows” is a map you can inspect — not a grade you have to trust.

Frequently asked questions

What is project-based learning?
Project-based learning teaches skills by building real, complete projects rather than working through isolated exercises or lectures. On Cartara the project is the unit of learning: you choose something worth building, and each concept you need — layout, APIs, authentication, deployment — is introduced at the moment the project demands it.
What is a knowledge-graph curriculum?
Instead of a linear sequence of chapters, a knowledge-graph curriculum maps concepts as connected nodes. Every concept a project touches becomes a node linked to guides, related projects, and resources — so learning is visual and interconnected, and you can see how what you just learned connects to what comes next.
Why learn concepts in context instead of in a fixed order?
Concepts learned because a real build needs them stick better than concepts memorized in the abstract. When your website needs users to sign in, you learn authentication then — motivated, in context, and applied immediately — rather than studying it weeks before you have any use for it.
How does Cartara know what a student understands?
The same knowledge graph that organizes the curriculum powers assessment: comprehension checks attach evidence to each concept node from the student's own code. What a student knows becomes a map you can inspect concept by concept, not a single grade you have to take on faith.
See the project library →Using this in a classroom?