Hi, you’ve had some great articles that I’ve read and bookmarked but they’re no longer available since blog site has changed. Any chance you’ll be re-releasing them in the future?
Some examples:
https://unity.com/blog/engine-platform/in-parameters-in-burst
https://unity.com/blog/engine-platform/bursting-into-2021-with-burst-1-5
Some of them are still available:
(I wish all of the engine platform articles made available again, they provided great insight)
Thank for bringing the missing blog post to our attention. I brought it our web team and at least the ones you link to should be revived now.
Thanks a lot. Could you also revive these (found on Burst documentation first page)
https://unity.com/blog/engine-platform/enhancing-mobile-performance-with-the-burst-compiler
https://unity.com/blog/technology/enhanced-aliasing-with-burst
Hi @vectorized-runner ,
Thanks again for alerting us to these being down! @mfjord has now started the process of trying to get these two new ones you just shared re-released too. 
So hopefully they will be up soon again, we will keep you posted!
They’re up but the code formatting is broken, makes it very hard to read
Aha, I missed that! Thanks for highlighting that.
Working on fixing that for the articles in this thread right away will get back to you once it’s done!
Back again,
The articles here now have all code-sections formatted correctly as code again:
Thanks for reaching out about this as we had missed it.
If you stumble over any other good unreleased articles/instances where the code isn’t formatted as code etc. don’t hesitate to reach out again, we appreciate it! 
In the article In parameters in Burst, only the first code-section is formatted correctly - all the remaining ones are missing.
I had a look at the article, but I can only see a single code snippet at the very beginning. There are no other code snippets in the article, just text and images / screenshots mostly of the generated assembly. I don’t see an issue in that article.
I think there may actually be some code blocks missing… yes that article mixes code snippets and photographs of code… but!
When Jimmy says this:
I think he’s referring to things like this: (tiny text is my own)
Additionally, inline code snippets with the single backticks are not rendered correctly, and the backticks show up directly in the article.
Yeah, each assembly snippet should have its corresponding source-code snippet in front of it.
Otherwise it would be necessary to infer the source code’s usage context — making the article difficult to read.
