Note from the workbench
How I turned Animals in Black into a digital ecosystem
Animals in Black brings together ten years of photography, 92 recorded species, 125 images and 69 prints available to buy. Rebuilding it was not a matter of redesigning a website or adding a basket. I needed to create a system in which a scientific archive, storytelling, commerce and conservation could use the same data and preserve the same identity in English and Italian.
The point
A digital project becomes robust when its parts are not built as separate rooms. In Animals in Black, every animal can be discovered, understood and purchased through one architecture. Content, catalogue, search, payments and structured data remain consistent without depending on a general-purpose CMS.
Ten years of photographs were not a folder of images
Animals in Black began in 2015. The animals are real, photographed in wildlife parks across northern Italy and then isolated against black through a post-production process I have developed over the years. Part of the value of every print supports the protection of animals and endangered species.
Over time, the photographs had grown alongside species records, common and scientific names, conservation status, copy, print sizes, prices, display options and content about biodiversity loss. Treating them as independent pages would have multiplied duplication and errors. Treating them as a simple catalogue would have removed the reason the project exists.
The 2026 rebuild therefore began before the interface. I identified the real entities in the project — species, photograph, product, variant, collection and IUCN status — and the relationships that needed to keep working as the website grew.
That decision now makes it possible to start with a photograph and reach its species, collection, conservation information and, when available, the print. The same connection works in reverse: someone interested in a species can reach the artwork without turning the information into a commercial pretext.
The decisive work was not putting many pages online. It was making sure that every page knew what it represented and how it connected to the rest of the project.
The catalogue had to begin with data, not pages
Every print has an Italian and English title, species name, scientific name, category, description, main image, room settings, sizes, finishes, prices, product codes and availability. Copying that information into dozens of pages would have turned every update into an endless manual check.
I built a single structured source instead. From that data, the website generates product pages, the shop, filters, internal search, related products, the basket, structured data and the feed supplied to Google Merchant Center.
The same photograph does not have to be rebuilt separately for the browser, Google, Stripe or the catalogue. Each system receives what it needs, while the product retains one identity. If a price or description changes, the update can be controlled at source and propagated without creating competing versions of the truth.
This approach is less conspicuous than a new animation. It is what makes it possible to govern a complex catalogue single-handedly, verify changes and expand the project without relying on memory or a chain of plugins.
Three numbers describe the scale of the project
The visible part of Animals in Black comes from three different sets. Species define its scientific and editorial record. Photographs represent the body of artistic work. Prints turn a selection of those images into products that can be purchased.
From archive to catalogue
Three distinct sets, connected by the same architecture
-
92
Species
Common and scientific names, class, IUCN status and population trend.
-
125
Photographs
The body of visual work created since 2015 and organised into four classes.
-
69
Prints
Works available to buy, each with variants, pricing, images and a product code.
These are not decorative counters. They explain why installing a theme and manually adding one page per photograph would never have been enough. The project needed an architecture able to distinguish each object while allowing them to work together.
Four systems, one identity
Animals in Black must operate as an archive, an editorial project, a shop and a conservation initiative at the same time. None of those parts can be attached to the others as an unrelated module.
Know the animals
Species, scientific names, photographs and conservation status remain organised and connected.
Understand the project
The photographic process, the vision and biodiversity loss have their own space without pretending to be a shop.
Purchase a print
Sizes, basket, payments, orders and shipping form one complete, controlled journey.
Create a real contribution
The share allocated to conservation organisations is tied to the value of the purchased products and recorded by the system.
A species page is not a copy of a shop page. A shop page does not pretend to be a scientific article. They can still share data, links and identity because the system understands the purpose of both.
That distinction also protects the project’s tone. The cause does not become an emotional device forced onto the basket, and the catalogue does not interrupt every piece of content with a purchase request. The commercial path exists, while remaining consistent with the respect owed to the photographed subjects.
Two languages mean two complete journeys
Translating buttons would not have been enough. The animals’ common names change, slugs need to sound natural in both languages and every photograph must retain the correct connection to its species, product and language alternative.
I therefore built genuine bilingual routing. Localised URLs, canonicals, hreflang, breadcrumbs, sitemaps, internal search, metadata and structured data are resolved consistently for English and Italian. An English page should not inherit an Italian slug or point to the wrong photograph merely because two names look similar.
This architecture also works beneath the surface. Search engines and AI systems can recognise the author, project, species, products and relationships without having to infer the language from a hybrid page. The selector remains a simple control for the visitor; behind it, the entire context of the resource changes.
To me, multilingual publishing is not a feature to display in a quotation. It is an integrity constraint: every piece of content must exist in the right place, remain reachable and be updatable without producing hybrid URLs or orphaned versions.
Selling without turning the website into a fragile platform
E-commerce adds responsibilities that a gallery does not have. It must preserve the basket, verify products and prices on the server, calculate shipping, entrust payment to the right provider, record an order once and produce the necessary documents. It must do so even when a page reloads, a request arrives twice or someone tries to alter data in the browser.
I chose guest checkout. A customer does not need to create a profile to buy a print, and Animals in Black stores neither passwords nor payment details. Stripe handles payment; the website controls the catalogue and order; the specialist laboratory handles production. Each part performs its own task without duplicating data or capabilities that belong to another infrastructure.
- catalogue data and prices are verified on the server;
- payment remains within Stripe’s infrastructure;
- orders and notifications withstand duplicate requests;
- privacy, terms of sale and documents are part of the flow;
- no customer accounts means less personal data and a smaller exposed surface.
The most important decision, once again, is not a visual effect. It is building the shop without surrendering it to a chain of themes, plugins and user accounts that would have increased dependencies, maintenance and points of attack.
When architecture produces observable results
A well-designed structure does not remain an invisible quality. External systems need to read the catalogue, distinguish variants, associate a product with its image and recognise the relationships between the project, author, species and content.
Google Merchant Center approved 345 catalogue entries and variants with no rejected products. That means the feed, codes, prices, availability, landing pages and shop data are consistent enough to pass the platform’s checks.
The editorial part is also becoming readable beyond the website. In the Bing review on 24 August 2026, Animals in Black reached 847 impressions and 31 citations across Microsoft’s AI systems, distributed over 13 pages. These figures are not used as a commercial promise. They show that different pages are understood as parts of the same body of information.
Browsers, search engines, AI systems, Merchant Center and Stripe recognise the same project, not five incompatible versions of its data.
These signals can be checked because the website was designed to produce evidence: sitemaps, feeds, structured data, events, application logs and testing procedures. Quality does not depend on a feeling or a successful-looking screen. It leaves a verifiable trail.
The system remained recognisable
The technical complexity could have turned Animals in Black into a shop like any other. It did not. Black remains a narrative space, the animals remain at the centre of the experience and selling does not replace the photographic project.
Editorial pages keep their own rhythm. Product pages add materials, sizes, finishes, pricing and room settings when they are relevant. The conservation contribution is connected to the actual value of the print, rather than entrusted to a generic sentence in the footer.
Building many features is possible. Building them without losing identity, clarity and control is the real work.
What this work demonstrates
Animals in Black is not an exercise, a customised theme or a collection of successful pages. It is a real system, developed and governed directly: archive, bilingual publishing, search, e-commerce, payments, compliance, security, SEO, GEO and AEO all share a deliberate architecture.
For a client, this method means beginning with the content and responsibilities of the project, not with a platform’s feature list. It means having a controlled source for data, consistent journeys, limited dependencies, repeatable checks and a structure that can evolve without being rebuilt for every new requirement.
Not every website needs to manage 92 species, 125 photographs and hundreds of commercial variants. Every website should still know what it represents, which data it governs, which risks it must avoid and how each part contributes to the final objective.
That is the difference between assembling pages and designing a digital ecosystem.