Continuous Integration (CI) Continuous Integration (CI) is a development practice where developers check-in code to a version control tool multiple times per day. Each time code is checked-in, an automated build is performed, allowing developers to identify problems with code quickly.
Continuous Delivery (CD) Continuous Delivery (CD) is a development practice where developers produce software in short cycles, ensuring that software can be easily released at any time. This ensures that developers are producing quality code and are identifying problems quickly.
Content files are files that are processed by your static site generator and output in a different format (usually .html).
They are usually Markdown files (.md, .markdown) or HTML files (.html).
Front matter is structured metadata that is stored at the top of a content file, and is identified by delimiters before and after the metadata.
This metadata is available to your templates when generating your site, and allows you to build robust, dynamic features into your static site.
Depending your static site generator, Front Matter can be formatted as YAML, TOML, or JSON.
Examples YAML — title: My New Post date: 2018-07-01 04:00:00 +0000 images: - /uploads/2018/07/01/twitter_card.
How do I backup my site?
For developers, backups are inherent due to the Git-backed nature of Forestry. Every change made to your site through Forestry is stored in version control.
However, a zip backup of your site can be downloaded from the dashboard if necessary.
Steps Navigate to the dashboard Click the … button beside the site you wish to download a backup of Choose “Download” from the menu
How do I set fallback/hidden values for Front Matter?
Adding Front Matter to your content allows you to add variables and configuration to your pages that can be used in your templates.
Often times, you will find that you are repeating the same front matter values across many files. For example, setting the same layout, or adding the same author across many posts.
Or you may want to provide a default value for optional fields.
In this scenario, it’s possible to provide a fallback or hidden value.
Static files are files that are not processed by your static site generator. Instead, they are just copied over as-is at built time.
Examples Jekyll: in Jekyll, this is any file without front matter. Hugo: in Hugo, this is any file in the staticDir, which defaults to static/
Static Site Generators
Static Site Generators are developer tools that convert various data formats into static sites.
These data formats are generally content files stored in a Git repository. They can also be data pulled from third-party services.
Examples Jekyll is the static site generator written in Ruby and created by GitHub founder, Tom Preston Werner. Hugo is the static site generator written in GoLang and created by Steve Francia.
Static sites are websites built using static, unchanging files. They require no server processing time to deliver the content to the user, which makes them very fast and performant.
Static site generators are the modern way of building static sites. They convert simple, text-based content files in static files ready for the web.
They’re fantastic for developers because they are extremely fast, are built to work with version-control, and require little-to-no setup compared to existing monolithic CMS solutions like Wordpress.
What versions of Hugo do you support?
We strive to always supports the previous 3 major versions of Hugo with their latest patch. (e.g, x.3.x, x.2.x, x.1.x).
Backwards compatibility is always available for sites using an older version of Hugo that was supported when the site was added to Forestry.
Note: Forestry does not provide immediate support for Hugo releases.
Other Software We also support the following software that is supported by Hugo:
asciidoc asciidoctor pandoc
What versions of Jekyll do you support?
Forestry will use whatever version of Jekyll is specified in your Gemfile.
If you don’t specify a version in your Gemfile, Forestry will use the default version used by GitHub Pages.
Defaults These are the ruby gems that Forestry will bundle with your build by default, without the need for a Gemfile. Forestry also lets you specify different versions of gems by including a Gemfile with your site.