This repository contains the source for the Github generated GeoServer home page.
If you stumble into any issue with the GeoServer web site please report it in our Jira issue tracker.
The site is built with Jekyll. To perform a single build of the site:
The site contents will result in the
Jekyll can also be run in "watch" mode for development:
jekyll serve -w
The site contents will be served at http://localhost:4000.
When a release is performed the site contents are updated to reflect the new release. Below is the process of updating site contents for a stable release.
release/stable/index.htmlwith the details of your new release. The
release_dateshould all be updated. The value for
jira_versioncan be found by navigating to that version on Jira and examining the URL. For example, for example,
https://osgeo-org.atlassian.net/projects/GEOS/versions/10601, giving a
10601. For a maintenance or development release, instead modify
release/dev/index.htmlrespectively. You can also update the value of
release/2.7.x/index.htmlto be the same as this latest release.
Copy stable to the appropriate version number (so your blog post has something to link to). For example if the
2.7.2make a copy using:
cp -r release/stable release/2.7.2
For a maintenance or development release, instead copy
_config.ymland update the
stable_versionproperty to the current version. This change will be reflected in
download/index.html. For a maintenance or development release, instead change
download/index.htmlby adding your new page to the list of releases. To find this list, do a text search for
releases. You should find a section that looks like this:
<ul class="list-inline"> <li><a href="/release/2.10.5">2.10.5</a></li> <li><a href="/release/2.10.4">2.10.4</a></li> <li><a href="/release/2.10.3">2.10.3/a></li> </ul> <ul class="list-inline"> <li><a href="/release/2.10.2">2.10.2</a></li> <li><a href="/release/2.10.1">2.10.1</a></li> <li><a href="/release/2.10.0">2.10.0/a></li> </ul> <ul class="list-inline"> <li><a href="/release/2.10-RC1">2.10-RC1</a></li> <li><a href="/release/2.10-beta">2.10-beta</a></li> <li><a href="/release/2.10-M0">2.10-M0</a></li> </ul>
There are seperate sections for
maintenance. Ensure you have the right section, then add a line to the top of the list for your version. Try to keep the lists balanced, and limit each list to no more than 4 items - create a third list row if necessary. Isolate milestones, beta and RC on their own row if you can.
When publishing a milestone, beta or release candidate:
There is also a special section for
developmentwe only provide links to milestone, beta and release candidates. These releases are being made available for testing but are not recommended for production use.
Create a new
_layouts/release_<version>.htmltemplate by copying the previous template and adding an entry for any new extensions that have been released on the new branch.
release/dev/index.htmlto reflect the new branch, and change the
When creating the final release:
Change all the entries for
release/master/index.htmlto reflect the new branch identities.
_config.ymlshould be blank (as the development period is now over).
download/index.html, copy the current
maintenancesection to the
archivedsection, copy the current
stablesection to the
maintenancesection, and update the
stablesection with the releases from the new stable branch.
Create the download page for nightly builds. For example, if creating the branch
index.htmlwith the appropriate versions.