Added all labels.

Author: DariuszDepta

.vitepress/theme/components/ChapterLabel.vue

@@ -2,7 +2,7 @@
 defineProps({
   label: {
     type: String,
-    default: 'CosmWasm Docs',
+    default: 'chapter',
   },
   bgColor: {
     type: String,
@@ -12,11 +12,11 @@ defineProps({
 </script>
 
 <template>
-  <span class="chapter-label" :style="{backgroundColor: bgColor}">{{ label }}</span>
+  <span class="label" :style="{backgroundColor: bgColor}">{{ label }}</span>
 </template>
 
 <style scoped>
-.chapter-label {
+.label {
   display: inline-block;
   color: white;
   border: none;

.vitepress/theme/components/SectionLabel.vue

@@ -0,0 +1,38 @@
+<script setup>
+defineProps({
+  chapter: {
+    type: String,
+    default: 'chapter',
+  },
+  section: {
+    type: String,
+    default: 'section',
+  },
+  bgChapter: {
+    type: String,
+    default: 'var(--bg-medium-blue)'
+  },
+  bgSection: {
+    type: String,
+    default: 'var(--bg-persian-pink)'
+  }
+})
+</script>
+
+<template>
+  <span class="label" :style="{backgroundColor: bgChapter}">{{ chapter }}</span>
+  <span class="label" :style="{backgroundColor: bgSection}">{{ section }}</span>
+</template>
+
+<style scoped>
+.label {
+  display: inline-block;
+  color: white;
+  border: none;
+  padding: 2px 10px 2px 8px;
+  border-radius: 12px;
+  user-select: none;
+  margin: 0 4px 20px 0;
+  font-size: 0.9em;
+}
+</style>

.vitepress/theme/index.ts

@@ -1,11 +1,13 @@
 import type { Theme } from 'vitepress'
 import DefaultTheme from 'vitepress/theme'
 import ChapterLabel from './components/ChapterLabel.vue'
+import SectionLabel from './components/SectionLabel.vue'
 import './style.css'
 
 export default {
     extends: DefaultTheme,
     enhanceApp({ app }) {
         app.component('ChapterLabel', ChapterLabel)
+        app.component('SectionLabel', SectionLabel)
     }
 } satisfies Theme

pages/guide/cosmwasm-core/architecture/actor-model.md

@@ -1,6 +1,8 @@
 [reentrancy issues]: https://ethereum.org/en/developers/docs/smart-contracts/security/#reentrancy
 [enum dispatch]: ../conventions/enum-dispatch
 [CEI pattern (Checks, Effects, Interactions)]: https://fravoll.github.io/solidity-patterns/checks_effects_interactions.html
+
+<SectionLabel chapter="core" section="architecture"></SectionLabel>
 
 # Actor model
 

pages/guide/cosmwasm-core/architecture/architecture.md

@@ -1,3 +1,5 @@
+<SectionLabel chapter="core" section="architecture"></SectionLabel>
+
 # Architecture
 
 (TBD)

pages/guide/cosmwasm-core/architecture/gas.md

@@ -4,6 +4,8 @@
 [inspired by NEAR]: https://docs.near.org/concepts/protocol/gas
 [#1120]: https://github.com/CosmWasm/cosmwasm/pull/1120
 
+<SectionLabel chapter="core" section="architecture"></SectionLabel>
+
 # Gas
 
 Gas is a way to measure computational expense of a smart contract execution, including CPU time and

pages/guide/cosmwasm-core/architecture/transactions.md

@@ -1,3 +1,5 @@
+<SectionLabel chapter="core" section="architecture"></SectionLabel>
+
 # Transactions
 
 Every contract invocation is wrapped into a transaction. If you know about transactions in SQL

pages/guide/cosmwasm-core/conventions/conventions.md

@@ -1,3 +1,5 @@
+<SectionLabel chapter="core" section="conventions"></SectionLabel>
+
 # Conventions
 
 Just like with any platform, there are certain conventions on how to write contracts for CosmWasm.

pages/guide/cosmwasm-core/conventions/enum-dispatch.md

@@ -1,3 +1,5 @@
+<SectionLabel chapter="core" section="conventions"></SectionLabel>
+
 # Enum dispatch
 
 In most production contracts you want to handle multiple message types in a single contract.

pages/guide/cosmwasm-core/conventions/library-feature.md

@@ -1,6 +1,8 @@
 [`cw-plus` contracts]: https://github.com/CosmWasm/cw-plus
 [`cw4-stake` contract]: https://github.com/CosmWasm/cw-plus/blob/48bec694521655d5b3e688c51e4185f740ea4640/contracts/cw4-stake/Cargo.toml#L22-L24
 
+<SectionLabel chapter="core" section="conventions"></SectionLabel>
+
 # Library feature
 
 In the ecosystem, there is the convention to gate the entrypoints of your contract behind a