Skip to content

docs(signage): making artwork with AI, and configuring a provider (PPT-2741) - #32

Open
camreeves wants to merge 3 commits into
mainfrom
feat/signage-ai
Open

docs(signage): making artwork with AI, and configuring a provider (PPT-2741)#32
camreeves wants to merge 3 commits into
mainfrom
feat/signage-ai

Conversation

@camreeves

Copy link
Copy Markdown
Contributor

Part of the AI signage feature (PPT-2741). No ordering constraint, though it describes behaviour that is not live until PlaceOS/rest-api#447 ships.

What this adds

Two pages.

A user-facing one on making signage artwork with AI: writing a brief, using reference images, editing an existing image, and how the branding and text blocks work.

An admin one on configuring a provider in backoffice, including what each vendor needs for credentials and how per-domain scoping works.

Testing

Builds clean.

Creeves and others added 2 commits August 28, 2026 00:36
A user page in the signage guide covering the brief, refining, the text and
logo layer and the limits, plus a Backoffice how-to for connecting a vendor,
the brand kit metadata and the rate tier to move to before enabling it for
a second customer.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The domain selector is gone: the page manages the domain it is served from, and
another customer's providers are not reachable. Adds the Region field, which
Vertex needs and which had no entry, says the credentials test is billed, and
explains where the shared fallback row actually comes from.
@netlify

netlify Bot commented Aug 31, 2026

Copy link
Copy Markdown

Deploy Preview for placeosdocs ready!

Name Link
🔨 Latest commit dff2800
🔍 Latest deploy log https://app.netlify.com/projects/placeosdocs/deploys/6a9664d298cabc0008a73bbc
😎 Deploy Preview https://deploy-preview-32--placeosdocs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Lighter touch than the code repos, since this is prose for admins and users
rather than JSDoc: the operational "why" stays, including why an AI Studio key
will not work for Google Vertex. What goes is the phrasing that defends a
design decision rather than telling the reader anything they can act on.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants