Contact person: Power BI–Style FrontEnd Data Portal Construction

Phone:Show

Email:Show

Location: Bengaluru, India

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"Build a Frontend Data-Viz Portal (Superset Embedded) — Frontend Only
0) What already exists

Apache Superset is fully built, production-ready, and live.

Embedding is already enabled (embedding IDs / token flow is configured and available).

Data models, charts, and dashboards are all ready in Superset.

Important: This project is frontend-only. No backend work and no Superset changes are needed.

1) What I need built

A modern client-facing web portal that embeds our existing Superset charts/dashboards and presents them with a Power BI–style look & feel.

2) Core scope (must-haves)

Embedding integration:

Use existing embedding IDs / SDK tokens (or supported secure method) to render Superset visuals inside the portal.

No direct Superset UI exposure; visuals should appear native to the portal.

Branding & theming controls:

Ability to re-style embedded visuals at the portal level (e.g., color palette, fonts, light/dark mode) to match the overall dashboard theme.

Goal: final experience should feel like a polished Power BI client view.

Dashboard layout & UX:

Clean, responsive grid layout (desktop/tablet/mobile).

Sticky header with title, filters area, and optional KPI cards.

Smooth loading states, error fallbacks, and empty-state messages.

Filter & navigation shell:

Global date/client/site filters (wired to embedded content as supported).

Left nav / top tabs for switching dashboards or sections.

Security & access (frontend responsibilities only):

Respect and use the existing secure token/embedding mechanism.

No token issuing logic needs to be built here.

Documentation & handover:

Readme for how to add/change embedded charts, update theme, and deploy.

Short loom/video or notes for content editors.

3) Out of scope (to avoid scope creep)

No changes to Superset datasets, SQL, charts, or dashboards.

No changes to Superset configuration or server-side auth.

No backend or token-issuance service development.

4) Tech preferences (open to suggestions)

React / [login to view URL] for the portal (SPA or SSR acceptable).

Tailwind CSS (or CSS variables) for theme control.

Familiarity with Superset Embedded SDK / iFrame integration and best practices.

5) Acceptance criteria (how we’ll call it “done”)

Portal loads at least one full dashboard and 3–4 charts via embedding, using our existing IDs/tokens.

Theme switch (brand color palette) updates the look of embedded visuals to match the portal.

Layout is responsive and feels like a Power BI client view (clean, minimal chrome).

Filters, nav, and loading/error states function smoothly.

Clear documentation for future editors.

6) Nice to have (bonus points)

Reusable “ChartCard” component (title, info tooltip, export button if allowed).

Brand presets (save multiple color/font themes).

Accessibility basics (keyboard nav, ARIA landmarks).

Simple role-based view gating (frontend-only routing/guards).

7) What I’ll provide

Superset URL (prod) + sample embedding IDs/tokens.

Branding guide (logo, colors, typography).

Example dashboard list and desired portal sections.


Please share:

Relevant examples of Superset embedding or BI-style portals you’ve built.

A brief approach outline (stack, embedding method, theming plan).

Estimated timeline & fixed-price quote (or clear milestone pricing).

Notes:

Again, no backend or Superset-side changes are required—frontend only.

I value clean design, fast performance, and a smooth client experience." (client-provided description)