All components · Category: Maps and places

Route draw

A route that draws itself across a stylized map, stop by stop.

A smooth line draws itself through your stops with a dot appearing at each, and a button draws it again. The stops are also listed as text for screen readers. With reduced motion the finished route is simply there.

Try it

<route-draw>

ViewPreviewCodeCSS

route-draw: A route that draws itself across a stylized map, stop by stop. 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

<route-draw seconds="4" locale="en"></route-draw>

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

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

RouteDraw.tsx

import { useEffect, useRef } from "react";

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

  useEffect(() => {
    const element = ref.current;
    if (!element) return;
    const onReplay = (event: Event) => {
      console.log((event as CustomEvent).detail);
    };
    element.addEventListener("route-draw:replay", onReplay);
    return () => {
      element.removeEventListener("route-draw:replay", onReplay);
    };
  }, []);

  return <route-draw ref={ref} seconds="4" 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.

RouteDraw.tsx

import { useEffect, useRef } from "react";

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

  useEffect(() => {
    const element = ref.current;
    if (!element) return;
    const onReplay = (event: Event) => {
      console.log((event as CustomEvent).detail);
    };
    element.addEventListener("route-draw:replay", onReplay);
    return () => {
      element.removeEventListener("route-draw:replay", onReplay);
    };
  }, []);

  return <route-draw ref={ref} seconds={4} 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/RouteDraw.vue

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

<template>
  <route-draw :seconds.prop="4" locale="en" @route-draw:replay="onReplay" />
</template>

vite.config.ts

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

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

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/route-draw.component.ts

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

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

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

<route-draw seconds={4} locale="en" onroute-draw:replay={onReplay}></route-draw>

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

route-draw {
  --rd-radius: 16px;
}

Props

Props of the component, read from its manifest
Prop	Type	Default	What it does
stops	list	none	The stops in order: a name and x and y as percentages of the map.
seconds	number 1 to 12	4	How long the route takes to draw, in seconds.
hideSample	boolean	false	Hides the Sample content mark (use it with your own stops).
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
replay	The visitor asked to draw the route again.

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 "Route draw" (route-draw): A route that draws itself across a stylized map, stop by stop. 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>
Region picker<region-picker>
Contact hours<contact-hours>