docs: flip TOML and envvars order (#2389)

docs/extra.css

@@ -45,6 +45,42 @@ h1, h2, h3, h4, h5, h6 {
     border-bottom: 1px solid  #e1e4e5;
     margin-bottom: 0.8em;
     padding-bottom: 0.2em;
+    scroll-margin: 1.5em 0;
+}
+
+/* make it so tables can overflow the content area, make the most of the content area */
+.wy-nav-content-wrap {
+  container-type: inline-size;
+}
+.wy-table-responsive {
+  overflow-x: auto;
+  overflow-y: hidden;
+  position: relative;
+  left: -3.236em;
+  max-width: calc(100cqw);
+  width: fit-content;
+  min-width: calc(100% + 3.236em + 3.236em);
+}
+.rst-content .section .wy-table-responsive .docutils {
+  padding-left: 3.236em;
+  padding-right: 3.236em;
+}
+.rst-content .section .wy-table-responsive .docutils thead,
+.rst-content .section .wy-table-responsive .docutils tbody {
+  background-color: white;
+}
+@media screen and (max-width: 768px) {
+  .wy-table-responsive {
+    left: -1em;
+  }
+  .rst-content .section .wy-table-responsive .docutils {
+    padding-left: 1em;
+    padding-right: 1em;
+  }
+}
+
+.wy-nav-content {
+  max-width: 900px;
 }
 
 .rst-content blockquote {

docs/setup.md

@@ -23,7 +23,24 @@ cibuildwheel
 !!!tip
     You can pass the `--platform linux` option to cibuildwheel to build Linux wheels, even if you're not on Linux. On most machines, the easiest builds to try are the Linux builds. You don't need any software installed except a Docker daemon, such as [Docker Desktop](https://www.docker.com/get-started/). Each platform that cibuildwheel supports has its own system requirements and platform-specific behaviors. See the [platforms page](platforms.md) for details.
 
-You should see the builds taking place. You can experiment with [options](options.md) using environment variables or pyproject.toml.
+You should see the builds taking place. You can experiment with [options](options.md) using pyproject.toml or environment variables.
+
+!!! tab "pyproject.toml"
+
+    If you write your options into [`pyproject.toml`](configuration.md#configuration-file), you can work on your options locally, and they'll be automatically picked up when running in CI.
+
+    > pyproject.toml
+
+    ```
+    [tool.cibuildwheel]
+    before-all = "uname -a"
+    ```
+
+    Then invoke cibuildwheel, like:
+
+    ```console
+    cibuildwheel
+    ```
 
 !!! tab "Environment variables"
 
@@ -46,23 +63,6 @@ You should see the builds taking place. You can experiment with [options](option
     cibuildwheel
     ```
 
-!!! tab "pyproject.toml"
-
-    If you write your options into [`pyproject.toml`](configuration.md#configuration-file), you can work on your options locally, and they'll be automatically picked up when running in CI.
-
-    > pyproject.toml
-
-    ```
-    [tool.cibuildwheel]
-    before-all = "uname -a"
-    ```
-
-    Then invoke cibuildwheel, like:
-
-    ```console
-    cibuildwheel
-    ```
-
 - Once you've got a build working locally, you can move on to [setting up a CI service](ci-services.md).
 - View the [full options reference](options.md) to see what cibuildwheel can do.
 - Check out the [FAQ](faq.md) for common questions.