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 signficant, one of the major pain points of this solution arises when large non-text files are introduced to your content.
Is it Time to Move on From WordPress?
WordPress 5.0 has been released, and with it comes their much-hyped new editing experience, Gutenberg. The inclusion of Gutenberg in this release has caused no shortage of acrimony in the WordPress community. The new editor is opt-out as opposed to opt-in (and opting out requires installing yet another plugin), and is such a significant departure from their original content editor that it is guaranteed to cause major issues with third-party plugins and themes (Gutenberg, for example, does not support WordPress’ meta box API, an essential component of customizing the current editing interface used by countless plugins.
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.
An Introduction to Theming in VuePress
When I first looked at VuePress, I marveled at how quickly you could install it alongside your project’s existing markdown docs to create a polished documentation website. This is without a doubt one of VuePress’ biggest strengths, but documentation is not the only thing it can do. VuePress is a highly flexible static site generator, and provides the ability to completely customize the way your pages are built via its Layout component.
Demystifying Hugo Conditionals
When we published our comparison of Jekyll and Hugo, we got a lot of flak from Hugo die-hards for suggesting that Jekyll had a more intuitive templating syntax. While the intuitiveness of a particular language is somewhat subjective, criticism of Hugo’s template syntax frequently comes up in discussion with other developers.
Hugo is a great choice for a static site generator: it’s compiled into a static binary, so it’s easy to install on any system, and it’s fast.
Using JSON Configuration With VuePress
Here at Forestry, we think VuePress is pretty cool. When it came time to set our sights on supporting SSGs beyond Hugo and Jekyll, we selected VuePress as our guinea pig. Our adoption of VuePress has helped to highlight the differences among the variety of Static Site Generators, and move us in a direction that will enable users of SSGs beyond Hugo and Jekyll to take advantage of Forestry’s content manager.
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.