25 Matching Annotations
  1. Dec 2021
    1. Fast forward to 2020, Jamstack hit the mainstream, and we saw millions of developers and major brands like Unilever, Nike, and PayPal embrace the architecture. Vital initiatives like the Covid Tracking Project were able to scale from 0 to 2 million API requests on the Jamstack. Frameworks like Nuxt became commercial businesses, and we celebrated large public companies like Microsoft and Cloudflare as they launched early Jamstack offerings.

      The JAMStack has been evolving since 2016 - and is proving to be a major tech stack / architecture going forward, and is starting to see mainstream adoption, and beyond static content centric sites.

  2. Oct 2021
    1. DIYJam Podcast

      Do-It-Yourself Jamstack Podcast Site

      Stackbit’s new Podcaster theme

    1. When I was looking for a way to build small, maintainable websites as an independent contractor, I found a local Vancouver company, Chloi, that was working on a static site generator called Harp. It was a plus that Kenneth Ormandy of Type Brigade had been involved in the project. (See his contributions on GitHub)

    1. Better Developer Experience

      Why Jamstack?

      I like the enhanced developer experience in particular, but it also helps that Jamstack sites have all of these benefits.

      • Better Performance
      • Higher Security
      • Cheaper, Easier Scaling
      • Better Developer Experience
    1. Jamstack

      The legacy version of the Run for Water site designed by Stephen Bau. Featured on Behance.

      This version is built with Jamstack, using Harp and DatoCMS.

      A similar approach could be used for the Co-Operating Manual for Spaceship Earth.

      A Modest Proposal

      Since the Buckminster Fuller Institute is using Airtable, it would be possible to follow the CSS-Tricks article on Going Jamstack with React, Serverless, and Airtable.

  3. getuikit.com getuikit.com
    1. WordPress & Joomla from the UIkit creators

      Run for Water

      I used one of these themes for the redesign of the Run for Water site. I transitioned away from Jamstack, because the organization is centred around volunteers, and it was important to empower them to easily make changes to the marketing front end of their organization. The WordPress theme has a beautiful interface for managing content. However, it goes against the philosophy of COPE (Create Once, Publish Everywhere), recommended by Karen McGrane in her presentations on Content in a Zombie Apocalypse.

      Symphony

      My interest in the subject of Adaptive Content goes back to the days when Symphony was my tool of choice.

    1. You can patch together a dozen services, each with its own account and billing, for hundreds of dollars a month, to get a similar result you’d have for a few dollars a month using WordPress on shared hosting,

      Matt Mullenweg’s criticism of Jamstack.

    1. Jamstack

      Going Jamstack with React, Serverless, and Airtable

      Exploring the possibility of integrating Airtable into the Builders Collective, I started looking into the Airtable API and integration into a Jamstack workflow. A CSS-Tricks article came up in a search.

    1. Rant on static sites

      I agree, Jamstack is brilliant, but time consuming. I decided on using Ghost to take the friction out of writing and publishing.

    1. Using the Hypothesis API

      What might it take to demo a Jamstack approach to connecting Airtable to Hypothesis with serverless functions in Netlify?

  4. May 2021
    1. go-jamming is a cool looking Webmention sender and receiver, particularly for SSGs. It can be used to service multiple websites as well.

      Requires a bit of configuration and build into one's templates, but it looks pretty well documented.

  5. 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.

  6. Jan 2021
  7. 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.
  8. May 2020