first draft emails improved

src/content/directory/email-service.yaml

@@ -0,0 +1,12 @@
+id: eMsRv1
+name: Email Service
+
+entry:
+  title: Email Service
+  url: /email-service/
+  group: Developer platform
+
+meta:
+  title: Cloudflare Email Service docs
+  description: Send transactional emails at scale with Cloudflare Email Service
+  author: "@cloudflare"

src/content/docs/email-routing/email-workers/index.mdx

@@ -9,7 +9,7 @@ With Email Workers you can leverage the power of Cloudflare Workers to implement
 
 Creating your own rules with Email Workers is as easy or complex as you want. You can begin using one of the starter templates that are pre-populated with code for popular use-cases. These templates allow you to create a blocklist, allowlist, or send notifications to Slack.
 
-If you prefer, you can skip the templates and use custom code. You can, for example, create logic that only accepts messages from a specific address, and then forwards them to one or more of your verified email addresses, while also alerting you on Slack.
+If you prefer, you can skip the templates and use custom code. You can, for example, create logic that only accepts messages from a specific address, and then forwards them to one or more of your [verified email addresses](/email-service/configuration/email-routing-addresses/#destination-addresses), while also alerting you on Slack.
 
 The following is an example of an allowlist Email Worker:
 

src/content/docs/email-routing/index.mdx

@@ -22,6 +22,12 @@ Create custom email addresses for your domain and route incoming emails to your
 
 </Description>
 
+:::note[Email Routing is now part of Email Service]
+Email Routing is now integrated into [Cloudflare Email Service](/email-service/), a complete email product suite. Email Service provides all the routing capabilities you already use, as well as the ability to send emails from Workers or external servers using a REST API.
+
+For new projects, refer to the [Email Service documentation](/email-service/). Existing Email Routing configurations continue to work without changes.
+:::
+
 <Plan id="email.email_routing.properties.availability.summary" />
 
 <Render file="email-routing-definition" product="email-routing" />

src/content/docs/email-service/api/index.mdx

@@ -0,0 +1,12 @@
+---
+title: API reference
+pcx_content_type: navigation
+sidebar:
+  order: 5
+  group:
+    hideIndex: true
+---
+
+import { DirectoryListing } from "~/components";
+
+<DirectoryListing />