Added conventions chapter.

Author: DariuszDepta

.vitepress/config.mts

@@ -16,25 +16,8 @@ export default withMermaid({
                 items: [
                     {text: 'Introduction', link: '/guide/cosmwasm-core/introduction'},
                     {text: 'Installation', link: '/guide/cosmwasm-core/installation'},
-                    {
-                        text: 'Entrypoints', link: '/guide/cosmwasm-core/entrypoints/entrypoints',
-                        items: [
-                            {text: 'Instantiate', link: '/guide/cosmwasm-core/entrypoints/instantiate'},
-                            {text: 'Execute', link: '/guide/cosmwasm-core/entrypoints/execute'},
-                            {text: 'Query', link: '/guide/cosmwasm-core/entrypoints/query'},
-                            {text: 'Migrate', link: '/guide/cosmwasm-core/entrypoints/migrate'},
-                            {text: 'Sudo', link: '/guide/cosmwasm-core/entrypoints/sudo'},
-                            {text: 'Reply', link: '/guide/cosmwasm-core/entrypoints/reply'},
-                        ]
-                    },
-                    {
-                        text: 'Architecture', link: '/guide/cosmwasm-core/architecture/architecture',
-                        items: [
-                            {text: 'Actor model', link: '/guide/cosmwasm-core/architecture/actor-model'},
-                            {text: 'Gas', link: '/guide/cosmwasm-core/architecture/gas'},
-                            {text: 'Transactions', link: '/guide/cosmwasm-core/architecture/transactions'},
-                        ]
-                    }
+                    {text: 'Entrypoints', link: '/guide/cosmwasm-core/entrypoints/entrypoints'},
+                    {text: 'Architecture', link: '/guide/cosmwasm-core/architecture/architecture'}
                 ]
             },
         ],
@@ -64,6 +47,13 @@ export default withMermaid({
                             {text: 'Transactions', link: '/guide/cosmwasm-core/architecture/transactions'},
                         ]
                     },
+                    {
+                        text: 'Conventions', collapsed: true, link: '/guide/cosmwasm-core/conventions/conventions',
+                        items: [
+                            {text: 'Library feature', link: '/guide/cosmwasm-core/conventions/library-feature'},
+                            {text: 'Enum dispatch', link: '/guide/cosmwasm-core/conventions/enum-dispatch'},
+                        ]
+                    },
                 ]
             },
         ],

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

@@ -0,0 +1,8 @@
+# Conventions
+
+Just like with any platform, there are certain conventions on how to write contracts for CosmWasm.
+This section will give you a quick overview of the different conventions set in the CosmWasm
+ecosystem.
+
+These conventions are about recommended programming patterns, and recommendations on how you should
+structure your contract to make it fit into the existing CosmWasm ecosystem better.

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

@@ -0,0 +1,38 @@
+# Enum dispatch
+
+In most production contracts you want to handle multiple message types in a single contract.
+Unfortunately you can't create multiple endpoints of the same type in a single contract, so you need
+to dispatch based on the message type.
+
+The most common way to do this is to use an enum to represent the different message types and then
+match on that enum in the endpoint.
+
+::: code-group
+
+```Rust [contract.rs]
+#[cw_serde]
+enum ExecuteMsg {
+    Add { value: i32 },
+    Subtract { value: i32 },
+}
+
+#[cfg_attr(not(feature = "library"), entry_point)]
+pub fn execute(
+    deps: DepsMut,
+    env: Env,
+    info: MessageInfo,
+    msg: ExecuteMsg,
+) -> StdResult<Response> {
+    match msg {
+        ExecuteMsg::Add { value } => {
+            // TODO: Add operation
+        }
+        ExecuteMsg::Subtract { value } => {
+            // TODO: Subtract operation
+        }
+    }
+    Ok(Response::new())
+}
+```
+
+:::

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

@@ -0,0 +1,37 @@
+[`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
+
+# Library feature
+
+In the ecosystem, there is the convention to gate the entrypoints of your contract behind a
+compile-time feature. The feature is conventionally called `library`.
+
+So instead of using the `#[entry_point]` macro directly, you should do this:
+
+::: code-group
+
+```Rust [contract.rs]
+#[cfg_attr(not(feature = "library"), entry_point)]
+pub fn instantiate(
+    deps: DepsMut,
+    env: Env,
+    info: MessageInfo,
+    msg: InstantiateMsg,
+) -> StdResult<Response> {
+    Ok(Response::new())
+}
+```
+
+:::
+
+::: tip :bulb: Tip
+You can see this in action in the [`cw-plus` contracts]. Here is an example in the [`cw4-stake` contract].
+:::
+
+The rationale behind this is that currently using `#[entry_point]` exports special symbols from the binary,
+and these symbols **must** be unique.
+
+That means if you have two `instantiate` endpoints annotated with `#[entry_point]` _somewhere_ in your project
+(that includes all your dependencies!), your contract will fail to compile.
+
+Using this library feature will enable developers to use your contract as a dependency and reuse your code.