Update documentation links in README

[barbara-celi]

Updated links in the README to point to the new developer documentation site.

What problem is this solving?

How to test it?

[Workspace](Link goes here!)

Screenshots or example usage:

Describe alternatives you've considered, if any.

Related to / Depends on

How does this PR make you feel? 🔗

![](put .gif link here - can be found under "advanced" on giphy)

[vtex-io-ci-cd]

Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖

Please select which version do you want to release:

• Patch (backwards-compatible bug fixes)

• Minor (backwards-compatible functionality)

• Major (incompatible API changes)

And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.

• No thanks, I would rather do it manually 😞

[vtex-io-docs-bot]

Beep boop 🤖

Thank you so much for keeping our documentation up-to-date ❤️

[github-actions]

Fails

🚫

We follow keepachangelog standards. Please, change the file CHANGELOG.md adding a small summary of your changes under the [Unreleased] section. Example: ## [Unreleased] + ### Fixed + - Issue with image sizing in the SKU Selector. Possible types of changes: Added for new features. Changed for changes in existing functionality. Deprecated for soon-to-be removed features. Removed for now removed features. Fixed for any bug fixes. Security in case of vulnerabilities.

Generated by 🚫 dangerJS against 3de80b2

[vtex-io-ci-cd]

Your PR has been merged! App is being published. 🚀
Version 2.29.1 → 2.29.2

After the publishing process has been completed (check #vtex-io-releases) and doing A/B tests with the new version, you can deploy your release by running:

vtex deploy vtex.store-header@2.29.2

After that your app will be updated on all accounts.

For more information on the deployment process check the docs. 📖