Spec: web UI icon fonts instead of inline SVG (#818)#858
Conversation
Adds headless spec and Q&A for migrating inline SVG chrome icons to a self-hosted icon font, scoped to docs/admin Svelte shells. Refs fullsend-ai#818 Co-authored-by: Cursor <cursoragent@cursor.com>
|
fullsend review is working on this — view logs |
Site previewPreview: https://9839fe8c-site.fullsend-ai.workers.dev Commit: |
Review: #858Head SHA: d7fe0ab SummaryClean spec-start PR that adds two planning documents ( FindingsNo findings. FooterOutcome: approve |
![fullsend-ai-review[bot]](https://avatars.githubusercontent.com/u/271249281?s=60&v=4){kind=small}
|
Closing per maintainer request: cleanup (withdraw draft spec PR). |
1 participant
Summary
Headless spec-start pass for fullsend-ai/fullsend#818: migrate docs/admin UI chrome icons from inline SVG to an icon font for easier styling and better caching on the wire.
Topic directory
docs/plans/2026-05-13-web-icon-fonts/—spec.md,qna.mdRecommended approach (short)
Self-host Material Symbols Outlined (variable font) via the Vite pipeline, shared CSS/conventions across
web/docsandweb/admin, replace inline<svg>in the shell components called out in the issue. Treat Mermaid diagram SVG as out of scope; decide GitHub logo via brand policy (font glyph vs one documented SVG exception).Top open questions
web/sharedCSS vs duplicated per-app imports?What to review
docs/plans/2026-05-13-web-icon-fonts/spec.md— options, recommendation, rollout, testingdocs/plans/2026-05-13-web-icon-fonts/qna.md— assumptions and scope boundary (Mermaid)Refs #818
Made with Cursor