-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: restructure getting started #1749
Conversation
e4b9730
to
3fd275e
Compare
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
ask a question. | ||
|
||
When you register for Flow, your account will use Flow's secure cloud storage bucket to store your data. | ||
Data in Flow's cloud storage bucket is deleted 30 days after collection. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
20 days?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it? We refer to 30 days in the current docs
@@ -195,7 +195,7 @@ captures: | |||
|
|||
Your capture definition will likely be more complex, with additional bindings for each table in the source database. | |||
|
|||
[Learn more about capture definitions.](/concepts/captures.md#pull-captures) | |||
[Learn more about capture definitions.](../../../../concepts/captures.md) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it not preferable to use root relative paths rather than document relative paths?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmm yeah you're right, updated these changes. still need to remove the non-existant anchor
This PR restructures the beginning of the docs site to try and streamline the onboarding experience for new users. The main goal is to push down complex technical instructions (storage setup, flowctl, etc.) and emphasize dashboard-based onboarding actions with examples.
This change is