diff --git a/src/components/talk/Events.astro b/src/components/talk/Events.astro
index 326484d22..677c38112 100644
--- a/src/components/talk/Events.astro
+++ b/src/components/talk/Events.astro
@@ -32,7 +32,7 @@ const { events } = Astro.props;
) : (
event.name
- )}
+ )}
{event.location && `in ${event.location} -`}
{new Date(event.date).toLocaleDateString("en-GB", {
day: "numeric",
diff --git a/src/content/talk/taking-flight-with-tailwind-css.md b/src/content/talk/taking-flight-with-tailwind-css.md
index b4cbdd9f4..21d103bf5 100644
--- a/src/content/talk/taking-flight-with-tailwind-css.md
+++ b/src/content/talk/taking-flight-with-tailwind-css.md
@@ -1,8 +1,7 @@
---
title: Taking Flight with Tailwind CSS
description:
- An introduction to the utility-first approach to writing CSS with a focus
- on the Tailwind CSS framework.
+ An introduction to the utility-first approach to writing CSS with a focus on the Tailwind CSS framework.
speakerdeck:
id: 10ca51f23560443d83b898a92929b4b3
ratio: "1.77777777777778"
diff --git a/src/pages/build-configs.mdx b/src/pages/build-configs.mdx
index 03cfd104f..cab0d3ae3 100644
--- a/src/pages/build-configs.mdx
+++ b/src/pages/build-configs.mdx
@@ -1,6 +1,6 @@
---
layout: ~/layouts/PageLayout.astro
-title: 'Configuration files as a service'
+title: "Configuration files as a service"
---
import Button from "~/components/Button.astro";
@@ -20,11 +20,11 @@ export const products = [
All of my projects contain similar build configuration files, such as Docker and Docker Compose files, PHPUnit and PHPStan configuration, and CI/CD pipeline workflows. I used to maintain these manually which was time-intensive and there was no guarantee that the same features or options were available from project to project.
-“Build Configs” is a tool I’ve written to maintain a canonical set of templates and generate them for each project based on a per-project configuration file.
+“Build Configs” is a tool I've written to maintain a canonical set of templates and generate them for each project based on a per-project configuration file.
This makes it quicker and easier for me to create or onboard new projects to work on and, as all of the base files are centralised, when I fix something or add a new feature, the changes can be pushed to every project that uses it.
-I’ve been using this on personal projects such as my [Docker Drupal](https://github.com/opdavies/docker-example-drupal) and [Docker LocalGov Drupal](https://github.com/opdavies/docker-example-drupal-localgov) example projects and for various client projects.
+I've been using this on personal projects such as my [Docker Drupal](https://github.com/opdavies/docker-example-drupal) and [Docker LocalGov Drupal](https://github.com/opdavies/docker-example-drupal-localgov) example projects and for various client projects.
## How does it work?
@@ -43,10 +43,7 @@ Coming soon: watch a video of me creating a new Drupal project from scratch and
To get your project started on the right foot, I will create a new Drupal project skeleton for you using `build-configs` that is ready to work on, including all of the generated files. You can even edit them if you like as they will get no ongoing updates.
-
+
### Ongoing updates and support (single site) - £{products[1].price} per month
@@ -56,11 +53,7 @@ This also includes unlimited support via a dedicated Slack channel and you can m
If you like, I can add you to a beta users list and you’ll get new experimental features before anyone else.
-
-
+
If you have multiple Drupal sites, [contact me](/contact) and we can work something out.