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

Hoss Man commented on SOLR-10655:
---------------------------------

NOTE: I've added {{// TODO: SOLR-10655 ...}} comments around all of the areas 
that were {{excerpt}} or {{excerpt-include}} in cwiki.

Also: one potentially problematic aspect is that 
{{using-the-solr-administration-user-interface}} was using {{excerpt-include}} 
inside of a list element to create a "sub list" ... i have no idea if 
attempting to do the same thing with asciidoc includes will work, or if we'll 
want to rethink that page structure slightly.

> refactor duplicate ref guide content into "snippet" files that can be included
> ------------------------------------------------------------------------------
>
>                 Key: SOLR-10655
>                 URL: https://issues.apache.org/jira/browse/SOLR-10655
>             Project: Solr
>          Issue Type: Sub-task
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: documentation
>            Reporter: Hoss Man
>
> in cwiki, we were using the "excerpt" and "excerpt-include" macros to mirror 
> some content across multiple pages.
> as part of the cwiki->adoc migration, these macros were just evaluated 
> durring export, and the content is now duplicated.
> moving forward, we should refactor this duplicated content into "snippet" 
> files that can be included in multiple places.  A few things we need to be 
> careful about when doing this:
> * ensuring anchors and relative links are generated in such a way that they 
> are still unique per-section
> * that some convention / page attributes are used such that the 
> BuildNavAndPDFBody code doesn't try to include them as "real" pages (or 
> errors that they have no parent)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

Reply via email to