Using WordPress? Every integration here is also available as a plugin. Browse the plugin store →

Coming soon — in testing, not yet released

Photo Gallery

Photo Gallery publishes images from a SharePoint library, a OneDrive folder or a SharePoint list as a grid, masonry, justified, carousel or slider gallery with an in-page lightbox — built and in testing, not yet released to customers.

Register interest See what is released today

Photo Gallery is built, and is being tested against real tenants before it is released. Nothing on this page can be bought or embedded yet, and what people ask for is what sets the order things are released in.

linden-museum.example/collection
linden museum
Collection A SharePoint folder as a gallery
Adding a photograph would mean adding a file, not editing a page.

A drawing of Photo Gallery on a fictional site, in our own tokens rather than a customer’s brand. It is a drawing of the arrangement, not a screenshot and not a running widget.

Putting it on the page

The pattern it follows.

Photo Gallery is not released, so there is no embed key to hand out and nothing here to paste yet. It is built on the same script-plus-custom-element pattern as every released component, described below.

There is no embed snippet yet

Embed keys are issued when a component is released, and this one has not been. The three parts beside this note are the pattern it already shares with the released components.

  1. The script tag

    One bundle for one component. It defines the custom element and does nothing else — no framework, no build step, and no change to how the rest of the page is built.

  2. The element

    An ordinary HTML tag, placed wherever the component should appear — including inside a page builder’s raw-HTML block, a shortcode, or a template partial.

  3. The embed key

    The key resolves to one configured instance — the Microsoft 365 source, the arrangement, the theme, and the domains allowed to render it. Change any of those and the page itself never has to be edited again.

What it does

How it works

The Photo Gallery component reads images from a SharePoint document library, a OneDrive folder, or a SharePoint list where each row is an image, and renders them as a gallery with an in-page lightbox. Publishing a photo means putting the file where it belongs rather than editing a page. It is built and in testing, and has not been released to customers.

Why it exists

Photographs are already organised in a shared folder that somebody maintains. Re-uploading them into the website’s own media library and keeping the two in step is duplicated work that quietly stops happening after a few months.

Element
<wpi-photo-gallery>
Reads from
SharePoint document libraries, OneDrive for Business, SharePoint lists
Arrangements
5 in the builder
Graph access
managed or proxy — the tenant chooses

Where it runs

Anywhere you can paste two lines of HTML

A custom element needs no build step and no framework, so where your site is built is not a question you have to answer before this one.

  • WordPress
  • Webflow
  • Squarespace
  • Shopify
  • Wix
  • Astro
  • Next.js
  • Drupal
  • SharePoint pages
  • Plain HTML

Named as examples of places HTML can be pasted. No partnership is implied and none of these are customers. WordPress is the one that gets more than an embed — the same Microsoft 365 jobs also ship as plugins with a Gutenberg block.

In detail

Everything Photo Gallery does.

7 capabilities, every one of them resolved from the embed key rather than written into the page — once the keys are issued.

  1. A folder or a list is the gallery

    A SharePoint document library or a OneDrive folder, either of which can read the subfolders below it, or a SharePoint list whose columns carry the title, caption, image, category, alt text, sort order and link for each row.

  2. Five arrangements

    Grid, masonry, justified rows, carousel or slider; two to six columns; a gap in pixels; an aspect ratio of the image’s own or 1:1, 4:3, 3:2 or 16:9; and cover or contain for how each image sits in its frame.

  3. A lightbox with captions and thumbnails

    Full-size viewing happens in the page, with captions and a thumbnail strip on by default and an optional slideshow running on an interval of 2 to 60 seconds. Downloads are off unless you turn them on.

  4. Search, category filter and ordering

    Sort by name, created date, modified date, size or a manual order, ascending or descending — applied across the whole source before the maximum-results cut, so it ranks everything rather than the first page. An optional search box and category filter narrow a large gallery.

  5. Paging for a big folder

    Up to 500 images, shown all at once or split into pages of up to 200, with a pager, a load-more button or infinite scroll.

  6. The file types it will serve

    JPEG, PNG, GIF, WebP, AVIF and HEIC by default, and the list is yours to narrow. SVG is deliberately not in it: an SVG served from our own origin is script-capable.

  7. The platform settings every component gets

    Domain allowlist, a Google Tag Manager container id, the shared theme tokens, custom CSS, and the same script-plus-custom-element embed pattern as the released components.

Tell us you are waiting on this one.

Photo Gallery is in testing and no release date is announced. What people ask for is what sets the order things are released in, so a sentence about your case is worth more here than a waiting list.

Register interest

Reaching your tenant

Two ways for us to reach Graph. One of them never lets us.

Every tenant runs in one mode or the other, and the choice belongs to your IT rather than to us. It is the reason this works inside organisations that will not delegate Graph access to a vendor.

managed

We hold the credentials

WPIntegrate runs the client-credentials flow for your tenant. Your administrator grants consent once and is not asked again.

proxy

You hold the credentials

You supply a base URL and an API key for your own gateway. We store that key encrypted at rest and never hold a Graph token at all.

Arrangements

The arrangements it offers

Each of these is a setting on the instance, not a different component — the source, the theme and the embed key stay the same when you change it.

  • Grid — two to six columns
  • Masonry
  • Justified rows
  • Carousel
  • Slider

Questions

What people ask about this one.

If yours is not here, ask it — the answers come back from a person rather than a form.

Can we use Photo Gallery yet?

Not yet. It is built and is being exercised against real tenants by our own team, and it has not been released to customers — so it cannot be created in a customer dashboard or embedded on a site. Video Gallery, which does the same job for video, is released today.

Where do the images come from?

Microsoft 365: a SharePoint document library, a OneDrive folder, or a SharePoint list with one row per image. Library and folder sources read the file’s own metadata; a list maps its columns to the caption, category and the rest.

Are the images copied onto WPIntegrate servers?

No. The gallery is built from the source when the page asks for it, rather than from a second copy somebody has to keep in step.

Can visitors download the originals?

Only if you switch downloads on. They are off by default, so a gallery can be viewable in the page without being distributable from it.