refactor: merge Storage usage page into Storage hub#2676
Open
TC-MO wants to merge 6 commits into
Open
Conversation
Absorb storage/usage.md into the Storage hub: intro -> ## Storage types (cards) -> Access -> Named and unnamed storages -> Data retention -> Estimate your costs -> Rate limiting -> Share -> Concurrent access -> Delete storages. Delete usage.md and relocate the three overview graphics onto their type pages. Sweep /platform/storage/usage#x cross-refs to /platform/storage#x across the type pages and academy, fixing the stale #sharing-storages-between-runs anchor to #share-storages-between-runs. Add an nginx 301 from /platform/storage/usage to /platform/storage.
TC-MO
added
documentation
Contributor
|
✅ Preview for this PR (commit |
Drop the access menu that restated its subheadings, hand the retention numbers to the callout, collapse padded sentences to imperative voice. Fix two latent defects (API clients access storages not just datasets; mangled hyphen in the delete-via-API bullet) and strip stray zero-width chars.
Contributor
|
Since you're at it, looks like a great opportunity to update screenshots :) |
szaganek
reviewed
Jun 25, 2026
szaganek
left a comment
szaganek
left a comment
Contributor
There was a problem hiding this comment.
Approved since we'll fix the screenshots together.
| - Check out [the docs about Actor tasks](/platform/actors/running/tasks). | ||
| - Read about the [two main storage options](/platform/storage/dataset) on the Apify platform. | ||
| - Understand the [crucial differences between named and unnamed storages](/platform/storage/usage#named-and-unnamed-storages). | ||
| - Understand the [crucial differences between named and unnamed storages](/platform/storage#named-and-unnamed-storages). |
Contributor
There was a problem hiding this comment.
Suggested change
| - Understand the [crucial differences between named and unnamed storages](/platform/storage#named-and-unnamed-storages). | |
| - Understand the [differences between named and unnamed storages](/platform/storage#named-and-unnamed-storages). |
|
|
||
| ### Apify Console | ||
|
|
||
| In Apify Console, open the [**Storage**](https://console.apify.com/storage) section in the left-side menu. Click through the tabs to view your key-value stores, datasets, and request queues, or select **API** in the top right corner to view related endpoints. To open a storage, click its **ID**. |
Contributor
There was a problem hiding this comment.
I'd change the info an accessing to a procedure, that follows this format.
|
|
||
| To share a storage, select **Share** in the **Actions** menu and provide an email, username, or user ID. | ||
|
|
||
|  |
Contributor
There was a problem hiding this comment.
I think we can get rid of this screenshot?
szaganek
approved these changes
Jun 25, 2026
Address PR review: reshape the Apify Console access paragraph into a step-by-step procedure.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Absorb storage/usage.md into the Storage hub: intro -> ## Storage types (cards) -> Access -> Named and unnamed storages -> Data retention -> Estimate your costs -> Rate limiting -> Share -> Concurrent access -> Delete storages. Delete usage.md and relocate the three overview graphics onto their type pages.
Sweep /platform/storage/usage#x cross-refs to /platform/storage#x across the type pages and academy, fixing the stale #sharing-storages-between-runs anchor to #share-storages-between-runs. Add an nginx 301 from /platform/storage/usage to /platform/storage.