-
Notifications
You must be signed in to change notification settings - Fork 367
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
feat: [M3-7538] - Cloud Manager Docs with Vitepress #10027
feat: [M3-7538] - Cloud Manager Docs with Vitepress #10027
Conversation
|
||
- uses: oven-sh/setup-bun@v1 | ||
with: | ||
bun-version: 1.0.21 |
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.
pinning bun version for good measure
.github/workflows/docs.yml
Outdated
|
||
- name: Build with VitePress | ||
run: | | ||
bunx vitepress@1.0.0-rc.35 build 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.
pinning the vitepress version as well. We may want to update this when the major version comes out
docs/plugins/sidebar.ts
Outdated
return markdownInfoArray; | ||
} | ||
|
||
export const guides = scanDirectory(DEVELOPMENT_GUIDE_PATH); |
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 is a pretty basic plugin to aggregate the pages in the development-guide
and populate the left sidebar.
As discussed with @bnussman-akamai it is not super dynamic at the moment since it won't handle recursion or other directories, but it serves our purpose well considering the doc structure isn't something that's been updated (or will be updated) very soon. If it does it wouldn't be too hard to update top get there.
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.
Can we include this info as a comment (as least: "Aggregates the pages in the development-guide and populates the left sidebar") in this file?
|
||
on: | ||
push: | ||
branches: [develop] |
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.
we may want to target master
eventually? I think it's ok for now but open to feedback
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.
My vote would be keeping develop
with this setup. Our docs are mostly targeted at developers and we want them looking at our latest documentation at all times.
I also hold this opinion on Storybook but I don't think many agree
If we start building multiple environments (like design.dev.linode.com or docs.cloud.dev.linode.com) then it would be a different story imo
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.
My vote would be keeping develop with this setup. Our docs are mostly targeted at developers and we want them looking at our latest documentation at all times.
I'd agree with this.
Coverage Report: ✅ |
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.
Awesome 🎉 I'm happy with the outcome!
This will definitely make it more appealing to document (and consume documentation) for Cloud Manager
|
||
on: | ||
push: | ||
branches: [develop] |
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.
My vote would be keeping develop
with this setup. Our docs are mostly targeted at developers and we want them looking at our latest documentation at all times.
I also hold this opinion on Storybook but I don't think many agree
If we start building multiple environments (like design.dev.linode.com or docs.cloud.dev.linode.com) then it would be a different story imo
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 a couple minor comments about documentation. This was looking good in the test deploy and running locally! 🎉
|
||
on: | ||
push: | ||
branches: [develop] |
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.
My vote would be keeping develop with this setup. Our docs are mostly targeted at developers and we want them looking at our latest documentation at all times.
I'd agree with this.
docs/plugins/sidebar.ts
Outdated
return markdownInfoArray; | ||
} | ||
|
||
export const guides = scanDirectory(DEVELOPMENT_GUIDE_PATH); |
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.
Can we include this info as a comment (as least: "Aggregates the pages in the development-guide and populates the left sidebar") in this file?
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 is great, awesome work @abailly-akamai and @bnussman-akamai! Looking forward to sprucing up the testing docs once this is merged 🎉
What's the motivation behind using bunx
over npx
? I thought npx
was a nice idea since it wouldn't require developers to install anything in addition to what we already require, and it's one more dependency we need support/document/maintain (similarly, I think we should also add a step in GETTING_STARTED.md
to instruct the user to install Bun, and document which version(s) we support). Regardless, it is cool seeing Bun in action!
@jdamore-linode I generally agree that If we want to keep is simple and not take the bet on Bun yet, I'm fine with reverting to |
Thanks @bnussman-akamai, that makes sense to me! I'm happy (and excited) to give Bun a shot. Also just noticed the addition to
Hear, hear! |
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.
Nice work @abailly-akamai!
Description 📝
This is the latest iteration of a docsite generation for the Cloud Manager docs.
It iterates over the two previous POCs:
This version addresses the concerns of added dependencies to build the docs and utilizes the much better looking
vitepress
version. Instead of adding dev dependencies to the monorepo we utilizenpx
(more specifically its bun equivalentbunx
) to get those on the fly during build time.As a result there's 0 dependencies added to generate our docs 🎉
The same process is used to develop locally.
The pages will eventually live at
https://linode.github.io/manager/
but until then the PR has been merged we can see the result at:👉 https://abailly-akamai.github.io/manager/
Thanks @bnussman-akamai for the vitepress suggestion, GH action and @mjac0bs for the inspiration!
Note: We will need to also link to this documentation from the README and in other knowledge sources, tasks that will be done separately (we also need to clean/update the docs themselves)
Changes 🔄
Preview 📷
How to test 🧪
yarn docs
to get the local versionAs an Author I have considered 🤔
Check all that apply