Assets in Milo Sites

[Ben-Zahler]

hi all,
in our portal, users should be able to download assets such as ppt, pdf, mp4 and zip files.
Additionally authors should be able to maintain metadata about the assets such as keywords (for our search engine) but also manage asset expiration dates.
Has someone implemented this in Milo? Is this actually officially supported in Milo?
@auniverseaway @honstar @narcis-radu

[mokimo]

Sounds like classic DAM functionality. I'm not aware of anything - the franklin discord might be able to help if none of the milo community can.

[Ben-Zahler]

thanks @mokimo , I did find in the franklin discord an AEM assets plugin: https://www.aem.live/docs/aem-assets-sidekick-plugin
I started a discussion in the discord, let's see if there is some response.
https://discord.com/channels/1131492224371277874/1244984252571844670/1244984252571844670
In the end, it seems that we need to keep the AEM instance simply for hosting our assets.

[mokimo]

Glad discord was a good pointer and you got an answer from Lars of the core team.

Hi Ben, yes this sounds like a job for AEM Assets, in particular the brand portal https://business.adobe.com/products/experience-manager/assets/brand-portal.html

[Ben-Zahler]

@mokimo unfortunately, I'm not sure if the brand portal meets our requirements.
Does anyone know if brand portal is available for Milo projects? What does it take to get brand portal set up?

[mokimo]

😕

It might be a good question to cross post on #milo-community - GWP doesn't really look into our dev discussion boards - they might already have a solution for assets.
Haven't heard about the brand portal yet, so not sure if someone already had set that up

[auniverseaway]

There's a couple things to unpack here:

1. Helix doesn't support any asset management.
2. Word's file format deficiencies makes any real asset management effectively impossible.
3. SharePoint is potentially a solve here, but probably not ideal. You would bolt on features like on/off or metadata management.

Even Dark Alley's asset integration which fixes item #2 would not really apply for your use case.

If you want to manage asset metadata and the lifecycle of asset availability, you are probably looking at using AEM Assets (or any of the newer flavors). If it was me, I would probably not use on-prem or Dexter since it would be awfully heavy for the use case... @sukamat or @npeltier or @honstar or @jenssingler please chime in here. I say this only if you want to make a clean break from current on-prem AEM. If you have an instance + dexter you want to re-purpose, I think that's a great path, too. The best migration is no migration.

At that point it's a mostly known problem: typical CDN type considerations, etc. and you would make links to content on Milo / Edge Delivery pages. Potentially even making some sort of feeds endpoint hosted out of your AEM instance.