[ https://issues.apache.org/jira/browse/SOLR-10595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16082879#comment-16082879 ]
Jan Høydahl commented on SOLR-10595: ------------------------------------ Note the rest of my sentence that you quoted from: "...which do not redirect to a particular version but stays on that URL" If we redirect confluence to this redirect that in turn redirects to 6_6 then the PageRank of a page will not be permanently transferred to a stable URL in the new guide but to a moving target.. > Redirect Confluence pages to new HTML Guide > ------------------------------------------- > > Key: SOLR-10595 > URL: https://issues.apache.org/jira/browse/SOLR-10595 > Project: Solr > Issue Type: Sub-task > Security Level: Public(Default Security Level. Issues are Public) > Components: documentation > Reporter: Cassandra Targett > Attachments: new-page-urls.txt, page-tree.xml > > > Once the new Ref Guide is live, we may want to redirect pages from Confluence > to the new HTML version. > I'm undecided if this is the best idea, I can see pros and cons to it. On the > pro side, I think it helps firmly establish the move away from Confluence and > helps users adjust to the new location. But I could see the argument that > redirecting is overly invasive or unnecessary and we should just add a big > warning to the page instead. > At any rate, if we do decide to do it, I found some Javascript we could tell > Confluence to add to the HEAD of each page to auto-redirect. With some > probably simple modifications to it, we could get people to the right page in > the HTML site: > https://community.atlassian.com/t5/Confluence-questions/How-to-apply-redirection-on-all-pages-on-a-space/qaq-p/229949 > -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org