Turin was a CSS image-hover library built around animated transparent-border treatments. Its archived documentation survives as a useful reference for recognising an older component and understanding how its classes were arranged.
This page consolidates that documentation in fresh language. It is not a new Turin release, and no verified redistributable Turin package is offered here. For a preserved downloadable library with live examples, see Izmir; the two libraries have related conventions but are not identical.
Recognise the base markup
The old installation page loaded turin.min.css and used a figure with class c4-turin, containing an image followed by figcaption. A missing stylesheet cannot be repaired by adding more classes. Confirm which file an existing project actually loads before changing its markup.
<figure class="c4-turin c4-border-slide-bottom-left"
tabindex="0">
<img src="sample.webp" width="800" height="600"
alt="A labelled sample of the project">
<figcaption class="c4-layout-bottom-left">
<div class="c4-reveal-up">
<h3>Project details</h3>
</div>
</figcaption>
</figure>
This is an illustrative reconstruction of the documented structure, not a functioning example without Turin’s CSS. Replace the sample image and alt with meaningful content. A focusable demonstration also does not become a link merely by having a hover effect.
Border families
The documentation listed fade, zoom, slide, vertical/horizontal, skew, flip, hinge, slam, deal, reveal and spin treatments. Their selectors begin c4-border-. Direction is part of the name: c4-border-slide-bottom-left is a different option from c4-border-slide-left.
Apply one border choice to the figure. For a repair, preserve the existing selector until you have established the library version: replacing a Turin class with an apparently similar Izmir class may change the border construction rather than just its direction.
Image treatments
The documented image family includes c4-image-zoom-in, c4-image-zoom-out, directional pan, left/right rotation and blur. These classes belong on the figure. They affect how much of the source image remains visible inside the component; inspect important content near the edge after a crop changes.
Text and delays
Caption items can be wrapped separately to reveal or fade them in different directions. The named choices include c4-reveal-up, c4-fade-left and c4-rotate-down-right. A wrapper lets a heading and its description move together without assigning an animation to every word.
The delay page’s code examples use c4-delay-200, c4-delay-400 and c4-delay-600 on caption wrappers. Its prose abbreviates the prefix and describes steps of 100 milliseconds through 1000. Check the stylesheet in the project before relying on an abbreviated name. Long delays can leave a card apparently empty while someone is trying to read it.
Overlay colours
Gradient directions use c4-gradient- with top, bottom, left, right or a corner such as top-left. The documentation ties the gradient to the primary and secondary colour properties. Choose the caption position and the actual photograph together: one fixed gradient may work on a dark image and fail on a pale one.
Caption layout
The default caption is centred. The eight named alternatives use c4-layout- with top-left, top-center, top-right, center-left, center-right, bottom-left, bottom-center or bottom-right. Apply the layout to figcaption, not to the animated child text.
Properties recorded by the old reference
--text-color,--primary-colorand--secondary-colorcontrol the documented text and overlay colours.--paddingprovides caption spacing;--border-radiuscontrols the outside corner shape.--border-marginand--border-widthchange the border’s inset and thickness.--transition-durationsets the transition time; it is distinct from an item’s delay.--overlay-opacityis the opacity property named in Turin’s documentation. It should not be replaced automatically by Izmir’s--image-opacity.
The old guide showed both a stylesheet rule after the library and a local inline override. For maintenance, a named component class in your own stylesheet makes it easier to find the adjustment later.
Use the reference to inspect, then test
Keep a copy of the original component before editing it. Confirm its loaded CSS and image paths, change one effect, then inspect keyboard focus, touch behaviour, caption length and reduced-motion preferences. Treat the documented behaviour as a starting point for that inspection, not as a current compatibility or accessibility certification.
The surviving pages preserve the component’s vocabulary. A dependable repair still needs the actual code from the project, a confirmed right to use it and a test in the browsers that matter to that project.