uuid:
  - value: bc747939-87ef-409b-bb1e-48c94863579c
langcode:
  - value: en
type:
  - target_id: daily_email
    target_type: node_type
    target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7
revision_timestamp:
  - value: '2025-05-11T09:00:20+00:00'
revision_uid:
  - target_type: user
    target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
revision_log: {  }
status:
  - value: true
uid:
  - target_type: user
    target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
title:
  - value: 'gray or grey, and center or centre?'
created:
  - value: '2024-02-15T00:00:00+00:00'
changed:
  - value: '2025-05-11T09:00:20+00:00'
promote:
  - value: false
sticky:
  - value: false
default_langcode:
  - value: true
revision_translation_affected:
  - value: true
path:
  - alias: /daily/2024/02/15/gray-or-grey--and-center-or-centre
    langcode: en
body:
  - value: |
      <p><a href="/blog/renaming-gray-grey-tailwind-css">I previously wrote</a> about how to change <code>gray</code> to <code>grey</code> in Tailwind CSS.</p>

      <p>So, instead of writing <code>bg-gray-200</code>, I could write <code>bg-grey-200</code>.</p>

      <p>This would be the correct spelling, as I live in the UK.</p>

      <p>But I recently realised that I don't change <code>text-center</code> or <code>items-center</code> when 'centre' would also be the correct spelling.</p>

      <p>So, what value is there to renaming <code>gray</code>?</p>

      <p>It adds inconsistency as it mixes US and UK English in this project and inconsistencies between different projects.</p>

      <p>It doesn't match the CSS colour name.</p>

      <p>And, if I'm working with others on a project, they also need to be aware of this as it's different from the default configuration and could cause some confusion and affect productivity.</p>

      <p>Keeping it the default value would make it easier to work on, collaborate on and maintain.</p>

      <p>Maybe, I'll leave it as <code>gray</code> in the future.</p>

              
    format: full_html
    processed: |
      <p><a href="http://default/blog/renaming-gray-grey-tailwind-css">I previously wrote</a> about how to change <code>gray</code> to <code>grey</code> in Tailwind CSS.</p>

      <p>So, instead of writing <code>bg-gray-200</code>, I could write <code>bg-grey-200</code>.</p>

      <p>This would be the correct spelling, as I live in the UK.</p>

      <p>But I recently realised that I don't change <code>text-center</code> or <code>items-center</code> when 'centre' would also be the correct spelling.</p>

      <p>So, what value is there to renaming <code>gray</code>?</p>

      <p>It adds inconsistency as it mixes US and UK English in this project and inconsistencies between different projects.</p>

      <p>It doesn't match the CSS colour name.</p>

      <p>And, if I'm working with others on a project, they also need to be aware of this as it's different from the default configuration and could cause some confusion and affect productivity.</p>

      <p>Keeping it the default value would make it easier to work on, collaborate on and maintain.</p>

      <p>Maybe, I'll leave it as <code>gray</code> in the future.</p>

              
    summary: null
field_daily_email_cta: {  }