move build system idea toward the top

README.md

@@ -19,6 +19,9 @@ and we will give you feedback.
 
 [Library for Data-Over-Audio Communication](#data-over-audio-messaging)
 
+
+[Save Us From Our Monstrously Complex Build System](#improve-our-monstrously-complex-build-system)
+
 Completed Projects From Previous Years
 --------------------------------------
 
@@ -53,7 +56,6 @@ Older Project Ideas
 
 [Worst of All Possible Worlds Interpreter](#worst-of-all-possible-worlds-interpreter)
 
-[Improve Our Monstrously Complex Build System](#improve-our-monstrously-complex-build-system)
 
 Web App UI Cleanup
 ------------------
@@ -238,6 +240,25 @@ is usually referred to as Pd.) However, the library may also be written in
 C, or C++.
 
 
+Improve Our Monstrously Complex Build System
+--------------------------------------------
+
+### Goal
+* simplify the build system so that it is intelligible to humans, especially
+new developers. Make it possible to build both the core of Purr Data and an
+an installer binary in less time than it currently takes.
+* improve the CI runners so they are easier to set up, maintain, and run
+* find a way for us to automate our release process
+
+### Challenges
+The build system uses many recursively-called Makefiles and even downloads
+a binary of the GUI toolkit using a wrapper script. While Purr Data does
+have regression testing, we don't currently check for things like making
+sure all the help documentation got installed correctly, or even that
+every single external library ships. It's quite dangerous even to make
+small changes to such complex makefiles, so some testing will need to be
+implemented to ensure that this project is a success.
+
 Core Accessibility
 ------------------
 
@@ -612,21 +633,4 @@ Etc.
 
 
 
-Improve Our Monstrously Complex Build System
---------------------------------------------
 
-### Goal
-* simplify the build system so that it is intelligible to humans, especially
-new developers. Make it possible to build both the core of Purr Data and an
-an installer binary in less time than it currently takes.
-* improve the CI runners so they are easier to set up, maintain, and run
-* find a way for us to automate our release process
-
-### Challenges
-The build system uses many recursively-called Makefiles and even downloads
-a binary of the GUI toolkit using a wrapper script. While Purr Data does
-have regression testing, we don't currently check for things like making
-sure all the help documentation got installed correctly, or even that
-every single external library ships. It's quite dangerous even to make
-small changes to such complex makefiles, so some testing will need to be
-implemented to ensure that this project is a success.