All components · Category: Depth and layers

Device mockup

A phone and a laptop in depth, with screens made from your text.

A laptop and a phone built from boxes in CSS depth, whose screens show a small page made from your headline, lines and button. The rig sways slowly, and reduced motion holds it still.

Try it

<device-mockup>

ViewPreviewCodeCSS

device-mockup: A phone and a laptop in depth, with screens made from your text. A picture of the real component, drawn from its own code. The controls change the picture and the code beside it; nothing here is sent or stored.

Generated from the component's manifest and the values above.

index.html

<device-mockup locale="en"></device-mockup>

Add the site's Taggor script once; the component appears when it loads.

taggor-component.js

const element = document.createElement("device-mockup");
element.setAttribute("locale", "en");
document.body.append(element);

Add the site's Taggor script once; the component appears when it loads.

DeviceMockup.tsx

export function DeviceMockup() {
  return <device-mockup locale="en" />;
}

Add the site's Taggor script once; the component appears when it loads.
React 18 sends every prop of a custom element as a text attribute.

DeviceMockup.tsx

export function DeviceMockup() {
  return <device-mockup locale="en" />;
}

Add the site's Taggor script once; the component appears when it loads.
React 19 sets a property when the element already has it, an attribute otherwise.

src/DeviceMockup.vue

<template>
  <device-mockup locale="en" />
</template>

vite.config.ts

import vue from "@vitejs/plugin-vue";
import { defineConfig } from "vite";

export default defineConfig({
  plugins: [
    vue({
      template: {
        compilerOptions: {
          isCustomElement: (tag) => tag === "device-mockup",
        },
      },
    }),
  ],
});

Add the site's Taggor script once; the component appears when it loads.
vite.config.ts tells Vue that this tag is not a Vue component.

src/app/device-mockup.component.ts

import { Component, CUSTOM_ELEMENTS_SCHEMA } from "@angular/core";

@Component({
  selector: "app-device-mockup",
  schemas: [CUSTOM_ELEMENTS_SCHEMA],
  template: `
    <device-mockup locale="en"></device-mockup>
  `,
})
export class DeviceMockupComponent {}

Add the site's Taggor script once; the component appears when it loads.
The component declares CUSTOM_ELEMENTS_SCHEMA.

src/TaggorComponent.svelte

<device-mockup locale="en"></device-mockup>

Add the site's Taggor script once; the component appears when it loads.

How an agent gets a component like this onto a site:

taggor checktaggor publish

The CSS variables the component exposes, set the way a customer's page would.

styles.css

/* device-mockup: no CSS variable set */

Props

Props of the component, read from its manifest
Prop	Type	Default	What it does
device	both \| phone \| laptop	both	Which devices to draw.
headline	string	none	Replaces the screen headline.
lines	list	none	The lines under the headline (up to four).
cta	string	none	Replaces the button on the screen.
locale	pt-BR \| en	en	–

Prop names and descriptions are the component's own, in English, as its author wrote them.

Events

This component fires no event.

Build one with your agent

Paste this into your agent. It asks you before it signs in, pays or goes further than checking and publishing.

Build me a Taggor component like "Device mockup" (device-mockup): A phone and a laptop in depth, with screens made from your text. Fetch https://taggor.dev/agent-setup/prompt.md and follow its instructions to set me up for Taggor. Ask me before you sign in, create an account, accept terms, pay for anything or type a secret. Check it with `taggor check` and publish it with `taggor publish`, and stop there. Do not promote it to production, attach it to a site, roll back anything or use --yes, --force or --force-drop-invalid unless I ask for exactly that in this conversation.

Related components

Layers in depth<layers-depth>
Tilting card<card-tilt>