For this article, I am assuming you already have Jekyll installed, with a project set up on your local machine to generate your static site's HTML files under your build directory of choice.

I am now using StatusCake for uptime checks and monitoring, after trying it for the ContentGardening.com site.

Monitoring is important these days, to help you improve the response time of your web apps, and give you insights on how they are used. Subscription-based services lower the barrier of entry by not requiring you to install and manage your own monitoring infrastructure. And they are generally free for developers.

I started structuring my projects to get the power and productivity benefits of tools such as Bower, which help you install and manage the static assets libraries for a web project in an automatic and centralized way.

In this series, I tried to give you an idea of using new tools and platforms such as Divshot for static sites hosting. I almost procrastinated, but finally kicked myself to deliver this third part, where I quickly present other cool services Divshot provides to make our hosting tasks easy.

Part 1 of this series introduced static apps deployment using the DivShot hosting service. In this 2nd article, let's see how to go further with automated continuous deployments. The solution I've decided to use for this is Wercker, combined with Github and DivShot. As an alternative to Wercker, one could choose Travis CI, though I've not tested it yet.

Divshot is a specialized hosting service for modern apps, in particular apps developped the static way, and I decided to use it for all my current projects that fit this category. Check out their list of features here.

Jekyll is not easy to install on Windows. Here is a work-in-progress howto on installing Jekyll on Windows, based on the documentation put together by Julian Thilo.

Here is how I install Jekyll on my Mac, which should be mostly applicable to a Linux box. Jekyll is currently available in version 2.5.2, but I also previously tested this procedure for 2.4.0.

So much to do and only so many hours in a day! If this is where you're at, you're not alone.

I work on projects using Plone, and I love working with its framework. I just worked an hour for my current project, and once again I enjoyed the fact that I can write stuff in a clean way. I can expose logic or behavior where and how I want it, using interfaces and components mechanisms provided by Zope libraries under the hood. It's got even better now that we have an elegant API.

There are many new methods for deploying web applications in a predictable way, fast, and while having fun. You might forget about system administration, database administion tasks, security updates, etc, if you get used to this.