[WIP] Media Hub - the centralised hub for your PW media

[Peter Knight]

Hey, I've started to create a Media Hub for Processwire.

[Edit...newest updates to UI are in later posts]

Screenshots attached. Obviously a few UI improvements are needed 🙂 

One of my clients requested a centralised media manager. I thought it'd be fun to give it a go and learn some stuff.

I know that with a self-built Module, it'll always be maintained, and I have an active interest in evolving it.

Shout out to @markus-th who just announced he is doing similar with WireMedia.

 

[Stefanowitsch]

Looks really good, too. I would like to give it a try when it is ready. A media manager solution is a must have feature IMHO.

[Peter Knight]

14 minutes ago, Stefanowitsch said:

Looks really good, too. I would like to give it a try when it is ready. A media manager solution is a must have feature IMHO.

I'd love some early testers, Stefan. Thanks for the offer.
If you're interested in trying it on a non-commercial site and are happy with temporarily breaking changes, I will be in touch when I'm a bit closer to the first version.

[Peter Knight]

Hey everyone, I have some updates to MediaHub to share.

Media Hub view

Screenshot of the Grid view...

• This is the grid view showing a thumbnail of all your images.
• Each card has helpful meta data (PNG, file size etc)
• Some images have crop applied denoted by the small pink badge. IE Lisbon tiles has 4 crop versions.
• Usual filters at the top and a search bar.

Screenshot of the Table view.

• Handy if you have hundreds of images
• Displays tags too

Screenshot of the Upload / Drag and drop mode

• There's some nice aniamtion / UI when the system is uploading several images

Tomorrow I'll share more...

 

 

 

 

 

[Krlos]

This looks awesome!

[10101]

This looks great!

Any chance you could share a bit more detail on how file storage and file usage in page templates will work?
Also wondering if there’ll be a custom field type replacing / extending the core image/file fields.

[Peter Knight]

Some more work. Not sure why the images are so fuzzy

Image detail page

• You can edit the usual stuff...Title, Alt, Description, and add Tags etc
• Some utilities in there too such as Download, Copy URl, Duplicate, Delete
• If an image has Crop versions they are displayed under the main image
• Crop versions has thumbs and table view
• A crop version has a detailed view too

Image Crop page

• There are presets, but you can create your own named crops
• Save as a crop version or save as a new image. 

The hardest part is in progress which is

1. A custom Inputfield which allows you to add images from the MediaHub. All while maintaining a connection back to the hub source file. IE it's important that there's no duplication and that the images in the Media Hub are a true source / canonical version
2. Displaying images in the page edit field in a nice consistent way with the existing UI. As much as possible, I want the user to feel like this the core and not some bolt-on with its own CSS. Although I am changing some things…

Hope you like!

P

 

 

[Peter Knight]

22 hours ago, 10101 said:

This looks great!

Any chance you could share a bit more detail on how file storage and file usage in page templates will work?
Also wondering if there’ll be a custom field type replacing / extending the core image/file fields.

Yeah sure. This is how I’m proceeding…

Every file is a page and has its own id folder. I guess that part is predictable enough.

Crops are simply variations of an image. They are stored in the same id folder with their own unique name.

Re. image fields, there’s a custom field which is designed to look and feel like a normal image field, but isn't a regular image field. 

A user adds images to the image hub field, but they are living, connected references to the source hub. IE the image hub assets are not detached copies. The hub is meant to be the centralised media hub. Otherwise, it wouldn’t be much of a hub.

At least that’s how it’s working right now. 🙂

 

 

[Peter Knight]

19 hours ago, Peter Knight said:

Crops are simply variations of an image. They are stored in the same id folder with their own unique name.

Rethinking my Media Hub cropping model 😑

I discovered a limitation when adding images via my new ImageHub field: selecting a crop doesn’t add a second item. Instead, it replaces the first crop selection.

Root cause: the field stores a PageArray / reference list keyed by page ID, so it silently dedupes. All crops belong to the same master image page (same ID), so you can only reference it once.

I’m leaning toward treating each crop as its own image/page (unique ID) with a master_id link, so multiple crops can be selected, ordered, reused across pages, and tracked for “where used”.

 

[maximus]

Hello, Peter.

Thanks for the updates — it's clear that you're moving fast and in the right direction.
Lots of screenshots, lots of details, it already looks solid.

Good luck with the improvements. Take your time, but also don't delay — the potential of the thing is good.

[Peter Knight]

How does everyone feel about folders? I have tags working but I am also considering Collections.

A photo could belong to one or more collections. In the background I’d allow the agency/developer to rename collections as folders. I know collections are more powerful but many clients are more at home with the concept of folders. 
And I feel like, why make them choose?

[Peter Knight]

6 hours ago, maximus said:

Hello, Peter.

Thanks for the updates — it's clear that you're moving fast and in the right direction.
Lots of screenshots, lots of details, it already looks solid.

Good luck with the improvements. Take your time, but also don't delay — the potential of the thing is good.

Cheer for the support Maximus. Having one of those days where I need a break from it all but more coming soon. Good to hear it’s useful.

[taotoo]

On 2/10/2026 at 11:13 PM, Peter Knight said:

the image hub assets are not detached copies.

I like this approach a lot - looking forward to seeing it in action!