docs: Update version references (#1470)

Author: castastrophe

docs/content/develop/step-5.md

@@ -39,8 +39,8 @@ tags = [ "develop" ]
     * See the diffs of what was merged between now & the last release
     * Or look at PR merged list with "last-updated" sort order: \
 [https://github.com/patternfly/patternfly-elements/pulls?q=is%3Apr+is%3Aclosed+sort%3Aupdated-desc](https://github.com/patternfly/patternfly-elements/pulls?q=is%3Apr+is%3Aclosed+sort%3Aupdated-desc)
-8. Update the file `CHANGELOG-prerelease.md` and save
-9. <span style="text-decoration:underline;">Search</span> for release tag string in /docs/layout directory i.e. "prerelease.19" and update to release number \
+8. Update the file `CHANGELOG-1.x.md` and save
+9. <span style="text-decoration:underline;">Search</span> for release tag string in /docs/layout directory i.e. "1.3.0" and update to release number \
 
 <img src="/version_storybook.png" width="450"/>
 
@@ -59,15 +59,15 @@ This script will do the following:
 1. Create release branch
 2. Create compiled assets and commit them
 3. Uses [lerna](https://lerna.js.org) to guess at what the next release will be
-    1. **Choose "custom prerelease" (for now)**
+    1. **Choose appropriate version bump (minor, patch)**
     2. It bumps the version numbers inside the package.json files in the components (currently all components are bumped, will fix)
 4. Pushes the branch
 5. Pushes independent tags for each component and pushes to NPM
 6. Remove compiled assets
 7. Returns you to the master branch
 
 
-### V. Github Updates
+### V. GitHub Updates
 
 1. Create a PR
 2. Get someone to review 
@@ -95,7 +95,7 @@ This script will do the following:
 ```
 Greetings! 
 
-There is a new release tag for PatternFly Elements,  [v1.0.0-prerelease.36](https://github.com/patternfly/patternfly-elements/releases/tag/v1.0.0-prerelease.36), which includes
+There is a new release tag for PatternFly Elements,  [v1.3.2](https://github.com/patternfly/patternfly-elements/releases/tag/v1.3.2), which includes
 
 
 
@@ -122,11 +122,12 @@ To roll a new release, use the following steps:
 1. Start in the root directory of the patternfly-elements project.
 2. Check out the master branch and pull down the latest: 
     - `git reset --hard && git clean -df && git checkout master && git fetch origin && git pull`
-3. To have lerna bump the verions, run: `npm run lerna version -- --no-git-tag-version --no-push --preid prerelease`.
+3. To have lerna bump the verions, run: `npm run lerna version -- --no-git-tag-version --no-push`.
     - Choose the appropriate version bump type for the release you're publishing:
-        - if bumping a prerelease version (example: from 1.0.0-prerelease.2 to 1.0.0-prerelease.3), choose *Custom Prerelease*
-4. Assign that version to this variable for use below: `$NEW_VERSION="1.0.0-prerelease.3"`.
-5. Create a new branch: `git checkout -b release/$NEW_VERSION` (example: release/1.0.0-prerelease.3).
+        - if bumping a patch version (example: from 1.3.2 to 1.3.3)
+        - if bumping a minor version (example: from 1.3.2 to 1.4.0)
+4. Assign that version to this variable for use below: `$NEW_VERSION="1.3.0"`.
+5. Create a new branch: `git checkout -b release/$NEW_VERSION` (example: release/1.3.0).
 5. Run a fresh install, build all the assets, and then force add those assets for the tag release:
     - `npm install && npm run build && git add elements/*/*.{js,map,css} -f`
 6. Commit the updates: `git commit -am "$NEW_VERSION"`

docs/content/getting-started/_index.md

@@ -30,8 +30,8 @@ $ npm install --save @patternfly/pfe-cta
 This will install not only the pfe-card and pfe-cta, but also the base element, "pfelement", and will save it to your package-lock.json. Depending on which browsers you support, you may also need to load the [custom-elements](https://github.com/webcomponents/polyfills/tree/master/packages/custom-elements) and webcomponentsjs [polyfills](https://www.webcomponents.org/polyfills).
 
 ```bash
-"@patternfly/pfe-card": "1.0.0-prerelease.42",
-"@patternfly/pfe-cta": "1.0.0-prerelease.42",
+"@patternfly/pfe-card": "1.3.2",
+"@patternfly/pfe-cta": "1.3.2",
 "@webcomponents/custom-elements": "^1.2.1",
 "@webcomponents/webcomponentsjs": "^2.2.10",
 ```

docs/content/theme/_index.md

@@ -53,7 +53,7 @@ Any other component making use of that same `ui-accent` value will inherit your
 
 Each component comes equipped to adjust its colors depending on the context inside which it exists. For example, should you need to put a default CTA (which is blue) on a dark blue card, the CTA will need to adapt so that the text remain readable. The card component therefore needs to pass down a `context` to the CTA, which it does using the `on="dark"` attribute.  This is programmatically applied by JavaScript that runs from the base class, `PFElement` (you don't have to do a thing!).  To manually override a component's context, you can do this by setting the `context="dark"` attribute.
 
-<pfe-card color="darkest">
+<pfe-card color="darkest" style="padding: 5px 10px; max-width: fit-content; margin-top: 10px;">
     <pfe-cta>
         <a href="#">Default</a>
 	</pfe-cta>

docs/layouts/_default/list.html

@@ -8,7 +8,7 @@
   <!-- Convert to a partial -->
   <nav id="main-toc">
     <section class="inner-toc">
-      <span class="label big" style="margin-bottom: 1.5rem;">Version 1.0.0-prerelease.56</span>
+      <span class="label big" style="margin-bottom: 1.5rem;">Version 1.3.2</span>
 
       <h3><a href="/getting-started">Getting Started</a></h3>
       <ul>

docs/layouts/_default/single.html

@@ -8,7 +8,7 @@
   <!-- Convert to a partial -->
   <nav id="main-toc">
     <section class="inner-toc">
-      <span class="label big" style="margin-bottom: 1.5rem;">Version 1.0.0-prerelease.56</span>
+      <span class="label big" style="margin-bottom: 1.5rem;">Version 1.3.2</span>
 
       <h3><a href="/getting-started">Getting Started</a></h3>
       <ul>

docs/layouts/partials/header.html

@@ -40,7 +40,7 @@
 <!-- Convert to a partial -->
 <nav id="mobile-toc" class="hide">
   <section class="inner-toc">
-    <span class="label big" style="margin-bottom: 1.5rem;">Version 1.0.0-prerelease.56</span>
+    <span class="label big" style="margin-bottom: 1.5rem;">Version 1.3.2</span>
 
     <h3><a href="/getting-started">Getting Started</a></h3>
     <ul>