anchor.diff:  
   *Pull Production Repo and Upload New Files*
   
  -. Checkout the directory you need to update from the production repo:
  +. Checkout the directory you need to update from the svn production repo:
   +
   [source,bash]
   $ svn co https://svn.apache.org/repos/infra/websites/production/lucene/content/solr/guide/<dir>
  
positive.code: Confirm you can browse to Guide manually by going to the new URL. For example:
  https://lucene.apache.org/solr/guide/7_7
  
  *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.
  
  Production URL: https://lucene.apache.org/extpaths.txt
  
  == Publish the Guide
  
  There are two steps to publishing the Guide: first, uploading the DRAFT pages with the production-ready version; and second, updating links to point to the new Guide.
  
  === Update DRAFT for Release
  
  Since the Guide has already been published, you need to update the production
  website repository and overwrite the existing files:
  
  *Build Production Guide*
  
  
negative.code: 
  == 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
  