Merge branch '3.4'

* 3.4:
  Add "Next" links to Best Practices

Author: weaverryan

best_practices/business-logic.rst

@@ -268,6 +268,10 @@ were defined by the PHP community. You can learn more about
 use the `PHP-CS-Fixer`_, which is a command-line utility that can fix the
 coding standards of an entire codebase in a matter of seconds.
 
+----
+
+Next: :doc:`/best_practices/controllers`
+
 .. _`full definition`: https://en.wikipedia.org/wiki/Business_logic
 .. _`Doctrine project`: http://www.doctrine-project.org/
 .. _`fixture class`: https://symfony.com/doc/current/bundles/DoctrineFixturesBundle/index.html#writing-simple-fixtures

best_practices/configuration.rst

@@ -210,5 +210,9 @@ through environment variables:
             # ...
             password: "%env(DB_PASSWORD)%"
 
+----
+
+Next: :doc:`/best_practices/business-logic`
+
 .. _`feature toggles`: https://en.wikipedia.org/wiki/Feature_toggle
 .. _`constant() function`: http://twig.sensiolabs.org/doc/functions/constant.html

best_practices/controllers.rst

@@ -237,4 +237,8 @@ If you need to execute some code before or after the execution of your controlle
 you can use the EventDispatcher component to
 :doc:`set up before and after filters </event_dispatcher/before_after_filters>`.
 
+----
+
+Next: :doc:`/best_practices/templates`
+
 .. _`ParamConverter`: https://symfony.com/doc/current/bundles/SensioFrameworkExtraBundle/annotations/converters.html

best_practices/creating-the-project.rst

@@ -91,6 +91,10 @@ Symfony applications can still use third-party bundles (installed in ``vendor/``
 to add features, but you should use PHP namespaces instead of bundles to organize
 your own code.
 
+----
+
+Next: :doc:`/best_practices/configuration`
+
 .. _`Composer`: https://getcomposer.org/
 .. _`Symfony Flex`: https://github.com/symfony/flex
 .. _`Symfony Skeleton`: https://github.com/symfony/skeleton

best_practices/forms.rst

@@ -192,3 +192,5 @@ handling the form submit. For example, you *could* have a ``new()`` action that
 *only* renders the form and a ``create()`` action that *only* processes the form
 submit. Both those actions will be almost identical. So it's much simpler to let
 ``new()`` handle everything.
+
+Next: :doc:`/best_practices/i18n`

best_practices/i18n.rst

@@ -76,4 +76,8 @@ English in the application would be:
         </file>
     </xliff>
 
+----
+
+Next: :doc:`/best_practices/security`
+
 .. _`JMSTranslationBundle`: https://github.com/schmittjoh/JMSTranslationBundle

best_practices/introduction.rst

@@ -98,5 +98,9 @@ for not doing it are various:
 * The amount of work spent on this could be better dedicated to improving
   your tests or adding features that provide real value to the end users.
 
+----
+
+Next: :doc:`/best_practices/creating-the-project`
+
 .. _`Fabien Potencier`: https://connect.sensiolabs.com/profile/fabpot
 .. _`Symfony Demo`: https://github.com/symfony/demo

best_practices/security.rst

@@ -385,6 +385,10 @@ If your company uses a user login method not supported by Symfony, you can
 develop :doc:`your own user provider </security/custom_provider>` and
 :doc:`your own authentication provider </security/custom_authentication_provider>`.
 
+----
+
+Next: :doc:`/best_practices/web-assets`
+
 .. _`ParamConverter`: https://symfony.com/doc/current/bundles/SensioFrameworkExtraBundle/annotations/converters.html
 .. _`@Security annotation`: https://symfony.com/doc/current/bundles/SensioFrameworkExtraBundle/annotations/security.html
 .. _`FOSUserBundle`: https://github.com/FriendsOfSymfony/FOSUserBundle

best_practices/templates.rst

@@ -116,5 +116,9 @@ If you're using the :ref:`default services.yaml configuration <service-container
 you're done! Symfony will automatically know about your new service and tag it to
 be used as a Twig extension.
 
+----
+
+Next: :doc:`/best_practices/forms`
+
 .. _`Twig`: http://twig.sensiolabs.org/
 .. _`Parsedown`: http://parsedown.org/

best_practices/web-assets.rst

@@ -25,6 +25,11 @@ the JavaScript-based tools used in modern web applications. Check out the
 `official Webpack Encore documentation`_ to learn more about all the available
 features.
 
+----
+
+Next: :doc:`/best_practices/tests`
+
+.. _`official Assetic documentation`: https://github.com/kriswallsmith/assetic
 .. _`Webpack Encore`: https://github.com/symfony/webpack-encore
 .. _`Webpack`: https://webpack.js.org/
 .. _`official Webpack Encore documentation`: https://symfony.com/doc/current/frontend.html