# Introduction

Notes 

* Talk about Developer Relations and the relationship between Platform Engineering, Developer Experience and SRE.
* Talk about Internal Developer Platforms, Team Topologies.
* Talk About Space and DevOps and Evolution over time.
* Chapter Goal 
* Introduce the concepts of Platform Engineering. Explain the evolution of DevOps to Platform Engineering and SRE. 
* Introduce Team Topologies as a very useful lens through which to view Platform Engineering. 
* Introduce capabilities as the key lens of what Platform Engineering provides, and talk about how capabilities are implemented through platform services and technical support, best practices and general guidance. 
* Introduce Internal Developer Platforms as the product of Platform Engineering.  
* Talk about conceptual load reduction briefly, segue into Developer Experience. 
* Talk about platform as a product as the way of viewing the output provided by a platform group as a single unified set of capabilities, often called an Internal Developer Platform, which provide developers with the self-service capabilities that will reduce their conceptual load and allow them to focus on their core responsibilities rather than incidental activities. 

{% embed url="<https://martinfowler.com/articles/building-infrastructure-platform.html>" %}

{% embed url="<https://getdx.com/podcast/product-manager-platform-engineering>" %}

{% embed url="<https://www.thoughtworks.com/en-de/perspectives/edition4-platform-strategy/article>" %}

{% embed url="<https://buildrightside.com/book/chapter2-platform-investments.html>" %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://www.platform-engineering.org/what-is-an-internal-developer-platform/introduction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.