Update digital.md

[ps2270]

I've made some typo corrections and also some revisions. Pls let me know if you think any of the revisions don't convey correctly the intended meaning.
One question about my changes:
I changed
most of this data was worked on in the Project's Google Drive [which sounded awkward to me]
to
most of this data was processed in the Project's Google Drive [but processing sounds like a different operation than what we did]

We can change it back to worked on, or perhaps change it to "edited"

[njr2128]

I think that we should keep the original because it is more technically precise. Static site generation does these three things (allows, reduces, minimizes) rather than the "fewer dependencies" causing the last two things

[njr2128]

change to:

static site generation, unlike CMS or database-driven projects, allows websites to be created with significantly fewer dependencies, and reduces maintenance overhead, as well as minimizes the risk of technological obsolescence. Content is already in its final form (as static pages are created beforehand) and can be sent as-is to the user.

[njr2128]

I believe there is a reason this is "respond with" - while grammatically in English this is usually "respond to," here it signifies that as traffic changes, the system is responsive

[njr2128]

DECISION: "respond to"

ALSO:

Because this is a well-established, fundamental web technology, techniques for serving static sites are likely to persist into the future as well as be universally understood by IT professionals tasked with keeping the assets online.

[njr2128]

Terry and I struggled with the wording here. As you mentioned, "processed" has a different meaning and should not be used here. Perhaps "edited"? Or leave as "worked on"?

[njr2128]

DECISION:
"worked on"

[njr2128]

@tcatapano, can you take a look at this and review too?

[ps2270]

Fine.

…

On Thu, Dec 31, 2020, 13:59 Naomi Rosenkranz ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In docs/about/digital.md <#164 (comment)> : > -Static site generation thus offers a number of advantages. It allows individualized software decisions and better control and maintenance of the site. Furthermore, open-source web servers like Apache and Nginx can very efficiently serve large amounts of static data and respond with increased user traffic, leading to lower server costs. Because the technology is so fundemental to the web, techniques for serving static sites are likely to persist into the future as well as be universally understood by IT professionals tasked with keeping the assets online. +Static site generation thus offers a number of advantages. It allows individualized software decisions and better control and maintenance of the site. Furthermore, open-source web servers like Apache and Nginx can very efficiently serve large amounts of static data and respond to increased user traffic, leading to lower server costs. Because the technology is so fundamental to the web, techniques for serving static sites are likely to persist into the future as well as be universally understood by IT professionals tasked with keeping the assets online. I believe there is a reason this is "respond with" - while grammatically in English this is usually "respond to," here it signifies that as traffic changes, the system is responsive — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#164 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AF75UYACBETK4UEONTBYKOTSXTX2ZANCNFSM4VPR5Z4A> .

[ps2270]

Worked on is fine

…

On Thu, Dec 31, 2020, 14:00 Naomi Rosenkranz ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In docs/about/digital.md <#164 (comment)> : > -The content for _Secrets of Craft and Nature_ involved the scholarly work of a number of different editors, teams, and collaborators working over several years to explore the intricacies of a complex historical text, Ms. Fr. 640. To facilitate the collaborative methods, most of this data was worked on in the Project's Google Drive. As the Project evolved and came closer to digital publication, more and more data was moved to Github repositories. At the same time, content was still under developement, and there was a need to draw from both Github and Google Drive at build time. +The content for _Secrets of Craft and Nature_ involved the scholarly work of a number of different editors, teams, and collaborators working over several years to explore the intricacies of a complex historical text, Ms. Fr. 640. To facilitate the collaborative methods, most of this data was processed in the Project's Google Drive. As the Project evolved and came closer to digital publication, more and more data was moved to Github repositories. At the same time, content was still under development, and there was a need to draw from both Github and Google Drive at build time. Terry and I struggled with the wording here. As you mentioned, "processed" has a different meaning and should not be used here. Perhaps "edited"? Or leave as "worked on"? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#164 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AF75UYHGOELWROFZFWLAX7DSXTYAXANCNFSM4VPR5Z4A> .

[njr2128]

All commented changes have been updated