If your library publishes from an Omeka S collection, whether that's exhibit pages, LibGuides, newsletters, or a blog like this one, you know how much quiet friction lives in the gap between "we have this digitized" and "it's now on the page." You open the collection in o…

Recently, we ran into an issue across several hosted Omeka sites where bots were hammering search and item pages, driving CPU usage to 100% and slowing everything to a crawl.

Generate preview cards you see when your Omeka S links are shared on Twitter, Facebook, or Slack.

I built a Data Visualization Builder module for Omeka S that turns collection metadata into interactive charts, maps, and timelines. Here's what it can do.

I've been building a lot with Omeka S lately and one of my favorite recent projects is a Chatbot module that lets visitors have a real conversation with a collection.

Omeka S includes a basic asset manager - but as your site grows, a flat list of files quickly becomes hard to manage.

I’m excited to share something I’ve wanted in Omeka S for a long time: a full-featured blog module.

Managing a collaborative digital collection means trusting multiple people with the ability to create, edit, and delete resources. That trust is easier to extend when you have a clear record of what actually happened.

Anyone who has managed a collaborative website knows the sinking feeling of an accidental edit. A block of carefully written content gets replaced, a page structure gets reorganised the wrong way, and there's no undo button.

Every digital collection is only as safe as its last backup. The Backup module for Omeka S was built to make that backup a reliable, repeatable, and fully self-contained operation - no extra server software required.