evidence

We’ve been using evidence (https://github.com/evidence-dev/evidence) for this. You can have agents build an ad hoc dashboard, or if it is worth sharing you can commit it.

Might want to add how this compares to other products in the space. Some that come to mind that are potentially tangentially related/similar: https://github.com/evidence-dev/evidence

We use ECharts extensively in Evidence (https://github.com/evidence-dev/evidence). Overall has been a delight.

We’re working on a static site generator for data analysts called evidence. It’s an alternative to conventional BI tools. Procedurally generating pages from data and linking them together is a core part of the offering. In many applications this is far easier for users than presenting them with a conventional filter interface. GitHub: https://github.com/evidence-dev/evidence Launch HN: https://news.ycombinator.com/item?id=28304781

We use a similar “baked data” approach with Duck DB + a static site generator in evidence https://github.com/evidence-dev/evidence

If you are a data analyst interested in making web apps, you might be interested in my OSS project, Evidence, which is a Static Site Generator for building reports and data apps with SQL and markdown. Repo (3K stars): https://github.com/evidence-dev/evidence Previous discussions on HN: https://news.ycombinator.com/item?id=28304781 - 91 comments https://news.ycombinator.com/item?id=35645464 - 97 comments

You might be interested in Evidence, a SQL-based open source BI tool where all content is version-controllable. Disclaimer: I’m one of the maintainers. A lot of companies use Evidence for customer facing and embedded reporting. https://github.com/evidence-dev/evidence Previous HN discussions: https://news.ycombinator.com/item?id=35645464 (97 comments) https://news.ycombinator.com/item?id=28304781 (91 comments)

We used ECharts to build our charting library at Evidence and it’s been a great experience overall (https://evidence.dev). We started with D3 and a few other tools, but felt that we get a lot more out of the box with ECharts, like interactivity and an events API. ECharts is also a lot more extensible than people give it credit for. If anyone is curious, we documented the process of selecting a charting library after assessing several options: https://github.com/evidence-dev/evidence/issues/136

One of the founders of Evidence here. Thanks the kind words Mike - that means a lot coming from you. I think that distinction is right -- we are focused on making a framework that is easy to use with a data analyst skill set, which generally means as little javascript as possible. As an example, the way you program client-side interactions in Evidence is by templating SQL which we run in duckDB web assembly, rather than by writing javascript. Evidence is also open source, for anyone who's interested. Repo: https://github.com/evidence-dev/evidence Previous discussions on HN: https://news.ycombinator.com/item?id=28304781 - 91 comments https://news.ycombinator.com/item?id=35645464 - 97 comments

I'm quite excited about this, and would also love to have it distributed as an NPM package. I work on an OSS web framework for reporting/ decision support applications (https://github.com/evidence-dev/evidence), and we use WASM duckDB as our query engine. Several folks have asked for PRQL support, and this looks like it could be a pretty seamless way to add it.

This looks awesome, congratulations. I think you’re onto something here. I work on an OSS reporting and analytics tool (https://github.com/evidence-dev/evidence) and the amount of time and effort that goes into a really good “print pdf”, and how valuable people find it, has been one of the more surprising parts of the project to me.

> Not sure the language you choose matters as much as making the API usable by a wide audience. Fully agree with this, and having typeset my masters thesis and later my resume using LaTeX, I think that the “authoring experience” is definitely the place to focus on improving, LaTeX just takes too damn long to get something good. If you’re interested in the “markup to document publishing” space, you might also be interested in the open-source report publishing tool I’m now working on, Evidence.dev (https://github.com/evidence-dev/evidence). It’s similarly based on markdown, though uses code fences to execute code, HTML style tags for charts and components, and {…} for JavaScript, i.e. --- title: Lorem Ipsum description: dolor sit amet, consectetur adipiscing elit --- ```sql petal_vs_sepal SELECT petal_length,

I'm working on an OSS BI tool focused on a document form factor. Might be of interest to you. https://github.com/evidence-dev/evidence