We are happy to announce that Boyle Software is now an official partner of Contentful, the content infrastructure platform that allows content providers to easily create, manage and distribute content across multiple channels.
Category Archives: CMS
Introducing the new Dstillery.com!
For the last few years, I’ve been working closely with Dstillery to develop a variety of consumer tools within the digital advertising space. As we collaborated with data scientists and engineers to create tools for their clients to manage and understand their audiences, it felt like a revamp of the corporate website would be in order. With every new product, we were enabling their customers the ability to effectively understand their data. We wanted to convey to potential customers that same feeling—data isn’t scary. Continue reading
Come Code With Us!
Over the past several months, we’ve had a number of developers join our team in New York and Ukraine, but we’re constantly growing and we are still looking for more! Continue reading
Galvanized signs up for HeartyHosting
We are pleased to announce that Galvanized Media has brought two of their most popular websites onto our HeartyHosting platform. As of July 1st, both Eat This, Not That! and Best Life are now on Boyle Software’s powerful cloud-hosting service, optimized for the kind of high-traffic these media sites receive on a regular basis. We have been handling overall development of Galvanized’s WordPress sites for several months now, but we are really happy that they have selected HeartyHosting for this pair of flagship properties.
Basic Drupal theme with Gulp as a task runner
Building custom themes for Drupal can be done with tons of approaches and many different ways of automating routine CSS operations. Here is the short list of tools I use with Gulp that I find solve close to 100% of the most common needs for Drupal (as well as for other CMS custom development). Feel free to share your thoughts on this list in the comments below. Continue reading
The all-new OK! Magazine
Last month, the Boyle Software team working with American Media, Inc., launched a completely redesigned and upgraded website for AMI’s popular celebrity magazine OK! – https://okmagazine.com
Lots of new features were introduced with the new OK! revamp: an “Exclusives” carousel, a “Blast from the Past” block, “Trending” zones, and a bunch of UX improvements. Photo galleries were improved not only in design but a “switcher” was also added, giving editors the ability to choose between different layouts: slideshows, list views, etc.
Drupal 8: Taxonomy Terms by Level
In Drupal 8, sometimes we have a lot of levels of taxonomy terms and we need to manage this in our code. For example, what if we need to get a specific level of the taxonomy?
So let’s imagine the following taxonomy tree:
A fix for Drupal 8’s broken preview
Drupal 8 is still beta-ish in so many aspects, that “workarounds” is becoming a separate genre of Drupal development tips and tricks.
The today’s workaround is for the bug in “node preview” functionality. It is not frequently used, but can be rather convenient for large websites with moderation enabled. The bug can be spotted only when CSS styles, applied to the node/page template rely on the <body> CSS classes, namely the core-added page-node-type-[node bundle] body class. It helps to effectively distinguish different node templates, and therefore are widely relied on by front-end developers. However, in preview mode, this class appears entirely missing, which breaks the styling.
A Drupal Tune-up for the Bike Club
We spend a good deal of time touting our work for “bigger” clients – but we take just as much pride in our work for the “smaller” ones. Over the years we have done lots of work for non-profits like NYC Swim and the Byrd Hoffman Water Mill Foundation and we’re pleased to have recently added the Five Boroughs Bicycle Club to our client roster.
Drupal 8 Migration: Field Updates
By default, the migrate module in Drupal 8 updates existing nodes by completely overwriting all the fields in the target node with the data from the migration. But what if your client has modified content on the target (D8) system, and still wants to update the content with newly-mapped fields? For instance, there is a “description” that has been updated after the first migration, but now the client wants “subtitle” field to be migrated (which was empty or not present during the first pass), without overwriting the description field changes. Continue reading