blog issueshttps://gitlab.torproject.org/tpo/web/blog/-/issues2020-06-27T14:30:04Zhttps://gitlab.torproject.org/tpo/web/blog/-/issues/22786The blog's search box is hard to find, particularly on high security mode2020-06-27T14:30:04ZteorThe blog's search box is hard to find, particularly on high security modeThere's no line around the search box on the blog, making it look like read-only text. Even worse, in High Security mode in Tor Browser, the search icon becomes a unicode placeholder.There's no line around the search box on the blog, making it look like read-only text. Even worse, in High Security mode in Tor Browser, the search icon becomes a unicode placeholder.HiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/22784Check for external resource being loaded by the tor-bootstrap template2020-06-27T14:30:04ZHiroCheck for external resource being loaded by the tor-bootstrap templateExternal resource prevent the site to be displayed properly on Tor browser.External resource prevent the site to be displayed properly on Tor browser.HiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/22783Remove fontawsome from the blog template2020-06-27T14:30:04ZHiroRemove fontawsome from the blog templateGlyphicons are not loaded on high security level in Tor browser.
The search box now is visible also on high-security mode.Glyphicons are not loaded on high security level in Tor browser.
The search box now is visible also on high-security mode.HiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/22774Figure out how much of each blog post to display on the index (front) page2020-06-30T09:22:11ZRoger DingledineFigure out how much of each blog post to display on the index (front) pageOn the old blog, we put the entirety of each blog post on the index pages. It was a conscious design choice -- it meant fewer posts got listed per index page, but you could actually read the posts by reading the index pages.
Now we have...On the old blog, we put the entirety of each blog post on the index pages. It was a conscious design choice -- it meant fewer posts got listed per index page, but you could actually read the posts by reading the index pages.
Now we have some subset of each post, and sometimes it's just a few lines, and sometimes it's "just" the first 35 bullet points of the changelog we're announcing.
We should figure out if we want to put all of each post, or just a teaser. And if we choose teaser, we should build code or policy that makes us more uniform in how much teaser we pick.
I'm including keyword ux-team because this is another one where they'd be helpful.HiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/22724New blog comment css has only one layer of comment replies2020-06-27T14:30:04ZRoger DingledineNew blog comment css has only one layer of comment replieshttps://blog.torproject.org/comment/269444#comment-269444
is a reply to
https://blog.torproject.org/comment/269430#comment-269430
but with the new css we got for comments last week, they're at the same level of indentation.https://blog.torproject.org/comment/269444#comment-269444
is a reply to
https://blog.torproject.org/comment/269430#comment-269430
but with the new css we got for comments last week, they're at the same level of indentation.HiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/22671Implement design changes to blog.torproject.org2020-06-27T14:30:04ZLinda LeeImplement design changes to blog.torproject.orgWe've taken the time to redesign blog.torproject.org. We think the new design is easier to read, uses the space better, and looks more Tor!
![tor-blogpage-before.png,300px](uploads/tor-blogpage-before.png,300px)
![tor-blogpage-commen...We've taken the time to redesign blog.torproject.org. We think the new design is easier to read, uses the space better, and looks more Tor!
![tor-blogpage-before.png,300px](uploads/tor-blogpage-before.png,300px)
![tor-blogpage-comments.png,300px](uploads/tor-blogpage-comments.png,300px)
Before: too much whitespace, confusing comments, too white.
![tor-blogpage-after.png,300px](uploads/tor-blogpage-after.png,300px)
After: more space used for content, intuitive comments, tor colors.
Since we're finished with the design, the next step is to incorporate all these changes and ship them. These include:
* legacy/trac#22392: removing the left column
* legacy/trac#22395: more intuitive comment threading
* legacy/trac#22510: increasing brand presence
* changes in font hierarchy, specifically h2 not being bold and in all caps.
* changes in color and styling
* including an onion icon next to tor people's comments (people who are registered on the blog) so that people can see which answers are more tor-official--see the attached image. Notice that the color of the onion depends on the color of the comment. For that, I suggest looking at: https://css-tricks.com/cascading-svg-fill-color/
The assets for the new design can be found here: https://projects.invisionapp.com/d/main#/console/11254922/239848960/inspect (look at the top navigation bar, and it has assets)HiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/22655Blog: feed has broken redirection2020-06-27T14:30:04ZcypherpunksBlog: feed has broken redirectionSteps to reproduce:
1. open https://blog.torproject.org/blog/feed , a feed URL provided by the page https://blog.torproject.org/ in any web browser (Tested: Firefox with different modifications, Epiphany)
What happens:
Loading the page...Steps to reproduce:
1. open https://blog.torproject.org/blog/feed , a feed URL provided by the page https://blog.torproject.org/ in any web browser (Tested: Firefox with different modifications, Epiphany)
What happens:
Loading the page fails with too many redirections.
The server sends a "301 Moved Permanently" status to the same URL (https://blog.torproject.org/blog/feed) until the browser aborts loading the page because of too many redirects.
What should happen:
Do not redirect recursively. You might want to redirect to https://blog.torproject.org/rss.xml.HiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/22625New blog events default to today2020-06-27T14:30:05ZRoger DingledineNew blog events default to todayWhen you make a new event on the blog, you can set the Start Time and the End Time. But when you have made the event, suddenly it's the top event on the frontpage. It turns out there's another, optional, time you can set, called "Calenda...When you make a new event on the blog, you can set the Start Time and the End Time. But when you have made the event, suddenly it's the top event on the frontpage. It turns out there's another, optional, time you can set, called "Calendar date", and if you don't set it, it fills in today.
We should make it fill in the same date as Start Time instead. Or make it leave the optional thing empty, and use the Start Time if Calendar date isn't filled in.
Long term goal should be having drupal copy the start date into the calendar date.HiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/22624"See all upcoming events" shows you events in 20082020-06-27T14:30:05ZRoger Dingledine"See all upcoming events" shows you events in 2008Go to the frontpage of the blog, and then click on "see all upcoming events" on the right column. You end up at
https://blog.torproject.org/events/upcoming
which starts off telling me about a January 24, 2008 event.
There is a subtle li...Go to the frontpage of the blog, and then click on "see all upcoming events" on the right column. You end up at
https://blog.torproject.org/events/upcoming
which starts off telling me about a January 24, 2008 event.
There is a subtle link called "See the events calendar" which brings us to
https://blog.torproject.org/events/month
which I think is the calendar we are hoping to see after the first click.HiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/22622You aren't allowed to use tags that haven't already been used2020-06-27T14:30:05ZRoger DingledineYou aren't allowed to use tags that haven't already been usedWhen you draft a new blog post, and pick the tag "foo", it prevents you from publishing, because "foo" is not a known tag.
It looks like you're only allowed to choose from tags that were used on the old blog?
The better behavior is to ...When you draft a new blog post, and pick the tag "foo", it prevents you from publishing, because "foo" is not a known tag.
It looks like you're only allowed to choose from tags that were used on the old blog?
The better behavior is to let people pick whatever tags they want to pick.HiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/22557Comment pagination links could go to `#comments` anchors2020-06-27T14:30:05ZDavid Fifielddcf@torproject.orgComment pagination links could go to `#comments` anchorsOn a page like https://blog.torproject.org/blog/tor-browser-70-released#comments, the comment pagination links at the bottom could have `#comments` appended to them, so that the page scrolls directly to the comments and you don't have to...On a page like https://blog.torproject.org/blog/tor-browser-70-released#comments, the comment pagination links at the bottom could have `#comments` appended to them, so that the page scrolls directly to the comments and you don't have to scroll down over the article again.
I mean these links at the bottom:
```
1 / 2 / 3 / Next › Last »
```
So, for example, clicking "Next" would take you to https://blog.torproject.org/blog/tor-browser-70-released?page=1#comments.HiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/22549Put more comments per page?2020-06-27T14:30:05ZRoger DingledinePut more comments per page?I'm sure this is a setting somewhere, but I have no clue where to find it.
In the old blog, we could fit a lot of comments before you had to click next.
That way you could search on the page.
In the new blog, it seems like after 10 co...I'm sure this is a setting somewhere, but I have no clue where to find it.
In the old blog, we could fit a lot of comments before you had to click next.
That way you could search on the page.
In the new blog, it seems like after 10 comments you're out of space and on to a second page.HiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/22530Redirection loop with disabled js on every page of blog.torproject.org2020-07-02T19:08:40ZcypherpunksRedirection loop with disabled js on every page of blog.torproject.orgFor several years everyone was able to post on https://blog.torproject.org without enabling JavaScript and other dangerous things.
Observed behaviour: can not post unless slider set to medium or low
Expected behaviour: high security sup...For several years everyone was able to post on https://blog.torproject.org without enabling JavaScript and other dangerous things.
Observed behaviour: can not post unless slider set to medium or low
Expected behaviour: high security supported
Steps to reproduce: try to post at https://blog.torproject.org with security slider on highHiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/22510Increasing brand presence on the Tor blog (i.e. to make it look more Tor-y)2020-06-27T14:30:05ZLinda LeeIncreasing brand presence on the Tor blog (i.e. to make it look more Tor-y)During the UX ticket triaging discussion, we realized that various people didn't like how bright the tor blog was, wanted more tor in the blog, and many other things. Let's intentionally design a color scheme and design for our new blog!...During the UX ticket triaging discussion, we realized that various people didn't like how bright the tor blog was, wanted more tor in the blog, and many other things. Let's intentionally design a color scheme and design for our new blog!
Possible options:
* using tor colors (light theme with tor-purple and tor-green accents, dark theme with tor-purple and tor-green accents, predominantly tor-purple theme, or predominantly tor-green theme)
* adding more graphics (onions, tor logo, etc.)
* making it look like our other sites (but torproject.org is not so great that we want it to necessarily look like it, looking at metrics.torproject.org can give ideas)
Resources:
* [How the current blog looks](https://blog.torproject.org/)
* [How the old blog used to look](https://web.archive.org/web/20170426133309/https://blog.torproject.org/blog/tor-browser-70a3-released)
* [Tor style guide](https://github.com/uracreative/tor-styleguide/blob/master/RGB/Tor%20Style%20Guide%20Complete%20-%20RGB.pdf)Antonelaantonela@torproject.orgAntonelaantonela@torproject.orghttps://gitlab.torproject.org/tpo/web/blog/-/issues/22509Put "Reply" bar at the bottom of comment2020-06-27T14:30:05ZcypherpunksPut "Reply" bar at the bottom of commentsubjsubjHiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/22464Upcoming events are in reversed order2020-06-27T14:30:06ZcypherpunksUpcoming events are in reversed orderCopied from ticket:22383#comment:9
>It looks like the events are ordered "farthest in the future" to "nearest in the future"?
>
>Which means that on the frontpage, we have events in August, and the events in June and July are hidden?Copied from ticket:22383#comment:9
>It looks like the events are ordered "farthest in the future" to "nearest in the future"?
>
>Which means that on the frontpage, we have events in August, and the events in June and July are hidden?HiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/22443Direct links to comments (old style) no longer work2020-06-27T14:30:06ZcypherpunksDirect links to comments (old style) no longer workLet say open legacy/trac#22153 and see https://blog.torproject.org/blog/tor-browser-70a3-released#comment-263144 in it. The blog will be shown at the beginning. It now wants strange https://blog.torproject.org/comment/263144#comment-2631...Let say open legacy/trac#22153 and see https://blog.torproject.org/blog/tor-browser-70a3-released#comment-263144 in it. The blog will be shown at the beginning. It now wants strange https://blog.torproject.org/comment/263144#comment-263144 permalink to work.HiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/22442Blog Search doesn't search in comments2020-06-27T14:30:06ZcypherpunksBlog Search doesn't search in commentsIt gives false sense of searching through the blog, but can't find anything written in comments.It gives false sense of searching through the blog, but can't find anything written in comments.HiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/22436Some blog users have blogger role, and others don't?2020-06-27T14:30:06ZRoger DingledineSome blog users have blogger role, and others don't?On the https://blog.torproject.org/admin/people page it turns out some people have the "blogger" role, and other people don't.
There are now two intermediate roles, "authenticated user" and "blogger". I guess that was true on the old bl...On the https://blog.torproject.org/admin/people page it turns out some people have the "blogger" role, and other people don't.
There are now two intermediate roles, "authenticated user" and "blogger". I guess that was true on the old blog too, but I don't think we had anybody in the "has an account but doesn't have the blogger role" there. Somehow some of the users lost that role in the transition. Or maybe we did have that distinction, but the people without the blogger role could still blog, edit comments, etc on the old blog. I'm not sure.
I just went through and added the blogger role to most people, so it isn't an urgent issue now.
Is there a downside to merging the two roles, that is, simplifying by making everybody who has an account into a blogger?
I guess we could go the other way too, which is letting ordinary people make accounts on our blog, so they can be the same human each time they comment, and maybe even so they can bypass captchas and stuff. Is there a downside to that? :)HiroHirohttps://gitlab.torproject.org/tpo/web/blog/-/issues/22426Missing `#comments` anchor on article pages2020-06-27T14:30:06ZDavid Fifielddcf@torproject.orgMissing `#comments` anchor on article pagesClicking an "_X_ comments" link from the index takes you to a URL with a `#comments` anchor at the end, for example:
https://blog.torproject.org/blog/we-are-upgrading-our-blog#comments
It's supposed to scroll you down to the comments, ...Clicking an "_X_ comments" link from the index takes you to a URL with a `#comments` anchor at the end, for example:
https://blog.torproject.org/blog/we-are-upgrading-our-blog#comments
It's supposed to scroll you down to the comments, but the article page is missing the appropriate anchor.
This bit of HTML:
```
<section>
<h2>Comments</h2>
```
needs to change to something like this:
```
<section id="comments">
<h2>Comments</h2>
```HiroHiro