sebastienvercammen / node-site-from-google-sheet Goto Github PK

Description

Add build steps to deliver the assets in an optimal format.

Why is this feature necessary?

Smaller files, less web server resources usage, higher throughput (in part due to improved cachability).

Thoughts on implementation

• Use src/ and dist/ folder naming
• Use hard cleanup: Completely remove dist/ before running build
• Add versioning when linking to static assets in HTML to bust cache on content changes
• Use npm scripts, not larger build tools. It can do everything we need it to
  • A custom build.js can be used as last resort if the scripts can't satisfy the requirements
  • Build scripts should run automatically after npm install
• Compatibility
  • Polyfill JS
  • normalize.css
• Optimize assets
  • Combine assets (JS, CSS)
  • Compress assets
    • Minify contents (HTML, JS, CSS)
    • Include a pre-gzipped version of static files to save on server resources