October 2015 Summaries

Netlify now offers detailed control over post-processing, allowing users to customize their static sites' performance and functionality. Users can disable post processing for sites that prioritize HTML/CSS sharing over performance enhancements. The feature also enables control over Pretty URLs, bundling, minification of CSS and JavaScript, and lossless image compressions. These features are available on Netlify's paid plans, with support team assistance available for any questions or concerns.

With our new domain alias feature, you can easily point several domains or subdomain to the same site. This feature allows for flexibility in handling multiple domains that need to resolve to the same website, whereas most static hosts can only handle one domain per website. Additionally, Netlify's flexible rewrite rules enable different subdomains to be handled as folders within the same site, providing more control and customization options.

Hi there. Hope you are having a great week. We've got lot's of big news so we will get right to it! Prerendering is the answer to SEO concerns for single page apps not behind login, and Netlify has built-in this feature now. If using a plan that supports prerendering, just check the "Prerender" checkbox from site settings and save. Prerendered pages are cached for 24 hours. Our open source build image now comes with a small build script to test builds locally under exact same conditions as on build machines. Netlify's domain alias feature allows multiple domains or subdomains to resolve to the same website, with flexible rewrite rules to handle different subdomains as folders within the same site.

This guide provides a step-by-step tutorial on how to host a Jekyll project on Netlify, including setting up continuous deployment. To start, users need to have Ruby and RubyGems installed, and then install Jekyll using the `gem install` command. Next, they create a new Jekyll project using `jekyll new`, and prepare their project for GitHub by listing files, confirming Gemfile versions, and adding a `.gitignore` file. Once the project is pushed to GitHub, users connect it to Netlify by authorizing access and selecting the repository. They then configure settings, build their site, and wait for Netlify to deploy it. The guide assumes Jekyll 4.0.0 and Ruby 2.7.0 versions, but notes that screenshots may be outdated.

Installing Brunch globally on your system, which you need to make sure Brunch has access to the proper dependencies, is done using the `npm install -g brunch` command. Additionally, installing bower at this step as well is recommended to avoid problems later on. A new Brunchnetlify directory is created with all necessary assets for development in Brunch. The project can be initialized and committed to a Git repository such as GitHub. To connect the site to Netlify, you need to link your GitHub repository to Netlify, authorize Netlify to access your GitHub account, select the correct repository, configure settings, build the site, and finally, deploy it to production with a custom domain. Throughout this process, Brunch's continuous deployment feature is utilized, allowing for seamless updates without manual intervention.

This guide provides a step-by-step tutorial on creating a static website using Hexo, a popular static site generator, and hosting it with Netlify. The process begins by setting up the local repository, initializing Git, adding files, committing changes, and pushing them to GitHub. Next, the user connects their GitHub repository to Netlify, authorizes access, selects the repository, configures settings, builds the site, and deploys it to a custom domain. Throughout the tutorial, screenshots are provided to illustrate each step of the process, making it easy for beginners to follow along.

We just made Netlify’s redirect engine smarter. Now, when a user tries to access a URL with multiple redirects in a chain, the redirect engine will automatically flatten it into one efficient rule, eliminating unnecessary roundtrips and reducing latency. This change ensures that users are redirected directly to their intended destination without experiencing intermediate redirects, resulting in a faster and more seamless experience. The update also benefits from being executed on Netlify's CDN nodes, minimizing extra roundtrip times and ensuring low latency for users.

To host a website built with Roots on Netlify, start by installing Roots globally using `npm install roots -g`, then create a new project using `roots new rootsnetlify`. Initialize a local Git repository and link it to GitHub. Then, connect your GitHub repository to Netlify by clicking "Link to GitHub" and authorizing the application. Finally, select the repository, configure any settings, build the site, and wait for Netlify to deploy it. With this setup, you can push changes to GitHub and see them live on Netlify with minimal manual effort.

Netlify now supports HTTP 2.0 out of the box, enabling instant cache invalidation for HTML files, improving performance in regions with existing CDN points of presence. The company has also rolled out new points of presence in South America, Australia, and Asia to reduce time-to-first-byte. Additionally, Netlify now automatically sets up redirects for canonical URLs, rewriting internal links and automatic redirects. Jekyll 3.0 is being launched next Monday, bringing significant updates to the popular static site generator. Netlify continues to be the fastest and most full-featured static site hosting service on the market.

This tutorial guides users on how to host a Middleman site on Netlify, including setting up continuous deployment. The process begins with installing Middleman and creating a new Git repository on GitHub. Next, the user connects their local repository to Netlify by adding the remote repository URL and authorizing access. Once connected, Netlify takes care of deploying updates and changes to the site, eliminating the need for manual deployment. The tutorial concludes with the user configuring their settings, building their site, and making it live for public viewing.