11 Matching Annotations
  1. Mar 2021
    1. I watched Ru work incredibly hard and diligently over many months to implement what she'd done. I wish I could do half of it, but I can definitely commiserate.

      Can't wait to see what you come up with in the coming year with the extra time you'll have gained not only from the switch, but everything else you've learned in the process.

  2. Jan 2021
  3. Dec 2020
    1. Because Jamstack projects don’t rely on server-side code, they can be distributed instead of living on a single server. Serving directly from a CDN unlocks speeds and performance that can’t be beat. The more of your app you can push to the edge, the better the user experience.
    2. Everything Lives in GitWith a Jamstack project, anyone should be able to do a git clone, install any needed dependencies with a standard procedure (like npm install), and be ready to run the full project locally. No databases to clone, no complex installs. This reduces contributor friction, and also simplifies staging and testing workflows.
    1. Better PerformanceWhy wait for pages to build on the fly when you can generate them at deploy time? When it comes to minimizing the time to first byte, nothing beats pre-built files served over a CDN.
  4. May 2020