Taggor

All components · Category: Galleries and media

Masonry filter

A masonry grid of pattern tiles with filter chips.

Tiles of different heights packed tight in a grid made only of CSS, with chips that filter them by tag and a count that says how many are showing. The tiles are geometric patterns drawn in code, and they come from props.

01

Try it

<masonry-filter>
View

Props

Accent
Corners
masonry-filter: A masonry grid of pattern tiles with filter chips. 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.

Code for

index.html

<masonry-filter locale="en"></masonry-filter>

<script>
  const element = document.querySelector("masonry-filter");
  element.addEventListener("masonry-filter:filter", (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("masonry-filter");
element.setAttribute("locale", "en");
element.addEventListener("masonry-filter:filter", (event) => {
  console.log(event.detail);
});
document.body.append(element);
  • Add the site's Taggor script once; the component appears when it loads.

MasonryFilter.tsx

import { useEffect, useRef } from "react";

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

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

  return <masonry-filter 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.

MasonryFilter.tsx

import { useEffect, useRef } from "react";

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

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

  return <masonry-filter 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/MasonryFilter.vue

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

<template>
  <masonry-filter locale="en" @masonry-filter:filter="onFilter" />
</template>

vite.config.ts

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

export default defineConfig({
  plugins: [
    vue({
      template: {
        compilerOptions: {
          isCustomElement: (tag) => tag === "masonry-filter",
        },
      },
    }),
  ],
});
  • 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/masonry-filter.component.ts

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

@Component({
  selector: "app-masonry-filter",
  schemas: [CUSTOM_ELEMENTS_SCHEMA],
  template: `
    <masonry-filter locale="en"></masonry-filter>
  `,
})
export class MasonryFilterComponent {
  constructor() {
    const host = inject<ElementRef<HTMLElement>>(ElementRef);
    const element = () => host.nativeElement.querySelector("masonry-filter");
    const onFilter = (event: Event) => {
      console.log((event as CustomEvent).detail);
    };
    afterNextRender(() => element()?.addEventListener("masonry-filter:filter", onFilter));
    inject(DestroyRef).onDestroy(() => element()?.removeEventListener("masonry-filter:filter", onFilter));
  }
}
  • 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 onFilter(event) {
    console.log(event.detail);
  }
</script>

<masonry-filter locale="en" onmasonry-filter:filter={onFilter}></masonry-filter>
  • 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

masonry-filter {
  --mf-radius: 16px;
}

02

Props

Props of the component, read from its manifest
PropTypeDefaultWhat it does
tileslistnoneThe tiles: a title, a pattern (rings, stripes, triangles, dots, waves), a hue, a height of 1 to 3 rows and a filter tag.
hideSamplebooleanfalseHides the Sample content mark (use it with your own tiles).
localept-BR | enen–

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

03

Events

Events of the component, read from its manifest
EventWhen it fires
filterThe visitor chose a filter.

04

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 "Masonry filter" (masonry-filter): A masonry grid of pattern tiles with filter chips. 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.

05

Related components