-
-
Notifications
You must be signed in to change notification settings - Fork 35.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Officialize" renaming of examples classes to addons #24579
Conversation
Co-authored-by: Marco Fugaro <[email protected]>
I think fundamentals.html in new manual are missing the information about import maps... |
New changes were added since last review.
Renaming the doc pages will break a lot of URLs. Without implementing a redirect, I do not vote for doing this. Besides, the PR got too complex. The first changes to the |
I tried to |
Okay, I fixed it somehow 🙏 |
Reverted those changes. |
@LeviPesin it might be better to open an issue for this first to see if there is support for the change, and also to figure out exactly what is required. I'm personally in favor but as @Mugen87 points out it has to happen without breaking URLs. Which might make this more complicated than it first appears. On the other hand maybe it's ok just to change the docs and page titles and leave URLs as they are? |
Hey, I believe this can be merged 👍 |
Related issue: #23406
Description
As we now have
three/addons
alias, and started to refer to examples classes as addons, isn't it the time to note that in documentation?