spudly / scripture.study Goto Github PK

Add a section to the website where you can search for verses by selecting one or more speakers. It will then show you every verse where they spake/wrote.

Show the geneology of a person in the scriptures. I already have a paper chart of the genealogy in the Book of Mormon that I made years ago and can use as a reference.

• user authentication
• audit mutations (lastUpdatedBy)

Allow uses to create lists where each list item is associated with a scriptural reference.

See https://scripture-study-staging.herokuapp.com/people/46753be1-488e-4db5-9c2a-e46bfa403a6a

react_devtools_backend.js:2273 TypeError: Cannot read property 'getBoundingClientRect' of undefined
    at index.client.js:43
    at Array.flatMap (<anonymous>)
    at index.client.js:43
    at ol (index.client.js:27)
    at vu (index.client.js:27)
    at t.unstable_runWithPriority (index.client.js:35)
    at Bo (index.client.js:27)
    at mu (index.client.js:27)
    at index.client.js:27
    at D (index.client.js:35)

It is likely not rendering the <FamilyTreePerson />.

Allow people to add questions to scriptures, and allow people to answer those questions. Dedicate a section to listing the questions and answers.

Questions should also be associated with verses so they can be rendered inline while reading them.

This section will show objects mentioned in the scriptures:

• name
• description
• owners
• scriptures where the object was mentioned

In the case of scriptural records, we can show who transferred them to who.

This section of the website will show places mentioned in the scriptures

• name
• description
• show on map where possible
• show scriptures where place is mentioned

move general purpose functions into new "pushpop" repo

On mobile, when attempting to highlight the last verse of a chapter, it sometimes messes up the selection when you try to assign a speaker. Rotating the phone helps by changing the orientation and the flow of text.

I think this could be mixed by adding some extra space under the chapter (margin bottom?)

Create a comparisons feature where you can compare scriptures side-by-side.

This will use a diff tool, just like viewing diffs between commits in git.

There are lots of good candidates for scriptures that should be compared to other scriptures, like all the isaiah chapters in 2 Nephi, or the times when JC quotes isaiah and malachi in 3rd Nephi.

Add a number field to the people table so we can reference same-named people by their numbers as well.

This should not be part of the "name" field, but should be a separate field we can use when rendering the name.

Example: Alma¹

right now it looks broken. also, need to make sure we're not nesting a inside of a because that's just weird.

Remember where you were:

• when logging in
• when logging out
• when re-opening the app closing it

Show geneaology chart for people in the scriptures

Add dark mode. Use tailwind pseudo-selectors for this, so we can type classes like this:

<div className="color-black darkmode:color-white" />

Create a section of the website for adding definitions for words and phrases.

These definitions would be shown inline while reading scriptures (perhaps with a wavy underline under the word/phrase).

• rename mongodb collection
• rename type "Person" to "Speaker"

server-side-render pages

rewrite navigation - it's not fully fleshed out and is terrible on mobile.

Would be nice to have a timeline feature.

The following would have dates associated with them and would show up on the timeline

• scripture chapters
• major scriptural events
• people

• create speaker
• update speaker
• delete speaker

We need chapter headings/summaries. Unfortunately we can't just use the same ones in the LDS edition of the scriptures because those are copyrighted.

I haven't been happy with mongo and would rather switch back to traditional SQL. Postgres seems to have overtaken mySQL in terms of popularity.

Heroku offers a free tier for their databases, so we should be able to setup DBs for multiple envs as well without paying through the nose. For now, we should setup one for staging and one for production.

See https://elements.heroku.com/addons/heroku-postgresql

Create a section of the website for tracking progress on annotating the scriptures with marks.

For example, it might show that 85% of the verses in the Book of Mormon have speaker marks associated with them.

the first time you open a chapter (without first having a service worker, cache, etc) the speakers list is empty so you get missing speaker errors. it works after you refresh

• when navigating to a chapter that you've read recently, it should preserve your scroll position
• when navigating to a chapter that you have NOT read recently, it should scroll to the top
• use sessionStorage to store these details so that it is not dependent on history and gets wiped out when your session ends

This will allow you to tag scripture verses with "topic" tags. You'll then be able to browse topics and see verses associated with that topic.

Add user authentication to prevent random visitors from editing stuff

Use github actions to run cypress tests. Ideally, we'd spin up (and seed) a postgres db specifically for testing. Not sure if this is possible...

• cypress working locally
• test coverage reports
• working in CI (Github Actions)
• post-deploy smoke test (is this possible?)

Create a windowed, scrollable timeline that shows:

• major events
• people who lived during that time