docs: set up v3 API ref. site #1425
Merged
Conversation
This file contains 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
WillieRuemmele
approved these changes
May 21, 2024
|
✅ : was coincidentally using these docs this A.M. for something else |
|
✅: edit this page now in footer |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Updates typedoc workflow to push site build to
gh-pages.I pushed the first build from local to confirm it Jekyll build worked while retaining the v1 API ref at
doc:https://github.com/jsforce/jsforce/tree/gh-pages
Changed GH pages it to serve from the root:
v3: https://jsforce.github.io/jsforce/
v1: https://jsforce.github.io/jsforce/doc/
When users click on
API Referencein https://jsforce.github.io/ they will get to the v3 API ref. The main page is the readme which links to v1 ones.changed here: jsforce/jsforce.github.io@63913c0
@W-15807592@