{entry.query}
- {entry.command}
-
- {entry.output.map((line) => (
-
- {line}
- ))}
- {entry.coreQuestion}
-- Without DevMap, your AI agent explores your codebase blindly, opening - files one by one, guessing what matters, rebuilding context from scratch - every session. -
- -- With DevMap, your agent gets a ready-made project map. Framework, entry - points, critical files, data flow, all structured, all accurate, all - generated from static analysis. -
- -{flow.command}
-
- {flow.output}
- - Your AI agent reads the map. Not the entire codebase. Faster execution. - Lower token usage. Better results. -
- -- Compatible with: {compatibleTools.join(", ")} -
-{entry.command}
-
- {command.name}{entry.command}
- {entry.coreQuestion}
-| - | Without DevMap | -With DevMap | -
|---|---|---|
| - {row.metric} - | -{row.without} | -{row.with} | -
+
+ {command}
+
+
+How it works
- -Static analysis
-
- One analyze pass builds the whole picture.
- Structure, routes, dependencies, critical files — computed once
- from your source code, deterministically.
-
Optional AI
-- Where a model is involved — enrichment, narration, answers — it - reads the structured snapshot instead of your raw code. AI is an - enhancement layer, not the foundation. -
-
+ Free and open source under the MIT license. Install it globally with{" "}
+ npm install -g @flaid/devmap when you want it on every project.
+
- DevMap analyzes your codebase once and builds a reusable context layer. - Routes, dependencies, entry points, critical files — all structured - so you stop re-explaining your project to every AI agent, every session. -
- -- One snapshot. Reused by every question after this. -
-+ DevMap reads your codebase and writes a map that developers and AI agents + can start from: entry points, critical files, features and routes. +
+ +Needs Node 22 or newer. No account or API key to analyze.
+ diff --git a/apps/web/src/components/landing/MethodSection.astro b/apps/web/src/components/landing/MethodSection.astro new file mode 100644 index 0000000..8c652f2 --- /dev/null +++ b/apps/web/src/components/landing/MethodSection.astro @@ -0,0 +1,161 @@ +--- +const steps = [ + "Scan files", + "Analyze files", + "Build the dependency graph", + "Detect the framework", + "Detect routes", + "Detect the database", + "Extract entities", + "Detect capabilities", + "Detect features", + "Infer the domain", + "Rank critical files", + "Generate flows" +]; +const optionalAi = "Infer the domain"; + +const frameworks = ["Next.js", "Astro", "Nuxt", "SvelteKit", "Express", "Fastify", "NestJS"]; +--- + +
+ Files, imports, routes, features and flows come from static analysis, so
+ the result doesn't change between runs. AI is optional and is used in
+ three places: inferring what the project is for, describing files, and
+ answering questions. If the provider fails, devmap analyze{" "}
+ still finishes.
+
{frameworks.join(", ")}.
+TypeScript, JavaScript, Vue, Svelte and Astro.
+Python, PHP, Go, Ruby, C# and Java: imports, exports and declarations.
+- devmap onboarding answers the one question every developer asks when - joining an unfamiliar project: -
- -"Where do I even begin?"
- -{item}
-- DevMap is MIT licensed and free to use. No subscription. No account - required. No DevMap servers involved. -
- -- If DevMap saves you time, consider supporting development. -
- -
+ devmap analyze writes a .devmap folder next to
+ your code. Agents open the small index first and follow it to the one
+ feature they need, instead of exploring the whole repository.
+
.devmap/{file.name}.devmap/index.json, trimmed, from analyzing this repository.
+ The highlighted lines are the entry points.
+ {lines.map((line) => (
+ {line.text}
+ ))}{point.text}
-- devmap fixes this: analyze once, reuse the map every session after. -