Open Book Canada showcases Ontario’s literary scene, with a focus on books and events produced by the province’s independent, Canadian-owned publishers.
The story of Open Book’s evolution starts with three separate websites: Open Book Toronto, launched in 2007, followed by sister site Open Book Ontario in 2010, and then Open Book Explorer. All three brands were designed to showcase and celebrate books and book culture in Ontario, each with a slightly different angle and approach. But all three had been built on Drupal-based sites, which, over time and with every addition, had become unwieldy, overly complex, and were failing at their objective to manage and showcase great content.
The Organization of Book Publishers of Ontario (OBPO) contracted with the Association of Canadian Publishers (ACP) and its 49th Shelf team to leverage to work they had done on 49th Shelf and its eco-system of book publishing websites, to consolidate the three existing sites into a single, reimagined Open Book site.
The new site needed to enable to Open Book Canada to achieve its goals to:
The resulting website is a widely read and highly regarded online magazine with a robust editorial program that supports multiple posts per day, a writer in residence, and an active events listing service to promote readings, book launches, and other literary events throughout Toronto and the rest of Ontario. The site is supported by book data from 49th Shelf, a linkage that will eventually see Open Book evolve into the largest-ever online platform dedicated to Ontario books and authors.
Open Book is now part of a community of major literary websites in Canada all maintained by the same systems and technology, including the eZ Publish CMS, that enable us to leverage and publish content, including rich ONIX publishing data, with ease. Its relaunch in fall 2016 was received with great enthusiasm by the literary community.
Learn more about our ecommerce websites for book publishers.
Events are the buzziest change between Universal Analytics (UA) and Google Analytics 4 (GA4). There’s a good reason for that — they mark a very substantial shift in how property owners track data on their sites. This is a daunting prospect and an opportunity. As a property owner, you will need to reevaluate how you use your analytics and how you can make the new system work for you. As you make the switch to GA4 before UA’s End Of Service date (July 1, 2023), you might be focusing on just recreating a familiar pattern and making your GA4 property look the same as your old UA dashboard; the better option is to clarify exactly what you need from your site’s analytics and leverage GA4’s superior flexibility to accomplish your goals.
We’ve discussed eep (Ease eZ Publish) several times over the years. It’s a powerful tool we at Mugo Web have used for innovative solutions. For the uninitiated, eep is a collection of scripts to support developers working with eZ Publish. Now that eZ Publish is a legacy product, we needed a new option for eZ Platform and Ibexa DXP. Introducing eep-bundle, a collection of Symfony commands specifically selected to work with the new system! We’ll dive in and look at some of the more useful functions eep-bundle provides, such as commands to work with cache, content, content field and type, location, section, and user data.
If you have a Google Analytics property, you’ve probably heard about the upcoming switch to GA4. You might have seen the banners across the top of the page when you log into UA. “Universal Analytics will no longer process new data in standard properties beginning July 1, 2023”, a polite yet vaguely threatening notification, easily ignored as a problem for next year. If you are proactive, you might have already started the switch to the new platform, having heard the recommendation to run both concurrently until the switch. And if you are like many, that might be as far as you’ve gotten.
Specialty presses have specific requirements that aren’t met by run-of-the-mill websites or standard e-commerce solutions. Their readers are among the most demanding consumers you’ll find online, and they want precise details about your publications, trustworthy reviews, and recommendations from a community of like-minded readers.
A retail shopping cart e-commerce system isn’t up to the standard these customers expect.
This is part of the reason why Mugo built ReaderBound, an all-in-one, a feature-rich website platform for publishers. The specific demands of this industry require an integrated, purpose-built commerce experience.
Libraries provide a myriad of services for their patrons, which requires a lot of coordination and communication. Patrons need multiple ways to interact with their librarians; in-person, via phone, social media, chat, etc. A modern library needs tools to quickly collect information and requests with an intuitive workflow for staff and the public.
When things go seriously wrong in a well-built but complicated system, the cause is often a cascade of small failures that pile up. Not that we’re building rockets over here, but an excellent example is the ill-fated Ariane flight V88. Solving the issues behind such failures can be problematic. Many things contribute to the difficulty, from the extensive use of caching to the need to convincingly reconstruct the failure in retrospect. Debugging this kind of failure, especially under pressure, is hard. We consider the ability to do this to be the hallmark of a senior developer. Even so, it is essential to have a team of experts working together to troubleshoot issues and find solutions promptly to help keep your site running.
If you manage one of the millions of websites affected by the Google-mandated migration from Universal Analytics (UA) to Google Analytics 4 (GA4), you might be following the best practice of simultaneously running UA and GA4 scripts until you’re ready to adopt GA4 fully. One of the analytics features that needs special attention is cross-domain tracking.