sanity-plugin-media-i18n
v2.3.6TypeScript
This version of `sanity-plugin-media` is for Sanity Studio V3. This version supports i18n fields
0/weekUpdated 1 years agoMITUnpacked: 2.7 MB
Published by Davit Hakobyan
npm install sanity-plugin-media-i18n> This is a Sanity Studio v3 plugin.
Installation
``sh`
npm install sanity-plugin-media-i18n
Sanity Media (for Sanity Studio v3)
> This plugin is for Sanity Studio v3.
> The Sanity Studio v2 version of this plugin is no longer maintained, but still accessible on the v2 branch.
> This plugin is a fork of the original media plugin but with support for i18n tags,titles and descriptions.
What is it?
A convenient way to browse, manage and refine your Sanity assets with the addition if i18n translateable meta fields.
Use it standalone as a browser, or optionally hook it up as a custom asset source and use it to power both image and file selection too.
Features
#### Manage and organise your assets
- Support for translatable fields like title, description and alt text
- Support for batch uploads with drag and drop support
- Edit text fields native to Sanity's asset documents, such as title, description, altText and originalFilename
- View asset metadata and a limited subset of EXIF data, if present
- Tag your assets individually or in bulk
- Manage tags directly within the plugin
- Get previews for audio and video files
- Easily select and delete multiple assets in bulk
#### Granular search tools
- Refine your search with any combination of search facets such as filtering by tag name, asset usage, file size, orientation, type (and more)
- Use text search for a quick lookup by title, description and alt text
#### Built for large datasets and collaborative editing in mind
- Virtualized grid + tabular views for super speedy browsing, even with thousands of assets and tags
- Utilises Sanity's real time updates for live changes from other studio members
#### Fits right in with your Sanity studio
- Built with the same UI components Sanity uses under the hood
- Fully responsive and mobile friendly
Install (Sanity Studio v3)
In your Sanity project folder:
`sh`
npm install --save sanity-plugin-media-i18n
or
`sh`
yarn add sanity-plugin-media-i18n
Usage
Add it as a plugin in your sanity.config.ts (or .js) file:
`js
import {media} from 'sanity-plugin-media-i18n'
export default defineConfig({
// ...
plugins: [media()]
})
`
This will enable the Media plugin as both a standalone tool (accessible in your studio menu) and as an additional asset source for your image and file fields.
$3
You can configure your studio to use this asset source either exclusively, or conditionally enable it based on the type of asset (image or file).
`js
import {media, mediaAssetSource} from 'sanity-plugin-media-i18n'
export default defineConfig({
// ...
plugins: [media()],
form: {
// Don't use this plugin when selecting files only (but allow all other enabled asset sources)
file: {
assetSources: previousAssetSources => {
return previousAssetSources.filter(assetSource => assetSource !== mediaAssetSource)
}
}
}
})
`
$3
`tssource.name
// sanity.config.ts
export default defineConfig({
//...
plugins: [
media({
locales: [{name: 'English', id: 'en'}, {name: 'Dutch', id: 'nl'}],
creditLine: {
enabled: true,
// boolean - enables an optional "Credit Line" field in the plugin.
// Used to store credits e.g. photographer, licence information
excludeSources: ['unsplash']
// string | string[] - when used with 3rd party asset sources, you may
// wish to prevent users overwriting the creditLine based on the
},
maximumUploadSize: 10000000
// number - maximum file size (in bytes) that can be uploaded through the plugin interface
})
]
})
Known issues
Filtering doesn't work on title, description and alt texts
- This is in the works, it will come soon
There isn't a way to edit asset fields directly from the desk (without opening the plugin)
- This is a bit of a sticking point, especially when working with large datasets
- For example, if you want to edit fields for an already selected image – you'll need to go into the plugin and then have to manually find that image (which can be laborious when sifting through thousands of assets)
- A future update will provide the ability to 'jump' straight to a selected asset
- However, exposing plugin fields directly on the desk (e.g. via a custom input component) is currently outside the scope of this project
Drag and drop uploads don't work when selecting with the plugin
- This is currently due to Sanity studio's file picker component taking precedence over window drag and drop events
- For now, you'll need to manually press the 'upload' button if you want to add images whilst in a selecting context
Downloaded images (downloaded with the download button) aren't the originally uploaded files
- Any images downloaded in the plugin are those _already processed_ by Sanity without any image transformations applied
- Please note these are not the original uploaded images: they will likely have a smaller file size and will be stripped of any EXIF data.
- Currently, it's not possible in Sanity to grab these original image assets within the studio - but this may change in future!
Limitations when using Sanity's GraphQL endpoints
- Currently, opt.media.tags on assets aren't accessible via GraphQL. This is because opt is a custom object used by this plugin and not part of Sanity's asset schema.
FAQ
#### I18NWhat language is default?
- English is defaultDo I need to provide languages?
- No, we will use English as defaultIs there a limit on the amount of languages?
- No, there is none
#### Asset fields
Where are asset fields stored?
- This plugin will read and write _directly_ on the asset document itself. This will either a document of type sanity.imageAsset or sanity.fileAsset
- This is analagous to setting values _globally_ across all instances of these assets
- This is in contrast to using the property when defining your document schema (on both image and file objects). Values that you define in the fields property can be considered 'local', or bound to the the document where that asset is linked.fields
- In other words, if you want to set a caption for an image and have that change between different documents – customise the property in your document schema's file/image field
- If you want to set values you can query in all instances of that asset (alternate text being a good example), consider setting those in the plugin
How can I query asset fields I've set in this plugin?
The following GROQ query will return an image with additional asset text fields as well as an array of tag names.
Note that tags are namespaced within opt.media and tag names are accessed via the current property (as they're defined as slugs on the tag.media document schema).
`
*[_id == 'my-document-id'] {
image {
asset->{
_ref,
_type,
altText,
description,
"tags": opt.media.tags[]->name.current,
title
}
}
}
What EXIF fields are displayed and how can I get these to show up?
- ISO, aperture, focal length, exposure time and original date are displayed
- By default, Sanity won't automatically extract EXIF data unless you explicitly tell it to
- Manually tell Sanity to process EXIF metadata by updating your image field options accordingly
- Note that all images uploaded directly within the plugin will include all metadata by default
#### Tags
How and where are asset tags stored?
- This plugin defines the document type media.tag
- All tags are stored as _weak_ references and being a third-party plugin, are stored in the namespaced object
- This behaviour differs from asset fields such as , description and altText which are stored directly on the asset as they're part of Sanity's defined asset schema
How can I hide the Media Tag document type which has now appeared in my desk?
- If you're not using a custom desk, Sanity attaches custom schema defined by third party plugins to your desk. This is currently the default behaviour
- However, you can override this behaviour by defining your own custom desk with Sanity's structure builder and simply omit the media.tag document type in your definition
How can I edit and / or delete tags I've already created?
- You can create, rename and delete tags from directly within the plugin itself
- It is _strongly recommended_ that you manually delete tags directly from within the plugin – doing so will ensure that (weak) references are removed from any linked assets
- Alternatively, you can delete tags either from the desk (if you're not using a custom desk) or via Sanity's API – just be mindful that any assets previously assigned to deleted tags will have 'hanging' weak references. This won't cause serious issues, but it may cause some false positives when searching. (E.g. a search for 'all assets where tags is not empty' will yield assets that have references to tags that no longer exist)
#### Deleting assets
Why am I unable to delete multiple assets, even if only one asset is in use?
- Batch mutations are carried out via Sanity transactions. These transactions are _atomic_, meaning that if one deletion fails (often because it's referenced elsewhere), then all mutations in the transaction will fail and no changes will occur
- To get around this, simply make sure that all assets you've marked for deletion are not referenced – this can be easily accomplished by using a search facet to only show assets which are not in use
#### Uploading assets
How does the plugin determine what should uploaded as a
sanity.imageAsset or sanity.fileAsset?
- As a rule of thumb, when uploading when accessing the plugin as a _tool_ (e.g. if you've acceessed it via the studio menu), it will look at any incoming files' MIME type. All files of type image/* will be uploaded as sanity.imageAsset whilst everything else will be treated as sanity.fileAsset
- If you upload when using the plugin in a _file_ selection context, these be uploaded as
Contributing
Contributions, issues and feature requests are welcome!
License
MIT © Sanity.io
Develop & test
This plugin uses @sanity/plugin-kit
with default configuration for build & watch scripts.
See Testing a plugin in Sanity Studio
on how to run this plugin with hot-reload in the studio.
$3
Run the "CI & Release" workflow. Make sure to select the main branch and check "Release new version".
Semantic release will only release on configured branches, so it is safe to run the workflow on any branch.