Add and update monthly updates (#124)

* Add and update monthlies

* Fix broken links

docs/intro/ink-vs-cosmwasm.md

@@ -90,7 +90,7 @@ ink! contracts can be deployed on a few different options:
 ## Dependencies
 
 The first step in CosmWasm development is to
-[install dependencies](https://docs.cosmwasm.com/docs/1.0/getting-started/installation),
+[install dependencies](https://docs.cosmwasm.com/docs/getting-started/installation),
 namely Go, Rust and `wasmd`.
 
 For ink! you can also find [a setup guide](/getting-started/setup) which will help you
@@ -99,7 +99,7 @@ with dependencies, namely Rust, `cargo-contract` and `substrate-contracts-node`.
 ## Environment Setup
 
 The next step in the CosmWasm development workflow is
-[setting up the environment](https://docs.cosmwasm.com/docs/1.0/getting-started/setting-env).
+[setting up the environment](https://docs.cosmwasm.com/docs/getting-started/setting-env).
 That consists mainly of configuring `wasmd` such that it has prefunded accounts that are able
 to interact with the network.
 
@@ -137,7 +137,7 @@ $ cargo test
 ## Deploy and Interact
 
 CosmWasm contracts are deployed and instantiated with help of the `wasmd` executable. The
-list of step is provided [here](https://docs.cosmwasm.com/docs/1.0/getting-started/interact-with-contract).
+list of step is provided [here](https://docs.cosmwasm.com/docs/getting-started/interact-with-contract).
 
 It is possible to deploy and interact with ink! contracts using either a CLI
 (`cargo-contract`), or a web UI ([`contracts-ui`](https://contracts-ui.substrate.io/)).

docs/monthly-update/2022/11.md

@@ -5,7 +5,7 @@ slug: /monthly-update/2022/11
 
 ## ink! `v4.0.0-beta` 🦑
 
-We released the ink! [`v4.0.0-beta`](https://github.com/paritytech/ink/releases/tag/v4.0.0-beta) 🎉
+We released the ink! [`v4.0.0-beta`](https://github.com/paritytech/ink/releases/tag/v4.0.0-beta)! 🎉
 
 The focus of this beta release was to establish the stable ABI for the final `v4.0.0`
 release. It means that whilst subsequent `beta` releases may contain breaking contract
@@ -40,12 +40,12 @@ team like ours. As of this writing we're spread across eight different countries
 
 Alex and German had a fireside chat session at [Sub0](https://sub0.polkadot.network/), the Polkadot Developer conference.
 
-We're still waiting for the recoding to be uploaded, and we'll share that link here when
-it's available!
+You can watch the recording [here on YouTube](https://www.youtube.com/watch?v=tIqcIxVm1GE).
 
 ![Sub0 Fireside 2022](/img/monthly-update/sub0-fireside-2022.jpg)
 
 ## ink! x OpenZeppelin 🔏
+
 The Polkadot council approved a [treasury proposal](https://polkadot.subsquare.io/council/motion/296) funding
 [OpenZeppelin](https://www.openzeppelin.com/)'s review and audit of ink! and the Contracts pallet.
 

docs/monthly-update/2022/12.md

@@ -0,0 +1,13 @@
+---
+title: December '22
+slug: /monthly-update/2022/12
+---
+
+## Happy Holidays! 🎊
+
+![ink! Merry Christmas!](/img/monthly-update/xmas-22.jpg)
+
+We wish you all happy holidays!
+
+We are excited for the new year and have great things planned – starting
+with our next major release ink! 4.0 early next year.

docs/monthly-update/2023/01.md

@@ -0,0 +1,39 @@
+---
+title: January '23
+slug: /monthly-update/2023/01
+---
+
+## ink! x OpenZeppelin 🔏
+
+![ink! OpenZeppelin](/img/monthly-update/ink-open-zeppelin.jpg)
+
+Late last year, the Polkadot council approved a [treasury proposal](https://polkadot.subsquare.io/council/motion/296) funding
+[OpenZeppelin](https://www.openzeppelin.com/)'s review and audit of ink! and the Contracts pallet.
+
+The tl;dr here is that OpenZeppelin will be taking a look at ink! as a language and will
+give some recommendations for how to make the language safer.
+
+The on-chain proposal was supported by the Polkadot ecosystem teams Astar Network,
+Bit.Country, OpenBrush, t3rn, Pendulum Network, Phala Network and Watr.
+All of these already have – or are planning to have – the Contracts pallet that supports
+ink! enabled on their runtime. 
+
+The OpenZeppelin audit is intended to make ink! even more secure and user-friendly for developers 
+than it already is. In addition, OpenZeppelin will provide feedback on security issues as well
+as on common security pitfalls that Solidity cannot improve, but that ink! can.
+
+The engagement with OpenZeppelin started in January. We're super happy about this
+and will share more as we go along!
+
+## ink! sessions from sub0 are online 📺️
+
+sub0 is a conference for developers building at every level of the Polkadot tech stack:
+from custom layer-1 blockchains to dApps & smart contracts, infrastructure, tooling,
+cross-chain interoperability solutions, and more.
+
+In November 2022, sub0 was taking place in Lisbon and two ink! sessions
+were part of the program. The recordings are now available on YouTube:
+
+* [Fireside Chat: ink! And Wasm Contracts](https://www.youtube.com/watch?v=tIqcIxVm1GE)
+* [Build An Oracle In ink! On Phala Network](https://www.youtube.com/watch?v=MhnZ42o4QZM)
+

sidebars.js

@@ -10,6 +10,8 @@ module.exports = {
     ],
     'Monthly Update': [
       'monthly-update/overview',
+      'monthly-update/2023/01',
+      'monthly-update/2022/12',
       'monthly-update/2022/11',
       'monthly-update/2022/10',
       'monthly-update/2022/09',

versioned_docs/version-4.0.0-alpha.1/intro/ink-vs-cosmwasm.md

@@ -90,7 +90,7 @@ ink! contracts can be deployed on a few different options:
 ## Dependencies
 
 The first step in CosmWasm development is to
-[install dependencies](https://docs.cosmwasm.com/docs/1.0/getting-started/installation),
+[install dependencies](https://docs.cosmwasm.com/docs/getting-started/installation),
 namely Go, Rust and `wasmd`.
 
 For ink! you can also find [a setup guide](/getting-started/setup) which will help you
@@ -99,7 +99,7 @@ with dependencies, namely Rust, `cargo-contract` and `substrate-contracts-node`.
 ## Environment Setup
 
 The next step in the CosmWasm development workflow is
-[setting up the environment](https://docs.cosmwasm.com/docs/1.0/getting-started/setting-env).
+[setting up the environment](https://docs.cosmwasm.com/docs/getting-started/setting-env).
 That consists mainly of configuring `wasmd` such that it has prefunded accounts that are able
 to interact with the network.
 
@@ -137,7 +137,7 @@ $ cargo test
 ## Deploy and Interact
 
 CosmWasm contracts are deployed and instantiated with help of the `wasmd` executable. The
-list of step is provided [here](https://docs.cosmwasm.com/docs/1.0/getting-started/interact-with-contract).
+list of step is provided [here](https://docs.cosmwasm.com/docs/getting-started/interact-with-contract).
 
 It is possible to deploy and interact with ink! contracts using either a CLI
 (`cargo-contract`), or a web UI ([`contracts-ui`](https://contracts-ui.substrate.io/)).