uuid: - value: 75787d98-31be-4b33-a434-15d5a43c07af langcode: - value: en type: - target_id: daily_email target_type: node_type target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7 revision_timestamp: - value: '2025-05-11T09:00:00+00:00' revision_uid: - target_type: user target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849 revision_log: { } status: - value: true uid: - target_type: user target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849 title: - value: 'Archiving Drupal websites as static websites' created: - value: '2025-03-18T00:00:00+00:00' changed: - value: '2025-05-11T09:00:00+00:00' promote: - value: false sticky: - value: false default_langcode: - value: true revision_translation_affected: - value: true path: - alias: /daily/2025/03/18/archiving langcode: en body: - value: |

Static websites can be created by writing each file by hand or using a tool like a static site generator.

But what if you've already got a dynamic website that you no longer need to be editable?

What if it was for an event that has passed, like a DrupalCamp?

If you no longer need to update the content via the admin UI, you could archive it by converting it to a static website.

Then you no longer need to maintain and update it, and simplify your hosting environment.

You could use Tome, a static site generator for Drupal, or use command line tools like wget with options like --mirror to create a static version by crawling a live website.

There are a few options on Drupal.org, which will also work with other CMSes and frameworks.

This is what I've done for old websites like our old DrupalCamp Bristol websites.

That means they're still available for people to see, but without the maintenance and security overhead.

format: full_html processed: |

Static websites can be created by writing each file by hand or using a tool like a static site generator.

But what if you've already got a dynamic website that you no longer need to be editable?

What if it was for an event that has passed, like a DrupalCamp?

If you no longer need to update the content via the admin UI, you could archive it by converting it to a static website.

Then you no longer need to maintain and update it, and simplify your hosting environment.

You could use Tome, a static site generator for Drupal, or use command line tools like wget with options like --mirror to create a static version by crawling a live website.

There are a few options on Drupal.org, which will also work with other CMSes and frameworks.

This is what I've done for old websites like our old DrupalCamp Bristol websites.

That means they're still available for people to see, but without the maintenance and security overhead.

summary: null field_daily_email_cta: { }