Why is my branch/site archived?
If you are using the personal plan and didn’t edit your site branch for more than three months, we will automatically archive it in order to save some precious resources on our servers.
Don’t worry site admins can always restore an archived branch in two clicks the next time your try to access it.
Click on the site or branch marked as archived and click on the Restore now button.Your branch or site is now active again.
How to manage Git branches in Forestry?
You can import as many branches as you want in Forestry, and you can set your teams permissions on each branch if you need to on our starter plan.
A site with multiple branches imported in Forestry How do I import a new branch? Click on the “Add Site” button to connect to your Git provider and pick up the branch you want to import. If this branch is a fork of another branch already configured for Forestry, given we store your settings in the repository, you won’t have to reconfigure your sections, your templates, or your preview.
Announcing Tina: an open-source site-editor
Our mission at Forestry is to help people build a better web but I often cringe when I watch someone log into their CMS for the first time. There’s a mental leap as they try to map their CMS (a collection of forms) to their site (a collection of well-designed-pages). Using a CMS feels more like filing your taxes and less like editing a website.
With our mission in mind, some people from our team have started a side-project that we’re excited to make public today, TinaCMS.
Introducing Site-based permissions and Teams
We are introducing changes to improve the way you manage collaborators on your sites.
Our previous model had a few limitations that we wanted to address:
Adding a user to an organization gave each of your members access to all organization sites. The only way to give users “developer” or “admin” permissions on a site was to make them a “developer” or “admin” across the entire organization. Guests on an individual site were restricted to “editor” permissions (No access to edit front matter templates or site settings) Site-specific access levels The available roles for users within an organizations are now “Member” or “Owner”.
Use Forestry With Azure DevOps Repos
Azure DevOps is a suite of code collaboration and deployment tools provided by Microsoft. Azure DevOps includes cloud hosting for git repositories, similar to Github, GitLab, and Bitbucket.
As of today, you can now import Azure DevOps repositories into Forestry! Forestry will sync the contents of your Azure DevOps repository by importing changes when they’re pushed to the repo, and committing content updates that you make in Forestry.
Importing Azure DevOps Repos to Forestry Our OAuth-based Quick Setup is not currently available for Azure DevOps repositories, so you must use our manual setup option when connecting to Azure DevOps.
Full Speed Ahead in 2019
We have a big update to share with you today! Today’s release marks the culmination of a lot of feature work, with one major goal in mind:
We wanna go fast.
Today, we’re launching:
Instant Previews, which will enable your previews to build faster; Git LFS support for media which will speed up Git operations on image-heavy sites; and Gatsby Support, allowing you to use Forestry with a “blazing fast” Gatsby frontend.
Announcing Image Handling with S3 🖼️ + Update Billing Contact Information 💵 and more
Happy New Year! We’re starting into 2019 with an exciting new feature.
Today we can announce support for S3 as an image storage provider for Forestry. The S3 integration makes it possible to efficiently store, organize and deliver images while keeping the editing experience in Forestry simple and clean.
Editors, marketers and writers can continue to use the Forestry Media Library without even knowing that they are using S3 in the backend.
Can I edit CSS files?
Forestry offers a friendly user interface to edit Markdown, JSON, YAML and TOML files.
Forestry is primarily meant for editors, not developers, stylesheets (CSS, Sass, Less, Stylus, etc.) and layouts are still edited through your usual developer workflow, usually locally in your favorite IDE and then pushed to your Git repository.
Forestry will automatically synch with your Git repository and restart your preview environment, so any change to layouts and styles will be reflected after you push your changes.
Data Files, Directories, and Duplicating Pages
The lumberjacks have been busy lately! Here’s what we’ve been up to:
Agnostic Data File Handling We have removed support for our old way of handling data files. Previously, we used some heuristics to automatically discover data files in your Jekyll and Hugo projects. Data files must now be manually configured by creating sections for them.
VuePress Now Out of Beta Abstracting data file discovery in our content manager has paved the way for more easily supporting other static site generators.
Introducing Custom Build Commands
We’re excited to announce Custom Build Commands! You can now decide what build command should be run for your project.
Until now Forestry chose the build command that needed to be run for you, which worked fine for most cases. However, this meant that projects that needed a custom build process were unable to use Forestry’s deployment tools and (in some cases) previews.
Picking your own commands enables you to really choose your own workflow and give you the flexibility you need.