Serverless Deployment Best Practices (Serverless)
Structured practices for deploying your applications will minimize bugs, maintain application security, and allow you to develop more rapidly. This post will review a variety of serverless deployment best practices as the complexity and scope of your serverless applications grow.

faastRuby: The next chapter (faastRuby)
Sadly, faastRuby has passed away. Here is a post explaining what happened - and how you can move on - both emotionally and with your code.

Workers Sites: Extending the Workers platform with our own serverless building blocks (Cloudflare blog)
You can now deploy entire websites directly to Cloudflare Workers and Workers KV. If you can statically generate the assets for your site - think create-react-app, Jekyll, or even the WP2Static plugin - then you can deploy it to our entire global network, which spans 194 cities in more than 90 countries.

Choosing between serverless and containers (SD Times)
Serverless works very well in small, discrete tasks, or large applications that are made up of small, discrete parts. Containers come in when there are more complex requirements, you need access to a lot of data, or when developers are writing in a language that serverless platforms don’t support yet.

GitCF – A RawGit-Like Service Running on Cloudflare Workers (GitHub)
GitCF is a service that is similar to RawGit, but running on Cloudflare Workers. The GitHub repo is linked above, and you can paste the script to Workers editor to get your own instance. Here’s a link to the demo.