Reorganized, renamed, and moved the Technical Overview information (p…

[dwelsch-esi]

Updated, reorganized,and renamed the technical overview (previously "Learning") per: https://github.com/etcd-io/website/issues/771#issue-2147186171

Did some minor rewriting. Moved the Glossary out of "Learning" into the main table of contents after "FAQ".

[dwelsch-esi]

@jmhbnz Balance that against confusing users who are familiar with the current documentation. My take would be to treat it like a software update: If it's a bug fix, it might be appropriate to also apply it to existing versions, but since it's (essentially) an enhancement, put it in the new release only. There might be considerations I haven't thought of, though. If the project votes to apply it to other versions, I'm happy to do so.

[ivanvc]

Thanks for the PR, @dwelsch-esi. I briefly looked into it but felt overwhelmed, as there were too many changes. I would suggest:

1. Break down the PR into more atomic ones; that way, it will be better for them to merge quicker and lessen the burden on the reviewers.
2. I agree with @jmhbnz. It may be confusing if the documents are not there when switching versions. One approach would be to add redirections to the new locations rather than just moving the files.

[jberkus]

I'll shepherd this in but I need to fix the merge conflicts first.

[jmhbnz]

I'll shepherd this in but I need to fix the merge conflicts first.

I'm not sure we have consensus for this to proceed as is. I would like to see the concern addressed about compatibility of docs between versions. Ivan had a great suggestion in https://github.com/etcd-io/website/pull/843#issuecomment-2109192633 of using redirects to ensure links work across versions.