A presentation by Justin Mayer
Saturday, February 21, 2015
Basic familiarity with the command line
… will be useful ☺
Content mixed with tags
Not very DRY
Only for technical folks
HTML generated by server
Content stored in database
Web-based editor
Web server
Application server
Database server
Upgrading application and database servers
Content versioning is hard
Migration is a pain
High-profile site links to you
Congratulations!
Association for Computing Machinery
http://queue.acm.org/detail.cfm?id=2721993
CMS treats content as instructions
Attack via crafted blog post or comment
DDoS
No longer “just files”
Content as files
Templates and content blocks: DRY
Generate locally; sync to server
Markdown
reStructured Text
Asciidoc
Textile
Not waiting on CPU to generate the page
No reverse proxying
Web servers are optimized for static assets
No app or DB server
Less moving parts
Source content is on your machine
Easier backups, versioning, migration
rsync
GitHub Pages
S3/CloudFront/Rackspace/Heroku
Written in Python
Nearly 250 contributors
Thriving ecosystem
https://staticsitegenerators.net/
386 of them listed (as of today)
Example: contact forms
Potentially an issue for huge sites
Not nearly as approachable
or user-friendly
Caching and parallel I/O
Web-based editing
Live page reloading
Self-hosted comments
Site search
Contact forms
Should be much more user-friendly
Want to hear about your experiences
Stay tuned
Simple, reliable, fast
Pairs well with microservices
Better control over your software and your data
Justin Mayer — @jmayer
This presentation:
justinmayer.com/talks/scale13x/rise-static-site-generators/