Docs: Move guides to manual.#30736
Merged
Merged
Conversation
Mugen87
commented
Mar 14, 2025
| text = text.replace( /\[example:([\w\_]+) ([\w\:\/\.\-\_ \s]+)\]/gi, '<a href="../../examples/#$1" target="_blank">$2</a>' ); // [example:name title] | ||
| text = text.replace( /\`(.*?)\`/gs, '<code class="notranslate" translate="no">$1</code>' ); // `code` | ||
|
|
||
| document.body.innerHTML = text; |
Collaborator
Author
There was a problem hiding this comment.
I had to enhance lesson.js so certain things like link definitions don't had to be changed.
However, it was no copy/paste of manual pages since code sections and links to the doc pages had to be changed.
This was referenced Mar 18, 2025
Open
Owner
|
Fixed the broken links: 49f25c6 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related issue: -
Description
Before switching to the new docs, I suggest to move the "manual" part of the current documentation to
https://threejs.org/manual/. This looks like so:In this way, there is a clear separation.
https://threejs.org/manual/represents the manual with guides and in-depth articles whereashttps://threejs.org/docs/represents the API documentation.Next step:
We can delete all contents in
/docsand remove it from git versioning./docswill then be the output directory of JSDoc.