Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Clarifying Bundle Best Practices is for *reusable* bundles #4250

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 12 additions & 5 deletions cookbook/bundles/best_practices.rst
Original file line number Diff line number Diff line change
@@ -1,12 +1,19 @@
.. index::
single: Bundle; Best practices

How to Use best Practices for Structuring Bundles
=================================================
Best Practices for Reusable Bundles
===================================

A bundle is a directory that has a well-defined structure and can host anything
from classes to controllers and web resources. Even if bundles are very
flexible, you should follow some best practices if you want to distribute them.
There are 2 types of bundles:

* Application-specific bundles: only used to build your application;
* Reusable bundles: meant to be shared across many projects.

This article is all about how to structure your **reusable bundles** so that
they're easy to configure and extend. Many of these recommendations do not
apply to application bundles because you'll want to keep those as simple
as possible. For application bundles, just follow the practices shown throughout
the book and cookbook.

.. index::
pair: Bundle; Naming conventions
Expand Down