blog issueshttps://gitlab.torproject.org/tpo/web/blog/-/issues2024-01-11T00:06:15Zhttps://gitlab.torproject.org/tpo/web/blog/-/issues/40068Comms: managing embargo and time sensitive blog posts2024-01-11T00:06:15ZGusComms: managing embargo and time sensitive blog postsAt times, the Comms Team must issue statements or announcements that are either under embargo or scheduled for release at a specific time. The availability of public merge requests to everyone can hinder this process. However, GitLab can...At times, the Comms Team must issue statements or announcements that are either under embargo or scheduled for release at a specific time. The availability of public merge requests to everyone can hinder this process. However, GitLab can provide an easy solution: by modifying the merge request permission and restricting access to only members of blog repository.
If there is consensus on this, we can compile a list of people from other teams who require access and add them as members of this repository.
(cc @pavel)GusGushttps://gitlab.torproject.org/tpo/web/blog/-/issues/40015Build time is out of control2023-05-16T19:29:38ZJérôme Charaouilavamind@torproject.orgBuild time is out of controlThe blog has a little over 1500 pages but is taking around 27 minutes to build on my desktop machine and over an hour on CI. It seems this is related to the design of Lektor as discussed in the upstream issue tracker: https://github.com/...The blog has a little over 1500 pages but is taking around 27 minutes to build on my desktop machine and over an hour on CI. It seems this is related to the design of Lektor as discussed in the upstream issue tracker: https://github.com/lektor/lektor/issues/180
Using the [limit-dependencies](https://github.com/dairiki/lektor-limit-dependencies) plugin may help cut build times down to manageable values.Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/web/blog/-/issues/40041Scrolling long blog comments will hide them into the corner of the screen2023-04-11T13:22:39ZshanzhanzScrolling long blog comments will hide them into the corner of the screen**Summarize the bug encountered concisely.**
Scrolling down long comments in some websites (including TPO blog) will make the comments go to the right more and more until the page disappear (screen search engine also wont solve the issu...**Summarize the bug encountered concisely.**
Scrolling down long comments in some websites (including TPO blog) will make the comments go to the right more and more until the page disappear (screen search engine also wont solve the issue). (Check the video about it)
### Steps to reproduce:
**How one can reproduce the issue - this is very important.**
1. Make your TB using safest security
2. visit https://blog.torproject.org/new-release-tor-browser-90/
3. Keep scrolling down
4. There you go
### Environment
**Which operating system are you using?**
Debian 11
**Which installation method did you use?**
Downloaded from website
### Relevant logs and/or screenshots
![cant_scroll_down](/uploads/74fa9ddea0fe0cfe991ab645500c3e10/cant_scroll_down.mp4)Jérôme Charaouilavamind@torproject.orgJérôme Charaouilavamind@torproject.orghttps://gitlab.torproject.org/tpo/web/blog/-/issues/40012Add categories to events2022-05-04T23:35:38ZJérôme Charaouilavamind@torproject.orgAdd categories to eventsIt would be nice to be able to categorize events so they could show up on index pages and feeds, but this is difficult because there doesn't seem to be a way to change `items = site.get('/blog').children` into a query that grabs both eve...It would be nice to be able to categorize events so they could show up on index pages and feeds, but this is difficult because there doesn't seem to be a way to change `items = site.get('/blog').children` into a query that grabs both events and blog posts. Notably, the `.children` method is *not* recursive.
This Lektor issue might be related: https://github.com/lektor/lektor/issues/445https://gitlab.torproject.org/tpo/web/blog/-/issues/40026Improve navbar for small screens2022-05-04T23:35:38ZJérôme Charaouilavamind@torproject.orgImprove navbar for small screensThe links in the top navbar could be displayed using a CSS burger menu on small screens, as it was on Drupal.The links in the top navbar could be displayed using a CSS burger menu on small screens, as it was on Drupal.https://gitlab.torproject.org/tpo/web/blog/-/issues/40010Evaluate options to integrate search on the new blog2022-02-18T08:35:30ZJérôme Charaouilavamind@torproject.orgEvaluate options to integrate search on the new blogThe old Drupal blog had a search function, and since the amount of content justifies it, we should consider adding a search function on the new Lektor blog.The old Drupal blog had a search function, and since the amount of content justifies it, we should consider adding a search function on the new Lektor blog.https://gitlab.torproject.org/tpo/web/blog/-/issues/40009Ensure all blog posts have at least 1 tag/category2022-01-12T19:39:44ZJérôme Charaouilavamind@torproject.orgEnsure all blog posts have at least 1 tag/categoryOnce the blog is migrated using the new tags mapping, we should ensure all existing blog posts have at least one tag.Once the blog is migrated using the new tags mapping, we should ensure all existing blog posts have at least one tag.https://gitlab.torproject.org/tpo/web/blog/-/issues/40028Add a 404 page2021-11-24T19:02:06ZJérôme Charaouilavamind@torproject.orgAdd a 404 pageCurrently, the HTTP 404 page is the default one from Apache. We can probably whip up a nicer looking one.Currently, the HTTP 404 page is the default one from Apache. We can probably whip up a nicer looking one.