Hoss Man commented on SOLR-10595:

bq. But that can be mitigated by flashing a warning that a newer version 
exists, and preferably offer a link to corresponding page for that version.

Spun off into LUCENE-7924

bq. Doing a redirect makes it harder to find, say ADDREPLICA for instance. Does 
it make sense to sequence redirects after search works on the new site?

Adding search to the new ref-guide seems like an orthoginal issue to adding 
redirects.  But for the sake of argument, let's assume for now they should be 
considered part and parcel...

To you, today, as an experienced user of cwiki: adding redirects may make it 
harder to find the docs on ADDREPLICA because you have preconcieved impressions 
that going to an existing page on cwiki.apache.org and doing a search in that 
search box will help you find it -- but the docs you find that way are stale 
and out of date.  A new user -- even if you deliberately instilled in them the 
preconcieved knowledge that going to cwiki is the best way to find docs -- may 
get frustrated when they can't find docs on commands/features added *after* the 
ref-guide migration using that same approach (and the likehook of that 
happening will only increase -- never decrease -- as time goes on and more docs 
are added/changed).  In the more general case that a new user does *NOT* 
already have preconcieved knowledge that going to cwiki is the best way to find 
docs, they are most likely to try and find dogs using google/web-search -- in 
which case the (current) lack of redirects means they are in roughly the same 
boat: they are very likely to first find stale / out of date (and growing more 
out of date daily) documentation.

adding cwiki->lucene.apache.org redirects seems like it can only improve the 
situation for most users -- independent of the question of when/how we add new 
(explicit) search functionality for the current hosted ref-guide.


I'll prep some mapping files and file an INFRA link soon.

> 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
>            Assignee: Hoss Man
>         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

To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to