chore(format)

This commit is contained in:
Oliver Davies 2023-04-25 01:09:10 +01:00
parent f4c19b9972
commit 0a87e15195
5 changed files with 12 additions and 17 deletions

View file

@ -2,10 +2,11 @@
interface Props {
href: string;
text: string;
};
}
const { href, text } = Astro.props as Props;
---
<div class="mt-6 not-prose">
<a
class="inline-flex items-center py-3 px-6 text-base font-medium text-white no-underline rounded-md duration-200 ease-in-out hover:bg-white focus:bg-white bg-blue-primary transition-color hover:text-blue-primary focus:text-blue-primary"

View file

@ -58,7 +58,9 @@ const { intro } = Astro.props;
<footer class="px-4 mt-4 text-center">
<Markdown>
<p>
Not sure? <a class="link" href="/archive">Browse the archive &rarr;</a>
Not sure? <a class="link" href="/archive"
>Browse the archive &rarr;</a
>
</p>
</Markdown>
</footer>

View file

@ -32,7 +32,7 @@ const { events } = Astro.props;
</a>
) : (
event.name
)}
)}
{event.location && `in ${event.location} -`}
{new Date(event.date).toLocaleDateString("en-GB", {
day: "numeric",

View file

@ -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"

View file

@ -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 Ive 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.
Ive 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.
<Button
href={products[0].link}
text={products[0].buttonText}
/>
<Button href={products[0].link} text={products[0].buttonText} />
### 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 youll get new experimental features before anyone else.
<Button
href={products[1].link}
text={products[1].buttonText}
/>
<Button href={products[1].link} text={products[1].buttonText} />
If you have multiple Drupal sites, [contact me](/contact) and we can work something out.