[docs] Move dlt docs out of embedded-elt docs (#27071)

## Summary & Motivation

As title.

Author: maximearmstrong

docs/content/_apidocs.mdx

@@ -394,6 +394,13 @@ Dagster also provides a growing set of optional add-on libraries to integrate wi
         Datahub from within Dagster ops.
       </td>
     </tr>
+    <tr>
+      <td>
+        <a href="/_apidocs/libraries/dagster-dlt">dlt</a> (
+        <code>dagster-dlt</code>)
+      </td>
+      <td>Provides support for running dlt within Dagster</td>
+    </tr>
     <tr>
       <td>
         <a href="/_apidocs/libraries/dagster-docker">Docker</a> (

docs/content/_navigation.json

@@ -1118,7 +1118,7 @@
         "children": [
           {
             "title": "dlt & Dagster",
-            "path": "/integrations/embedded-elt/dlt"
+            "path": "/integrations/dlt"
           },
           {
             "title": "Sling & Dagster",
@@ -1570,6 +1570,10 @@
             "title": "Delta Lake (dagster-deltalake)",
             "path": "/_apidocs/libraries/dagster-deltalake"
           },
+          {
+            "title": "dlt (dagster-dlt)",
+            "path": "/_apidocs/libraries/dagster-dlt"
+          },
           {
             "title": "Docker (dagster-docker)",
             "path": "/_apidocs/libraries/dagster-docker"

docs/content/api/modules.json.gz

@@ -70,6 +70,7 @@ Explore guides for integrations with external services.
     href="/integrations/dbt-cloud"
   ></ArticleListItem>
   <ArticleListItem title="DuckDB" href="/integrations/duckdb"></ArticleListItem>
+  <ArticleListItem title="dlt" href="/integrations/dlt"></ArticleListItem>
   <ArticleListItem
     title="Embedded ELT"
     href="/integrations/embedded-elt"
@@ -138,6 +139,10 @@ Explore libraries that are maintained by the Dagster core team.
     title="dbt"
     href="/_apidocs/libraries/dagster-dbt"
   ></ArticleListItem>
+  <ArticleListItem
+    title="dlt"
+    href="/_apidocs/libraries/dagster-dlt"
+  ></ArticleListItem>
   <ArticleListItem
     title="Embedded ELT"
     href="/_apidocs/libraries/dagster-embedded-elt"

docs/content/api/searchindex.json.gz

@@ -65,10 +65,10 @@ To follow the steps in this guide, you'll need:
 - **[To install](/getting-started/install) the following libraries**:
 
   ```bash
-  pip install dagster dagster-embedded-elt
+  pip install dagster dagster-dlt
   ```
 
-  Installing `dagster-embedded-elt` will also install the `dlt` package.
+  Installing `dagster-dlt` will also install the `dlt` package.
 
 ---
 
@@ -165,10 +165,10 @@ Ensure that these variables are defined in your environment, either in your `.en
 
 ## Step 4: Define a DagsterDltResource
 
-Next, we'll define a <PyObject module="dagster_embedded_elt.dlt" object="DagsterDltResource" />, which provides a wrapper of a dlt pipeline runner. Use the following to define the resource, which can be shared across all dlt pipelines:
+Next, we'll define a <PyObject module="dagster_dlt" object="DagsterDltResource" />, which provides a wrapper of a dlt pipeline runner. Use the following to define the resource, which can be shared across all dlt pipelines:
 
 ```python
-from dagster_embedded_elt.dlt import DagsterDltResource
+from dagster_dlt import DagsterDltResource
 
 dlt_resource = DagsterDltResource()
 ```
@@ -179,9 +179,9 @@ We'll add the resource to our <PyObject module="dagster" object="Definitions" />
 
 ## Step 5: Create a dlt_assets definition for GitHub
 
-The <PyObject object="dlt_assets" module="dagster_embedded_elt.dlt" decorator /> decorator takes a `dlt_source` and `dlt_pipeline` parameter. In this example, we used the `github_reactions` source and created a `dlt_pipeline` to ingest data from Github to Snowflake.
+The <PyObject object="dlt_assets" module="dagster_dlt" decorator /> decorator takes a `dlt_source` and `dlt_pipeline` parameter. In this example, we used the `github_reactions` source and created a `dlt_pipeline` to ingest data from Github to Snowflake.
 
-In the same file containing your Dagster assets, you can create an instance of your <PyObject object="dlt_assets" module="dagster_embedded_elt.dlt" decorator /> by doing something like the following:
+In the same file containing your Dagster assets, you can create an instance of your <PyObject object="dlt_assets" module="dagster_dlt" decorator /> by doing something like the following:
 
 <Note>
   If you are using the{" "}
@@ -195,7 +195,7 @@ In the same file containing your Dagster assets, you can create an instance of y
 
 ```python
 from dagster import AssetExecutionContext, Definitions
-from dagster_embedded_elt.dlt import DagsterDltResource, dlt_assets
+from dagster_dlt import DagsterDltResource, dlt_assets
 from dlt import pipeline
 from dlt_sources.github import github_reactions
 
@@ -242,19 +242,15 @@ And that's it! You should now have two assets that load data to corresponding Sn
 
 ### Overriding the translator to customize dlt assets
 
-The <PyObject module="dagster_embedded_elt.dlt" object="DagsterDltTranslator" /> object can be used to customize how dlt properties map to Dagster concepts.
+The <PyObject module="dagster_dlt" object="DagsterDltTranslator" /> object can be used to customize how dlt properties map to Dagster concepts.
 
-For example, to change how the name of the asset is derived, you can override the <PyObject module="dagster_embedded_elt.dlt" object="DagsterDltTranslator" method="get_asset_key" /> method, or if you would like to change the key of the upstream source asset, you can override the <PyObject module="dagster_embedded_elt.dlt" object="DagsterDltTranslator" method="get_deps_assets_keys" /> method.
+For example, to change how the name of the asset is derived, you can override the <PyObject module="dagster_dlt" object="DagsterDltTranslator" method="get_asset_key" /> method, or if you would like to change the key of the upstream source asset, you can override the <PyObject module="dagster_dlt" object="DagsterDltTranslator" method="get_deps_assets_keys" /> method.
 
-```python file=/integrations/embedded_elt/dlt_dagster_translator.py
+```python file=/integrations/dlt/dlt_dagster_translator.py
 from collections.abc import Iterable
 
 import dlt
-from dagster_embedded_elt.dlt import (
-    DagsterDltResource,
-    DagsterDltTranslator,
-    dlt_assets,
-)
+from dagster_dlt import DagsterDltResource, DagsterDltTranslator, dlt_assets
 from dlt.extract.resource import DltResource
 
 from dagster import AssetExecutionContext, AssetKey
@@ -298,13 +294,13 @@ In this example, we customized the translator to change how the dlt assets' name
 
 A common question is how to define metadata on the external assets upstream of the dlt assets.
 
-This can be accomplished by defining a <PyObject object="AssetSpec" /> with a key that matches the one defined in the <PyObject module="dagster_embedded_elt.dlt" object="DagsterDltTranslator" method="get_deps_assets_keys" /> method.
+This can be accomplished by defining a <PyObject object="AssetSpec" /> with a key that matches the one defined in the <PyObject module="dagster_dlt" object="DagsterDltTranslator" method="get_deps_assets_keys" /> method.
 
 For example, let's say we have defined a set of dlt assets named `thinkific_assets`, we can iterate over those assets and derive a <PyObject object="AssetSpec" /> with attributes like `group_name`.
 
-```python file=/integrations/embedded_elt/dlt_source_assets.py
+```python file=/integrations/dlt/dlt_source_assets.py
 import dlt
-from dagster_embedded_elt.dlt import DagsterDltResource, dlt_assets
+from dagster_dlt import DagsterDltResource, dlt_assets
 
 from dagster import AssetExecutionContext, AssetSpec
 
@@ -340,11 +336,11 @@ While still an experimental feature, it is possible to use partitions within you
 
 That said, here is an example of using static named partitions from a dlt source.
 
-```python file=/integrations/embedded_elt/dlt_partitions.py
+```python file=/integrations/dlt/dlt_partitions.py
 from typing import Optional
 
 import dlt
-from dagster_embedded_elt.dlt import DagsterDltResource, dlt_assets
+from dagster_dlt import DagsterDltResource, dlt_assets
 
 from dagster import AssetExecutionContext, StaticPartitionsDefinition
 
@@ -385,11 +381,11 @@ Want to see real-world examples of dlt in production? Check out how we use it in
 
 ## APIs in this guide
 
-| Name                                                                         | Description                                                    |
-| ---------------------------------------------------------------------------- | -------------------------------------------------------------- |
-| <PyObject module="dagster_embedded_elt.dlt" object="dlt_assets" decorator /> | The core dlt asset factory for building ingestion jobs         |
-| <PyObject module="dagster_embedded_elt.dlt" object="DagsterDltResource" />   | The dlt resource for running ingestions.                       |
-| <PyObject module="dagster_embedded_elt.dlt" object="DagsterDltTranslator" /> | A translator for specifying how to map between dlt and Dagster |
+| Name                                                            | Description                                                    |
+| --------------------------------------------------------------- | -------------------------------------------------------------- |
+| <PyObject module="dagster_dlt" object="dlt_assets" decorator /> | The core dlt asset factory for building ingestion jobs         |
+| <PyObject module="dagster_.dlt" object="DagsterDltResource" />  | The dlt resource for running ingestions.                       |
+| <PyObject module="dagster_dlt" object="DagsterDltTranslator" /> | A translator for specifying how to map between dlt and Dagster |
 
 ---
 

docs/content/api/sections.json.gz

@@ -30,4 +30,4 @@ Sling provides an easy-to-use YAML configuration layer for loading data from fil
 
 With the ability to leverage pre-made [verified sources](https://dlthub.com/docs/dlt-ecosystem/verified-sources/) like [Hubspot](https://dlthub.com/docs/dlt-ecosystem/verified-sources/hubspot) and [Notion](https://dlthub.com/docs/dlt-ecosystem/verified-sources/notion), and [destinations](https://dlthub.com/docs/dlt-ecosystem/destinations/) like [Databricks](https://dlthub.com/docs/dlt-ecosystem/destinations/databricks) and [Snowflake](https://dlthub.com/docs/dlt-ecosystem/destinations/snowflake), integrating dlt into your Dagster project enables you to load a data in an easy and structured way.
 
-[Click here to get started](/integrations/embedded-elt/dlt) with the dlt integration.
+[Click here to get started](/integrations/dlt) with the dlt integration.

docs/content/integrations.mdx

@@ -308,6 +308,6 @@ def my_assets(context, sling: SlingResource):
   ></ArticleListItem>
   <ArticleListItem
     title="dlt & Dagster"
-    href="/integrations/embedded-elt/dlt"
+    href="/integrations/dlt"
   ></ArticleListItem>
 </ArticleList>

docs/content/integrations/embedded-elt/dlt.mdx renamed to docs/content/integrations/dlt.mdx

@@ -6,8 +6,8 @@ title: Dagster & dlt
 sidebar_label: dlt
 excerpt: Easily ingest and replicate data between systems with dlt through Dagster.
 date: 2024-08-30
-apireflink: https://docs.dagster.io/_apidocs/libraries/dagster-embedded-elt
-docslink: https://docs.dagster.io/integrations/embedded-elt/dlt
+apireflink: https://docs.dagster.io/_apidocs/libraries/dagster-dlt
+docslink: https://docs.dagster.io/integrations/dlt
 partnerlink: https://www.getdbt.com/
 logo: /integrations/dlthub.jpeg
 categories:
@@ -24,7 +24,7 @@ This integration allows you to use [dlt](https://dlthub.com/) to easily ingest a
 ### Installation
 
 ```bash
-pip install dagster-embedded-elt
+pip install dagster-dlt
 ```
 
 ### Example