English
Understand the application stack
Understand which part of the application handles which work before extending a project. This guide explains the stack described in the documentation without assuming a downloadable package is available.
What you will learn
You will be able to describe the application, interface, and data responsibilities when discussing a change with a developer.
The application handles server work
PHP and Laravel provide the application foundation. This is the part to consider when a change concerns server-side behavior, data handling, or connected services. Begin by describing the user journey and the information it needs rather than choosing a technology in isolation.
The interface presents the journey
React and Inertia provide interactive interfaces. Tailwind CSS and shadcn-compatible primitives support presentation. Separate a change in wording or appearance from a change in what the application does. Use the existing editor for supported text and design choices before planning custom code.
Local and production data have different roles
The documentation describes SQLite for simple local work and PostgreSQL in production. A local example is not a production hosting plan. Discuss the application, database, file storage, secure connections, and backups together with the developer who will set up the project.
Prepare a useful technical handoff
Explain what the visitor should do, what data the journey needs, which outside services are involved, and how you will test the result. The downloadable product is intended to remain self-hostable, but operating it still requires technical setup and care. Avoid treating a coding agent or the starting code as a substitute for review and maintenance.
Put it into practice
Your handoff should connect the user journey to interface, application, data, and operational work. Use the setup guide to turn those responsibilities into a project plan.