Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider rewriting the hero text/project "tagline" #78

Open
MarkBennett opened this issue Sep 25, 2021 · 4 comments · Fixed by #80
Open

Consider rewriting the hero text/project "tagline" #78

MarkBennett opened this issue Sep 25, 2021 · 4 comments · Fixed by #80
Labels
documentation Improvements or additions to documentation

Comments

@MarkBennett
Copy link

It's not totally clear why I should care about, "Composable, responsive, React-based data visualization".

Reading the motivation it seems like you've learned a lot over the last year, but I'd zoom in on the pain or challenge you faced and how how this solves it, then put a sentence that states the pain and how your library solves it. Would help put it in context for others trying to understand it.

@CAYdenberg CAYdenberg added the documentation Improvements or additions to documentation label Sep 27, 2021
@CAYdenberg
Copy link
Owner

Got it. Good feedback. Thanks for the advice.

@CAYdenberg
Copy link
Owner

I rewrote the Motivation section completely: any chance you could tell if this is an improvement @MarkBennett ?

Why?

I've worked with a few great, battle-tested React data-vis libraries, including Formidable, Nivo and React-Vis. While these are often enough to produce beautiful charts with very few lines of code, they have limitations when attempting to integrate with more complicated data-centered apps.

Some of the things I struggled with were:

  • applying responsive design principles to alter text or visual design depending on screen size
  • rescaling axes in response to user interaction or container size
  • supporting non-mouse events that modern users tend to expect, like swipe and pinch gestures
  • seemlessly interconverting between SVG (server-side rendering!) and canvas (animations! performance!)
  • using component-centric engineering to mix chart types or creates new types

Hypocube introduces a layer of indirection between the "data", as mapped on a Cartesian plane, and the "design", authored in units of pixels. A base Chart component manages the scaling and passes it down via context. Hypocube uses several parts of d3 to manipulate drawing instructions, but takes a React-based approach to managing the DOM - and the canvas context.

@MarkBennett
Copy link
Author

That looks way better Casey! My only suggestion would be to try to summarize it in a quick sentance at the top of the page. You'll probably want to do this in your own words, but something short and sweet like:

"Performant, responsive and powerful data visualization for your React applications"

@CAYdenberg
Copy link
Owner

OK.

Thanks so much for all your help with this 👍

@CAYdenberg CAYdenberg reopened this Sep 28, 2021
@CAYdenberg CAYdenberg changed the title Frame your solution in terms of a pain your solving Consider rewriting the hero text/project "tagline" Sep 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants