Open navClose nav

The Forestry Blog

Welcome to the Forestry blog! Read up on news regarding our product and the JAMStack!

3 Tips for Mastering Blocks

Last week, we brought you a theme for Jekyll that takes advantage of Forestry’s Blocks feature to build whole page layouts using modular components, called uBuild. This week, I ported uBuild to Hugo to make it available to our Hugo users. When we first announced the Blocks feature, I created a Hugo theme called Sawmill to demonstrate the Blocks’ page-building capabilities. Since creating that theme, I’ve been using Blocks extensively and have learned a lot about how to use this feature effectively.

uBuild: A New Jekyll Theme Using Blocks

Back in April we announced a feature that we believed was a game-changer for static site content managers. Blocks was here to introduce a way for you to put together sites using pre-composed site snippets inside Forestry. While we did our best to show you how to set them up and give you an idea of how powerful they could be, we noticed that getting to know Blocks and figuring out how to set them up from scratch wasn’t as self-explanatory as we had hoped.

Hugo Support for All Versions, Sorting for Pages and more

We just made a big change to how we handle Hugo projects and introduced a few new features that make it easier to stay organized. Hugo Support for All Versions 🔥🔥🔥 Hugo has a great developer community that is constantly pushing new versions out. Until now you sometimes had to wait a few months until you were able to use the latest version of Hugo with Forestry as we were trying to catch up.

5 Ways to Handle Forms on Your Static Site

When I first started exploring the potential of static sites, I was attracted by their speed and simplicity. I knew these benefits came at a cost, however: since static sites can’t run backend code, there are limits to what you can accomplish with a static solution. I no longer see things this way. JAMStack is not about sacrificing features for the sake of a performant, easy to maintain website. Rather, it is about re-evaluating how much of your desired functionality should be delegated to your web frontend.

Renaming Files and Improving Editing in a Team

It’s a cloudy day ☁️ here on Prince Edward Island, the perfect opportunity to announce some new features. Over the past couple weeks, we were hard at work to improve the editor experience for our Git-backed content manager. Renaming files is just one of those updates. We also needed to improve notifications and indicators to make working in a team on Forestry easier. Renaming Files ✍️ Freshly out — you can now change the name for your content files with Forestry.

For Static Sites, There’s No Excuse Not to Use a CDN

Are you getting the most out of your static site? If you’re not hosting your site on a CDN, you definitely aren’t. CDNs, or Content Delivery Networks, are commonly used to distribute static resources like images, videos, and client-side code (CSS and JavaScript.) Since a static site is composed entirely of static resources (including the HTML pages,) it is possible to serve the entire website through a CDN! In this article, we will explore why you should be using a CDN to host your static site, and how you can do it with Netlify.

Mastering Image Delivery With Cloudinary

Applying a responsive strategy for displaying images means more than just adding max-width: 100%; to your image tags. You don’t want to display an image that is much larger than the area it occupies, otherwise you’re just wasting bits. You need to deliver scaled-down versions of these images where appropriate. A popular way to generate these scaled-down assets is to automatically resize our images during the build process, using something like a gulp task, but that solution isn’t perfect.

Cloudinary Integration, Data File Templates and Other Features

Image Transformation and Responsive Image Delivery Today we’re proud to announce an easy way to optimize your image delivery with a Cloudinary integration for Forestry. As a developer you can now use the super fast Cloudinary CDN and store your assets outside your repository. While at the same time your editors can use Forestry’s Media Library and Editor to upload and manage Cloudinary assets without even knowing it. It’s as simple as adding your cloud name, API key and secret to your site’s settings to get started.

Enhance Your Hugo JSON API Using Custom Output Formats and Netlify Redirects

Hugo makes it super easy to build simple APIs with its built-in output formats. In my previous article, we built a fully functional JSON API. Today we’re going to extend the capabilities of this API and improve the user experience with better URLs. At the moment our API can look up specific items, but can’t look at them in relation to each other. Say you want to know what players are in a specific team: with our current API, you can’t do that easily.

How To Use Hugo's Image Processing With Forestry

0.32 update introduced built-in image processing for certain assets. One limitation of this feature is that it only works for page resources, which are page-relative assets stored alongside your posts in the content/ directory of your site. Since Forestry’s uploads are stored in the static/uploads/ directory by default, these assets cannot be resized in your templates using Hugo’s built-in resizer. This document will provide a step-by-step guide for working around this limitation.