<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Dashboard on Lin's Blog</title><link>https://coder.tw/en/tags/dashboard/</link><description>Recent content in Dashboard on Lin's Blog</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 23 Dec 2016 01:58:44 +0000</lastBuildDate><atom:link href="https://coder.tw/en/tags/dashboard/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Make a Dashboard on a TV</title><link>https://coder.tw/en/posts/how-to-make-a-dashboard-on-tv/</link><pubDate>Fri, 23 Dec 2016 01:58:44 +0000</pubDate><guid>https://coder.tw/en/posts/how-to-make-a-dashboard-on-tv/</guid><description>&lt;p&gt;The TV hanging in our office has been sitting empty for a long time, and that is not a good use of it. So I recently started planning to show some important numbers on it, such as conversion rate, traffic, and live visitors. I originally thought a dashboard would be a simple request: two or three days of backend work to organize the data, then D3.js on the front end to draw the charts. Or I could make it even simpler and use custom reports in Google Analytics. But once I started researching, I found the problem was not so simple. Let me walk you through it.&lt;/p&gt;</description></item></channel></rss>