Hi David, On Thu, May 3, 2018 at 10:11 AM, David Bosschaert <[email protected]> wrote: > ...I'm not sure I like the idea of renaming sling-org-apache-sling-feature to > sling-org-apache-sling-feature-docs as that repository also contains the > API classes, so it's not just a docs repo....
Ah ok, sorry I missed that. > ...I wasn't aware of the http://sling.apache.org/repolist.html page, but it > seems that the sling-org-apache-sling-feature is simply missing from that > page. Do you know how I could add it? It *is* currently already listed in > the default.xml of the aggregator... Yeah, it's missing there due to the rules used to extract the group name in the website template script that Radu pointed to, [1] If that repository name was sling-org-apache-sling-feature-api for example it would be in the feature group - but that's no big deal. My point was that IMO all "feature" repositories should point to the permanent URL that has the general documentation for the feature model - so maybe just add a link from all "feature" READMEs to https://github.com/apache/sling-org-apache-sling-feature if that's where you intend those docs to be, or to a new page under http://sling.apache.org/documentation/bundles.html which can act as the entry point. Hope this clarifies what I mean ;-) -Bertrand [1] https://github.com/apache/sling-aggregator/blob/master/collect-sling-repos.groovy
