| Age | Commit message (Collapse) | Author |
|---|
|
When using reference links (`[a link to something][something]`) the link
goes itself is referred to later in the file. This normally should be a
line that starts with the reference name in brackets, followed by the
actual link (`[something]: <link>`).
Many of these reference links in the repo have unnecessary leading
spaces. While this renders OK, at least with GitHub's markdown
rendering, it currently causes problems for sites like kubernetes.dev
that pull in these docs and attempt to update the links so they are
usable from a different rendered location.
While the script that does that import should probably be updated to be
a little more robust, this addresses the immediate need of fixing these
broken kubernetes.dev links by removing the leading whitespaces so they
are properly recongized and updated.
Also some very minor cleanup in some older files. While these don't
appear to be imported elsewhere, they were cleaned up to avoid the risk
of any future copy/paste issues that could happen prior to the doc
import script being updated to handle things correctly.
Signed-off-by: Sean McGinnis <stmcg@amazon.com>
|
|
While the trailing brackets [] are markdown compatible they break the links with the contributor-site link generator when the content is ingested.
|
|
Co-authored-by: Christoph Blecker <admin@toph.ca>
|
|
Signed-off-by: markyjackson-taulia <marky.r.jackson@gmail.com>
|
|
* Update communication guide to match style guidelines
Update the Zoom and Slack communication guides to match style guidelines. This also includes a few updates, grammar fixes, and modifications from the community.
Co-authored-by: Aaron Epperson <aaron@aaronepperson.com>
Co-authored-by: Bob Killen <killen.bob@gmail.com>
* Fix links in slack-guidelines
Co-authored-by: Aaron Epperson <aaron@aaronepperson.com>
Co-authored-by: Bob Killen <killen.bob@gmail.com>
|
|
Signed-off-by: Josh Berkus <josh@agliodbs.com>
|
|
pointless anyway since it would be 100% pinned posts.
|
|
|
|
|
|
* Clarify requirements for asking for a slack channel
Signed-off-by: Jorge O. Castro <jorgec@vmware.com>
* Fix some grammatical errors
* Fix hyperlink to cncf slack
Signed-off-by: Jorge O. Castro <jorgec@vmware.com>
* Actually fix link to CNCF slack
Signed-off-by: Jorge O. Castro <jorgec@vmware.com>
* Add clarification on private channels
Signed-off-by: Jorge O. Castro <jorgec@vmware.com>
* Update communication/slack-guidelines.md
Co-authored-by: Irvi Aini <7439590+irvifa@users.noreply.github.com>
* Update communication/slack-guidelines.md
Co-authored-by: Irvi Aini <7439590+irvifa@users.noreply.github.com>
Co-authored-by: Irvi Aini <7439590+irvifa@users.noreply.github.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Renamed 'ihor' -> 'idvoretskyi' to follow the nickname consistency across the community (GitHub, Slack, Twitter, etc.)
|
|
Apologies for the pedantry, just read through the doc after the link from the community meeting, and wanted to fix up a couple minor grammar/spelling issues
|
|
guide, etc.
|
