Where to Get Help or Report Issues for dc.js

For dc.js support, use Stack Overflow or the user group ("mailing list") for questions and longer discussions, and GitHub Issues for bug reports and feature requests. The project also maintains a Changelog, a Frequently Asked Questions and Wiki page, and an API Reference for self-service answers. When asking for help, include a working example — the project explicitly notes that this gets you help faster.

Which channel to use

The site is direct about routing: "Please direct questions and support requests to Stack Overflow or the user group." GitHub Issues is reserved for bugs and feature requests, so a usage question posted there is likely to be redirected.

Documentation to check first

• Annotated source to the Nasdaq Example — the site points to this as the starting point for understanding how a full dc.js dashboard is assembled.
• API Reference — for method-level behavior.
• Frequently Asked Questions and Wiki — worth searching before posting, since recurring questions tend to land here.
• Changelog — relevant if something changed between versions; the documentation page itself is marked "WIP - Documentation for dc-v5," so version matters when you compare your code against the docs.

Get help faster with a working example

The site's own advice is to fork a starter and reproduce your problem there:

• blank jsFiddle — example
• blank jsFiddle — blank
• bl.ock — example
• bl.ock — blank

The practical workflow: fork the blank fiddle, add the minimum chart and data that reproduces the issue, confirm it still misbehaves, then paste that link into your Stack Overflow question or mailing-list post. A runnable link removes the guesswork for whoever answers, which is why the project calls it out explicitly.

What dc.js is, in one line

dc.js is a JavaScript charting library with native crossfilter support for efficient exploration of large multi-dimensional datasets; it uses d3 to render charts as CSS-friendly SVG, and the charts are data driven and reactive, giving instant feedback on user interaction. It runs in the browser and on mobile devices. That combination — crossfilter for filtering, d3 for rendering — is why most questions you'll ask fall into either "how do I filter/group the data" or "how do I render/style the chart," and it helps to say which side your question is on.

A concrete example of the kind of question these channels handle

The Nasdaq 100 example on the site (27 years of index data, 1985/11/01–2012/06/29) is built to answer questions like: what is the chance the Nasdaq 100 gains or loses tomorrow, is Friday or Monday the unluckiest day for investors, is spring better than winter to invest, and when did the outliers occur. If you're trying to reproduce that kind of interaction — a time-range brush that filters the other charts, a reset control, a day-of-week breakdown — and it isn't behaving, that's a Stack Overflow or user-group question, ideally with a fiddle attached. Public data source for that example: PiTrading.com.