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

Use Sphinx to manage docs/latest/ #120

Closed
wants to merge 1 commit into from
Closed

Conversation

kzys
Copy link
Member

@kzys kzys commented Mar 9, 2022

This commit adds https://containerd.io/docs/latest/, based on
github.com/containerd/containerd's docs directory.

We would need docs/1.6/, docs/1.5/, ... eventually. But for now
we can start from the tip of the main branch.

@kzys kzys force-pushed the sphinx branch 4 times, most recently from d6023fd to b474949 Compare March 9, 2022 19:05
@kzys kzys changed the title Add Sphinx Use Sphinx to manage docs/latest/ Mar 9, 2022
This commit adds https://containerd.io/docs/latest/, based on
github.com/containerd/containerd's docs directory.

We would need docs/1.6/, docs/1.5/, ... eventually. But for now
we can start from the tip of the main branch.

Signed-off-by: Kazuyoshi Kato <katokazu@amazon.com>
@@ -0,0 +1,43 @@
# containerd
Copy link
Member Author

@kzys kzys Mar 9, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For docs/latest, we should have this index.md and possibly conf.py in containerd/containerd.

For released versions such as 1.6, I'd like to have versioned documents like https://www.envoyproxy.io/docs. However we generally backport only security fixes. So just using the existing branches wouldn't work.

Is it okay to backport documentation changes from main to release/1.x?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it okay to backport documentation changes from main to release/1.x?

Yes

@kzys
Copy link
Member Author

kzys commented Mar 9, 2022

@AkihiroSuda
Copy link
Member

Is this still draft?

@AkihiroSuda AkihiroSuda linked an issue Mar 24, 2022 that may be closed by this pull request
@estesp
Copy link
Member

estesp commented Mar 31, 2022

Overall I'm LGTM on this direction; we have some things to figure out with how we point to this site and the fact that the "UI" /design isn't really aligned with the overall website, but I'm fine with that generally. At some point it would be nice to make it like going between pkg.go.dev and go.dev; that top bar is consistent across both, even though the pkg site (I assume) is generated based on doc input from the source.

@AkihiroSuda
Copy link
Member

We should now remove https://github.com/containerd/containerd.io/blob/main/.github/workflows/sync-releases.yml , but it can be a separate PR.

cri/config.md
cri/crictl.md
cri/decryption.md
cri/installation.md
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is outdated, being deprecated in containerd/containerd#6758

cri/crictl.md
cri/decryption.md
cri/installation.md
cri/proposal.md
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is historical (containerd/containerd#6754), no need to be linked here

cri/decryption.md
cri/installation.md
cri/proposal.md
cri/registry.md
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Outdated, not worth linking

@kzys
Copy link
Member Author

kzys commented Apr 5, 2022

This is superseded by #121.

@kzys kzys closed this Apr 5, 2022
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.

Merge this repo into main repo? (or vice versa)
3 participants