<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>D3-Js on Visualizing.JP</title>
        <link>https://visualizing.jp/en/tags/d3-js/</link>
        <description>Recent content in D3-Js on Visualizing.JP</description>
        <generator>Hugo -- gohugo.io</generator>
        <language>en-US</language>
        <copyright>Yuichi Yazaki</copyright>
        <lastBuildDate>Sat, 03 Oct 2020 00:00:00 +0900</lastBuildDate><atom:link href="https://visualizing.jp/en/tags/d3-js/index.xml" rel="self" type="application/rss+xml" /><item>
        <title>Drawing Charts with D3.js and Flexbox Instead of SVG</title>
        <link>https://visualizing.jp/en/d3-flexbox/</link>
        <pubDate>Sat, 03 Oct 2020 00:00:00 +0900</pubDate>
        
        <guid>https://visualizing.jp/en/d3-flexbox/</guid>
        <description>&lt;img src="https://visualizing.jp/d3-flexbox/images/social-facebook.png" alt="Featured image of post Drawing Charts with D3.js and Flexbox Instead of SVG" /&gt;&lt;p&gt;This article introduces Drawing Charts with D3.js and Flexbox Instead of SVG from a practical data visualization workflow perspective.&lt;/p&gt;
&lt;p&gt;The emphasis is on how the tool, format, or workflow fits into practical visualization work.&lt;/p&gt;
&lt;h2 id=&#34;practical-context&#34;&gt;Practical Context
&lt;/h2&gt;&lt;p&gt;A tool or format matters because it changes what can be produced, repeated, shared, or maintained. The important question is not only whether it works once, but whether it supports a reliable workflow with clear inputs and outputs.&lt;/p&gt;
&lt;h2 id=&#34;workflow-notes&#34;&gt;Workflow Notes
&lt;/h2&gt;&lt;ul&gt;
&lt;li&gt;Check the data format and assumptions before adopting the workflow.&lt;/li&gt;
&lt;li&gt;Separate one-time setup issues from repeatable production steps.&lt;/li&gt;
&lt;li&gt;Document version, data source, and conversion settings when reproducibility matters.&lt;/li&gt;
&lt;li&gt;Prefer simple outputs first, then add interaction or styling after the data is correct.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;summary&#34;&gt;Summary
&lt;/h2&gt;&lt;p&gt;Drawing Charts with D3.js and Flexbox Instead of SVG is relevant as part of the broader craft of preparing, transforming, and publishing data. The value comes from understanding both the technical mechanism and the communication task it supports.&lt;/p&gt;</description>
        </item>
        <item>
        <title>Responsive Layouts with D3.js</title>
        <link>https://visualizing.jp/en/responsive-d3/</link>
        <pubDate>Fri, 01 Jan 2016 00:00:00 +0900</pubDate>
        
        <guid>https://visualizing.jp/en/responsive-d3/</guid>
        <description>&lt;img src="https://visualizing.jp/responsive-d3/images/thumb_ph_vizjp.png" alt="Featured image of post Responsive Layouts with D3.js" /&gt;&lt;p&gt;This article introduces Responsive Layouts with D3.js from a practical data visualization workflow perspective.&lt;/p&gt;
&lt;p&gt;The emphasis is on how the tool, format, or workflow fits into practical visualization work.&lt;/p&gt;
&lt;h2 id=&#34;practical-context&#34;&gt;Practical Context
&lt;/h2&gt;&lt;p&gt;A tool or format matters because it changes what can be produced, repeated, shared, or maintained. The important question is not only whether it works once, but whether it supports a reliable workflow with clear inputs and outputs.&lt;/p&gt;
&lt;h2 id=&#34;workflow-notes&#34;&gt;Workflow Notes
&lt;/h2&gt;&lt;ul&gt;
&lt;li&gt;Check the data format and assumptions before adopting the workflow.&lt;/li&gt;
&lt;li&gt;Separate one-time setup issues from repeatable production steps.&lt;/li&gt;
&lt;li&gt;Document version, data source, and conversion settings when reproducibility matters.&lt;/li&gt;
&lt;li&gt;Prefer simple outputs first, then add interaction or styling after the data is correct.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;summary&#34;&gt;Summary
&lt;/h2&gt;&lt;p&gt;Responsive Layouts with D3.js is relevant as part of the broader craft of preparing, transforming, and publishing data. The value comes from understanding both the technical mechanism and the communication task it supports.&lt;/p&gt;</description>
        </item>
        <item>
        <title>Reusable Components with D3.js</title>
        <link>https://visualizing.jp/en/d3js-reusable/</link>
        <pubDate>Thu, 18 Dec 2014 00:00:00 +0900</pubDate>
        
        <guid>https://visualizing.jp/en/d3js-reusable/</guid>
        <description>&lt;img src="https://visualizing.jp/d3js-reusable/images/thumb_ph_vizjp.png" alt="Featured image of post Reusable Components with D3.js" /&gt;&lt;p&gt;This article introduces Reusable Components with D3.js from a practical data visualization workflow perspective.&lt;/p&gt;
&lt;p&gt;The emphasis is on how the tool, format, or workflow fits into practical visualization work.&lt;/p&gt;
&lt;h2 id=&#34;practical-context&#34;&gt;Practical Context
&lt;/h2&gt;&lt;p&gt;A tool or format matters because it changes what can be produced, repeated, shared, or maintained. The important question is not only whether it works once, but whether it supports a reliable workflow with clear inputs and outputs.&lt;/p&gt;
&lt;h2 id=&#34;workflow-notes&#34;&gt;Workflow Notes
&lt;/h2&gt;&lt;ul&gt;
&lt;li&gt;Check the data format and assumptions before adopting the workflow.&lt;/li&gt;
&lt;li&gt;Separate one-time setup issues from repeatable production steps.&lt;/li&gt;
&lt;li&gt;Document version, data source, and conversion settings when reproducibility matters.&lt;/li&gt;
&lt;li&gt;Prefer simple outputs first, then add interaction or styling after the data is correct.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;summary&#34;&gt;Summary
&lt;/h2&gt;&lt;p&gt;Reusable Components with D3.js is relevant as part of the broader craft of preparing, transforming, and publishing data. The value comes from understanding both the technical mechanism and the communication task it supports.&lt;/p&gt;</description>
        </item>
        <item>
        <title>D3 Unconf 2014 Report, Part 2</title>
        <link>https://visualizing.jp/en/d3-unconf-2014-2/</link>
        <pubDate>Sun, 20 Apr 2014 00:00:00 +0900</pubDate>
        
        <guid>https://visualizing.jp/en/d3-unconf-2014-2/</guid>
        <description>&lt;img src="https://visualizing.jp/d3-unconf-2014-2/images/fi_D3Conf2014-2.png" alt="Featured image of post D3 Unconf 2014 Report, Part 2" /&gt;&lt;p&gt;This article introduces D3 Unconf 2014 Report, Part 2 from a practical data visualization workflow perspective.&lt;/p&gt;
&lt;p&gt;The emphasis is on how the tool, format, or workflow fits into practical visualization work.&lt;/p&gt;
&lt;h2 id=&#34;practical-context&#34;&gt;Practical Context
&lt;/h2&gt;&lt;p&gt;A tool or format matters because it changes what can be produced, repeated, shared, or maintained. The important question is not only whether it works once, but whether it supports a reliable workflow with clear inputs and outputs.&lt;/p&gt;
&lt;h2 id=&#34;workflow-notes&#34;&gt;Workflow Notes
&lt;/h2&gt;&lt;ul&gt;
&lt;li&gt;Check the data format and assumptions before adopting the workflow.&lt;/li&gt;
&lt;li&gt;Separate one-time setup issues from repeatable production steps.&lt;/li&gt;
&lt;li&gt;Document version, data source, and conversion settings when reproducibility matters.&lt;/li&gt;
&lt;li&gt;Prefer simple outputs first, then add interaction or styling after the data is correct.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;summary&#34;&gt;Summary
&lt;/h2&gt;&lt;p&gt;D3 Unconf 2014 Report, Part 2 is relevant as part of the broader craft of preparing, transforming, and publishing data. The value comes from understanding both the technical mechanism and the communication task it supports.&lt;/p&gt;</description>
        </item>
        <item>
        <title>D3 Unconf 2014 Report, Part 1</title>
        <link>https://visualizing.jp/en/d3-unconf-2014-1/</link>
        <pubDate>Fri, 11 Apr 2014 00:00:00 +0900</pubDate>
        
        <guid>https://visualizing.jp/en/d3-unconf-2014-1/</guid>
        <description>&lt;img src="https://visualizing.jp/d3-unconf-2014-1/images/fi_D3Conf2014-1.png" alt="Featured image of post D3 Unconf 2014 Report, Part 1" /&gt;&lt;p&gt;This article introduces D3 Unconf 2014 Report, Part 1 from a practical data visualization workflow perspective.&lt;/p&gt;
&lt;p&gt;The emphasis is on how the tool, format, or workflow fits into practical visualization work.&lt;/p&gt;
&lt;h2 id=&#34;practical-context&#34;&gt;Practical Context
&lt;/h2&gt;&lt;p&gt;A tool or format matters because it changes what can be produced, repeated, shared, or maintained. The important question is not only whether it works once, but whether it supports a reliable workflow with clear inputs and outputs.&lt;/p&gt;
&lt;h2 id=&#34;workflow-notes&#34;&gt;Workflow Notes
&lt;/h2&gt;&lt;ul&gt;
&lt;li&gt;Check the data format and assumptions before adopting the workflow.&lt;/li&gt;
&lt;li&gt;Separate one-time setup issues from repeatable production steps.&lt;/li&gt;
&lt;li&gt;Document version, data source, and conversion settings when reproducibility matters.&lt;/li&gt;
&lt;li&gt;Prefer simple outputs first, then add interaction or styling after the data is correct.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;summary&#34;&gt;Summary
&lt;/h2&gt;&lt;p&gt;D3 Unconf 2014 Report, Part 1 is relevant as part of the broader craft of preparing, transforming, and publishing data. The value comes from understanding both the technical mechanism and the communication task it supports.&lt;/p&gt;</description>
        </item>
        <item>
        <title>Normalization in Visualization</title>
        <link>https://visualizing.jp/en/normalize-visualize/</link>
        <pubDate>Mon, 24 Mar 2014 00:00:00 +0900</pubDate>
        
        <guid>https://visualizing.jp/en/normalize-visualize/</guid>
        <description>&lt;img src="https://visualizing.jp/normalize-visualize/images/fi_Normalize.png" alt="Featured image of post Normalization in Visualization" /&gt;&lt;p&gt;This article examines Normalization in Visualization as a case study in data visualization, information design, or visual culture.&lt;/p&gt;
&lt;p&gt;The article is useful as a case study in how data, design choices, and context shape interpretation.&lt;/p&gt;
&lt;h2 id=&#34;what-it-shows&#34;&gt;What It Shows
&lt;/h2&gt;&lt;p&gt;The main point is not only the finished visual form, but also the reasoning behind it: what was selected, emphasized, simplified, or compared. Those decisions determine what readers can notice.&lt;/p&gt;
&lt;h2 id=&#34;design-and-context-notes&#34;&gt;Design and Context Notes
&lt;/h2&gt;&lt;ul&gt;
&lt;li&gt;Identify the data, audience, and communication goal behind the work.&lt;/li&gt;
&lt;li&gt;Notice how visual form, annotation, and context shape interpretation.&lt;/li&gt;
&lt;li&gt;Distinguish the core idea from details that belong to a specific medium or moment.&lt;/li&gt;
&lt;li&gt;Treat the example as a prompt for design judgment rather than a universal rule.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;summary&#34;&gt;Summary
&lt;/h2&gt;&lt;p&gt;Normalization in Visualization shows how visualization works as both analysis and communication. Reading it carefully means looking at the data, the visual encoding, and the cultural or practical context around the work.&lt;/p&gt;</description>
        </item>
        <item>
        <title>D3: Data Formats and Requests</title>
        <link>https://visualizing.jp/en/d3-requests/</link>
        <pubDate>Sun, 22 Sep 2013 00:00:00 +0900</pubDate>
        
        <guid>https://visualizing.jp/en/d3-requests/</guid>
        <description>&lt;img src="https://visualizing.jp/d3-requests/images/fi_D3DatFormat.png" alt="Featured image of post D3: Data Formats and Requests" /&gt;&lt;p&gt;This article introduces D3: Data Formats and Requests from a practical data visualization workflow perspective.&lt;/p&gt;
&lt;p&gt;The emphasis is on how the tool, format, or workflow fits into practical visualization work.&lt;/p&gt;
&lt;h2 id=&#34;practical-context&#34;&gt;Practical Context
&lt;/h2&gt;&lt;p&gt;A tool or format matters because it changes what can be produced, repeated, shared, or maintained. The important question is not only whether it works once, but whether it supports a reliable workflow with clear inputs and outputs.&lt;/p&gt;
&lt;h2 id=&#34;workflow-notes&#34;&gt;Workflow Notes
&lt;/h2&gt;&lt;ul&gt;
&lt;li&gt;Check the data format and assumptions before adopting the workflow.&lt;/li&gt;
&lt;li&gt;Separate one-time setup issues from repeatable production steps.&lt;/li&gt;
&lt;li&gt;Document version, data source, and conversion settings when reproducibility matters.&lt;/li&gt;
&lt;li&gt;Prefer simple outputs first, then add interaction or styling after the data is correct.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;summary&#34;&gt;Summary
&lt;/h2&gt;&lt;p&gt;D3: Data Formats and Requests is relevant as part of the broader craft of preparing, transforming, and publishing data. The value comes from understanding both the technical mechanism and the communication task it supports.&lt;/p&gt;</description>
        </item>
        <item>
        <title>D3: TopoJSON</title>
        <link>https://visualizing.jp/en/d3-topojson/</link>
        <pubDate>Wed, 18 Sep 2013 00:00:00 +0900</pubDate>
        
        <guid>https://visualizing.jp/en/d3-topojson/</guid>
        <description>&lt;img src="https://visualizing.jp/d3-topojson/images/fi_TopoJson.png" alt="Featured image of post D3: TopoJSON" /&gt;&lt;p&gt;This article introduces D3: TopoJSON from a practical data visualization workflow perspective.&lt;/p&gt;
&lt;p&gt;The emphasis is on how the tool, format, or workflow fits into practical visualization work.&lt;/p&gt;
&lt;h2 id=&#34;practical-context&#34;&gt;Practical Context
&lt;/h2&gt;&lt;p&gt;A tool or format matters because it changes what can be produced, repeated, shared, or maintained. The important question is not only whether it works once, but whether it supports a reliable workflow with clear inputs and outputs.&lt;/p&gt;
&lt;h2 id=&#34;workflow-notes&#34;&gt;Workflow Notes
&lt;/h2&gt;&lt;ul&gt;
&lt;li&gt;Check the data format and assumptions before adopting the workflow.&lt;/li&gt;
&lt;li&gt;Separate one-time setup issues from repeatable production steps.&lt;/li&gt;
&lt;li&gt;Document version, data source, and conversion settings when reproducibility matters.&lt;/li&gt;
&lt;li&gt;Prefer simple outputs first, then add interaction or styling after the data is correct.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&#34;summary&#34;&gt;Summary
&lt;/h2&gt;&lt;p&gt;D3: TopoJSON is relevant as part of the broader craft of preparing, transforming, and publishing data. The value comes from understanding both the technical mechanism and the communication task it supports.&lt;/p&gt;</description>
        </item>
        
    </channel>
</rss>
