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

Explore Moving Documentation To GitHub Pages #1436

Open
ihcsim opened this issue May 11, 2022 · 13 comments
Open

Explore Moving Documentation To GitHub Pages #1436

ihcsim opened this issue May 11, 2022 · 13 comments

Comments

@ihcsim
Copy link
Contributor

ihcsim commented May 11, 2022

We should explore moving the docs site to GitHub Pages. It seems to provide better support for markdown/HTML/CSS/JS and integration with GitHub Actions. Together with Jekyll, it also offer a wide selection of themes.

@github-actions
Copy link
Contributor

Thanks for opening this issue 👍. The team will review it shortly.

If this is a bug report, make sure to include clear instructions how on to reproduce the problem with minimal reproducible examples, where possible. If this is a security report, please review our security policy as outlined in SECURITY.md.

If you haven't already, please take a moment to review our project's Code of Conduct document.

@julio-lopez
Copy link
Contributor

@ihcsim https://github.com/gohugoio/hugo is a good alternative for Jekyll, if not preferred.

@ihcsim
Copy link
Contributor Author

ihcsim commented May 11, 2022

@julio-lopez No complains about Hugo; I used it in a previous project. What does the Hugo/GH Pages integration look like? I haven't looked into it, but GH Pages mentioned Jekyll has built-in support.

@github-actions
Copy link
Contributor

This issue is marked as stale due to inactivity. Add a new comment to reactivate it.

@github-actions github-actions bot added the stale label Jul 11, 2022
@pavannd1
Copy link
Contributor

Still relevant

@Sagar2366
Copy link
Contributor

@ihcsim @pavannd1 I would like to work on this issue.

@ihcsim
Copy link
Contributor Author

ihcsim commented Oct 4, 2022

@Sagar2366 Currently, all the docs are written in rst format. Any idea what porting it over to GH Pages with Hugo looks like, including CI automation etc.?

@github-actions
Copy link
Contributor

github-actions bot commented Dec 4, 2022

This issue is marked as stale due to inactivity. Add a new comment to reactivate it.

@github-actions github-actions bot added the stale label Dec 4, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Jan 4, 2023

This issue is closed due to inactivity. Feel free to reopen it, if it's still relevant.

@mlavi
Copy link
Contributor

mlavi commented Mar 16, 2023

Let's share this with our new Technical Writer

@mlavi mlavi self-assigned this Mar 16, 2023
@mlavi
Copy link
Contributor

mlavi commented Mar 16, 2023

https://github.com/kanisterio/kanister/tree/master/docs are published to S3+Cloudfront during internal Kanister release pipeline. Let's discuss refactoring build+publish docs to GitHub.

@pavannd1 pavannd1 removed the triage label Mar 16, 2023
@pavannd1 pavannd1 added the frozen label Jun 6, 2023
@hairyhum
Copy link
Contributor

#2642 is merged. Now we need to make a GH workflow to build and publish the docs.

@mlavi
Copy link
Contributor

mlavi commented Jun 5, 2024

While that is underway, I've made REQ0054258 with Veeam CT to update DNS with doc-new IN CNAME kanisterio.github.io

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

No branches or pull requests

6 participants