Move documentation to a more permanent home
SethTisue opened this issue · comments
It's not good for a 2018 blog post to also serve as the documentation. We should keep it in-repo so we can update it.
We could add a note to the top of the old post, redirecting readers to the current documentation. (This is what we did, for example, with https://www.lightbend.com/blog/scala-inliner-optimizer which eventually turned into the more permanent https://docs.scala-lang.org/overviews/compiler-options/optimizer.html.)
The core docs have already been moved to https://scalacenter.github.io/scalac-profiling/. The rest will be there gradually.
The rest will be there gradually
Is it too soon to add the notice to the blog post, then? Or should I go ahead?
Or should I go ahead?
I think the microsite is good enough already. And so, go ahead.