Skip to content

feat: product page revamp - #578

Merged
krishanu-datazip merged 28 commits into
masterfrom
product-pages-revamp
Oct 15, 2026
Merged

krishanu-datazip merged 28 commits into
masterfrom
product-pages-revamp

Conversation

@krishnajain-15

Copy link
Copy Markdown
Collaborator

Summary

Rebuilds /olake-go and /olake-fusion from the new Figma landing-page designs, on a shared set of product-page building blocks.

What changed

OLake Go

  • New hero (sources strip, dashboard picture), problem statement, five feature tabs, benchmarks, call-to-action and FAQ.
  • The benchmark table only lists sources that have numbers in the chosen mode, so Kafka and MSSQL no longer show "coming soon" on mobile.
  • The sources marquee no longer runs into its label.

OLake Fusion

  • New hero with contour rings and the Run History dashboard.
  • Problem statement as a ruled column with four line drawings.
  • Features: Tiered Compaction, Omit Decay, Easy Configuration and Self-Hosted, each with its own product picture.
  • Benchmarks against Spark compaction, with the "How OLake Fusion does this" notes. The table fits phone widths without sideways scrolling.
  • Call-to-action and FAQ.

Shared (src/components/landing/product/)

  • ProductPage, ProductHero, ProductFeatures (ARIA tabs, keyboard navigation), BenchmarkShell, ProductCta, ProductFaq, plus mock.tsx helpers and product.css.
  • Product pictures are drawn at design size and scaled with CSS only, with no JS resize logic.

Notes for reviewers

  • The Fusion hero headline stays on the existing PostHog A/B test. The Figma headline is not applied.
  • FAQ answers are kept as they are, because they feed the FAQ JSON-LD in seo.ts.
  • Copy fixes from the design: "Maintainence" to "Maintenance", "Self Hosted" to "Self-Hosted", "10x faster" to "10x simpler" for the config-parameter row, and the second "Environment" row to "Status".
  • Grey text that failed WCAG AA contrast in the design uses darker tokens (text-olake-muted, text-olake-muted-on-dark, text-olake-blue-on-dark).
  • Navbar and footer are the shared Lakeside ones and are unchanged.
  • Removed: old Go and Fusion components, fusion.css, and the shared images only they used.
  • Added fonts: Geist (weights 300–600) and Geist Mono, self-hosted with the licence file.

Testing

  • docusaurus build passes; TypeScript has no errors.
  • Compared against Figma at 1440px; checked 390, 820 and 1024px for layout and sideways scrolling.
  • Checked each feature tab and the PostHog headline fallback.

Replace the hero, architecture diagram, cloud problem section, feature
selector, benchmark card and closing CTA with the new design:

- Hero on a strata-line background with Github / Visit Docs buttons, a
  scrolling "Available Sources" strip and the Jobs dashboard mock that
  fades into the page.
- "Problem Statement" frame with four illustrated problem cards.
- Features card with pill tabs and the blue CDC card holding the job
  editor mock.
- Dark full-bleed benchmark section: latest-release strip, comparison
  table (full load / CDC, five sources), "How OLake Go does this" notes
  and a link bar to the detailed benchmarks.
- Blue "Get in touch" card and a restyled FAQ accordion (same questions,
  so the FAQPage JSON-LD still matches).

Product mocks are drawn at design size and scaled to fit with CSS only.
Assets are exported from Figma into static/img/landing/go. Geist Mono is
self-hosted for the benchmark notes. Text greys that fail WCAG AA in the
design use the existing --olake-muted tokens.
…ith Figma

Scale the dashboard mock's tab labels and their line height the way the
design's component instances render them, give the Jobs title its design
line height, and drop text-balance from the problem heading so it breaks
where the design does.
Give the scrolling logos their own lane after the "Available Sources"
label, faded in past it and out at the right edge with a mask, instead of
sliding under gradient overlays right up against the label text. Draw the
live dot as a CSS circle with a spread halo: the exported SVG built its
halo with feMorphology, which browsers render as a square.
Implement the go-2, go-3 and go-4 frames from Figma for the Schema
Evolution, Parallel Chunking and Resumable Syncs tabs: the schema mapping
table, the parallel chunk progress list and the checkpoint/resume cards,
each on its own placement of the dotted background, with the copy placed
as in its frame. CDC keeps the go-1 job editor.
…sen mode

Kafka and MSSQL only have full-load benchmarks, so with CDC selected their
tabs opened the "coming soon" panel. Follow the home page table: list a
source only in the modes it has data for, and when the selected source has
none in the new mode fall back to the first one that does. The choice
returns when switching back to Full Load.
Pull the pieces the OLake Go page shares with the upcoming OLake Fusion
design into src/components/landing/product: the page shell with the
palette and paper grain, the hero copy and buttons, the feature tab
strip and blue card, the dark benchmark shell (release strip, notes,
link bar), the closing CTA card, the FAQ accordion, and the mock-up
helpers (scale-to-fit, fade, shared navigation rail). Icons both pages
use move to static/img/landing/product.

The Go page renders pixel-identically at 1440px and 390px.
Rebuild /olake-fusion on the shared product page blocks used by OLake Go:

- Hero with the contour rings, the Run History dashboard and the lifted
  run-metrics card; on narrower screens the whole picture is fitted so the
  card is not cut off. The PostHog A/B headline is kept.
- Problem Statement as a ruled column with the four line drawings.
- Features: Tiered Compaction, Omit Decay, Easy Configuration and
  Self-Hosted, each with its own product mock-up.
- Benchmarks table against Spark compaction and the "How OLake Fusion does
  this" notes; the table fits phone widths without side scrolling.
- Get in touch CTA and the FAQ (existing answers kept for the JSON-LD).

ProductFeatures takes a className for the section's spacing. The old
Fusion components, fusion.css and the shared images only they used are
removed. Copy fixes from the design: Maintenance, Self-Hosted, "10x
simpler" for the parameter count, and "Status" for the deployment state.
@CLAassistant

CLAassistant commented Oct 13, 2026 •

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

Convert every image of the OLake Go and OLake Fusion pages (go/, fusion/
and product/ under static/img/landing) from SVG and PNG to WebP and point
the components at the new files.

- Icons and small line art: lossless, rasterised at 2x their display size.
- Page backgrounds and source logos (PNG): lossless WebP.
- Soft glows: lossy at a quarter size, they are blurs shown stretched.
- Hairline art (hero strata, hero contours): lossless at 1x.

MockIcon uses object-contain so icons that a flex row squeezes keep their
proportions, as the SVGs did. Rendered pages match the previous output at
1440 and 390 px (same heights, differences only at icon edges), and the
combined image weight drops from 1.12 MB to 0.46 MB.
@krishanu-datazip

Copy link
Copy Markdown
Collaborator

Duplicate images

fusion/feature-config-info.webp and fusion/feature-config-question.webp
fusion/dashboard-caret.webp and fusion/dashboard-caret-open.webp
go/feature-chunking-dot.webp and go/feature-chunking-dot-lg.webp

Comment thread src/components/landing/go/GoDashboardMock.tsx Outdated
Comment thread src/components/landing/product/ProductFeatures.tsx
Comment thread src/components/landing/fusion/FusionDashboardMock.tsx Outdated
Comment thread src/components/landing/fusion/FusionHero.tsx Outdated
Comment thread src/components/landing/fusion/FusionFeatures.tsx
Comment thread src/components/landing/go/GoFeatures.tsx
Comment thread src/components/landing/product/mock.tsx Outdated
Comment thread src/components/landing/go/GoHero.tsx Outdated
Comment thread src/data/landing/go/features.ts Outdated
Comment thread src/components/landing/fusion/FusionFaq.tsx Outdated
Comment thread src/components/landing/product/ProductFaq.tsx Outdated
Comment thread src/components/landing/go/GoBenchmark.tsx Outdated
@krishanu-datazip

Copy link
Copy Markdown
Collaborator

Also in moblie view we have seperate design, we have to integrate that as well
Screenshot 2026-10-13 at 11 49 53 PM
This is our current design replace it the latest design

Three pairs of images were byte-for-byte identical. Keep one of each and
point the mock-ups at it:

- fusion/feature-config-info -> fusion/feature-config-question
- fusion/dashboard-caret-open -> fusion/dashboard-caret
- go/feature-chunking-dot-lg -> go/feature-chunking-dot

The rendered pages are unchanged.
…status

The Jobs table under the OLake Go hero repeated one source logo, one
destination logo and the green "Success" tag on every row, so a MySQL job
showed the MongoDB mark and a failed job looked successful.

- Each source and destination now shows its own logo, reusing the sources
  strip artwork (MySQL, PostgreSQL, MongoDB, Oracle, Amazon S3) plus the
  Apache Iceberg mark.
- Failed rows get a red tag and Pending rows an orange one; only Success
  keeps the green check.
- The placeholder destinations (Dropbox, Google Drive, OneDrive, Box) and
  SQLite are replaced with what OLake Go supports (Apache Iceberg, Amazon
  S3, Oracle), so every label has a real logo.
- The failed and running status icons move to shared product/ so the Go
  and Fusion dashboards use the same files; the four per-row logo files
  they replace are removed.
- Fusion's Omit Decay icons were named the wrong way round
  (decay-active was the done tick); renamed to decay-done and
  decay-pending. No visual change.
Comment thread src/data/landing/fusion/benchmark.ts
Comment thread src/components/landing/go/GoHero.tsx Outdated
@krishanu-datazip

Copy link
Copy Markdown
Collaborator

LGTM

@deepanshupal09-datazip deepanshupal09-datazip changed the title Product pages revamp feat: product page revamp Oct 15, 2026
@krishanu-datazip

Copy link
Copy Markdown
Collaborator

LGTM

@krishanu-datazip
krishanu-datazip merged commit 33b961f into master Oct 15, 2026
2 checks passed
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.

4 participants