Archive of past Mugo Web projects
While many Mugo projects transition into long-term partnerships, we are also called upon to help companies with specific projects for short-term goals. Our team are trusted experts, who can support in-house developers in many different enterprises. We're proud of the work we did in these cases and are happy to showcase our experience.
Mugo partnership 2014
Hootsuite's website had been created by great organic growth, but as their company and needs matured, they sought out an enterprise content management system. It needed to be scalable, enable quick content changes, support many integrations, and bring together multiple departments. They chose eZ Publish as the CMS and Mugo Web as the principal implementation team. For the entire year during implementation, Mugo Developers worked from the Hootsuite offices as their in-house development team.
Together with the Hootsuite marketing team, Mugo built a framework independent of the Hootsuite product stack to support future growth and content management best practices so that the website could be a lead generation machine.
Mugo did the following at Hootsuite:
Mugo partnership 2015
eWEEK was the flagship publication of QuinStreet Enterprise. Originally PC Week when it launched in 1983, it covered technology news, enterprise IT trends, and reviews of new tech products in a variety of digital formats.
Mugo built a new website for eWEEK that enabled:
Mugo partnership 2008
Mugo migrated Car and Driver's website, holding 50,000 content objects, to run on a platform based on eZ Publish. We focused on implementing a new design, setting up new content organization, and implementing some enhanced, interactive features such as an advanced image gallery and a car configurator.
Mugo partner since 2025
St. Thomas Public Library launches new website with expanded features.
The latest improvements to the Mugo Library platform focus on enhanced usability for library staff. Since these back-end improvements aren’t as noticeable as the front-end user experience, we wanted to take the opportunity to give a peek “under the hood”, and showcase what makes the Mugo Library event and calendar solution ideal for public libraries. Our new enhancements include expanded reporting, a new viewing interface, back-end patron search, and integration with the meeting room module.
One of our clients needed to migrate all their customers to another entitlement service, requiring them to create new Single Sign-On (SSO) accounts. Concerned that many customers might struggle with the SSO setup process and overwhelm the customer support team, Mugo designed a "graduated authentication" system that dynamically balanced temporary free access with required account creation, allowing our client to manage customer support workload in real time. Instead of forcing all customers to the SSO setup at once, a smooth transition was implemented, providing immediate support for anyone who needed it.
Responsive images are a cornerstone of modern web design. They enable websites to deliver optimized visuals that adapt seamlessly to a wide range of devices, screen sizes, and resolutions. By serving appropriately sized images based on the user’s device capabilities, responsive images ensure fast load times, reduced bandwidth usage, and a consistent visual experience.
Recently, we added a new feature to the Mugo Library all-in-one CMS solution for library websites to make it easier for patrons to search for their event registrations. This enhancement makes providing quality customer service in libraries easier and puts more control in the hands of patrons.
Many of our solutions use Solr as a search engine. We find that Solr can provide powerful and flexible search experiences, customizable through its configuration. In this case, we resolved an issue where very generic names of important pieces of content were making them harder to find.
Caching plays a critical role in the performance and scalability of websites. One of the most important tools for controlling caching behaviour is the Cache-Control HTTP header. This header defines how responses are cached by browsers, reverse proxies, and CDNs, and how long they remain valid.
In complex websites, different page types often require different caching strategies. For example, on a news website, an article page may be cached for a few hours to a day, while the homepage — where content changes frequently — may only be cached for a few minutes.