Dear friends and readers:

On October 1st, 2013, I announced that JavaScript Allongé became free: It is now licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License. You are free:

• to Share—to copy, distribute and transmit the work
• to Remix—to adapt the work
• to make commercial use of the work

Read the license yourself for the full details. But the bottom line is, it’s free, free, FREE!

And don’t just take my word for it, here’s the entire book online.

Yes, you can take the HTML that is available online or the markdown source in this repository and make your own PDF. Or any other format. Please be aware that while it's technically possible to game the LeanPub system to produce the PDF or other formats, I ask you as a personal favour to find another way to make a PDF.

The license permits this choice, but IMO it is contrary to the spirit of sharing and openness to use their resources and work to do something that isn't aligned with their mission. And of course, they may not care for the idea, I don't know and I don't want to undermine what has been a tremendous service for helping people write great technical books.

Yes, please do.

Sure thing, you can send a donation via PayPal to [email protected], or click this button to donate $10 to help me write:

And I'd also like you to share it, in this form, in PDF, or anything else. Go wild, just follow the attribution rules in the license.

Go for it, you are free to make commercial use of the work. For example, you could host it on your site and make money from ads, or write a JS tool and use the book as part of the help content.

It's all good, just follow the license terms. It is technically possible to create an identical clone of the book on LeanPub. I do not prohibit this activity, but I do ask you as a personal favour to ask yourself whether you could do even better, for instance to add value by adding your own annotations, expansions, and commentary. I'd love to see an "Annotated JavaScript Allongé."

I'd also love to see translations, editions with large print, or anything else that brings something new to the world. Many people have asked for a hard-copy version. Who will be the first to set up shop on lulu.com?

Thanks, but my email inbox is a disaster zone. Let's treat the book like OSS. In order of my preference, you should:

1. Create an issue, fork the repo, fix the issue, and then send me a pull request. (Best!!)
2. Fork the repo, fix things to your satisfaction, and then send me a pull request. (Better!)
3. Create an issue. (Good.)

Thanks!