Updating Continue to match changes in web dev practice

[spdegabrielle]

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

[spdegabrielle]

Another possibility; custom #lang's or eDSL's to support the above by either highlighting existing languages or creating new ones.

[spdegabrielle]

@sorawee @greghendershott @jeapostrophe @jbclements @mbutterick - I CC you all because you all had valuable input on the other Continue issue.

[spdegabrielle]

sorry forgot to include @bennn

[euhmeuh]

That a very good idea. I have plans for that because that's exactly what I'm trying to add with https://github.com/euhmeuh/web-galaxy and https://github.com/soegaard/urlang.
As I explore the ways you can implement features such as authentication, CSRF, javascript generation... I'm building up some notes and I'll try to put them together and make a tutorial out of it.

If anyone has experience with building up modern websites with racket/web-server, please share your methods 😉

I'd be glad to contribute to Continue when I have substantial material.