svn commit: r1809601 - in /sling/site/trunk/content/documentation/bundles: sling-query.mdtext sling-query/vs-jcr.mdtext

[to...@apache.org]

Author: tomekr
Date: Mon Sep 25 10:38:47 2017
New Revision: 1809601

URL: http://svn.apache.org/viewvc?rev=1809601&view=rev
Log:
SLING-6676: Get more documentation for Sling Query

-fixed links in the main documentation page


Modified:
    sling/site/trunk/content/documentation/bundles/sling-query.mdtext
    sling/site/trunk/content/documentation/bundles/sling-query/vs-jcr.mdtext

Modified: sling/site/trunk/content/documentation/bundles/sling-query.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/bundles/sling-query.mdtext?rev=1809601&r1=1809600&r2=1809601&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/bundles/sling-query.mdtext (original)
+++ sling/site/trunk/content/documentation/bundles/sling-query.mdtext Mon Sep 25 10:38:47 2017
@@ -32,8 +32,8 @@ SlingQuery is inspired by the jQuery fra
 
 ## Features
 
-* useful [operations](https://github.com/Cognifide/Sling-Query/wiki/Method-list) to traverse the resource tree,
-* flexible [filtering syntax](https://github.com/Cognifide/Sling-Query/wiki/Selector-syntax),
+* useful [operations]({{ refs.methods.path }}) to traverse the resource tree,
+* flexible [filtering syntax]({{ refs.selectors.path }}),
 * lazy evaluation of the query result,
 * `SlingQuery` object is immutable (thread-safe),
 * fluent, friendly, jQuery-like API.
@@ -51,15 +51,14 @@ Add following Maven dependency to your `
 ## Documentation
 
 * [CIRCUIT 2014 presentation](http://cognifide.github.io/Sling-Query/circuit2014/)
-* [Basic ideas](https://github.com/Cognifide/Sling-Query/wiki/Basic-ideas)
-* [Method list](https://github.com/Cognifide/Sling-Query/wiki/Method-list)
-* [Selector syntax](https://github.com/Cognifide/Sling-Query/wiki/Selector-syntax)
-	* [Operator list](https://github.com/Cognifide/Sling-Query/wiki/Operator-list)
-	* [Modifier list](https://github.com/Cognifide/Sling-Query/wiki/Modifier-list)
-	* [Hierarchy operator list](https://github.com/Cognifide/Sling-Query/wiki/Hierarchy-operator-list)
-* [Examples](https://github.com/Cognifide/Sling-Query/wiki/Examples)
+* [Basic ideas]({{ refs.basic-ideas.path }})
+* [Method list]({{ refs.methods.path }})
+* [Selector syntax]({{ refs.selectors.path }})
+	* [Operator list]({{ refs.operators.path }})
+	* [Modifier list]({{ refs.modifiers.path }})
+	* [Hierarchy operator list]({{ refs.hierarchy-operators.path }})
+* [Examples]({{ refs.examples.path }})
 
 ## External resources
 
-* See the [Apache Sling website](http://sling.apache.org/) for the Sling reference documentation. Apache Sling, Apache and Sling are trademarks of the [Apache Software Foundation](http://apache.org).
-* Method names, selector syntax and some parts of documentation are inspired by the [jQuery](http://jquery.com/) library.
\ No newline at end of file
+* Method names, selector syntax and some parts of documentation are inspired by the [jQuery](http://jquery.com/) library.

Modified: sling/site/trunk/content/documentation/bundles/sling-query/vs-jcr.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/bundles/sling-query/vs-jcr.mdtext?rev=1809601&r1=1809600&r2=1809601&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/bundles/sling-query/vs-jcr.mdtext (original)
+++ sling/site/trunk/content/documentation/bundles/sling-query/vs-jcr.mdtext Mon Sep 25 10:38:47 2017
@@ -14,4 +14,4 @@ As a rule of thumb - if you have a compl
 | You want to find all descendants of given type        | Yes!      | -          |
 | You'd like to get ordered results                     | Yes!      | -          |
 
-[1] - Actually, the `find()` operation uses QUERY strategy by default, which means that the selector string is transformed to a SQL2 query. However, the transformation process is very naïve and simply skips all conditions that can't be easily transformed to SQL2 (eg. selector `[jcr:content/jcr:title=some title]` won't be transformed as it contains some subresource reference). The result of this query is then filtere manually. See [searchStrategy](Method list#searchstrategystrategy) for more details.
+[1] - Actually, the `find()` operation uses QUERY strategy by default, which means that the selector string is transformed to a SQL2 query. However, the transformation process is very naïve and simply skips all conditions that can't be easily transformed to SQL2 (eg. selector `[jcr:content/jcr:title=some title]` won't be transformed as it contains some subresource reference). The result of this query is then filtere manually. See [searchStrategy](methods.html#searchstrategystrategy) for more details.