Github user joeymcallister commented on the issue:
https://github.com/apache/geode-site/pull/2
@metatype Thanks for looking at the Travis issue.
I get what you're saying with the second RewriteRule, but my concern is
that it also would impact directories that shouldn't be impacted, like `11`,
`10`, and soon `12`. In other words, it would redirect `/guide/11/` to
`/guide/11/11/`.
I spent the past couple of weeks submitting to Google's My Removal Requests
page every search result pointing to `/docs/guide/...`. There may be a few
stragglers, but Google should zap them when it eventually re-crawls the Geode
site. Not creating a redirect to the files at `guide/` might cause some
short-term strife with broken links from, for instance, the wiki, but I think
the impact will be minimal and may be remedied by fixing the broken links to
point to the new `guide/latest/` locations.
I _could_ create redirects for each of the files and directories within
`guide` that we want redirected to `latest`, but that seems more like a bandage
that eventually would need to be removed anyway.
What do you think?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
