Integrate docsite

RELEASING.md

@@ -18,14 +18,24 @@ to
 # OpenZeppelin Contracts for Cairo v0.2.0 (account/Account.cairo)
 ```
 
-(3) Create a release branch and add a tag to it. This branch can be useful if we need to push a hot fix on top of an existing release in the case of a bug.
+(3) Update documentation version in `docs/antora.yml`
+
+```diff
+ name: cairo-contracts
+ title: Contracts for Cairo
+-version: 0.1.0
++version: 0.2.0
+ (...)
+```
+
+(4) Create a release branch and add a tag to it. This branch can be useful if we need to push a hot fix on top of an existing release in the case of a bug.
 
 ```sh
 git checkout -b release-0.2.0
 git tag v0.2.0
 ```
 
-(4) Push the tag to the main repository, [triggering the CI and release process](https://github.com/OpenZeppelin/cairo-contracts/blob/b27101eb826fae73f49751fa384c2a0ff3377af2/.github/workflows/python-app.yml#L60).
+(5) Push the tag to the main repository, [triggering the CI and release process](https://github.com/OpenZeppelin/cairo-contracts/blob/b27101eb826fae73f49751fa384c2a0ff3377af2/.github/workflows/python-app.yml#L60).
 
 ```sh
 git push origin v0.2.0