Link to the regression tests in some more places

_layouts/regrtests_results.html

@@ -99,21 +99,21 @@ <h2 class="font-secondary">Summary:</span>
 
                 {% if case.result %}
                 <div class="cell  {{case.result }} results-case-list-item  text-mobile-right">
-                  <span class="text-small text-muted d-mobile-none">RESULT:</span>
+                  <span class="text-small text-muted d-mobile-none">RESULT: </span>
                   <span class="case-result">{{case.result }}</span>
                   {%- if case.result == "skipped" -%}
                     {%- assign note = case.note | default: result.note-%}
                     {%- assign lownote = note | downcase -%}
                     {%- if lownote contains "todo: rustpython" -%}
                       {%- assign note = lownote | remove: "todo: rustpython," | remove: "todo: rustpython:" | remove: "todo: rustpython" | strip -%}
                       {%- if note and note != "" %}
-                        <span class="text-small text-muted d-mobile-none">TO RESOLVE:</span>
+                        <span class="text-small text-muted d-mobile-none">TO RESOLVE: </span>
                         <span class="d-mobile-none case-note">{{ note }}</span>
                       {%- endif -%}
                     {%- elsif note == "implementation detail specific to cpython" -%}
                         <span class="text-small text-muted d-mobile-none">(CPython only)</span>
                     {%- else -%}
-                        <span class="text-small text-muted d-mobile-none">not skipped by us:</span>
+                        <span class="text-small text-muted d-mobile-none">not skipped by us: </span>
                         <span class="text-small d-mobile-none case-note">{{ note }}</span>
                     {%- endif -%}
                   {%- endif -%}

_posts/2020-04-05-how-to-contribute-by-cpython-unittest.markdown

@@ -13,6 +13,8 @@ Let's find an incompatibility issue and fix it.
 
 1. See `Lib/test` directory of the project. There are many `test_` prefixed files like `test_unicode.py`.
 2. Try to open one of them. It might look just fine at a glance - but search for `TODO: RUSTPYTHON` in the files. There are tons of skipped, marked as an expected failure or commented out tests.
+  1. Alternatively, try looking at the [regression tests results]({% link pages/regression-tests-results.markdown %}) to find skipped ones; some of them have
+     notes for a way to resolve the issue.
 3. Choose one or two interesting bugs. Remove the test blocker - skip, expectedFailure or comments.
 4. Try to fix them.
 

assets/style.css

@@ -324,6 +324,10 @@ ul.list-inline {
     content: "  🤷‍♀️";
 }
 
+.case-result::after {
+    margin-right: 5px;
+}
+
 /* filters */
 
 .filter {

index.markdown

@@ -36,6 +36,10 @@ Each of these implementations offer some benefits: Jython, for example, compiles
 
 IronPython is well-integrated with .NET, which means IronPython can use the .NET framework and Python libraries or vice versa.
 
-We want to unlock the same possibilities that Jython and IronPython enable, but for the Rust programming language. Then we want to do more. Using RustPython, we want to compile Python to WebAssembly and allow users to run their Python code natively in the browser.  
+We want to unlock the same possibilities that Jython and IronPython enable, but for the Rust programming language. In addition, thanks to Rusts' minimal runtime, we're able to compile RustPython to WebAssembly and allow users to run their Python code easily in the browser.
 
 Check the "learn more" section for an explainer of all those jargon-y words, or read the blog for more in-depth technical discussion.
+
+### Other Resources
+
+- [CPython test compatibility]({% link pages/regression-tests-results.markdown %})