April 2017 Summaries

The author, Brian Douglas, the founder of OpenSauced, recently implemented search functionality on his website using Algolia's DocSearch solution. The integration was relatively straightforward and quick to implement, with minimal issues requiring swift resolutions from the community and support team. Brian praises Algolia for its simplicity, ease of use, and open-source nature, recommending it as a go-to solution for search needs. He also notes that Netlify CMS is now onboard with other popular projects like React and Stripe, which utilize DocSearch for their search functionality.

Netlify CMS is an open-source solution that helps bloggers stay consistent with their content creation by providing a streamlined blog setup and integration with GitHub as a backend, which integrates directly with Netlify's Authentication Provider feature. To set up Netlify CMS on a Middleman blog, you need to create an admin folder in the public folder, add an index.html file and a config.yml file, and configure the collections and fields for the CMS. The CMS allows users to create, edit, and update posts via their web browser, and automatically makes GitHub commits when saving a post, which can be ideal for continuous deployment from GitHub to Netlify. Additionally, Netlify CMS offers features such as creating an editorial workflow that creates a Pull Request to view content changes and preview on a deploy preview.

The use of `resolvePromiseProperties` allows developers to create cleaner, more readable code when working with REST APIs that return data from multiple endpoints. By utilizing this function, developers can easily manage promises and avoid unnecessary mutations, parallelize promise execution where possible, and simplify object construction. This is particularly useful in scenarios where API responses have varying shapes or require asynchronous processing. The implementation of `resolvePromiseProperties` is straightforward, leveraging `zipObject` from Lodash to zip the resulting object back together, making it an efficient solution for handling groups of related promises.

In this episode of JAMstack Radio, host Phil Hawksworth interviews Sashko Stubailo and Jonas Helfer from Meteor about Apollo, a set of tools designed to simplify the use of GraphQL. They discuss the current state of the GraphQL ecosystem and its evolving toolset. Additionally, they introduce Optics, a paid service that provides server data analytics and performance insights.

Hugo 0.20 has been released, bringing a new set of features that can be easily utilized by users on Netlify, allowing them to install specific versions of Hugo without waiting for the company's update process. Previously, users had two options: wait for Netlify to install the version or manually add it to their repository. Now, users only need to set an environment variable `HUGO_VERSION` with the desired version number to use a new version on Netlify. This change also utilizes Deploy Contexts, which can be used to test with a specific version of Hugo without affecting production sites. Additionally, this update is part of Netlify's commitment to Open Source and showcases their Binrc program that automates downloading release files from GitHub.

You can password protect specific deploy previews in Netlify by using deploy contexts, which allow you to perform different behavior on selected deploys. This involves creating an _headers file that will be used only for deploy previews on specified branches, causing Basic HTTP Authentication to be enforced for the entire site in those previews. The process involves setting up a Makefile and netlify.toml file with specific commands and contexts to achieve this functionality, which can then be adapted to other tooling used by developers.

We've chosen a color palette that is simple yet effective, allowing our design work to take center stage. The simplicity of the palette ensures it gets out of the way and simplifies the overall design process. This approach also enables us to avoid overwhelming the user with too many visual elements, making it easier for them to focus on the core functionality of our redesigned user interface.

As the Support team leader at Netlify, Chris aims to create a seamless user experience by addressing corner cases and improving software usability. The goal is to provide support that's usable in seconds without requiring extensive documentation or technical expertise. With an expanding customer base, Netlify seeks another support engineer to join their team, emphasizing collaboration with designers, marketers, developers, and operations teams to ensure the service meets customers' needs. The ideal candidate should possess strong written communication skills, proficiency with networking and frontend development, and a willingness to work hard to solve problems and provide honest feedback.