[ 
https://issues.apache.org/jira/browse/SOLR-10670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Høydahl updated SOLR-10670:
-------------------------------
    Attachment: SOLR-10670.patch

That was a smart move :)

I improved on it somewhat more by adding a conditional <head><title> too in 
head.html, which simplifies the header title of the home page even more:
{code:xml}
{% if page.title == "Home" %}
<title>{{ site.site_title }}</title>
{% else %}
<title>{{ page.title }} | {{ site.site_title }}</title>
{% endif %}
{code}

I built a guide with all these changes which can be previewed at 
http://cominvent.com/solr-refguide/. New patch attached.

But now the text above the left-hand menu is "Home", which I guess is fine if 
it was clickable, but it is not. So then perhaps it should say something else?

> [ref-guide] Various top-bar fixes
> ---------------------------------
>
>                 Key: SOLR-10670
>                 URL: https://issues.apache.org/jira/browse/SOLR-10670
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: documentation
>            Reporter: Jan Høydahl
>              Labels: asciidoc, html
>             Fix For: 6.6
>
>         Attachments: SOLR-10670-home.patch, SOLR-10670.patch, SOLR-10670.patch
>
>
> A few suggestions for the new ref-guide HTML format:
> * Favicon is not displayed, image missing in folder
> * Topnav link to community should point to 
> http://lucene.apache.org/solr/community.html
> * Replace "Solr News" link with a "Solr Website" link - we should link to the 
> website
> * Instead of pointint the Source Code link to cryptic apache GIT, point to 
> https://lucene.apache.org/solr/community.html#version-control where people 
> get more context and can also find the GitHub link



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