-
Notifications
You must be signed in to change notification settings - Fork 64
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
Add hugo docsy website #70
base: main
Are you sure you want to change the base?
Conversation
I guess step 1 is to merge and step 2 would be to setup a netlify deployment based on our repo? |
@tallaxes how do you feel about letting the base docs that just copied our existing documentation go in as is minus the doc change? We need to add docs on
ETC Or do you think we should merge docs with AWS and have them in one place? Does the karpenter website code belong here? Referring to questions still to be answered here |
Signed-off-by: David Tesar <[email protected]>
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.
Thanks
Here's a review - I hope it's useful.
Signed-off-by: David Tesar <[email protected]>
Signed-off-by: David Tesar <[email protected]>
Signed-off-by: David Tesar <[email protected]>
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.
nits if you want them
Signed-off-by: David Tesar <[email protected]>
So what are next steps once this merges in? We buy a domain? Then setup netlify to deploy based on main, as well as preview builds? |
@sftim thank you for your review here btw its appreciated! |
You can use the netlify deploy url to start. |
feat: add hugo docsy website
docs: some changes to existing documentation to make it work and make sense in the website
Description
You can see what the website looks like for this code via the netlify deployment here. If desired - a more granular breakdown of commit changes on the PR I merged in my fork.
Does this change impact docs?
Release Note