Discord Rotten Tomatoes — Update #3

• It took some getting used to the Clerk documentation since there’s not a clear delineation of what purely React documentation vs NextJS is at some points.
• I created the user onboarding sequence diagram to help me understand how the app will work with all its dependencies. I created two:
  • The first one was a rough draft to help me get started. But I saw it needed more granularity regarding the actors in the sequence.
  • The second diagram was more clean-cut. I saw how Clerk did their onboarding sequence diagram. It helped me realize that using the Browser as an actor allows me to outline URLs and other interactions the user views, and using a Client actor will enable me to focus on business logic in the React app.
• I created a scratch file in Webstorm to help me quickly test the Clerk backend SDK.
  • I want Clerk to know if a user has been onboarded and is authorized to use the app, i.e., in my Discord server.
• Also, Clerk’s QuickStart guide made me realize I need react-router to help simplify my components.
  • I was doing checks to see if a user onboarded in the dashboard/home page
  • With React Router, I plan on separating the flows into different pages. So if a user has not been onboarded, they can visit or be redirected to the onboarding page where they can set their review weights
• Using React Router and having to set up the routes manually tempts me to want to pivot to NextJS but my goal is not to make this too abstracted as I want to learn why a tool like NextJS exists. I need some hardships in this learning phase so I know why the drill was created when there is a screwdriver and when I use one or the other.

I wrote this quick update in bullet points once I figured out the onboarding flow I’m going with. It was quick and fast to think it out, and I don’t have to remember the details in a month when I hit a huge milestone. I like this format and see myself using it going forward.