Purpose
Support embeds Firestruct help and Chatwoot support access inside the app so users can ask for help without leaving their workspace context.
Behavior
- Support is a visible workspace module.
- It does not support output modes or workspace tabs in the same way data modules do.
- The support panel uses Chatwoot configuration and web view/controller components.
The support surface is meant for product help, setup questions, and issue handoff when a Firestruct workflow needs human review. It should keep users in context: the selected module, project type, environment, and recent logs are the details most likely to make a support request actionable.
Users should still avoid pasting secrets into support conversations. Service account JSON, OAuth tokens, Firebase access tokens, private user data, and production exports should stay local unless a secure support process explicitly requests a redacted artifact. For routine questions, link to the relevant help article first and include screenshots or logs only when they clarify the issue.
Help-Center Relationship
The docs in this folder are intended to become source content for help.firestruct.com. Support articles should be imported from module gui.md and cli.md files when the help center is ready.
Help-center articles should use stable module names, clear safety language, and links that resolve to published article slugs rather than repository paths. That keeps search crawlers and users away from broken Markdown source URLs.
Source Anchors
Sources/FirestructApp/Features/Support/UI/SupportModuleView.swiftSources/FirestructApp/Features/Support/UI/ChatwootSupportWebView.swiftSources/FirestructApp/Features/Support/UI/SupportWidgetPanelController.swiftSources/FirestructApp/Features/Support/Model/ChatwootSupportConfiguration.swift