Switch from Wordpress site to Github Pages

[chiraag-nataraj]

I've seen several requests on here (at the end of issues, for example) to update things on the website. It might be easier to manage if we move from the current Wordpress site to a Github page, since other people can also help maintain it.

Just a thought.

[smitsohu]

There is also #2090

[chiraag-nataraj]

Yup. But I presume moving our official documentation is slightly different from the website (which provides common usage, etc), so while it's related, I'd regard it as a separate goal.

[chiraag-nataraj]

@netblue30, thoughts?

[chiraag-nataraj]

Let's move the discussion over to #2729.

[tredondo]

Let's move the discussion over to #2729.

I wasn't around when this decision was made, but it seems the migration to Wordpress is pretty involved, mainly due to the comments and the blog (which still has entries there as of this month), so IMO it would make sense to keep it separate from the meta ticket (#2729). In that vein, I'll continue here.

So regarding the comments migration issue raised by @SkewedZeppelin,

The important bit about it is how low barrier it is. ie. no need to create a forum account or anything.

I think GitHub is a pretty low barrier of entry, and prevents spam very well.

find a solution for the comments

We now have GitHub discussions, which can host unanswered comments from Wordpress. For resolved Q&As, I think the best palce would be the Wiki FAQ, so I took the liberty to create some examples.

I went through all the Wordpress pages, and here are the ones with comments, as well as the date of the most recent comment. I think we should focus on the most recent ones first, and I also think it's fine if old comments are left in peace.

• https://firejail.wordpress.com/download-2/ - May 2020
• https://firejail.wordpress.com/download-2/release-notes/ - Aug2020
• https://firejail.wordpress.com/features-3/ - I've added the only relevant Q to the Wiki FAQ
• https://firejail.wordpress.com/features-3/man-firejail/ - Aug 2020
• https://firejail.wordpress.com/documentation-2/ - created a discussion for the only relevant comment
• https://firejail.wordpress.com/documentation-2/basic-usage/comment-page-1/#comments - Nov 2020
• https://firejail.wordpress.com/2021/01/21/firejail-tips-and-tricks/ - Feb 2021, all answered by @netblue30
• https://firejail.wordpress.com/documentation-2/building-custom-profiles/ - Mar 2019
• https://firejail.wordpress.com/documentation-2/firefox-guide/ - Feb 2021
• https://firejail.wordpress.com/documentation-2/linux-capabilities-guide/ - all old or sort of answered
• https://firejail.wordpress.com/2017/05/15/linux-mint-sandboxing-guide/ - comments left to be addressed: starting from the Netflix one, through to the last (Aug 2019)
• https://firejail.wordpress.com/support/ - Feb 2021. This has 280+ comments.
• The blog - the blog after Tips and tricks don't have any comments. That one has 8. I haven't looked at old blog posts, and we should think about what to do with the comments on blog posts
  • replace the comments feature with a note at the bottom pointing users to the GitHub Discussions?
  • let them be separately from GitHub at all?
  • Is the blog moving anywhere?

If anyone wants to continue the work, feel free :)

[SkewedZeppelin]

@tredondo

Perhaps replace the comments feature with a note at the bottom pointing users to the GitHub Discussions?

GitHub (Discussions) requires an account. A comment on the WordPress doesn't. One of the nice things about GitLab is its 'service desk' feature where anyone can email in and an issue is created. Discourse can also be configured this way. More wholesome solutions like traditionally SourceForge or more recently Sourcehut feature a built-in mailing list. @rusty-snake put a lot of effort in remaking the site, it is not an easy task at all. It is sad to see it rot.