Make most tables not wrap on small screens

content/blog/01_types_basics.md

@@ -428,6 +428,7 @@ and already be up-to-speed on a big chunk of the content.
 {{< /block >}}
 
 #### Rules
+{{< foldtable >}}
 | Rule         | Description |
 |--------------|-------------|
 | {{< latex >}}s : \text{string} {{< /latex >}}| String literals have type \\(\\text{string}\\) |

content/blog/10_compiler_polymorphism.md

@@ -64,6 +64,7 @@ rules work together below.
 {{< /sidenote >}} I will also give a quick
 summary of each of these rules.
 
+{{< foldtable >}}
 Rule|Name and Description
 -----|-------
 {{< latex >}}

content/blog/coq_dawn.md

@@ -219,6 +219,7 @@ Here, we may as well go through the three constructors to explain what they mean
 Now it's time for some fun! The UCC language specification starts by defining two values:
 true and false. Why don't we do the same thing?
 
+{{< foldtable >}}
 |UCC Spec| Coq encoding |
 |---|----|
 |\\(\\text{false}\\)=\\([\\text{drop}]\\)| {{< codelines "Coq" "dawn/Dawn.v" 41 42 >}}
@@ -257,6 +258,7 @@ element, as specified. The proof for \\(\\text{true}\\) is very similar in spiri
 
 We can also formalize the \\(\\text{or}\\) operator:
 
+{{< foldtable >}}
 |UCC Spec| Coq encoding |
 |---|----|
 |\\(\\text{or}\\)=\\(\\text{clone}\\ \\text{apply}\\)| {{< codelines "Coq" "dawn/Dawn.v" 65 65 >}}

themes/vanilla

@@ -1 +1 @@
-Subproject commit c5a28bf7ef0ea0ec4f534cf2bff231d1ad43bcea
+Subproject commit 869f9d12c84ebf38fe8f21611af9d3bf7ff5ea0d