Skip to content

Commit

Permalink
docs(journal): updating the daily notes..
Browse files Browse the repository at this point in the history
  • Loading branch information
h0lybyte committed Nov 10, 2024
1 parent 2b67176 commit 50f4437
Showing 1 changed file with 6 additions and 1 deletion.
7 changes: 6 additions & 1 deletion apps/kbve.com/src/content/journal/11-10.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -105,4 +105,9 @@ import { Adsense, Tasks } from '@kbve/astropad';
Okay after migrating both the user profile and the user card out of the sign up process, we can begin building out the onboarding process.
This process will have to be done on both the `@kbve/laser` project and also in the `@kbve/expo-bbq`, since we need to include this for both astro and expo.
In both situations, I will open four instances of VS Code and tackle them all at the same time!
This is the peak of development, my brain is going to be broken as I do this xD
This is the peak of development, my brain is going to be broken as I do this xD
Under the current expo, it will be `packages/expo-bbq/src/components/auth/user/TamaOnboard.tsx` and then inside of that we can build out the component!
This would be the barebone component, aka, `TamaOnboard`, and it would have two states that it would manage.
The first state would be for the `username` and making sure that it is unique before setting it up, however it would be noted that it is the user's public username.
The second state would be for the profile card, the core specific here would be preparing the basic information for the init card.
Hmm, okay these two states should be enough for us to move forward, I believe we can always go back around and double check the onboarding when it goes live into production.

0 comments on commit 50f4437

Please sign in to comment.