Hey 👋

One of the main benefits of working with blazor is that you can use C# both server side and client side. It allows frontend and backend developers to share a single codebase (something that was only possible with javascript before). This feature is possible because of Web Assembly which gives .NET a low level language to target when compiling C#. One issue with Web Assembly is that it is still in development and doesn’t have direct access to the DOM like javascript does. So calls to the DOM need to be handled with an IJSRuntime interface which allows developers to call JavaScript functions from .NET methods and vice-versa. ...

If you followed my previous post on deploying a static website using S3, CloudFront, and Route53, you might have noticed that if you go to a page that doesn’t exist, you get a page that looks like this: This is because of the origin access control settings. AWS recommends using origin access control because it allows the S3 bucket containing your website files to restrict access to everyone except CloudFront. ...

In this article I’m going to show you how to create a GitHub workflow which automatically deploys a hugo website on a set schedule. Add access keys I host this website on AWS CloudFront. In order for GitHub to be able to deploy my website, it needs access to my AWS account. In my last article you learned how to create an IAM user with the necessary permissions for deploying a Hugo website. You will need the same setup here. ...

In this article, I’m going to show you how to use Hugo’s built-in hugo deploy command to deploy your site to a CloudFront distribution. You’re going to learn how to set up an IAM user on AWS, authenticate the AWS CLI, and configure the Hugo CLI so that you can deploy your Hugo website using 1 command. Before you begin, make sure you have a CloudFront distribution with an S3 bucket as an origin. You can find a guide on setting one up here. You are also going to need to have the AWS CLI and Hugo installed. ...

In this article, you will learn how to store a static website on S3, use CloudFront as a content delivery network to distribute your website globally, and finally, use Route53 to access your website from a custom domain of your choice. Before you start, you should have the files for your static website and a domain name with a hosted zone on Route53. Ultimately, you will have a website that uses HTTPS, is accessible from a custom domain, and is distributed globally, giving your users faster loading times. ...

LibMan is a lightweight tool for managing client side libraries. It is integrated in Visual Studio 2017+ or it can be installed as a .NET tool using the following command: dotnet tool install --global Microsoft.Web.LibraryManager.Cli To set up LibMan, go to your project’s root directory and run this: libman init This creates a libman.json file which looks like this: { "version": "1.0", "defaultProvider": "cdnjs", "libraries": [] } You can then customize the libman file with the libraries you want to use: ...