Peter Knight

Yes already have it done. Each asset has a details page with a Usage table. This lists the places where an asset is used etc. The attached should give you an idea even if this asset is only used in one place.

Media Hub update The Media Hub now has a folder view Folders is the default name for the view. It can be renamed to Gallery, Collections, Assets, Media, etc. Media assets can exist in one or more Folders so essentially they operate like Tags Clicking a Folder name will filter the main MediaHub by items within that Folder (and optionally sub folders) On an Asset detail view, you can quickly add and remove an association to a folder Support for Folder nesting, renaming etc is working

Incidentally, when you mention you reached limits of performance, where and how did those limits manifest? I ran your query / issue through my AI Agent and had the following response. The Real Diagnosis Your friend likely experienced real slowness, but the cause is almost certainly inefficient query patterns (loading too many pages at once, N+1 queries, unindexed searches) rather than a fundamental limitation of pages-as-assets. These are the same problems any ORM-based system hits at scale, and they have well-known solutions. What MediaHub Would Need for 100K Assets Problem Fix Effort Crops filter loads all crop pages Direct SQL: SELECT DISTINCT master_id Small N+1 crop count per listing Batch query or denormalized count field Small LIKE search on title/desc Add FULLTEXT indexes Small Tag dropdown loads all tags Already paginated or use autocomplete Small No query caching Add WireCache for expensive queries Medium Standard pagination at scale PW handles this natively with start= + limit= Already done Streaming large exports Use $pages->findMany() (lazy loading) Small None of these require rethinking the data model. They're standard database optimization work. Summary The page-per-asset architecture is sound and scalable. ProcessWire's page model with proper indexing handles 100K+ pages without issue. The current MediaHub implementation has a handful of query patterns that would need optimization (mostly the crop filter and N+1 counts), but these are straightforward fixes. Switching to a JSON-in-field approach would solve the wrong problem while creating a bespoke data layer that loses most of PW's value and introduces its own harder-to-fix scaling issues. //END What do you think of above

Hey David Thanks for that. I am planning another sprint next week. Right now, I am approaching this from a traditional image-as-page approach. Each crop variation of a 'master' image is also a separate page. That's possibly not as good for scalability but better from the point of view of having a new page image field listing all my images and crops. I dont have any sites with 10K + images so I'm happy enough with this solution but I will certainly reconsider and you've given me some other ideas too which I'll tackle next week. Will DM you re. other items. Cheers

Sounds great. Any examples or screenshots for us?

Anyone tried OpenClaw yet on a local machine? I see lots of tweets about Mac minis and OC and people running much cheaper agents etc

Sure, just visit cursor.com on a mobile device and log in. Look for the Agents link in top right. Select your project and branch if you’re connected to Git Then if you’re out, at the gym or on anywhere away from desk I just dictate the features I want and let the cloud agents run.

Toon link. Less readable perhaps than JSON for humans but it’s created for and optimised for machines

That’s amazing. I note you chose JSON for export. Have you seen the token optimised Toon? Might be a good additional option or even YAML? Looking forward to trying P

I’m on Cursor Ultra and have been for some time. Even on Ultra I am frequently hitting my plan limits and while I don’t mind paying more, I’m going to rely less on the highest end models soon and start trying auto mode more. I’ll try to do more manual coding for the tasks I can do and stop leaning on agents for CSS changes etc.

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.

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?

Don’t forget Cursor cloud agents. Give a cloud agent a plan and the agent works in the background while you’re away from the laptop. I give them a task on the iPad when I’m at the gym and by the time I’m home there’s a new branch waiting for me. I can’t verify this but somehow I’ve often found the quality of the cloud agents to be better than the desktop ones even on the same model. Can’t be true? But feels that way.

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”.

It's good to see Cursor getting a bit of airtime and some mentions. Been using it since around 2024, and it's improving rapidly. The latest AI models too are impressive. It helps me with development, some UI design, SEO and pretty much is across 90% of my daily work these days apart from some design work. One of the best things about AI Agents is they can run in the cloud. So I'll often fire up a Cusror AI agent while I'm out for a walk or at the gym. I get home and the development work is ready for review and merge. I have yet to use Claude Code yet but I also see people speak highly of it. It's more terminal-based. Worth a look. Especially with Claude's new skills. Here's a good video from a Meta Engineer using CC.