Block Labels 🔖, Read-Only Docs 📝😍 and More
Last week we added a bunch of features to make your life a little easier!
You are shaping Forestry every day with your feedback and this is exactly what happened with this improvement. You made us aware that Blocks can get hard to navigate when you add the same Block multiple times. To make this easier you can now add a display_field to label your Blocks.
We believe the best way to explain intricate settings or features is documentation right at your fingertips.
Create In-App Documentation For Content Editors
Say you’re writing some code and you hit a road block: what was the name of that method again? Which parameters do I need to send in this API request? What does this error message mean? At times like this, developers reach for the documentation. Ideally, this documentation is close at hand in order to minimize the interruption to your coding flow.
Forestry’s content editor plays an interesting role in the creation of static sites.
Migrating to Key-based Authentication
Head’s up! We’re making some changes to how Forestry authenticates with your Git repos.
Today, we rolled out an update that uses persistent SSH keys to interact with your repo. Previously, we were relying on OAuth tokens to gain access as needed, but some users were encountering problems with this method as tokens would intermittently expire before they could be refreshed. Using long-lived SSH credentials is intended to solve this problem.
In Search of the Best Continuous Deployment Service
We’ve written before about the advantages of automated deployment, particularly for static sites. Continuous Integration and Continuous Deployment are a ubiquitous strategy for managing the release of software. There are several options out there for running your CI/CD pipelines, with their own strengths and weaknesses. Which one should you use? In this article, we will look at 5 different services that you can use to build, test, and deploy your code.
Keeping Content DRY: Data Relationships In Hugo
Don’t Repeat Yourself is the perennial mantra of the software developer. It doesn’t mean you should never do the same thing twice, but instead refers to having a single, authoritative source of truth for every piece of information used in your software.
Don’t Repeat Yourself is frequently applied to code, where knowledge is susceptible to duplication through the copying and pasting of code blocks where an abstraction should be used instead.
VuePress Brings Your Documentation to Life
VuePress has the flexibility to build any static site, but it particularly excels at working with documentation. In this article, I’ll show you how to adapt your docs to VuePress for documentation that survives on Github, but thrives on its own.
Support for VuePress [Beta]
VuePress support is here! 🎉🎉🎉
Support for Static Site Generators (SSGs), beyond Jekyll and Hugo, was on our roadmap for a while now. In fact, Jordan mentioned adding other SSGs to Forestry back when our first beta was leaked on Producthunt two years ago.
Why did you make us wait? We love to create a great content management experience and make an app that is as easy-to-use for developers as it is for editors.
Creating a Multilingual Blog With Jekyll
Reaching an international audience means having international content. Having your content available in multiple languages is great for maximizing your potential audience. On top of that, ensuring your multilingual site’s content is easy to edit is especially important, to enable translators without development experience to work effectively and reduce the incidence of translation errors.
In this post, I will explore how to set up a Jekyll site to support multiple languages, and use Forestry to provide an interface for creating translations.
Snippets, Custom Content Sections and More
I’m happy to announce some new features today! ☀️
Long awaited, our Snippets feature is finally here. Our Hugo users felt especially strong about using Hugo’s powerful Shortcodes feature in Forestry. You can now add HTML snippets to your Markdown Editor whether you’re using Hugo or Jekyll.
Moreover, the team has continued to improve the sidebar. We added advanced configuration of content sections so you can control the structure of your content in Forestry.
Why We Created a Git-Backed Content Manager
Software developers have long used Version Control Systems for tracking changes to code. Any code project will benefit greatly from using version control, and any developer worth her salt should be wary of a codebase that does not use version control. Version control makes it easy to monitor changes to code, track down bugs, and manage releases.
Forestry’s content manager is supported by Git, one of the most popular version control systems available today.