|
| 1 | +## Pivotal Cloud Foundry Partners Template |
| 2 | + |
| 3 | +This template helps partners prepare documentation for Pivotal Cloud Foundry (PCF) partner services that appear on [Pivotal Network](https://network.pivotal.io/). |
| 4 | + |
| 5 | +### <a id='overview'></a>Overview |
| 6 | + |
| 7 | +Every partner service in PCF is documented on our PCF documentation site. The links to these partner service docs appear on the [front page](http://docs.pivotal.io) under **Partner Services for Pivotal Cloud Foundry**. |
| 8 | + |
| 9 | +For a good example of a partner service doc, see [MongoDB Enterprise Service for PCF](https://docs.pivotal.io/partners/mongodb/index.html). |
| 10 | + |
| 11 | +### <a id='template'></a>How To Use This Template |
| 12 | + |
| 13 | +Partners use this template to develop the documentation for their PCF service. This repo currently includes templates for the following topics: |
| 14 | + |
| 15 | +* [index.html.md.erb](./docs-content/index.html.md.erb): The index of your docs. |
| 16 | +* [installing.html.md.erb](./docs-content/installing.html.md.erb): How to install and configure your product tile. |
| 17 | +* [using.html.md.erb](./docs-content/using.html.md.erb): How to use your product. |
| 18 | +* [release-notes.html.md.erb](./docs-content/release-notes.html.md.erb): Release notes for your product. |
| 19 | + |
| 20 | +To begin using this repo to develop your documentation, perform the following steps: |
| 21 | + |
| 22 | +1. Make a fork of this repo. |
| 23 | +1. Clone your fork onto your local machine. |
| 24 | +1. Work your way through each topic, replacing the placeholders in ALL-CAPS and following the instructions in **bold**. |
| 25 | + * When writing your documentation, follow the guidelines in [Style Notes for Tile Authors](style-guide.md). |
| 26 | +1. Complete the subnav by replacing the placeholders in ALL-CAPS in the subnav file at `docs-book/master_middleman/source/subnavs/myservice_subnav.erb` in this repo. |
| 27 | +1. View your documentation as a live local site in a browser, by following the steps below in the [How To Use Bookbinder To View Your Docs](#bookbinder) section. |
| 28 | +1. When you've finished your documentation, make a pull request to merge your fork into this repo and email the PCF Docs Team at [email protected]. |
| 29 | + |
| 30 | +### <a id='bookbinder'></a>How To Use Bookbinder To View Your Docs |
| 31 | + |
| 32 | +[Bookbinder](https://github.com/pivotal-cf/bookbinder/blob/master/README.md) is a command-line utility for stitching Markdown docs into a hostable web app. The PCF Docs Team uses Bookbinder to publish our docs site, but you can also use Bookbinder to view a live version of your documentation on your local machine. |
| 33 | + |
| 34 | +Bookbinder draws the content for the site from `docs-content`, the subnav from `docs-book`, and various layout configuration and assets from `docs-layout`. |
| 35 | + |
| 36 | +To use Bookbinder to view your documentation, perform the following steps: |
| 37 | + |
| 38 | +1. Install Bookbinder by running `gem install bookbindery`. If you have trouble, consult the [Zero to Bookbinder](#zero-to-bookbinder) section to make sure you have the correct dependencies installed. |
| 39 | +1. On your local machine, `cd` into `docs-book` in the cloned repo. |
| 40 | +1. Run `bundle install` to make sure you have all the necessary gems installed. |
| 41 | +1. Build your documentation site with `bookbinder` in one of the two following ways: |
| 42 | + * Run `bundle exec bookbinder watch` to build an interactive version of the docs and navigate to `localhost:4567/myservice/` in a browser. (It may take a moment for the site to load at first.) This builds a site from your content repo at `docs-content`, and then watches that repo to update the site if you make any changes to the repo. |
| 43 | + * Run `bundle exec bookbinder bind local` to build a Rack web-app of the book. After the bind has completed, `cd` into the `final_app` directory and run `rackup`. Then navigate to `localhost:9292/myservice/` in a browser. |
| 44 | + |
| 45 | +### <a id='zero-to-bookbinder'></a>Zero to Bookbinder: How to Install Bookbinder and Build, View, and Edit Your Docs from Nothing |
| 46 | + |
| 47 | +If you are reading this, Pivotal has invited you to a git repo where you can build and edit documentation in the Ruby / Markdown / HTML format that the online publishing tool [Bookbinder](https://github.com/pivotal-cf/bookbinder/blob/master/README.md) uses to build Pivotal's documentation. |
| 48 | + |
| 49 | +Here's how to install Bookbinder and build your docs from the repo, starting from scratch, on a Mac OS X machine. |
| 50 | + |
| 51 | +<p class="note"><strong>Note</strong>: All steps below are implicitly preceded with, "If you haven't already..." You should skip any installation steps that have already contributed to your environment.</p> |
| 52 | + |
| 53 | +#### Install Ruby |
| 54 | + |
| 55 | +In Terminal window: |
| 56 | + |
| 57 | +1. Make and `cd` into a workspace directory. |
| 58 | + |
| 59 | + `$ mkdir workspace` |
| 60 | + |
| 61 | + `$ cd workspace` |
| 62 | + |
| 63 | +1. Follow the instructions at `http://brew.sh` to install brew / homebrew |
| 64 | + |
| 65 | + `$ /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"` |
| 66 | + |
| 67 | +1. Install your own (non-system) ruby. |
| 68 | + |
| 69 | + `$ brew install ruby` |
| 70 | + |
| 71 | +#### Set up Git |
| 72 | + |
| 73 | +1. Download and Install git by following the instructions at [git-scm.com](https://git-scm.com/download/). |
| 74 | + |
| 75 | +1. Install your own (non-system) bash-completion (optional). |
| 76 | + |
| 77 | + `$ brew install git bash-completion` |
| 78 | + |
| 79 | +1. If you don't already have one, generate a public/private RSA key pair, and save the key to your `~/.ssh` directory. |
| 80 | + ``` |
| 81 | + $ ssh-keygen |
| 82 | + Generating public/private rsa key pair. |
| 83 | + Enter file in which to save the key (/Users/pspinrad/.ssh/id_rsa): |
| 84 | + ``` |
| 85 | +
|
| 86 | +1. Get a [Github](http://github.com) account. |
| 87 | +
|
| 88 | +1. Add your RSA public key to your Github account / profile page. |
| 89 | +
|
| 90 | + `$ cat ~/.ssh/id_rsa.pub # copy and paste this into Github profile page as new key` |
| 91 | +
|
| 92 | +#### Get the Correct Ruby Version for Bookbinder: Ruby 2.3.0 |
| 93 | +
|
| 94 | +1. Install a Ruby manager such as chruby. |
| 95 | +
|
| 96 | + `$ brew install chruby` |
| 97 | +
|
| 98 | +1. Add your Ruby manager to your `~/.bashrc` by appending the following line: |
| 99 | +
|
| 100 | + `source /usr/local/opt/chruby/share/chruby/chruby.sh` |
| 101 | +
|
| 102 | +1. Install the `ruby-install` installer. |
| 103 | +
|
| 104 | + `$ brew install ruby-install` |
| 105 | +
|
| 106 | +1. Run `ruby-install` to install Ruby 2.3.0. |
| 107 | +
|
| 108 | + `$ ruby-install ruby 2.3.0` |
| 109 | +
|
| 110 | +1. Select the following Ruby version. |
| 111 | +
|
| 112 | + `chruby ruby-2.3.0` |
| 113 | +
|
| 114 | +#### Install Bookbinder |
| 115 | +
|
| 116 | +1. Install `bundler`. |
| 117 | +
|
| 118 | + `$ gem install bundler` |
| 119 | +
|
| 120 | +1. Install bookbinder (the `bookbindery` gem). |
| 121 | +
|
| 122 | + `$ gem install bookbindery` |
| 123 | +
|
| 124 | +#### Build the Docs Locally |
| 125 | +
|
| 126 | +1. Clone the docs template repo you will be building from. |
| 127 | +
|
| 128 | + `$ git clone [email protected]:pivotal-cf/docs-partners-template` |
| 129 | +
|
| 130 | +1. `cd` into the `book` subdirectory of the repo. |
| 131 | +
|
| 132 | + `$ cd docs-partners-template/docs-book` |
| 133 | +
|
| 134 | +1. Run `bundle install` to install all book dependencies. |
| 135 | +
|
| 136 | + `$ bundle install` |
| 137 | +
|
| 138 | +1. Run `bundle exec bookbinder watch` to build the book on your machine. |
| 139 | +
|
| 140 | + `$ bundle exec bookbinder watch` |
| 141 | + |
| 142 | +1. Browse to `localhost:4567` to view the book locally and "watch" any changes that you make to source `html.md.erb` files. As you make and save changes to the local source files for your site, you will see them in your browser after a slight delay. |
| 143 | +
|
| 144 | +1. After each session of writing or revising your docs source files, commit and push them to your github repo. |
| 145 | +
|
| 146 | +### About Subnavs of Published Tile Documentation |
| 147 | +
|
| 148 | +After your tile documentation has been published, the subnav used for the live documentation is contained in this directory: https://github.com/pivotal-cf/docs-book-partners/tree/master/master_middleman/source/subnavs |
| 149 | +
|
| 150 | +However, you should also continue to maintain the local subnav file so that the subnav looks correct when you or a Pivotal writer builds your documentation locally with bookbinder for review or editing. |
| 151 | +
|
| 152 | +To edit a subnav for your tile documentation, follow these steps: |
| 153 | +
|
| 154 | +1. Make a pull request against the subnav file in https://github.com/pivotal-cf/docs-book-partners/tree/master/master_middleman/source/subnavs |
| 155 | +
|
| 156 | +2. Make the same changes in the subnav file (in /docs-book/master_middleman/source/subnavs/ of your tile repo) and make a pull request for that change too. |
| 157 | +
|
| 158 | +Happy documenting! |
| 159 | +
|
| 160 | + |
| 161 | +
|
| 162 | + |
| 163 | +
|
0 commit comments