<p>Whenever you see an Asset, Entry, Category, or Tag (really, any type of "Element" in Craft), you can double-click the attached tile (in your case, the Asset thumbnail, in your Entry) to get an element editor modal.</p>

<p>This makes editing resources that are one-away much easier than finding it in its element index.</p>

<p>See below for an example:</p>

<p><a href="https://i.sstatic.net/KoUb0.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/KoUb0.png" alt="An example of an Element HUD in Craft 3"></a></p>

<blockquote>
  <p>Two things to note: first, this does happen to be attached <em>inside</em> a Matrix field, but that's just coincidental—this same feature is available wherever you have a relation field (including other modals); second, I have no fields assigned to this Volume, so it's showing two standard fields, the Filename and Title. Your fields will appear below these.</p>
</blockquote>

CC BY-SA 4.0
2018-08-30T06:26:17.203Z
Awesome! I‘ll see if I can add a comment to make it findable for editors and add a required field. Else I‘ll stick to matrix similar to what jon herra proposes
Urs
CC BY-SA 4.0
2018-08-30T06:55:45.513Z
I'll stick to matrix – it's easier to understand for editors
Urs
CC BY-SA 4.0
2018-08-29T23:17:16.520Z
2018-08-29T23:17:16.520Z
August Miller
<p>You could go for a lightweight content-builder. That would mean that you could and would create a matrix blocktype for each of your content elements i.e. one blocktype for image with all the metadata you could chew on as fields, another for say body with some props too and so forth.</p>

<p>That would also give your users some neat control over the document flow.</p>

<p>Then you would saw it seamlessly together on the template layer. Your Content-Editors will not feel a thing.</p>

CC BY-SA 4.0
2018-08-29T22:57:46.610Z
2018-08-29T22:57:46.610Z
Herra Jon
<p>I'd like to add very basic metadata to assets (Alttext, Caption..)</p>

<p>I noticed in volumes you can add custom field types – but they're not appearing when editing the entry. I found it can be edited in the assets view, but that's too complicated for editors.</p>

<p>If those values should be editable in the entry – should the matrix field type be used?</p>

<assets><custom-fieldtype>
Assets metadata: Matrix required?
# Assets metadata: Matrix required?

(Asked by: username_0 on 2018-08-29)

I'd like to add very basic metadata to assets (Alttext, Caption..)

I noticed in volumes you can add custom field types – but they're not appearing when editing the entry. I found it can be edited in the assets view, but that's too complicated for editors.

If those values should be editable in the entry – should the matrix field type be used?

**Tags:** assets, custom-fieldtype


---

## 2 answers

### Answer by username_1 on 2018-08-29. Score: 1 | Accepted answer

Whenever you see an Asset, Entry, Category, or Tag (really, any type of "Element" in Craft), you can double-click the attached tile (in your case, the Asset thumbnail, in your Entry) to get an element editor modal.

This makes editing resources that are one-away much easier than finding it in its element index.

See below for an example:

[![An example of an Element HUD in Craft 3](https://i.sstatic.net/KoUb0.png)](https://i.sstatic.net/KoUb0.png)

> Two things to note: first, this does happen to be attached *inside* a Matrix field, but that's just coincidental—this same feature is available wherever you have a relation field (including other modals); second, I have no fields assigned to this Volume, so it's showing two standard fields, the Filename and Title. Your fields will appear below these.

> **Comments:**
> **username_0**: Awesome! I‘ll see if I can add a comment to make it findable for editors and add a required field. Else I‘ll stick to matrix similar to what jon herra proposes  
> **username_0**: I'll stick to matrix – it's easier to understand for editors  

---

### Answer by username_2 on 2018-08-29. Score: 2

You could go for a lightweight content-builder. That would mean that you could and would create a matrix blocktype for each of your content elements i.e. one blocktype for image with all the metadata you could chew on as fields, another for say body with some props too and so forth.

That would also give your users some neat control over the document flow.

Then you would saw it seamlessly together on the template layer. Your Content-Editors will not feel a thing.


---

