[
https://issues.apache.org/jira/browse/LUCENE-8987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16962044#comment-16962044
]
Uwe Schindler commented on LUCENE-8987:
---------------------------------------
Hi,
I was talking last week with Infra on Apachecon:
- We should only move our website (the CMS) to pelican and GIT.
- We should *not* move or commit any javadocs or other non-CMS generated
content (refguide) to the CMS Git. This does not scale and is also not wanted.
The Git repository should be used to manage the markdown sources and the
resulting static HTML pages after staging, not content that's "one-time write"
like refguide or javadocs. Those should be Subversion.
- Infra fully supports Subversion for static webpages and will forever do. One
example is e.g. dist.apache.org which is stored in SVN.
- It's not yet clearly defined how the whole thing would be administered/setup:
E.g., it could be "Alias" directive in the HTTP Server config or similar. We
should in all cases open a new Issue with INFRA to set this up.
For all
> 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
