Link directory
About studio-pietra.example
studio-pietra.example is the shared link directory for Studio Pietra. 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 6 profile pages (6 people, 0 organizations). Across those records there are 6 published social-profile destinations, 12 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 studio-pietra.example. 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
| Public record type | Count |
|---|---|
| Profile pages | 6 |
| Individual people | 6 |
| Organizations | 0 |
| Social-profile destinations | 6 |
| Direct contact or resource links | 12 |
| Profiles with website destinations | 6 |
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.
Anja Novak
Anja Novak's directory page brings together Email, Projects and LinkedIn. The profile identifies Anja Novak as Senior architect. It also points to studio-pietra.example as a website destination. The entry is generated from the same repository data used by the visible cards, metadata and machine-readable profile information.
Hugo Alves
Hugo Alves's directory page brings together Email, Projects and LinkedIn. The profile identifies Hugo Alves as Studio manager. It also points to studio-pietra.example as a website destination. The entry is generated from the same repository data used by the visible cards, metadata and machine-readable profile information.
Inês Carvalho
Inês Carvalho's directory page brings together Email, Projects and LinkedIn. The profile identifies Inês Carvalho as Founding partner. It also points to studio-pietra.example as a website destination. The entry is generated from the same repository data used by the visible cards, metadata and machine-readable profile information.
Léa Moreau
Léa Moreau's directory page brings together Email, Projects and LinkedIn. The profile identifies Léa Moreau as Interior designer. It also points to studio-pietra.example as a website destination. The entry is generated from the same repository data used by the visible cards, metadata and machine-readable profile information.
Rui Tavares
Rui Tavares's directory page brings together Email, Projects and LinkedIn. The profile identifies Rui Tavares as Partner. It also points to studio-pietra.example as a website destination. The entry is generated from the same repository data used by the visible cards, metadata and machine-readable profile information.
Tiago Santos
Tiago Santos's directory page brings together Email, Projects and LinkedIn. The profile identifies Tiago Santos as Architect. It also points to studio-pietra.example 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 studio-pietra.example address rather than a temporary browser state, making the profile suitable for messages, contact cards and printed material.
Open Bio Page ships a single demo profile so you can see the layout before replacing `content/bios/` with your own people. Each entry is generated from repository JSON; empty fields stay empty instead of being filled with assumptions. After a GitHub Fork, swap the demo for your brand and republish.
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.
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 studio-pietra.example 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 studio-pietra.example/massimo. Canonical metadata and the sitemap use the same path-based addresses for consistent discovery.