CSMonitor.com is the most visited eZ Publish site in North America.
Mugo has been working with The Christian Science Monitor since April 2010. CSMonitor.com is the hub for the online, Kindle, and print editions, as well as for multiple syndication channels. It is the most visited eZ Publish site in North America.
Development work is grouped into 2-week release cycles in order to consistently drive new features. At Mugo Web, we use our experience with eZ Publish and web publishing in general to address a wide range of issues, such as caching, clustering, syndication, ad servers, multimedia content, searching, and more. From inserting social media buttons to tuning low-level cache performance with eZ's Distributing File System clustering, we are trusted to look at all things eZ Publish. We also provide support in multiple timezones.
"The team members we work with at Mugo have demonstrated a high caliber of competency in the work they do, and it instills great confidence in us to know that we have such quality professionals in our corner. Their consistent delivery has helped us develop a fluid system for enacting change and improvements on our website. We certainly look forward to continuing this relationship!"
- Wendy Prugh, Program Manager, The Christian Science Monitor
Over the past year, Mugo has helped CSMonitor.com keep readers on the site by increasing the average number of pageviews per visit by 30%, and achieve a 50% increase in total number of pageviews per month to 36 million. We've helped The Christian Science Monitor have its best fiscal year since 1963.
CSMonitor.com is a busy news website, with dozens of editors posting breaking news and commentary throughout the day.
The homepage and topic landing pages are managed using dynamic layout blocks with the frontpage management tool eZ Flow, which empowers editors to hand-pick featured stories as well as configure blocks that automatically update with new content.
Key article categories include World, USA, Commentary, Business, Environment, Innovation, Science, Culture, and Books. In addition to the more traditional article content type, there are blog posts, list articles, photo galleries, videos, and interactive quizzes.
Microsites feature different designs and sponsorship.
There is significant integration with social media networks such as Facebook, Twitter, Google+, Disqus, and AddThis. For example, users can share personalized quiz results with their friends.
CSMonitor.com has a sophisticated publishing workflow system, which includes content preview, an approval workflow, and scheduled publishing. Editors can create related content links and tag content in various ways. In addition, related content can be suggested and automatically populated using eZ Find (for content from within the site) and using Inform's automated content categorization and tagging (for content internal and external to the site).
Editorial interface enhancements include:
We've implemented a flexible framework for editors to specify common SEO fields as well as extended meta tags for specific search needs, Open Graph, and more.
CSMonitor.com's content model and structure achieves both user-friendly interfaces and efficient page generation. Mugo Web has helped the Christian Science Monitor to dynamically grow and shape its content model, empowering staff and engaging readers. We've implemented new content displays, such as list articles; helped launch new sections, such as their Monitor Breakfast area; and created and improved dynamic layout blocks using eZ Flow.
Automated data import brings in content from an in-house media publishing platform. Data export is achieved in many ways: via an XML format to be consumed by InDesign for print layouts; via RSS for end users; and for content syndication with publishing partners (Yahoo, Amazon, and more) using formats such as nitf, nfb, lmt, newsml, and more.
Content is re-used for the mobile site, so that editors do not have to manage separate content trees for different channels. The mobile site features automated mobile device detection and supports all of the main features and content types of the main site.
CSMonitor.com has an archive installation that hosts articles dating back to 1980.
Mugo is consistently optimizing the website's performance.
CSMonitor.com runs an eZ Distributed File System (eZ DFS) cluster setup, with front-end web servers sharing a file system and a master-slave database architecture. There is a web server dedicated to administrative and editorial interfaces.
We've extended eZ Publish's cache handling functionality to achieve optimal cache clearing rules. We've also optimized the caching settings that get integrated with the Akamai CDN (Content Delivery Network) to balance server efficiency (caching what you can as long as possible) and timeliness of content. Interactive content types such as quizzes have been configured to work in a static cache environment.
We use the Solr-based eZ Find extension to achieve complex content fetches and to generate topic-based pages and automated content lists.
Mugo has improved image handling to reduce dependence on a shared file system. We've added maintenance scripts to organize content and to identify and remove orphaned and obsolete content (such as images and old content versions). We proactively patch eZ Publish issues and submit the code back to the main kernel.
We've implemented advanced performance monitoring for key services such as the databases, the shared file system, and the web servers. We've troubleshooted and protected the site against attacks from greedy news aggregators gone bad and other unexpected sources, to ensure that it runs as smooth as possible.
We use Assembla for ticketing, milestones, releases, wikis, version control, and more. We have individual development environments and a staging environment separate from the production environment.
Mugo Web enjoys the collaborative working atmosphere with The Christian Science Monitor. We work to set realistic expectations and goals and work to satisfy many stakeholders, interests, and business needs. The website presents ongoing new technology challenges, and we are counted upon to help with the continued success of the news organization.
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.
A great deal is only “great” if it ends up paying off in the long run.
This truth is perhaps best expressed by author Terry Pratchett in his “Boots theory” of economic value, as laid out in his iconic Discworld novel series:
The Toxics Use Research Institute (TURI) at the University of Massachusetts Lowell wanted to add memos to records in its Pollution Prevention Options Analysis System (P2OASys), a database for evaluating and comparing the safety of chemistries. TURI could have elected to simply add a field to its database structure, but it saw a bigger opportunity to reinvent a key system that had not been updated for more than five years.
Business data is inevitably distributed across multiple systems. However, we know that customers are not prepared to deal with that kind of complexity, especially when they see little relevance or value to the task at hand. A typical location for this kind of friction is in the integration of the Content Management System (CMS) and the Customer Relationship Management system (CRM). Integrating the two can help provide a seamless experience for the customer and increase the overall usability of your website.
Websites are not static things; they are a dynamic part of your company and the actual storefront for all of your online customers. Most companies acknowledge the importance of upkeep on their brick and mortar branches, websites often aren’t given the same consideration. Your website should constantly evolve to keep up with current standards, trends, and the functionality your clients deserve. We often don’t realize what opportunities we are missing and what we are leaving on the table by relegating website maintenance to the bottom of the list.
Promoting events and managing attendee registrations is one of the key ways a modern website supports a public library's educational mission. Here at Mugo Web, we’ve developed a comprehensive Custom Event Registration System that lets library staff schedule recurring event series, create waiting lists for popular programs, and even manage sign-ups for multiple children from one family.