Recap

Since the conversations about this topic have occurred in multiple places and this PR combines discussion about the philosophy of the change with the particulars about where the change is made, then I shall recap the discussion here:

• It is believe that referring to Kedro primarily as a tool for data scientists may dissuade non-data scientists from using it
• Since non-data scientists constitute a large population of potential Kedro users, then that may limit the overall adoption of Kedro
• Therefore a change has been discussed, in order to prevent referring to Kedro primarily as a tool for data scientists
• (Avoiding the term “advanced analytics” is preferred)
• The emerging consensus is for “data engineering and data science” as the preferable term (where space allows), and “data pipelines” (where there is not sufficient space)
• Changing the messaging to this will lead to some inconsistent messaging (even on the same page) - however there is already a wide range of messaging in current Kedro material, so this change may not cause an overall increase in inconsistency (in fact it may even make things more consistent in certain places)

Philosophical decision

We will make the suggested change (to “data engineering and data science” / “data pipelines”), based on this reasoning:

• It seems likely that changing the messaging could increase interest in Kedro, and other similar products use “data engineer”
• There seems to be little risk in increasing the inclusiveness of the language (and the original reason for anchoring on “data science” in order to align with the marketing approach of McKinsey at the time is no longer a driving factor)
• There is an emerging consensus which presents a workable solution, and the term “data engineering” is currently prominent in the messaging of related tools
• There is some support across the TSC to update the Kedro messaging, and none have expressed a strong objection

Implementation

The messaging must be changed across:

• Website
• Docs (Use "data engineering and data science" across the docs #5249)
• GitHub (readme and meta data for Kedro and Awesome-Kedro)
• PyPI
• Other locations?

This PR addresses the changes to the website.

NB: Another PR must be created to change the messaging across the docs.
NB: Other issues must be created to change the messaging across the other locations listed above.

Originally posted by @Joseph-Perkins in kedro-org/kedro-website#207 (comment)