Products, evidence, regulatory content, and resources

Documentation home

Product collection and detail pages

Use Product Listing to help buyers choose what to explore, and Product Detail for one product's technical and supporting information. Product Directory provides collection cards; Product Portfolio supports a smaller related-product presentation. Product 01/02/03 are neutral starter records to rename with your approved product identifiers.

The Product Hero provides introductory copy, optional media, and actions. Product Detail Hero adds product category, model name, and optional quick facts. Empty images do not create image frames. Quick facts require both a value and label. Blank destinations suppress actions; supply actual product pages when ready.

Technical specifications

1. Open the Specification List module on a Product Detail page.
2. Name a group if useful.
3. Enter a Specification term and Specification value together. Add a note where context or limitations are needed.
4. Preview, save, and review the result.

The editor allows 1–8 groups, each with 1–20 structural specification records. Rows without a term or value do not render. A group without any complete rows does not render. To return to an empty state when the last record cannot be deleted, clear its fields. The section introduction can remain visible.

The theme does not validate specifications. Verify units, product variants, document versions, and every value against your approved product documentation.

Presentation structure, not medical or regulatory verification

MedTech Structure provides presentation structure only. It does not validate clinical evidence, verify claims, provide legal advice, determine regulatory status, certify compliance, or create approved medical claims.

Your organization is responsible for supplying and reviewing evidence sources, populations and context, methods, outcomes and metrics, product claims, regulatory status, standards, certifications, and quality information. Obtain the appropriate internal review before publication and update content when its supporting information changes.

Evidence and quality information

Evidence Highlight organizes a title, summary, study context, population/sample, source/publication, reference link, optional metric, and footnote. An evidence title is needed for an item to appear. A metric needs its label and at least one supporting summary/context/population field to display. These display conditions do not establish that a metric or claim is valid.

Use Proof Strip and editorial facts only for statements you can substantiate. Do not turn neutral starter entries into implied clinical proof.

Standards Register groups buyer-supplied information. An entry needs both a title and information value; notes and document links are optional. Use precise scope and applicable context. A visible entry is not a theme-issued certification or approval.

Resources and document links

Resource Directory organizes resources with type, title, metadata, summary, optional image, and action. It supports 0–12 records; a standalone module initializes three structural records, while a page such as News can start with none. Only titled resources appear.

Resource Highlight emphasizes one resource with optional secondary resources. Document Links presents titled documents with optional type and metadata. Document Links retains at least one structural record; a completely blank record does not become a public row.

Add action text and a usable destination to show a resource/document action. Link only to approved resources you have permission to share, and check access permissions as a visitor. Starter titles do not supply files.

Resource Landing combines explanation, access guidance, and an optional native form. Configure resource delivery separately; a form on the page alone does not protect a file or create a gated-download process. See forms and conversion.