Tina Cloud, the next iteration of Forestry
Over the past 14 months, we’ve been hard at work building the next iteration of Forestry CMS, Tina Cloud. We’re launching soon a public beta for Tina Cloud and are initially focused on a narrow use case to refine some UI/UX work before expanding the beta to a larger audience. This narrow use-case will target React-based sites, preferably using Next.js.
Tina Cloud Tina Cloud is a headless API backend that talks to your Git repository, much like Forestry but with an open-source GraphQL API.
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.
Forestry.io at Jamstack Conf - San Francisco, Oct 16-18
I’m excited to be speaking at Jamstack Conf in San Francisco on Oct 16th. I’ll be speaking about the future of content management and announcing an open-source project that we’re really excited about.
The inaugural event was a blast last year and it sounds like they’re taking it to the next level this year.
If you’re attending this year, make sure you pop by our booth and say hi! I hope to see you there!
Full Text Searching with Postgres
At Forestry, we use Postgres as our primary data store. In this article I’ll show you how we used tsvectorto improve searching for documents in the CMS.
The tsvector Type Postgres has a data type called tsvector that is used for full text search. A tsvector value merges different variants of the same word and removes duplicates to create a sorted list of distinct words called lexemes.
SELECT to_tsvector('pg_catalog.english', 'Never gonna give you up.
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.
Gulp and Webpack: Getting the Best of Both Worlds
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.
Versioning Large Files with Git LFS
I’ve written before about the advantages of keeping content in version control. A quick recap of the benefits:
Content is portable - just git clone Full content history is available; can rollback changes and recover earlier revisions Content updates can take advantage of the same workflows popular with code: pull request→review→merge While the benefits are significant, one of the major pain points of this solution arises when large non-text files are introduced to your content.
How I reduced my Jekyll build time by 61%
At the time of writing, Jekyll’s performance is still actively being worked on by the Core Team for an upcoming version 4 release. One of the main complaints about Jekyll for users is often the build times of larger websites. I want to take this opportunity to see just how much I can expect to improve my current site’s build times by using the latest master branch.
Sound good? Let’s get started.