lucene-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Walz (Jira)" <>
Subject [jira] [Commented] (LUCENE-8987) Move Lucene web site from svn to git
Date Thu, 14 Nov 2019 19:01:00 GMT


Adam Walz commented on LUCENE-8987:

Thanks [~danmuzi], there are some known issues. I still need to go through each page with
a fine-toothed comb to ensure parity with production. This process will be easier now that
the site is on staging rather than building locally only. I'll go through these mistakes this


I've been trying to port changes in from the svn site, but haven't ported anything in the
last week which is why the slack channel is unchanged. I'll fix that.

> Move Lucene web site from svn to git
> ------------------------------------
>                 Key: LUCENE-8987
>                 URL:
>             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|]
from a git branch, [see dev list email|].
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|] from a {{content/}} folder.
> The goal of this issue is to explore how this can be done for [|]
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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message