dosubot[bot] commented on issue #36794: URL: https://github.com/apache/superset/issues/36794#issuecomment-3681995081
<!-- Greeting --> Hi @amoljagadale-max! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team. <!-- Answer --> Superset's dashboard layout and styling are intentionally constrained by its architecture, so pixel-perfect replication of Figma designs or highly custom UI/UX is not feasible—layout is managed by a grid system and chart slices, and fine-grained CSS or grouping is limited and often inconsistent. While you can try advanced CSS overrides, these are best-effort and may break with updates or not apply as expected due to the way components are rendered and styled [[source]](https://github.com/apache/superset/blob/master/superset-frontend/src/dashboard/components/Dashboard.jsx) [[source]](https://github.com/apache/superset/issues/32820). Ant Design theming in Superset primarily affects core UI elements like navigation, menus, and buttons, not dashboard or chart card visuals. Even with per-dashboard theme assignment and the theme editor, changes to colors, typography, or spacing will not significantly impact dashboard content or chart appearance [[source]](https://github.com/apache/superset/discussions/34647) [[source]](https://github.com/apache/superset/discussions/35532). For ECharts, customization is limited to what is exposed in the chart editor and JSON metadata. Some appearance tweaks (like axis label font size or colors) may be possible via JSON, but support is inconsistent and depends on chart type and Superset/ECharts version. Embedding custom ECharts via iFrame in Markdown is not officially supported and is often blocked by security/sanitization settings; the recommended way to embed dashboards is via the Embedded SDK with guest tokens, which does not allow arbitrary chart extension via iFrame [[source]](https://github.com/apache/superset/discussions/33127) [[source]](https://github.com/apache/superset/issues/36377). Exporting dashboards (PNG/PDF/email) is limited to the visible viewport and desktop layout—there is no built-in support for exporting the full scrollable dashboard, controlling export dimensions, or generating mobile-friendly/responsive exports. Configuration options exist for WebDriver timeouts and device scale factor, but not for mobile rendering or blank space removal. These are known and expected limitations of the current export engine [[source]](https://github.com/apache/superset/discussions/31432). In summary: Superset is designed for data exploration and BI, not for pixel-perfect UI or mobile-first exports. For richer UI, experiment with advanced CSS selectors and JSON metadata, but expect limitations. For embedding and theming, use the official SDK and theme editor, but know their scope is mostly core UI, not dashboard visuals. For exports, current limitations are by design and not easily worked around. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/6dff462c-f10d-4a94-9f08-c407dcefe204?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/6dff462c-f10d-4a94-9f08-c407dcefe204?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/6dff462c-f10d-4a94-9f08-c407dcefe204?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/6dff462c-f10d-4a94-9f08-c407dcefe204?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/6dff462c-f10d-4a94-9f08-c407dcefe204?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/6dff462c-f10d-4a94-9f08-c407dcefe204?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/6dff462c-f10d-4a94-9f08-c407dcefe204?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=Superset%27s%20dashboard%20layout%20and%20styling%20are%20intentionally%20constrained%20by%20its%20architecture%2C%20so%20pixel-perfect%20replication%20of%20Figma%20designs%20or%20highly%20custom%20UI/UX%20is%20not%20feasible%E2%80%94layout%20is%20managed%20by%20a%20grid%20system%20and%20chart%20slices%2C%20and%20fine-grained%20CSS%20or%20grouping%20is%20limited%20and%20often%20inconsistent.%20While%20you%20can%20try%20advanced%20CSS%20overrides%2C%20these%20are%20best-effort%20and%20may%20break%20with%20updates%20or%20not%20apply%20as%20expected%20due%20to%20the%20way%20components%20are%20rendered%20and%20styled%20%5B%5Bsource%5D%5D%28https%3A//github.com/apache/superset/blob/master/superset-frontend/src/dashboard/components/Dashboard.jsx%29%20%5B %5Bsource%5D%5D%28https%3A//github.com/apache/superset/issues/32820%29.%0A%0AAnt%20Design%20theming%20in%20Superset%20primarily%20affects%20core%20UI%20elements%20like%20navigation%2C%20menus%2C%20and%20buttons%2C%20not%20dashboard%20or%20chart%20card%20visuals.%20Even%20with%20per-dashboard%20theme%20assignment%20and%20the%20theme%20editor%2C%20changes%20to%20colors%2C%20typography%2C%20or%20spacing%20will%20not%20significantly%20impact%20dashboard%20content%20or%20chart%20appearance%20%5B%5Bsource%5D%5D%28https%3A//github.com/apache/superset/discussions/34647%29%20%5B%5Bsource%5D%5D%28https%3A//github.com/apache/superset/discussions/35532%29.%0A%0AFor%20ECharts%2C%20customization%20is%20limited%20to%20what%20is%20exposed%20in%20the%20chart%20editor%20and%20JSON%20metadata.%20Some%20appearance%20tweaks%20%28like%20axis%20label%20font%20size%20or%20colors%29%20may%20be%20possible%20via%20JSON%2C%20but%20support%20is%20inconsistent%20and%20depends%20on%20chart%20type%20and%20Superset /ECharts%20version.%20Embedding%20custom%20ECharts%20via%20iFrame%20in%20Markdown%20is%20not%20officially%20supported%20and%20is%20often%20blocked%20by%20security/sanitization%20settings%3B%20the%20recommended%20way%20to%20embed%20dashboards%20is%20via%20the%20Embedded%20SDK%20with%20guest%20tokens%2C%20which%20does%20not%20allow%20arbitrary%20chart%20extension%20via%20iFrame%20%5B%5Bsource%5D%5D%28https%3A//github.com/apache/superset/discussions/33127%29%20%5B%5Bsource%5D%5D%28https%3A//github.com/apache/superset/issues/36377%29.%0A%0AExporting%20dashboards%20%28PNG/PDF/email%29%20is%20limited%20to%20the%20visible%20viewport%20and%20desktop%20layout%E2%80%94there%20is%20no%20built-in%20support%20for%20exporting%20the%20full%20scrollable%20dashboard%2C%20controlling%20export%20dimensions%2C%20or%20generating%20mobile-friendly/responsive%20exports.%20Configuration%20options%20exist%20for%20WebDriver%20timeouts%20and%20device%20scale%20factor%2C%20but%20not%20for%20mobile%20rendering% 20or%20blank%20space%20removal.%20These%20are%20known%20and%20expected%20limitations%20of%20the%20current%20export%20engine%20%5B%5Bsource%5D%5D%28https%3A//github.com/apache/superset/discussions/31432%29.%0A%0AIn%20summary%3A%20Superset%20is%20designed%20for%20data%20exploration%20and%20BI%2C%20not%20for%20pixel-perfect%20UI%20or%20mobile-first%20exports.%20For%20richer%20UI%2C%20experiment%20with%20advanced%20CSS%20selectors%20and%20JSON%20metadata%2C%20but%20expect%20limitations.%20For%20embedding%20and%20theming%2C%20use%20the%20official%20SDK%20and%20theme%20editor%2C%20but%20know%20their%20scope%20is%20mostly%20core%20UI%2C%20not%20dashboard%20visuals.%20For%20exports%2C%20current%20limitations%20are%20by%20design%20and%20not%20easily%20worked%20around.) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/ tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/36794) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
