Opened 3 weeks ago

Last modified 12 days ago

#33115 new defect

Migrating the blog to a static web site with Lektor

Reported by: hiro Owned by: hiro
Priority: Medium Milestone:
Component: Webpages/Blog Version:
Severity: Normal Keywords:
Cc: tpa-roadmap-march Actual Points:
Parent ID: Points: 10
Reviewer: Sponsor:

Description (last modified by hiro)

We have been having issues with the blog for a long time. The template we are using was developed for another purpose and never really finished.
We also spend a lot of money on Drupal that could rather be spent somewhere else.

I propose to migrate the blog to a static website with lektor and have comments running from I have actually been in contact with discourse and they have offered to run a forum for us for free (#33105). Addittionally they would run an .onion and a subdomain.

Moderation on discourse is much easier than on drupal comments (another pain point for the blog), and we would get a forum that we could use for other purposes too.

This is how the blog can be migrated.

  • We will do mockups and approve them with all the parties involved.
  • We will start migrating content and have it on staging for testing.
  • Once we are happy we will archive the current blog into static pages and move the static bloc to

What we will lose:

  • Version history on posts.
  • Old comments. I see no value in migrating old blog comments to discourse to be honest. It would be a lot of effort and the old comments will be archived anyways in the blog archive.

What we will gain:

  • Once the blog has been migrated creating posts will be no different than editing anyone of our websites. It would actually be a bit easier since there are a few different template and pages in our website and the blog will just have posts.
  • Anyone that is currently updating the websites will be able to help people with blog posts, therefore we will gain a lot more of blog admins.
  • The blog will run from our static www rotation, so we will not have to run expensive services or 2 cache VMs in front of it to avoid paing a lot to a third party for page views.
  • We will not have to update a service every now and again. The blog will run out of static HTML.
  • We will be able to update the templates according to our styleguide.
  • Functionalities that we will build won't break because of a drupal update.

Child Tickets

Change History (4)

comment:1 Changed 3 weeks ago by hiro

Description: modified (diff)
Parent ID: #33105

comment:2 Changed 3 weeks ago by gaba

Cc: tpa-roadmap-march added
Points: 10

comment:3 Changed 3 weeks ago by anarcat

is it part of the spec here to allow users unfamiliar with git to edit the website? i'm wondering if we've given any thought to which tools could be used for that purpose...

i wonder if tools like this could be useful for us:

those are hugo frontends, but they could easily apply to lektor as well....

comment:4 Changed 12 days ago by pili

I would like to highlight the need for an events/calendar plugin or similar.

Also, we might want to keep the following notes on this from the last dev meeting:

Note: See TracTickets for help on using tickets.