eleventy-base-blog VS assemblylift

11ty is a lightweight static site generator. I chopped up my HTML and used the 11ty starter template called eleventy-base-blog as the structural foundation for the site.

Sure! It's on github at https://github.com/nosecreek/dustin-lammiman - I started with https://github.com/11ty/eleventy-base-blog for the basic templating logic.

Eleventy Base Blog demo site Source

To generate a static blog, we will be using Eleventy. Using the blog example from Eleventy as a base for our blog. Clone the repository:

I would do this with Eleventy which is a powerful static site generator with support for html partials (partial is what I call your toolbar here). You would use the template language nunjucks which Eleventy comes with support for, or you can choose plain html too if you don't want the Nunjucks capabilities for logic like if/else, for loops, javascript injection of dynamic values in your html at site generation time, etc. This repo shows most of the techniques you could need and use: https://github.com/11ty/eleventy-base-blog

For the second site I made using 11ty, I used this repo which is a more advanced 11ty template that can be customized. After following the instructions in the README.md file and edited all the markdown I came up with this:

Pre-established Eleventy Blog Template Go to eleventy base blog to clone the repository to your local file/folder.

The next example we'll look at goes more into depth of 11ty. We are creating this site from this template.

Say you want a more professonal looking site without having to do a lot of extra work, you’re in luck! 11ty has a community that has created templates that are available at this site. For this example, we will use the eleventy-base-blog, make sure to go to this repo and select the USE THIS TEMPLATE button to make a copy of the project in your namespace.

AssemblyLift is an open platform for cloud-native application development. AssemblyLift provides a portable, function-oriented framework and WebAssembly-based runtime which can be deployed to AWS Lambda or Kubernetes. The AssemblyLift CLI generates HashiCorp Terraform infrastructure code from simple TOML definitions, and takes care of compiling and packaging functions and services for deployment. To make a clichéd comparison, think of it as Infrastructure on Rails 😛

Since our last post introducing the AssemblyLift v0.4-alpha series, we've had two new alpha releases which introduced some major additions & improvements!

Today we're making available the first alpha release of AssemblyLift v0.4. This initial release brings a few exiting improvements to AssemblyLift including

After nearly two years in part-time development, AssemblyLift has been through three major revisions, sitting now at v0.3.2.

In this guide we'll use AssemblyLift to deploy our Lambda function, and define our API and an authorizer. AssemblyLift is an open platform which allows you to quickly develop high-performance serverless applications. Service functions are written in the Rust programming language and compiled to WebAssembly. The AssemblyLift CLI takes care of compiling and deploying your code, as well as building and deploying all the needed infrastructure!

Normally what we've described above would be a pretty complicated set up (and a much longer article 😜). Luckily we can use AssemblyLift to do all the heavy work for us!

This article will walk through building and deploying a simple static site, served using AWS Lambda and API Gateway. To accomplish this we will use AssemblyLift, an open-source platform designed to quickly & easily accomplish such a task.

If you've never heard of it or just need a reminder, AssemblyLift is an open platform for developing cloud-native applications. At its core are the AssemblyLift Runtime and the AssemblyLift CLI. The runtime provides an environment for executing compiled WebAssembly (WASM) on infrastructure such as AWS Lambda, and is one of the more unique aspects of the platform which we'll dig into more below.

Service TOML definitions now support specifying authorizers by ID for each function. These map to API Gateway authorizers; currently only IAM and JWT are supported. See the pull request for examples.