⚠ This page is served via a proxy. Original site: https://github.com
This service does not collect credentials or authentication data.
Skip to content

Conversation

@Danielle9897
Copy link
Member

This keeps your active dataset lean while preserving historical data.

### Use cases

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should comply with our standard start pages format (see the AI agents start page for example - a few summarized use cases, can add detailed ones within the documentation, e.g. in the overview for little more details or on its own page as a preparation for future real use cases with examples etc.)

The team gets faster queries, smaller indexes, and lower storage costs - while still being able to load any archived order when needed.

### Technical documentation links ✨

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

needs to comply with the standard format here too (use image cards, e.g. to basic API/Studio pages)

@@ -0,0 +1,55 @@
---
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

generally (unrelated to this page), isn't the data archival documentation a natural candidate for the Documents folder? (not necessarily in this PR, but might as well)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants