-
Notifications
You must be signed in to change notification settings - Fork 48
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
Write first few levels of each target area #1
Comments
@openspectrum Feel free to put your initial before any of the not-yet-checked off sections. |
@zspencer thanks! I claimed several, keep tagging them as we go. Do you have a sample that I can use as a template? I'd like to keep my structure as close to yours, if possible. |
@openspectrum template here: #2 |
@zspencer when you use the language of "publish" and "subscribe" (under Events and Callbacks), do you literally mean a publish/subscribe system like RSS, or are you using those terms as synonyms for event "firing" and "listening"? I just want to be sure that I understand your intention, know what the scope of these exercises are, and use the best language for them. |
Publish is synonymous with fire/trigger here and Subscribe is synoymous with listen. |
Ok so we can put DOM manipulation stuff in "Interacting with the User". What about exercises that deal with state management? Like modals, animations, etc. Does that belong in Events & Callbacks? |
Syntax and Idioms
{ }
, Hugs( )
, and Full Stops;
Algorithms and Computer Science
Events and Callbacks
this
Interacting with the User
The text was updated successfully, but these errors were encountered: