configure callouts

Author: vkryachko

contributor-docs/_config.yml

@@ -49,6 +49,23 @@ mermaid:
 # Enable or disable heading anchors
 heading_anchors: true
 
+callouts_level: quiet
+callouts:
+  highlight:
+    color: yellow
+  important:
+    title: Important
+    color: blue
+  new:
+    title: New
+    color: green
+  note:
+    title: Note
+    color: purple
+  warning:
+    title: Warning
+    color: red
+
 # Back to top link
 back_to_top: true
 back_to_top_text: "Back to top"

contributor-docs/components/dependencies.md

@@ -100,14 +100,14 @@ To declare a required dependency use the following in your `ComponentRegistrar`:
 The provider will return `null` if the dependency is not present in the app.
 
 {: .warning }
-> When the app uses [Play's dynamic feature delivery](https://developer.android.com/guide/playcore/feature-delivery),
-> `provider.get()` can return your dependency when it becomes available, so be prepared for that.
-> And don't store references to the result of `provider.get()` calls.
+When the app uses [Play's dynamic feature delivery](https://developer.android.com/guide/playcore/feature-delivery),
+`provider.get()` can return your dependency when it becomes available, so be prepared for that.
+And don't store references to the result of `provider.get()` calls.
 
 See [Dynamic Module Support]({{ site.baseurl }}{% link components/dynamic_modules.md %}) for details
 
 {: .warning }
-> See Deferred dependencies if you your dependency has a callback based apis
+See Deferred dependencies if you your dependency has a callback based apis
 
 ## Deferred Dependencies
 
@@ -169,10 +169,10 @@ To consume such a set the interested `Component` needs to declare a special kind
   set will get initialized.
 
 {: .warning }
-> Similar to optional `Provider` dependencies, where an optional dependency can become available at runtime due to
-> [Play's dynamic feature delivery](https://developer.android.com/guide/playcore/feature-delivery),
-> `Set` dependencies can change at runtime by new elements getting added to the set.
-> So make sure to hold on to the original `Set` to be able to observe new values in it as they are added.
+Similar to optional `Provider` dependencies, where an optional dependency can become available at runtime due to
+[Play's dynamic feature delivery](https://developer.android.com/guide/playcore/feature-delivery),
+`Set` dependencies can change at runtime by new elements getting added to the set.
+So make sure to hold on to the original `Set` to be able to observe new values in it as they are added.
 
 Example:
 

contributor-docs/components/executors.md

@@ -154,7 +154,7 @@ Qualified<CoroutineDispatcher> dispatcher = qualified(Blocking::class.java, Coro
 #### Direct executor
 
 {: .warning }
-> Prefer `@Lightweight` instead of using direct executor as it could cause dead locks and stack overflows.
+Prefer `@Lightweight` instead of using direct executor as it could cause dead locks and stack overflows.
 
 For any trivial tasks that don't need to run asynchronously
 

contributor-docs/onboarding/new_sdk.md

@@ -41,9 +41,9 @@ the library will have once released. e.g. `firebase-common` directory
 hosts code for the `com.google.firebase:firebase-common` SDK.
 
 {: .warning }
-> Note that the build file name for any given SDK is not `build.gradle` or `build.gradle.kts`
-> but rather mirrors the name of the sdk, e.g.
-> `firebase-common/firebase-common.gradle` or `firebase-common/firebase-common.gradle.kts`.
+Note that the build file name for any given SDK is not `build.gradle` or `build.gradle.kts`
+but rather mirrors the name of the sdk, e.g.
+`firebase-common/firebase-common.gradle` or `firebase-common/firebase-common.gradle.kts`.
 
 All of the core Gradle build logic lives in `buildSrc` and is used by all
 SDKs.