Summary

Tutorials utilizing just Liquid logic is considered safe since Liquid is inherently non-evaling. However, tutorials with Ruby code to be used as plugins cannot be deemed safe without proper review and test-coverage.
Therefore, place a disclaimer to indirectly state that the user discretion is recommended.

The disclaimer is not rendered by default. Tutorials with Ruby code need to explicitly enable it via the front matter:

plugin_disclaimer: true

While testing this in the context of #8521, I noticed that it wasn't using the CSS I expected. Seems like this should have the regular "note" class applied...

the regular "note" class applied..

@chrisfinazzo I chose to go with the bronze+chocolate-brown palette so that it is subtle and doesn't pop right out at the visitor (like the sky-blue or red note boxes on other pages) especially since the info within is not directly related to the topic of the page.
Whatsay? Change it anyways?

the regular "note" class applied..

@chrisfinazzo I chose to go with the bronze+chocolate-brown palette so that it is subtle and doesn't pop right out at the visitor (like the sky-blue or red note boxes on other pages) especially since the info within is not directly related to the topic of the page.
Whatsay? Change it anyways?

Oh, I see.

This is actually the color scheme I was thinking of, just couldn't tell at first glance. Unless I missed it, I don't see the .disclaimer-ribbon class applied elsewhere, so it made more sense to use .note in a form in which it already exists - for example, at the bottom of the Troubleshooting page.

@jekyllbot: merge +doc