Mugo Web's blog

Google’s recent announcements about its “privacy sandbox” – a collection of browser-based technologies the tech giant is pushing as the new industry standard for programmatic ad targeting – offers a glimpse of online advertising’s probable future following the inevitable demise of third-party cookies.

Prioritizing features for your library’s new website goes well beyond bells and whistles. How will the new site encourage patron engagement, what are the exact hurdles you will need to clear during the project, and how will the site eventually justify your investment?

Business of Apps is always looking to add features to its WordPress websites to keep pace with the rapidly changing apps market, the focus of the B2B publisher’s daily news coverage, opinion, and events.

The Cleaner Solutions laboratory conducts dozens of new, highly detailed cleaning product reviews each month. But an outdated data input workflow and publishing process resulted in the CleanerSolutions.org website being updated irregularly and some research simply falling through the cracks and never being published.

The Ibexa DXP excels at multi-site installations. For example, on the same installation, you can create multiple sites that share the same database, or that share the same code but use independent databases. Different sites can share the same base design and templates, but make use of site-specific overrides where relevant. For sites with user logins, you might need Single Sign-On (SSO) behavior, so that whenever a user logs in to one site, they are automatically logged in to all sites without having to re-enter their credentials. In this post, we'll review how to implement SSO logins on an Ibexa DXP website, specifically one where some of the sites are still using eZ Publish legacy siteaccesses.

If you use Moneris for payment processing, its Hosted Payment Page with data preload increases security, reduces fraud, and ultimately saves the merchant money by reducing chargeback fees incurred by fraudulent card testing.

Deciding to develop your website to conform to the Web Content Accessibility Guidelines (WCAG, pronounced “wickag”) is a positive move that will allow more visitors to consume your content and will help meet impending legal requirements. But how do you get started? What steps do you need to take to make your site more accessible and ensure it stays accessible?

We here at Mugo have helped many teams navigate the website accessibility process. The following outline can help you navigate the process.

When working with Symfony applications, the routing component is key to mapping your website URLs to custom PHP code in controllers. In this post, we explain how to define URL routes and how to use match conditions.

The Rich Text field is one of the most powerful fields in eZ Platform. It enables editors to format content using headers, paragraphs, bold, italic, and much more. It is natively included when you edit content in the eZ Platform Admin UI. Sometimes, however, you need to add editing capabilities to custom pages outside of the standard editing experience. Here’s how to enable editing Rich Text field content on any custom page on your website.

Recently, we built a platform running more than 80 websites on eZ Publish / eZ Platform. New sites would get added to this platform over time, so we needed to automate its ongoing maintenance, including automated SSL certificate renewals.

Librarians who can easily manage the content and pages on their websites say they are happy with the overall usefulness of their sites. Unfortunately, most librarians report they have yet to adopt modern web publishing tools that help make these benefits a reality.

Certain fonts feature glyphs that intentionally overlap.

This largely applies to "brush" or "script" type fonts where the overlap is intentional to achieve the effect of connected letters. Using a web font like that becomes a problem as soon as you try to apply opacity to text using the font.