tome export
This commit is contained in:
parent
52278c3a53
commit
7a52afab5f
960 changed files with 3670 additions and 2229 deletions
|
@ -82,15 +82,15 @@
|
|||
],
|
||||
"body": [
|
||||
{
|
||||
"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 ",
|
||||
"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=\"/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=\"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>\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
|
||||
}
|
||||
],
|
||||
"feeds_item": [
|
||||
{
|
||||
"imported": "1970-01-01T00:33:45+00:00",
|
||||
"imported": "1970-01-01T00:32:50+00:00",
|
||||
"guid": null,
|
||||
"hash": "ca4c680e0cbb4095fc2e8350b85a012f",
|
||||
"target_type": "feeds_feed",
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue