Inline links to Symfony docs

Author: wouterj

book/from_flat_php_to_symfony2.rst

@@ -320,6 +320,8 @@ As it stands now, that code would need to be added to every controller file.
 If you forget to include something in one file, hopefully it doesn't relate
 to security...
 
+.. _book-from_flat_php-front-controller:
+
 A "Front Controller" to the Rescue
 ----------------------------------
 

create_framework/front-controller.rst

@@ -71,7 +71,7 @@ routing all client requests to a single PHP script.
 .. tip::
 
     Exposing a single PHP script to the end user is a design pattern called
-    the "`front controller`_".
+    the ":ref:`front controller <book-from_flat_php-front-controller>`".
 
 Such a script might look like the following::
 
@@ -237,5 +237,3 @@ variable.
 
     If you decide to stop here, you can probably enhance your framework by
     extracting the URL map to a configuration file.
-
-.. _`front controller`: http://symfony.com/doc/current/book/from_flat_php_to_symfony2.html#a-front-controller-to-the-rescue

create_framework/http-foundation.rst

@@ -78,8 +78,8 @@ unit test for the above code::
 .. note::
 
     If our application were just slightly bigger, we would have been able to
-    find even more problems. If you are curious about them, read the `Symfony
-    versus Flat PHP`_ chapter of the Symfony documentation.
+    find even more problems. If you are curious about them, read the
+    :doc:`/book/from_flat_php_to_symfony2` chapter of the book.
 
 At this point, if you are not convinced that security and testing are indeed
 two very good reasons to stop writing code the old way and adopt a framework
@@ -302,7 +302,6 @@ applications using it (like `Symfony`_, `Drupal 8`_, `phpBB 4`_, `ezPublish
 5`_, `Laravel`_, `Silex`_, and `more`_).
 
 .. _`Twig`: http://twig.sensiolabs.org/
-.. _`Symfony versus Flat PHP`: http://symfony.com/doc/current/book/from_flat_php_to_symfony2.html
 .. _`HTTP specification`: http://tools.ietf.org/wg/httpbis/
 .. _`audited`: http://symfony.com/blog/symfony2-security-audit
 .. _`Symfony`: http://symfony.com/

create_framework/http-kernel-controller-resolver.rst

@@ -142,7 +142,8 @@ method is not defined, an argument has no matching attribute, ...).
     With the great flexibility of the default controller resolver, you might
     wonder why someone would want to create another one (why would there be an
     interface if not?). Two examples: in Symfony, ``getController()`` is
-    enhanced to support `controllers as services`_; and in
+    enhanced to support
+    :doc:`controllers as services </cookbook/controller/service>`; and in
     `FrameworkExtraBundle`_, ``getArguments()`` is enhanced to support
     parameter converters, where request attributes are converted to objects
     automatically.

create_framework/http-kernel-httpkernel-class.rst

@@ -122,9 +122,9 @@ And in your controller, return a ``StreamedResponse`` instance instead of a
 
 .. tip::
 
-    Read the `Internals`_ chapter of the Symfony documentation to learn more
-    about the events dispatched by HttpKernel and how they allow you to change
-    the flow of a request.
+    Read the :doc:`/reference/events` reference to learn more about the events
+    dispatched by HttpKernel and how they allow you to change the flow of a
+    request.
 
 Now, let's create a listener, one that allows a controller to return a string
 instead of a full Response object::
@@ -200,5 +200,3 @@ worlds: a custom framework, tailored to your needs, but based on a rock-solid
 and well maintained low-level architecture that has been proven to work for
 many websites; a code that has been audited for security issues and that has
 proven to scale well.
-
-.. _`Internals`: http://symfony.com/doc/current/book/internals.html#events

create_framework/http-kernel-httpkernelinterface.rst

@@ -40,7 +40,7 @@ Update your framework so that it implements this interface::
     }
 
 Even if this change looks trivial, it brings us a lot! Let's talk about one of
-the most impressive one: transparent `HTTP caching`_ support.
+the most impressive one: transparent :doc:`HTTP caching </book/http_cache>` support.
 
 The ``HttpCache`` class implements a fully-featured reverse proxy, written in
 PHP; it implements ``HttpKernelInterface`` and wraps another

create_framework/introduction.rst

@@ -121,6 +121,5 @@ In the next chapter, we are going to introduce the HttpFoundation Component
 and see what it brings us.
 
 .. _`Symfony`: http://symfony.com/
-.. _`documentation`: http://symfony.com/doc
 .. _`Silex`: http://silex.sensiolabs.org/
 .. _`Composer`: http://packagist.org/about-composer

create_framework/routing.rst

@@ -78,10 +78,12 @@ of default values for route attributes (``array('name' => 'World')``).
 
 .. note::
 
-    Read the official `documentation`_ for the Routing component to learn more
-    about its many features like URL generation, attribute requirements, HTTP
-    method enforcements, loaders for YAML or XML files, dumpers to PHP or
-    Apache rewrite rules for enhanced performance, and much more.
+    Read the
+    :doc:`Routing component documentation </components/routing/introduction>` to
+    learn more about its many features like URL generation, attribute
+    requirements, HTTP method enforcements, loaders for YAML or XML files,
+    dumpers to PHP or Apache rewrite rules for enhanced performance, and much
+    more.
 
 Based on the information stored in the ``RouteCollection`` instance, a
 ``UrlMatcher`` instance can match URL paths::
@@ -218,5 +220,3 @@ generate absolute URLs::
         $dumper = new Routing\Matcher\Dumper\PhpMatcherDumper($routes);
 
         echo $dumper->dump();
-
-.. _`documentation`: http://symfony.com/doc/current/components/routing.html