Using Nitride - Pipelines
I found a good way of working on a project is being able to see the end product. That means forging a minimal path from the start to end, and then going back to flesh it out. Interestingly, this is the opposite of how I write novels because, in those, the journey is the important part. Not so much with development projects.
In this case, the goal is to get a website generated and the ability to see it locally.
Series
Project Setup
Since this mainly a .NET project, we start by creating a new project and solution. This is a fairly simple generator and I don't plan on needing more than one assembly, so I'm going to throw everything into `//src/dotnet/` for the website.
$ dotnet new console --name Generator --output src/dotnet $ dotnet new solution --name Website $ dotnet sln add src/dotnet/Generator.csproj
And since we want to have the project run, we also update the `Justfile`:
# //Justfile
# Builds the typewriter.press website
build-typewriter:
dotnet run --project src/dotnet/Generator.csproj --
And that gives us an easy command to run that works anywhere underneath the Git repository (thanks to [[Just]]).
$ just build-typewriter dotnet run --project src/dotnet/Generator.csproj -- Hello, World!
Setting up NuGet
At the moment, the `MfGames.*` assemblies are not on nuget.org. There are a couple of reasons, mostly self-doubt that anyone would find this useful and the dread of setting up a SSL certificate which appeared to be required. My current intent is to do it once I have a number of sites using Nitride or I get a request to do so. Until then, I use `NuGet.config` file to hook up my libraries to the website.