Rebrand playbook as 'Engineering Fundamentals' (microsoft#1029)

* Rebrand playbook as 'Engineering Fundamentals'. Also fix a few typos and broken links.

* WeaveWorks out of business and link broke. Replaced with link to GitLab

* Add https://www.gartner.com/en/information-technology/glossary/citizen-developer to exclusion list

Author: day-jeff

README.md

@@ -1,4 +1,4 @@
-# ISE Code-With Customer/Partner Engineering Playbook
+# ISE Engineering Fundamentals Customer/Partner Engineering Playbook
 
 An engineer or data scientist working on an [ISE](docs/ISE.md) project...
 

docs/ISE.md

@@ -1,6 +1,6 @@
 # Who We Are
 
-Our team, ISE (Industry Solutions Engineering), works side by side with customers to help them tackle their toughest technical problems both in the cloud and on the edge. We meet customers where they are, work in the languages they use, with the open source frameworks they use, on the operating systems they use. We work with enterprises and start-ups across many industries from financial services to manufacturing. Our work covers a broad spectrum of domains including IoT, machine learning, and high scale compute. Our "superpower" is that we work closely with both our customers’ engineering teams and Microsoft’s product engineering teams, developing real-world expertise that we can use to help our customers grow their business and help Microsoft improve our products and services.
+Our team, ISE (Industry Solutions Engineering), works side-by-side with customers to help them tackle their toughest technical problems both in the cloud and on the edge. We meet customers where they are, work in the languages they use, with the open source frameworks they use, and on the operating systems they use. We work with enterprises and start-ups across many industries from financial services to manufacturing. Our work covers a broad spectrum of domains including IoT, machine learning, and high scale compute. Our "superpower" is that we work closely with both our customers’ engineering teams and Microsoft’s product engineering teams, developing real-world expertise that we can use to help our customers grow their business and help Microsoft improve our products and services.
 
 We are very community focused in our work, with one foot in Microsoft and one foot in the open source communities that we help. We make pull requests on open source projects to add support for Microsoft platforms and/or improve existing implementations. We build frameworks and other tools to make it easier for developers to use Microsoft platforms. We source all the ideas for this work by maintaining very deep connections with these communities and the customers and partners that use them.
 

docs/agile-development/advanced-topics/team-agreements/working-agreements.md

@@ -33,7 +33,7 @@ their own, and adjust times, communication channels, branch naming policies etc.
 ## Quality and not Quantity
 
 - We agree on a [Definition of Done](definition-of-done.md) for our user story's and sprints and live by it.
-- We follow engineering best practices like the [Code With Engineering Playbook](https://github.com/microsoft/code-with-engineering-playbook)
+- We follow engineering best practices like the [Engineering Fundamentals Engineering Playbook](https://github.com/microsoft/code-with-engineering-playbook)
 
 ## Scrum Rhythm
 
@@ -77,7 +77,7 @@ The Process Lead is responsible for leading any scrum or agile practices to enab
 
 - We follow the git flow branch naming convention for branches and identify the task number e.g. `feature/123-add-working-agreement`
 - We merge all code into main branches through PRs
-- All PRs are reviewed by one person from [Customer/Partner Name] and one from Microsoft (for knowledge transfer and to ensure code and security standards are met)
+- All PRs are reviewed by one person from <Customer/Partner Name> and one from Microsoft (for knowledge transfer and to ensure code and security standards are met)
 - We always review existing PRs before starting work on a new task
 - We look through open PRs at the end of stand-up to make sure all PRs have reviewers.
 - We treat documentation as code and apply the same [standards to Markdown](../../../code-reviews/recipes/markdown.md) as code

docs/code-reviews/pull-requests.md

@@ -82,8 +82,8 @@ See also [Pull Request Template](./pull-request-template.md)
 
 ## Resources
 
-* [Writing a great pull request description](https://www.pullrequest.com/blog/writing-a-great-pull-request-description)
-* [Review code with pull requests (Azure DevOps)](https://learn.microsoft.com/en-us/azure/devops/repos/git/pull-requests?view=azure-devops)
+* [Writing a great pull request description](https://www.pullrequest.com/blog/writing-a-great-pull-request-description/)
+* [Review code-with pull requests (Azure DevOps)](https://learn.microsoft.com/azure/devops/repos/git/pull-requests)
 * [Collaborating with issues and pull requests (GitHub)](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests)
 * [Google approach to PR size](https://google.github.io/eng-practices/review/developer/small-cls.html)
 * [Feature Flags](https://www.martinfowler.com/articles/feature-toggles.html)

docs/continuous-delivery/gitops/deploying/README.md

@@ -2,7 +2,7 @@
 
 ## What is GitOps?
 
-GitOps is a way of managing your infrastructure and applications so that the whole system is described declaratively and version controlled (most likely in a Git repository), and having an automated process that ensures that the deployed environment matches the state specified in a repository."- [WeaveWorks](https://www.weave.works/technologies/gitops/#what-is-gitops)
+"GitOps is an operational framework that takes DevOps best practices used for application development such as version control, collaboration, compliance, and CI/CD, and applies them to infrastructure automation." See [GitLab: What is GitOps?](https://about.gitlab.com/topics/gitops/).
 
 ## Why should I use GitOps?
 

docs/continuous-integration/markdown-linting/README.md

@@ -35,4 +35,4 @@ To start using this pipeline:
 
 ## References
 
-[Markdown Code Reviews in the Code With Engineering Playbook](https://microsoft.github.io/code-with-engineering-playbook/code-reviews/recipes/markdown/#code-review-checklist)
+[Markdown Code Reviews in the Engineering Fundamentals Playbook](https://microsoft.github.io/code-with-engineering-playbook/code-reviews/recipes/markdown/#code-review-checklist)

docs/design/design-reviews/recipes/async-design-reviews.md

@@ -13,11 +13,11 @@ This in turn results in the following benefits:
 
 ## Measures
 
-The metrics and/or KPIs used for design reviews overall would still apply. See [design reviews](../README.md#Measures) for measures guidance.
+The metrics and/or KPIs used for design reviews overall would still apply. See [design reviews](../README.md#measures) for measures guidance.
 
 ## Participation
 
-The participation should be same as any design review. See [design reviews](../README.md#Participation) for participation guidance.
+The participation should be same as any design review. See [design reviews](../README.md#participation) for participation guidance.
 
 ## Facilitation Guidance
 

docs/documentation/recipes/static-website-with-mkdocs.md

@@ -2,7 +2,7 @@
 
 [MkDocs](https://www.mkdocs.org/) is a tool built to create static websites from raw markdown files. Other alternatives include [Sphinx](https://www.sphinx-doc.org/en/master/), and [Jekyll](https://jekyllrb.com/).
 
-We used MkDocs to create [ISE Code-With Engineering Playbook](https://microsoft.github.io/code-with-engineering-playbook/) static website from the contents in [the GitHub repository](https://github.com/microsoft/code-with-engineering-playbook). Then we deployed it to [GitHub Pages](https://pages.github.com/).
+We used MkDocs to create [ISE Engineering Fundamentals Playbook](https://microsoft.github.io/code-with-engineering-playbook/) static website from the contents in [the GitHub repository](https://github.com/microsoft/code-with-engineering-playbook). Then we deployed it to [GitHub Pages](https://pages.github.com/).
 
 We found MkDocs to be a good choice since:
 

docs/index.md

@@ -1,4 +1,4 @@
-# ISE Code-With Engineering Playbook
+# ISE Engineering Fundamentals Playbook
 
 An engineer working for a [ISE](ISE.md) project...
 

linkcheck.json

@@ -62,7 +62,8 @@
       "https://lldb.llvm.org/",
       "https://www.microsoft.com/",
       "https://aka.ms/opensource/security/",
-      "https://www.pluralsight.com/courses/"
+      "https://www.pluralsight.com/courses/",
+      "https://www.gartner.com/en/information-technology/glossary/citizen-developer"
     ],
     "only_errors": true,
     "cache_duration": "24h",

mkdocs.yml

@@ -1,7 +1,7 @@
 ---
-site_name: Code With Engineering Playbook
+site_name: Engineering Fundamentals Playbook
 site_url: https://microsoft.github.io/code-with-engineering-playbook
-site_description: ISE Code With Engineering Playbook
+site_description: ISE Engineering Fundamentals Engineering Playbook
 site_author: Microsoft ISE
 
 repo_url: https://github.com/microsoft/code-with-engineering-playbook/