Design the Integration between Drive and your Pipeline

[pishoyg]

Likely, this means letting them contribute through Drive instead of Git.
List the data sources, and redirect the flow to Drive (think about this!)
A few sources that immediately come to my mind are:

• Crum (Roots, derivations, types, meanings, and page numbers)
• Crum's Notes
• Crum's Scans
• Crum's Explanatory Images
• The Bible
• copticsite.com's Dictionary and Suffixes
• Dawoud's Screenshots
• Dawoud's Page Numbers
• future data...

Thinking about Drive, it might be even easier for users to contribute
through a sheet instead of a Drive folder (e.g. for notes). Use sheets
whenever possible.

Thought: Another possibility is for Git to continue to be the source of truth.
But what we can do is have users share their contributions via Drive, and then
we will implement a pipeline to integrate the contributions made through Drive
into Git.

1. Marcion's pipeline should retrieve the data manually collected /
   overridden for dawoud-pages and crum-last-page, rather than simply
   write an empty placeholder column. (p2, 1-2 hours)

[pishoyg]

Note: Removed the milestone, since this is about the pipeline that supports the site, rather than about the site itself. The site can be published, and the pipeline can be perfected later.

[pishoyg]

Note: We somewhat have a pipeline for publications (the Bible, the Kindle dictionary, the flashcards). We still need to design the data "mirror" gsheets.

Note: This was requested when the site didn't exist. We should perhaps reconsider whether we want to use Drive gsheets as a sink at all. The site might suffice, and we can just use Drive gsheets as a source for users to input augmentations.

[pishoyg]

We prefer using the site / app as an interface for most data.
The use of Drive has become more limited. It will likely be used:

1. As a convenient way to type augmentations in TSVS format.
2. For publishing data, by sharing a public link to a file that gets updated with every release (this is the case for the Bible, the Kindle dictionary, and the flashcards package).

Thus, this is somewhat redundant given #78 and #109. (In the former, you are yet to build the pipeline around this future lovely sheet; in the latter, the links are there already in your vault.sh and are being used in your Makefile, you just need to list them and cement them.)