Parting wisdom: Martin’s final tips configuring Fonto

In this weekly series, Martin describes a question that was raised by a Fonto developer, how it was resolved and why Fonto behaved like that in the first place. After a hiatus of writing, this is my last post. I decided to move on from Fonto, and I’d like to write down my final tips on how to configure Fonto best! Reload / retry performance for developers: just run it local! The number one frustration I have seen with a number of partners is the full integration of Fonto in their CMS. Every code change on the Fonto side requires the editor to be rebuilt (fdt editor build), deployed into the CMS and refreshed in the browser. The editor build takes close to a minute for big editors, and the redeploy is also not always instant.