All the features developers need right out of the box: Global CDN, Continuous Deployment, one click HTTPS and more…
Netlify is a unified platform that automates your code to create high-performant, easily maintainable sites and web apps.
Simply push your code and let Netlify take care of the rest.
- Deploying a Jekyll Site on Netlifyby Bryan King TutorialJan 14, 18
First things first, you’re going to need a local instance of Jekyll. It’s built on Ruby, so you’re going to need that installed too before we can create a website.
- using stripe elements with netlify formsby chris draycott-wheatley TutorialJan 12, 18
Stripe Elements are pre-built UI components ready to drop into your website and customise to your preference.
- 10 Netlify features to surprise and delightby Phil Hawksworth ArticleJan 04, 18
During my first days as a Netlify employee, I learned about some features that surprised me. The response to my tweet announcing my new role was interesting, too. I received lots of kind words of congratulations along with questions about features I assumed were well known or understood.
- Notes about migrating to Hugoby Fatih Arslan TutorialNov 30, 17
I’ve moved my blog to a new blogging platform. This time from Wordpress.com to Hugo. I took some notes about various parts of this migration. I wrote some of my thoughts on why I made the switch, ideas, improvements for the design and custom tooling for my editing workflow.
- Setting Up a Continuous Deployment Pipeline with Gatsby.js, Contentful and Netlify | halfelectronic.comTutorialNov 23, 17
Ever since I published my first entry a couple of weeks ago, I have been asked a couple questions regarding the approach I followed to set up Gatsby.js, Contentful and Netlify, so I thought it would be a good idea to write a post about it.
- Contentful and Netlify: The Dynamic Duo of Static Site Managementby Malik Browne ArticleNov 15, 17
When it comes to blogging there are tons of platforms available for people to use. A blog could be using a static site generator like Jekyll, or a powerful content management system (CMS) like Wordpress or Drupal. Each of these tools has their own specific process for development.
- Middleman Netlify Server Pushby Joost Baaij TutorialAug 07, 17
Last month, Netlify introduced their implementation of HTTP/2 Server Push. We started using this and have have noticed significantly faster websites. Here is how to configure Middleman to use this feature.
- Migrating from Jekyll+Github Pages to Hugo+Netlifyby Sara Soueidan TutorialJun 07, 17
During the last 18 months, working on my Web site became a daunting task—be that for developing, redesigning it, writing a blog post, or making updates to my speaking and workshop pages. My then static site generator, Jekyll, is why. And a change has long been overdue…
- GraphCMS - GraphQL Based Headless CMSby Jeff Escalante TutorialMay 17, 17
One of the great advantages of headless CMS’ is that they are able to be consumed by a wide variety of different applications and build tools, rather than being tied specifically to a web frontend. And today we’ll be talking about using GraphCMS to create a static site - an architecture that suits many use cases much better than using a dynamic site or single page app.
- Go static: 5 reasons to try JAMstack on your next project.by Tom Bennet, Builtvisible ArticleMar 13, 17
- Creating a staging environment for Jekyllby Eduardo Bouças TutorialFeb 22, 17
A staging or pre-production environment is a testing infrastructure that replicates as best as possible the setup of a live site. In the context of a Jekyll site, it can be used to share a new post or feature with a selected group of people before a roll out to the general public. In this post, I’ll show you how I created one and how I make use of it.
- A publishing workflow for teams using static site generatorsby Keybits TutorialJan 02, 17
If your team is semi-technical, and writes content for a static site generator such Jekyll or Hugo, you may have wondered how to approve new content before deploying it to production.
- Isomorphic rendering on the JAM Stackby Phil Hawksworth TutorialAug 01, 16
I have been experimenting with something that seemed obvious to me for a while. A web development model which gives a pre-rendered, ready-to-consume, straight-into-the-eyeballs web page at every URL of a site. One which, once loaded, then behaves like a client-side, single page app.
The fact that so many frameworks set about this with all manner of complex add-ons and machinery gave me cause to think I was missing something big. So I built a simple proof of concept with a static site generator to see if this model could work. I’m pretty pleased with it. Let me talk you through the approach and show you the result.
- Developing a Static Site Generator Workflowby Thomas Peham, Sitepoint TutorialFeb 04, 16
In this article, I’d like to give you some insights into the journey we undertook in the last couple of months to change our stack of tools and the way we produce and deploy new landing pages.
- Why WeWork.com uses a static generator and why you should tooby Ramin Bozorgzadeh, WeWork Resource/WebsiteDec 09, 15
- Static sites go all Hollywoodby Phil Hawksworth Video/PresentationSep 22, 15
The popularity of building web sites with static site generators is on the rise. Their reduced complexity, easier compliance, cheaper hosting, and other benefits are getting people’s attention, but they do have limits.
This talk will explore how we can break through some of those limits with the use of a new breed of hosted tools and services. We’ll look at practical examples of how a static site generator can help deliver a modern web development workflow, support a living styleguide, and also pack the kind of dynamic punch that you’d only think possible from bigger application stacks.
- Netlify vs. Amazon S3by Mathias Biilmann, Netlify ArticleMar 06, 15
In short: S3 manages files. Netlify manages sites.
- Building a Static CMSArticleDec 05, 14
We ended up finding two great services, Contentful and Netlify, that worked well with our current toolset to achieve the Holy Grail: a static CMS.
- Five Reasons you want HTTPS for your Static siteby Mathias Biilmann, Netlify ArticleOct 03, 14
It might seem like a static site is already plenty secure: there’s no moving parts, no risk of SQL injection, no openings for XSS attacks, no cookies to hijack, no personalized data sent over the wire, etc, etc, etc… But here are 5 good reasons you should switch to HTTPS for your static site today.