Static Sites

Just HTML, CSS, and JS.

Sometimes called JAM stack(Javascript,API's & Markup)

• Why?
• How I like it.
• Netlify Goodness.

Why

• Simple - it's easy to reason about
  • The output is easy to inspect
  • Compiles and optimizes itself on build
  • There are source-maps
  • Customizable but sane defaults.

• Fast - any server can dish flat files out asap

  It's just html, css, and js files.

• Scalable - Many solutions exist to scale it's assets on demand.
  • s3, Azure Blob Storage
  • IIS, Apache
  • Netlify...

Might not be a good fit:

• Large eCommerce systems that change often
• Micro$oft Tools Requirement
• Brownfield On-Site DB.
• Others?

How

There is a sea of options:

• Sapper A JS based solution
• Wyam A .NET based tool
• Jekyll Popular site generate used with Github
• Hugo  "The world’s fastest framework for building websites" in go
• So many more....

Javascript™

JS is taking over the world.

Offers endless pre-built solutions to common problems from the open source community.

Large pool of people who can leverage it for good and evil.

Webpack

Endlessly configurable assest bundeler for web assets

Able to sense changes in files and hot reload.

Well supported and documented.

Markdown

/*
Title: Page Title
Description: Meta description
*/

# Header Title
Lorem Ipsum, yada, yada, yada.

Pug

A css selector based html template language that relies on indentation. Div elements are implied if one is not specified

extends ../templates/default
block vars
  -var title = 'Page Title'
  -var description = 'Meta description';
block content
  h1 Header Title
  .content.d-flex.flex-column
    .card.card-default
      .card-body
        p#customIdForHi
          | Hi,
        p Lorem Ipsum, yada, yada, yada.

Netlify

Netlify Build

Netlify Functions

Netlify Forms

Azure?

Future