Details
-
Task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
New
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
Attachments
Attachments
Issue Links
- is depended upon by
-
LUCENE-9198 Remove news section from TLP website
- Resolved
- is related to
-
LUCENE-9048 Tutorial and docs section missing from the new website
- Resolved
-
SOLR-13910 Create security news feed on website with RSS/Atom feed
- Resolved
- relates to
-
LUCENE-9229 Lucene web site broken links
- Open
1.
|
Migrate existing site content (except javadoc, refguide) | Resolved | Jan Høydahl |
|
||||||||
2.
|
Setup minimal site with working Pelican build | Resolved | Jan Høydahl |
|
||||||||
3.
|
Configure branches, auto build and auto stage/publish | Resolved | Jan Høydahl |
|
||||||||
4.
|
Design a new solution for publishing JavaDoc | Resolved | Jan Høydahl | |||||||||
5.
|
Fix issues to get site up to par with current prod | Resolved | Jan Høydahl |
|
||||||||
6.
|
Find a way to publish Solr RefGuide and Javadocs without checking into git | Resolved | Uwe Schindler | |||||||||
7.
|
Add Apache license headers | Resolved | Jan Høydahl |
|
||||||||
8.
|
Document how to update web site | Closed | Jan Høydahl |
|
||||||||
9.
|
Update Release docs an scripts with new site instructions | Closed | Jan Høydahl |
|
||||||||
10.
|
Officially publish the new site | Resolved | Uwe Schindler | |||||||||
11.
|
Make page ready for pure HTTPS | Resolved | Uwe Schindler |