Sawmill: A Razor-sharp Layout Composer for Hugo and Forestry
When it comes to creating websites, good content strategy is all about turning ideas into HTML with a minimal amount of friction. Whether using a CMS with a web interface or editing content files for a static site generator, content creators need an easy way to create visually interesting and well-structured content.
Every approach is a compromise between flexibility and ease-of-use. Even if a developer could anticipate all of a content creator’s needs, these needs will change over time.
Blocks - Give Your Editors the Power to Build Pages
Today we introduce Blocks - a powerful Field Type that enables your editors to build entire landing pages from scratch and create rich blog post layouts with a pre-defined code template, we call it a Block Template.
This feature was inspired by CraftCMS’ Matrix fields and the Wordpress Plugin Advanced Custom Fields.
What is Blocks? Blocks is a Field Type that is made up of multiple templates, so-called Block Templates.
HTML File Contents are Moving to Plaintext Editor
We are not changing or removing the Markdown WYSIWYG editor. Our Markdown editor will continue to offer both plaintext and WYSIWYG input modes. In fact, removing the HTML WYSIWYG editor will allow us to focus on making the Markdown editor even better.
The HTML WYSIWYG Editor has proven to be less and less the state-of-the-art content editing experience it once set out to be. Considering the issues the HTML WYSIWYG Editor causes and the merits Markdown provides we made the decision to discontinue our WYSIWYG HTML Editor on 5/11/2018.
Build a JSON API With Hugo's Custom Output Formats
As developers, we love open and accessible data. For example, you may want to use your local transit data for a mobile app, or maybe you want a service like Zapier or IFTTT to send you an email every time the weather forecast calls for rain. If you’re a super geek like @bdougieyo, you’ve built an app that tells you when to leave work in order to avoid traffic from your local baseball team’s home games (from his excellent talk here).
Hugo or Jekyll? 6 Factors You Should Know
Choosing the right tools to build a website isn’t easy these days. There’s just too many options! Building a static site is one of these options, which comes with many advantages like top-notch security, blazingly-fast performance, and reduced costs.
When it comes to building static sites, the two leading solutions right now are Hugo and Jekyll. So the question is, which is right for you?
To answer that question, we’ll take a look at the features, speed, and extensibility of each, looking for the pros and the cons of both generators.
CircleCI Followup: Deploying Via rsync
This tutorial was updated on April 3, 2018.
In last week’s article, we showed you how to automate the deployment of a Hugo site using CircleCI. The example we provided used the awscli utility to deploy the results of your build process to an AWS S3 bucket. In this follow-up, we will show you how to use the rsync utility to deploy your site to any rsync-enabled server.
We’re excited to announce new pricing!
Now, the Personal plan supports unlimited sites and up to 3 free Guest users per site (a “Guest” is a single-site user with limited permissions, similar to an “editor”). The Business plan also supports unlimited sites, but is designed for larger teams who need to manage many users across their sites and branches. Finally, our Enterprise plan is designed for large organizations with special requirements.
Automate Your Static Site Deployment with CircleCI
This tutorial was updated on April 3, 2018 to use bep/s3deploy in place of aws/aws-cli.
This article is part of our on-going Frontend Friday modern web development series
Tools like Hugo, Jekyll, and Gatsby have made building static sites a popular and practical choice for developers. One major disadvantage these tools have, however, is the need to regenerate and redeploy their files every time there is new content to publish.
Up & Running With Hugo, Part 2: Setting up GitHub & Forestry (CI & CD)
This guide was most recently updated on March 16, 2018.
— – For this week on Frontend Friday, we have a follow up to Up & Running With Hugo, Part 1: Building Your First Site. This week, we cover integrating your repository with GitHub, and setting up continuous integration and continuous deployment with Forestry.io and some other handy tools.
Table of Contents Introduction Setting up Git Setting up Continuous Integration Setting up Continuous Deployment with Forestry Next Steps 1) Introduction Before we continue, you might be asking What is CI & CD.