-
Notifications
You must be signed in to change notification settings - Fork 35
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
Replace chapter 4 with gists, blocks and blockbuilder #42
Comments
Note that one sad consequence of this choice is that we would lose the possibility to use alert() in the examples, at least with blockbuilder. |
Hm - interesting idea! I'm personally a big fan of making everyone putting their things online. I also think it's fantastic seeing that you are able to create a webpage and put it online within a day! I haven't really used gists. How would that work? And how does the integration into bl.ocks work? Loosing alerts is a little bit sad.. it seems people really enjoy them on their first toy pages (although I encourage them to quickly move on from alerts after ;)) |
blocks are just a way to display gists directly in the browser ; it was blockbuilder is a website that displays blocks/gists, but also enables to Limitations are:
As both blocks and blockbuilder use github gists as their file backend, -- Fil |
Learning git seems to be too much load for this lesson.
It's probably an easier path to learn to create gists, and you'll have covered half the way to properly using Github.
With gists we get access to the d3 ecosystem of bl.ocks.org and blockbuilder.
Also it takes some pressure off “publishing”, just because it looks more like “playground”. We can even start with anonymous gists!
The text was updated successfully, but these errors were encountered: