# Nimbly

> Nimbly is a lean, open source, full-stack web framework. Code, content and data live as plain files in Git, and a request runs its route and nothing else.

- Atomic design. Pages, components, data and routes are building blocks that stay reusable as the product grows.
- Made for agentic coding. Small targets, clear contracts, predictable places, documentation built for agents and changes that are reviewable in Git.
- No bloat. No database server, no plugin stack and a lean frontend bundle.
- Everything included. Template engine, file-based resources, REST API, admin with inline editing, users and roles, forms, i18n, scheduler, email and more.
- Developer experience. A dev container and a site up with two commands, fast builds, small readable files in predictable places.

All pages in one file: https://atomic.nimblyweb.com/llms-full.txt
Source code: https://github.com/Nimbly-Web-Systems/nimbly-core

## Learn

- [Introduction](https://atomic.nimblyweb.com/en/docs/learn/introduction.md): What Nimbly is, what a project looks like and where to read next.
- [Installation](https://atomic.nimblyweb.com/en/docs/learn/installation.md): Clone core, add your application and run two commands to have a working site.
- [For AI agents](https://atomic.nimblyweb.com/en/docs/learn/for-ai-agents.md): How an agent works in a Nimbly project: where to read, where each block lives and which rules always hold.

## Concepts

- [Atomic design in Nimbly](https://atomic.nimblyweb.com/en/docs/concepts/atomic-design.md): A small set of atoms and one way to combine them: every project composes exactly the blocks it needs.
- [Core and ext](https://atomic.nimblyweb.com/en/docs/concepts/core-and-ext.md): Two repositories and one runtime: what belongs in core, what belongs in ext and how the folders are laid out.
- [Templates and shortcodes](https://atomic.nimblyweb.com/en/docs/concepts/templates.md): How a page is assembled from small templates and shortcodes, and how templates are found.
- [Resources: data as files](https://atomic.nimblyweb.com/en/docs/concepts/resources.md): The data layer: file-backed records, the .meta file that describes them, and the conventions every resource follows.
- [Routing](https://atomic.nimblyweb.com/en/docs/concepts/routing.md): Folders are routes: static and dynamic routes, input checks at the boundary, subdomain folders and localized addresses.
- [Field-level i18n](https://atomic.nimblyweb.com/en/docs/concepts/i18n.md): Languages as part of the system: language routes, translated fields, static texts and templates per language.
- [Choosing the rendering boundary](https://atomic.nimblyweb.com/en/docs/concepts/rendering-boundary.md): What is rendered on the server, what runs in the browser and how to choose the boundary between them.
- [Lean by design](https://atomic.nimblyweb.com/en/docs/concepts/lean-by-design.md): KISS, YAGNI and DRY as working rules: simple parts, no speculative code, one place for each thing.

## Reference

- [CLI](https://atomic.nimblyweb.com/en/docs/reference/cli.md): Every command of ./nimbly: setup, builds, tests, upkeep, scheduler and statistics.