Make all links relative
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:
parent
0d359f81d6
commit
7a7dc297ca
349 changed files with 698 additions and 698 deletions
|
@ -82,9 +82,9 @@
|
|||
],
|
||||
"body": [
|
||||
{
|
||||
"value": "\n <p>I've been <a href=\"https:\/\/www.oliverdavies.uk\/presentations\/taking-flight-with-tailwind-css\">speaking about and advocating for Tailwind CSS<\/a> and utility-first CSS for a long time.<\/p>\n\n<p>In my slide deck, I show screenshots of websites that are all built with Tailwind CSS - including some <a href=\"https:\/\/www.oliverdavies.uk\/blog\/uis-ive-rebuilt-tailwind-css\">rebuilds of existing websites<\/a>.<\/p>\n\n<p>I do this to show that the same approach and framework can be used to create different-looking designs because the classes are atomic and can be reused and combined as needed.<\/p>\n\n<p>This isn't the case with other CSS frameworks that focus on components first.<\/p>\n\n<p>As an experiment, some time ago I decided to <a href=\"https:\/\/bootstrap-with-tailwind.oliverdavies.uk\">rebuild some of the Bootstrap example components using Tailwind CSS<\/a>.<\/p>\n\n<p>I've only done a pricing grid and album, but I may do more in the future.<\/p>\n\n<p>I originally built the examples with Astro but have ported them to Sculpin, which I'm more familiar with.<\/p>\n\n<p>If you want to see how I've built these components or how for an example of building a static website with Sculpin, <a href=\"https:\/\/code.oliverdavies.uk\/opdavies\/bootstrap-with-tailwind\">check out the source code<\/a>.<\/p>\n\n ",
|
||||
"value": "\n <p>I've been <a href=\"/presentations\/taking-flight-with-tailwind-css\">speaking about and advocating for Tailwind CSS<\/a> and utility-first CSS for a long time.<\/p>\n\n<p>In my slide deck, I show screenshots of websites that are all built with Tailwind CSS - including some <a href=\"/blog\/uis-ive-rebuilt-tailwind-css\">rebuilds of existing websites<\/a>.<\/p>\n\n<p>I do this to show that the same approach and framework can be used to create different-looking designs because the classes are atomic and can be reused and combined as needed.<\/p>\n\n<p>This isn't the case with other CSS frameworks that focus on components first.<\/p>\n\n<p>As an experiment, some time ago I decided to <a href=\"https:\/\/bootstrap-with-tailwind.oliverdavies.uk\">rebuild some of the Bootstrap example components using Tailwind CSS<\/a>.<\/p>\n\n<p>I've only done a pricing grid and album, but I may do more in the future.<\/p>\n\n<p>I originally built the examples with Astro but have ported them to Sculpin, which I'm more familiar with.<\/p>\n\n<p>If you want to see how I've built these components or how for an example of building a static website with Sculpin, <a href=\"https:\/\/code.oliverdavies.uk\/opdavies\/bootstrap-with-tailwind\">check out the source code<\/a>.<\/p>\n\n ",
|
||||
"format": "full_html",
|
||||
"processed": "\n <p>I've been <a href=\"https:\/\/www.oliverdavies.uk\/presentations\/taking-flight-with-tailwind-css\">speaking about and advocating for Tailwind CSS<\/a> and utility-first CSS for a long time.<\/p>\n\n<p>In my slide deck, I show screenshots of websites that are all built with Tailwind CSS - including some <a href=\"https:\/\/www.oliverdavies.uk\/blog\/uis-ive-rebuilt-tailwind-css\">rebuilds of existing websites<\/a>.<\/p>\n\n<p>I do this to show that the same approach and framework can be used to create different-looking designs because the classes are atomic and can be reused and combined as needed.<\/p>\n\n<p>This isn't the case with other CSS frameworks that focus on components first.<\/p>\n\n<p>As an experiment, some time ago I decided to <a href=\"https:\/\/bootstrap-with-tailwind.oliverdavies.uk\">rebuild some of the Bootstrap example components using Tailwind CSS<\/a>.<\/p>\n\n<p>I've only done a pricing grid and album, but I may do more in the future.<\/p>\n\n<p>I originally built the examples with Astro but have ported them to Sculpin, which I'm more familiar with.<\/p>\n\n<p>If you want to see how I've built these components or how for an example of building a static website with Sculpin, <a href=\"https:\/\/code.oliverdavies.uk\/opdavies\/bootstrap-with-tailwind\">check out the source code<\/a>.<\/p>\n\n ",
|
||||
"processed": "\n <p>I've been <a href=\"/presentations\/taking-flight-with-tailwind-css\">speaking about and advocating for Tailwind CSS<\/a> and utility-first CSS for a long time.<\/p>\n\n<p>In my slide deck, I show screenshots of websites that are all built with Tailwind CSS - including some <a href=\"/blog\/uis-ive-rebuilt-tailwind-css\">rebuilds of existing websites<\/a>.<\/p>\n\n<p>I do this to show that the same approach and framework can be used to create different-looking designs because the classes are atomic and can be reused and combined as needed.<\/p>\n\n<p>This isn't the case with other CSS frameworks that focus on components first.<\/p>\n\n<p>As an experiment, some time ago I decided to <a href=\"https:\/\/bootstrap-with-tailwind.oliverdavies.uk\">rebuild some of the Bootstrap example components using Tailwind CSS<\/a>.<\/p>\n\n<p>I've only done a pricing grid and album, but I may do more in the future.<\/p>\n\n<p>I originally built the examples with Astro but have ported them to Sculpin, which I'm more familiar with.<\/p>\n\n<p>If you want to see how I've built these components or how for an example of building a static website with Sculpin, <a href=\"https:\/\/code.oliverdavies.uk\/opdavies\/bootstrap-with-tailwind\">check out the source code<\/a>.<\/p>\n\n ",
|
||||
"summary": null
|
||||
}
|
||||
],
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue