[
https://issues.apache.org/jira/browse/LUCENE-8987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17038491#comment-17038491
]
Namgyu Kim commented on LUCENE-8987:
------------------------------------
Hi [~janhoy] :D
Thanks for reflecting my comment.
I checked again and there are some mismatched links.
h4. 1. Download links in TLP News ([https://lucene.staged.apache.org/news.html])
I think the link should change to
[[https://lucene.apache.org/core/downloads.html]] and
[[https://lucene.apache.org/solr/downloads.html]]
=>
[[https://lucene.staged.apache.org/core/downloads.html]] and
[[https://lucene.staged.apache.org/solr/downloads.html]]
h4. 2. Inconsistency for the Solr guide page
Currently, the guide page link in FEATURES and RESOURCES and DOWNLOAD are
different.
1) FEATURES
All 'SOLR REF GUIDE' icons point to [https://lucene.apache.org/solr/guide/**]
ex) In [https://lucene.staged.apache.org/solr/features.html#query] ->
[https://lucene.apache.org/solr/guide/searching.html]
2) RESOURCES
'Solr Quick Start' and 'HTML Version of the Reference Guide' point to
[https://lucene.staged.apache.org/solr/guide/**]
3) DOWNLOAD
'Reference Guide chapter “Upgrade Notes”' and "System Requirements" at the end
point to [https://lucene.apache.org/solr/guide/**]
h4. 3. Javadoc page for Lucene and Solr
There seems to be an intentional "lucene.staged.apache.org" now, but there are
a few mismatched pages.
1) Lucene Javadocs in core
Release Docs -> [https://lucene.staged.apache.org/core/8_4_1/index.html] ->
404 Not Found
2) Solr Javadocs in RESOURCES
Latest Release -> [https://lucene.staged.apache.org/solr/api/index.html] ->
404 Not Found
3) Lucene Downloads
Change log(8.4.1) ->
[https://lucene.apache.org/core/8_4_1/changes/Changes.html]
Change log(7.7.2) ->
[https://lucene.apache.org/core/7_7_2/changes/Changes.html]
-> Inconsistency with 1)
4) Solr Downloads
Change log(8.4.1) ->
[https://lucene.apache.org/solr/8_4_1/changes/Changes.html]
Change log(7.7.2) ->
[https://lucene.apache.org/solr/7_7_2/changes/Changes.html]
-> Inconsistency with 2)
> 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
