[LUCENE-8987] Move Lucene web site from svn to git

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Component/s: general/website
• Lucene Fields: New
• Assignee: Jan Høydahl
• Reporter: Jan Høydahl
• Created: 22/Sep/19 22:47
• Updated: 09/Mar/20 09:10
• Resolved: 09/Mar/20 09:10

Description

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

Issue Links

• is depended upon by: LUCENE-9198 Remove news section from TLP website
• is related to: LUCENE-9048 Tutorial and docs section missing from the new website
• is related to: INFRA-19439 Add a way to publish static HTML content of huge size (outside of pelican CMS) without checking into Git
• is related to: SOLR-13910 Create security news feed on website with RSS/Atom feed
• is related to: INFRA-19859 Switch production website to Pelican
• relates to: LUCENE-9229 Lucene web site broken links

Sub-Tasks

• Migrate existing site content (except javadoc, refguide): Resolved
• Setup minimal site with working Pelican build: Resolved
• Configure branches, auto build and auto stage/publish: Resolved
• Design a new solution for publishing JavaDoc: Resolved
• Fix issues to get site up to par with current prod: Resolved
• Find a way to publish Solr RefGuide and Javadocs without checking into git: Resolved
• Add Apache license headers: Resolved
• Document how to update web site: Closed
• Update Release docs an scripts with new site instructions: Open
• Officially publish the new site: Resolved
• Make page ready for pure HTTPS: Resolved