docs: document new buckets model card metadata field

Adds documentation for the new `buckets` metadata field that links
models to storage buckets (moon-landing#17491).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: Pierrci

docs/hub/model-cards.md

@@ -72,6 +72,9 @@ license: "any valid license identifier"
 datasets:
 - dataset1
 - dataset2
+buckets:
+- bucket1
+- bucket2
 base_model: "base model Hub identifier"
 ---
 ```
@@ -182,6 +185,16 @@ datasets:
 - HuggingFaceFW/fineweb
 ```
 
+### Specifying a bucket
+
+You can specify the [storage buckets](./storage-buckets) linked to your model in the model card metadata section. The buckets will be shown as tags on the model page and the linked bucket pages will show the model in return. You should use the Hub bucket identifier, which is the same as the bucket's repo name:
+
+```yaml
+buckets:
+- my-org/my-bucket
+- my-org/another-bucket
+```
+
 ### Specifying a task (`pipeline_tag`)
 
 You can specify the `pipeline_tag` in the model card metadata. The `pipeline_tag` indicates the type of task the model is intended for. This tag will be displayed on the model page and users can filter models on the Hub by task. This tag is also used to determine which [widget](./models-widgets#enabling-a-widget) to use for the model and which APIs to use under the hood.

docs/hub/storage-buckets.md

@@ -314,6 +314,18 @@ Buckets are well-suited for maintaining rolling backups. With a Git-based [Datas
 hf sync ./daily-backup hf://buckets/my-user/backups/latest --delete
 ```
 
+### Linking models to buckets
+
+You can create a two-way link between a model and a bucket by adding the `buckets` field to the model card metadata. The linked models will then appear on the bucket page, and the bucket will appear as a tag on the model page.
+
+```yaml
+# In the model card YAML frontmatter
+buckets:
+- my-org/my-bucket
+```
+
+See [Specifying a bucket](./model-cards#specifying-a-bucket) in the model cards documentation for more details.
+
 ## Pricing
 
 Storage Buckets are billed based on the amount of data stored, with simple per-TB pricing. Enterprise plans benefit from dedup-based billing, where shared chunks across files directly reduce the billed footprint.