DETAIL PANEL · DEMO

Sample project review

Keep your context while reviewing the details.

Ready for review
Template route
/felix/components/funnel-chart
Project
Riverside workspace (fictitious)
Owner
Morgan Lee (fictitious)

Summary

This is an original example. The underlying page stays visible while the panel holds the details. No account, payment or external service is connected.

Review note

Skip to content

Funnel chart ​

Back to Felix charts · JSON chart contract

A funnel compares ordered stages of a nested population: people reaching a later stage also reached the earlier ones. Stage width can encode count, while overall and previous-step rates answer different questions. Do not add stage counts as if they were disjoint parts. Use a bar chart for unrelated categories, a Sankey for branching flow and explicit drop-off paths, or cohort retention for activity by elapsed period where users may return.

Preview, spec and editable example ​

Funnel

Fictitious local data

FunnelStage: View · Count: 100Stage: Start · Count: 78Stage: Submit · Count: 55Stage: Complete · Count: 40View: 100Start: 78Submit: 55Complete: 40

4 source rows from sample.funnel. Focus a mark or a data row to read exact values.

Synthetic local data · funnel · sample.funnel

The preview is rendered from the JSON in Spec. Open Example to edit the component, source, encoding and options, then choose Render JSON. The source registry is separately editable so you can try your own labels and values without embedding numbers in the chart spec. Nothing is sent, saved or fetched. Invalid input reports a field path and keeps the last valid preview.

Wire contract ​

This example selects funnel. The spec uses component, optional title, subtitle and insight, a named data.source, encoding and component-specific options. Data filters, stable sorting and limits are applied before rendering. The source holds headers and rows; every encoding names a real source column.

json
{
  "component": "funnel",
  "title": "Funnel",
  "subtitle": "Fictitious local data",
  "data": {
    "source": "sample.funnel"
  },
  "encoding": {
    "step": "Stage",
    "count": "Count"
  },
  "options": {}
}

Encoding ​

ChannelSource column
stepStage
countCount

Options ​

Supported contract options: highlight, unit. These are validated by component; unknown fields are rejected. This renderer supports a conservative subset and rejects options that are not implemented rather than ignoring them. See current renderer scope.

Data, interaction and accessibility ​

Hover, focus, click, Enter or Space on a mark to read its exact source row. Data view shows the same filtered and sorted source rows in a scrollable table. Replay motion replays the entrance; reduced motion removes it. Ready/Loading/Empty are local demonstration states only and never invent a network result. The controls and spec tabs support keyboard use, including Left/Right, Home and End in the tab list.

Felix chart colors adapt to light and dark appearance. Turquoise leads; slate supports the comparison. Highlight names, labels, a focus outline and the exact data remain available without relying only on color. Sources are local and bounded to 2,000 rows. Unknown components, sources, fields and options fail visibly. There is no HTML, JavaScript or remote URL execution in a spec.

Integration ​

vue
<script setup>
import FelixJsonChart from './FelixJsonChart.vue'
const spec = /* validated chart spec from your application */ {}
const sources = /* named local source registry */ {}
</script>

<template>
  <FelixJsonChart :spec="spec" :sources="sources" />
</template>

resolveSpec(spec, sources) validates and resolves a chart model; chartGeometry(model) derives marks from that model. The documentation wrapper owns editor drafts and the last valid preview. Your application owns data fetching, authorization, refresh/error state and persistence. This local example is not a live data service. See the contract and supported renderers before adapting production data.

Lateral detail drawer

Open a detail panel without losing the page behind it. This shared pattern follows the current template's colors. Fictitious data; actions stay local.