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

tome export

Browse source
This commit is contained in:
Oliver Davies 2025-05-30 02:14:32 +01:00
parent 52278c3a53
commit 7a52afab5f
960 changed files with 3670 additions and 2229 deletions
Download patch file Download diff file Expand all files Collapse all files

6
content/node.75787d98-31be-4b33-a434-15d5a43c07af.json
View file

@ -82,15 +82,15 @@
],
"body": [
{
"value": "\n <p>Static websites can be created by writing each file by hand or using a tool like <a href=\"/presentations\/sculpin\">a static site generator<\/a>.<\/p>\n\n<p>But what if you've already got a dynamic website that you no longer need to be editable?<\/p>\n\n<p>What if it was for an event that has passed, like a DrupalCamp?<\/p>\n\n<p>If you no longer need to update the content via the admin UI, you could archive it by converting it to a static website.<\/p>\n\n<p>Then you no longer need to maintain and update it, and <a href=\"/daily\/2025\/03\/13\/deploy\">simplify your hosting environment<\/a>.<\/p>\n\n<p>You could use <a href=\"/daily\/2025\/03\/15\/tome\">Tome, a static site generator for Drupal<\/a>, or use command line tools like <code>wget<\/code> with options like <code>--mirror<\/code> to create a static version by crawling a live website.<\/p>\n\n<p>There are <a href=\"https:\/\/www.drupal.org\/docs\/administering-a-drupal-site\/creating-a-static-archive-of-a-drupal-site\">a few options on Drupal.org<\/a>, which will also work with other CMSes and frameworks.<\/p>\n\n<p>This is what I've done for old websites like our old DrupalCamp Bristol websites.<\/p>\n\n<p>That means they're still available for people to see, but without the maintenance and security overhead.<\/p>\n\n ",
"value": "\n <p>Static websites can be created by writing each file by hand or using a tool like <a href=\"\/presentations\/sculpin\">a static site generator<\/a>.<\/p>\n\n<p>But what if you've already got a dynamic website that you no longer need to be editable?<\/p>\n\n<p>What if it was for an event that has passed, like a DrupalCamp?<\/p>\n\n<p>If you no longer need to update the content via the admin UI, you could archive it by converting it to a static website.<\/p>\n\n<p>Then you no longer need to maintain and update it, and <a href=\"\/daily\/2025\/03\/13\/deploy\">simplify your hosting environment<\/a>.<\/p>\n\n<p>You could use <a href=\"\/daily\/2025\/03\/15\/tome\">Tome, a static site generator for Drupal<\/a>, or use command line tools like <code>wget<\/code> with options like <code>--mirror<\/code> to create a static version by crawling a live website.<\/p>\n\n<p>There are <a href=\"https:\/\/www.drupal.org\/docs\/administering-a-drupal-site\/creating-a-static-archive-of-a-drupal-site\">a few options on Drupal.org<\/a>, which will also work with other CMSes and frameworks.<\/p>\n\n<p>This is what I've done for old websites like our old DrupalCamp Bristol websites.<\/p>\n\n<p>That means they're still available for people to see, but without the maintenance and security overhead.<\/p>\n\n ",
"format": "full_html",
"processed": "\n <p>Static websites can be created by writing each file by hand or using a tool like <a href=\"/presentations\/sculpin\">a static site generator<\/a>.<\/p>\n\n<p>But what if you've already got a dynamic website that you no longer need to be editable?<\/p>\n\n<p>What if it was for an event that has passed, like a DrupalCamp?<\/p>\n\n<p>If you no longer need to update the content via the admin UI, you could archive it by converting it to a static website.<\/p>\n\n<p>Then you no longer need to maintain and update it, and <a href=\"/daily\/2025\/03\/13\/deploy\">simplify your hosting environment<\/a>.<\/p>\n\n<p>You could use <a href=\"/daily\/2025\/03\/15\/tome\">Tome, a static site generator for Drupal<\/a>, or use command line tools like <code>wget<\/code> with options like <code>--mirror<\/code> to create a static version by crawling a live website.<\/p>\n\n<p>There are <a href=\"https:\/\/www.drupal.org\/docs\/administering-a-drupal-site\/creating-a-static-archive-of-a-drupal-site\">a few options on Drupal.org<\/a>, which will also work with other CMSes and frameworks.<\/p>\n\n<p>This is what I've done for old websites like our old DrupalCamp Bristol websites.<\/p>\n\n<p>That means they're still available for people to see, but without the maintenance and security overhead.<\/p>\n\n ",
"processed": "\n <p>Static websites can be created by writing each file by hand or using a tool like <a href=\"http:\/\/default\/presentations\/sculpin\">a static site generator<\/a>.<\/p>\n\n<p>But what if you've already got a dynamic website that you no longer need to be editable?<\/p>\n\n<p>What if it was for an event that has passed, like a DrupalCamp?<\/p>\n\n<p>If you no longer need to update the content via the admin UI, you could archive it by converting it to a static website.<\/p>\n\n<p>Then you no longer need to maintain and update it, and <a href=\"http:\/\/default\/daily\/2025\/03\/13\/deploy\">simplify your hosting environment<\/a>.<\/p>\n\n<p>You could use <a href=\"http:\/\/default\/daily\/2025\/03\/15\/tome\">Tome, a static site generator for Drupal<\/a>, or use command line tools like <code>wget<\/code> with options like <code>--mirror<\/code> to create a static version by crawling a live website.<\/p>\n\n<p>There are <a href=\"https:\/\/www.drupal.org\/docs\/administering-a-drupal-site\/creating-a-static-archive-of-a-drupal-site\">a few options on Drupal.org<\/a>, which will also work with other CMSes and frameworks.<\/p>\n\n<p>This is what I've done for old websites like our old DrupalCamp Bristol websites.<\/p>\n\n<p>That means they're still available for people to see, but without the maintenance and security overhead.<\/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": "a776e5053b9f9b1276b131cb30130d86",
"target_type": "feeds_feed",