Skip to main content

jack.taranto

Jack Taranto
Front end Developer

Location

Sydney

Drupal came to Jack around version 4.7.x and has been working with it ever since. Jack started as a Front End Developer in 2006 and has worked for PreviousNext since 2009 making him our longest running employee. Jack codes in HTML, sass, jQuery, ES6, PHP and Twig and loves everything about Front End Development. Except Internet Explorer. Jack hates Internet Explorer.

My blog posts

Reusable style guide components using field formatters and twig embed

by jack.taranto /

At PNX, style guide driven development is our bag. It’s what we love: building a living document that provides awesome reference for all our front end components. And Drupal 8, with its use of Twig, complements this methodology perfectly. The ability to create a single component, and then embed that component and its markup throughout a Drupal site in a variety of different ways without having to use any tricks or hacks is a thing of beauty.

All your variable are belong to us

by jack.taranto /

The bread and butter work for a themer is printing output on pages. In Drupal 7 there are many ways to achieve this goal: tpl files, Display Suite, theme functions, render arrays, etc. Yet often the easiest way to get some data on a page is via a preprocess function printing a variable into a tpl file.

Mobile advertising using responsive ads

by jack.taranto /

Online advertising is a beast that is inherently un-responsive. Ad blocks with set dimensions are served from a 3rd party provider, making it is as inflexible as a concrete post. So when someone starts talking about responsive ads everyone will always go a little quiet, until someone in the room mutters something like “you can have responsive ads, providing all ad slots on the page are 300 wide”.

Despite that seemingly common attitude, after a little thought it’s really not that difficult to get your head around the concept of responsive ads: An ad provider serves our website three different ad sizes, one for each screen size we’re targeting. We then use a little JS and CSS media query love to show and hide each ad slot depending on the client’s device. Pretty straightforward right?

 

Pagination