[
https://issues.apache.org/jira/browse/LUCENE-8987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17037878#comment-17037878
]
Uwe Schindler commented on LUCENE-8987:
---------------------------------------
[~janhoy]: I found a very hackish way to fix this problem. I am delaying the
link generation to the templating phase. The trick was to just add a
placeholder in the content HTML and then in the template do a string replace of
the content. Not sure if this is the best idea, but anybody who telle me a
better way: Come up!
{noformat}
content/pages/solr/resources.md | 2 +-
themes/lucene/templates/solr/resources.html | 4 ++++
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/content/pages/solr/resources.md b/content/pages/solr/resources.md
index f2e9b89e2..1685ade99 100644
--- a/content/pages/solr/resources.md
+++ b/content/pages/solr/resources.md
@@ -49,7 +49,7 @@ Beginning with Solr 4.4, a detailed reference guide is
available online.
Solr generates JavaDocs for all included code in each release.
Copies of this documentation for every release can be found online:
-* [Latest Release](/solr/{{ LUCENE_LATEST_RELEASE | replace(".", "_")
}}/index.html)
+* [Latest Release](__DOCSLINK__)
<h3 class="offset" id="additional-documentation">Additional Documentation</h3>
diff --git a/themes/lucene/templates/solr/resources.html
b/themes/lucene/templates/solr/resources.html
index aef2de26a..5e9f5fca3 100644
--- a/themes/lucene/templates/solr/resources.html
+++ b/themes/lucene/templates/solr/resources.html
@@ -9,3 +9,7 @@
<dd><a data-scroll href="#presentations">Presentations</a></dd>
<dd><a data-scroll href="#videos">Videos</a></dd>
{% endblock %}
+
+{% block content_inner %}
+{{ page.content | replace('__DOCSLINK__', '/solr/%s/index.html' %
LUCENE_LATEST_RELEASE | replace(".", "_")) }}
+{% endblock content_inner %}
{{noformat}}
> Move Lucene web site from svn to git
> ------------------------------------
>
> Key: LUCENE-8987
> URL: https://issues.apache.org/jira/browse/LUCENE-8987
> Project: Lucene - Core
> Issue Type: Task
> Components: general/website
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Priority: Major
> Attachments: lucene-site-repo.png
>
>
> INFRA just enabled [a new way of configuring website
> build|https://s.apache.org/asfyaml] from a git branch, [see dev list
> email|https://lists.apache.org/thread.html/b6f7e40bece5e83e27072ecc634a7815980c90240bc0a2ccb417f1fd@%3Cdev.lucene.apache.org%3E].
> It allows for automatic builds of both staging and production site, much
> like the old CMS. We can choose to auto publish the html content of an
> {{output/}} folder, or to have a bot build the site using
> [Pelican|https://github.com/getpelican/pelican] from a {{content/}} folder.
> The goal of this issue is to explore how this can be done for
> [http://lucene.apache.org|http://lucene.apache.org/] by, by creating a new
> git repo {{lucene-site}}, copy over the site from svn, see if it can be
> "Pelicanized" easily and then test staging. Benefits are that more people
> will be able to edit the web site and we can take PRs from the public (with
> GitHub preview of pages).
> Non-goals:
> * Create a new web site or a new graphic design
> * Change from Markdown to Asciidoc
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
