Filed from the dynamic/daisy-content audit.
POST assets takes filename, folder, title, externalId, conflict, publish. There is no alt text, caption or description.
That matters more for AI-driven population than for a human editor, for a specific reason: the moment of upload is the moment the caller has the most context about why the image exists. An agent composing a "meet the team" section knows the image is a portrait of a named person in a specific role. If alt text has to be set later, through a separate write against the Image record, it usually just doesn't get set — and the result is a site populated at speed with no accessible image descriptions.
WordPress's wp_upload_media takes title, caption, description and alt_text alongside the file for exactly this reason.
Proposed
Accept the asset-metadata fields on POST assets and on compositions/page's assets[] items, applied to the created/matched record. Worth considering whether alt text should be effectively required for image types on the population surface — an accessibility default that an agency would want on by default and could opt out of.
Note the existing hash-skip behaviour returns existed: true with the full record for identical content; metadata supplied on a re-upload should presumably still be applied to the existing record, or at least the behaviour should be stated explicitly.
Filed from the
dynamic/daisy-contentaudit.POST assetstakesfilename,folder,title,externalId,conflict,publish. There is no alt text, caption or description.That matters more for AI-driven population than for a human editor, for a specific reason: the moment of upload is the moment the caller has the most context about why the image exists. An agent composing a "meet the team" section knows the image is a portrait of a named person in a specific role. If alt text has to be set later, through a separate write against the
Imagerecord, it usually just doesn't get set — and the result is a site populated at speed with no accessible image descriptions.WordPress's
wp_upload_mediatakestitle,caption,descriptionandalt_textalongside the file for exactly this reason.Proposed
Accept the asset-metadata fields on
POST assetsand oncompositions/page'sassets[]items, applied to the created/matched record. Worth considering whether alt text should be effectively required for image types on the population surface — an accessibility default that an agency would want on by default and could opt out of.Note the existing hash-skip behaviour returns
existed: truewith the full record for identical content; metadata supplied on a re-upload should presumably still be applied to the existing record, or at least the behaviour should be stated explicitly.