From Quick Share to Custom Microsite: Choosing the Right Way to Distribute Your Brand Assets

Ask a photographer why they carry more than one lens, and the answer is rarely that one lens is better than the others. A wide-angle lens does something a macro lens cannot, and neither one is right for every shot. Choosing how to share your brand works the same way.

If your team needs to get brand assets in front of an audience, partners, distributors, agencies, or the public, there is more than one right answer inside Acquia.

The question is not which option is best. It is which one matches what you are actually trying to do. For many teams, the answer is more than one of them.

Here is a look at three options: what each one is genuinely good at, and what to consider before choosing.

Standard Portals: the fastest way to share what is already approved

A Standard Portal is a simple, self-serve hub. It pulls approved assets from your Acquia DAM library and puts them behind a shareable link. Options for login required, password protected, or public for whoever is on the other end.

Where it works well: You need to get a defined set of approved files, images, documents, and videos, to a partner, an agency, or a distributor, and you need it live in minutes now. No need for heavy design or layout choices. Just get assets out quickly.

A limitation to consider: A Standard Portal is not built to carry your brand's look and feel. It is a functional container, not a branded experience. You can include a logo and colors but not much further.

Brand Portals: the same speed, more branding and light navigation

A Brand Portal does everything a Standard Portal does, with your visual identity and a set of real brand tools built in: a color palette section with HEX, RGB, CMYK, and Pantone swatches, a dynamic gallery that updates automatically as your DAM changes, and a navigation menu that lets visitors move between sections instead of scrolling one long page. It is a genuine step up in both design and organization

Where it works well: The same quick-turnaround sharing use case as a Standard Portal, but for situations where the experience itself needs to look like it came from your brand, a distributor hub, a regional partner page, a media kit.

A limitation to consider: Font and layout options are limited compared to a CMS. There is no way to build a header or footer once and reuse it across hundreds of portals, so at scale, every portal is maintained by hand instead of updated from one source. And while Brand Portals include some analytics, heatmaps and click-path data are not part of that, a gap that matters if understanding visitor behavior is as important as sharing the assets.

Source CMS with DAM Asset Gallery: when you need a full microsites, not a share link

This is a different kind of capability. Acquia Source's AI Site Builder Agent turns a brief into a full, multi-page, on-brand site, and DAM Asset Gallery brings your governed asset library directly into it, the same library behind your Portals, so the people building and visiting that site are working from the same approved files as everyone else.

Where it works well: A custom brand toolkit for a business unit or a client. A campaign or product microsite with real structure, multiple pages, its own navigation. A single home page that brings several existing portals together in one place for an audience that should not have to know where each piece lives. Anywhere a team has been quietly recreating the same layout by hand because nothing else fit.

Another reason this matters: because it is a real site, not a shared folder, it comes with real site analytics. If this page is core to a go-to-market push, a product launch, a campaign you need to prove out, you get heatmaps, click data, and the kind of visibility into what visitors actually do that a portal was never built to provide. That is useful the moment this stops being a nice-to-have and becomes something your team is measured on.

A limitation to consider: This is not the tool for a five-minute asset share. It’s not a heavy lift, but it does take more setup to build reusable components. If all you need is to send a partner 20 approved files, reaching for a full site is more than the moment calls for.

An overview of Acquia’s Portal and Microsite offerings for DAM

How to decide

Think of this less as a single choice and more as a scale. Grabbing a handful of approved files calls for a Standard Portal. Needing that experience to look and feel like your brand, with some structure to navigate, calls for a Brand Portal. Needing something with real pages, its own analytics, and room to grow, a toolkit, a microsite, a home base for several portals at once, is where Source CMS and DAM Asset Galleries take over.

You don’t need to settle on one option. You can use two or three based on your business needs. Quick shares where speed matters. Brand portals for some branding and higher asset counts. Full custom microsites for highly visible, highly branded distribution. Most working photographers carry more than one lens. You can match Acquia’s asset distribution tools to the job.

Curious which combination fits what you are working on right now? Talk to your Acquia representative today.