All components · Category: Heroes and buttons

Hero with glow orbs

A hero over soft orbs that lean toward the pointer.

Three glowing orbs drift on their own and lean toward the pointer at different depths. The pointer is read only inside the component, only for a mouse or a pen, and only when the visitor allows motion.

Try it

<hero-orbs>

ViewPreviewCodeCSS

hero-orbs: A hero over soft orbs that lean toward the pointer. 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

<hero-orbs locale="en"></hero-orbs>

<script>
  const element = document.querySelector("hero-orbs");
  element.addEventListener("hero-orbs:clicked", (event) => {
    console.log(event.detail);
  });
</script>

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

taggor-component.js

const element = document.createElement("hero-orbs");
element.setAttribute("locale", "en");
element.addEventListener("hero-orbs:clicked", (event) => {
  console.log(event.detail);
});
document.body.append(element);

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

HeroOrbs.tsx

import { useEffect, useRef } from "react";

export function HeroOrbs() {
  const ref = useRef<HTMLElement>(null);

  useEffect(() => {
    const element = ref.current;
    if (!element) return;
    const onClicked = (event: Event) => {
      console.log((event as CustomEvent).detail);
    };
    element.addEventListener("hero-orbs:clicked", onClicked);
    return () => {
      element.removeEventListener("hero-orbs:clicked", onClicked);
    };
  }, []);

  return <hero-orbs ref={ref} 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.
The event is heard with addEventListener, inside an effect.

HeroOrbs.tsx

import { useEffect, useRef } from "react";

export function HeroOrbs() {
  const ref = useRef<HTMLElement>(null);

  useEffect(() => {
    const element = ref.current;
    if (!element) return;
    const onClicked = (event: Event) => {
      console.log((event as CustomEvent).detail);
    };
    element.addEventListener("hero-orbs:clicked", onClicked);
    return () => {
      element.removeEventListener("hero-orbs:clicked", onClicked);
    };
  }, []);

  return <hero-orbs ref={ref} 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.
The event is heard with addEventListener, inside an effect.

src/HeroOrbs.vue

<script setup lang="ts">
function onClicked(event: Event) {
  console.log((event as CustomEvent).detail);
}
</script>

<template>
  <hero-orbs locale="en" @hero-orbs:clicked="onClicked" />
</template>

vite.config.ts

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

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

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/hero-orbs.component.ts

import { afterNextRender, Component, CUSTOM_ELEMENTS_SCHEMA, DestroyRef, ElementRef, inject } from "@angular/core";

@Component({
  selector: "app-hero-orbs",
  schemas: [CUSTOM_ELEMENTS_SCHEMA],
  template: `
    <hero-orbs locale="en"></hero-orbs>
  `,
})
export class HeroOrbsComponent {
  constructor() {
    const host = inject<ElementRef<HTMLElement>>(ElementRef);
    const element = () => host.nativeElement.querySelector("hero-orbs");
    const onClicked = (event: Event) => {
      console.log((event as CustomEvent).detail);
    };
    afterNextRender(() => element()?.addEventListener("hero-orbs:clicked", onClicked));
    inject(DestroyRef).onDestroy(() => element()?.removeEventListener("hero-orbs:clicked", onClicked));
  }
}

Add the site's Taggor script once; the component appears when it loads.
The component declares CUSTOM_ELEMENTS_SCHEMA.
The event is heard with addEventListener, inside an effect.

src/TaggorComponent.svelte

<script>
  function onClicked(event) {
    console.log(event.detail);
  }
</script>

<hero-orbs locale="en" onhero-orbs:clicked={onClicked}></hero-orbs>

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

hero-orbs {
  --ho-radius: 20px;
}

Props

Props of the component, read from its manifest
Prop	Type	Default	What it does
eyebrow	string	none	The small line above the headline.
headline	string	none	The headline.
sub	string	none	The line under the headline.
cta	string	none	The button label.
href	url	none	Where the button goes.
locale	pt-BR \| en	en	–

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

Events

Events of the component, read from its manifest
Event	When it fires
clicked	The button was pressed.

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 "Hero with glow orbs" (hero-orbs): A hero over soft orbs that lean toward the pointer. 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

Word-rotating hero<hero-word-rotator>
Split hero with a form<hero-split-form>
Magnetic button<button-magnetic>