http://git-wip-us.apache.org/repos/asf/sling-site/blob/c958e496/content/documentation/the-sling-engine/dispatching-requests.md ---------------------------------------------------------------------- diff --git a/content/documentation/the-sling-engine/dispatching-requests.md b/content/documentation/the-sling-engine/dispatching-requests.md index 8eef6e4..1c0188f 100644 --- a/content/documentation/the-sling-engine/dispatching-requests.md +++ b/content/documentation/the-sling-engine/dispatching-requests.md @@ -33,13 +33,13 @@ The following steps should give you an overview how a request is processed in Sl * Wraps the `HttpServletRequest` and the `HttpServletResponse` into the `SlingHttpServletRequest` and the `SlingHttpServletResponse` * Checks if Sling is ready for processing the request (checks at the moment for an existing ResourceResolverFactory service, a ServletResolver service and a MimeTypeService) * Create the ResourceResolver based on the Session (by default creates a `JcrResourceResolver2`) - * Locate the [Resource]({{ refs.resources.path }}) on the basis of the request by calling `ResourceResovler.resolve` through `RequestData.initResource` (see also [URL decomposition]({{ refs.url-decomposition.path }})) - * Locate the servlet or script (see [Servlets]({{ refs.servlets.path }})) by calling `ServletResolver.resolveServlet` through `RequestData.initServlet` + * Locate the [Resource](/documentation/the-sling-engine/resources.html) on the basis of the request by calling `ResourceResovler.resolve` through `RequestData.initResource` (see also [URL decomposition](/documentation/the-sling-engine/url-decomposition.html)) + * Locate the servlet or script (see [Servlets](/documentation/the-sling-engine/servlets.html)) by calling `ServletResolver.resolveServlet` through `RequestData.initServlet` -1. After this setup, the request level filters are called (the ones registered as `javax.servlet.Filter` with the property `filter.scope=request`, see [Filters]({{ refs.filters.path }}) for details). +1. After this setup, the request level filters are called (the ones registered as `javax.servlet.Filter` with the property `filter.scope=request`, see [Filters](/documentation/the-sling-engine/filters.html) for details). If any called filter doesn't call `FilterChain.doFilter` at the end of the `Filter.doFilter` method request processing stops here. -1. After having called all request level filters, the component level filters (registered with the property `filter.scope=component`, see [Filters]({{ refs.filters.path }}) for details) are called. +1. After having called all request level filters, the component level filters (registered with the property `filter.scope=component`, see [Filters](/documentation/the-sling-engine/filters.html) for details) are called. 1. After having called the component level filters, the request servlet or script is finally called to process the request. @@ -53,7 +53,7 @@ If a servlet or script is including another resource for processing through the 1. The servlet or script to handle the resource is resolved calling the `ServletResolver.resolverServlet` method. -1. The component level filters (registered with the property `filter.scope=component`) are called again (see [Filters]({{ refs.filters.path }}) for details). +1. The component level filters (registered with the property `filter.scope=component`) are called again (see [Filters](/documentation/the-sling-engine/filters.html) for details). 1. The servlet or script is called to process the request.
http://git-wip-us.apache.org/repos/asf/sling-site/blob/c958e496/content/documentation/the-sling-engine/mappings-for-resource-resolution.md ---------------------------------------------------------------------- diff --git a/content/documentation/the-sling-engine/mappings-for-resource-resolution.md b/content/documentation/the-sling-engine/mappings-for-resource-resolution.md index 1f0a04e..789db2f 100644 --- a/content/documentation/the-sling-engine/mappings-for-resource-resolution.md +++ b/content/documentation/the-sling-engine/mappings-for-resource-resolution.md @@ -14,7 +14,7 @@ Title: Mappings for Resource Resolution ### Properties The mapping of request URLs to resources is mainly configured in a configuration tree which is (by default) located below `/etc/map`. The actual location can be configured with the `resource.resolver.map.location` property of the `org.apache.sling.jcr.resource.internal.JcrResourceResolverFactoryImpl` configuration. -That way you can even make it [run mode specific]({{ refs.sling-settings-org-apache-sling-settings.path }}) by having a unique path per [run mode specific OSGi configuration]({{ refs./jcr-installer-provider.path }}). +That way you can even make it [run mode specific](/documentation/bundles/sling-settings-org-apache-sling-settings.html) by having a unique path per [run mode specific OSGi configuration]({{ refs./jcr-installer-provider.path }}). When dealing with the new resource resolution we have a number of properties influencing the process: http://git-wip-us.apache.org/repos/asf/sling-site/blob/c958e496/content/documentation/the-sling-engine/resources.md ---------------------------------------------------------------------- diff --git a/content/documentation/the-sling-engine/resources.md b/content/documentation/the-sling-engine/resources.md index b45a185..99dd73a 100644 --- a/content/documentation/the-sling-engine/resources.md +++ b/content/documentation/the-sling-engine/resources.md @@ -75,7 +75,7 @@ The path mapping functionality may be used to hide internal resource organizatio The `map(String)` applies the path mapping algorithm in the reverse order. That is, first the path mappings are reversed and then any virtual mappings are checked. So, a path `/content/sample` might be mapped `/sample` to revers the `/content` prefixing. Or the main administrative page - say `/system/admin/main.html` \- may be mapped to the virtual URL `/`. -More details on mappings can be found at [Mappings for Resource Resolution]({{ refs.mappings-for-resource-resolution.path }}). +More details on mappings can be found at [Mappings for Resource Resolution](/documentation/the-sling-engine/mappings-for-resource-resolution.html). ### Relative Path Resolution @@ -122,23 +122,23 @@ Resources may by provided by OSGi bundles. Providing bundles have a Bundle manif The `BundleResourceProvider` supporting bundle-based Resources provides directories as Resources of type `nt:folder` and files as Resources of type `nt:file`. This matches the default primary node types intended to be used for directories and files in JCR repositories. -For details see [Bundle Resource.]({{ refs.bundle-resources-extensions-bundleresource.path }}) +For details see [Bundle Resource.](/documentation/bundles/bundle-resources-extensions-bundleresource.html) ### Servlet Resources -Servlet Resources are registered by the Servlet Resolver bundle for Servlets registered as OSGi services. See [Servlet Resolution]({{ refs.servlets.path }}) for information on how Servlet Resources are provided. +Servlet Resources are registered by the Servlet Resolver bundle for Servlets registered as OSGi services. See [Servlet Resolution](/documentation/the-sling-engine/servlets.html) for information on how Servlet Resources are provided. ### File System Resources The Filesystem Resource Provider provides access to the operating system's filesystem through the Sling ResourceResolver. Multiple locations may be mapped into the resource tree by configuring the filesystem location and the resource tree root path for each location to be mapped. -For details see [File System Resources]({{ refs.accessing-filesystem-resources-extensions-fsresource.path }}). +For details see [File System Resources](/documentation/bundles/accessing-filesystem-resources-extensions-fsresource.html). ### Merged Resources The merged resource provider exposes a view on merged resources from multiple locations. -For details see [Resource Merger]({{ refs.resource-merger.path }}). +For details see [Resource Merger](/documentation/bundles/resource-merger.html). ### Custom Resource providers Custom ResourceProvider services can be used to integrate your own custom resources in the Sling resource tree. @@ -151,7 +151,7 @@ Sling now supports full CRUD functionality on Resources, without necessarily hav The advantage is that this works for any ResourceProvider that supports the required operations. See the testSimpleCRUD method in [WriteableResourcesTest][5] for a basic example of how that works. -More details can be found at [Sling API CRUD Support]({{ refs.sling-api-crud-support.path }}). +More details can be found at [Sling API CRUD Support](/documentation/the-sling-engine/sling-api-crud-support.html). ## Resource Observation @@ -169,7 +169,7 @@ Resource events are sent out via the OSGi Event Admin. You can subscribe to thos ## Wrap/Decorate Resources -The Sling API provides an easy way to wrap or decorate a resource before returning. Details see [Wrap or Decorate Resources]({{ refs.wrap-or-decorate-resources.path }}). +The Sling API provides an easy way to wrap or decorate a resource before returning. Details see [Wrap or Decorate Resources](/documentation/the-sling-engine/wrap-or-decorate-resources.html). [1]: http://sling.apache.org/apidocs/sling8/org/apache/sling/api/resource/ResourceMetadata.html "ResourceMetadata" http://git-wip-us.apache.org/repos/asf/sling-site/blob/c958e496/content/documentation/the-sling-engine/service-authentication.md ---------------------------------------------------------------------- diff --git a/content/documentation/the-sling-engine/service-authentication.md b/content/documentation/the-sling-engine/service-authentication.md index a699cf4..b34e221 100644 --- a/content/documentation/the-sling-engine/service-authentication.md +++ b/content/documentation/the-sling-engine/service-authentication.md @@ -15,7 +15,7 @@ To access the data storage in the Resource Tree and/or the JCR Repository authentication is required to properly setup access control and guard sensitive data from unauthorized access. For regular request processing this authentication step is handled by the Sling -[{{ refs.authentication.headers.title }}]({{ refs.authentication.path }}) +[{{ refs.authentication.headers.title }}](/documentation/the-sling-engine/authentication.html) subsystem. On the other hand there are also some background tasks to be executed http://git-wip-us.apache.org/repos/asf/sling-site/blob/c958e496/content/documentation/the-sling-engine/servlets.md ---------------------------------------------------------------------- diff --git a/content/documentation/the-sling-engine/servlets.md b/content/documentation/the-sling-engine/servlets.md index d996b34..ca21533 100644 --- a/content/documentation/the-sling-engine/servlets.md +++ b/content/documentation/the-sling-engine/servlets.md @@ -8,7 +8,7 @@ Title: Servlets and Scripts [TOC] -See also [URL to Script Resolution]({{ refs.url-to-script-resolution.path }}) which explains how Sling maps URLs +See also [URL to Script Resolution](/documentation/the-sling-engine/url-to-script-resolution.html) which explains how Sling maps URLs to a script or and servlet. ## Servlet Registration @@ -193,4 +193,4 @@ While an opting servlet seems to be a nice way of picking the right servlet to p ## Error Handler Servlet(s) or Scripts -Error handling support is described on the [Errorhandling]({{ refs.errorhandling.path }}) page. +Error handling support is described on the [Errorhandling](/documentation/the-sling-engine/errorhandling.html) page. http://git-wip-us.apache.org/repos/asf/sling-site/blob/c958e496/content/documentation/the-sling-engine/the-sling-launchpad.md ---------------------------------------------------------------------- diff --git a/content/documentation/the-sling-engine/the-sling-launchpad.md b/content/documentation/the-sling-engine/the-sling-launchpad.md index 5f7f5ad..77066a6 100644 --- a/content/documentation/the-sling-engine/the-sling-launchpad.md +++ b/content/documentation/the-sling-engine/the-sling-launchpad.md @@ -8,7 +8,7 @@ Title: The Sling Launchpad [TOC] -This tries to explain how exactly the Sling Launchpad works, what constitutes the Sling Launchpad and how you can use the Sling Launchpad to custom create you Sling launchers. For a view behind the scenes of the Sling Launchpad Base module (the actual launcher) you might want to refer to the [Embedding Sling]({{ refs.embedding-sling.path }}) page. +This tries to explain how exactly the Sling Launchpad works, what constitutes the Sling Launchpad and how you can use the Sling Launchpad to custom create you Sling launchers. For a view behind the scenes of the Sling Launchpad Base module (the actual launcher) you might want to refer to the [Embedding Sling](/documentation/development/embedding-sling.html) page. ## Sling Home @@ -182,7 +182,7 @@ The *Launchpad App* and *Launchpad WebApp* bundles are actually projects which j * Take the appropriate secondary artifact from the *Launchpad Base* project: *app* for the Standalone Java Application or *webapp* for the Web Application and unpack * Take the *Launchpad Base* primary artifact and place it under the name `org.apache.sling.launchpad.base.jar` into the `resources` folder -* Copies the list of artifacts defined in the [Provisioning model]({{refs.slingstart.path}}) +* Copies the list of artifacts defined in the [Provisioning model](/documentation/development/slingstart.html) * Finally pack all together into a single big JAR or WAR file The artifacts can be configured to use different JCR repository implementations, based on the value of the `-Dsling.run.modes` property. The following run modes are available for the 8 version of the Sling Launchpad: http://git-wip-us.apache.org/repos/asf/sling-site/blob/c958e496/content/documentation/the-sling-engine/url-decomposition.md ---------------------------------------------------------------------- diff --git a/content/documentation/the-sling-engine/url-decomposition.md b/content/documentation/the-sling-engine/url-decomposition.md index 186f4e7..35b8114 100644 --- a/content/documentation/the-sling-engine/url-decomposition.md +++ b/content/documentation/the-sling-engine/url-decomposition.md @@ -11,7 +11,7 @@ Title: URL decomposition # Overview # During the *Resource Resolution* step, the client request URI (as being returned by [HttpServletRequest.getRequestURI()](http://docs.oracle.com/javaee/6/api/javax/servlet/http/HttpServletRequest.html#getRequestURI())) is decomposed into the following parts (in exactly this order): -1. **Resource Path** - For existing resources the resource path is the longest match (also considering its [mappings]({{ refs.mappings-for-resource-resolution.path }})) pointing to a resource where the next character is either a dot (`.`) or it is the full request URI. +1. **Resource Path** - For existing resources the resource path is the longest match (also considering its [mappings](/documentation/the-sling-engine/mappings-for-resource-resolution.html)) pointing to a resource where the next character is either a dot (`.`) or it is the full request URI. Otherwise (for a path not matching any existing resource) the resource path ends at the *first dot (`.`)* in the request url. The exact logic for retrieving the resource path is implemented at [ResourceResolver.resolve(HttpServletRequest,String)](https://sling.apache.org/apidocs/sling7/org/apache/sling/api/resource/ResourceResolver.html#resolve-javax.servlet.http.HttpServletRequest-java.lang.String-). *It is impossible to tell from just looking at the request URI where the resource path part ends. You have to know the underlying resource structure to know how a URL is decomposed. You cannot safely assume that the resource path will always end at the first dot!*. 1. **Selectors** - If the first character in the request URL after the resource path is a dot (`.`), the string after the dot up to but not including the last dot before the next slash character or the end of the request URL comprises the selectors. If the resource path spans the complete request URL no selectors exist. If only one dot follows the resource path before the end of the request URL or the next slash, also no selectors exist. 1. **Extension** - The string after the last dot after the resource path in the request URL but before the end of the request URL or the next slash after the resource path in the request URL is the extension. http://git-wip-us.apache.org/repos/asf/sling-site/blob/c958e496/content/documentation/the-sling-engine/url-to-script-resolution.md ---------------------------------------------------------------------- diff --git a/content/documentation/the-sling-engine/url-to-script-resolution.md b/content/documentation/the-sling-engine/url-to-script-resolution.md index 846cd5b..de929bb 100644 --- a/content/documentation/the-sling-engine/url-to-script-resolution.md +++ b/content/documentation/the-sling-engine/url-to-script-resolution.md @@ -10,11 +10,11 @@ Title: URL to Script Resolution This page explains how Sling maps URLs to a script or and servlet. -See also [Servlets and Scripts]({{ refs.servlets.path }}) which provides detailed info about how to register servlets. +See also [Servlets and Scripts](/documentation/the-sling-engine/servlets.html) which provides detailed info about how to register servlets. First of all Sling looks up the resource identified by the URL - typically a path inside the JCR repository, which is annotated by the `sling:resourceType` property which defines the resource type of that resource. Using this resource type (which is kind of a relative path, -eg. "myblog/comment"), scripts or servlets are looked up. For more details about how the initial resource is identified for a specific request URL look at [URL decomposition]({{refs.url-decomposition.path}}). +eg. "myblog/comment"), scripts or servlets are looked up. For more details about how the initial resource is identified for a specific request URL look at [URL decomposition](/documentation/the-sling-engine/url-decomposition.html). Scripts and servlets are itself resources in Sling and thus have a resource path: this is either the location in the JCR repository, the resource type in a servlet component configuration or the "virtual" bundle resource path http://git-wip-us.apache.org/repos/asf/sling-site/blob/c958e496/content/documentation/tutorials-how-tos/46-line-blog.md ---------------------------------------------------------------------- diff --git a/content/documentation/tutorials-how-tos/46-line-blog.md b/content/documentation/tutorials-how-tos/46-line-blog.md index fea988f..3da7a7d 100644 --- a/content/documentation/tutorials-how-tos/46-line-blog.md +++ b/content/documentation/tutorials-how-tos/46-line-blog.md @@ -14,11 +14,11 @@ I used this example in my [Rapid JCR application development with Apache Sling]( ## Audience -Although this is a simple sample, it requires some custom settings to work. If you're just starting with Sling, [Discover Sling in 15 minutes]({{ refs.discover-sling-in-15-minutes.path }}) might be a better choice. +Although this is a simple sample, it requires some custom settings to work. If you're just starting with Sling, [Discover Sling in 15 minutes](/documentation/getting-started/discover-sling-in-15-minutes.html) might be a better choice. ## Step 0: Start, configure and login to Sling -See [Getting and Building Sling]({{ refs.getting-and-building-sling.path }}) for how to start Sling. Start it on port 8888 for the below links to work. +See [Getting and Building Sling](/documentation/development/getting-and-building-sling.html) for how to start Sling. Start it on port 8888 for the below links to work. For this sample we need the optional *org.apache.sling.samples.path-based.rtp* bundle, if it's not present in the [OSGi console](http://localhost:8888/system/console/bundles), install and start it. That bundle is not released yet so you might need to build it yourself, from its [source](http://svn.apache.org/repos/asf/sling/trunk/samples/path-based-rtp). The bundle must then appear in the [OSGI console's list of bundles](http://localhost:8888/system/console/bundles), with name = *org.apache.sling.samples.path-based.rtp* and status = *Active*. @@ -157,7 +157,7 @@ To keep things simple, we'll refrain from adding ESP-based features at this poin ## That's the power of Sling -The 46-line blog is a good example of the power of Sling. It leverages the [SlingPostServlet]({{ refs.manipulating-content-the-slingpostservlet-servlets-post.path }}), which handles POST requests in a form-friendly way, and the [`sling.js`](http://svn.apache.org/repos/asf/sling/trunk/bundles/servlets/post/src/main/resources/system/sling.js) client library, which provides high-level functionality on the client side. +The 46-line blog is a good example of the power of Sling. It leverages the [SlingPostServlet](/documentation/bundles/manipulating-content-the-slingpostservlet-servlets-post.html), which handles POST requests in a form-friendly way, and the [`sling.js`](http://svn.apache.org/repos/asf/sling/trunk/bundles/servlets/post/src/main/resources/system/sling.js) client library, which provides high-level functionality on the client side. ///Footnotes Go Here/// http://git-wip-us.apache.org/repos/asf/sling-site/blob/c958e496/content/documentation/tutorials-how-tos/getting-resources-and-properties-in-sling.md ---------------------------------------------------------------------- diff --git a/content/documentation/tutorials-how-tos/getting-resources-and-properties-in-sling.md b/content/documentation/tutorials-how-tos/getting-resources-and-properties-in-sling.md index 8369b3c..750a443 100644 --- a/content/documentation/tutorials-how-tos/getting-resources-and-properties-in-sling.md +++ b/content/documentation/tutorials-how-tos/getting-resources-and-properties-in-sling.md @@ -98,4 +98,4 @@ Then, to access a specific String property called `propName`: String rule = properties.get(propName, (String) null); -For more details about resources and how to access them in Sling, you can refer to the [Sling documentation about Resources]({{ refs.resources.path }}). +For more details about resources and how to access them in Sling, you can refer to the [Sling documentation about Resources](/documentation/the-sling-engine/resources.html). http://git-wip-us.apache.org/repos/asf/sling-site/blob/c958e496/content/documentation/tutorials-how-tos/testing-sling-based-applications.md ---------------------------------------------------------------------- diff --git a/content/documentation/tutorials-how-tos/testing-sling-based-applications.md b/content/documentation/tutorials-how-tos/testing-sling-based-applications.md index 9367327..1e3c992 100644 --- a/content/documentation/tutorials-how-tos/testing-sling-based-applications.md +++ b/content/documentation/tutorials-how-tos/testing-sling-based-applications.md @@ -30,7 +30,7 @@ Note that our utilities do not cleanup the repository between tests, so you must The next step is to use mock classes and services to simulate components that are needed for testing. This makes it possible to test OSGi service classes without an OSGi framework, or classes accessing the Sling or JCR API without a running Sling instance or JCR repository. -The [Development]({{ refs.development.path }}) documentation page contains a section "Testing Sling-based Applications" lising all mock implementations available as part of the Apache Sling project. +The [Development](/documentation/development.html) documentation page contains a section "Testing Sling-based Applications" lising all mock implementations available as part of the Apache Sling project. In other cases we use [jmock](http://www.jmock.org/) or [Mockito][1] to help create mock objects without having to write much code - such mocking libraries take care of the plumbing and allow you to write just the bits of code that matter (often with funny syntaxes). The tests of the [org.apache.sling.event](https://svn.apache.org/repos/asf/sling/trunk/bundles/extensions/event/) bundle, for example, make extensive use of such mock services. @@ -62,7 +62,7 @@ Such tests are obviously slower than plain unit tests and tests that use mocks. ## Server-side JUnit tests -The tools described on the [JUnit server-side testing support]({{ refs.org-apache-sling-junit-bundles.path }}) page allow for +The tools described on the [JUnit server-side testing support](/documentation/bundles/org-apache-sling-junit-bundles.html) page allow for running JUnit tests on an live Sling instance, as part of the normal integration testing cycle. ## HTTP-based integration tests http://git-wip-us.apache.org/repos/asf/sling-site/blob/c958e496/content/guides.md ---------------------------------------------------------------------- diff --git a/content/guides.md b/content/guides.md index 92f29d9..bcae798 100644 --- a/content/guides.md +++ b/content/guides.md @@ -9,18 +9,18 @@ Title: Guides These pages contain further information in a more informal way. - * [Discover Sling in 15 minutes ]({{ refs.discover-sling-in-15-minutes.path }}) - title says it all + * [Discover Sling in 15 minutes ](/documentation/getting-started/discover-sling-in-15-minutes.html) - title says it all - * [Resources]({{ refs.resources.path }}) -- Presents the Resource as the object around which Sling is built + * [Resources](/documentation/the-sling-engine/resources.html) -- Presents the Resource as the object around which Sling is built * [Servlet Resolution]({{ refs.servlet-resolution.path }}) -- How Sling resolves the servlet or script responsible for rendering a Resource. - * [Request Parameters]({{ refs.request-parameters.path }}) -- Explains how Sling provides request parameters to servlets, scripts and filters. - * [Repository Based Development]({{ refs.repository-based-development.path }}) -- Shows how WebDAV is supported by Sling. + * [Request Parameters](/documentation/the-sling-engine/request-parameters.html) -- Explains how Sling provides request parameters to servlets, scripts and filters. + * [Repository Based Development](/documentation/development/repository-based-development.html) -- Shows how WebDAV is supported by Sling. - * [Bundle Management]({{ refs.installing-and-upgrading-bundles.path }}) -- Explains how to install, upgrade and uninstall Bundles using the Sling Management console. + * [Bundle Management](/documentation/tutorials-how-tos/installing-and-upgrading-bundles.html) -- Explains how to install, upgrade and uninstall Bundles using the Sling Management console. These pages refer to the old Component API and launcher, and remain referred to here until more up to date documentation has been prepared: - * [Getting and Building Sling]({{ refs.getting-and-building-sling.path }}) -- A short recount on the first step for getting a running Sling instance after checking out the source from the SVN repository - * [Default Mapping and Rendering]({{ refs.default-mapping-and-rendering.path }}) -- Explains default mapping of repository nodes to Content instances and selection of a default Component. - * [Dispatching Requests]({{ refs.dispatching-requests.path }}) -- Explains how a Component may dispatch requests to include further content renderings in the response to the client's request + * [Getting and Building Sling](/documentation/development/getting-and-building-sling.html) -- A short recount on the first step for getting a running Sling instance after checking out the source from the SVN repository + * [Default Mapping and Rendering](/documentation/the-sling-engine/default-mapping-and-rendering.html) -- Explains default mapping of repository nodes to Content instances and selection of a default Component. + * [Dispatching Requests](/documentation/the-sling-engine/dispatching-requests.html) -- Explains how a Component may dispatch requests to include further content renderings in the response to the client's request http://git-wip-us.apache.org/repos/asf/sling-site/blob/c958e496/content/index.md ---------------------------------------------------------------------- diff --git a/content/index.md b/content/index.md index 26b7bd0..dfbbc5c 100644 --- a/content/index.md +++ b/content/index.md @@ -9,7 +9,7 @@ Title: Apache Sling - Bringing Back the Fun! **Apache Sling™** is an innovative web framework that is intended to bring back the fun to web development. -Discussions about Sling happen on our mailing lists, see the [Project Information]({{refs.project-information.path}}) +Discussions about Sling happen on our mailing lists, see the [Project Information](/project-information.html) page for more info. # Apache Sling in five bullets points @@ -44,7 +44,7 @@ complex applications. </ul> -Refer to the news [archive]({{ refs.news.path }}) for all news. +Refer to the news [archive](/news.html) for all news. ## History @@ -63,8 +63,8 @@ this: ## Getting started -If you prefer doing rather than reading, please proceed to [Discover Sling in 15 minutes]({{refs.discover-sling-in-15-minutes.path}}) - or read through the recommended links in the [Getting Started]({{refs.getting-started.path}}) +If you prefer doing rather than reading, please proceed to [Discover Sling in 15 minutes](/documentation/getting-started/discover-sling-in-15-minutes.html) + or read through the recommended links in the [Getting Started](/documentation/getting-started.html) section, where you can quickly get started on your own instance of Sling. ## Use Cases for Sling http://git-wip-us.apache.org/repos/asf/sling-site/blob/c958e496/content/news.md ---------------------------------------------------------------------- diff --git a/content/news.md b/content/news.md index dce7c01..d5161ab 100644 --- a/content/news.md +++ b/content/news.md @@ -6,7 +6,7 @@ status=published ~~~~~~ Title: News -* New Releases: [Apache Sling 9]({{refs.sling-launchpad-9-released.path}}), Apache Sling Launchpad Testing 9, Apache Sling Launchpad Testing WAR version 9, Apache Sling Launchpad Testing Fragment Bundle 2.0.12, Apache Sling Launchpad Testing Services 2.0.12, Apache Sling Launchpad Test Bundles 0.0.2, Apache Sling Launchpad Testing Services WAR 2.0.12, Apache Sling Integration Tests 1.0.4 ( June 12S , 2017 ) +* New Releases: [Apache Sling 9](/news/sling-launchpad-9-released.html), Apache Sling Launchpad Testing 9, Apache Sling Launchpad Testing WAR version 9, Apache Sling Launchpad Testing Fragment Bundle 2.0.12, Apache Sling Launchpad Testing Services 2.0.12, Apache Sling Launchpad Test Bundles 0.0.2, Apache Sling Launchpad Testing Services WAR 2.0.12, Apache Sling Integration Tests 1.0.4 ( June 12S , 2017 ) * New Releases: Apache Sling JUnit Core 1.0.26, Testing Clients 1.1.0, JUnit Remote Test Runners 1.0.12, Tooling Support Install 1.0.4, and Tooling Support Source 1.0.4 (June 6th, 2017) * New Releases: Apache Sling Resource Inventory 1.0.8, Content Distribution Core 0.2.8, Testing Sling Mock 2.2.12, Log Tracer 1.0.4, and Commons Metrics 1.2.2 (June 6th, 2017) * New Releases: Apache Sling JCR Content Parser 1.2.2, JCR ContentLoader 2.2.4, File System Resource Provider 2.1.4, File System Resource Provider 1.4.4, Maven Sling Plugin 2.3.0 (June 2nd, 2017) @@ -156,7 +156,7 @@ Title: News * New Release: Apache Sling Discovery Commons 1.0.12 (March 29th, 2016) * New Release: Apache Sling Scripting Sightly Engine 1.0.18 (March 18th, 2016) * New Release: Apache Maven Sling Plugin 2.1.8 (March 16th, 2016) -* New Release: [Apache Sling IDE Tooling for Eclipse 1.1.0]({{refs.sling-ide-tooling-11-released.path}}) (March 14th, 2016) +* New Release: [Apache Sling IDE Tooling for Eclipse 1.1.0](/news/sling-ide-tooling-11-released.html) (March 14th, 2016) * New Releases: Apache Sling Resource Resolver 1.4.8, Apache Sling JCR Resource 2.7.4, and Apache Sling Installer Core 3.6.8 (March 11th, 2016) * New Releases: Apache Sling Health Check Core 1.2.4, Apache Sling Health Checks Annotations 1.0.4, Apache Sling JCR Davex 1.3.2, and Apache Sling JCR Webdav 2.3.4 (March 8th, 2016) * New Release: Apache Sling Scripting Sightly Engine 1.0.16 (March 5th, 2016) @@ -205,7 +205,7 @@ Title: News * New Releases: Apache Sling Launchpad Base 2.6.6, Apache Sling Event 3.7.6, Apache Sling Provisioning Model 1.4.0, and Apache Sling Maven Launchpad Plugin 2.3.4 (October 26th, 2015) * New Releases: Apache Sling Archetype Parent version 4, Apache Sling Bundle Archetype version 1.0.4, Apache Sling JCRInstall Bundle Archetype 1.0.4, Apache Sling Initial Content Archetype 1.0.4, Apache Sling Servlet Archetype 1.0.4, Apache Sling Slingstart Archetype 1.0.0 (October 19th, 2015) * New Release: Apache Sling Auth Core 1.3.12 (October 18th, 2015) -* New Release: [Apache Sling 8]({{refs.sling-launchpad-8-released.path}}) (October 16th, 2015) +* New Release: [Apache Sling 8](/news/sling-launchpad-8-released.html) (October 16th, 2015) * New Release: Apache Sling Maven Plugin for Supporting Bundle Development 2.1.2 (October 15th, 2015) * New Release: Apache Sling Auth Forms 1.0.8 (October 13, 2015) * New Releases: Apache Sling Scripting Sightly Engine 1.0.6, Apache Sling Scripting Sightly Models Use Provider 1.0.0, Apache Sling Scripting Sightly REPL 1.0.2, Apache Sling Scripting JavaScript 2.0.26, Apache Sling XSS Protection API 1.0.6 (October 12th, 2015) http://git-wip-us.apache.org/repos/asf/sling-site/blob/c958e496/content/news/sling-launchpad-9-released.md ---------------------------------------------------------------------- diff --git a/content/news/sling-launchpad-9-released.md b/content/news/sling-launchpad-9-released.md index e645f0b..212dbe1 100644 --- a/content/news/sling-launchpad-9-released.md +++ b/content/news/sling-launchpad-9-released.md @@ -46,9 +46,9 @@ New modules added: Validation, Context-Aware Configuration, Repository Initializ A number of new general-purpose modules have been added to the Sling Launchpad: -* [Validation]({{refs.validation.path}}) -* [Context-Aware configuration]({{refs.context-aware-configuration.path}}) -* [Repository Initialization Language]({{refs.repository-initialization.path}}) +* [Validation](/documentation/bundles/validation.html) +* [Context-Aware configuration](/documentation/bundles/context-aware-configuration/context-aware-configuration.html) +* [Repository Initialization Language](/documentation/bundles/repository-initialization.html) Tooling: HTL Maven Plugin --- @@ -78,7 +78,7 @@ administrative access to the repository via `loginAdministrative`. We have remov of `loginAdministrative` in the Sling code and replaced then with a service-based approach - `loginService`. We encourage you to do the same. -Documentation available at [Service Authentication]({{refs.service-authentication.path}}). +Documentation available at [Service Authentication](/documentation/the-sling-engine/service-authentication.html). Removed org.apache.sling.commons.json and org.json bundles --- http://git-wip-us.apache.org/repos/asf/sling-site/blob/c958e496/content/project-information.md ---------------------------------------------------------------------- diff --git a/content/project-information.md b/content/project-information.md index 90c6bcd..cb117d9 100644 --- a/content/project-information.md +++ b/content/project-information.md @@ -8,13 +8,13 @@ Title: Project Information This document provides an overview of the various documents and links that are part of this project's general information: -* [Community Roles and Processes]({{ refs.apache-sling-community-roles-and-processes.path }}) -* [Project Team]({{ refs.project-team.path }}) +* [Community Roles and Processes](/project-information/apache-sling-community-roles-and-processes.html) +* [Project Team](/project-information/project-team.html) * [Mailing Lists](#mailing-lists) * [Issue Tracking](#issue-tracking) * [Source Repository](#source-repository) * [Continuous Integration](#continuous-integration) -* [Project License]({{ refs.project-license.path }}) +* [Project License](/project-information/project-license.html) * [Documentation Repository](#documentation-repository) http://git-wip-us.apache.org/repos/asf/sling-site/blob/c958e496/content/project-information/project-team.md ---------------------------------------------------------------------- diff --git a/content/project-information/project-team.md b/content/project-information/project-team.md index 15f091a..ac66585 100644 --- a/content/project-information/project-team.md +++ b/content/project-information/project-team.md @@ -68,7 +68,7 @@ The following list of former committers and PMC members have chosen to go emerit | farra | **J Aaron Farr** | | Mentor | | jukka | **Jukka Zitting** | Adobe | Champion, Mentor | -Committers with their names printed in bold face have also been members of the PMC (or PPMC during Sling incubation) as defined in [Apache Sling Community Roles and Processes]({{ refs.apache-sling-community-roles-and-processes.path }}) +Committers with their names printed in bold face have also been members of the PMC (or PPMC during Sling incubation) as defined in [Apache Sling Community Roles and Processes](/project-information/apache-sling-community-roles-and-processes.html) ## Emeritus PMC members http://git-wip-us.apache.org/repos/asf/sling-site/blob/c958e496/content/project-information/security.md ---------------------------------------------------------------------- diff --git a/content/project-information/security.md b/content/project-information/security.md index 73b8f49..7a79e32 100644 --- a/content/project-information/security.md +++ b/content/project-information/security.md @@ -23,7 +23,7 @@ Questions about: * obtaining further information on a published vulnerability * availability of patches and/or new releases -should be addressed to our public users mailing list. Please see the [Project Information]({{ refs.project-information.path }}) page for details of how to subscribe. +should be addressed to our public users mailing list. Please see the [Project Information](/project-information.html) page for details of how to subscribe. The private security mailing address is: security(at)sling.apache.org.
