-
Notifications
You must be signed in to change notification settings - Fork 480
JS101 Improvements #58
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
Labels
Comments
Amen brother. Please rock out to your heart's content and I'll be happy to look at anything you come up with. |
I volunteer to review for this... let it rip. |
@adrocknaphobia has also been doing some work in this area, and @rwldrn we'll definitely be happy to have your help to once we've got this freshened up |
You know where to ping me ;) |
Made some updates to 2/3 pages. Find my Pull Request here: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
From a high-level, this is good since code can (sometimes) communicate quicker and more directly than words explaining that code. However, it feels like a lot of the sections in JavaScript101 could use some supporting text (and page structure - to make it more palatable, like
<h3>
's, paragraph breaks, etc...). The ones in particular are:What are people's thoughts on stuff like this? Should we use more text to explain it? I think so, but would love some other opinions (esp those on the jQuery team).
If you all agree, I'd be happy to rock out first versions of revisions.
The text was updated successfully, but these errors were encountered: