Merge pull request #476 from danidoni/blog-post-for-sprint-176

Blog post for Spring 176

_includes/partials/_series-of-posts-about-request-redesign.md

@@ -10,5 +10,4 @@ In July 2023 we introduced [Set Bugowner action and diff comments for non-beta u
 In September 2023 we focused on [Build Results Summary Gets Into Shape](/2023/09/08/request-workflow-redesign).
 Later 2023, in November, we added the [Build Status Refresh and Other Insights on Our Request Page](/2023/11/30/introducing-build-status-refresh-and-other-insights-in-our-request-page).
 The year 2024 started with [Revamping the Request Build Status Page and Introducing the Dark Mode](/2024/01/25/revamping-the-build-status-page-and-introducing-the-dark-mode).
-We continued in February with [Build Results Summary Chart Links to Build Results Overview](/2024/02/19/build-results-summary-chart-links-to-build-results).
-And now we did some [Improvements On the Redesigned Request Page](/2024/04/08/improvements-on-the-redesigned-request-page).
+We continued in February with [Build Results Summary Chart Links to Build Results Overview](/2024/02/19/build-results-summary-chart-links-to-build-results) and in April with [Improvements On the Redesigned Request Page](/2024/04/08/improvements-on-the-redesigned-request-page).

_posts/development/2024-10-23-make-it-easier-for-users-to-understand-what-is-there-on-a-request.md

@@ -0,0 +1,39 @@
+---
+layout: post
+title: 3 Improvements For Collaboration on the Request Page
+category: development
+---
+Today we want to tell you about three significant improvements we have just introduced that make it easier to collaborate on the request page. Those improvements are part of the [beta program](/2018/10/04/the-beta-program/).
+
+{% include partials/_series-of-posts-about-request-redesign.md %}
+
+## More Clarity on the Diffs
+
+The diff tab now shows small highlights (called eyecatchers) that show the exact change. Those eyecatchers will help you see what exactly is new or changed and allow you to focus better on those differences, making it easier to review the request.
+
+<figure>
+  <img src="/images/posts/2024-10-23/eyecatchers.png" alt="Eyecatchers in a file diff" />
+  <figcaption>Eyecatchers in a file diff</figcaption>
+</figure>
+
+## Less Clutter in Conversations
+
+Before we had two boxes on the conversation timeline: if you wanted to write a comment, you had to find the comment box, if you wanted to give a reason because you declined something you had to find the decision box. Now, you only have one box, so you don't have to think where you write things anymore because there is no choice!
+
+<figure>
+  <img src="/images/posts/2024-10-23/decision_and_comment_boxes_combined.png" alt="Review decisions and comment boxes combined" />
+  <figcaption>Review decisions and comment boxes combined</figcaption>
+</figure>
+
+## Less Noise in the Build Results
+
+The build results of a request were showing a lot of information that is not really useful to decide if you should merge the request or not, like the "Excluded" state. We limited the build results in the overview to succeeded/failed and building now. This will make easier for you to understand the state of the request and help you make a decision about it.
+
+<figure>
+  <img src="/images/posts/2024-10-23/better_build_results.png" alt="Better build results" />
+  <figcaption>Better build results</figcaption>
+</figure>
+
+We hope those changes will help you focus better on the important bits of a request. As always we are eager to know what do you think about this!
+
+{% include partials/_how-to-give-us-feedback.md %}