Frequently asked questions
Answers to key questions about content, review process, and site use. Vitra uses single-root localization and static publishing.
What information can I find on the site?
The catalog shows products, evidence materials, methodology, warnings, and technical pages prepared for transparency.
Does the site give medical advice?
No. Materials are informational and do not replace consultation with a qualified professional.
How should I read a product score?
The score is a navigation signal and should be read together with descriptions, limitations, and sources.
When is a product page ready for publication?
When it has a product card, evidence material, visible warnings, and has been checked in preview.
What does an affiliate link mean?
It is a commercial link to an external offer and is separated from editorial evaluation.
Why are some pages short?
A new site starts from a skeleton; detailed content can be added after a separate request and review.
How do I suggest a new product?
Use the suggestion form and describe the product, brand, or source.
How are sources checked?
The editorial workflow keeps structured fields and public links, then checks the preview before publication.
What does preview mean?
Preview is a preliminary Cloudflare Pages version checked before publishing to the domain.
What happens after approval?
Approved content is published as static HTML, CSS, and JavaScript files.
Can content be edited?
Yes. The administrator or AI agent selects the site, page, and fields to edit in the matrix.
How are prices updated?
Price is a separate field and can be changed without replacing the whole layout.
How should images be handled?
An image should have a public path or uploaded file plus a short alt text.
Why are there no language folders?
Each site has one root locale for a specific GEO and publishes content at the domain root.
How is content created?
Content follows the selected page contract and is checked before publication.
Who controls the layout?
The site keeps layout, modules, schema, canonical URLs, preview, and deploy gates.
What happens if generation fails?
The status shows stage, percentage, and error; publication does not happen automatically.
What is a technical page?
Technical pages include contact, policies, methodology, FAQ, and disclaimer pages.
How do I verify that a page is published?
After deploy, the page is checked at its public URL and must be present in the static bundle.
What should I check visually?
Check H1, description, form, buttons, footer, warnings, images, and internal links.