cases: Versioning Data and Models (rewrite)

[jorgeorpinel]

Continuation of #1716 (comment)

• Moves the use case location and replaces all the links, adds a redirect.
• Includes same related changes to other docs as cases: Versioning Data and Model Files (review) #1716
• Removes term "SCM" in favor of "version control" (and other phrases) — see https://trends.google.com/trends/explore?geo=US&q=Source%20code%20management,%2Fm%2F015_g6,%2Fm%2F0fj8g
• Redefines "data artifact" glossary term (could be removed from the glossary actually, not sure).

UPDATE: Pending stuff

• PR scope cases: Versioning Data and Models (rewrite) #1747 (review)
• 2-column section? cases: Versioning Data and Models (rewrite) #1747 (review)

[shcheklein]

It's good in a sense that we are starting it from scratch 👍

Regarding the intro- it still does not give any sense why would versioning data and models is important (reference to a problem), how DVC solves it and why DVC is the way to go (selling the philosophy).

[jorgeorpinel]

Another iteration of this is ready for review. Here are 2 known (minor) issues I see:

[shcheklein]

A final ask in private to update this a bit

[shcheklein]

Cool 😎 stuff!

[jeremydesroches]

@jorgeorpinel would you still like me to review this for SEO-related updates, as you mentioned before?

[jorgeorpinel]

That would be useful @jeremydesroches but completely up to you. Also at this point, since the rewrite was merged recently, do you think we should wait more weeks to be able to compare search patterns vs the previous version?

I guess giving it a read to make sure the key terms you added in https://github.com/iterative/dvc.org/pull/1806/files#diff-34b5f307478d996f5f763b6e71d8e9689543d9ef99f85d36a505c8ef47e57fee are still there (if possible) would be ideal.