Fix the broken links in the documentation

documentation/articles/BroadcastingMessagesToOtherUsers.asciidoc

@@ -9,8 +9,8 @@ layout: page
 
 In this tutorial we will create an application where any user can send a
 broadcast message to all other active users. We will start from a
-project where push has been enabled (see link:EnablingServerPush.asciidoc[Enabling
-server push] for details).
+project where push has been enabled (see <<EnablingServerPush#, Enabling
+server push>> for details).
 
 For simplicity, we will use a static `Broadcaster` which is shared between
 all users and all sessions. Each UI will register itself to this

documentation/articles/CreatingAComponentExtension.asciidoc

@@ -10,7 +10,7 @@ layout: page
 In this tutorial we create a simple extension that can be attached to a
 `PasswordField`, displaying a floating notification if the user's Caps
 Lock seems to be enabled. We assume the reader is already familiar with
-the link:CreatingAUIExtension.asciidoc[Creating a UI extension]
+the <<CreatingAUIExtension#, Creating a UI extension>>
 tutorial.
 
 This extension has almost no server-side functionality; the whole Extension

documentation/articles/CreatingMultiTabApplications.asciidoc

@@ -31,4 +31,4 @@ public void init(VaadinRequest request) {
 
 More examples on URI fragments and parameters can be found at:
 
-* link:UsingURIFragments.asciidoc[Using URI fragments]
+* <<UsingURIFragments#, Using URI fragments>>

documentation/articles/IntegratingAJavaScriptLibraryAsAnExtension.asciidoc

@@ -8,12 +8,12 @@ layout: page
 = Integrating a JavaScript library as an extension
 
 JavaScript can also be used for creating Extensions e.g. for integrating
-existing JavaScript libraries. See link:CreatingAUIExtension.asciidoc[Creating a UI extension] for general information about Extensions. The main
+existing JavaScript libraries. See <<CreatingAUIExtension#, Creating a UI extension>> for general information about Extensions. The main
 difference when using JavaScript is that you extend
 `AbstractJavaScriptExtension`, that your shared state class should
 extend `JavaScriptExtensionState` and then of course that your
-client-side implementation is written in JavaScript. See link:IntegratingAJavaScriptComponent.asciidoc[Integrating a
-JavaScript component] for basic information about how to use JavaScript
+client-side implementation is written in JavaScript. See <<IntegratingAJavaScriptComponent#, Integrating a
+JavaScript component>> for basic information about how to use JavaScript
 for your client-side logic.
 
 This tutorial will create a simple Extension for integrating

documentation/articles/UsingAJavaScriptLibraryOrAStyleSheetInAnAddOn.asciidoc

@@ -21,7 +21,7 @@ defining class is located. This means that e.g.
 `@StyleSheet({"redbutton.css"})` on the class `com.example.RedButton` will
 cause the file `com/example/redbutton.css` on the classpath to be loaded
 in the browser. `@JavaScript` works in exactly the same way - see
-link:IntegratingAJavaScriptComponent.asciidoc[Integrating a JavaScript component]
+<<IntegratingAJavaScriptComponent#, Integrating a JavaScript component>>
 for a practical example.
 
 [source,java]

documentation/articles/UsingRPCToSendEventsToTheClient.asciidoc

@@ -96,8 +96,8 @@ public class MyComponentConnector extends AbstractComponentConnector {
 ....
 
 (`MyComponentServerRpc` is introduced in
-link:SendingEventsFromTheClientToTheServerUsingRPC.asciidoc[Sending
-events from the client to the server using RPC]. `Window` here is
+<<SendingEventsFromTheClientToTheServerUsingRPC#, Sending
+events from the client to the server using RPC>>. `Window` here is
 `com.google.gwt.user.client.Window`, _not_ `com.vaadin.ui.Window`.)
 
 Finally, in *MyComponent* we use the RPC via a proxy:

documentation/articles/UsingServerInitiatedEvents.asciidoc

@@ -132,4 +132,4 @@ by using for instance a `ScheduledExecutorService` instead to make the
 executor service handle the iteration and interval (e.g. `Executors.newScheduledThreadPool(1).scheduleAtFixedRate(...)`).
 
 For more information on how to enable push or polling in your
-application, see link:EnablingServerPush.asciidoc[Enabling server push] or link:UsingPolling.asciidoc[Using polling].
+application, see <<EnablingServerPush#, Enabling server push>> or <<UsingPolling#, Using polling>>.

documentation/articles/VaadinOnGrailsCreateProjectInIntelliJIDEA.asciidoc

@@ -109,5 +109,5 @@ application context, add a new bean, change method signature and other
 image:http://vaadinongrails.com/img/recompile-idea.png[Recompile IDEA]
 
 Now you can continue with
-link:VaadinOnGrailsDatabaseAccess.asciidoc[Vaadin
-on Grails - Database access]
+<<VaadinOnGrailsDatabaseAccess#, Vaadin
+on Grails - Database access>>

documentation/articles/VaadinOnGrailsDatabaseAccess.asciidoc

@@ -10,8 +10,8 @@ layout: page
 _Versions used in this tutorial: Grails 2.3.x, Vaadin 7.1.x. News and
 updates about Vaadin on Grails are available on
 https://twitter.com/VaadinOnGrails[VaadinOnGrails]. This is continuation
-of link:VaadinOnGrailsCreateProjectInIntelliJIDEA.asciidoc[Vaadin
-on Grails - Create project in IntelliJ IDEA]_
+of <<VaadinOnGrailsCreateProjectInIntelliJIDEA#, Vaadin
+on Grails - Create project in IntelliJ IDEA>>_
 
 We are going to create persistence a domain class that is automatically
 mapped into a database through Hibernate. GORM from Grails framework

documentation/articles/VaadinOnGrailsMultipleUIs.asciidoc

@@ -10,7 +10,7 @@ layout: page
 _Versions used in this tutorial: Grails 2.3.x, Vaadin 7.1.x. News and
 updates about Vaadin on Grails are available on
 https://twitter.com/VaadinOnGrails[VaadinOnGrails]. This is continuation
-of link:VaadinOnGrailsDatabaseAccess.asciidoc[Vaadin on Grails - Database access]_
+of <<VaadinOnGrailsDatabaseAccess#, Vaadin on Grails - Database access>>_
 
 In `grails-app/conf/VaadinConfig.groovy`, we can change URL mapping to
 UI. Also, we can define multiple UIs to be accessible from one Grails

documentation/articles/VaadinTutorialForSwingDevelopers.asciidoc

@@ -503,8 +503,7 @@ database using “lazy loading” implementations of the
 https://vaadin.com/api/com/vaadin/data/Container.html[Container API].
 You can pretty easily write a totally custom version for your specific
 use case, but the strongly suggested method is to use helpers like
-https://vaadin.com/web/matti/blog/-/blogs/connecting-large-amounts-of-data-to-ui[LazyList]
-or https://vaadin.com/addon/lazy-query-container[LazyQueryContainer]
+LazyList or https://vaadin.com/addon/lazy-query-container[LazyQueryContainer]
 instead.
 
 [[structuring_your_ui_code]]

documentation/articles/ValoThemeGettingStarted.asciidoc

@@ -9,7 +9,7 @@ layout: page
 
 To create your own variation of the Valo theme, start by creating a new
 custom theme for your project. See
-the link:CreatingAThemeUsingSass.asciidoc[Creating a theme using Sass] 
+the <<CreatingAThemeUsingSass#, Creating a theme using Sass>> 
 tutorial to get that done.
 
 Change your theme import and include from Reindeer to Valo:

documentation/articles/contents.asciidoc

@@ -10,7 +10,7 @@ Helpful articles about Vaadin Framework written by the users for the users. The
 articles are presented as written by the author. Vaadin does not edit or maintain them.
 Pull requests welcome!
 
-NOTE: All contributions are very welcome! Just write your article in link:asciidoctor.org/docs/asciidoc-writers-guide[AsciiDoc],
+NOTE: All contributions are very welcome! Just write your article in link:https://asciidoctor.org/docs/asciidoc-writers-guide[AsciiDoc],
 put it in this directory and send us a pull request. Updates to existing articles
 are great, too.
 

documentation/components/components-overview.asciidoc

@@ -64,13 +64,13 @@ abstract class.
 There are three more specific types of components.
 
 Field Components:: allow user to edit a value in the UI. All extend [classname]#AbstractField#. Field components are described in detail in
-<<dummy/../../../framework/component/components-fields.asciidoc#components.fields,"Field Components">>.
+<<dummy/../../../documentation/components/components-fields#components.fields,"Field Components">>.
 
 Selection Component:: show a list of data that the user can select from. All extend [classname]#AbstractListing#. Selection components are described in detail in
-<<dummy/../../../framework/component/components-selection.asciidoc#components.selection,"Selection Components">>.
+<<dummy/../../../documentation/components/components-selection#components.selection,"Selection Components">>.
 
 Layouts and Component Containers:: Components that can contain other components. All layouts and containers implement the [interfacename]#HasComponents# interface. Layout components are described in detail in
-<<dummy/../../../framework/layout/layout-overview.asciidoc#layout.overview,"Managing
+<<dummy/../../../documentation/layout/layout-overview#layout.overview,"Managing
 Layout">>.
 
 ((("Sampler")))
@@ -83,7 +83,7 @@ In addition to the built-in components, many components are available as
 add-ons, either from the Vaadin Directory or from independent sources. Both
 commercial and free components exist. The installation of add-ons is described
 in
-<<dummy/../../../framework/addons/addons-overview.asciidoc#addons.overview,"Using
+<<dummy/../../../documentation/addons/addons-overview#addons.overview,"Using
 Vaadin Add-ons">>.
 
 ////
@@ -99,4 +99,4 @@ The diagram is also included in the six-page DZone Refcard, which you can find
 at https://vaadin.com/refcard.
 
 ====
-////
+////