Very interesting , I always wonder how you can combine those two together.��
Really nice I now see the teapot stuff, for example this
GET: 'demo/common/style.css' -> [ self styleCss ];
is really flexible meaning you can interpret http addresses and map them to pharo methods. This a really cool idea indeed, I see now why people are excited about teapot. Excuse my ignorance about web development but html/css and js always scared me away :D
If its that simple I am definetly going to use this for my website with pharo as backend as you did with this example.
Loads of potential here. Thanks for this tutorial.��