diff --git a/daprdocs/assets/scss/_sidebar-tree.scss b/daprdocs/assets/scss/_sidebar-tree.scss index 025114590..cd8e4f69d 100644 --- a/daprdocs/assets/scss/_sidebar-tree.scss +++ b/daprdocs/assets/scss/_sidebar-tree.scss @@ -30,8 +30,8 @@ } @include media-breakpoint-up(md) { - & > ul { - padding-left: .5rem; + & .ul-1 ul { + padding-left: 1.5em; } } @@ -85,7 +85,22 @@ & > .td-sidebar-nav__section { padding-top: .5rem; - padding-left: 0rem; + padding-left: 1.5rem; + } + + li i { // Layout of icons + padding-right: 0.5em; + &:before{ + display: inline-block; + text-align: center; + min-width: 1em; + } + } + + .td-sidebar-link.tree-root{ + font-weight: $font-weight-bold; + color: $td-sidebar-tree-root-color; + margin-bottom: 1rem; } } @@ -93,8 +108,7 @@ @include media-breakpoint-up(md) { padding-top: 4rem; background-color: $td-sidebar-bg-color; - padding-right: .5rem; - padding-left: .5rem; + padding-right: 1rem; border-right: 1px solid $td-sidebar-border-color; } @@ -144,4 +158,4 @@ #content-desktop {display: none;} #content-mobile {display: block;} } -} \ No newline at end of file +} diff --git a/daprdocs/content/en/developing-applications/building-blocks/configuration/app-configuration-overview.md b/daprdocs/content/en/developing-applications/building-blocks/configuration/app-configuration-overview.md index a368c615b..5fd34c9bb 100644 --- a/daprdocs/content/en/developing-applications/building-blocks/configuration/app-configuration-overview.md +++ b/daprdocs/content/en/developing-applications/building-blocks/configuration/app-configuration-overview.md @@ -8,9 +8,9 @@ description: "Use Dapr to get and watch application configuration" Consuming application configuration is a common task when writing applications and frequently configuration stores are used to manage this configuration data. A configuration item is often dynamic in nature and is tightly coupled to the needs of the application that consumes it. For example, common uses for application configuration include names of secrets that need to be retrieved, different identifiers, partition or consumer IDs, names of databased to connect to etc. These configuration items are typically stored as key-value items in a database. -Dapr provides a [State Management API]({{}})) that is based on key-value stores. However, application configuration can be changed by either developers or operators at runtime and the developer needs to be notified of these changes in order to take the required action and load the new configuration. Also the configuration data may want to be read only. Dapr's Configuration API allows developers to consume configuration items that are returned as key/value pair and subscribe to changes whenever a configuration item changes. +Dapr provides a [State Management API]({{}}) that is based on key-value stores. However, application configuration can be changed by either developers or operators at runtime and the developer needs to be notified of these changes in order to take the required action and load the new configuration. Also the configuration data may want to be read only. Dapr's Configuration API allows developers to consume configuration items that are returned as key/value pair and subscribe to changes whenever a configuration item changes. -*This API is currently in `Alpha state` and only available on gRPC. An HTTP1.1 supported version with this URL `/v1.0/configuration` will be available before the API becomes stable. * +*This API is currently in `Alpha state` and only available on gRPC. An HTTP1.1 supported version with this URL `/v1.0/configuration` will be available before the API becomes stable.* ## References diff --git a/daprdocs/content/en/developing-applications/building-blocks/pubsub/pubsub-raw.md b/daprdocs/content/en/developing-applications/building-blocks/pubsub/pubsub-raw.md index 859ac8470..ed73fe900 100644 --- a/daprdocs/content/en/developing-applications/building-blocks/pubsub/pubsub-raw.md +++ b/daprdocs/content/en/developing-applications/building-blocks/pubsub/pubsub-raw.md @@ -50,9 +50,7 @@ with DaprClient() as d: pubsub_name='pubsub', topic='TOPIC_A', data=json.dumps(req_data), - metadata=( - ('rawPayload', 'true') - ) + publish_metadata={'rawPayload': 'true'} ) # Print the request print(req_data, flush=True) diff --git a/daprdocs/content/en/operations/components/component-scopes.md b/daprdocs/content/en/operations/components/component-scopes.md index 29834b032..e2de36179 100644 --- a/daprdocs/content/en/operations/components/component-scopes.md +++ b/daprdocs/content/en/operations/components/component-scopes.md @@ -91,7 +91,7 @@ curl -i -d '{ "message": "hello" }' \ ``` ## Using namespaces with pub/sub -Read [Pub/Sub and namespaces]({{< ref "component-scopes.md" >}}) for more information on scoping components. +Read [Configure Pub/Sub components with multiple namespaces]({{< ref "pubsub-namespaces.md" >}}) for more information on using namespaces with pub/sub. ## Application access to components with scopes @@ -127,4 +127,4 @@ scopes: - [Configure Pub/Sub components with multiple namespaces]({{< ref "pubsub-namespaces.md" >}}) - [Use secret scoping]({{< ref "secrets-scopes.md" >}}) -- [Limit the secrets that can be read from secret stores]({{< ref "secret-scope.md" >}}) \ No newline at end of file +- [Limit the secrets that can be read from secret stores]({{< ref "secret-scope.md" >}}) diff --git a/daprdocs/layouts/partials/footer.html b/daprdocs/layouts/partials/footer.html index ea35b9dd9..e159a171d 100644 --- a/daprdocs/layouts/partials/footer.html +++ b/daprdocs/layouts/partials/footer.html @@ -1,15 +1,15 @@ {{ $links := .Site.Params.links }}