Change:
<!-- overview --> This document helps you get started using the Kubernetes [NetworkPolicy API](/docs/concepts/services-networking/network-policies/) to declare network policies that govern how pods communicate with each other. <ins> {{% thirdparty-content %}} </ins> ## {{% heading "prerequisites" %}}

Discussion:
Per our discussion in today's SIG Docs: Sections of the site, like will always have some degree of 3rd party content, due to the fact that a k8s developer must implement an external networking CNI. The majority of post-3rd party content KEP PR's we get that actually involve third party content are to pages like this one. A part of the reasons is that a change like the KEP requires initial communication (which was well done) but also ongoing communication. This change proposes the following: Create a reusable Note or similar shortcode for pages that fall under . The note should: Be translatable (use a key) Warn people that they must use a 3rd party plugin/software for this step Indicate that per the projects are listed alphabetically Indicate that additions to this list/page must directly provide a solution for this step of an implementation (i.e. for the cluster networking page, projects listed must provide a networking solution – no 'nice to haves' that make networking easier or somehow nicer.) Link to the content guidelines for more info on acceptable additions to the page.
/assign /area web-development /priority important-longterm
/language en
Wording for review: This section contains links to third party projects which provide functionality required by Kubernetes. The Kubernetes project authors are not responsible for these projects. Projects are listed alphabetically, in accordance with [CNCF website guidelines]. To add a project to this list, read the <a href="/contribute/style/content-guide/#third-party-content"content guide</abefore submitting a change.
Related:
How about:
LGTM, I'll go ahead and implement. Thank you for the edit!
Hello , Some late feedback (sorry I missed the meeting): Since this is a "special" note, I think it warrants a different color on the left hand border. Is there another shortcode besides note or warning that could be used to set off the text? Could substitute the shortcode "Note" text with "Third party content"? The language in the third party content message is a bit obtuse. When this label is applied, can the reader assume that all content on the page falls under these guidelines? This sentence, "Kubernetes project authors are not responsible for these projects" seems repetitive. Third party implies an external source and outside of the project's domain.

Is there another shortcode besides note or warning that could be used to set off the text? Could substitute the shortcode "Note" text with "Third party content"? All good feedback. How would you phrase it differently?
Hi. I am not entirely sure. The text is okay, though, it may not be clear about what is "required for Kubernetes to function". What do you want readers to do: determine if their project belongs in the section (read the content guide) read the content as third party content (Sig Docs is hosting the links but not responsible for the content on the page)? [One idea:] This section links to third party projects and follows [CNCF website guidelines] by listing projects alphabetically. [Do you want to suggest adding content or not?] If you are considering adding content in this section, read the before submitting a change. [Do you need a statement about content responsibility?]
Is there another shortcode besides note or warning that could be used to set off the text? Could substitute the shortcode "Note" text with "Third party content"? I think this is a good suggestion. I'll update the PR. What do you want readers to do: This section links to third party projects and follows [CNCF website guidelines] by listing projects alphabetically. If you are considering adding content in this section, read the content guide before submitting a change. Is this blocking for the PR? If we can't come up with a concrete alternative, I'd prefer to merge the PR, re-open this issue, and continue to work on the wording. Would that be okay,
Sure . I think what you have is fine. As an aside, did you consider using the theme's shortcode (which has a parameter)? It may work as well as wrapping the "third party content" shortcode in a note/warning shortcode. I think you can set the attribute too.
I'm imagining a one-line shortcode that, when rendered, closely matches the styles of existing callouts. I'd rather not use callouts from the Docsy theme because that's different from our existing callouts (something to handle in a separate issue, I feel). Wording-wise I'm happy to see something merged and leave room to iterate. Would you be happy to implement that?
Hi.

I agree, let's get this change moving forward with a single line shortcode with similar styling to the existing callouts. The shortcode would use two template strings: one variable for the message title and another variable for the message body. In the future, I could imagine a flexible interface or more generic shortcode that accepts at least one argument: the name of the variable representing the message title.