Update workflow documentation in contributing page

CONTRIBUTING.md

@@ -21,11 +21,38 @@ New features and enhancements are also managed via [issues](https://github.com/1
 Pull requests represent a proposed solution to a specified problem.  They should always reference an issue that describes the problem and contains discussion about the problem itself.  Discussion on pull requests should be limited to the pull request itself, i.e. code review.
 
 For more on how 10up writes and manages code, check out our [10up Engineering Best Practices](https://10up.github.io/Engineering-Best-Practices/).
-
 ## Workflow
 
-The `develop` branch is the development branch which means it contains the next version to be released. `trunk` contains the latest released version.  Always work on the `develop` branch and open up PRs against `develop`.
-
-## Release instructions
+The `develop` branch is the development branch which means it contains the next version to be released. `trunk` contains the latest released version.
+
+### Feature branches
+
+1. From the `develop` branch create a new feature branch with the following naming structure: `feature|fix/[github-issue-number]--[branch-description]` (i.e. `feature/10--accordion-component-build`).
+2. Do work on the `feature` or `fix` branch. When finished, submit a pull request to merge your work back into the `develop` branch. In the PR, link to the issue (see the sidebar options on the right).
+3. If there are conflicts between your branch and the code that now exists on `develop` branch, merge `develop` into your branch to reintegrate new changes and resolve any conflicts.
+4. Assign a minimum on 1 reviewer to the pull request. At least one engineer must review all PRs.
+5. Once PR is approved and all tests pass, the creator of the PR performs the merge into `develop`.
+6. Pull down the `develop` branch locally and test updates to verify everything is working correctly.
+
+### Updating Packages (npm)
+1. Once a package is ready to publish to npm, a `maintainer/owner` creates a PR against `trunk` from `develop` or a `release` branch.
+2. Manually update the package version in their respective `package.json` file to the next desired version and upate the `CHANGELOG.md` within the package directory.
+3. Within the package, run `npm publish --access public` to release the package to npm.
+4. Verify npm packages have been updated (i.e. [10up Accordion Component](https://www.npmjs.com/package/@10up/component-accordion) on NPM).
+5. Merge the PR into `trunk`.
+6. Merge `trunk` back into `develop` to complete the package update.
+
+### Release instructions
+_NOTE: Release is this instance is referring to the repository version history - not the npm package(s)_
+
+1. Before starting a release, verify all pertinent npm packages have been updated: If any updated components (`/packages`) needing to be relased to npm exist, see [Updating Packages](#user-content-updating-packages) above.
+2. Create a new issue in github to track the release. Name the release version in the github issue. Refer to [releases](https://github.com/10up/component-library/releases) for the latest release.
+2. Create a branch from `develop` named `release/[github-issue-number]-[release-number]`.
+3. With the release branch checked out locally, in the `/docs` directory run `bundle install` and `bundle exec jekyll serve`. Verify everything is working correctly.
+4. Create a pull request in github to merge the `release/[github-issue-number]-[release-number]` branch into `trunk`. Assign one reviewer to the PR. Add "Component Libarary Release [release number]" and "CHANGELOG" updates to the description.
+5. Once branch is approved, all tests pass, and merged on github, switch to the `trunk` branch locally and pull the changes you just merged.
+6. Verify changes are working correctly locally and, once the deploy is complete, on [Baseline](https://baseline.10up.com/components).
+7. Create a new tag in the repository matching the release number (i.e. `git tag 0.1.3`).
+8. Run `git push --tags` to push the newly created tag to the git repository.
+9. Merge `trunk` back into `develop` to complete the cycle.
 
-TBD