How to Contribute to Solr Documentation

The Lucene/Solr project has made it easy for anyone to contribute to the Solr Reference Guide with a patch.

The Guide is written in simple AsciiDoc-formatted files, and the source lives in the main Lucene/Solr source repository, right alongside the code.

The following sections give an overview of how to work with AsciiDoc-format files, how our documentation is generated, and how to do a Ref Guide release.

Once you have a patch you’d like to contribute, you can submit it with a JIRA issue, the same as any other patch. See also the Solr wiki section on How To Contribute for information on submitting patches.

Working with AsciiDoc Files

AsciiDoc Syntax Cheatsheet

The definitive manual on AsciiDoc syntax is in the Asciidoctor User Manual. To help people get started, however, here is a simpler cheat sheet.

AsciiDoc vs Asciidoctor Syntax

We use tools from the Asciidoctor project to build the HTML and PDF versions of the Ref Guide. Asciidoctor is a Ruby port of the original AsciiDoc project, which was mostly abandoned several years ago.

While much of the syntax between the two is the same, there are many conventions supported by Asciidoctor that did not exist in AsciiDoc. While the Asciidoctor project has tried to provide back-compatibility with the older project, that may not be true forever. For this reason, it’s strongly recommended to only use the Asciidoctor User Manual as a reference for any syntax that’s not described here.

Basic AsciiDoc Syntax


Put asterisks around text to make it bold.


Use underlines on either side of a string to put text into italics.


Equal signs (=) are used for heading levels. Each equal sign is a level. Each page can only have one top level (i.e., only one section with a single =).

Levels should be appropriately nested. During the build, validation occurs to ensure that level 3s are preceded by level 2s, level 4s are preceded by level 3s, etc. Including out-of-sequence heading levels (such as a level 3 then a level 5) will not fail the build, but will produce an error.

Code Examples

Use backticks ` for text that should be monospaced, such as code or a class name in the body of a paragraph.

Longer code examples can be separated from text with source blocks. These allow defining the syntax being used so the code is properly highlighted.

Example Source Block
<field name="id" type="string" indexed="true" stored="true" required="true" multiValued="false" />

If your code block will include line breaks, put 4 hyphens (----) before and after the entire block.

Source Block Syntax Highlighting

The PDF and HTML outputs use Pygments to add syntax highlighting to code examples. This is done by adding the language of the code block after the source, as shown in the above example source block (xml in that case).

Pygments has a long selection of lexers available. You can see the full list at Use one of the valid short names to get syntax highlighting for that language.

Ideally, we will have an appropriate lexer to use for all source blocks, but that’s not possible. When in doubt, choose text, or leave it blank.

Block Titles

Titles can be added to most blocks (images, source blocks, tables, etc.) by simply prefacing the title with a period (.). For example, to add a title to the source block example above:

.Example ID field
<field name="id" type="string" indexed="true" stored="true" required="true" multiValued="false" />

When converting content to HTML or PDF, Asciidoctor will automatically render many link types (such as http: and mailto:) without any additional syntax.

However, you can add a name to a link by adding the URI followed by square brackets:[Solr Website]

A warning up front, linking to other pages can be a little bit painful. There are slightly different rules depending on the type of link you want to create, and where you are linking from.

The build process includes a validation for internal or inter-page links, so if you can build the docs locally, you can use that to verify you constructed your link properly (or pay attention to the Jenkins build after your commit).

With all of the below examples, you can add text to display as the link title by adding a comma after the section reference followed by the display text, as in:

<<schema-api.adoc#modify-the-schema,Modify the Schema>>

To link to an anchor (or section title) on the same page, you can simply use double angle brackets (<< >>) around the anchor/heading/section title you want to link to. Any section title (a heading that starts with equal signs) automatically becomes an anchor during conversion and is available for deep linking.


If I have a section on a page that looks like this (from defining-fields.adoc):

== Field Properties

Field definitions can have the following properties:

To link to this section from another part of the same defining-fields.adoc page, I simply need to put the section title in double angle brackets, as in:

See also the <<Field Properties>> section.

The section title will be used as the display text; to customize that add a comma after the the section title, then the text you want used for display.

When linking to any section (on the same page or another one), you must also be aware of any pre-defined anchors that may be in use (these will be in double brackets, like [[ ]]). When the page is converted, those will be the references your link needs to point to.


Take this example from configsets-api.adoc:

== Create a ConfigSet

To link to this section, there are two approaches depending on where you are linking from:

  • From the same page, simply use the anchor name: <<configsets-create>>.

  • From another page, use the page name and the anchor name: <<configsets-api.adoc#configsets-create>>.

To link to another page or a section on another page, you must refer to the full filename and refer to the section you want to link to.

Unfortunately, when you want to refer the reader to another page without deep-linking to a section, you cannot simply put the other file name in angle brackets and call it a day. This is due to the PDF conversion - once all the pages are combined into one big page for one big PDF, the lack of a specific reference causes inter-page links to fail.

So, you must always link to a specific section. If all you want is a reference to the top of another page, you can use the page-shortname attribute found at the top of every page as your anchor reference.


The file upgrading-solr.adoc has a page-shortname at the top that looks like this:

= Upgrading Solr
:page-shortname: upgrading-solr
:page-permalink: upgrading-solr.html

To construct a link to this page, we need to refer to the file name (upgrading-solr.adoc), then use the page-shortname as our anchor reference. As in:

For more information about upgrades, see <<upgrading-solr.adoc#upgrading-solr>>.
As of July 2017, all pages have a page-shortname that is equivalent to the filename (without the .adoc part).

Linking to a section is the same conceptually as linking to the top of a page, you just need to take a little extra care to format the anchor ID in your link reference properly.

When you link to a section on another page, you must make a simple conversion of the title into the format the section ID will be created during the conversion. These are the rules that transform the sections:

  • All characters are lower-cased.

    • Using security.json with Solr becomes using security.json with solr

  • All non-alpha characters are removed, with the exception of hyphens (so all periods, commas, ampersands, parentheses, etc., are stripped).

    • using security.json with solr becomes using security json with solr

  • All whitespaces are replaced with hyphens.

    • using security json with solr becomes using-security-json-with-solr


The file schema-api.adoc has a section "Modify the Schema" that looks like this:

== Modify the Schema

`POST /_collection_/schema`

To link from to this section from another page, you would create a link structured like this:

  • the file name of the page with the section (schema-api.adoc),

  • then the hash symbol (#),

  • then the converted section title (modify-the-schema),

  • then a comma and any link title for display.

The link in context would look like this:

For more information, see the section <<schema-api.adoc#modify-the-schema,Modify the Schema>>.

Ordered and Unordered Lists

AsciiDoc supports three types of lists:

  • Unordered lists

  • Ordered lists

  • Labeled lists

Each type of list can be mixed with the other types. So, you could have an ordered list inside a labeled list if necessary.

Unordered Lists

Simple bulleted lists need each line to start with an asterisk (*). It should be the first character of the line, and be followed by a space.

These lists also need to be separated from the

Ordered Lists

Numbered lists need each line to start with a period (.). It should be the first character of the line, and be followed by a space.

This style is preferred over manually numbering your list.

Labeled Lists

These are like question & answer lists or glossary definitions. Each line should start with the list item followed by double colons (::), then a space or new line.

Labeled lists can be nested by adding an additional colon (such as :::, etc.).

If your content will span multiple paragraphs or include source blocks, etc., you will want to add a plus sign (+) to keep the sections together for your reader.

We prefer this style of list for parameters because it allows more freedom in how you present the details for each parameter. For example, it supports ordered or unordered lists inside it automatically, and you can include multiple paragraphs and source blocks without trying to cram them into a smaller table cell.


There are two ways to include an image: inline or as a block.

Inline images are those where text will flow around the image. Block images are those that appear on their own line, set off from any other text on the page.

Both approaches use the image tag before the image filename, but the number of colons after image define if it is inline or a block. Inline images use one colon (image:), while block images use two colons (image::).

Block images automatically include a caption label and a number (such as Figure 1). If a block image includes a title, it will be included as the text of the caption.

Optional attributes allow you to set the alt text, the size of the image, if it should be a link, float and alignment.


Tables can be complex, but it is pretty easy to make a basic table that fits most needs.

Basic Tables

The basic structure of a table is similar to Markdown, with pipes (|) delimiting columns between rows:

| col 1 row 1 | col 2 row 1|
| col 1 row 2 | col 2 row 2|

Note the use of |=== at the start and end. For basic tables that’s not exactly required, but it does help to delimit the start and end of the table in case you accidentally introduce (or maybe prefer) spaces between the rows.

Header Rows

To add a header to a table, you need only set the header attribute at the start of the table:

| header col 1 | header col 2|
| col 1 row 1 | col 2 row 1|
| col 1 row 2 | col 2 row 2|
Defining Column Styles

If you need to define specific styles to all rows in a column, you can do so with the attributes.

This example will center all content in all rows:

[cols="2*^" options="header"]
| header col 1 | header col 2|
| col 1 row 1 | col 2 row 1|
| col 1 row 2 | col 2 row 2|

Alignments or any other styles can be applied only to a specific column. For example, this would only center the last column of the table:

[cols="2*,^" options="header"]
| header col 1 | header col 2|
| col 1 row 1 | col 2 row 1|
| col 1 row 2 | col 2 row 2|

Many more examples of formatting:

More Options

Tables can also be given footer rows, borders, and captions. You can determine the width of columns, or the width of the table as a whole.

CSV or DSV can also be used instead of formatting the data in pipes.

Admonitions (Notes, Warnings)

AsciiDoc supports several types of callout boxes, called "admonitions":

  • NOTE

  • TIP




It is enough to start a paragraph with one of these words followed by a colon (such as NOTE:). When it is converted to HTML or PDF, those sections will be formatted properly - indented from the main text and showing an icon inline.

You can add titles to admonitions by making it an admonition block. The structure of an admonition block is like this:

.Title of Note
Text of note

In this example, the type of admonition is included in square brackets ([NOTE]), and the title is prefixed with a period. Four equal signs give the start and end points of the note text (which can include new lines, lists, code examples, etc.).

Tools for Working with AsciiDoc Files

AsciiDoc vs Asciidoctor

The Solr Ref Guide is written in AsciiDoc format. This format is generally considered an extension of Markdown, because it has support for tables of contents, better table support, and other features that make it more appropriate for writing technical documentation.

We are using a version of the AsciiDoc syntax along with tools from an open source project called Asciidoctor. This provides full support for the AsciiDoc syntax, but replaces the original Python processor with one written in Ruby. There is a Java implementation, known as AsciidoctorJ. Further extensions from the original AsciiDoc project include support for font-based icons and UI elements.

Helpful Tools

You can write AsciiDoc without any special tools. It’s simply text, with familiar syntax for bold (*) and italics (_).

Having some tools in your editor is helpful, though.

Doc Preview

This allows you to see your document in something close to what it might appear like when output to HTML.

  • Atom has AsciiDoc Preview, which gives you a panel that updates as you type. There are also a couple of other plugins to support AsciiDoc format and auto-complete.

  • There is a Live Preview browser plugin for Chrome, Firefox and Opera which allow you to open your AsciiDoc page in the browser. It will also update as you type.

  • There is also an Intellij IDEA plugin to support AsciiDoc format.

Modifying the Output Formats

The Solr Reference Guide is published in two formats: HTML and PDF. Different tools are used for each.

Making Changes to HTML Version

The Solr Ref Guide uses Jekyll to build the HTML version of the site.

What is Jekyll?

Jekyll is a static site generator, meaning that it takes some set of documents and produces HTML pages. It allows for templating of the pages, so each page has the same look and feel without having to code headers, footers, logos, etc., into every page.

Jekyll is an open source project written in Ruby, online at

Jekyll-Asciidoctor Plugin

We use a plugin for Jekyll from the Asciidoctor project to integrate Jekyll with Asciidoc formatted content. The source for the plugin is available at

This plugin allows us to use Asciidoctor-style variables with Jekyll, instead of having to maintain two sets of the same variables (one for HTML version and another for PDF version).

Jekyll Basics

The following sections describe the main features of Jekyll that you will encounter while working with the Solr Ref Guide.


The _config.yml is a global configuration file that drives many of the options used when building the site (particularly in our use of Jekyll).

We have templatized _config.yml so in our use of Jekyll you will find it as solr-ref-guide/_config.yml.template. This allows us to define some variables during the build, and use common Lucene/Solr build parameters (such as versions, etc.).

Front Matter

Front matter for Jekyll is like a header that defines the title of the page, and any other variables that may be helpful or even required when rendering the page.

Every document that will be converted to HTML must include at least the page title at the top of the page.

Many guides to Jekyll also say that defining the layout in the front matter is required. However, since we only have one layout for all pages, we have defined this as a default.

The Solr Ref Guide uses the front matter to define some custom attributes on a per page basis:

  • page-shortname - uniquely identifying the page

  • page-permalink - permanent URL of a page,

  • page-children - ordered list of child pages, this is used to build the site navigation menu that appears to the left of each page’s content (and to order the pages in the PDF)

There are also some optional custom attributes that can be defined in pages to affect the Table of Contents presentation in jekyll:

  • page-toclevels - changes how "deep" the TOC will be in terms of nested section/sub-section titles (default = 2)

  • page-tocclass - changes the CSS class applied to the TOC, default = "normal", resulting in the class name toc-normal. The other option is "right", to put the TOC on the right side of the page.

  • page-toc - if this is false, then no TOCs will be generated for the page at all.

The special macro
can be used anywhere in a page to create an "In this Section" TOC covering only the sub-headings in the same section. :page-toc: false will also prevent this macro from working, so if you want no "top level" TOC, but you do want section TOCs, use :page-toclevels: 0

Layouts define the "look and feel" of each page.

Jekyll uses Liquid for page templates.

For our implementation of Jekyll, layouts are found in solr-ref-guide/src/_layouts


Include files are usually small files that are pulled into a layout when a page is being built. They are Liquid templates that define an area of the page. This allows flexibility across layouts - all pages can have the same header without duplicating code, but different pages could have different menu options.

Include files that we use define the top navigation, the page header, the page footer, and tables of contents.

For our implementation of Jekyll, include files are found in solr-ref-guide/src/_includes.

Data Files

Data files include data such as lists, that should be included in each page. The left-hand navigation is an example of a data file.

For our implementation of Jekyll, data files are found in solr-ref-guide/src/_data.

Building the HTML Site

An Ant target build-site will build the full HTML site. This target builds the navigation for the left-hand menu, and converts all .adoc files to .html, including navigation and inter-document links.

Making Changes to the PDF Version

The main published artifact of the Solr Reference Guide is a PDF document.

The PDF version of the Ref Guide uses asciidoctor-pdf (indirectly) to convert the .adoc files to PDF.

In order for all of the various files to be converted into a single, large, PDF file, another .adoc file must be created.

About asciidoctor-pdf

Our PDF build process uses the asciidoctor-ant project to integrate Asciidoctor.

The asciidoctor-ant project is really an Ant wrapper around asciidoctorj. This is a Java binding of several Asciidoctor projects that produces a .jar that includes Asciidoctor, Asciidoctor PDF and Asciidoctor EPub.

Since it is a binding for the Ruby implementations of these three projects, they each work the same way they would if we were using the Ruby versions.

Configuring the PDF Theme

Nearly all of the styling and layout of the PDF is controlled by a single YAML file that is called a theme.

See the section Modifying the Theme for information on how to update the theme.

Declaring the Theme to Use

Our theme is refguide-theme.yml, found in solr/solr-ref-guide/pdf/themes.

New themes must be named to include -theme.yml at the end. They must also be in proper YAML format.

The theme to use when generating the PDF is defined with the pdf-style attribute. Only the first part of the file name is used. So, a theme file named refguide-theme.yml is selected by defining pdf-style=refguide.

In the section Asciidoctor PDF Attributes below, we can see how we’ve declared this in our Ant target.

Modifying the Theme

All of the styling capabilities are described in the Asciidoctor PDF Theming Guide.

About the Uber-Document

In order for all of the files in .adoc format to be compiled into a single PDF, we need to give the process one .adoc file (an "uber-document") that includes all of the content we want in the PDF. In other words, there is no command that says "take all the files in this directory and make one PDF".

Asciidoctor has a nice feature called the include directive, which allows you to insert content from another file into the current file (more details in the Asciidoctor documentation).

We wanted to make sure we didn’t add to the burden of maintaining the PDF by asking everyone to update the uber-document or trying to institute some sort of check on if all the pages are included and in the right place in the hierarchy. Instead, the uber-document is build programmatically at build time.

The uber-document is found in solr/solr-ref-guide/src/pdf/SolrRefGuide-all.adoc. This document is very simple - it includes only the Apache license statement and a single include directive to another file:


The Ant target build-pdf includes a dependency on another target, build-nav-data-files. This target looks at each document and builds the pdf-main-body.adoc file with the proper hierarchy of all pages.

You will not see the pdf-main-body.adoc in solr/solr-ref-guide/src/_data directory. This file exists only once it has been built, and it is placed in the build directory, at solr/solr-ref-guide/build/content_data.

Configuring the build-pdf Ant Target

Since most of the styling and layout is defined by the theme, the options that must be configured in the Ant target relate to where to find referenced files, font directories, image directories, and similar top-level document settings.

There are two types of settings at work in our Ant target. First are the settings which are part of the asciidoctor-ant jar. Second, we are able to declare any Asciidoctor PDF attribute (setting) that we want to apply to the entire PDF.

Our Ant target (build-pdf) uses the following settings:

  <attribute key="icons" value="font" />
  <attribute key="icon-set" value="fa" />
  <attribute key="pdf-stylesDir" value="./pdf/themes"/>
  <attribute key="pdf-style" value="refguide"/>
  <attribute key="pdf-fontsDir" value="./pdf/fonts"/>
  <attribute key="pagenums" value='' />
  <attribute key="figure-caption!" value='' />
  <attribute key="idprefix" value='' />
  <attribute key="idseparator" value='-' />
  <!-- attributes used in adoc files -->
  <!-- NOTE: If you add any attributes here for use in adoc files, you almost certainly need to also add
      them to the _config.yml.template file for building the jekyll site as well
  <!-- ... -->

There are a lot of options here. Note that some include the <attribute> tag and some do not. Those that do not are options provided by asciidoctor-ant so don’t need any special syntax. The options with the <attribute> tag are not provided by asciidoctor-ant but are supported by asciidoctor-pdf so will be applied when the target is run. A few of these are custom variables that we have defined ourselves.

Asciidoctor Ant Attributes

Defines where to find the source file to build the PDF. The variable is declared earlier in build.xml.


The source file name, which in our case will be built as described in the section About the Uber-Document.


The root path for any included files.


Defines where the resulting PDF file should go. In this case, the


The output format. The asciidoctor-ant jar is also capable of outputting DocBook format, so we must declare we want a PDF.


The file extensions to allow for the source document.


The library to use for syntax highlighting source code.


The directory to use to find images referenced in the documents.


Adds support for book-style format and sections, such as a preface, colophon, glossary, index, etc.


Allows including resources that are external to the parent directory of the source file. For example, source examples could be pulled from Solr’s source code instead of copied to documentation. This setting allows that to happen.

Asciidoctor PDF Attributes
<attribute key="icons" value="font" />

The style of icons.

<attribute key="icon-set" value="fa" />

The icon set to use. We use the Font Awesome font set.

<attribute key="pdf-stylesDir" value="./pdf/themes"/>

The directory to find PDF themes. See the section Configuring the PDF Theme for more details on themes.

<attribute key="pdf-style" value="refguide"/>

The theme to use. The theme must be saved in the directory referenced with the pdf-stylesDir attribute, and must be named <pdf-style>-theme.yml.

<attribute key="pdf-fontsDir" value="./pdf/fonts"/>

The directory where to find fonts declared in the theme.

<attribute key="figure-caption!" value='' />

Sets caption labels and numbers (such as "Figure 1") to block images. The exclamation at the end of this setting in our config disables figure captioning.

<attribute key="idprefix" value='' />

Sets the prefix for auto-generated section IDs, such as those from headings in a page. In our config, this is effectively "null", so auto-generated section IDs do not have any prefix.

<attribute key="idseparator" value='-' />

Sets the separator between words in auto-generated section IDs to a hyphen (-).

Custom Attributes

These attributes use variables that are inserted by Ant during the PDF creation process. This allows us to pull from standard Lucene/Solr build files, and not have to update several places for any release. The Ant build process updates the _config.yml file from the _config.yml.template, then these attributes pull the proper value from that file.

<attribute key="solr-guide-draft-status" value="$" />

Indicates if this is a DRAFT PDF or not.

<attribute key="solr-guide-version" value="$7.0" />

The version of the Guide itself.

<attribute key="solr-docs-version" value="$7.0" />

The version of Solr covered by this guide.

<attribute key="solr-javadocs" value="$" />

Sets the path for Solr javadoc links to include the right path for the current release version.

<attribute key="lucene-javadocs" value="$" />

Sets the path for Lucene javadoc links to the right path for the current release version.

<attribute key="build-date" value="${DSTAMP}" />

Sets the date of the build to add the date to the footer of each page of the PDF.

<attribute key="build-year" value="${current.year}" />

Sets the year of the build to add the date to the copyright notice.

Building & Publishing the Guide

Publication Process

About the Formats

The Solr Ref Guide is published in two formats: PDF and HTML.

The PDF version is the official release, and requires a vote before release. See Publishing PDF Version for details on how to generate the PDF and hold a vote.

The HTML version is considered a "convenience" version, and does not require a vote. See Publishing HTML Version for details on how to publish the HTML.

It’s strongly preferred that both PDF and HTML versions are available during the vote for the PDF. However, since the HTML version is not an official release, it is more of an unwritten rule to publish the HTML at the same time as producing a release candidate for the PDF.

Publishing PDF Version

The PDF version of the Solr Reference Guide is the official version. As such, it is voted on by the community before release, and is treated as an official artifact of the Lucene/Solr project.

  • You have checked out the Lucene/Solr source code on the machine you will be doing the release from. You will need scripts in the dev-tools directory.

  • You have generated a GPG key. See the Apache documentation on generating a code signing key.

  • You have Python 3 installed. This is needed to poll the mirrors after release to be sure it’s propagated enough to make the announcement.

Generate the PDF

No local dependencies are required to build the PDF. The Ant target will download the jars and other items it requires.

The build process generates the PDF, including the page hierarchy, and then runs an optimization script on the PDF to make it smaller.

To build the PDF:

  1. Run ant build-pdf -Dsolr-guide-version=X.Y

  2. The resulting PDF will be in solr/build/solr-ref-guide.

The -Dsolr-guide-version system property is optional. By default the build system uses the of the current branch and assumes this is a DRAFT build.
Prepare and Upload Release Candidate

The dist/dev Subversion repository includes a directory for the Solr Ref Guide at lucene/solr/ref-guide which can host the release candidate (RC) during the VOTE stage of the process.

These steps walk through checking out this directory and uploading the Guide to it.

  1. Checkout the directory: svn co solr-ref-guide-rc

    • If you have already checked out this directory, you can simply update it: svn update solr-ref-guide-rc

  2. Change directories so solr-ref-guide-rc is your working directory (cd solr-ref-guide-rc).

The next step requires that you have already generated your GPG keys. Your GPG passphrase will be required.
  1. Run the Prep Ref Guide script to prepare the RC. This script ensures proper naming of the PDF file, generates .sha1 and .asc files and creates the proper RC sub-directories under solr-ref-guide-rc.

    1. The structure of the input is: <path/PDFfilename> <Solrversion-RC#> GPGkey.

    2. From the solr-ref-guide-rc directory, it will look something like this:

      $ ~/lucene-source/dev-tools/scripts/ apache-solr-ref-guide-7.0.pdf 7.0-RC0
      + mkdir apache-solr-ref-guide-7.0-RC0
      + mv apache-solr-ref-guide-7.0.pdf apache-solr-ref-guide-7.0-RC0/apache-solr-ref-guide-7.0.pdf
      + cd apache-solr-ref-guide-7.0-RC0
      + sha1sum apache-solr-ref-guide-7.0.pdf
      + gpg -u DEADBEEF --armor --output apache-solr-ref-guide-7.0.pdf.asc --detach-sig apache-solr-ref-guide-7.0.pdf
      You need a passphrase to unlock the secret key for
      user: "Your Name <>"
      4096-bit RSA key, ID DEADBEEF, created 1969-07-04
  2. Add and commit the new release candidate to the dist/dev with these steps:

    1. svn add apache-solr-ref-guide-7.0-RC0

    2. svn commit -m "7.0 ref guide RC0"

Hold a VOTE

Votes must be sent to the lucene-dev mailing list (

  1. Send an email to with subject, "VOTE: Release Apache Solr Ref Guide for Solr X.Y".

  2. The body of the email should include the full URL of the RC directory in the dist/dev repo. Such as:

  3. You can add your own +1 to the vote announcement email.

  4. If there are issues that need to be resolved, you can start the process over, using RC1, RC2, etc., as needed.

Ideally, the HTML version will also be available for voters to evaluate, see the section Publishing HTML Version below for details of how to do that.

Publish to Production & Archive Old Versions

Once at least three PMC members have voted for release (see Apache Voting Process for details on the rules for votes), the release candidate can be released.

  1. Use the Publish Solr Ref Guide script ( to generate the proper SVN commands to be run to execute a remote move of the RC files to the final dist/releases repository.

    1. The script takes only the version and RC number that passed the vote as inputs, such as 7.0-RC0.

    2. The input and output of the script will look like this:

      $ ~/lucene-source/dev-tools/scripts/ X.Y-RCZ
      ## Run the following commands when ready...
      svn move -m 'publishing apache-solr-ref-guide-X.Y-RCZ'
      svn rm -m 'cleaning up apache-solr-ref-guide-X.Y-RCZ'
  2. The release should propagate to as many mirrors as possible before announcing the release, generally 24 hours is long enough. Use the Poll Mirrors script ( to check the status:

    python3 -u ~/lucene-source/dev-tools/scripts/ -details -p lucene/solr/ref-guide/apache-solr-ref-guide-X.Y.pdf
    • This script requires Python 3 to be installed on your machine.

    • If you have over 85% of the mirrors with the file, it’s OK to go ahead with the announcement.

  3. You may get an automated email about updating the ASF release repository; you can safely ignore this email.

  4. The dist/releases repo is only meant to keep the latest releases. Shortly after new releases are mirrored, they are copied to, so older releases can safely be deleted from dist/releases since they have been backed up in the archives.

    1. Run the Archive Ref Guide script ( using the X.Y version of the Ref Guide that has just been published. Older RCs will also be removed.

    2. Again, this script doesn’t do any direct removal of files, it only outputs SVN commands for you to copy and paste:

      $ ~/lucene-source/dev-tools/scripts/ X.Y
      ## Run the following commands when ready...
      # Delete old releases
      svn rm -m 'removing archived ref guide files prior to X.Y'
      # Delete old RC files
      svn rm -m 'cleaning up old RCs now that X.Y has been released'
Announce the Release

Announce the availability of the new Ref Guide on and CC and

You must send the announcement email from your email address or announce@apache will reject it.

Always use the link to the download redirector for the announcement, as it will automatically direct users to the closest mirror for download:

You could also include a link to the HTML version in your announcement, if the publication process for that has finished.

Publishing HTML Version

The steps to publish the Guide differ depending on if it is the first time the Guide has been published or if it is an update to an already published Guide.

Building the HTML Version

If you have the required dependencies on your local machine, you can build the HTML version with ant build-site -Dsolr-guide-version=X.Y. The dependencies are listed in solr-ref-guide/README.adoc.


If you do not have the required dependencies, and don’t choose to install them, you can download the files from the Jenkins (Solr Reference Guide job). But these HTML pages will have the DRAFT status noted in them and will not be suitable for publishing.

Publish a New Guide
Step 1: Update extpaths.txt in CMS Staging
  1. Checkout CMS trunk:

    svn co --depth=immediates website-source
    • If you already have this repo checked out, you can simply svn up website-source to update to the latest revision.

  2. cd website-source

  3. Add Guide branch dir: echo solr/guide/X_Y >> extpaths.txt

  4. Commit changes:

    svn commit -m "Update CMS production sync exceptions for X_Y_Z Guide" extpaths.txt
Step 2: Push Guide to Website Production

Go to the checkout directory where you have built the Guide and push the documentation via subversion import. You must push it to the path you just added to extpaths.txt, so if the path you added was solr/guide/6_5, you’ll use the path as shown in the below example:

svn -m "Add Ref Guide for Solr 6.5" import <checkoutroot>/solr/build/solr-ref-guide/html-site

Confirm you can browse to these URLs manually, and especially that solr javadocs link back to lucene’s correctly. Example:

Step 3: Push Staging extpaths.txt to Production

The extpaths.txt works by listing paths that should be ignored when the CMS syncs the staging and production repositories. Publishing staging to production will only succeed if the paths listed in extpaths.txt exist in production. At the same time, if a path exists in production but not in staging it will be deleted unless it is defined in extpaths.txt. After pushing the content to production, check that the extpaths.txt in production includes the proper path to ensure that the Guide is not deleted incorrectly. If it does not exist in production, try to publish the site again to make sure it is updated.

Update Ref Guide Landing Page

Update the landing page at to link to the newest version.

You can use the CMS system for this since it is a small change, or you can edit the file locally and commit it to the staging repo.

Update a Published Guide

If you need to re-publish an existing online copy of the Guide, you will need to checkout the directory in production website repository and overwrite the existing files:

  1. Build the new HTML files locally (ant clean build-site), or download them from Jenkins.

  2. Checkout the directory you need to update from the production repo: svn co<dir>;.

    • This command checks out the Guide version directory into a local subdirectory with the same name as the version (such as "6_5"). You can provide a better name locally if you prefer by adding it to the end of the command shown above.

    • Don’t shortcut this and download the whole production website. It will take an incredibly long time and that will feel like forever.

  3. Copy the files from the build location to the checked out Guide directory. For example, if we needed to replace the current Guide for Solr 6.5, we’d do cp -r <checkoutroot>/solr/build/html-site 6_5/.

  4. Use svn status to see the files modified.

  5. If there are any pages added or deleted, use svn add <file> or svn rm <file> as needed.

  6. Commit the changes: svn commit -m "Update production 6.5 Ref Guide"

Comments on this Page

We welcome feedback on Solr documentation. However, we cannot provide application support via comments. If you need help, please send a message to the Solr User mailing list.