All components · Category: Polls and quizzes

Quick poll

One question, a few options and a vote that is counted.

Native radio buttons and a Vote button. The vote is stored without any personal data, so nothing asks for consent.

Try it

<quick-poll>

ViewPreviewCodeCSS

quick-poll: One question, a few options and a vote that is counted. 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

<quick-poll
  poll-id="landing"
  question="Which feature should we build first?"
  locale="en"
  options="[&quot;Dark mode&quot;,&quot;Mobile app&quot;,&quot;WhatsApp integration&quot;]"
></quick-poll>

<script>
  const element = document.querySelector("quick-poll");
  element.addEventListener("quick-poll:voted", (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("quick-poll");
element.setAttribute("poll-id", "landing");
element.setAttribute("question", "Which feature should we build first?");
element.setAttribute("locale", "en");
element.options = [
  "Dark mode",
  "Mobile app",
  "WhatsApp integration"
];
element.addEventListener("quick-poll:voted", (event) => {
  console.log(event.detail);
});
document.body.append(element);

Add the site's Taggor script once; the component appears when it loads.
Lists and objects go in as a property of the element, not an attribute.

QuickPoll.tsx

import { useEffect, useRef } from "react";

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

  useEffect(() => {
    const element = ref.current;
    if (!element) return;
    Object.assign(element, {
      options: [
        "Dark mode",
        "Mobile app",
        "WhatsApp integration"
      ],
    });
    const onVoted = (event: Event) => {
      console.log((event as CustomEvent).detail);
    };
    element.addEventListener("quick-poll:voted", onVoted);
    return () => {
      element.removeEventListener("quick-poll:voted", onVoted);
    };
  }, []);

  return <quick-poll
      ref={ref}
      poll-id="landing"
      question={"Which feature should we build first?"}
      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.
Lists and objects go in as a property of the element, not an attribute.
The event is heard with addEventListener, inside an effect.

QuickPoll.tsx

import { useEffect, useRef } from "react";

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

  useEffect(() => {
    const element = ref.current;
    if (!element) return;
    Object.assign(element, {
      options: [
        "Dark mode",
        "Mobile app",
        "WhatsApp integration"
      ],
    });
    const onVoted = (event: Event) => {
      console.log((event as CustomEvent).detail);
    };
    element.addEventListener("quick-poll:voted", onVoted);
    return () => {
      element.removeEventListener("quick-poll:voted", onVoted);
    };
  }, []);

  return <quick-poll
      ref={ref}
      poll-id="landing"
      question={"Which feature should we build first?"}
      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.
Lists and objects go in as a property of the element, not an attribute.
The event is heard with addEventListener, inside an effect.

src/QuickPoll.vue

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

<template>
  <quick-poll
    poll-id="landing"
    question="Which feature should we build first?"
    locale="en"
    :options.prop="[&quot;Dark mode&quot;,&quot;Mobile app&quot;,&quot;WhatsApp integration&quot;]"
    @quick-poll:voted="onVoted"
  />
</template>

vite.config.ts

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

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

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.
Lists and objects go in as a property of the element, not an attribute.

src/app/quick-poll.component.ts

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

@Component({
  selector: "app-quick-poll",
  schemas: [CUSTOM_ELEMENTS_SCHEMA],
  template: `
    <quick-poll
      poll-id="landing"
      [question]="&#39;Which feature should we build first?&#39;"
      locale="en"
      [options]="values.options"
    ></quick-poll>
  `,
})
export class QuickPollComponent {
  readonly values = {
    options: [
      "Dark mode",
      "Mobile app",
      "WhatsApp integration"
    ],
  };

  constructor() {
    const host = inject<ElementRef<HTMLElement>>(ElementRef);
    const element = () => host.nativeElement.querySelector("quick-poll");
    const onVoted = (event: Event) => {
      console.log((event as CustomEvent).detail);
    };
    afterNextRender(() => element()?.addEventListener("quick-poll:voted", onVoted));
    inject(DestroyRef).onDestroy(() => element()?.removeEventListener("quick-poll:voted", onVoted));
  }
}

Add the site's Taggor script once; the component appears when it loads.
The component declares CUSTOM_ELEMENTS_SCHEMA.
Lists and objects go in as a property of the element, not an attribute.
The event is heard with addEventListener, inside an effect.

src/TaggorComponent.svelte

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

<quick-poll
  poll-id="landing"
  question={"Which feature should we build first?"}
  locale="en"
  options={[
    "Dark mode",
    "Mobile app",
    "WhatsApp integration"
  ]}
  onquick-poll:voted={onVoted}
></quick-poll>

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

quick-poll {
  --qp-radius: 999px;
}

Props

Props of the component, read from its manifest
Prop	Type	Default	What it does
pollId	string	poll	Tells this poll's votes apart from other polls of the site.
question	string	Qual recurso você quer ver primeiro?	–
options	list	["Modo escuro","Aplicativo para celular","Integ…	The answers, in the site's language.
locale	pt-BR \| en	pt-BR	–

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
voted	The vote was accepted by Taggor.

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 "Quick poll" (quick-poll): One question, a few options and a vote that is counted. 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

Live poll<live-poll>
Quiz<quiz-result>
Feedback collector<feedback-collector>