Adopt the Section IDs extension

See gh-1009

Author: wilkinsona

docs/build.gradle

@@ -9,6 +9,7 @@ configurations {
 }
 
 dependencies {
+	asciidoctorExt("io.spring.asciidoctor:spring-asciidoctor-extensions-section-ids:0.6.3")
 	asciidoctorExt("io.spring.asciidoctor.backends:spring-asciidoctor-backends:0.0.5")
 
 	testCompileOnly("org.hamcrest:hamcrest-core")

docs/src/docs/asciidoc/configuration.adoc

@@ -5,14 +5,14 @@ This section covers how to configure Spring REST Docs.
 
 
 
-[[configuration-uris]]
+[[configuration.uris]]
 === Documented URIs
 
 This section covers configuring documented URIs.
 
 
 
-[[configuration-uris-mockmvc]]
+[[configuration.uris.mockmvc]]
 ==== MockMvc URI Customization
 
 When using MockMvc, the default configuration for URIs documented by Spring REST Docs is as follows:
@@ -45,7 +45,18 @@ TIP: To configure a request's context path, use the `contextPath` method on `Moc
 
 
 
-[[configuration-uris-webtestclient]]
+[[configuration.uris.rest-assured]]
+==== REST Assured URI Customization
+
+REST Assured tests a service by making actual HTTP requests. As a result, URIs must be
+customized once the operation on the service has been performed but before it is
+documented. A
+<<customizing-requests-and-responses.preprocessors.modify-uris, REST-Assured-specific
+preprocessor>> is provided for this purpose.
+
+
+
+[[configuration.uris.webtestclient]]
 ==== WebTestClient URI Customization
 
 When using WebTestClient, the default base for URIs documented by Spring REST Docs is `http://localhost:8080`.
@@ -60,7 +71,7 @@ include::{examples-dir}/com/example/webtestclient/CustomUriConfiguration.java[ta
 
 
 
-[[configuration-snippet-encoding]]
+[[configuration.snippet-encoding]]
 === Snippet Encoding
 
 The default snippet encoding is `UTF-8`.
@@ -85,7 +96,7 @@ You can configure the JVM's default `Charset` by using the `file.encoding` syste
 
 
 
-[[configuration-snippet-template-format]]
+[[configuration.snippet-template-format]]
 === Snippet Template Format
 
 The default snippet template format is Asciidoctor.
@@ -107,7 +118,7 @@ include::{examples-dir}/com/example/webtestclient/CustomFormat.java[tags=custom-
 
 
 
-[[configuration-default-snippets]]
+[[configuration.default-snippets]]
 === Default Snippets
 
 Six snippets are produced by default:
@@ -136,7 +147,7 @@ include::{examples-dir}/com/example/webtestclient/CustomDefaultSnippets.java[tag
 
 
 
-[[configuration-default-preprocessors]]
+[[configuration.default-preprocessors]]
 === Default Operation Preprocessors
 
 You can configure default request and response preprocessors during setup by using the `RestDocumentationConfigurer` API.

docs/src/docs/asciidoc/contributing.adoc

@@ -6,23 +6,23 @@ However, we cannot achieve that goal without your contributions.
 
 
 
-[[contributing-questions]]
+[[contributing.questions]]
 === Questions
 
 You can ask questions about Spring REST Docs on https://stackoverflow.com[Stack Overflow] by using the `spring-restdocs` tag.
 Similarly, we encourage you to help your fellow Spring REST Docs users by answering questions.
 
 
 
-[[contributing-bugs]]
+[[contributing.bugs]]
 === Bugs
 
 If you believe you have found a bug, please take a moment to search the {github}/issues?q=is%3Aissue[existing issues].
 If no one else has reported the problem, please {github}/issues/new[open a new issue] that describes the problem in detail and, ideally, includes a test that reproduces it.
 
 
 
-[[contributing-enhancements]]
+[[contributing.enhancements]]
 === Enhancements
 
 If you would like an enhancement to be made to Spring REST Docs, pull requests are most welcome.

docs/src/docs/asciidoc/customizing-requests-and-responses.adoc

@@ -64,19 +64,19 @@ See <<Preprocessors, below>> for further details.
 
 
 
-[[customizing-requests-and-responses-preprocessors]]
+[[customizing-requests-and-responses.preprocessors]]
 === Preprocessors
 
 
 
-[[customizing-requests-and-responses-preprocessors-pretty-print]]
+[[customizing-requests-and-responses.preprocessors.pretty-print]]
 ==== Pretty Printing
 
 `prettyPrint` on `Preprocessors` formats the content of the request or response to make it easier to read.
 
 
 
-[[customizing-requests-and-responses-preprocessors-mask-links]]
+[[customizing-requests-and-responses.preprocessors.mask-links]]
 ==== Masking Links
 
 If you are documenting a hypermedia-based API, you may want to encourage clients to navigate the API by using links rather than through the use of hard coded URIs.
@@ -86,32 +86,32 @@ You can also specify a different replacement if you wish.
 
 
 
-[[customizing-requests-and-responses-preprocessors-modify-headers]]
+[[customizing-requests-and-responses.preprocessors.modify-headers]]
 ==== Modifying Headers
 
 You can use `modifyHeaders` on `Preprocessors` to add, set, and remove request or response headers.
 
 
 
-[[customizing-requests-and-responses-preprocessors-replace-patterns]]
+[[customizing-requests-and-responses.preprocessors.replace-patterns]]
 ==== Replacing Patterns
 
 `replacePattern` on `Preprocessors` provides a general purpose mechanism for replacing content in a request or response.
 Any occurrences that match a regular expression are replaced.
 
 
 
-[[customizing-requests-and-responses-preprocessors-modify-uris]]
+[[customizing-requests-and-responses.preprocessors.modify-uris]]
 ==== Modifying URIs
 
-TIP: If you use MockMvc or a WebTestClient that is not bound to a server, you should customize URIs by <<configuration-uris, changing the configuration>>.
+TIP: If you use MockMvc or a WebTestClient that is not bound to a server, you should customize URIs by <<configuration.uris, changing the configuration>>.
 
 You can use `modifyUris` on `Preprocessors` to modify any URIs in a request or a response.
 When using `WebTestClient` bound to a server, this lets you customize the URIs that appear in the documentation while testing a local instance of the service.
 
 
 
-[[customizing-requests-and-responses-preprocessors-writing-your-own]]
+[[customizing-requests-and-responses.preprocessors.writing-your-own]]
 ==== Writing Your Own Preprocessor
 
 If one of the built-in preprocessors does not meet your needs, you can write your own by implementing the `OperationPreprocessor` interface.