Comments (7)
Yes
4.27 would seem better in section 5 - patterns.
from data_viz_reader.
I think this is how we should reorganize Section 4 :
Sections 4.1, 4.2, 4.3, 4.18, 4.19 and 4.26 should all be put under 4.24 considering they are links to articles that contain some cool/unique data visualizations.
The remaining individual case studies that show the specific data visualizations with them can be treated as independent entities like they are currently. There are some case studies that are missing a visual with them and what I think is that it would be more appealing and understandable if each individual case study had at least 1 visual with it.
from data_viz_reader.
Yes! Thanks for adding more suggestions on this. It is obviously that 4.19 and 4.26 are not case studies, which should not be put in the same way as others. And I also agree with your points that each case studies better had at least one visual chart with reference.
Maybe we can work together to solve this problem? @SaloniS95
from data_viz_reader.
Sure! @lpyuan
Also, in my other Issue that I put up, I added this part where I think some other sections' subtopics can be put in section 4 and vice versa :
Sections :: suggested section
5.6 : case studies
5.10 : case study
4.27: fundamentals
what do you think about these??
from data_viz_reader.
It would be better to move 5.6 and 5.10 to chapter 4, and is 4.27 part of fundamentals or patterns?
from data_viz_reader.
For the individual case studies, what do you think about grouping the case studies by type of visualization (e.g. all maps grouped together)?
from data_viz_reader.
That's a good idea! I think we can do in that way~
from data_viz_reader.
Related Issues (20)
- Week 10 issue 4: addition of customer insights dashboard to chapter 3 case studies
- Section 6.9: Content addition related to Importance of Ethics
- Data Visualization Tip #03
- Section 2.1.3.6 lacking cohesiveness
- Adding Examples to Metrics in 6.2
- section 7.1 Future of Data Viz
- 2.7.2.4 improvements showing infographic/viz best practices
- More Readable Format Needed in 6.6.5.1
- 4.6 connections visualization is confusing
- New Structure of 4.4.5.1 ** Different Map Techniques **
- 2.4.7.7 Analytics Tools - Format Chart
- 2.4.7 Parameters in Tableau
- 7.4.8 Tabpy - More information
- 6.2 Readability
- 6.4 Data Cleaning
- 6.2 Hidden Data
- 6.2 define what 'prerequisites' are meant
- In section 2.1.3.6, formatting issue
- Section 2.2.2.1.3, duplicate graph
- Section 2.4.7.5 Creating Groups - Incorrect placement of <ul> <li> tags
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from data_viz_reader.