Skip to content

Commit 911fbcf

Browse files
committed
fix emoji on lesson and icon for foundry
1 parent 9cbe17f commit 911fbcf

File tree

2 files changed

+11
-20
lines changed

2 files changed

+11
-20
lines changed

pages/lessons/projects/6.mdx

Lines changed: 11 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,11 @@
11
---
22
i18n: 'erc20'
3-
title: Your own Token w/Foundry
3+
title: Your own Token with Foundry
44
description:
55
Create and deploy an ERC20 Token (UNI, MKR, DAI, etc.) using the Foundry
66
toolkit.
77
icons:
88
[
9-
'git',
109
'solidity',
1110
'foundry',
1211
'openzeppelin',
@@ -63,10 +62,7 @@ Some basic functionality that our tokens need to provide are:
6362
- Approve an amount of tokens from an account to be spent by a third-party
6463
account
6564

66-
<!-- Side Drawer -->
67-
68-
<details>
69-
<summary>More info on the ERC20 Standard</summary>
65+
<SideDrawer buttonText="More info on the ERC20 Standard">
7066

7167
To achive the functionality needed for an ERC20 token, the standard requires us
7268
to implement 9 methods and 2 events.
@@ -94,16 +90,14 @@ event Approval(address indexed _owner, address indexed _spender, uint256 _value)
9490
You can check the details in the full EIP-20 titled
9591
[ERC-20: Token Standard](https://eips.ethereum.org/EIPS/eip-20#token)
9692

97-
</details>
93+
</SideDrawer>
9894

9995
## Has someone created a battle-tested library for the standard?
10096

10197
Yes. OpenZeppelin (among others) has created an implementation we can inherit to
10298
create
10399
our own tokens easily.
104100

105-
<!-- Open Zeppelin Side Drawer / Callout -->
106-
107101
## Let's code, but first...
108102

109103
Before we start hacking away without any structure to follow, what is our
@@ -112,11 +106,11 @@ project's structure and what do we want to achieve?
112106
Since we are _BUIDLING_, i'd like to think of our project, or smart contract,
113107
the same way as we would _roughly_ build a house:
114108

115-
- 1. Foundations
116-
- 2. Structure: Framing, Walls and Roof
117-
- 3. Doors and Windows
118-
- 4. Security
119-
- 5. Final touches
109+
* 1 - Foundations
110+
* 2 - Structure: Framing, Walls and Roof
111+
* 3 - Doors and Windows
112+
* 4 - Security
113+
* 5 - Final touches
120114

121115
Before we build, we need a stable, leveled surface to place our foundations so
122116
we can build on top.
@@ -504,10 +498,7 @@ locked (only) for intruders!
504498

505499
Congratulations! We have built a fully functioning token!
506500

507-
<!-- Side Drawer -->
508-
509-
<details>
510-
<summary>Here's my final Solidity code</summary>
501+
<SideDrawer buttonText="Here's my final Solidity code">
511502

512503
Here we have our fully functioning house, I mean... token:
513504

@@ -542,7 +533,7 @@ contract MyToken is ERC20, AccessControl {
542533
}
543534
```
544535

545-
</details>
536+
</SideDrawer>
546537

547538
Given that we have our house completed, you might want to add a personalized
548539
detail to it, like a special furniture, wall paint, or make it a smart home.
@@ -787,4 +778,4 @@ be live and kicking.
787778

788779
Now that we have built our house and it's has been accepted in the real estate
789780
register, we can invite our friends by transferring them some MTK, or **even**
790-
minting them some tokens, even if that affects your tokenomics :wink:
781+
minting them some tokens, even if that affects your tokenomics 😉

public/assets/foundry.png

14.2 KB
Loading

0 commit comments

Comments
 (0)