Define Our Terms

[Soyokaze-42]

I've noticed quite a bit of ambiguity in the terms we are using to describe the app. It would help us to define our terms and strictly use them in our discussions. Let's use this issue to hash out the initial set of terms we are going to use to describe these things. Please add terms in the comments below that are up for discussion, discuss them, and propose changes to the terms here in the issue description so we can get on the same page. Once we have consensus, we will add these to the README.

Terms:

• Card: A single prayer that has a category, title, scripture reference, and helptext.
• User Card: A card that has been associated with a user and includes notes, whether it has been answered, whether the user has hidden the card, and some statistical measures of usage.
• Prayer Deck: The current collection of User Cards a user will be/is/has finished praying through. There is only one. The Cards will be swapped out for new ones when the user starts a new prayer.
• Daily Deck: A prayer deck generated programmatically with user options (like frequency, whether it has been answered or hidden...).

Concept-Only Terms:

• Category Deck: A collection of all user cards for a particular user with a particular category.
• Prayer Box: All Category Decks.

[Soyokaze-42]

Unless we need to keep or use information about the category (other than the title), Category Deck will not be in the database. It can be, but it isn't right now.

[kenancasey]

I don't like the word page in the definition of a Prayer Box. I thought we were defining data schema/conceptual structures, not UI. Can we reword that Prayer Box definition to decouple it from the UI?

[kenancasey]

To be clear, I'm for having a shared vocabulary for key concepts to aid communication.

[Soyokaze-42]

There are two UI components in there - I totally agree that we should segregate. Category Deck and Prayer Box are both not schema things. I moved them in the description - what do you think?

I also did not define all the schema terms. Do you think this should be comprehensive for the schema? I was going for the ones that matter for our issues. We get better readability at the expense of the chance of leaving something important out.

[benjoeclark]

I have tried a Figma Mock-up with this naming convention. https://www.figma.com/file/lpfV0Ony7djEKA8XkpAoD7/Mock-up?type=design&node-id=0%3A1&mode=design&t=TsTVg8FTgAd1gAox-1

[Soyokaze-42]

Kenan and I were talking about the PrayerDeck. I was thinking we would have multiple PrayerDecks and consider one deck a prayer, but it is simpler to think of the PrayerDeck as the current deck of cards being prayed. There will only ever be one per user. Instead of counting PrayerDecks (the way I was thinking, this would be the number of prayers facilitated), we can instead use the UserCards prayed as the metric for user progress for the site. It gets us out of determining if a PrayerDeck is finished or not as far as tracking metrics go. I'm adjusting the definition above, but more discussion is welcome!