reading-notes

View the Project on GitHub TrunkOfUkuleles/reading-notes

Questions

  1. Why do we not need more .html pages in a multi-page React app? React is a SPA design, so everything is rendered off of one HTML root

  2. If we wanted a component to show up on every page, where would we put it and why? Outside the outside of the browser router would put you high up in the site archetecture on the index.js. YOu would be app level, but not have access to the routing methods Inside the , outside a This gives you access to most of the app, but stioll witin the browser itself Inside a Specific to the route itself

Vocab

Composition - propcess of object design for protoitypal inheritance Children / Child Components - components or elements within a “parent” element Hash Routing - helping tro render client side to use a base app url as a base to similate different content Link Routing - direct links to addresses

Preview

Which 3 things had you heard about previously and now have better clarity on? Hooks, useEffect, hash tables

Which 3 things are you hoping to learn more about in the upcoming lecture/demo? hooks, the mouting lifecycle, hooks and state management accross app

What are you most excited about trying to implement or see how it works? simple state management