Web · content systems · operations
BioPly.
A connected digital presence.
A materials brand needs more than a good-looking website. Its product pages, documents and everyday communication need to speak the same language.
My contributionDigital direction and delivery across web, content and operational tooling, using AI-assisted workflows. Material development, manufacturing and product declarations remain the BioPly team’s work.
Make the material easier to understand.
The problem: different product families, languages and kinds of evidence can turn a website into a collection of disconnected pages.
The work: shape and implement the digital presentation: product layouts, navigation, localized content and clear routes to an enquiry or supporting material.
- Keep a shared visual language while allowing product-specific layouts.
- Make mobile browsing a first-class route, not a scaled-down desktop screenshot.
- Keep actual material photographs distinct from conceptual application visuals.
The public capture and local implementation are separate evidence: a website screenshot does not establish authorship of every image, sentence or historic release.
One information hierarchy. More than one language.
The problem: translated documents can drift apart: different layouts, stale values, inconsistent terminology or an attractive illustration mistaken for a real installation.
The work: adapt product and commercial information into consistent localized documents, keeping owner-approved source data and the difference between real photography and concepts visible.
- Reuse the brand’s visual vocabulary across the website and documents.
- Preserve approved specifications rather than “improving” their numbers.
- Inspect the rendered document, not just its editable source.
This cover is rendered from the project’s approved Italian catalogue. Only a document-cover excerpt is shown; the full commercial dossier is not distributed here.
Measure useful actions, not everything.
The problem: a useful measurement layer should explain interest in products and enquiries without forwarding arbitrary page text, form contents or campaign details.
The work: an explicit event allowlist, payload sanitization and tracking gates for eligible hosts, opt-out and browser privacy signals.
The local implementation separates what may be collected from whether collection is allowed. That boundary is more useful to show here than a private dashboard.
sanitizeEvent → explicit event + property allowlist canTrack → eligible host + privacy signals URL → origin + pathname, not query contents
A simplified diagram based on the inspected implementation in src/lib/analytics.ts. It is not a screenshot of an analytics product.
Prepare the work. Keep approval explicit.
The problem: commercial communication is not finished when a draft exists. It still needs accurate content, consistent visuals, language adaptation and a clear publication decision.
The work: prepare reusable outreach material and reviewable assets, while keeping external actions behind human approval.
- Pair genuine material photography with clearly labeled application concepts.
- Keep product-specific qualifications attached to the relevant claims.
- Separate prepared collateral from a message actually sent or a campaign result.
The connected work