-
Notifications
You must be signed in to change notification settings - Fork 597
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
add, like, all the docs #11
Comments
Needs more docs about forms too. See #18 and: https://developer.mozilla.org/en-US/docs/Web/API/HTMLFormElement/elements |
We should merge efforts with the rest of the TCBY stack as per max-mapper/yo-yo#25 (comment) |
Feel that with the handbook out there we can probs close this ✨ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The rest is already documented
Building browser applications is rough. People talk about all these fancy techs but rarely provide examples on how to do things well. Even stuff like HTTP requests is often treated like: "nah mate, figure it out yourself". I would quite like to have all common cases explained, so people can create a mental model of how things work. Most of it doesn't include extending the
choo
api, but rather provide examples of how it can work together with the native browser APIs, and where needed provide suggestions for packages that make dealing with it easier.The text was updated successfully, but these errors were encountered: