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

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

Commit 8a138908c58593e2c7d3221d4f8624693afe2f5c in lucene-solr's branch 
refs/heads/master from Chris Hostetter
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=8a13890 ]

SOLR-11540: eliminate the need for explicitly definied page-shortname and/or 
page-permalink attributes in our asciidoc source files


> eliminate the need for page-shortname and/or page-permalink attributes in our 
> asciidoc source files
> ---------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-11540
>                 URL: https://issues.apache.org/jira/browse/SOLR-11540
>             Project: Solr
>          Issue Type: Sub-task
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: documentation
>            Reporter: Hoss Man
>            Assignee: Hoss Man
>         Attachments: SOLR-11540.patch
>
>
> From parent issue...
> bq. Furthermore: the entire {{page-shortname}} and {{page-permalink}} 
> variables in all of our {{*.adoc}} files arn't really neccessary – they are a 
> convention I introduced early on in the process of building our the sidebar & 
> next/pre link generation logic, but are error prone if/when people rename 
> files.
> Assuming SOLR-11539 works out, we can implicitly (in BuildNavAndPDFBody and 
> our jekyll templates) use the basename of the {{file.adoc}} as the 
> {{shortname}}, and use {{shortname + ".html"}} as the {{permalink}} and be 
> done with it.
> If SOLR-11539 doesn't work out, we can still generate those variables in the 
> same way -- but we also have to validate that the generated values match the 
> title (see existing patch in parent issue)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

Reply via email to