diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
index 722e3490..4d4ac58b 100644
--- a/.github/CODEOWNERS
+++ b/.github/CODEOWNERS
@@ -1,18 +1,12 @@
-#cpp code owners
-cpp/               @rapidsai/<repo>-cpp-codeowners
-
-#python code owners
-python/            @rapidsai/<repo>-python-codeowners
-python/dask_cudf/  @rapidsai/<repo>-dask-codeowners
 
 #cmake code owners
-**/CMakeLists.txt  @rapidsai/<repo>-cmake-codeowners
-**/cmake/          @rapidsai/<repo>-cmake-codeowners
+**/CMakeLists.txt     @rapidsai/rapids-cmake-codeowners
+*.cmake               @rapidsai/rapids-cmake-codeowners
 
 #build/ops code owners
-.github/           @rapidsai/ops-codeowners 
-ci/                @rapidsai/ops-codeowners
-conda/             @rapidsai/ops-codeowners
-**/Dockerfile      @rapidsai/ops-codeowners
-**/.dockerignore   @rapidsai/ops-codeowners
-docker/            @rapidsai/ops-codeowners
+.github/              @rapidsai/ops-codeowners
+ci/                   @rapidsai/ops-codeowners
+conda/                @rapidsai/ops-codeowners
+**/Dockerfile         @rapidsai/ops-codeowners
+**/.dockerignore      @rapidsai/ops-codeowners
+docker/               @rapidsai/ops-codeowners
diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
index 0045d314..8fa9c6c2 100644
--- a/.github/ISSUE_TEMPLATE/bug_report.md
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -1,6 +1,6 @@
 ---
 name: Bug report
-about: Create a bug report to help us improve ___PROJECT___
+about: Create a bug report to help us improve rapids-cmake
 title: "[BUG]"
 labels: "? - Needs Triage, bug"
 assignees: ''
@@ -18,9 +18,7 @@ A clear and concise description of what you expected to happen.
 
 **Environment details (please complete the following information):**
  - Environment location: [Bare-metal, Docker, Cloud(specify cloud provider)]
- - Method of ___PROJECT___ install: [conda, Docker, or from source]
-   - If method of install is [Docker], provide `docker pull` & `docker run` commands used
- 
+ - CMake version
 
 **Additional context**
-Add any other context about the problem here.
+For harder to track issue it can be helpful to attach the file generated from `cmake --system-information <file>` when executed from the same enviornment as the failure.
diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md
index 12a85e0d..94cd3bd9 100644
--- a/.github/ISSUE_TEMPLATE/feature_request.md
+++ b/.github/ISSUE_TEMPLATE/feature_request.md
@@ -1,6 +1,6 @@
 ---
 name: Feature request
-about: Suggest an idea for ___PROJECT___
+about: Suggest an idea for rapids-cmake
 title: "[FEA]"
 labels: "? - Needs Triage, feature request"
 assignees: ''
@@ -8,7 +8,7 @@ assignees: ''
 ---
 
 **Is your feature request related to a problem? Please describe.**
-A clear and concise description of what the problem is. Ex. I wish I could use ___PROJECT___ to do [...]
+A clear and concise description of what the problem is. Ex. I wish I could use rapids-cmake to do [...]
 
 **Describe the solution you'd like**
 A clear and concise description of what you want to happen.
diff --git a/.github/ISSUE_TEMPLATE/submit-question.md b/.github/ISSUE_TEMPLATE/submit-question.md
index 3714e22f..6d3bbb96 100644
--- a/.github/ISSUE_TEMPLATE/submit-question.md
+++ b/.github/ISSUE_TEMPLATE/submit-question.md
@@ -1,6 +1,6 @@
 ---
 name: Submit question
-about: Ask a general question about ___PROJECT___
+about: Ask a general question about rapids-cmake
 title: "[QST]"
 labels: "? - Needs Triage, question"
 assignees: ''
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 402e8bb6..c4c74432 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,28 +1,42 @@
 <!--
 
-Thank you for contributing to ___PROJECT___ :)
+Thank you for contributing to rapids-cmake :)
 
 Here are some guidelines to help the review process go smoothly.
 
 1. Please write a description in this text box of the changes that are being
    made.
 
-2. Please ensure that you have written units tests for the changes made/features
+2. Please ensure that you have followed the following guidelines for the changes made/features
    added.
 
+   - Each function should follow the `rapids_<component>_<file_name>` naming pattern
+   - Each function should go into a separate `.cmake` file in the approiate directory
+   - Each user facing `.cmake` file should have include guards (`include_guard(GLOBAL)`)
+   - Each user faceing `.cmake` file should be documented using the rst structure
+   - Each function first line should be `list(APPEND CMAKE_MESSAGE_CONTEXT "rapids.<component>.<function>")`
+
+   - A file should not modify any state simply by being included. State modification should
+     only occur inside functions unless absolutely neccessary due to restrctions of the CMake
+     language.
+      - Any files that do need to break this rule can't be part of `rapids-<component>.cmake`.
+
 3. If you are closing an issue please use one of the automatic closing words as
    noted here: https://help.github.com/articles/closing-issues-using-keywords/
 
 4. If your pull request is not ready for review but you want to make use of the
-   continuous integration testing facilities please label it with `[WIP]`.
+   continuous integration testing facilities please mark your pull request as Draft.
+   https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request#converting-a-pull-request-to-a-draft
 
 5. If your pull request is ready to be reviewed without requiring additional
-   work on top of it, then remove the `[WIP]` label (if present) and replace
-   it with `[REVIEW]`. If assistance is required to complete the functionality,
-   for example when the C/C++ code of a feature is complete but Python bindings
-   are still required, then add the label `[HELP-REQ]` so that others can triage
-   and assist. The additional changes then can be implemented on top of the
-   same PR. If the assistance is done by members of the rapidsAI team, then no
+   work on top of it, then remove it from "Draft" and make it "Ready for Review".
+   https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/changing-the-stage-of-a-pull-request#marking-a-pull-request-as-ready-for-review
+
+   If assistance is required to complete the functionality, for example when the
+   CMake code of a feature is complete but downstream testing is still required,
+   then add the label `help wanted` so that others can triage and assist.
+   The additional changes then can be implemented on top of the same PR.
+   If the assistance is done by members of the rapidsAI team, then no
    additional actions are required by the creator of the original PR for this,
    otherwise the original author of the PR needs to give permission to the
    person(s) assisting to commit to their personal fork of the project. If that
diff --git a/.gitignore b/.gitignore
new file mode 100644
index 00000000..a33518f0
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1,21 @@
+## Common
+.DS_Store
+
+## C++ test build directory
+build/
+example/build/
+
+## Eclipse IDE
+.project
+.cproject
+.settings
+
+## IntelliJ IDE
+.idea/
+.idea_modules/
+*.iml
+*.ipr
+*.iws
+
+## VSCode IDE
+.vscode
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 9f1ebb62..8e9466a2 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,4 +1,6 @@
-# ___PROJECT___ 0.0.0 (DD Mon YYYY)
+# rapids-cmake 0.20.0 (Date TBD)
+
+Please see https://github.com/rapidsai/rapids-cmake/releases/tag/v0.20.0a for the latest changes to this development branch.
 
 ## New Features
 
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 5cb2b5bf..1129d926 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,9 +1,9 @@
-# Contributing to ___PROJECT___
+# Contributing to rapids-cmake
 
-If you are interested in contributing to ___PROJECT___, your contributions will fall
+If you are interested in contributing to rapids-cmake, your contributions will fall
 into three categories:
 1. You want to report a bug, feature request, or documentation issue
-    - File an [issue](https://github.com/rapidsai/___PROJECT___/issues/new/choose)
+    - File an [issue](https://github.com/rapidsai/rapids-cmake/issues/new/choose)
     describing what you encountered or what you want to see changed.
     - The RAPIDS team will evaluate the issues and triage them, scheduling
     them for a release. If you believe the issue needs priority attention
@@ -20,15 +20,73 @@ into three categories:
 
 ## Code contributions
 
+While RAPIDS core provides commonly used scripts we know that they aren't universal and might need to be composed in different ways.
+
+This means that the code we are developing should be designed for composibility, and all side-effects
+or CMake behavior changes should be explicitly opt-in.
+
+So when writing new rapids-cmake features make sure to think about how users might want to opt-in, and
+provide the necessary function decomposition. For example lets look at an example of wanting to have an
+easy wrapper around creating libraries and setting properties.
+
+```
+[=[ BAD ]=]
+
+function(rapids_add_library target )
+  add_library(${target} ${ARGN})
+  set_target_properties(cudf
+      PROPERTIES
+                 CUDA_STANDARD                        17
+                 CUDA_STANDARD_REQUIRED               ON
+  )
+endfunction()
+
+rapids_add_library(example SHARED ...)
+
+
+[=[ GOOD ]=]
+
+function(rapids_cmake_setup_target target )
+  set_target_properties(${target}
+      PROPERTIES
+                 CUDA_STANDARD                        17
+                 CUDA_STANDARD_REQUIRED               ON
+  )
+endfunction()
+
+function(rapids_add_library target)
+  add_library(example ${ARGN})
+  rapids_cmake_setup_target( example )
+endfunction()
+
+rapids_add_library(example SHARED ...)
+
+```
+
+Here we can see that breaking out `rapids_cmake_setup_target` is important as it allows users
+that don't/can't use `rapids_add_library` to still opt-in to other features.
+
+
+Please ensure that when you are creating new features you follow the following guidelines:
+   - Each function should follow the `rapids_<component>_<file_name>` naming pattern
+   - Each function should go into a separate `.cmake` file in the approiate directory
+   - Each user facing `.cmake` file should have include guards (`include_guard(GLOBAL)`)
+   - Each user faceing `.cmake` file should be documented using the rst structure
+   - Each function first line should be `list(APPEND CMAKE_MESSAGE_CONTEXT "rapids.<component>.<function>")`
+   - A file should not modify any state simply by being included. State modification should
+     only occur inside functions unless absolutely neccessary due to restrctions of the CMake
+     language.
+        - Any files that do need to break this rule can't be part of `rapids-<component>.cmake`.
+
 ### Your first issue
 
-1. Read the project's [README.md](https://github.com/rapidsai/___PROJECT___/blob/main/README.md)
+1. Read the project's [README.md](https://github.com/rapidsai/rapids-cmake/blob/main/README.md)
     to learn how to setup the development environment
-2. Find an issue to work on. The best way is to look for the [good first issue](https://github.com/rapidsai/___PROJECT___/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22)
-    or [help wanted](https://github.com/rapidsai/___PROJECT___/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22) labels
+2. Find an issue to work on. The best way is to look for the [good first issue](https://github.com/rapidsai/rapids-cmake/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22)
+    or [help wanted](https://github.com/rapidsai/rapids-cmake/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted%22) labels
 3. Comment on the issue saying you are going to work on it
 4. Code! Make sure to update unit tests!
-5. When done, [create your pull request](https://github.com/rapidsai/___PROJECT___/compare)
+5. When done, [create your pull request](https://github.com/rapidsai/rapids-cmake/compare)
 6. Verify that CI passes all [status checks](https://help.github.com/articles/about-status-checks/). Fix if needed
 7. Wait for other developers to review your code and update code as needed
 8. Once reviewed and approved, a RAPIDS developer will merge your pull request
@@ -39,7 +97,7 @@ and ask for clarifications!
 ### Seasoned developers
 
 Once you have gotten your feet wet and are more comfortable with the code, you
-can look at the prioritized issues of our next release in our [project boards](https://github.com/rapidsai/___PROJECT___/projects).
+can look at the prioritized issues of our next release in our [project boards](https://github.com/rapidsai/rapids-cmake/projects).
 
 > **Pro Tip:** Always look at the release board with the highest number for
 issues to work on. This is where RAPIDS developers also focus their efforts.
diff --git a/LICENSE b/LICENSE
index 1a89b905..e832bc1a 100644
--- a/LICENSE
+++ b/LICENSE
@@ -186,7 +186,7 @@
       same "printed page" as the copyright notice for easier
       identification within third-party archives.
 
-   Copyright 2020 NVIDIA Corporation
+   Copyright 2021 NVIDIA Corporation
 
    Licensed under the Apache License, Version 2.0 (the "License");
    you may not use this file except in compliance with the License.
diff --git a/README.md b/README.md
index d79bf9a6..ff258ae1 100644
--- a/README.md
+++ b/README.md
@@ -1,76 +1,111 @@
-# RAPIDS Standard Repo Template
+# <div align="left"><img src="https://rapids.ai/assets/images/rapids_logo.png" width="90px"/>&nbsp;rapids-cmake</div>
 
-This is repo is the standard RAPIDS repo with the following items to make all RAPIDS repos consistent:
+**NOTE:** For the latest stable [README.md](https://github.com/rapidsai/rapids-cmake/blob/main/README.md) ensure you are on the `main` branch.
 
-- GitHub File Templates
-  - Issue templates
-  - PR template
-- GitHub Repo Templates
-  - Issue/PR labels
-  - Project tracking and release board templates
-- Files
-  - `CHANGELOG.md` skeleton
-  - `CONTRIBUTING.md` skeleton
-  - `LICENSE` file with Apache 2.0 License
-  - `README.md` skeleton
+## Overview
 
+This is a collection of CMake modules that are useful for all CUDA RAPIDS
+projects. By sharing the code in a single place it makes rolling out CMake
+fixes easier.
 
-## Usage for new RAPIDS repos
 
-1. Clone this repo
-2. Find/replace all in the clone of `___PROJECT___` and replace with the name of the new library
-3. Inspect files to make sure all replacements work and update text as needed
-4. Customize issue/PR templates to fit the repo
-5. Update `CHANGELOG.md` with next release version, see [changelog format](https://docs.rapids.ai/resources/changelog/) for more info
-6. Add developer documentation to the end of the `CONTRIBUTING.md` that is project specific and useful for developers contributing to the project
-    - The goal here is to keep the `README.md` light, so the development/debugging information should go in `CONTRIBUTING.md`
-7. Complete `README.md` with project description, quick start, install, and contribution information
-8. Remove everything above the RAPIDS logo below from the `README.md`
-9. Check `LICENSE` file is correct
-10. Change git origin to point to new repo and push
-11. Alert OPS team to copy labels and project boards to new repo
+## Installation
 
-## Usage for existing RAPIDS repos
+The `rapids-cmake` module is designed to be acquired via CMake's [Fetch
+Content](https://cmake.org/cmake/help/latest/module/FetchContent.html) into your project.
 
-1. Follow the steps 1-9 above, but add the files to your existing repo and merge
-2. Alert OPS team to copy labels and project boards to new repo
+```cmake
 
-## Useful docs to review
+cmake_minimum_required(...)
 
-- Issue triage & release planning
-  - [Issue triage process with GitHub projects](https://rapidsai.github.io/devdocs/docs/releases/triage/)
-  - [Release planning with GitHub projects](https://rapidsai.github.io/devdocs/docs/releases/planning/)
-- Code release process
-  - [Hotfix process](https://rapidsai.github.io/devdocs/docs/releases/hotfix/)
-  - [Release process](https://rapidsai.github.io/devdocs/docs/releases/process/)
-- Code contributions
-  - [Code contribution guide](https://rapidsai.github.io/devdocs/docs/contributing/code/)
-  - [Filing issues](https://rapidsai.github.io/devdocs/docs/contributing/issues/)
-  - [Filing PRs](https://rapidsai.github.io/devdocs/docs/contributing/prs/)
-  - [Code of conduct](https://rapidsai.github.io/devdocs/docs/resources/conduct/)
-- Development process
-  - [Git branching and merging methodology](https://rapidsai.github.io/devdocs/docs/resources/git/)
-  - [Versions and tags](https://rapidsai.github.io/devdocs/docs/resources/versions/)
-  - [Changelog format](https://rapidsai.github.io/devdocs/docs/resources/changelog/)
-  - [Style guide](https://rapidsai.github.io/devdocs/docs/resources/style/)
-  - [Labels](https://rapidsai.github.io/devdocs/docs/maintainers/labels/)
+include(FetchContent)
+FetchContent_Declare(
+  rapids-cmake
+  GIT_REPOSITORY https://github.com/rapidsai/rapids-cmake.git
+  GIT_TAG        branch-<VERSION_MAJOR>.<VERSION_MINOR>
+)
+FetchContent_MakeAvailable(rapids-cmake)
+include(rapids-cmake)
+include(rapids-cpm)
+include(rapids-cuda)
+include(rapids-export)
+include(rapids-find)
 
----
+project(....)
+```
 
-# <div align="left"><img src="https://rapids.ai/assets/images/rapids_logo.png" width="90px"/>&nbsp;___PROJECT___</div>
+Note that we recommend you install `rapids-cmake` into the root `CMakeLists.txt` of
+your project before the first `project` call. This allows us to offer features such as
+`rapids_cuda_architectures()`
 
-The [RAPIDS](https://rapids.ai) ___PROJECT___ ..._insert project description_...
+## Usage
 
-**NOTE:** For the latest stable [README.md](https://github.com/rapidsai/___PROJECT___/blob/main/README.md) ensure you are on the `main` branch.
+`rapids-cmake` provides a collection of useful CMake settings that any RAPIDS project may use.
+While they maybe common, we know that they aren't universal and might need to be composed in
+different ways.
 
-## Quick Start
+To use function provided by `rapids-cmake` projects have two options:
+- Call `include(rapids-<component>)` as that imports all commonly used functions for that component
+- Load each function independently via `include(${rapids-cmake-dir}/<component>/<function_name>.cmake)`
 
-## Install ___PROJECT___
 
-### Conda
+## Components
 
-### Docker
+Complete online documentation for all components is currently under development. Currently
+you can read the existing documentation by looking at the inline restructure text of
+each cmake file.
 
-## Contributing Guide
+### cmake
+The `rapids-cmake` module contains helpful general CMake functionality
 
-Review the [CONTRIBUTING.md](https://github.com/rapidsai/___PROJECT___/blob/main/CONTRIBUTING.md) file for information on how to contribute code and issues to the project.
+- `rapids_cmake_build_type( )` handles initialization of `CMAKE_BUILD_TYPE`
+- `rapids_cmake_support_conda_env( target [MODIFY_PREFIX_PATH])` Establish a target that holds the CONDA enviornment
+  include and link directories.
+
+### cpm
+
+The `rapids-cpm` module contains CPM functionality to allow projects to acquire dependencies consistently.
+For consistentcy All targets brought in via `rapids-cpm` are GLOBAL targets.
+
+- `raipds_cpm_init()` handles initialization of the CPM module.
+- `raipds_cpm_find(<project> name BUILD_EXPORT_SET <name> INSTALL_EXPORT_SET <name>)` Will search for a module and fall back to installing via CPM. Offers support to track dependencies for easy package exporting
+
+### cuda
+
+The `rapids-cuda` module contains core functionality to allow projects to build CUDA code robustly.
+The most commonly used function are:
+
+- `rapids_cuda_init_architectures(<project_name>)` handles initialization of `CMAKE_CUDA_ARCHITECTURE`. MUST BE CALLED BEFORE `PROJECT()`
+- `rapids_cuda_init_runtime(<mode>)` handles initialization of `CMAKE_CUDA_RUNTIME_LIBRARY`.
+
+### export
+
+The `rapids-export` module contains core functionality to allow projects to easily record and write out
+build and install dependencies, that come from `find_package` or `cpm`
+
+- `rapids_export_package(<type> <package_name> <export_set>)` Explicitly record a `find_package` call for `install`
+  or `build` exporting. Used by `rapids_export` to generate a correct config module.
+- `rapids_export_cpm(<type> <package_name> <export_set>)` Explicitly record a `cpm` call for `install` or `build`
+  exporting. Used by `rapids_export` to generate a correct config module.
+- `rapids_export_find_package_file(<type> <file_path> <export_set>)` Explicitly record a custom `Find<Pkg>.cmake`
+  file that is required for the `install` or `build` export set. Used by `rapids_export` to correctly install
+  custom FindModules.
+- `rapids_export(<type> <project> EXPORT_SET <name>)` write out all the require components of a projects config
+  module so that the `install` or `build` directory can be imported via `find_package`. See `rapids_export`
+  documentation for full documentation
+
+
+### find
+
+The `rapids-find` module contains core functionality to allow projects to easily generate FindModule or export
+`find_package` calls:
+
+The most commonly used function are:
+
+- `rapids_find_package(<project_name> BUILD_EXPORT_SET <name> INSTALL_EXPORT_SET <name> )` Combines `find_package` and support to track dependencies for easy package exporting
+- `rapids_generate_module(<PackageName> HEADER_NAMES <paths...> LIBRARY_NAMES <names...> )` Generate a FindModule for the given package. Allows association to export sets so the generated FindModule can be shipped with the project
+
+
+## Contributing
+
+Review the [CONTRIBUTING.md](https://github.com/rapidsai/rapids-cmake/blob/main/CONTRIBUTING.md) file for information on how to contribute code and issues to the project.