Why static rendering?
There are two main reasons to use the feature. One or both may apply to you — or you may have other reasons. 1. Performance There is a simple reason why a site that’s been rendered to disk will often load faster than the Manila version. In a static site, the pages have been pre-built. In Manila, pages are built on the fly, for every request. This means a static server is doing much less work than a Manila server: all it has to do is read a file and return the contents to the browser. Latency — the time it takes before the server starts returning data to the browser — is thus lower. 2. Staging You may want a private and a public site. You can use the Manila site as your private site and the static site as your public site. When a page is ready to “go live” — when it’s ready to be rendered to the static server — you can tell Manila to render the page. This allows you to iterate over your copy without making all your edits public. You can create a new page and edit it until it’s the
