You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by di...@apache.org on 2021/12/30 18:42:39 UTC
[sling-org-apache-sling-sitemap] branch master updated: trivial: fix wording in README.md
This is an automated email from the ASF dual-hosted git repository.
diru pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-org-apache-sling-sitemap.git
The following commit(s) were added to refs/heads/master by this push:
new dd13214 trivial: fix wording in README.md
dd13214 is described below
commit dd13214ef2e610fe1e7a044042b3851de33256d4
Author: Dirk Rudolph <di...@apache.org>
AuthorDate: Thu Dec 30 19:42:31 2021 +0100
trivial: fix wording in README.md
---
README.md | 13 +++++++------
1 file changed, 7 insertions(+), 6 deletions(-)
diff --git a/README.md b/README.md
index 06c5f4f..f1f04d4 100644
--- a/README.md
+++ b/README.md
@@ -74,15 +74,16 @@ module must implement an appropriate `SitemapGenerator` that fits their content
`ResourcceTreeSitemapGenator` implementation is available to cover the most common use cases.
Each `SitemapGenerator` may produce multiple sitemaps for a given sitemap root. For example a default sitemap and a news
-specific sitemap, that contains only 1000 urls that were changed in the past 2 days. Or as another example would a
-product sitemap for each of a catalogues top level categories. To enable that, a `SitemapGenerator` can return _0..n_
-names for a given resource, each name representing a single sitemap at the given resource.
+specific sitemap, that contains only up to 1000 urls that were changed in the past 2 days. Or as another example,
+consider an eCommerce site, that generates a product sitemap for each top level category of a catalog. To enable that,
+a `SitemapGenerator` can return _0..n_ names for a given resource, each name representing a single sitemap at the given
+resource.
`SitemapGenerator` implementations need to be registered as OSGI services. In case of an overlap, it depends on
the `service.ranking` which `SitemapGenerators` are used for a particular sitemap root. For example, it may be that two
-`SitemapGenerators` can generator a default sitemap for a sitemap root, but the second one can also generate a news
-sitemap. The first, higher-ranked `SitemapGenerator` will be used for the default sitemap, but the second will still be
-taken into account for the news sitemap.
+`SitemapGenerators` can generate a default sitemap for a sitemap root, but the second one can also generate a news
+sitemap. The first, higher-ranked `SitemapGenerator` will be used for the default sitemap, but the second one will still
+be taken into account for the news sitemap.
#### Background Generation