Updating Continue to match changes in web dev practice
Nobody has claimed this yet.
- Dominant language
- Racket
- Stars
- 99
- Forks
- 48
- PR merge metrics
- No merged PRs in 30d
Description
I think that Continue, as a flagship tutorial for Racket, needs new sections to cover changes in web development practice especially supporting client side web frameworks(angular,Ember,Vue,React) by building backends that support XMLHttpRequest/WebSockets/Fetch. Other possibilities include
- developing with client side racket (RacketScript, Urlang, Whalesong?)
- authentication (both doing it yourself, or using OpenID to)
- creating and accessing web API's like AWS, twitter etc.
I think the best way to do this would be to develop a tutorial in the style of Continue, then it could be linked from, or integrated into the Continue tutorial.
Any thoughts? Is this a good or bad idea? Would it be better to focus community effort elsewhere?
Kind regards,
Stephen
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing Continue tutorial and comparing it with the proposed topics: client-side frameworks, XMLHttpRequest/WebSockets/Fetch, client-side Racket, authentication, and web APIs. Done would require an agreed scope and a tutorial in the Continue style that is either linked from or integrated into Continue.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, web-dev
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100