# Is Nimbly right for my project?

Choose Nimbly based on your domain, team and operational needs.

Nimbly fits projects where a team wants to define its own domain, presentation and behavior while using integrated resource, editing and operational foundations.

## Good starting points

Structured content sites, event programmes, membership systems, application portals and custom business tools can share the same underlying resource and composition mechanisms. The framework supplies building blocks; project-specific workflows still need to be implemented.

## Team requirements

Developers work with PHP, HTML, templates and command-line tooling. The frontend uses Tailwind CSS, DaisyUI and Alpine.js. Editors can use resource administration and authorized inline editing once the team defines the content model.

## Evaluate the workload

File-backed resources, caching and indexes are part of the architecture. Validate your expected record volume, query patterns, writes, media storage and concurrency with representative data. Do not assume a project-specific workflow, third-party connector or database query model exists without inspecting its implementation.

## Decide with a small feature

Build the [events example](/en/docs/learn/events/), configure a restricted editor role and test one integration. Review how the structure fits your team and how you will [operate](/en/docs/operate/deployment/) and [back up](/en/docs/operate/backup-recovery/) the system.