Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
docs | dcb8be4 | Commit Preview URL Branch Preview URL |
Apr 21 2026, 02:01 AM |
| ├── Core concepts | ||
| │ ├── How dlt works | ||
| │ ├── Source | ||
| │ ├── Resource |
There was a problem hiding this comment.
we could add job here as well (thinking out loud), in case we want to have a unified approach towards docs. there would need to be a "dltHub" label. Just a raw thought, please challenge it
There was a problem hiding this comment.
Thoughts:
- dltHub should have its own docs section and Concepts page
- this is important because these docs will be maintained in the relevant repository rather than
dlt-hub/dltin the future
- this is important because these docs will be maintained in the relevant repository rather than
- Job is still an ambiguous word given "Load job" in dlt
| ├── Sources (→ verified-sources/index) | ||
| │ ├── REST APIs (→ rest_api/index) | ||
| ├── Sources | ||
| │ ├── [link] 10k+ LLM Context |
| │ │ ├── Advanced | ||
| │ │ └── Add incremental configuration | ||
| │ ├── Cloud storage and filesystem (→ filesystem/index) | ||
| │ │ └── Incremental |
| │ │ ├── Vaults | ||
| │ │ ├── Complex types | ||
| │ │ └── Add credentials | ||
| │ ├── Adjust a schema |
There was a problem hiding this comment.
also should go to Schema management
| │ ├── Contract & evolution | ||
| │ ├── Export & visualization | ||
| │ └── Naming convention | ||
| ├── ETL |
There was a problem hiding this comment.
What about "transformations" on the first line of the hierarchy?
|-- Transformations
|-- ELT
|-- ETL
There was a problem hiding this comment.
Agree with Alena here, ETL/ELT does not specifically mean Transformation, my instant question is - what were we talking before then? hehe
| │ | ||
| ├── Optimizing dlt | ||
| │ └── Performance | ||
| ├── Performance |
There was a problem hiding this comment.
I would avoid any content on the 0 level, I mean, to open the "Performance" page you should click Performance, but users very often just open the toggle and click pages from the list
There was a problem hiding this comment.
Agreed with your UI concern. Will fix the inconsistent behavior in our docs. Had previously opened a ticket about it: #3520
| │ ├── LanceDB | ||
| │ ├── Qdrant | ||
| │ ├── Dremio | ||
| │ ├── Destination (custom) |
There was a problem hiding this comment.
I would keep this page and rename it to "Reverse ETL"
| │ └── 1.12.1 | ||
| │ | ||
| ├── Core concepts | ||
| │ ├── How dlt works |
There was a problem hiding this comment.
It looked strange under "Core Concepts". I'll merge it with the early intro pages
| │ └── Education (→ tutorial/education) | ||
| │ ├── Fundamentals course | ||
| │ └── Advanced course | ||
| ├── Installation |
There was a problem hiding this comment.
What about intro? it's a good starting point
There was a problem hiding this comment.
I will add it back after installation
| │ │ │ └── Requests | ||
| │ │ └── [link] 5k+ REST APIs with LLMs | ||
| │ ├── 30+ SQL databases (→ sql_database/index) | ||
| │ │ └── OpenAPI Generator |
There was a problem hiding this comment.
not sure if it's still relevant, with claude and open api spec you'll get your source in minutes without our generator
| │ │ └── Add credentials | ||
| │ ├── Adjust a schema | ||
| │ ├── Dashboard | ||
| │ ├── Access loaded data (→ dataset-access/index) |
There was a problem hiding this comment.
do you want to remove this section completely, or just not sure where to place it?
Dashboard and access can live together under "Data Quality" for example
There was a problem hiding this comment.
Currently, this section is deeply nested and hard to find. Each pages is quite short
Most of this content will go under:
- the concept pages for Dataset and Relation
- our canonical tutotrial "how to use dlt" under the section "access loaded data".
| @@ -0,0 +1,190 @@ | |||
| docsSidebar | |||
| ├── Installation | |||
| ├── Build with AI | |||
There was a problem hiding this comment.
This is a part of paid product - dltHub, we should make sure that it's clearly understandable
| │ ├── Contract & evolution | ||
| │ ├── Export & visualization | ||
| │ └── Naming convention | ||
| ├── ETL |
There was a problem hiding this comment.
Agree with Alena here, ETL/ELT does not specifically mean Transformation, my instant question is - what were we talking before then? hehe
4 participants
Review the git diff "per commit" to see the before and after of the visual organisation of the docs sections