Skip to content
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

Open
wants to merge 9 commits into
base: main
Choose a base branch
from
Open

Add hugo docsy website #70

wants to merge 9 commits into from

Conversation

dtzar
Copy link

@dtzar dtzar commented Dec 16, 2023

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?

  • Yes, PR includes docs updates

Release Note

add hugo docsy website

@Bryce-Soghigian
Copy link
Collaborator

I guess step 1 is to merge and step 2 would be to setup a netlify deployment based on our repo?

README.md Outdated Show resolved Hide resolved
@Bryce-Soghigian
Copy link
Collaborator

@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

  1. Supported cluster configurations
  2. Self Hosted VS NAP
  3. Comprehensive Nodepool docs
  4. FAQs

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]>
Copy link

@sftim sftim left a 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.

website/content/en/_index.html Outdated Show resolved Hide resolved
Makefile Show resolved Hide resolved
website/package.json Outdated Show resolved Hide resolved
website/netlify.toml Show resolved Hide resolved
website/netlify.toml Show resolved Hide resolved
website/netlify.toml Show resolved Hide resolved
website/layouts/robots.txt Outdated Show resolved Hide resolved
website/content/en/docs/contributing/_index.md Outdated Show resolved Hide resolved
website/content/en/docs/_index.md Outdated Show resolved Hide resolved
Signed-off-by: David Tesar <[email protected]>
Copy link

@sftim sftim left a 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]>
@Bryce-Soghigian
Copy link
Collaborator

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?

@Bryce-Soghigian
Copy link
Collaborator

@sftim thank you for your review here btw its appreciated!

@dtzar
Copy link
Author

dtzar commented Dec 23, 2023

You can use the netlify deploy url to start.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants