-
-
Notifications
You must be signed in to change notification settings - Fork 382
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
Define Glossary #1800
Define Glossary #1800
Conversation
Deployment of preview was successful: https://woodpecker-ci-woodpecker-pr-1800.surge.sh |
Co-authored-by: qwerty287 <80460567+qwerty287@users.noreply.github.com>
Co-authored-by: Anbraten <anton@ju60.de>
Co-authored-by: Anbraten <anton@ju60.de>
Co-authored-by: qwerty287 <80460567+qwerty287@users.noreply.github.com>
What do you think about moving this to the user docs. I guess it would be quite nice if users would read that to for example be able to ask much better questions in the chat, issues. |
This comment was marked as outdated.
This comment was marked as outdated.
@anbraten moved, hope it's in a better spot now |
This comment was marked as off-topic.
This comment was marked as off-topic.
@6543 I had a short look around. And liked how the following pages placed it right after the
So between getting started and pipeline syntax, might be a good place: In addition I checked the search and would suggest we change the terms to headings so they are more important in the search and the user can use easily navigate them and then use the links you have added to navigate to the corresponding pages after getting a short introduction of that term. Extending to something like those concepts & philosophy pages could be nice in the future as well:
Also really nice is how argo structed their docs in a tranining / like a course way. So you learn step by step more advanced concepts of the tool: |
based on #745 (comment)
close #1724