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 recently started <a href=\"https:\/\/www.oliverdavies.uk\/daily\/2024\/12\/18\/self-hosting-podcast\">self-hosting the episodes for the Beyond Blocks podcast<\/a>.<\/p>\n\n<p>Instead of hosting the episodes on a third party service, the MP3 files are hosted on my server and played using the HTML5 audio element.<\/p>\n\n<p>The first step was to add the files to my website codebase and deploy them to the server. This was the smallest deployable iteration of this project.<\/p>\n\n<p>The second iteration was to change the player on the episode page.<\/p>\n\n<p>This is still a work-in-progress as I need to finish building the podcast feed to submit to iTunes, Spotify, etc.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>I didn't need to wait to finish this before I could change the player, and I didn't need to do that before uploading the MP3 files.<\/p>\n\n<p>Each was its own deployable step, and this is how I like to approach tasks.<\/p>\n\n<p>I like to break things down as much as possible to find the smallest piece of task that can be committed and deployed.<\/p>\n\n<p>Deploying features iteratively is less risky that deploying everything at once.<\/p>\n\n<p>You're deploying changes in smaller parts, making it less likely for something to go wrong, and easier to identify and resolve any issues.<\/p>\n\n<p>And, if you need to roll back or revert a change, you can affect only the part you need instead of everything.<\/p>\n\n ",
|
||||
"value": "\n <p>I recently started <a href=\"/daily\/2024\/12\/18\/self-hosting-podcast\">self-hosting the episodes for the Beyond Blocks podcast<\/a>.<\/p>\n\n<p>Instead of hosting the episodes on a third party service, the MP3 files are hosted on my server and played using the HTML5 audio element.<\/p>\n\n<p>The first step was to add the files to my website codebase and deploy them to the server. This was the smallest deployable iteration of this project.<\/p>\n\n<p>The second iteration was to change the player on the episode page.<\/p>\n\n<p>This is still a work-in-progress as I need to finish building the podcast feed to submit to iTunes, Spotify, etc.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>I didn't need to wait to finish this before I could change the player, and I didn't need to do that before uploading the MP3 files.<\/p>\n\n<p>Each was its own deployable step, and this is how I like to approach tasks.<\/p>\n\n<p>I like to break things down as much as possible to find the smallest piece of task that can be committed and deployed.<\/p>\n\n<p>Deploying features iteratively is less risky that deploying everything at once.<\/p>\n\n<p>You're deploying changes in smaller parts, making it less likely for something to go wrong, and easier to identify and resolve any issues.<\/p>\n\n<p>And, if you need to roll back or revert a change, you can affect only the part you need instead of everything.<\/p>\n\n ",
|
||||
"format": "full_html",
|
||||
"processed": "\n <p>I recently started <a href=\"https:\/\/www.oliverdavies.uk\/daily\/2024\/12\/18\/self-hosting-podcast\">self-hosting the episodes for the Beyond Blocks podcast<\/a>.<\/p>\n\n<p>Instead of hosting the episodes on a third party service, the MP3 files are hosted on my server and played using the HTML5 audio element.<\/p>\n\n<p>The first step was to add the files to my website codebase and deploy them to the server. This was the smallest deployable iteration of this project.<\/p>\n\n<p>The second iteration was to change the player on the episode page.<\/p>\n\n<p>This is still a work-in-progress as I need to finish building the podcast feed to submit to iTunes, Spotify, etc.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>I didn't need to wait to finish this before I could change the player, and I didn't need to do that before uploading the MP3 files.<\/p>\n\n<p>Each was its own deployable step, and this is how I like to approach tasks.<\/p>\n\n<p>I like to break things down as much as possible to find the smallest piece of task that can be committed and deployed.<\/p>\n\n<p>Deploying features iteratively is less risky that deploying everything at once.<\/p>\n\n<p>You're deploying changes in smaller parts, making it less likely for something to go wrong, and easier to identify and resolve any issues.<\/p>\n\n<p>And, if you need to roll back or revert a change, you can affect only the part you need instead of everything.<\/p>\n\n ",
|
||||
"processed": "\n <p>I recently started <a href=\"/daily\/2024\/12\/18\/self-hosting-podcast\">self-hosting the episodes for the Beyond Blocks podcast<\/a>.<\/p>\n\n<p>Instead of hosting the episodes on a third party service, the MP3 files are hosted on my server and played using the HTML5 audio element.<\/p>\n\n<p>The first step was to add the files to my website codebase and deploy them to the server. This was the smallest deployable iteration of this project.<\/p>\n\n<p>The second iteration was to change the player on the episode page.<\/p>\n\n<p>This is still a work-in-progress as I need to finish building the podcast feed to submit to iTunes, Spotify, etc.<\/p>\n\n<h2 id=\"here%27s-the-thing\">Here's the thing<\/h2>\n\n<p>I didn't need to wait to finish this before I could change the player, and I didn't need to do that before uploading the MP3 files.<\/p>\n\n<p>Each was its own deployable step, and this is how I like to approach tasks.<\/p>\n\n<p>I like to break things down as much as possible to find the smallest piece of task that can be committed and deployed.<\/p>\n\n<p>Deploying features iteratively is less risky that deploying everything at once.<\/p>\n\n<p>You're deploying changes in smaller parts, making it less likely for something to go wrong, and easier to identify and resolve any issues.<\/p>\n\n<p>And, if you need to roll back or revert a change, you can affect only the part you need instead of everything.<\/p>\n\n ",
|
||||
"summary": null
|
||||
}
|
||||
],
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue