Questions to answer in V2

🎨 Figma designs link 🖌️

Storing user details and progress (including rationale)

• piablo user back-end storage ⇒
  1. I believe we should store the checkpoint quizzes and final quiz and aggregate their total score, but maybe I haven’t thought deeply about potential problems. What are the pitfalls from the proposed approach?
  2. What about browser session storage? What needs to get stored (if at all) in there?

Design and Development of all quiz structures

• piablo what type of architecture can we use for checkpoint questions?
  1. personally I still love the smooth side-drawer experience, like sliding a book in or out of a shelve (therapeutic for me) ⇒ how would a side-drawer work architecturally on v2?
  2. pages ⇒ would these pages appear and disappear in the same way our present side-drawers work?
  3. pop-ups ⇒ personally I’m not a fan of pop-ups because of their traditional ‘pop’ aspect - I find it sudden and therefore distracting. But maybe there is a smoother way of building them?
• piablo final-quiz ⇒
  1. can we, or should we use the same architecture as checkpoints for final quizzes?

SEO and Semantics

• piablo when do we introduce the idea of SEO friendly directory/file structure naming for v2
  • Which part of the file structure should we concentrate on? Please give an e.g. …
  • does this affect other parts of logic and where? give e.g. …
  • do we need to create PRs to make adjustments?
• piablo n.b. edit: do we change ALL of the titles and descriptions in front matter, <Layout> and <LessonHeader> components to match? It seems reasonable that we do, since we point the learner to them semantically in the body of the lesson (primarily, but not exclusively in the intros and outros)
• piablo how should we approach creating tags? e.g. beginner, fundamental, development, web3. You could go crazy with the categories.
  1. Is there maybe an algorithm, or programme that we could use to automate that?
  2. My reasoning would be to try and limit the amount of tags and not increase that number, is that a wise thought?

‘Stacking’ (sub)topics, quizzes, components in .mdx files meaningfully

• piablo placement of content text in relation to (sub) topics: checkpoints; side-drawers; final quiz is a bit messy at the moment. The left hand accordion menu will have gaps with ‘stray lines of text’ on the page between (sub)topics or checkpoints/final quiz. For me that’s a bit messy.

  • here is what it looks like now (05.12.2023):

  

  • One solution here we can relate the checkpoint that we are building to a ‘success’ message to the learner for after the checkpoint question
  • it would be nice to remove all the “Set the pomodoro/touch grass ⌛😊” messages from the actual page. We could possibly incorporate that in the ‘success’ message.

• below a table for seeing where checkpoint questions are in lessons - and (sub)topics that ‘meet’ or clash with those checkpoint questions and what type of message we could add… and how:

| | which checkpoint title? (open side-drawer to see) | what text is between? (the probable idea is to remove this text from page) | subsequent header? | possible update of checkpoint title? | possible success message? | | --- | --- | --- | --- | --- | --- | | lesson 1 | Warm-up Questions | How was that? + 2 side-drawers + Did you set the pomodoro? ⌛😊 | What are we going to do? | | | | | Blockchain and Solidity Smart Contracts | Well done! Now, go touch some grass! ⌛ | Now we begin writing our code | | | | | Variables and Functions | Go touch some grass and set the pomodoro when you return ⌛😊 | Events and dealing with on-chain storage | | | | | All about Events | Go touch some grass ⌛😊 | Compile & Deploy | | | | | | | | | | | | | | | | | | lesson 2 | Some previous knowledge, some prediction | How did you find that? No worries… | NO HEADER - the header is the MEME effectively | | | | | Creating a Robust Development Environment | n/a | Let’s start coding! | | | | | Solidity and Contracts in Context | Don't forget the pomodoro ⌛😊 | Mint… Feels Good | | | | | Creating NFT ID with the Power of Inheritence | n.b. here is a side-drawer to the ‘Longer Path (learn about JSON) | Deploy! Back to Solidity... kind of... | | | | Longer Path (learn about JSON and IPFS) side-drawer lesson | Web3 File Storage and Good Practices | p.s. Good for you for taking on this extra adventure! 🧙🏾 | n/a ….OR… actually Deploy! Back to Solidity… kind of… | | | | | Testing our Configurations with Scripts | Set your pomodoro ⌛😊 | Things just got real! | | | | | Adopting Wise Developer Practices | Ok. We are ready, let's deploy to … | 👈🏾 I think “Ok. We are ready….” is supposed to be the header. | | | | | | | | | | | | | | | | | | lesson 3 | Some previous knowledge, some prediction | How did that go? No pressure if there …. | Lesson breakdown | | | | | Minting Tiers with Solidity | ⌛ Pomodoro? 😊 🌱 | Create tokenURI function | | | | | Giving Personality and Access to our Tokens | ⌛ Pomodoro? 😊 🌱 | Time for our Deploy Script | | | | | Getting Our Tokens Out to the World | ⌛ Pomodoro? 😊 🌱 | Let’s mint! | | | | | | | | | | | | | | | | | | | | | | | | | lesson 4 | Check out Your Previous Knowledge | And set sail . . . | Why automated testing? | | | | | Understanding our Environment | ⌛ Pomodoro? 😊 🌱 | What do we want to test on our TierNFT contract? | | | | | General Testing Concepts | n/a = no text | Let's add tests for mint() | | | | | Cross-checking Logic from Tests to Contract | ⌛ Pomodoro? 😊 🌱 | Testing tokenURI() | | | | | Refactoring Code and Testing SVG | n/a | Food for Thought (ie. summary | | | | | | | | | | | lesson 5 | | | | | | | | | | | | | | lesson 6 | Check out Your Previous Knowledge | We hope that was a little eye-opener…..! | Tokens, crypto, coins, ERC-20. Is it all the same? | | | | | Foundations of our contract with Foundry | Everything's ready, so let's go ahead and start coding Solidity. | Create the Framing and Walls | | | | | Laying out the basics of the contract | n/a | Lock the Door! | | | | | Defining permissions for use of our contract | n/a | Register your house in the Real Estate Register | | | | | Deploying with Foundry | n/a | Querying the Block Explorer | | | | | | | | | | | Intro_Eth pt. 1 (checkpoint buttons have semantic text) | no warm up quiz | | | | | | Did you get all that? | Comprehension Check | n/a | Installation | | | | Keeping up? Test yourself | Comprehension Check | Now you’re ready to surf … | The quick tour | | | | | | | | | | | | | | | | | | Intro_Eth pt. 2 | | | | | | | | | | | | | | Intro_Eth pt. 3 | | | | | | | | | | | | | | | | | | | |

• how do we grab the message? Do we hard code it into the lesson? Or do we grab a string of text programmatically from elsewhere e.g. the title of the warm-up or checkpoint question set e.g.

What additional, if any texts do we need?

• piablo hey uma do we need some kind of ‘landing page’ e.g. ‘Who or What is Academy?’, or ‘Getting Started’, etc?
  1. and/or there any other places that we need descriptors/descriptive texts in the platform?