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

[EPIC] Work on snippets infrastructure #4069

Closed
3 of 5 tasks
abrennan89 opened this issue Jul 28, 2021 · 6 comments
Closed
3 of 5 tasks

[EPIC] Work on snippets infrastructure #4069

abrennan89 opened this issue Jul 28, 2021 · 6 comments
Assignees
Labels
Epic Epics to group issues kind/infrastructure Docs infrastructure related kind/mkdocs lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/medium

Comments

@abrennan89
Copy link
Contributor

abrennan89 commented Jul 28, 2021

TO DO:

This is just a brain dump for now, we can split these into individual issues in the epic as we assign / work on them.

Setting this as critical priority for the following reasons:

  • It would save us massive amounts of duplication in docs if we get our snippets properly in order.
  • Somewhat prevents reorg of content not having this ironed out, e.g. what when something needs to be included in both admin and dev guides? If we want to get rid of the serving and eventing sections, we need this soon.
  • The longer we take to do this, the more cleanup there will be to do from folks adding duplicate / additional content that should be part of a snippet.
@snneji
Copy link
Contributor

snneji commented Aug 23, 2021

@abrennan89 Has there been a decision on which snippets plugin we want to use? If so can we close #3769? If not we can add #3769 as the first issues in this epic.

@abrennan89 abrennan89 removed this from the v0.27.0 milestone Aug 27, 2021
@snneji
Copy link
Contributor

snneji commented Dec 10, 2021

Hi @abrennan89, I would like to create the issues for this epic. Are you happy for me to create issues from the TO DO list?
Is there anything else you would want added?

@abrennan89
Copy link
Contributor Author

@snneji I think that's fine to go ahead with, thanks

@snneji snneji removed the kind/spike label Dec 13, 2021
@github-actions
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 14, 2022
@psschwei
Copy link
Contributor

/lifecycle frozen

@knative-prow knative-prow bot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 14, 2022
@snneji snneji reopened this Jun 12, 2022
@abrennan89 abrennan89 self-assigned this Aug 2, 2022
@snneji snneji moved this to In progress in Docs WG Roadmap Aug 30, 2022
@abrennan89
Copy link
Contributor Author

Work to move sections to snippets is ongoing. I don't think this epic is required anymore.

Repository owner moved this from In progress to Done in Docs WG Roadmap Sep 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Epic Epics to group issues kind/infrastructure Docs infrastructure related kind/mkdocs lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/medium
Projects
None yet
Development

No branches or pull requests

4 participants