Update 'README.md'

README.md

@@ -5,18 +5,25 @@ This is intended to be commited to incrementally,
 stubs can/should be added to existing docs where applicable,
 ideas for future trees can be submitted as new .md
 
-## Where We're At
+## Selected topics
-All topics need related library articles aggregated, sorted by rough skill level
-- Beginner
-- Intermediate
-- Hard
 
-`http_to_phy.md`  
+### [HTTP to Physical](http_to_phy.md)
-WIP for "How do I understand how an HTTP message is sent at a deep level?"  
+
-Needs:  
+How does a web request actually get from A to B?
+
+TODO:
 - Better links to topics
 - Editing pass / blurb cleanup
 
+### [Compilers: How To Make a Programming Language](compilers.md)
+
+How do I make a simple programming language?
+
+TODO:
+- More links, lots for each section
+
+## Other topic ideas
+
 `asm.md`  
 WIP for "How do I understand what my computer is really doing at the bottom level?"  
 (Better question for this one? Should this be a subtopic instead?)  
@@ -30,17 +37,13 @@ Needs:
 - Subtopics broken out
 - Header blurb
 
-`compilers.md`  
+## Technical Design
-WIP for "What do compilers actually do?"  
+
-Needs:  
+See Notion: https://handmade-network.notion.site/Education-24259fc59b5e4101b89834451f0c3e98
-- Subtopics defined concretely for the learning flow
-- Header blurb
 
 ## Scratch Notes
+
 Try to mark down potential useful cross-topic links as you go, we'll try to
 populate and cross pollinate as articles get ready to ship
 
 Is it possible to get the library archive accessible to filter through for resource ideas?
-
-Anything we need from the site technically?
-Backlinks? Past-article stack? Limited multi-user access right control?