Having a short Jekyll build time helps you iterate faster while developing and goes a long way to improving the experience for editors on CloudCannon. In this post, we’re going over how to identify bottlenecks in your Jekyll build and tips on how to address them.
Our main goal at CloudCannon is to make collaboration between developers and non-technical editors seamless. To an extent we’ve achieved this with editing a Jekyll site; editors can update HTML, Markdown, front matter, blog posts, collections and data files without knowing anything about Jekyll or HTML but what about Git? Recently we’ve been working to achieve the same level of integration for Git workflows. In this post I’m going over some of the new workflows CloudCannon supports.
Today we are announcing a big improvement to the way teams use CloudCannon. We have updated our pricing to be more team friendly and a simpler structure to get you going faster. Additionally, we have added Organisations which allows greater team management, branding and data sharing.
It’s great to see the different ways people are using the Jekyll templates we launched late last year. To continue this success, we’ve put together three new templates ready for your next site. These are licensed under MIT to feel free to use them on client/commercial projects.
Social share buttons are commonplace on a range of websites. Many social networks provide embed code to build them quickly, however these solutions load a number of additional requests and resources. This increases the load time for your pages.