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

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

Commit 8b65515f073e6b9de063fda2df775dc8595339c1 in lucene-solr's branch 
refs/heads/master from [~ctargett]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=8b65515 ]

SOLR-11050: remove Confluence-style anchors and fix all incoming links


> Ref Guide: Remove Confluence-style anchor refs & clean up duplicate section 
> titles
> ----------------------------------------------------------------------------------
>
>                 Key: SOLR-11050
>                 URL: https://issues.apache.org/jira/browse/SOLR-11050
>             Project: Solr
>          Issue Type: Task
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: documentation
>            Reporter: Cassandra Targett
>            Assignee: Cassandra Targett
>             Fix For: 7.0
>
>
> To ensure section and page title uniqueness during conversion, we retained 
> Confluence-style anchor references in the new .adoc files, which lead to long 
> links and confusion about how to construct a link to another page/section. It 
> was always the intention to remove these, but we didn't do it during the 
> initial post-conversion cleanup and I neglected to file an issue for it.
> A script for this has been suggested, but that's problematic because many 
> section titles are repeated on different pages (like "Input", etc.), and 
> someone needs to decide how to modify the section titles to ensure clarity 
> and uniqueness at the same time. Otherwise, Ref Guide builds will fail.



--
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

Reply via email to