Add LessonHeader to each of the fundamentals.

Author: briangershon

pages/lessons/fundamentals/cli_lesson.mdx

@@ -5,7 +5,9 @@ icons: []
 authors: ['piablo', 'georgemac510']
 ---
 
-## Navigating in a CLI for beginners
+import { LessonHeader } from '../../../components/mdx/LessonHeader'
+
+<LessonHeader title="Navigating in a CLI for beginners" />
 
 A CLI is an invaluable tool for development. It's actually quite straightforward to use, but just a bit tricky to get used to initially. You can't see everything readily, like you would in your computer's graphical user interface, but we'll teach you how to **navigate** the pathways, so you can get around easily. CLI stands for **C**ommand **L**ine **I**nterface. Generally speaking, Linux users call a CLI a terminal, Mac users call it a console, Windows users a shell. All these names have some technical differences, and we are going to stick with CLI for now. Happy travels! 
 

pages/lessons/fundamentals/code-editors.mdx

@@ -6,7 +6,9 @@ icons: []
 author: 'georgemac510'
 ---
 
-# Code Editors (IDEs)
+import { LessonHeader } from '../../../components/mdx/LessonHeader'
+
+<LessonHeader title="Code Editors (IDEs)" />
 
 ## What is an IDE?
 

pages/lessons/fundamentals/connect-with-rpc.mdx

@@ -5,7 +5,9 @@ icons: []
 author: 'georgemac510'
 ---
 
-# Connecting to a Network via RPC
+import { LessonHeader } from '../../../components/mdx/LessonHeader'
+
+<LessonHeader title="Connecting to a Network via RPC" />
 
 **Remote Procedure Call (RPC)** could be classified as a type of API
 (application programming interface) that allows for developers to run code that

pages/lessons/fundamentals/decentralized-storage.mdx

@@ -5,7 +5,9 @@ icons: []
 author: ['georgemac510', 'pbillingsby']
 ---
 
-# Decentralized Storage with Arweave and IPFS/Filecoin
+import { LessonHeader } from '../../../components/mdx/LessonHeader'
+
+<LessonHeader title="Decentralized Storage with Arweave and IPFS/Filecoin" />
 
 Among the many use cases for these great technologies, the most common are for
 storage of image, audio and video NFTs as well as deploying web dApps. Here are two protocols that specialize in decentralized data storage.

pages/lessons/fundamentals/install-npm.mdx

@@ -5,7 +5,9 @@ icons: []
 author: 'georgemac510'
 ---
 
-# How to install node.js and npm
+import { LessonHeader } from '../../../components/mdx/LessonHeader'
+
+<LessonHeader title="How to install node.js and npm" />
 
 ![NPM Overload Joke](/assets/lessons/install_npm/npm-jokes-1.png)
 

pages/lessons/fundamentals/nft-hosting.mdx

@@ -6,8 +6,9 @@ icons: []
 author: 'georgemac510'
 ---
 
-# NFT hosting through OpenSea and Rarible
+import { LessonHeader } from '../../../components/mdx/LessonHeader'
 
+<LessonHeader title="NFT hosting through OpenSea and Rarible" />
 
 ## What are NFTs?
 

pages/lessons/fundamentals/open_zeppelin.mdx

@@ -5,7 +5,9 @@ icons: ['openzeppelin']
 author: ['piablo', '7i7o']
 ---
 
-# Open Zeppelin Smart Contract Concepts
+import { LessonHeader } from '../../../components/mdx/LessonHeader'
+
+<LessonHeader title="Open Zeppelin Smart Contract Concepts" />
 
 We are going to stand on the shoulder of giants and leverage the power of open
 source to create our project in a simpler way, while not losing focus on

pages/lessons/fundamentals/testnets.mdx

@@ -5,7 +5,9 @@ icons: []
 author: 'piablo'
 ---
 
-# Test, test, test, testnets
+import { LessonHeader } from '../../../components/mdx/LessonHeader'
+
+<LessonHeader title="Test, test, test, testnets" />
 
 **TL'DR**
 

pages/lessons/fundamentals/token-standards.mdx

@@ -5,10 +5,11 @@ icons: ['ethereum']
 author: 'piablo' 
 ---
 
-
 **LEGO and our digital Web3 realm…..**
 
-# What are token standards and why do we need them?
+import { LessonHeader } from '../../../components/mdx/LessonHeader'
+
+<LessonHeader title="What are token standards and why do we need them?" />
 
 There is an analogy used in the Web3 world that a blockchain such as Ethereum, Polkadot, or Solana is a platform for money-LEGOs. When audited contracts, DeFi protocols, crypto tokens, etc all have recognisable standards across the eco-system, it guarantees that they can inter-operate smoothly with each other. So when crypto tokens are designed, we need to make sure the infrastructure on the blockchain, e.g. crypto *wallets* can communicate with them. We therefore ensure that the whole system is composable, just like Lego blocks.
 

pages/lessons/fundamentals/wallets.mdx

@@ -6,7 +6,9 @@ icons: []
 author: ['piablo', 'Meowy']
 ---
 
-# Web3 wallets, and public and private keys....
+import { LessonHeader } from '../../../components/mdx/LessonHeader'
+
+<LessonHeader title="Web3 wallets, and public and private keys..." />
 
 ### What do we have in store?