opdavies/oliverdavies.uk
1
0
Fork 0
Code Issues 1 Pull requests Projects 1 Releases Packages Wiki Activity Actions

Make all links relative

Browse source 
Now the abs_to_rel module is enabled, links can be made relative so they
work on the current environment.
This commit is contained in:
Oliver Davies 2025-05-29 16:42:25 +01:00
parent 0d359f81d6
commit 7a7dc297ca
349 changed files with 698 additions and 698 deletions
Download patch file Download diff file Expand all files Collapse all files

4
content/node.bc747939-87ef-409b-bb1e-48c94863579c.json
View file

@ -82,9 +82,9 @@
],
"body": [
{
"value": "\n <p><a href=\"https:\/\/www.oliverdavies.uk\/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>\n\n<p>So, instead of writing <code>bg-gray-200<\/code>, I could write <code>bg-grey-200<\/code>.<\/p>\n\n<p>This would be the correct spelling, as I live in the UK.<\/p>\n\n<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>\n\n<p>So, what value is there to renaming <code>gray<\/code>?<\/p>\n\n<p>It adds inconsistency as it mixes US and UK English in this project and inconsistencies between different projects.<\/p>\n\n<p>It doesn't match the CSS colour name.<\/p>\n\n<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>\n\n<p>Keeping it the default value would make it easier to work on, collaborate on and maintain.<\/p>\n\n<p>Maybe, I'll leave it as <code>gray<\/code> in the future.<\/p>\n\n ",
"value": "\n <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>\n\n<p>So, instead of writing <code>bg-gray-200<\/code>, I could write <code>bg-grey-200<\/code>.<\/p>\n\n<p>This would be the correct spelling, as I live in the UK.<\/p>\n\n<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>\n\n<p>So, what value is there to renaming <code>gray<\/code>?<\/p>\n\n<p>It adds inconsistency as it mixes US and UK English in this project and inconsistencies between different projects.<\/p>\n\n<p>It doesn't match the CSS colour name.<\/p>\n\n<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>\n\n<p>Keeping it the default value would make it easier to work on, collaborate on and maintain.<\/p>\n\n<p>Maybe, I'll leave it as <code>gray<\/code> in the future.<\/p>\n\n ",
"format": "full_html",
"processed": "\n <p><a href=\"https:\/\/www.oliverdavies.uk\/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>\n\n<p>So, instead of writing <code>bg-gray-200<\/code>, I could write <code>bg-grey-200<\/code>.<\/p>\n\n<p>This would be the correct spelling, as I live in the UK.<\/p>\n\n<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>\n\n<p>So, what value is there to renaming <code>gray<\/code>?<\/p>\n\n<p>It adds inconsistency as it mixes US and UK English in this project and inconsistencies between different projects.<\/p>\n\n<p>It doesn't match the CSS colour name.<\/p>\n\n<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>\n\n<p>Keeping it the default value would make it easier to work on, collaborate on and maintain.<\/p>\n\n<p>Maybe, I'll leave it as <code>gray<\/code> in the future.<\/p>\n\n ",
"processed": "\n <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>\n\n<p>So, instead of writing <code>bg-gray-200<\/code>, I could write <code>bg-grey-200<\/code>.<\/p>\n\n<p>This would be the correct spelling, as I live in the UK.<\/p>\n\n<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>\n\n<p>So, what value is there to renaming <code>gray<\/code>?<\/p>\n\n<p>It adds inconsistency as it mixes US and UK English in this project and inconsistencies between different projects.<\/p>\n\n<p>It doesn't match the CSS colour name.<\/p>\n\n<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>\n\n<p>Keeping it the default value would make it easier to work on, collaborate on and maintain.<\/p>\n\n<p>Maybe, I'll leave it as <code>gray<\/code> in the future.<\/p>\n\n ",
"summary": null
}
],