Add scaladoc docs

[BarkingBad]

No description provided.

[julienrf]

Thank you @BarkingBad! I think this would be a useful addition, although I found a few issues.

[julienrf]

I think you need to link its previous/next page

[BarkingBad]

Could you elaborate what headers should I use? I was basing on this page while choosing header settings

[julienrf]

I am not sure, actually. It seems there are no next/previous pages in this layout.

Did you check that the website renders correctly? Is your page reachable from the index page? Maybe you need to add it to the index.md page?

[BarkingBad]

Jonathan already told me how to fix this, will push new version soon

[BarkingBad]

Page shoud be visible now from both root page in Scala 3 section or from /scala3 suburi

[b-studios]

@BarkingBad@julienrf What do you think of changing the title of the document to: "All new Scaladoc for Scala 3"? Just to emphasize its relation to Scala 3 again...

[BarkingBad]

Sound great, will change :D

[BarkingBad]

@julienrf I think the PR should be ready for review, however it should not be merged before update docs PR

[b-studios]

Thanks @BarkingBad! I just made a quick pass over the document and added some suggestions.

[BarkingBad]

Hey, I have added migration guide as @julienrf asked me, however I encounter weird behaviour.

Sometimes, my article is not visible in the navigation tree

Exists

Doesn't exist

Exists

Doesn't exist

I guess I didn't updated some kind of index, could you point me out what should I fix?

[b-studios]

This is really strange. Did you check that it is not a caching problem?

[julienrf]

I found a few issues. Also, in the matrix comparison I think we should not mark Scala 2 settings that have no equivalent in Scala 3 as “implemented” in the last column.

[julienrf]

What do you mean by “We don’t migrate it”? Did it exist in Scala 2?

[BarkingBad]

These are the new features of scaladoc that we were considering whether we should implement them in the old scaladoc, however we know that -siteroot as the static site would be too tiresome to migrate it.

[julienrf]

Ah OK, what do you think of using the word “backporting” instead of “migrating”, when it’s about the Scala 3 -> Scala 2 direction?

[BarkingBad]

Good idea, will change

[BarkingBad]

I have applied all the requested changes @julienrf, hope the docs are now understandable.
There will be some dead links at CI pointing to dotty.epfl.ch, however I hope they will be fixed as soon as new nightly will be published

@b-studios I tried pruning docker container, browser caches etc, but with no avail. Do you mind trying to reproduce it locally?

[b-studios]

Hey @BarkingBad, I tried to reproduce your problem, but it looks good on my end. I just noticed an overflow here:

[b-studios]

And the CI still fails because some links are broken.

[BarkingBad]

Oh, ok, didn't see the overflow, will change to codeblock instead.

As it comes to CI, as I said we have to wait till the nightly will be published, unfortunately, the last one failed so links are not updated yet.

[BarkingBad]

@b-studios, hopefully new documentation at dotty.epfl.ch has been published this night, so all links should be good now. Could you rerun CI task since I don't have permission to do so.

[b-studios]

Looks good now. If @julienrf is happy with the changes I can go ahead and merge.

[julienrf]

Thank you!