De Luisa family

De Luisa family profiles

Andrea De Luisa
Andrea
Arianna De Luisa
Arianna
Camilla De Luisa
Camilla
Giovanni De Luisa
Giovanni
Laura De Luisa
Laura
Massimo De Luisa
Massimo
Nicole De Luisa
Nicole
Pasticceria De Luisa
Pasticceria

Family directory

About deluisa.bio

deluisa.bio is the shared link directory for the De Luisa family. It gives each listed person a stable page for the public websites, contact methods and social profiles they have chosen to publish. The home page is an index: select a portrait to open that profile, or continue through this guide for a text description of the directory. The visual cards and the text below are built from the same source records, so visitors, search engines and non-JavaScript clients receive the same names and destinations.

The directory currently contains 8 profile pages: 7 for individual family members and 1 for Pasticceria De Luisa. Across those records there are 18 published social-profile destinations, 7 direct contact or resource links and 6 website destinations. These figures are calculated from the public profile data during the site build; they are inventory counts, not audience or performance claims.

Every portrait links to a canonical address under deluisa.bio. A profile may include a personal or business website, email or telephone details, a downloadable resource, a booking link, and public accounts on services such as Instagram, Facebook, LinkedIn, GitHub, X, Telegram or LINE. Not every person uses every service. An omitted field means that the corresponding profile record does not currently publish that destination.

Directory at a glance

Counts calculated from the public De Luisa profile records
Public record typeCount
Profile pages8
Individual people7
Organizations1
Social-profile destinations18
Direct contact or resource links7
Profiles with website destinations6

Directory entries

The summaries in this section are deliberately limited to information already shown on each page. They do not infer occupations, relationships, locations or private details. Follow a name to see the current set of links for that entry.

Andrea De Luisa

Andrea De Luisa's directory page brings together Email me, Instagram and Facebook. It also points to deluisaandrea.it as a website destination. The entry is generated from the same repository data used by the visible cards, metadata and machine-readable profile information.

Arianna De Luisa

Arianna De Luisa's directory page brings together Instagram and Facebook. It also points to pasticceriadeluisa.it as a website destination. The entry is generated from the same repository data used by the visible cards, metadata and machine-readable profile information.

Camilla De Luisa

Camilla De Luisa's directory page brings together Instagram. It also points to pasticceriadeluisa.it as a website destination. The entry is generated from the same repository data used by the visible cards, metadata and machine-readable profile information.

Giovanni De Luisa

Giovanni De Luisa's directory page brings together Instagram. The entry is generated from the same repository data used by the visible cards, metadata and machine-readable profile information.

Laura De Luisa

Laura De Luisa's directory page brings together Facebook. It also points to pasticceriadeluisa.it as a website destination. The entry is generated from the same repository data used by the visible cards, metadata and machine-readable profile information.

Massimo De Luisa

Massimo De Luisa's directory page brings together Book a 30-min call, Email me, Download CV, GitHub, LinkedIn, X, Telegram, Line, Instagram and Facebook. The profile identifies Massimo De Luisa as CTO & Product Engineer. It also points to deluisa.me as a website destination. The entry is generated from the same repository data used by the visible cards, metadata and machine-readable profile information.

Nicole De Luisa

Nicole De Luisa's directory page brings together Email me, Instagram and Facebook. The entry is generated from the same repository data used by the visible cards, metadata and machine-readable profile information.

Pasticceria De Luisa

Pasticceria De Luisa's directory page brings together Email us, Call us, Instagram and Facebook. The profile identifies Pasticceria De Luisa as Artisan Bakery & Pastry Shop. It also points to pasticceriadeluisa.it as a website destination. The entry is generated from the same repository data used by the visible cards, metadata and machine-readable profile information.

How to use the directory

Start with the profile whose name or portrait you recognize. Each profile page places the person's or business's chosen identity at the top, followed by the destinations available for that record. Buttons use descriptive labels, and external destinations open at their published URLs. The share control copies the canonical deluisa.bio address rather than a temporary browser state, making the profile suitable for messages, contact cards and printed material.

Massimo De Luisa's entry is the most detailed current example. It identifies him as “CTO & Product Engineer” and describes his work as “Platforms, mobile apps and AI-assisted workflows that stay simple under pressure.” His profile publishes a website, a booking destination, email, a curriculum-vitae download and seven social accounts. That quotation comes directly from his English profile text; it is not an editorial endorsement or a rewritten biography.

Pasticceria De Luisa has a business entry rather than a personal one. Its profile identifies the activity as an artisan bakery and pastry shop and publishes its official website, email, telephone number, Instagram and Facebook destinations. Arianna, Camilla and Laura also link to the Pasticceria website from their own directory pages. Andrea's entry links to deluisaandrea.it and public contact destinations, while Giovanni and Nicole currently use smaller sets of published links. The directory preserves those differences instead of filling empty fields with assumptions.

Sources, structure and accuracy

Profile data is maintained in one record per entry and converted into static HTML when the site is built. That means names, headings, descriptions and links are present in the initial document response; a crawler or text browser does not need to execute JavaScript to discover them. JavaScript adds optional interaction, including client-side navigation, analytics subject to consent, link sharing and the portrait shuffle on the home page. The underlying directory remains readable when those enhancements are unavailable.

Machine-readable metadata follows the public vocabulary documented by Schema.org for collection pages. The home document identifies the website, the collection, its ordered list and the people or organization represented by the entries. Individual profiles identify their main person or organization and use canonical URLs so multiple discovery paths resolve to one preferred address.

Automated crawlers can also consult the site's robots.txt, XML sitemap, LLM index and full text export. The robots file follows the standard described in RFC 9309 and explicitly allows the public directory while excluding the private administration route. These discovery files supplement the HTML; they do not replace it.

The public profile owner is the source of each editable record. Because destinations can change, the canonical profile page should be treated as the current directory entry. External services control their own pages, availability and privacy practices. A link from deluisa.bio indicates that the destination is published in the relevant profile record; it does not imply ownership of the external platform or verification by that platform.

Frequently asked questions

Does the directory work without JavaScript?

Yes. The home guide, profile names, links, headings and structured metadata are pre-rendered as static HTML. JavaScript adds optional interaction but is not required to read or follow the public directory.

Where does the profile information come from?

Each entry comes from its public profile record in the site repository. The page does not add inferred jobs, locations, family relationships or private information when a record leaves those fields empty.

Which URL should be shared?

Share the canonical path shown on the profile, such as deluisa.bio/massimo. Canonical metadata and the sitemap use the same path-based addresses for consistent discovery.