A collection of proven guidelines for building, deploying, and maintaining Laravel applications.
Every Laravel project is different. What works well for one project might not suit another. These guidelines are suggestions, not strict rules.
Project budget matters too. With limited resources, you may not implement every guideline perfectly. That's okay. Even partial implementation of these practices will benefit your project in the long run.
We welcome contributions from the Laravel community. For version 1, we're focusing on widely accepted practices. You can add your own guidelines too.
Current Status: Some sections are still under development. We're building this incrementally to keep the scope manageable.
- Choose a category - Find the best section for your guideline
- Create a clear title - Make it descriptive and concise
- Write a brief introduction - Explain what the practice is
- Add a "Why" section - Explain the benefits
- Include code examples - Show practical implementation
- Define project suitability - When to use this practice and when not to
- Add resources - Link to relevant documentation or articles
- Keep a tight focus - Each best practice should cover one specific topic
- Avoid mixing topics - Configuration, deployment, and infrastructure details should be separate practices
- Link to related practices - Reference other best practices instead of explaining them in detail
- Minimal, relevant examples - Include only code examples that directly demonstrate the core practice
This guide is evolving. We welcome your ideas on structure, content, and organization. If you have questions feel free to ask