80 lines
3.5 KiB
YAML
80 lines
3.5 KiB
YAML
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: |
|
|
<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>
|
|
|
|
<p>But what if you've already got a dynamic website that you no longer need to be editable?</p>
|
|
|
|
<p>What if it was for an event that has passed, like a DrupalCamp?</p>
|
|
|
|
<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>
|
|
|
|
<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>
|
|
|
|
<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>
|
|
|
|
<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>
|
|
|
|
<p>This is what I've done for old websites like our old DrupalCamp Bristol websites.</p>
|
|
|
|
<p>That means they're still available for people to see, but without the maintenance and security overhead.</p>
|
|
|
|
|
|
format: full_html
|
|
processed: |
|
|
<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>
|
|
|
|
<p>But what if you've already got a dynamic website that you no longer need to be editable?</p>
|
|
|
|
<p>What if it was for an event that has passed, like a DrupalCamp?</p>
|
|
|
|
<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>
|
|
|
|
<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>
|
|
|
|
<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>
|
|
|
|
<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>
|
|
|
|
<p>This is what I've done for old websites like our old DrupalCamp Bristol websites.</p>
|
|
|
|
<p>That means they're still available for people to see, but without the maintenance and security overhead.</p>
|
|
|
|
|
|
summary: null
|
|
field_daily_email_cta: { }
|