Consider adding a new property type "asset" or "asset_url"

[michael]

E.g. this would apply for the image node type in editable website.

https://github.com/michael/editable-website/blob/main/src/routes/create_session.js#L210-L222

Question is if this concept should be introduced in svedit or if its rather app-land. we just need a way to figure out which nodes are referencing assets. so we can track which asset is referenced where and when orphaned assets can be safely deleted.

Maybe it's more flexible to add "asset" as a possible property type. like the "src" attribute of image would be of type asset, because it points to a file. then we could reuse that mechanism for other files like mp3s or pdfs etc.

[johannesmutter]

Do you think the editing behaviour would be different between type "block" and type "asset"? If not I think it would rather add complexity (another concept to know about). I personally did not yet feel the need for a different node type when working with image/ video assets or external videos like Vimeo.

[michael]

Yeah i think node kind is off the table. that doesn't make sense. a special property type 'asset' may make sense assuming that almost all backends will need some way to reason about properties referencing assets. but then again, maybe i will just start doing this in app-land to see the full picture. Adding a property type would avoid scattering schema metadata to different places, but technically you are correct that for svedit on the client the property being a string is fine, doesn't need any more information. this hint is only useful for the server to track asset references.