Docs: Stub out new 'building' structure #212
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description 📝
Previously, our documentation structure was scattered across conceptual categories that didn't align with how developers actually build applications:
Now, the documentation follows a logical build-test-deploy workflow that mirrors the actual development process:
The restructure creates a natural progression: developers start by creating a project, connect their data sources, build and test locally, evaluate accuracy, configure advanced features, add custom logic, create automations, and finally integrate via APIs. This eliminates the cognitive overhead of jumping between conceptual categories when following practical tutorials.
We've also renamed key sections for clarity - "Data Sources" becomes "Connect Data Sources", "Business Logic" becomes "Add Custom Business Logic", and "PromptQL APIs" becomes "APIs and SDKs" - making it immediately obvious what each section helps you accomplish.