-
Notifications
You must be signed in to change notification settings - Fork 839
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
build: deploy new docs #7409
build: deploy new docs #7409
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one suggested change to add the trailing slash to the Docusaurus URL and I think we're good to go here. The Docusaurus env variable displayed correctly and the docs site was accessible from the GitHub PR page.
scripts/deploy/deploy_docs
Outdated
- Storybook: https://eui.elastic.co/pr_${GIT_PULL_REQUEST_ID}/storybook | ||
- New docs site (in development): https://eui.elastic.co/pr_${GIT_PULL_REQUEST_ID}/new-docs" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This URL doesn't have the trailing /
at the end of the Docusaurus link, and I think that's what's causing the docs header to display twice when the URL resolves to /new-docs/index.html
. If I add the trailing slash, it shows the header properly and has the same URL as the EUI logo in the docs preview site.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, this is strange. I'm testing some configuration variations to see if we can fix it without forcing that slash there just in case it would cause troubles when deployed to /
in the future
0210750
to
445db1f
Compare
Preview staging links for this PR:
|
💚 Build Succeeded
History
cc @tkajtoch |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 LGTM!
Summary
This PR resolves #7402 by updating
build_docs
anddeploy_docs
to build the new docs site and deploy it undernew-docs
directory.QA