feat: add storybook and animated planet component

[shadowusr]

What's done

• Installed storybook
• Implemented the AnimatedPlanet component, which will be used on the main page. Tested that it runs smoothly in Chrome, Firefox and Safari
• Set up github action for deploying static to S3. Currently to my personal bucket, but we can change that at any time just by editing a couple of secrets

One issue remains — website currently displays incorrectly; page renders twice. That maybe fixed later, maybe in another PR.

[github-actions]

✅ Successfully deployed static

• Docs website
• Storybook

[shadowusr]

Docusaurus detects broken links. Since we don't have /blog and other pages yet, it won't build successfully. Changed broken links to # for now.

[shadowusr]

You can't adequately resize svg, if you use paths in it as offset-path (motion path) for other elements. We use trail paths as motion paths for planes, so if svg with trails resizes planes would move along the wrong directory.

There are two ways to circumvent this: use transform scale with resize observer or re-calculate paths via d3.js with resize observer. Scale seems easier and more lightweight.

This hook provides a transform scale-based solution.

[shadowusr]

Here we use a hack to keep this planet png size below 20KB, making it extremely lightweight. In order for it to not be blurry on high-res displays we use clip-path to cut a perfect circle contour, so it appears to be high-res.

[miripiruni]

@shadowusr Super good!

I have question about https://storage.yandexcloud.net/testplane-ci/testplane-docs/website-static/8551288637-17-1/index.html — imho there is a bug, page is duplicated.

[shadowusr]

I have question about https://storage.yandexcloud.net/testplane-ci/testplane-docs/website-static/8551288637-17-1/index.html — imho there is a bug, page is duplicated.

Yeah, that's a bug, I mentioned it in the PR description. I'm going to address it in the next PR, because it's not linked to current changes.

Still not sure why this is happening. Definitely related to server side rendering (when I turn it off, page renders just fine). But the most weird thing about it is that if I serve the exact same bundle locally, page renders correctly. After uploading to S3, this happens. Not the first time, same thing happened with a different bucket and different docusaurus project.