The sixth Community Asks Sprint, which is the final one of 2025, has now concluded. The focus was on site design and usability, and we got a number of requests for things to improve. The first ask we decided to take on was not actually raised on the announcement post, but it is something that has been needing to be addressed for quite a while and I am happy to announce that we ultimately found a way to get it done.
Issues addressed during this sprint
Copy Button on Stack Overflow - As of today, users will be able to copy blocks of code directly from posts on Stack Overflow, by clicking the new Copy button in the top right corner of the code block: The copy will include three lines of attribution, which will be rendered as comments using the format appropriate for the language of the code block in question. This is something users have been asking for for almost as long as Stack Overflow has been around. We are rolling it out first on Stack Overflow, but there is potential to add it to other tech sites in the future.
Spoiler accessibility improvements - We made spoilers tabbable so you don’t need to use the mouse cursor to access them, and added the option to hit "enter" to reveal them when they're focused. These changes will apply to all sites that use spoilers.
Spoilers in comments - We have also introduced spoilers in comments, which we will be testing out first on Puzzling Stack Exchange. The syntax for comment spoilers is [!spoiler goes here!] . Once we make sure they are working appropriately on Puzzling, we will turn them on for other sites that use spoilers.
We would have liked to be able to get to more than a handful of asks during this sprint, but the Copy button turned out to be quite a big issue to tackle. Though this wasn’t something the community requested us to address during this specific sprint, we do feel like this represents a big benefit to users, making life easier for everyone who uses Stack Overflow to solve problems. We can also enable this feature on other tech sites that use code blocks, let us know here if this functionality would benefit other Stack Exchange communities.
Bug reports about the copy button can be made directly as an answer to this post, or linked here if a bug report is posted separately on MSO (or MSE).
What’s next?
I’m glad that, in addition to the copy button, we were also able to make spoilers more accessible to use on the sites where they are a crucial feature. However, there were a lot more requests made than we were able to complete this sprint, so we will share the rest of the asks from the announcement post with teams running Community Asks Sprints in the future. The next Community Asks Sprint will be after the new year, and we look forward to continuing to make improvements to users' experience on the Stack Exchange network in 2026. We will announce the date for the next sprint once we have it.