Ver Fonte

added prev/next links to docs

Travis Northcutt há 13 anos atrás
pai
commit
cee5fed25f
7 ficheiros alterados com 15 adições e 0 exclusões
  1. 2 0
      doc/00-intro.md
  2. 2 0
      doc/01-basic-usage.md
  3. 2 0
      doc/02-libraries.md
  4. 2 0
      doc/03-cli.md
  5. 2 0
      doc/04-schema.md
  6. 3 0
      doc/05-repositories.md
  7. 2 0
      doc/06-community.md

+ 2 - 0
doc/00-intro.md

@@ -59,3 +59,5 @@ autoloading:
     require 'vendor/.composer/autoload.php';
     require 'vendor/.composer/autoload.php';
 
 
 That's all it takes to have a basic setup.
 That's all it takes to have a basic setup.
+
+[Basic Usage](01-basic-usage.md) →

+ 2 - 0
doc/01-basic-usage.md

@@ -177,3 +177,5 @@ This can be useful for autoloading classes in a test suite, for example.
 > **Note:** Composer provides its own autoloader. If you don't want to use
 > **Note:** Composer provides its own autoloader. If you don't want to use
 that one, you can just include `vendor/.composer/autoload_namespaces.php`,
 that one, you can just include `vendor/.composer/autoload_namespaces.php`,
 which returns an associative array mapping namespaces to directories.
 which returns an associative array mapping namespaces to directories.
+
+← [Intro](00-intro.md)  |  [Libraries](02-libraries.md) →

+ 2 - 0
doc/02-libraries.md

@@ -158,3 +158,5 @@ publish it on packagist as well. And this is really easy.
 You simply hit the big "Submit Package" button and sign up. Then you submit
 You simply hit the big "Submit Package" button and sign up. Then you submit
 the URL to your VCS repository, at which point packagist will start crawling
 the URL to your VCS repository, at which point packagist will start crawling
 it. Once it is done, your package will be available to anyone.
 it. Once it is done, your package will be available to anyone.
+
+← [Basic usage](01-basic-usage.md) |  [Command-line interface](03-cli.md) →

+ 2 - 0
doc/03-cli.md

@@ -184,3 +184,5 @@ commands) to finish executing. The default value is 60 seconds.
 If you are using composer from behind an HTTP proxy, you can use the standard
 If you are using composer from behind an HTTP proxy, you can use the standard
 `HTTP_PROXY` or `http_proxy` env vars. Simply set it to the URL of your proxy.
 `HTTP_PROXY` or `http_proxy` env vars. Simply set it to the URL of your proxy.
 Many operating systems already set this variable for you.
 Many operating systems already set this variable for you.
+
+← [Libraries](02-libraries.md)  |  [Schema](04-schema.md) →

+ 2 - 0
doc/04-schema.md

@@ -388,3 +388,5 @@ dir` (from config).
 See (Vendor Bins)[articles/vendor-bins] for more details.
 See (Vendor Bins)[articles/vendor-bins] for more details.
 
 
 Optional.
 Optional.
+
+← [Command-line interface](03-cli.md)  |  [Repositories](05-repositories.md) →

+ 3 - 0
doc/05-repositories.md

@@ -262,3 +262,6 @@ You can disable the default packagist repository by adding this to your
             }
             }
         ]
         ]
     }
     }
+
+
+← [Schema](04-schema.md)  |  [Community](06-community.md) →

+ 2 - 0
doc/06-community.md

@@ -26,3 +26,5 @@ The developer mailing list is on [google groups](http://groups.google.com/group/
 IRC channels are available for discussion as well, on
 IRC channels are available for discussion as well, on
 irc.freenode.org [#composer](irc://irc.freenode.org/composer) for users and
 irc.freenode.org [#composer](irc://irc.freenode.org/composer) for users and
 [#composer-dev](irc://irc.freenode.org/composer-dev) for development.
 [#composer-dev](irc://irc.freenode.org/composer-dev) for development.
+
+← [Repositories](05-repositories.md)