numbered folders :)

program-basics/hello-solana/anchor/programs/hello-solana/src/lib.rs → 1-program-basics/1-hello-solana/anchor/programs/hello-solana/src/lib.rs

@@ -9,6 +9,8 @@ pub mod hello_solana {
     pub fn hello(ctx: Context<Hello>) -> Result<()> {
         
         msg!("Hello, Solana!");
+
+        msg!("Our program's Program ID: {}", &id());
         
         Ok(())
     }

program-basics/hello-solana/native/program/src/lib.rs → 1-program-basics/1-hello-solana/native/program/src/lib.rs

@@ -25,5 +25,7 @@ fn process_instruction(
     
     msg!("Hello, Solana!");
 
+    msg!("Our program's Program ID: {}", &program_id);
+
     Ok(())
 }

1-program-basics/4-custom-instruction-data-expanded/README.md

@@ -0,0 +1,7 @@
+# Custom Instruction Data - Expanded
+
+:gem: Here's where Anchor really shines. :gem:   
+
+You'll notice in these examples that the `native` version of the program is much more verbose on the client side - due to the fact that we have to re-create every custom data type from our Rust code.   
+
+This is one of Anchor's greatest features. The framework will extract all of that information out of the Rust source and into JSON and TypeScript files. This makes it much easier and more dynamic to re-create these data types on the client side. Although it's still necessary to do (which can be trivial), it's >100x easier with Anchor.

README.md

@@ -48,9 +48,8 @@ How to build & run:
 - ### Program Basics
 - [x] 1. Hello Solana
 - [x] 2. Custom instruction data
-- [] 3. Instruction accounts
-- [] 4. Recommended program layout
-- [] 5. Custom instruction data expanded
+- [x] 3. Recommended program layout
+- [x] 4. Custom instruction data expanded
 - ### Accounts
 - [ ] 1. Creating a system account
 - [ ] 2. Modifying an account's data