[v16] Edit docs CI workflows to accommodate Docusaurus #50551
+60
−84
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.
Backports #48388
Copy the
gravitational/teleport
source into thecontent
directory of agravitational/docs-website
clone and overwrite thegit-update
yarn script with a no-op command. With way, we can use thegravitational/teleport
clone across multiple workflow steps (e.g., the prose linting step), and can identify a branch to pull using theactions/checkout
defaults. Name the submodule directorycurrent
to match the expectations of the Docusaurus site.Remove the Vercel preview workflow. After the docs engine migration, we'll no longer need to deploy a preview to Vercel in order to show docs authors what their potential changes look like on a rendered docs site.
Also fixes spelling errors caught by a later version of cspell.
exit
commands for failedcd
spackage.json
in the same pipelineUse latest Docusaurus site config schema
Fix the Prepare docs site configuration step
cd
sconfig.json
prepared for the Docusaurus site