The documentation contains a few references to issues from the now archived yewstack/docs repository.
Since the docs repository is read-only, the same issues should be re-created here and the links in the docs should be updated to point to the new issue.

"Contribute to our docs" links

• Page: [Components Lifecycle Diagram](https://yew.rs/docs/conce

Hi, I'm not sure if more platforms are interesting to you, but I've made a slightly more complete implementation of padding a struct to the cache line size here:

https://github.com/tinco/cache_line_size

I got the information on the cache line sizes from the Go compiler repository, so I'm pretty sure these are correct for all platforms Go runs on, which is a whole bunch.

CE have released their own take on tracing, with following notable changes compared to original ZIO Tracing:

• Instead of parsing lambdas, CE throws exceptions in IO constructors and cleans up stacktraces. That also means there is no regional control of tracing and AFAIK no way to avoid slight overhead even when tracing is completely disabled – but OTOH it may probably work on Scala.js
• Trace

Do you think it's necessary at this stage?

Maybe as a followup to #192 we could try to update the bastion arch picture.

It would allow us to put it back on the readme and it would look better on the website :)