I wanted to create this blog to keep track of my progress while working on my current web application. I hope that this documentation will help me improve my technical writing skills and help me keep track of never-ending ideas or roadblocks along the way.
Recap // June 9, 2022
My web application is definitely a work-in-progress at this point. So far, I just want to get the simple components ready such as the card-reading and user authentication features.
At this moment, the card-reading feature is a stand alone component. The placeholder images for each of the 78 cards are currently very quick sketches I made on ProCreate. I have grand schemes for the cards — to either design better cards or turn them into simple 3D cards.
How does the card reading function work?
It’s very simple actually! With several functions inside one file to keep the different functions organized. Each card is linked to a number from 1 through 78. I followed the numbering according the Rider Waite deck — the most popular traditional deck used among tarot readers. I created 7 different spread options that select different amounts of cards. After selecting a spread, my
cardPick function is called. The cardPick function grabs a random number between 1 and 78. That number is then pushed to a list called cards. If the spread calls for more than one card, then the function will pick more numbers until it is finished. Before the number can be pushed to the list, it is compared to existing numbers to ensure that all numbers are unique. Pushing the cards into a list helps me keep track of spreads, avoid duplicates, and eventually will help me spreads to users efficiently.
While I am still setting up user authentication, there are only simple credentials being saved at the moment. Those credentials being; name, email, and password. Once user authentication is completed, I want to link the card-reader function to user accounts so those with accounts can save spreads that resonate with them for future reference.