[ 
https://issues.apache.org/jira/browse/SOLR-6520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16890114#comment-16890114
 ] 

ASF subversion and git services commented on SOLR-6520:
-------------------------------------------------------

Commit 369a5dc796e998f11fa5f76b40ade5aad8cff6ea in lucene-solr's branch 
refs/heads/master from Jan Høydahl
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=369a5dc ]

SOLR-6520: Replace old wiki link with versioned RefGuide link in version 
specific release docs


> Documentation web page is missing link to live Solr Reference Guide
> -------------------------------------------------------------------
>
>                 Key: SOLR-6520
>                 URL: https://issues.apache.org/jira/browse/SOLR-6520
>             Project: Solr
>          Issue Type: Improvement
>          Components: documentation
>    Affects Versions: 4.10
>         Environment: web
>            Reporter: Alexandre Rafalovitch
>            Assignee: Alexandre Rafalovitch
>            Priority: Minor
>              Labels: documentation, website
>             Fix For: 8.1, master (9.0)
>
>         Attachments: SOLR-6520.patch
>
>
> The [official document page for 
> Solr|https://lucene.apache.org/solr/documentation.html] is missing the link 
> to the live Solr Reference Guide. Only the link to PDF is there. In fact, one 
> has to go to the WIKI, it seems to find the link. 
> It is also not linked from [the release-specific documentation 
> page|https://lucene.apache.org/solr/4_10_0/index.html] either.
> This means the search engines do not easily discover the new content and it 
> does not show up in searches for when people look for information. It also 
> means people may hesitate to look at it, if they have to download the whole 
> PDF first.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to