All components · Category: Heroes and buttons

Magnetic button

A button that leans toward the pointer and bursts when pressed.

It leans toward the pointer when it comes near, then answers a press with a burst of particles and a check that draws itself. Reduced motion keeps only the check. It is a real button for the keyboard.

Try it

<button-magnetic>

ViewPreviewCodeCSS

button-magnetic: A button that leans toward the pointer and bursts when pressed. 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

<button-magnetic locale="en"></button-magnetic>

<script>
  const element = document.querySelector("button-magnetic");
  element.addEventListener("button-magnetic:pressed", (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("button-magnetic");
element.setAttribute("locale", "en");
element.addEventListener("button-magnetic:pressed", (event) => {
  console.log(event.detail);
});
document.body.append(element);

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

ButtonMagnetic.tsx

import { useEffect, useRef } from "react";

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

  useEffect(() => {
    const element = ref.current;
    if (!element) return;
    const onPressed = (event: Event) => {
      console.log((event as CustomEvent).detail);
    };
    element.addEventListener("button-magnetic:pressed", onPressed);
    return () => {
      element.removeEventListener("button-magnetic:pressed", onPressed);
    };
  }, []);

  return <button-magnetic 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.

ButtonMagnetic.tsx

import { useEffect, useRef } from "react";

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

  useEffect(() => {
    const element = ref.current;
    if (!element) return;
    const onPressed = (event: Event) => {
      console.log((event as CustomEvent).detail);
    };
    element.addEventListener("button-magnetic:pressed", onPressed);
    return () => {
      element.removeEventListener("button-magnetic:pressed", onPressed);
    };
  }, []);

  return <button-magnetic 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/ButtonMagnetic.vue

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

<template>
  <button-magnetic locale="en" @button-magnetic:pressed="onPressed" />
</template>

vite.config.ts

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

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

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/button-magnetic.component.ts

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

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

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 onPressed(event) {
    console.log(event.detail);
  }
</script>

<button-magnetic locale="en" onbutton-magnetic:pressed={onPressed}></button-magnetic>

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

button-magnetic {
  --bm-radius: 20px;
}

Props

Props of the component, read from its manifest
Prop	Type	Default	What it does
text	string	none	The button label; the language's own when empty.
doneText	string	none	The label after a press.
strength	number 4 to 40	18	The most the button moves, in px.
holdMs	number 600 to 6000	2600	How long the success look stays, in ms.
particles	number 6 to 24	14	Particles in the burst.
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
pressed	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 "Magnetic button" (button-magnetic): A button that leans toward the pointer and bursts when pressed. 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

Hold to confirm button<button-hold-confirm>
Success check<success-check>
Hero with glow orbs<hero-orbs>