Update markdown files for preprocessing purposes

[BarkingBad]

No description provided.

[julienrf]

Could you please check that the content of the files here is consistent with what we have on docs.scala-lang? I see some differences in the file other-new-features/export.md, for instance.

[BarkingBad]

@julienrf I think the difference is because of #13327, I will update it asap, but currently I'm on vacations so if you'd like to merge it earlier you can take over this PR

[bishabosha]

also needs updates integrated from #13328 and #13338

[BarkingBad]

@bishabosha @julienrf I updated the docs, I hope now everything is up to date (I rebased on top of the current master and checked if everything is applied correctly) The faster we merge it the better, since we will avoid diverging again

[julienrf]

If I understand correctly, this PR does two things:

1. It overwrites the content of the .md documentation files of the dotty repository with the content of the repo docs.scala-lang,
2. It changes the generateDocumentation task such that it only renders the API documentation (the blog and static pages are not anymore part of the output).

An important consequence is that we won’t be able to generate the dotty.epfl.ch website anymore after this PR is merged. I think this is fine, but before we do that I suggest we do a last update to clearly indicate on the website that its content is frozen/archived/unmaintained, with pointers on the place to find up to date information (on every page).

Another (annoying) thing is that we must be very careful in the way we overwrite the content of the md files. We need to make sure we don’t loose any important changes that have been applied in the dotty repository (but not in docs.scala-lang). There seems to be such changes, related to experimental features…

[bishabosha]

there have been a few updates to Scala 3 docs on docs.scala-lang.org since this was last pushed

[julienrf]

@bishabosha This is not so much a big deal, actually (I mean, this is not blocking this PR). We can pick these changes later.

[BarkingBad]

I believe this line will preserve older static site files while publishing nightlies according to:
https://github.com/peaceiris/actions-gh-pages#%EF%B8%8F-keeping-existing-files-keep_files

[BarkingBad]

Actually this could not work (would overwrite top level index.html), so I updated genDocs script

[BarkingBad]

I will add manually to dotty-website pregenerated static site with banners that the files are frozen since this commit.

[BarkingBad]

PoC banners for files that will be moved to docs.scala-lang eventually:

Banner for all the other static site docs:

[BarkingBad]

This PR scala/dotty.epfl.ch#6 should be merged right after this one. If we merge it earlier it can be overridden once nightly docs will be published.

[julienrf]

This PR lampepfl/dotty-website#6 should be merged right after this one. If we merge it earlier it can be overridden once nightly docs will be published.

Should we consider publishing the nightly docs somewhere else than on dotty.epfl.ch? Or just make sure that they only override the API documentation, but nothing else.

I think scala/dotty.epfl.ch#6 should be merged before this PR, since this PR disables the website.

[BarkingBad]

If we merged it, then the very first nightly of dotty would override the files with banners, thus we will lose the changes. We can create small PR with changes to the genDocs script and Build.scala so the files won't be overridden anymore, but we have to merge them at least on the same day.

[BarkingBad]

Should we consider publishing the nightly docs somewhere else than on dotty.epfl.ch? Or just make sure that they only override the API documentation, but nothing else.

I think nightlies can be still published on dotty.epfl.ch, since rather there is a little traffic, most people will hit the stable docs (3.x, 3.0.2). Nonetheless, the domain is not so important in that case.

[BarkingBad]

Closing since we merged #13587