-
Notifications
You must be signed in to change notification settings - Fork 42
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
Make a Mad Dash #1
Comments
Thanks for that, @Smolations. I haven't used Dash before, but it looks like there already exists a d3.js doc set. Have you tried that out? If so, can you help me understand the benefit to making an alternate D3 package for Dash? Thanks! |
Sure! Dash has two main types of documentation: docsets and cheatsheets. Docsets are the FULL documentation for all methods, etc. that is usually found on the software website. Cheat sheets are, well, I think you know. =] I was requesting specifically to add the cheat sheet to the list of user-contributed cheat sheets. It's way less work than adding a full docset, I assure you. 😆 |
Ah, thanks. I will look into this. I'm in the process of revising my book for a 2nd edition, and it could make sense to release a Dash-ified version of the cheat sheet as part of that code package. |
Awesome, thanks for your consideration! 👍 |
@Smolations Have you seen this? |
@alignedleft I have not, but it doesn't quite solve my problem either. While it may have docsets Dash is missing, it shares much of the documentation Dash provides. For me, the two main reasons to purchase Dash were:
I do appreciate the suggestion, though! 😄 |
@Smolations Yes, of course! I was just thinking it could be a nice alternative (for different contexts, perhaps). |
Your d3 cheat sheet is fantastic! This issue is not a bug, but rather a feature request. Almost all of the devs at my company use Dash to reference documentation during development. It would be awesome if you provided your cheat sheet as a user-contributed docset for that piece of software. I know it would help me out quite a bit!
😄
The text was updated successfully, but these errors were encountered: