Mathias gave this talk at the first editing of the Static Web-Tech Meetup in San Francisco, at the Netlify office.
It cover how to move from a dynamic approach to building websites, to a modern approach based on static site generation, and maps out the landscape of static site generators.
Dynamic to Static
Onboarding to static site generation from a dynamic workﬂow
What does Wordpress
Powers 24% of the Internet
Blows up all the time!
When you upgrade a plugin
A Static Approach
What if we reengineered Wordpress as a Static Site
What is Static?
It’s not about:
Dynamic content vs static brochure
Database vs Flat Files
Writing HTML by hand
What is Static?
No dynamic programming on the server
A Caching Contract
Static Wordpress: WP-admin
Static Wordpress: WP-Includes
Static Wordpress: PHP Crap
Replacing The PHP
Picking a static site generator
Typical Static Site
Lets look at netlify.com - currently a Jekyll based site
netlify.com the whole ﬂow
Picking Your Static
What you should look for…
The Modern Static Site Generator
Filtering & Sorting
Mapping out the STG
Build Tools Build Tools/STG Full Fledged STG Specialized STG
What to look for: Asset Pipeline
Composable? Extensible? vs Simple? No conﬁguration?
What to look for: Content
External APIs? Contentful, Prismic, Google Docs
What to look for: Metadata
YAML? JSON? TOML?
Separate Data Document
What to look for: Filter & Sort
Code in templates?
Built-in Sort and Filter features?
Easy helper methods?
What to look for: Plugins
Can you write plugins?
What’s possible with a plugin?
What else do you want from a static site generator?