[WIP] Ftr: configuration store docs

daprdocs/content/en/concepts/building-blocks-concept.md

@@ -27,3 +27,4 @@ The following are the building blocks provided by Dapr:
 | [**Actors**]({{<ref "actors-overview.md">}}) | `/v1.0/actors` |  An actor is an isolated, independent unit of compute and state with single-threaded execution. Dapr provides an actor implementation based on the Virtual Actor pattern which provides a single-threaded programming model and where actors are garbage collected when not in use.
 | [**Observability**]({{<ref "observability-concept.md">}}) | `N/A` |  Dapr system components and runtime emit metrics, logs, and traces to debug, operate and monitor Dapr system services, components and user applications.
 | [**Secrets**]({{<ref "secrets-overview.md">}}) | `/v1.0/secrets` | Dapr offers a secrets building block API and integrates with secret stores such as Azure Key Vault and Kubernetes to store the secrets. Service code can call the secrets API to retrieve secrets out of the Dapr supported secret stores.
+| [**Configuration**]({{<ref "configuration-store-overview.md">}}) | `/v1.0/configuration` |  Dapr Configuration Components

daprdocs/content/en/developing-applications/building-blocks/configuration-store/_index.md

@@ -0,0 +1,7 @@
+---
+type: docs
+title: "Configuration"
+linkTitle: "Configuration"
+weight: 50
+description: Application Configuration building block
+---

daprdocs/content/en/developing-applications/building-blocks/configuration-store/configuration-store-overview.md

@@ -0,0 +1,20 @@
+---
+type: docs
+title: "Configuration overview"
+linkTitle: "Overview"
+weight: 10
+description: Overview of the configuration building block
+aliases:
+---
+
+## Introduction
+Using configuration, you can get your application configuration using dapr's API. The configuration can be stored in configuration store you like. This building block's  benefit is to let you to get application configuration easily from any mature solution, like redis, nacos, etc. We call each implement of configuration is a kind of state store. In the API, the statestore parameter is also used to distinguish the configuration stores selected by the user
+
+## Get Configuration
+
+Get configuration operation can be used to get configuraiton content from target state store with target key. The user can start the application and load it from the required State Store with an API call.
+
+## Subscribe Configuration
+
+Subscribe configuration can be used to subscribe configuration in target state store with target key. It would first get exist data and subscribe the changes of target configuration. 
+