anchor.diff:  +
   * This command checks out the Guide version directory into a local subdirectory with the same name as the version (such as "7_7"). 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_.
  -. Copy the files from the build location to the checked out Guide directory. For example, if we needed to replace the Guide for Solr 7.7, we'd do `cp -r ./solr/build/solr-ref-guide/html-site 7_7/.`
  +. Copy the files from the build location to the checked out Guide directory. For example, if we needed to replace the Guide for Solr 7.7, we'd do `cp -r ./solr/solr-ref-guide/build/html-site 7_7/.`
   . Use `svn status` to see the files modified. If there are any pages added or deleted, use `svn add <file>` or `svn rm <file>` as needed.
   . Commit the changes: `svn commit -m "Update production 7.7 Ref Guide"`
   
  
positive.code: 
  * You have checked out the Lucene/Solr source code on the machine you will be doing the release from.
  * You have Subversion installed. This is needed for committing the HTML files to the production website repo.
  * You have installed Ruby and several gems described in the README file located at `solr/solr-ref-guide/README.adoc` in your Lucene/Solr checkout.
  * All builds must be done from the release branch the Guide is for.
  
  NOTE: Builds are available via https://builds.apache.org/view/L/view/Lucene/[Jenkins] for several branches. However, these HTML pages will have the `DRAFT` status noted in them and are not suitable for final production publishing.
  
  == Build the DRAFT Guide
  
  The build process generates the page hierarchy and builds the HTML pages with custom templates the Lucene/Solr project has defined.
  
  To build the HTML:
  
  . Navigate to `./solr/solr-ref-guide`, where the Guide's `build.xml` is located.
  . Run:
  +
  [source,bash]
  $ gradlew clean buildSite
  +
  This will produce pages with a DRAFT watermark across them. While these are fine for initial DRAFT publication, see the section <<Publish the Final Guide>> for steps to produce final production-ready HTML pages.
  . The resulting Guide will be in `solr/build/solr-ref-guide`. The HTML files themselves will be in `solr/build/solr-ref-guide/html-site`.
  
  == Upload to the Website
  
  Push the Guide directly to production via Subversion `import` from where you built it.
  
  [source,bash]
  svn -m "Add Ref Guide for Solr 7.7" import <checkoutroot>/solr/build/solr-ref-guide/html-site https://svn.apache.org/repos/infra/websites/production/lucene/content/solr/guide/7_7
  
  Confirm you can browse to Guide manually by going to the new URL. For example:
  https://lucene.apache.org/solr/guide/7_7
  
negative.code: Build the Guide locally with a parameter for the Guide version. This requires the same <<Pre-Requisites,pre-requisites>> from above.
  
  [source,bash]
  $gradlew clean solr:solr-ref-guide:buildSite -PsolrGuideVersion=X.Y
  
  where `X.Y` is the version you want to publish (i.e., `7.7`).
  
  IMPORTANT: The `-PsolrGuideVersion` system property is optional if you build drafts locally or as pre-publication DRAFTs (i.e., not for publication). By default the build system uses the `build.gradle` file in the current branch to identify the version and assumes this is a `DRAFT` build which will have a DRAFT watermark and other labels on the pages. Including the `-PsolrGuideVersion` system property ensures the DRAFT watermark and labels are removed from the HTML files.
  
  *Pull Production Repo and Upload New Files*
  
  