blog issueshttps://gitlab.torproject.org/tpo/web/blog/-/issues2021-12-13T19:21:54Zhttps://gitlab.torproject.org/tpo/web/blog/-/issues/40011Fossilize old Drupal blog2021-12-13T19:21:54ZJérôme Charaouilavamind@torproject.orgFossilize old Drupal blogIt would be a good idea to fossilize and archive the old Drupal blog, it might come in handy eventually.
@anarcat had some ideas about how we can proceed.It would be a good idea to fossilize and archive the old Drupal blog, it might come in handy eventually.
@anarcat had some ideas about how we can proceed.Launch support's Forum and Blog migrationJérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/web/blog/-/issues/40008Convert tags to smaller set of blog post categories2021-11-17T15:18:04ZJérôme Charaouilavamind@torproject.orgConvert tags to smaller set of blog post categoriesIn the process of migrating the Drupal site to Lektor, @duncan and I agreed it might make sense to replace the blog post tags with a predefined set of categories. This would simplify the Lektor site structure since we'd be able to forgo ...In the process of migrating the Drupal site to Lektor, @duncan and I agreed it might make sense to replace the blog post tags with a predefined set of categories. This would simplify the Lektor site structure since we'd be able to forgo the use of the `lektor-tags` module and allow us to provide RSS/Atom feeds of posts in each category.
The list of tags currently used on the blog is available here: https://pad.riseup.net/p/QqaP7feFvQlPJrDHmSyXLaunch support's Forum and Blog migrationJérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/web/blog/-/issues/40007A very simple author's page2021-08-31T13:39:08ZGusA very simple author's pageAs we already have a tag page, can we have an authors' page, ie, a page that list all the blog posts made by someone?As we already have a tag page, can we have an authors' page, ie, a page that list all the blog posts made by someone?Launch support's Forum and Blog migrationJérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/web/blog/-/issues/40006Add markup for sharing links on social media sites2021-08-31T13:55:31ZdonutsAdd markup for sharing links on social media sitesComms often have to create and upload separate images when sharing links on Facebook, Twitter and Mastodon as our current blog posts don't generate link previews on the timeline.
To reduce this effort, could we add the appropriate share...Comms often have to create and upload separate images when sharing links on Facebook, Twitter and Mastodon as our current blog posts don't generate link previews on the timeline.
To reduce this effort, could we add the appropriate share metatags for the following platforms:
- [Facebook](https://developers.facebook.com/docs/sharing/webmasters#markup)
- [Twitter](https://developer.twitter.com/en/docs/twitter-for-websites/cards/overview/markup)
- [Mastodon](https://docs.joinmastodon.org/entities/card/) (it seems this uses Opengraph too, so no further action may be necessary)
Full-sized cards featuring the blog post's title, description and banner image would be great, please.Launch support's Forum and Blog migrationJérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/web/blog/-/issues/40004Migrate the blog out of Drupal and into a static site generator with a commen...2022-01-26T16:56:00ZGabagaba@torproject.orgMigrate the blog out of Drupal and into a static site generator with a comment service### Content
* [x] Import blog posts from Drupal
* [x] Import events from Drupal
* [x] Import comment archive
* [x] Configure RSS/Atom feeds (posts + events)
* [x] Implement categories to replace tags (depends on https://gitlab.torp...### Content
* [x] Import blog posts from Drupal
* [x] Import events from Drupal
* [x] Import comment archive
* [x] Configure RSS/Atom feeds (posts + events)
* [x] Implement categories to replace tags (depends on https://gitlab.torproject.org/tpo/web/blog/-/issues/40008)
* [x] Test Discourse comments embedding (depends on https://gitlab.torproject.org/tpo/tpa/team/-/issues/40183)
* [x] Test draft post feature
### Layout
* [x] Import relevant CSS styles from old blog
* [x] Setup 2-column responsive layout
* [x] Mirror header and footer contents from other Tor websites
### Deployment
* [x] Ensure functioning newsletter image URL redirections ([example](https://newsletter.torproject.org/archive/2021-11-01-privacy-is-a-human-right/))
* [x] Plan/implement publishing moratorium and comments section closure on Drupal
* [x] Full, final content import from Drupal
* [x] Setup static web mirrors for new site
* [x] Transition `blog.torproject.org` address
* [x] Fossilize old Drupal site (tpo/web/blog#40011)
* [ ] ~~Wind down Pantheon subscription~~ (tpo/tpa/team#40526)
* [ ] ~~Retire (or reconfigure) cache*.torproject.org machines~~ (tpo/tpa/team#40527)
### Workflow
* [x] Implement Review Apps for easy MR previews
* [x] Document final publishing workflow of the new blog
Documentation of the project requirements lives at https://gitlab.torproject.org/tpo/tpa/team/-/wikis/service/blogLaunch support's Forum and Blog migrationJérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.org2021-11-17https://gitlab.torproject.org/tpo/web/blog/-/issues/33115Migrating the blog to a static web site with Lektor2021-07-22T19:30:16ZHiroMigrating the blog to a static web site with LektorWe 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...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 discourse.org. I have actually been in contact with discourse and they have offered to run a forum for us for free (legacy/trac#33105). Addittionally they would run an .onion and a torproject.org 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 blog.torproject.org.
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.Launch support's Forum and Blog migrationHiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/22397Add a (single) onion service for the new tor blog2021-11-16T14:10:59ZteorAdd a (single) onion service for the new tor blogWhen we asked for this for the old blog, it wasn't technically feasible (or it was a legacy system, so we decided not to do it).
I hope that onion service compatibility (mainly URL rewrites) was one of the requirements for the new blog.When we asked for this for the old blog, it wasn't technically feasible (or it was a legacy system, so we decided not to do it).
I hope that onion service compatibility (mainly URL rewrites) was one of the requirements for the new blog.Launch support's Forum and Blog migrationJérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/web/blog/-/issues/40044Comments are broken on onion version2023-06-26T16:53:02ZsreadyComments are broken on onion versionWhen visiting some post through onion service ([example](http://pzhdfe7jraknpj2qgu5cz2u3i4deuyfwmonvzu5i3nyw4t4bmg7o5pad.onion/new-alpha-release-tor-browser-120a1/)) with JS enabled, there is a browser error instead of comments section. ...When visiting some post through onion service ([example](http://pzhdfe7jraknpj2qgu5cz2u3i4deuyfwmonvzu5i3nyw4t4bmg7o5pad.onion/new-alpha-release-tor-browser-120a1/)) with JS enabled, there is a browser error instead of comments section. Looks related to CSP.Sponsor 9 - Phase 6 - Usability and Community Intervention on Support for Democracy and Human RightsJérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.org2023-06-30https://gitlab.torproject.org/tpo/web/blog/-/issues/13264integrate the new jekyll blog into the tor website homepage2020-06-27T14:30:11ZAndrew Lewmanintegrate the new jekyll blog into the tor website homepageintegrate the new jekyll blog into the tor website homepage.
With the new jekyll blog platform, we can integrate the latest posts into the index.wml which creates the home page on the main www.torproject.org site.integrate the new jekyll blog into the tor website homepage.
With the new jekyll blog platform, we can integrate the latest posts into the index.wml which creates the home page on the main www.torproject.org site.2014 Tor Blog Replacementhttps://gitlab.torproject.org/tpo/web/blog/-/issues/13263test migration of comments to juvia2020-06-27T14:30:11ZAndrew Lewmantest migration of comments to juviaTest a migration of blog comments to juviaTest a migration of blog comments to juvia2014 Tor Blog Replacementhttps://gitlab.torproject.org/tpo/web/blog/-/issues/13262test blog migration2020-06-27T14:30:11ZAndrew Lewmantest blog migrationTest a migration of the blog to the new jekyll systemTest a migration of the blog to the new jekyll system2014 Tor Blog Replacementhttps://gitlab.torproject.org/tpo/web/blog/-/issues/13118Design an updated look and feel for the comment system2020-06-27T14:30:11ZAndrew LewmanDesign an updated look and feel for the comment systemDesign an updated look and feel for the comment systemDesign an updated look and feel for the comment system2014 Tor Blog Replacementhttps://gitlab.torproject.org/tpo/web/blog/-/issues/10480Export comments from current blog2020-06-27T14:30:11ZAndrew LewmanExport comments from current blogExport comments from current blog in some sane format and some ability to import the threads, etc. into a new system.Export comments from current blog in some sane format and some ability to import the threads, etc. into a new system.2014 Tor Blog Replacementhttps://gitlab.torproject.org/tpo/web/blog/-/issues/10479Export blog posts from current blog2020-06-27T14:30:12ZAndrew LewmanExport blog posts from current blogExport everything in some sane format for future imports (html vs. markdown?)Export everything in some sane format for future imports (html vs. markdown?)2014 Tor Blog Replacementhttps://gitlab.torproject.org/tpo/web/blog/-/issues/40070write a blog post about the static mirror system2024-03-14T15:12:02Zanarcatwrite a blog post about the static mirror systemI found [this post](https://alexcabal.com/posts/standard-ebooks-and-classic-web-tech) to be pretty interesting. I wish I could write about some fancy new high-tech system we've built in TPA that's the cutting edge of technology, but the ...I found [this post](https://alexcabal.com/posts/standard-ebooks-and-classic-web-tech) to be pretty interesting. I wish I could write about some fancy new high-tech system we've built in TPA that's the cutting edge of technology, but the reality is that we're a hodgepodge collection of legacy systems we're keeping alive by a wise combination of "if it ain't broken don't fix it" and "okay, this is too horrible, let's fix that tiny piece", migrating one system at a time toward modernity.
The static mirror system is an excellent example of this. When I arrived, it was mostly built from shell servers and... Jenkins, which was hard to use and generally disliked. We migrated to GitLab and built a shim to avoid having to replace the entire system. That handful of servers is pumping out gigabits per second, it's easy to deploy and scale out (although *that* could be made easier).
This is mostly summarizing and glorifying the docs I've already written in the [service docs](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/howto/static-component/).
This would be, therefore, an interesting blog post on its own, but I think it could also serve as great advertisement for the job posting (tpo/tpa/team#41542).anarcatanarcathttps://gitlab.torproject.org/tpo/web/blog/-/issues/40069Give Tails Release Managers the Developer status2024-02-27T14:06:05ZanonymGive Tails Release Managers the Developer statusAccording to the [documentation](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/service/blog#how-to-write-a-new-blog-post-in-gitlab) the `Developer` status is required to create a new branch as part of making a new blog post (which I...According to the [documentation](https://gitlab.torproject.org/tpo/tpa/team/-/wikis/service/blog#how-to-write-a-new-blog-post-in-gitlab) the `Developer` status is required to create a new branch as part of making a new blog post (which I guess explains why I don't see the "New branch" button). So, in order for for Tails Release Managers to be able to publish blog posts, we need that status.
The current Tails Release Managers that have accounts on your Gitlab and need this status are:
* [anonym](https://gitlab.torproject.org/anonym)
* [boyska](https://gitlab.torproject.org/boyska)
* [intrigeri](https://gitlab.torproject.org/intrigeri)Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/web/blog/-/issues/40067Update Tor policies link2023-11-08T21:43:20ZGusUpdate Tor policies linkLet's update the policies gitlab link to https://community.torproject.org/policiesLet's update the policies gitlab link to https://community.torproject.org/policieshttps://gitlab.torproject.org/tpo/web/blog/-/issues/40066Update CoC link2023-10-25T21:24:35ZGusUpdate CoC linkTor Code of Conduct document moved from gitweb to gitlab (https://gitlab.torproject.org/tpo/community/policies/-/blob/master/code_of_conduct.txt?ref_type=heads).
We need to change the link: https://gitlab.torproject.org/tpo/web/blog/-/b...Tor Code of Conduct document moved from gitweb to gitlab (https://gitlab.torproject.org/tpo/community/policies/-/blob/master/code_of_conduct.txt?ref_type=heads).
We need to change the link: https://gitlab.torproject.org/tpo/web/blog/-/blob/main/templates/macros/blog.html#L87Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/web/blog/-/issues/40065Replace fallback Tor Browser images2023-10-18T18:15:57ZdonutsReplace fallback Tor Browser imagesSince time immemorial the applications team have been using [this image as a fallback](https://gitlab.torproject.org/tpo/web/blog/-/blob/main/assets/static/images/blog/tor-browser.png) for Tor Browser related posts that don't have a dedi...Since time immemorial the applications team have been using [this image as a fallback](https://gitlab.torproject.org/tpo/web/blog/-/blob/main/assets/static/images/blog/tor-browser.png) for Tor Browser related posts that don't have a dedicated image.
I was wondering if we can replace this with three images going forward:
- For general posts not related to a specific release, use this generic graphic: [tor-browser-stable](/uploads/6dbfceba369800a78e0249b370ad0e02/tor-browser-stable.png)
- For subsequent releases in the 13.0 series, use this graphic: [tor-browser-13](/uploads/64823b0fa72da3a8629a3969e4fab0ad/tor-browser-13.png)
- For alpha release posts, use this new dedicated alpha graphic: [tor-browser-alpha](/uploads/599063c3e193722f533f04c6271a7b99/tor-browser-alpha.png)
What do you think @richard? also FYI @pierovdonutsdonutshttps://gitlab.torproject.org/tpo/web/blog/-/issues/40064Please add this event to our blog2023-04-04T15:40:48ZIsabela FernandesPlease add this event to our blogPalestine Digital Activism Forum 2023
23-25 May
https://pdaf.net/
Hosted by 7amleh – The Arab Center for the Advancement of Social Media. Members of the Tor Project will speak at this event.
ps: there is a longer explanation of the ...Palestine Digital Activism Forum 2023
23-25 May
https://pdaf.net/
Hosted by 7amleh – The Arab Center for the Advancement of Social Media. Members of the Tor Project will speak at this event.
ps: there is a longer explanation of the event, but I am not sure if it fits in the events area. I am pasting it here just in case. Who from Tor is speaking: Isabela, Raya and Nighat.
7amleh – The Arab Center for the Advancement of Social Media launched the first Palestine Digital Activism Forum in 2017, and since then it has become one of 7amleh’s annual events.
The PDAF aims to:
-Provide a platform to discuss the challenges that Palestinians face the Palestinian civil society to protect Palestinian digital rights and digital activists working on the Palestinian cause in a positive and constructive manner.
-Provide a space for exchanging social media experiences and expertise in order to develop social media activism inside and outside Palestine and to develop strategies to address the serious challenges and threats faced by digital activists.
-Link the work of local organizations and movements with international counterparts to exchange experiences and to find solutions to the dilemmas they face and ways to cooperate and coordinate actions.Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.org