March 2021 - tor-commits - lists.torproject.org

[community/staging] better strings for l10n
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 5d985dbcaabaef9f6a1f6a1273ca8ad0e06ece3e Author: emma peel <emma.peel(a)riseup.net> Date: Sat Oct 12 11:56:59 2019 +0200 better strings for l10n --- content/onion-services/overview/contents.lr | 26 ++++++++++++++++++-------- 1 file changed, 18 insertions(+), 8 deletions(-) diff --git a/content/onion-services/overview/contents.lr b/content/onion-services/overview/contents.lr index 330dea4..1122aa1 100644 --- a/content/onion-services/overview/contents.lr +++ b/content/onion-services/overview/contents.lr @@ -16,7 +16,8 @@ html: two-columns-page.html --- body: -Onion services are services that can only be accessed over Tor. Running an onion service gives your users all the security of HTTPS with the added privacy benefits of Tor Browser. +Onion services are services that can only be accessed over Tor. +Running an onion service gives your users all the security of HTTPS with the added privacy benefits of Tor Browser. ## Why onion services? @@ -29,32 +30,41 @@ Onion services are an overlay network on top of TCP/IP, so in some sense IP addr ### End-to-end authentication -When a user visits a particular onion, they know that the content they are seeing can only come from that particular onion. No impersonation is possible, which is generally not the case. Usually, reaching a website does not mean that a man-in-the-middle did not reroute to some other location (e.g. DNS attacks). +When a user visits a particular onion, they know that the content they are seeing can only come from that particular onion. +No impersonation is possible, which is generally not the case. +Usually, reaching a website does not mean that a man-in-the-middle did not reroute to some other location (e.g. DNS attacks). ### End-to-end encryption -Onion service traffic is encrypted from the client to the onion host. This is like getting strong SSL/HTTPS for free. +Onion service traffic is encrypted from the client to the onion host. +This is like getting strong SSL/HTTPS for free. ### NAT punching -Is your network filtered and you can't open ports on your firewall? This could happen if you are in a university campus, an office, an airport, or pretty much anywhere. Onion services don't need open ports because they punch through NAT. They only establish outgoing connections. +Is your network filtered and you can't open ports on your firewall? +This could happen if you are in a university campus, an office, an airport, or pretty much anywhere. +Onion services don't need open ports because they punch through NAT. They only establish outgoing connections. ## The Onion Service Protocol: Overview -Now the question becomes **what kind of protocol is needed to achieve all these properties?** Usually, people connect to an IP address and are done, but how can you connect to something that does not have an IP address? +Now the question becomes **what kind of protocol is needed to achieve all these properties?** +Usually, people connect to an IP address and are done, but how can you connect to something that does not have an IP address? In particular, an onion service's address looks like this: `vww6ybal4bd7szmgncyruucpgfkqahzddi37ktceo3ah7ngmcopnpyyd.onion` -This looks weird and random because it's the _identity public key_ of the onion service. That's one of the reasons we can achieve the security properties above. +This looks weird and random because it's the _identity public key_ of the onion service. +That's one of the reasons we can achieve the security properties above. -The onion service protocol uses the Tor network so that the client (Alice) can introduce itself to the service (Bob), and then set up a rendezvous point with the service over the Tor network. Here is a detailed breakdown of how this happens: +The onion service protocol uses the Tor network so that the client (Alice) can introduce itself to the service (Bob), and then set up a rendezvous point with the service over the Tor network. +Here is a detailed breakdown of how this happens: ### Act 1: Where the onion service sets up its introduction points ![Onion Services: Step 1](/static/images/onion-services/overview/tor-onion-services-1.png) -As the first step in the protocol, Bob (the onion service) contacts a bunch of Tor relays and asks them to act as his _introduction points_, by establishing long-term circuits to them. These circuits are anonymized circuits, so Bob does not reveal his locations to his introduction points. +As the first step in the protocol, Bob (the onion service) contacts a bunch of Tor relays and asks them to act as his _introduction points_, by establishing long-term circuits to them. +These circuits are anonymized circuits, so Bob does not reveal his locations to his introduction points. As part of this step, Bob gives its introduction point a special "authentication key", so that if any clients come for introductions later the introduction point can use that key to match them to Bob.

1 0

[community/staging] add user research guidelines
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 3d9fff6c216a76b91da5bddede82d0cd8ff520a7 Author: Antonela <hola(a)antonela.me> Date: Fri Oct 18 10:38:11 2019 -0300 add user research guidelines close https://dip.torproject.org/torproject/ux/team/issues/26 --- content/user-research/guidelines/contents.lr | 75 ++++++++++++++++++++++++++++ 1 file changed, 75 insertions(+) diff --git a/content/user-research/guidelines/contents.lr b/content/user-research/guidelines/contents.lr new file mode 100644 index 0000000..d208e25 --- /dev/null +++ b/content/user-research/guidelines/contents.lr @@ -0,0 +1,75 @@ +section: user research +--- +section_id: user-research +--- +title: User Research Guidelines +--- +subtitle: We collect only necessary data to improve our services. +--- +hide: yes +--- +key: 3 +--- +html: two-columns-page.html +--- +body: + +Congrats! You're going to run your first User Research for Tor - and we are delighted to have you on board! +In this place, you will find helpful guidelines that are designed to make your research easier for you and your audience. + +First of all, make sure you read the [Tor Code of Conduct](https://linktocodeofconduct). + +## Respect privacy +At Tor, we collect only necessary data to improve our services; we don't collect invasive data about user behaviors - we test our software, not people. + +## Be a good listener and open-minded +Listening is a skill to build bridges. In Tor, we want people to build bridges, not walls - and we believe this is not just for our services, but as well for our communities. Get in here to read some suggestions about being a better listener and make a great research experience. <link> + +## Learn +When we are in Tor training, we listen to the stories people tell us about their context, about the laws of the Internet, and the difficulties they are going through. This is how we learn how we can help and create new mechanisms to facilitate access to information through Tor products. When we listen, we do research, we learn. + +## Describe and Ask for consent +We don't collect names or contact details of interview participants, and any time you're going to receive impressions, surveys, or records, you should ask for their consent to participate - this should be recorded or registered in the form. + +You'd love to read about your experiences during the training, product testing, and interviews. There are a few ways to do this: + +* Scenario: describe the process of the test you ran. +* Demographics: While we are not interested in specific characteristics of our audience, or binary attributes, we must know the total reach of your Tor training. You should take [this material]() with you on the day of your research, distribute it among participants, and answer their questions about how to fill it in if they have any. +* Interview Process: Thank the participant for their willingness to participate in this process and explain that we are testing the product, not them. The interview should not last longer than 20 minutes, you can record if you wish, but you can also take notes on the printed material you will carry with you (or on your computer). Thank the participant again and end the interview. +Send us the result - you don't have to write a report, we can do this data analysis with the material you collected. + + +## Coordinate with the trainer and the Tor UX team +You're not doing all this work alone - we will support you with meetings, guides, and mentorship if you want. You can join us at any time on our IRC channel #tor-ux and our [mailing list](). + +You must be aligned about the agenda and time to run interviews (if that is the case) during the end of the training. **We strongly recommend that you go through the program of the exercise with the trainer**. Also, we want you two to coordinate feedbacks together — both for you and for your audience. + +By the beginning of the training, be sure to let everyone know whats your role there and why you're taking notes of the practice. + +## Get prepared! +Print and bring with you the material that you will need to run the research - that will probably be something like: + +* Demographics +* Usability test +* Usability methodology + +It is easier to have this material printed and in hands, but if you prefer, you can also type it on your computer. + +Keep in mind that you might not have a useful Internet in the venue, so if you're going to install a Tor feature with someone during the interview, you may need to have it downloaded before the training. + +## Report to Tor UX team +Before ending the training, coordinate with the trainer the feedbacks, you two should work together to hand out post-its for the audience; you can give one post-it on each color and ask them to fill it with what they think about: 1. the service they just learned; 2. Tor project; and 3. Tor, in general. It can also be questions - keep in mind that every feedback is proper feedback. + +We must hear back from you. We want to know how the training and the research were for you, how we can improve our support, and also if you're going to keep running Tor User Research. Please, fill out [this form](https://limesurvey), by the end of it, we will also ask your address to send to you a researcher kit (t-shirts and stickers). +We hope to hear back from you very soon! + +You can find our document to report [here](https://linkto). But if you think you won't have time to gather and report in this format, we would love to have another way to get the material you collected. You can take pictures or send your 'raw' notes for us. + +## Additional links + +* [Strength in Numbers: Usable Tools Don't Need to Be Invasive](https://blog.torproject.org/strength-numbers-usable-tools-dont-ne… + +There are plenty of documents online about how to run a User Research, here you can find some of them: +* [Design Kit: The Human-Centered Design Toolkit](https://www.ideo.com/post/design-kit) +* [A collection of activities, the Exploratorium facilitates a participatory design and development process](https://okthanks.com/exploratorium) +* [Knowledge Base](https://simplysecure.org/knowledge-base/)

1 0

[community/staging] review content, add links
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 5b70c18d816bd835fdda8cb069564ca9c588238a Author: Antonela <hola(a)antonela.me> Date: Fri Oct 18 10:57:58 2019 -0300 review content, add links --- content/user-research/guidelines/contents.lr | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/content/user-research/guidelines/contents.lr b/content/user-research/guidelines/contents.lr index d208e25..a036343 100644 --- a/content/user-research/guidelines/contents.lr +++ b/content/user-research/guidelines/contents.lr @@ -2,6 +2,8 @@ section: user research --- section_id: user-research --- +color: primary +--- title: User Research Guidelines --- subtitle: We collect only necessary data to improve our services. @@ -17,7 +19,7 @@ body: Congrats! You're going to run your first User Research for Tor - and we are delighted to have you on board! In this place, you will find helpful guidelines that are designed to make your research easier for you and your audience. -First of all, make sure you read the [Tor Code of Conduct](https://linktocodeofconduct). +First of all, make sure you read the [Tor Code of Conduct](https://gitweb.torproject.org/community/policies.git/tree/code_of_…. ## Respect privacy At Tor, we collect only necessary data to improve our services; we don't collect invasive data about user behaviors - we test our software, not people. @@ -40,7 +42,7 @@ Send us the result - you don't have to write a report, we can do this data analy ## Coordinate with the trainer and the Tor UX team -You're not doing all this work alone - we will support you with meetings, guides, and mentorship if you want. You can join us at any time on our IRC channel #tor-ux and our [mailing list](). +You're not doing all this work alone - we will support you with meetings, guides, and mentorship if you want. You can join us at any time on our IRC channel #tor-ux and our [mailing list](https://lists.torproject.org/cgi-bin/mailman/listinfo/ux). You must be aligned about the agenda and time to run interviews (if that is the case) during the end of the training. **We strongly recommend that you go through the program of the exercise with the trainer**. Also, we want you two to coordinate feedbacks together — both for you and for your audience. @@ -71,5 +73,5 @@ You can find our document to report [here](https://linkto). But if you think you There are plenty of documents online about how to run a User Research, here you can find some of them: * [Design Kit: The Human-Centered Design Toolkit](https://www.ideo.com/post/design-kit) -* [A collection of activities, the Exploratorium facilitates a participatory design and development process](https://okthanks.com/exploratorium) -* [Knowledge Base](https://simplysecure.org/knowledge-base/) +* [Simply Secure Knowledge Base](https://simplysecure.org/knowledge-base/) +* [OK Thanks Exploratorium ](https://okthanks.com/exploratorium)

1 0

[community/staging] Bringing onion services section in line with other sections
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit f160b86710d2af6346650c2670939177c9f04299 Author: Pili Guerra <pili(a)piliguerra.com> Date: Fri Oct 11 11:20:23 2019 +0200 Bringing onion services section in line with other sections --- content/onion-services/ssl-tls/contents.lr | 21 ------------- templates/onion-services.html | 49 ++++++++++++++---------------- 2 files changed, 22 insertions(+), 48 deletions(-) diff --git a/content/onion-services/ssl-tls/contents.lr b/content/onion-services/ssl-tls/contents.lr deleted file mode 100644 index e60a121..0000000 --- a/content/onion-services/ssl-tls/contents.lr +++ /dev/null @@ -1,21 +0,0 @@ -section: onion services ---- -section_id: onion-services ---- -color: primary ---- -image: lock ---- -_template: layout.html ---- -title: Adding SSL/TLS to a .onion site ---- -subtitle: Add more security and authenticity for your .onion. ---- -key: 2 ---- -html: two-columns-page.html ---- -body: - -Coming soon diff --git a/templates/onion-services.html b/templates/onion-services.html index 94e834a..a4a7ed6 100644 --- a/templates/onion-services.html +++ b/templates/onion-services.html @@ -7,43 +7,30 @@ <img src="/static/images/home/png/{{ this.section_id }}.png" class="img-fluid" alt="{{ _(this.section) }}" /> </div> </div> - <a href="{{ this.path|url }}overview/"><h2 class="text-primary"><u>{{ _('Learn more about onion services here') }} - <i class="fas fa-arrow-right"></i></u> - </h2></a> - <div class="row py-5"> + <div class="row"> {% for child in this.children|sort(attribute='key') %} - {% if child.key != '0' %} - <div class="col-sm-6 col-md-6 col-sm-12 col-xl-6 py-4"> - <div class="card h-100 border-0"> + <div class="col-sm-6 col-md-6 col-sm-12 col-xl-6 py-3"> + <div class="card h-100"> <div class="card-body"> - <h2 class="text-primary display-2"><i class="fas fa-{{ child.image }}"></i></h2> - <h4 class="card-title text-primary">{{ child.title }}</h4> - <p class="card-text">{{ child.subtitle }}</p> - <a href="{{ child.path|url }}">{{ child.cta }} <i class="fas fa-arrow-right"></i></a> + <div class="card-body"> + <h4 class="card-title text-primary"> + <a href="{{ child.path|url(alt=this.alt) }}">{{ _(child.title) }}</a> + </h4> + <p class="card-text">{{ _(child.subtitle) }}</p> + </div> </div> </div> </div> - {% endif %} {% endfor %} </div> <div class="row py-5 text-center mx-auto"> <h2 class="display-4 text-primary text-center mx-auto">{{ _('Onionize any website') }}</h2> <p class="text-center"> - {{ _('There\'s a toolkit that lets you take any existing website and host it as a .onion site. You would wanna do this because .onion sites are more secure than just regular sites. We show you how to use this toolkit and onionize a site.') }} + {{ _('There\'s a toolkit that lets you take any existing website and host it as a .onion site. You would want do this because .onion sites are more secure than just regular sites. We show you how to use this toolkit and onionize a site.') }} </p> - </div> - <div class="row mx-auto"> - <div class="col-6"> - <a href="https://github.com/alecmuffett/eotk#i-want-to-create-my-own-project"> - <h3 class="text-primary text-center mx-auto"><u>{{ _('Learn more') }} - <i class="fas fa-arrow-right"></i></u> - </h3></a> - </div> - <div class="col-6"> - <a href="https://github.com/alecmuffett/eotk"><h3 class="text-primary text-center mx-auto"><u>{{ _('Check out the code') }} - <i class="fas fa-arrow-right"></i></u> - </h3></a> - </div> + <a class="btn btn-lg btn-outline-primary mx-auto my-3" href="https://github.com/alecmuffett/eotk"> + {{ _('Check out the code') }}<i class="ml-3 pt-2 fas fa-arrow-right"></i> + </a> </div> <div class="row py-5 text-center mx-auto"> <h2 class="display-4 text-primary text-center mx-auto">{{ _('Featured .onion sites') }}</h2> @@ -63,6 +50,14 @@ </div> </div> {% endfor %} - + </div> + <div class="row py-5 text-center mx-auto"> + <h2 class="display-4 text-primary text-center mx-auto my-3">{{ _('Learn More') }}</h2> + <p class="text-center"> + {{ _('Are you interested in learning more about onion services? Join our tor-onions mailing list to speak with other onion service operators.')}} + </p> + <a class="btn btn-lg btn-outline-primary mx-auto my-3" href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-onions"> + {{ _('Tor Onions mailing list') }}<i class="ml-3 pt-2 fas fa-arrow-right"></i> + </a> </div> </div>

1 0

[community/staging] update user research content
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit ee883fbc4107546c3076c4409d65be2af9b36cff Author: Antonela <hola(a)antonela.me> Date: Wed Oct 16 12:02:59 2019 -0300 update user research content --- templates/user-research.html | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/templates/user-research.html b/templates/user-research.html index c2c323a..e12fa62 100644 --- a/templates/user-research.html +++ b/templates/user-research.html @@ -13,8 +13,10 @@ <div class="card h-100"> <div class="card-body"> <div class="card-body"> - <h4 class="card-title text-primary">{{ child.title }}</h4> - <p class="card-text">{{ child.subtitle }}</p> + <h4 class="card-title text-primary"> + <a href="{{ child.path|url(alt=this.alt) }}">{{ _(child.title) }}</a> + </h4> + <p class="card-text">{{ _(child.subtitle) }}</p> </div> </div> </div> @@ -22,11 +24,11 @@ {% endfor %} </div> <div class="row py-5 text-center mx-auto"> - <h2 class="display-4 text-primary text-center mx-auto">{{ _('Be a user testing coordinator') }}</h2> + <h2 class="display-4 text-primary text-center mx-auto">{{ _('Become a Community User Researcher') }}</h2> <p class="text-center"> - {{ _('Are you a UX researcher interested in running Tor user tests? Have new ideas, suggestions, or studies that can help improve Tor applications? Help us by coordinating user testing, and we\'ll send you a Tor t-shirt.') }}</p> - <h3 class="text-primary text-center mx-auto"><u>{{ _('User research list') }} - <i class="fas fa-arrow-right"></i></u> - </h3> + {{ _('Are you a design researcher, user researcher, student, or someone interested in learning more about Tor users? Do you have new ideas, suggestions, or research that can help improve Tor applications? Help us by coordinating user research with your local community, and learn more about best practices for working with users at-risk.') }}</p> + <a class="btn btn-lg btn-outline-primary mx-auto my-3" href="https://lists.torproject.org/cgi-bin/mailman/listinfo/ux"> + {{ _('UX team mailing list') }}<i class="ml-3 pt-2 fas fa-arrow-right"></i> + </a> </div> </div>

1 0

[community/staging] add alpha testers survey link
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 8e91b85c38934963b221c737f1c28b8fc5c8e0c4 Author: Antonela <hola(a)antonela.me> Date: Wed Oct 16 12:26:46 2019 -0300 add alpha testers survey link --- content/user-research/become-tester/contents.lr | 14 +------------- 1 file changed, 1 insertion(+), 13 deletions(-) diff --git a/content/user-research/become-tester/contents.lr b/content/user-research/become-tester/contents.lr index 3602131..c30c983 100644 --- a/content/user-research/become-tester/contents.lr +++ b/content/user-research/become-tester/contents.lr @@ -2,21 +2,9 @@ section: user research --- section_id: user-research --- -color: primary ---- -image: eye ---- -_template: layout.html ---- title: Become a Tester --- -subtitle: We regularly release Tor Browser Alpha versions to allow users to test software improvements and new ideas. +subtitle: We regularly release Tor Browser Alpha versions to allow users to test software improvements and new ideas. [Sign up to be in our testing pool](https://survey.torproject.org/alpha-tester). --- key: 1 --- -html: two-columns-page.html ---- -body: - -We regularly release Tor Browser Alpha versions to allow users to test software improvements and new ideas. -Sign up to be in our testing pool >

1 0

[community/staging] Changed buttons to ordered list
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 7c7daf97db0a30f224a2d6af6cbeaefd0412b25e Author: LilyLME <38939048+LilyLME(a)users.noreply.github.com> Date: Sat Oct 5 17:27:41 2019 +0100 Changed buttons to ordered list The steps followed to sign up on Transifex to become a Tor translator are supposed to be an ordered list, so that the reader follows them chronologically. --- .../localization/becoming-tor-translator/contents.lr | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/content/localization/becoming-tor-translator/contents.lr b/content/localization/becoming-tor-translator/contents.lr index 229f70d..1e48e58 100644 --- a/content/localization/becoming-tor-translator/contents.lr +++ b/content/localization/becoming-tor-translator/contents.lr @@ -29,19 +29,19 @@ In order to begin contributing you will have to sign up with Transifex. Here's a # Signing Up On Transifex -- Head over to the [Transifex signup page](https://transifex.com/signup/). +1. Head over to the [Transifex signup page](https://transifex.com/signup/). Enter your information into the fields and click the 'Sign Up' button: ![Sign up to Transifex](/static/images/localization/tr1.png) -- Fill out the next page with your name and select "Localization" and "Translator" from the drop-down menus: +1. Fill out the next page with your name and select "Localization" and "Translator" from the drop-down menus: ![Fill out details](/static/images/localization/tr2.png) -- On the next page, select 'Join an existing project' and continue. -- On the next page, select the languages you speak from the drop-down menu and continue. -- You are now signed up! Go to the [Tor Transifex page](https://www.transifex.com/otf/torproject/). -- Click the blue 'Join Team' button on the far right: +1. On the next page, select 'Join an existing project' and continue. +1. On the next page, select the languages you speak from the drop-down menu and continue. +1. You are now signed up! Go to the [Tor Transifex page](https://www.transifex.com/otf/torproject/). +1. Click the blue 'Join Team' button on the far right: ![Join Team](/static/images/localization/tr3.png) -- Select the language you would like to translate from the dropdown menu: +1. Select the language you would like to translate from the dropdown menu: ![Choose Language](/static/images/localization/tr4.png) -- A notification will now show up on the top of the page like so: +1. A notification will now show up on the top of the page like so: ![Request Submitted](/static/images/localization/tr5.png) -After your membership is approved, you're ready to begin. \ No newline at end of file +After your membership is approved, you're ready to begin.

1 0

[community/staging] fix title case
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 0e1f7b8c4a985e1b68547b00ee1228193257313e Author: Antonela <hola(a)antonela.me> Date: Wed Oct 16 11:59:21 2019 -0300 fix title case --- content/user-research/become-tester/contents.lr | 2 +- content/user-research/open/contents.lr | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/user-research/become-tester/contents.lr b/content/user-research/become-tester/contents.lr index 248d815..3602131 100644 --- a/content/user-research/become-tester/contents.lr +++ b/content/user-research/become-tester/contents.lr @@ -8,7 +8,7 @@ image: eye --- _template: layout.html --- -title: Become a tester +title: Become a Tester --- subtitle: We regularly release Tor Browser Alpha versions to allow users to test software improvements and new ideas. --- diff --git a/content/user-research/open/contents.lr b/content/user-research/open/contents.lr index c0a9198..17cb0f9 100644 --- a/content/user-research/open/contents.lr +++ b/content/user-research/open/contents.lr @@ -8,7 +8,7 @@ image: eye --- _template: layout.html --- -title: Open user research +title: Open User Research --- subtitle: We put our users in the center of our development process. That is how we bring privacy-enhancing technology to the ones who more need it. Explore what we are working on and start to run user research with your local community. ---

1 0

[community/staging] match layout with other sections
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 24a118e67fa93d79c6eec22aaced4ac1bc60e0c7 Author: Antonela <hola(a)antonela.me> Date: Wed Oct 16 11:58:25 2019 -0300 match layout with other sections --- templates/user-research.html | 16 +++++++--------- 1 file changed, 7 insertions(+), 9 deletions(-) diff --git a/templates/user-research.html b/templates/user-research.html index 3c3ac7b..c2c323a 100644 --- a/templates/user-research.html +++ b/templates/user-research.html @@ -7,17 +7,15 @@ <img src="/static/images/home/png/{{ this.section_id }}.png" class="img-fluid" alt="{{ _(this.section) }}" /> </div> </div> - <h2 class="text-primary"><u>{{ _('Want to know more? Take a look at our process') }} - <i class="fas fa-arrow-right"></i></u> - </h2> - <div class="row py-5"> + <div class="row"> {% for child in this.children|sort(attribute='key') %} - <div class="col-sm-6 col-md-6 col-sm-12 col-xl-6 py-4"> - <div class="card h-100 border-0"> + <div class="col-sm-6 col-md-6 col-sm-12 col-xl-6 py-3"> + <div class="card h-100"> <div class="card-body"> - <span class="text-primary h3"><i class="far fa-{{ child.image }}"></i></span> - <h4 class="card-title text-primary my-3">{{ child.title }}</h4> - <p class="card-text">{{ child.subtitle }}</p> + <div class="card-body"> + <h4 class="card-title text-primary">{{ child.title }}</h4> + <p class="card-text">{{ child.subtitle }}</p> + </div> </div> </div> </div>

1 0

[community/staging] add item to nav
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 025ee4439a7dfc6b9c39c0b136c91d870e9c0f08 Author: Antonela <hola(a)antonela.me> Date: Wed Oct 16 12:12:52 2019 -0300 add item to nav --- databags/pagenav+en.ini | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/databags/pagenav+en.ini b/databags/pagenav+en.ini index 7d03cec..57c87f6 100644 --- a/databags/pagenav+en.ini +++ b/databags/pagenav+en.ini @@ -10,6 +10,10 @@ label = Localization path = outreach label = Outreach +[user-research] +path = user-research +label = User Research + [relay-operations] path = relay-operations label = Relay Operations

1 0