08.12.2016 Views

Mariquita Book - mk2

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

We were always keen at Classic Boat to create covers that had an<br />

impact. By 2014 we were happy with our new design and logo,<br />

and it’s always a sign of true confidence when you can cover up<br />

the magazine’s name albeit partially. It’s a confidence trick on<br />

the reader to leave out so much type but with <strong>Mariquita</strong> under<br />

full sail it looked like she was jumping off the page.<br />

Dan Houston<br />

Editor, Classic Boat<br />

When you are putting a boat like <strong>Mariquita</strong> on the cover, you<br />

want to get it right. Of course, we work hard on every Classic<br />

Boat cover. Often they go through endless permutations, with<br />

different boats, different angles, different words … but boats<br />

like <strong>Mariquita</strong> don’t come around too often. This was the<br />

first time in a while that we’d had real access to the yacht.<br />

The quality of photography was not a problem. Those lines<br />

are remarkably kind on the lens. But which image to choose<br />

of one of the world’s most photographed boats? The image<br />

we chose – one of quite a few options on the table, as I recall<br />

– captures the thrill of seeing her under full sail, and we felt<br />

it said more to our readers about what the magazine was<br />

about that month than even the Classic Boat logo. It would<br />

be a marketing mistake to obscure the logo in its entirety,<br />

but <strong>Mariquita</strong>’s topsails made up in abundance for anything<br />

missed in typography. This October cover of Classic Boat was<br />

a special edition for distribution through the Med in which<br />

<strong>Mariquita</strong> is well known.<br />

Peter Smith<br />

Senior Art Editor, Classic Boat<br />

44

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!