All components · Category: Maps and places

Region picker

A stylized map of regions to choose on the map or in a list.

Click a region of a made-up map, or use the list beside it: the keyboard has real buttons, the mouse has the drawing, and both stay in sync. The chosen region lifts and its note appears below. Names and notes come from props.

Try it

<region-picker>

ViewPreviewCodeCSS

region-picker: A stylized map of regions to choose on the map or in a list. 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

<region-picker selected="Middle Bay" locale="en"></region-picker>

<script>
  const element = document.querySelector("region-picker");
  element.addEventListener("region-picker:pick", (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("region-picker");
element.setAttribute("selected", "Middle Bay");
element.setAttribute("locale", "en");
element.addEventListener("region-picker:pick", (event) => {
  console.log(event.detail);
});
document.body.append(element);

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

RegionPicker.tsx

import { useEffect, useRef } from "react";

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

  useEffect(() => {
    const element = ref.current;
    if (!element) return;
    const onPick = (event: Event) => {
      console.log((event as CustomEvent).detail);
    };
    element.addEventListener("region-picker:pick", onPick);
    return () => {
      element.removeEventListener("region-picker:pick", onPick);
    };
  }, []);

  return <region-picker ref={ref} selected="Middle Bay" 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.

RegionPicker.tsx

import { useEffect, useRef } from "react";

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

  useEffect(() => {
    const element = ref.current;
    if (!element) return;
    const onPick = (event: Event) => {
      console.log((event as CustomEvent).detail);
    };
    element.addEventListener("region-picker:pick", onPick);
    return () => {
      element.removeEventListener("region-picker:pick", onPick);
    };
  }, []);

  return <region-picker ref={ref} selected="Middle Bay" 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/RegionPicker.vue

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

<template>
  <region-picker
    selected="Middle Bay"
    locale="en"
    @region-picker:pick="onPick"
  />
</template>

vite.config.ts

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

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

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/region-picker.component.ts

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

@Component({
  selector: "app-region-picker",
  schemas: [CUSTOM_ELEMENTS_SCHEMA],
  template: `
    <region-picker selected="Middle Bay" locale="en"></region-picker>
  `,
})
export class RegionPickerComponent {
  constructor() {
    const host = inject<ElementRef<HTMLElement>>(ElementRef);
    const element = () => host.nativeElement.querySelector("region-picker");
    const onPick = (event: Event) => {
      console.log((event as CustomEvent).detail);
    };
    afterNextRender(() => element()?.addEventListener("region-picker:pick", onPick));
    inject(DestroyRef).onDestroy(() => element()?.removeEventListener("region-picker:pick", onPick));
  }
}

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

<region-picker selected="Middle Bay" locale="en" onregion-picker:pick={onPick}></region-picker>

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

region-picker {
  --rp-radius: 16px;
}

Props

Props of the component, read from its manifest
Prop	Type	Default	What it does
regions	list	none	The regions, up to six, in the order of the map's slots: a name and a note.
selected	string	none	The region chosen at the start, by name.
hideSample	boolean	false	Hides the Sample content mark (use it with your own regions).
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
pick	The visitor chose a region.

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 "Region picker" (region-picker): A stylized map of regions to choose on the map or in a list. 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

Store locator<store-locator>
Route draw<route-draw>
Open now sign<open-now>