> ## Documentation Index
> Fetch the complete documentation index at: https://docs.photon.codes/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Content
> Build every outbound message shape with Spectrum content builders.
export const TypeTooltip = ({name, type, children}) => {
const [visible, setVisible] = React.useState(false);
const [pos, setPos] = React.useState({
top: 0,
left: 0
});
const triggerRef = React.useRef(null);
const show = () => {
if (triggerRef.current) {
const rect = triggerRef.current.getBoundingClientRect();
setPos({
top: rect.bottom + 6,
left: rect.left
});
}
setVisible(true);
};
const hide = () => setVisible(false);
return <>
{children || {name}}
{visible &&
{type}
}
;
};
Spectrum exposes a family of content builders for text, markdown, attachments, rich previews, replies, edits, typing indicators, chat metadata, and provider-specific payloads. Any API that takes a accepts a plain string or a ;
}`} />.
Use this section when you need to choose the right outbound content shape or understand how a builder degrades across providers.
Send plain text and stream generated text into supported providers.
Send styled text that renders through each provider's native formatting model.
Send files from paths or buffers with stable attachment IDs.
Send voice notes with audio metadata and provider fallbacks.
Share contact cards from structured data, users, or vCards.
Render URLs as rich previews with lazy Open Graph metadata.
Present URLs as tappable app-style cards where providers support them.
Send poll prompts and receive selected options as content.
Bundle multiple messages into one logical visual group.
Send provider-specific structured payloads.
Thread content under an existing message.
Rewrite previously sent outbound messages.
Retract a previously sent outbound message.
Send start and stop typing signals.
Rename chats through the content pipeline.
Set or clear group chat avatars.
Send multiple content items or reply with multiple parts.
## Builder shortcut
Plain strings are equivalent to `text()`:
```ts theme={null}
await space.send("Hello, world.");
await space.send(text("Hello, world."));
```
Reach for an explicit builder when you need provider-aware behavior, structured metadata, or a content type that is not plain text.