Feature request: Stack Snippet

Question

It is possible to get the feature Stack Snippet also on WPSE?

At first I think is the default much helpful for snippets with html, css, javascript. Perhaps is enhancement to work with a WordPress back end inside the load of requirements helpful to demonstrate with WordPress core functions.

I think is much helpful to understand the answers, the snippets and easy to see how it works. Currently we use often jsfiddle or similar.

Why?

Every question is better for having minimal, reproducible code. Right now the best way to tell people to do that is to point them to JSFiddle, which is off-site. Using this feature, we plan to push new posters to embed runnable code that reproduces their problem.

Similarly, answers that include runnable code are easier to use and understand, because you can try them out. Obviously JSFiddle is hugely popular in answers already, so we just wanted to make it even easier to use.

Obviously the same rules apply: code-only questions or answers will still be blocked (and, in fact, because of how it's implemented all the existing checks will just work out of the box).

Answer 1

Recently, our VP of Engineering looked at a similar request on GIS:

I think it wasn't totally obvious from the initial release that snippets are really only for JS/HTML/CSS code (a replacement for jsfiddle.net, basically). A good indicator of whether they'll be useful on a site is the number of answers with javascript in them, and especially posts linking to jsfiddle.

Currently, 126 posts link to jsfiddle.net and of the 58,911 questions, just 867 are tagged javascript. So from what I see, WordPress doesn't really deal with Javascript enough to be an ideal candidate for this feature. Since snippets are often misunderstood, you might find the feature more annoying then beneficial.

We are looking at combining the code and snippet shortcuts, which might make the feature more palatable on sites that don't embed JavaScript very often. But there's no guarantee it will eliminate confusion.