All components · Category: Loading and feedback
Not found page
A playful not-found scene with a ghost whose eyes follow the pointer.
Two big digits and a friendly ghost between them, all in SVG. The ghost floats and its eyes follow the pointer inside the component's box. A headline, a sentence and a link home sit below.
01
Try it
Props
Generated from the component's manifest and the values above.
index.html
<page-404 href="https://example.com/" locale="en"></page-404>
- Add the site's Taggor script once; the component appears when it loads.
taggor-component.js
const element = document.createElement("page-404");
element.setAttribute("href", "https://example.com/");
element.setAttribute("locale", "en");
document.body.append(element);
- Add the site's Taggor script once; the component appears when it loads.
Page404.tsx
export function Page404() {
return <page-404 href="https://example.com/" 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.
Page404.tsx
export function Page404() {
return <page-404 href="https://example.com/" 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.
src/Page404.vue
<template>
<page-404 href="https://example.com/" locale="en" />
</template>
vite.config.ts
import vue from "@vitejs/plugin-vue";
import { defineConfig } from "vite";
export default defineConfig({
plugins: [
vue({
template: {
compilerOptions: {
isCustomElement: (tag) => tag === "page-404",
},
},
}),
],
});
- 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/page-404.component.ts
import { Component, CUSTOM_ELEMENTS_SCHEMA } from "@angular/core";
@Component({
selector: "app-page-404",
schemas: [CUSTOM_ELEMENTS_SCHEMA],
template: `
<page-404 href="https://example.com/" locale="en"></page-404>
`,
})
export class Page404Component {}
- Add the site's Taggor script once; the component appears when it loads.
- The component declares CUSTOM_ELEMENTS_SCHEMA.
src/TaggorComponent.svelte
<page-404 href="https://example.com/" locale="en"></page-404>
- 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 publishThe CSS variables the component exposes, set the way a customer's page would.
styles.css
page-404 {
--p4-radius: 20px;
}02
Props
| Prop | Type | Default | What it does |
|---|---|---|---|
| heading | string | none | Replaces the headline. |
| message | string | none | Replaces the sentence. |
| cta | string | none | Replaces the link text. |
| href | url | none | Where the link goes; without it the link goes to / on your site. |
| locale | pt-BR | en | en | – |
Prop names and descriptions are the component's own, in English, as its author wrote them.
03
Events
This component fires no event.
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 "Not found page" (page-404): A playful not-found scene with a ghost whose eyes follow the pointer.
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
- Empty state<empty-state>
- Orbit loader<loader-orbit>
- Announcement bar<announcement-bar>