Update June 5, 2025
Snippets is now live on Stacks Editor. While this integration was mainly for feature parity, we did make some improvements so that the feature would run smoothly with the new Stacks Editor:
Key improvements:
- Improved support for the previously listed front-end tags.
- Fixed remaining bugs and introduced various performance improvements.
- Added a new icon and popover to make Snippets more discoverable.
This feature is now available for immediate use, with the deployment happening across two closely timed stages early on Thursday June 5:
- First, all users who use Stacks editor will see Snippets available
- Then, the front-end tags that never had Stacks Editor will see the Stacks Editor + Snippets We want to be clear about the two-stage rollout, in case anyone happens to experience something odd in between.
Let us know your thoughts!
Update April 21, 2025
Originally, today was slated to mark the launch of the Snippets working group. However, due to low interest and signups, we have decided to cancel this initiative. While this adjustment was unexpected, it allows us to reassess and improve how we engage with the community on future iterations.
We are currently in the internal testing phase of Snippets and look forward to sharing more details with you soon. Community feedback remains a vital part of our process. Once the Snippets integration is officially rolled out, we will welcome feedback and bug reports to be reported directly on Meta.
Stack Snippets, created a decade ago, is used to add runnable code to Q&A:
The goal of this feature is to encourage users to create minimally viable and functional code when asking code-centric questions. Answers could then be in the form of a stack snippet which resolved the question at hand. We hope that Stack Snippets enable people to not have to go to other websites in order to produce runnable code.
The goal of this rollout is to ensure feature parity by incorporating Stack Snippets into the Stacks Editor. In our previous rollout, the integration of Stack Snippets was out of scope, restricting functionality for frontend code tags such as:
javascript html css reactjs angular node.js jquery react-native next.js typescript tailwind-css
Although Snippets' core functionalities remain the same, we've enhanced them to ensure smooth operation in the new rich text editing environment. We are working to make sure this is a seamless integration, but we are still looking for your active feedback.
Announcing Stack Snippets for the Stacks Editor working group
It is important to us that we invest time into features that actively improve your experience when crafting answers. To better understand the needs of our contributors, we’re creating a working group to explore the updated Stack Snippets ahead of its addition to the Stacks Editor on Stack Overflow. So, we are looking for volunteers who regularly use Stack Snippets to join a private Teams instance to collaborate with us to refine the integration.
The working group is set to begin on April 21st, with the feedback phase continuing through mid-May.
Important Info for You to Know:
We have employed working groups in the past, and this one will operate pretty much the same meaning:
- Feedback and discussions will take place in a private instance of Stack Overflow for Teams.
- The development team—Community Managers, Developers, Product Managers, and Designers—will work closely with volunteer reviewers to respond to bug reports, feature requests, and feedback.
- To volunteer as a reviewer and join discussions, please complete this form. (It shouldn’t take more than a few minutes!)
- Those who sign up to be reviewers will receive an invite before the start date of April 21st. We’ll notify the community once all invitations are sent.
We highly value the feedback we receive from Meta; however, for this stage of testing, we’ve chosen to move the process to a private Teams instance. This decision isn't meant to exclude Meta but rather to create an environment where we can collaborate and iterate in real-time with the community on this version prior to release. Following internal testing, we plan to transition to a public general release, where members of the Meta community can provide feedback.
