Presentation "Sketching designs using the Five Design-Sheet Methodology" - IEEE VIS2015
GitHub REST API v3 Newer versions seem to be based on GraphQL: GitHub GraphQL API v4
GitHub API - Event types GitHub API - Users API
GHArchive Data saved by the GHArchive Possible preprocessed dataset for the graph visualization
Create React App documentation React documentation React Router documentation
Google's Typescript style guide Airbnb's React/JSX Style Guide
Blog - Coderstats: GitHub data science
Devtrends Devtrends data source
Metabase allows for choosing different visualizations for the same dataset
Interactive notebooks of visualizations Interesting controls/interactions with a force graph (dblclick zoom, max limit on zooming)
Search functionality in a d3.js graph
Using D3 and React Together to Make Visualizations in TypeScript This one is pretty outdated but a good starter. I adapted this one as a base for this project, and had to fix many errors that occured due to the use of older versions of TypeScript, React and D3.
D3 within React the right way: Essentially uses a (second) virtual DOM, seems fine, but limit's us to React's animations - which I am not too familiar with.
Bringing Together React, D3, And Their Ecosystem Discusses a lot of possibilities, esp. their advantages and disadvantages, and interoperability between their ecosystems. The simplest method, the one I am using currently, i.e. in commit 7eadba35943b54dffc3374998e43f5cf132f3cf2, let's D3 handle all DOM-related operations, but results in a poor experience considering React. Also this does not render server-side, which should be of no concern to me currently, but is, if I somehow, want to release this on my website (for fun or any other reason) The "best" approach he discusses makes it so that React has full control over the DOM, which also means that all shapes and animations have to be implemented in React and not D3, which seems like a huge amount of work that I would only deem necessary in a professional production environment. The third approach is something that already seems like mine, the discussion of that follows in the following literature reference
Integrating D3.js visualizations in a React app I like the approach, because it moves the DOM manipulation strictly to D3 which makes it so that 2 libraries do not manipulate the same DOM at the same time.