Skip to content

docs(apps): add custom portal blocks component page - #192

Open
flixlix wants to merge 2 commits into
mainfrom
docs/custom-portal-blocks
Open

flixlix wants to merge 2 commits into
mainfrom
docs/custom-portal-blocks

Conversation

@flixlix

@flixlix flixlix commented Nov 16, 2026

Copy link
Copy Markdown

Summary

The app components docs cover journey blocks, custom pages and portal extensions, but nothing on custom portal blocks: the blocks other teams can now build for customer portals and configure per placed block in the Portal Builder.

  • New page docs/apps/components/custom-portal-block.md: what a custom portal block is and when to use a Portal Extension instead, a quick start (npm create @epilot/spark-block, playground, deploy), per-block settings and their field types, and what an update does to blocks already placed in a portal.
  • Entry in the components overview.
  • The full step-by-step guide stays in the Spark docs (https://spark-ui.epilot.io/docs/sdk/create-a-block); this page links to it instead of repeating it.

Testing

  • npm run build succeeds; no broken links reported. The only errors are existing SVGs under static/img/integrations/, unrelated to this change.
  • The Spark links return 200.
  • The quick start and update behavior were walked end to end on dev: a block created with the published @epilot/create-spark-block, deployed, placed and configured in the Portal Builder, checked as a logged-in customer, then updated to a new version that reached the placed block without re-adding it.

Generated by Claude Code

This branch has not been deployed

No deployments
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.

1 participant