-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
WIP: Versioned docs #17905
WIP: Versioned docs #17905
Conversation
Codecov Report
@@ Coverage Diff @@
## main #17905 +/- ##
=======================================
Coverage ? 47.39%
=======================================
Files ? 952
Lines ? 132524
Branches ? 0
=======================================
Hits ? 62807
Misses ? 62145
Partials ? 7572 Continue to review full report at Codecov.
|
Makefile
Outdated
cd docs; make trans-copy clean build-offline; | ||
cd docs; make trans-copy clean ; | ||
#git co release/v1.13 && PUBLIC=public/v1.13 make build-offline ; | ||
git co release/v1.14 && PUBLIC=public/v1.14 make build-offline ; |
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 avoid having to hardcode the release branch? Maybe some logic that builds all branches, back to a certain starting branch?
Some more users are misled by documents recently, they are asking about why they do not have the registry feature. |
I think the final solution for docs will be docusaurus, which has support for versioning, like woodpecker-ci has :) |
Done is better than perfect, as long as it can continue to improve without difficulty. If we can use a simple mechanism to split the documents for versions (months ago), then there will be no user asking about strange questions any more, and there is still a chance to improve the versioned document system. Today there is one more user asking about why he doesn't have package feature in discord. |
Yeah, I'm not opposed to having some intermediate solution now, just pointing out potential better solutions for the future :) |
Today one more |
7713b29
to
783f865
Compare
No description provided.