Merge pull request #192 from goanpeca/enh/check-links

PR: Fix broken links and add a script to check these links
2017-09-26 07:00:16 +08:00 · 2017-09-26 07:00:16 +08:00 · c47e29573c
commit c47e29573c
parent 06a56998a4 f8a55a83d7
150 changed files with 756 additions and 304 deletions
--- a/content/community/behavior/code-of-conduct/contents+es.lr
+++ b/content/community/behavior/code-of-conduct/contents+es.lr
@ -32,6 +32,6 @@ gutter:
 Créditos
 ------------

-Este Código de Conducta se ha adaptado del `"Contributor Covenant", versión 1.3.0 <http://contributor-covenant.org/version/1/3/0/>`__
+Este Código de Conducta se ha adaptado del `"Contributor Covenant", versión 1.3.0 <https://www.contributor-covenant.org/version/1/3/0/code-of-conduct.html>`__
 ---
 _slug: codigo-de-conducta
--- a/content/community/behavior/code-of-conduct/contents+pt.lr
+++ b/content/community/behavior/code-of-conduct/contents+pt.lr
@ -29,7 +29,7 @@ gutter:
 Créditos
 ---------------

-Esse Código de Conduta foi adaptado do `Contributor Covenant, version 1.3.0 <http://contributor-covenant.org/version/1/3/0/>`__
+Esse Código de Conduta foi adaptado do `Contributor Covenant, version 1.3.0 <https://www.contributor-covenant.org/version/1/3/0/code-of-conduct.html>`__
 ---
 summary: Espera-se que todos os participantes da comunidade BeeWare aderissem ao código de conduta.
 ---
--- a/content/community/behavior/code-of-conduct/contents.lr
+++ b/content/community/behavior/code-of-conduct/contents.lr
@ -34,4 +34,4 @@ gutter:
 Credits
 -------------

-This Code of Conduct is adapted from the `Contributor Covenant, version 1.3.0 <http://contributor-covenant.org/version/1/3/0/>`__
+This Code of Conduct is adapted from the `Contributor Covenant, version 1.3.0 <https://www.contributor-covenant.org/version/1/3/0/code-of-conduct.html>`__
--- a/content/community/behavior/making-a-coc-complaint/contents+pt.lr
+++ b/content/community/behavior/making-a-coc-complaint/contents+pt.lr
@ -1,6 +1,6 @@
 body:

-Se você acredita que alguém está violando o `Código de Conduta <../code-of-conduct/>`__ nós pedimos que você reporte isso para o projeto BeeWare enviando um email a um ou mais mantenedores do projeto (listados na barra lateral). Todas as denuncias serão mantidas em sigilo. Em alguns casos nós podemos determinar que uma declaração pública precisará ser feita. Se esse for o caso, a identidade de todas as vitimas e reportadores serão mantidas em sigilo a menos que os envolvidos nos instrua do contrário.
+Se você acredita que alguém está violando o `Código de Conduta </pt_BR/community/behavior/code-of-conduct/>`__ nós pedimos que você reporte isso para o projeto BeeWare enviando um email a um ou mais mantenedores do projeto (listados na barra lateral). Todas as denuncias serão mantidas em sigilo. Em alguns casos nós podemos determinar que uma declaração pública precisará ser feita. Se esse for o caso, a identidade de todas as vitimas e reportadores serão mantidas em sigilo a menos que os envolvidos nos instrua do contrário.

 **Se você acredita que alguém corre perigo de vida, por favor entre primeiro em contato com os agentes da lei apropriado**. Se você não tem certeza de qual agência de lei é apropriada, por favor inclua isso na sua notificação e nós tentaremos notifica-los.

--- a/content/community/behavior/making-a-coc-complaint/contents.lr
+++ b/content/community/behavior/making-a-coc-complaint/contents.lr
@ -4,7 +4,7 @@ title: Making a CoC complaint
 ---
 body:

-If you believe someone is violating the `BeeWare Project Code of Conduct <../code-of-conduct/>`__ we ask that you report it to the BeeWare Project by emailing one or more of the project maintainers (listed in the sidebar). All reports will be kept confidential. In some cases we may determine that a public statement will need to be made. If that's the case, the identities of all victims and reporters will remain confidential unless those individuals instruct us otherwise.
+If you believe someone is violating the `BeeWare Project Code of Conduct </community/behavior/code-of-conduct/>`__ we ask that you report it to the BeeWare Project by emailing one or more of the project maintainers (listed in the sidebar). All reports will be kept confidential. In some cases we may determine that a public statement will need to be made. If that's the case, the identities of all victims and reporters will remain confidential unless those individuals instruct us otherwise.

 **If you believe anyone is in physical danger, please notify appropriate law enforcement first**. If you are unsure what law enforcement agency is appropriate, please include this in your report and we will attempt to notify them.

--- a/content/community/getting-help/contents+pt.lr
+++ b/content/community/getting-help/contents+pt.lr
@ -17,7 +17,7 @@ Nós usamos o issue tracker para localizar um bug, bem como um fórum de discuss
 Perguntas Diretas para os Principais Contribuidores
 ---------------------------------------------------------------------

-Se você precisa de ajuda e não se sente confortável de usar um fórum publico, por favor sinta-se a vontade de contatar qualquer um dos `Principais Contribuidores <../team/>`__, por email, twitter ou Gitter.
+Se você precisa de ajuda e não se sente confortável de usar um fórum publico, por favor sinta-se a vontade de contatar qualquer um dos `Principais Contribuidores </pt_BR/community/team/>`__, por email, twitter ou Gitter.

 ---
 sort_key: 3
--- a/content/community/members/3a61928e/contents.lr
+++ b/content/community/members/3a61928e/contents.lr
@ -8,8 +8,14 @@ level: bronze
 ---
 join_date: 2017-06-11
 ---
-description: Carol Willing is a Director of the Python Software Foundation, a core developer for Project Jupyter, and a Research Software Engineer at Cal Poly San Luis Obispo.
+description:
+
+Carol Willing is a Director of the Python Software Foundation, a core developer for Project Jupyter, and a Research Software Engineer at Cal Poly San Luis Obispo.

 She’s also Geek-In-Residence at Fab Lab San Diego and co-organizes PyLadies San Diego and San Diego Python. She’s an active contributor to open source projects, a maintainer for OpenHatch and the Anita Borg Institute’s open source projects. Combining a love of nature, the arts, and math with a BSE in Electrical Engineering from Duke and an MS in Management from MIT, she’s enjoyed creating and teaching others for over 20 years.

-She recently spoke at PyCon US 2016, PyCon Philippines 2016, Write/Speak/Code 2016, SciPy 2016, PyData Carolinas 2016, and PyCon TW 2017.
+She recently spoke at PyCon US 2016, PyCon Philippines 2016, Write/Speak/Code 2016, SciPy 2016, PyData Carolinas 2016, and PyCon TW 2017.
+---
+image: 3a61928e-large.png
+---
+image_small: 3a61928e-small.png
--- a/content/community/members/github/contents.lr
+++ b/content/community/members/github/contents.lr
@ -9,3 +9,7 @@ name: GitHub
 url: https://github.com
 ---
 description: `GitHub <https://github.com>`__  is how people build software. They support a community where more than 21 million people learn, share, and work together to build software.
+---
+image: github-large.png
+---
+image_small: github-small.png
--- a/content/community/members/revsys/contents+es.lr
+++ b/content/community/members/revsys/contents+es.lr
@ -10,8 +10,12 @@ url: http://www.revsys.com/
 ---
 description:

-El enfoque principal de `Revolution Systems <http://www.revsys.com>`__ es la construcción y mantenimiento de aplicaciones web personalizadas, consultoría y soporte técnico para una variedad de tecnologías de código abierto. Su principal experiencia se encuentra en la consultoría `Python <http://www.python.org/>`__, `Django <http://www.djangoproject.com/>`__, PostgreSQL, devops y el rendimiento a escala. Para obtener una lista completa de servicios, visita la página `servicios <http://www.revsys.com/services/>`__.
+El enfoque principal de `Revolution Systems <http://www.revsys.com>`__ es la construcción y mantenimiento de aplicaciones web personalizadas, consultoría y soporte técnico para una variedad de tecnologías de código abierto. Su principal experiencia se encuentra en la consultoría `Python <https://www.python.org/>`__, `Django <https://www.djangoproject.com/>`__, PostgreSQL, devops y el rendimiento a escala. Para obtener una lista completa de servicios, visita la página `servicios <http://www.revsys.com/services/>`__.

 El software y los diversos niveles de soporte necesarios para administrar un negocio en el mundo actual no necesitan ser costoso de adquirir, mantener y personalizar. Revolution Systems trabaja con las empresas para reducir sus costos y hacer que sus sistemas sean más fáciles de entender y usar. Esto se hace exclusivamente con software de código abierto y se pide la ayuda de expertos externos como sea necesario.

 ¿No estás convencido aún? `Lee lo que dicen los clientes de Revolution Systems <http://www.revsys.com/testimonials/>`__ sobre ellos.
+---
+image: revsys-large.png
+---
+image_small: revsys-small.png
--- a/content/community/members/revsys/contents.lr
+++ b/content/community/members/revsys/contents.lr
@ -10,8 +10,12 @@ url: http://www.revsys.com/
 ---
 description:

-`Revolution Systems' <http://www.revsys.com>`__ primary focus is building and maintaining customized web applications, consulting, and technical support for a variety of Open Source technologies. Their core expertise lies in `Python <http://www.python.org/>`__, `Django <http://www.djangoproject.com/>`__, PostgreSQL, devops and performance/scaling-related consulting. For a complete list of services please visit the `services <http://www.revsys.com/services/>`__ page.
+`Revolution Systems' <http://www.revsys.com>`__ primary focus is building and maintaining customized web applications, consulting, and technical support for a variety of Open Source technologies. Their core expertise lies in `Python <https://www.python.org/>`__, `Django <https://www.djangoproject.com/>`__, PostgreSQL, devops and performance/scaling-related consulting. For a complete list of services please visit the `services <http://www.revsys.com/services/>`__ page.

 Software and the various levels of support needed to run a business in today's world do not need to be expensive to acquire, maintain and customize. Revolution Systems works with companies to reduce their costs and make their systems simpler to understand and use. This is done exclusively using Open Source software and calling on the help of external subject matter experts as needed.

 Not convinced?  `Read what Revolution Systems' clients say <http://www.revsys.com/testimonials/>`__ about them.
+---
+image: revsys-large.png
+---
+image_small: revsys-small.png
--- a/content/community/resources/djangocon-europe-2016-beyond-web-2.0/contents+pt.lr
+++ b/content/community/resources/djangocon-europe-2016-beyond-web-2.0/contents+pt.lr
@ -11,7 +11,7 @@ In this talk, Dr Russell Keith-Magee will explore the problems, and the potentia
 ---
 event_name: DjangoCon Europe 2016
 ---
-event_url: https://djangocon.eu/speakers/5
+event_url: https://2016.djangocon.eu/speakers/5
 ---
 pub_date: 2016-04-01
 ---
@ -20,3 +20,5 @@ resource_type: video
 title: Beyond Web 2.0 - Django and Python in the modern web ecosystem
 ---
 url: http://fast.wistia.net/embed/iframe/w5dpd2z3ym?canonicalUrl=https%3A%2F%2Fopbeat.com%2Fevents%2Fdjangocon-eu-2016%2F&canonicalTitle=DjangoCon%20Europe%202016%2C%20Budapest%20%7C%20Opbeat
+---
+_slug: djangocon-europe-2016-beyond-web-2
--- a/content/community/resources/djangocon-europe-2016-beyond-web-2.0/contents.lr
+++ b/content/community/resources/djangocon-europe-2016-beyond-web-2.0/contents.lr
@ -12,7 +12,7 @@ url: http://fast.wistia.net/embed/iframe/w5dpd2z3ym?canonicalUrl=https%3A%2F%2Fo
 ---
 event_name: DjangoCon Europe 2016
 ---
-event_url: https://djangocon.eu/speakers/5
+event_url: https://2016.djangocon.eu/speakers/5
 ---
 pub_date: 2016-04-01
 ---
--- a/content/community/resources/djangocon-us-2013/contents+es.lr
+++ b/content/community/resources/djangocon-us-2013/contents+es.lr
@ -4,7 +4,7 @@ description: Una charla relámpago en DjangoCon US 2013, donde Russell Keith-Mag
 ---
 event_name: DjangoCon US 2013
 ---
-event_url: http://2013.djangocon.us/
+event_url: https://2013.djangocon.us/
 ---
 pub_date: 2013-09-4
 ---
--- a/content/community/resources/djangocon-us-2013/contents+pt.lr
+++ b/content/community/resources/djangocon-us-2013/contents+pt.lr
@ -4,7 +4,7 @@ description: Uma lightning talk na DjangoCon US 2013, onde Russell Keith-Magee a
 ---
 event_name: DjangoCon US 2013
 ---
-event_url: http://2013.djangocon.us/
+event_url: https://2013.djangocon.us/
 ---
 pub_date: 2013-09-4
 ---
--- a/content/community/resources/djangocon-us-2013/contents.lr
+++ b/content/community/resources/djangocon-us-2013/contents.lr
@ -4,7 +4,7 @@ description: A lightning talk at DjangoCon US 2013, where Russell Keith-Magee an
 ---
 event_name: DjangoCon US 2013
 ---
-event_url: http://2013.djangocon.us/
+event_url: https://2013.djangocon.us/
 ---
 pub_date: 2013-09-4
 ---
@ -12,4 +12,4 @@ resource_type: video
 ---
 url: https://www.youtube.com/embed/M-pGfGf7zkY?t=1932
 ---
-author: Russell Keith-Magee
+author: Russell Keith-Magee
--- a/content/community/resources/how-i-became-an-open-source-contributor/contents+pt.lr
+++ b/content/community/resources/how-i-became-an-open-source-contributor/contents+pt.lr
@ -8,4 +8,4 @@ resource_type: article
 ---
 title: How I became an open source contributor
 ---
-url: http://plainsight.in/blog/how-i-became-an-open-source-contributor/
+url: https://ankushthakur.com/blog/how-i-became-an-open-source-contributor/
--- a/content/community/resources/how-i-became-an-open-source-contributor/contents.lr
+++ b/content/community/resources/how-i-became-an-open-source-contributor/contents.lr
@ -6,6 +6,6 @@ pub_date: 2016-2-16
 ---
 resource_type: article
 ---
-url: http://plainsight.in/blog/how-i-became-an-open-source-contributor/
+url: https://ankushthakur.com/blog/how-i-became-an-open-source-contributor/
 ---
-author: Ankush Thakur
+author: Ankush Thakur
--- a/content/community/resources/how-to-write-a-python-transpiler/contents.lr
+++ b/content/community/resources/how-to-write-a-python-transpiler/contents.lr
@ -10,7 +10,7 @@ In this talk, you'll be introduced to the tools and libraries Python provides to
 ---
 event_name: PyCon US 2017
 ---
-event_url: https://2017.pycon.us
+event_url: https://us.pycon.org/2017/
 ---
 pub_date: 2017-05-20
 ---
--- a/content/community/resources/linux-conf-au-2014-the-cobblers-children-have-no-shoes-development-tools-and-the-unix-philosophy/contents+es.lr
+++ b/content/community/resources/linux-conf-au-2014-the-cobblers-children-have-no-shoes-development-tools-and-the-unix-philosophy/contents+es.lr
@ -10,7 +10,7 @@ description: En esta charla, Russell Keith-Magee describe cómo las herramientas
 ---
 event_name: Linux Australia 2014 - Mini conferencia de programación abierta
 ---
-event_url: http://lca2014.linux.org.au/
+event_url: https://linux.conf.au/
 ---
 author: Russell Keith-Magee
 ---
--- a/content/community/resources/linux-conf-au-2014-the-cobblers-children-have-no-shoes-development-tools-and-the-unix-philosophy/contents+pt.lr
+++ b/content/community/resources/linux-conf-au-2014-the-cobblers-children-have-no-shoes-development-tools-and-the-unix-philosophy/contents+pt.lr
@ -4,7 +4,7 @@ description: Nessa conversa, Russell Keith-Magee explica como tem faltado ferram
 ---
 event_name: Linux Australia 2014 - Open Programming Miniconf
 ---
-event_url: http://lca2014.linux.org.au/
+event_url: https://linux.conf.au/
 ---
 pub_date: 2014-01-17
 ---
--- a/content/community/resources/linux-conf-au-2014-the-cobblers-children-have-no-shoes-development-tools-and-the-unix-philosophy/contents.lr
+++ b/content/community/resources/linux-conf-au-2014-the-cobblers-children-have-no-shoes-development-tools-and-the-unix-philosophy/contents.lr
@ -10,6 +10,6 @@ description: In this talk, Russell Keith-Magee describes how development tools h
 ---
 event_name: Linux Australia 2014 - Open Programming Miniconf
 ---
-event_url: http://lca2014.linux.org.au/
+event_url: https://linux.conf.au/
 ---
-author: Russell Keith-Magee
+author: Russell Keith-Magee
--- a/content/community/resources/making-a-tv-remote-in-python/contents+es.lr
+++ b/content/community/resources/making-a-tv-remote-in-python/contents+es.lr
@ -8,6 +8,6 @@ pub_date: 2017-02-04
 ---
 resource_type: article
 ---
-url: https://hackernoon.com/making-a-tv-remote-in-python-ef1dd5409524#.vk3neoxfx
+url: http://hackernoon.com/making-a-tv-remote-in-python-ef1dd5409524
 ---
 _slug: como-hacer-un-control-remoto-en-python
--- a/content/community/resources/making-a-tv-remote-in-python/contents.lr
+++ b/content/community/resources/making-a-tv-remote-in-python/contents.lr
@ -8,4 +8,4 @@ pub_date: 2017-02-04
 ---
 resource_type: article
 ---
-url: https://hackernoon.com/making-a-tv-remote-in-python-ef1dd5409524#.vk3neoxfx
+url: http://hackernoon.com/making-a-tv-remote-in-python-ef1dd5409524
--- a/content/community/resources/podcastinit/contents+es.lr
+++ b/content/community/resources/podcastinit/contents+es.lr
@ -8,6 +8,6 @@ pub_date: 2016-7-2
 ---
 resource_type: podcast
 ---
-url: http://pythonpodcast.com/russell-keith-magee-beeware.html
+url: https://pythonpodcast.com/episode-64-beeware-with-russell-keith-magee/
 ---
 author: Russell Keith-Magee
--- a/content/community/resources/podcastinit/contents.lr
+++ b/content/community/resources/podcastinit/contents.lr
@ -8,6 +8,6 @@ pub_date: 2016-7-2
 ---
 resource_type: podcast
 ---
-url: http://pythonpodcast.com/russell-keith-magee-beeware.html
+url: https://pythonpodcast.com/episode-64-beeware-with-russell-keith-magee/
 ---
-author: Russell Keith-Magee
+author: Russell Keith-Magee
--- a/content/community/resources/pycon-au-2013-tinkering-with-tkinter/contents+es.lr
+++ b/content/community/resources/pycon-au-2013-tinkering-with-tkinter/contents+es.lr
@ -16,7 +16,7 @@ url: https://www.youtube.com/embed/yI7NYgP54sw
 ---
 event_name: PyCon AU 2013
 ---
-event_url: http://2013.pycon-au.org/schedule/30033/view_talk
+event_url: 
 ---
 pub_date: 2013-07-10
 ---
--- a/content/community/resources/pycon-au-2013-tinkering-with-tkinter/contents.lr
+++ b/content/community/resources/pycon-au-2013-tinkering-with-tkinter/contents.lr
@ -16,10 +16,10 @@ url: https://www.youtube.com/embed/yI7NYgP54sw
 ---
 event_name: PyCon AU 2013
 ---
-event_url: http://2013.pycon-au.org/schedule/30033/view_talk
+event_url: 
 ---
 pub_date: 2013-07-10
 ---
 resource_type: video
 ---
-author: Russell Keith-Magee
+author: Russell Keith-Magee
--- a/content/community/resources/pycon-au-2014-release-the-yak/contents+es.lr
+++ b/content/community/resources/pycon-au-2014-release-the-yak/contents+es.lr
@ -6,7 +6,7 @@ url: https://www.youtube.com/embed/W0W0s0-Ryc0?t=790
 ---
 event_name: PyCon Australia 2014
 ---
-event_url: http://2014.pycon-au.org/
+event_url: 
 ---
 pub_date: 2014-08-08
 ---
--- a/content/community/resources/pycon-au-2014-release-the-yak/contents.lr
+++ b/content/community/resources/pycon-au-2014-release-the-yak/contents.lr
@ -6,10 +6,10 @@ url: https://www.youtube.com/embed/W0W0s0-Ryc0?t=790
 ---
 event_name: PyCon AU 2014
 ---
-event_url: http://2014.pycon-au.org/
+event_url: 
 ---
 pub_date: 2014-08-08
 ---
 resource_type: video
 ---
-author: Russell Keith-Magee
+author: Russell Keith-Magee
--- a/content/community/resources/pycon-au-2015-python-on-the-move/contents+es.lr
+++ b/content/community/resources/pycon-au-2015-python-on-the-move/contents+es.lr
@ -10,7 +10,7 @@ En esta charla, Russell Keith-Magee examinará el estado actual del uso de Pytho
 ---
 event_name: PyCon Australia 2015
 ---
-event_url: https://2015.pycon-au.org
+event_url: 
 ---
 pub_date: 2015-08-02
 ---
--- a/content/community/resources/pycon-au-2015-python-on-the-move/contents.lr
+++ b/content/community/resources/pycon-au-2015-python-on-the-move/contents.lr
@ -10,7 +10,7 @@ In this talk, Russell Keith-Magee will survey the current state of using Python
 ---
 event_name: PyCon AU 2015
 ---
-event_url: https://2015.pycon-au.org
+event_url: 
 ---
 pub_date: 2015-08-02
 ---
@ -18,4 +18,4 @@ resource_type: video
 ---
 url: https://www.youtube.com/embed/Cbkcr3ofBmk
 ---
-author: Russell Keith-Magee
+author: Russell Keith-Magee
--- a/content/community/resources/python-all-the-things/contents+es.lr
+++ b/content/community/resources/python-all-the-things/contents+es.lr
@ -8,7 +8,7 @@ editors_pick: yes
 ---
 event_name: PyCon Australia 2016
 ---
-event_url: http://2016.pycon-au.org
+event_url: https://2016.pycon-au.org
 ---
 pub_date: 2016-08-14
 ---
--- a/content/community/resources/python-all-the-things/contents.lr
+++ b/content/community/resources/python-all-the-things/contents.lr
@ -8,7 +8,7 @@ editors_pick: yes
 ---
 event_name: PyCon AU 2016
 ---
-event_url: http://2016.pycon-au.org
+event_url: https://2016.pycon-au.org
 ---
 pub_date: 2016-08-14
 ---
--- a/content/community/resources/what-makes-the-open-source-project-beeware-sticky-for-sponsorships-and-contributions/contents+es.lr
+++ b/content/community/resources/what-makes-the-open-source-project-beeware-sticky-for-sponsorships-and-contributions/contents+es.lr
@ -1,6 +1,6 @@
 title: ¿Qué hace que el proyecto de código abierto BeeWare sea 'pegajoso' para patrocinadores y colaboradores
 ---
-description: Robert Gibb de `MaxCDN <https://maxcdn.com>`__ discute por qué se convirtieron en patrocinadores del Proyecto BeeWare.
+description: Robert Gibb de `MaxCDN <https://www.maxcdn.com>`__ discute por qué se convirtieron en patrocinadores del Proyecto BeeWare.
 ---
 pub_date: 2016-4-26
 ---
--- a/content/community/resources/what-makes-the-open-source-project-beeware-sticky-for-sponsorships-and-contributions/contents.lr
+++ b/content/community/resources/what-makes-the-open-source-project-beeware-sticky-for-sponsorships-and-contributions/contents.lr
@ -1,6 +1,6 @@
 title: What Makes the Open Source Project BeeWare Sticky for Sponsorships and Contributions
 ---
-description: Robert Gibb from `MaxCDN <https://maxcdn.com>`__ discusses why they became a financial sponsor of the BeeWare Project.
+description: Robert Gibb from `MaxCDN <https://www.maxcdn.com>`__ discusses why they became a financial sponsor of the BeeWare Project.
 ---
 pub_date: 2016-4-26
 ---
@ -8,4 +8,4 @@ resource_type: article
 ---
 url: https://www.maxcdn.com/blog/beeware-be-sticky/
 ---
-author: Robert Gibb
+author: Robert Gibb
--- a/content/community/resources/whats-the-buzz-python-gorges-on-tools-and-libraries/contents+es.lr
+++ b/content/community/resources/whats-the-buzz-python-gorges-on-tools-and-libraries/contents+es.lr
@ -6,7 +6,7 @@ pub_date: 2016-6-8
 ---
 resource_type: article
 ---
-url: http://www.infoworld.com/article/3081324/application-development/whats-the-buzz-python-gorges-on-tools-and-libraries.html
+url: https://www.infoworld.com/article/3081324/application-development/whats-the-buzz-python-gorges-on-tools-and-libraries.html
 ---
 author: Paul Krill
 ---
--- a/content/community/resources/whats-the-buzz-python-gorges-on-tools-and-libraries/contents.lr
+++ b/content/community/resources/whats-the-buzz-python-gorges-on-tools-and-libraries/contents.lr
@ -6,6 +6,6 @@ pub_date: 2016-6-8
 ---
 resource_type: article
 ---
-url: http://www.infoworld.com/article/3081324/application-development/whats-the-buzz-python-gorges-on-tools-and-libraries.html
+url: https://www.infoworld.com/article/3081324/application-development/whats-the-buzz-python-gorges-on-tools-and-libraries.html
 ---
-author: Paul Krill
+author: Paul Krill
--- a/content/community/team/elias/contents+es.lr
+++ b/content/community/team/elias/contents+es.lr
@ -2,7 +2,7 @@ name: Elias Dorneles
 ---
 description:

-Elias es una máquina de afeitar de yaks certificada. Le gusta jugar con Python y proyectos de código abierto. En casa, le gusta leer, cocinar y tocar canciones de los Beatles en su guitarra.
+Elias es una máquina de afeitar yaks certificada. Le gusta jugar con Python y con proyectos de código abierto. En casa le gusta leer, cocinar y tocar canciones de los Beatles en su guitarra.

 Elias logra sobrevivir con un poco de ayuda de sus amigos.
 ---
--- a/content/contact/media/contents+ar.lr
+++ b/content/contact/media/contents+ar.lr
@ -23,46 +23,46 @@ body:
 BeeWare شعار
 ~~~~~~~~~~~~

-.. image:: beeware-150.png
+.. image:: /contact/media/beeware-150.png
    :alt: BeeWare logo

-* `صغير <./beeware-150.png>`__
-* `متوسط <./beeware-519.png>`__
-* `Vector <./beeware.eps>`__
+* `صغير </contact/media/beeware-150.png>`__
+* `متوسط </contact/media/beeware-519.png>`__
+* `Vector </contact/media/beeware.eps>`__

 BeeWare  شعار عريض
 ~~~~~~~~~~~~~~~~~~~

-.. image:: beeware-wide-143.png
+.. image:: /contact/media/beeware-wide-143.png
    :alt: BeeWare logo (wide)

-* `صغير <./beeware-wide-143.png>`__
-* `متوسط <./beeware-wide-600.png>`__
-* `كبير <./beeware-wide-2028.png>`__
-* `Vector <./beeware-wide.eps>`__
+* `صغير </contact/media/beeware-wide-143.png>`__
+* `متوسط </contact/media/beeware-wide-600.png>`__
+* `كبير </contact/media/beeware-wide-2028.png>`__
+* `Vector </contact/media/beeware-wide.eps>`__

 BeeWare شعار ناشطي
 ~~~~~~~~~~~~~~~~~~~~~~~~

-.. image:: beeware-enthusiasts-150.png
+.. image:: /contact/media/beeware-enthusiasts-150.png
    :alt: BeeWare Enthusiasts logo

-* `صغير <./beeware-enthusiasts-150.png>`__
-* `متوسط <./beeware-enthusiasts-600.png>`__
-* `كبير <./beeware-enthusiasts-2000.png>`__
-* `Vector <./beeware-enthusiasts.eps>`__
+* `صغير </contact/media/beeware-enthusiasts-150.png>`__
+* `متوسط </contact/media/beeware-enthusiasts-600.png>`__
+* `كبير </contact/media/beeware-enthusiasts-2000.png>`__
+* `Vector </contact/media/beeware-enthusiasts.eps>`__

 Brutus النحلة
 ~~~~~~~~~~~~~~

-.. image:: brutus-128.png
+.. image:: /contact/media/brutus-128.png
    :alt: Brutus the Bee

-* `صغير <./brutus-32.png>`__
-* `متوسط <./brutus-128.png>`__
-* `كبير <./brutus-256.png>`__
-* `كبير جدا <./brutus-1024.png>`__
-* `Vector <./brutus.eps>`__
+* `صغير </contact/media/brutus-32.png>`__
+* `متوسط </contact/media/brutus-128.png>`__
+* `كبير </contact/media/brutus-256.png>`__
+* `كبير جدا </contact/media/brutus-1024.png>`__
+* `Vector </contact/media/brutus.eps>`__

 ---
 summary: هل أنت من منظمة اعلامية و أردت أن تكتب شيئا حول مشروعنا؟ إليك بعض الموارد التي قد تفيدك
--- a/content/contact/media/contents+es.lr
+++ b/content/contact/media/contents+es.lr
@ -34,10 +34,10 @@ Logo (ancho) de BeeWare
 .. image:: /contact/media/beeware-wide-143.png
    :alt: BeeWare logo (wide)

-* `Small </contact/media/beeware-wide-143.png>`__ 
-* `Medium </contact/media/beeware-wide-600.png>`__ 
-* `Large </contact/media/beeware-wide-2028.png>`__ 
-* `Vector </contact/media/beeware-wide.eps>`__
+* `Pequeño </contact/media/beeware-wide-143.png>`__ 
+* `Mediano </contact/media/beeware-wide-600.png>`__ 
+* `Grande </contact/media/beeware-wide-2028.png>`__ 
+* `Vectorial </contact/media/beeware-wide.eps>`__

 Logo de Entusiastas de BeeWare
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@ -45,10 +45,10 @@ Logo de Entusiastas de BeeWare
 .. image:: /contact/media/beeware-enthusiasts-150.png
    :alt: BeeWare Enthusiasts logo

-* `Small </contact/media/beeware-enthusiasts-150.png>`__ 
-* `Medium </contact/media/beeware-enthusiasts-600.png>`__ 
-* `Large </contact/media/beeware-enthusiasts-2000.png>`__ 
-* `Vector </contact/media/beeware-enthusiasts.eps>`__
+* `Pequeño </contact/media/beeware-enthusiasts-150.png>`__ 
+* `Mediano </contact/media/beeware-enthusiasts-600.png>`__ 
+* `Grande </contact/media/beeware-enthusiasts-2000.png>`__ 
+* `Vectorial </contact/media/beeware-enthusiasts.eps>`__

 Brutus la abeja
 ~~~~~~~~~~~~~~~~~~~
@ -56,11 +56,11 @@ Brutus la abeja
 .. image:: /contact/media/brutus-128.png
    :alt: Brutus the Bee

-* `Small </contact/media/brutus-32.png>`__ 
-* `Medium </contact/media/brutus-128.png>`__ 
-* `Large </contact/media/brutus-256.png>`__  
-* `X-large </contact/media/brutus-1024.png>`__ 
-* `Vector </contact/media/brutus.eps>`__
+* `Pequeño </contact/media/brutus-32.png>`__ 
+* `Mediano </contact/media/brutus-128.png>`__ 
+* `Grande </contact/media/brutus-256.png>`__  
+* `Extra grande </contact/media/brutus-1024.png>`__ 
+* `Vectorial </contact/media/brutus.eps>`__

 ---
 summary: ¿Perteneces a una organización de medios de comunicación y quieres escribir algo sobre BeeWare? Estos son algunos recursos que puede ser útiles.
--- a/content/contact/media/contents+pt.lr
+++ b/content/contact/media/contents+pt.lr
@ -18,46 +18,46 @@ Logos
 Logo do BeeWare
 ~~~~~~~~~~~~~~~~

-.. image:: beeware-150.png
+.. image:: /contact/media/beeware-150.png
    :alt: Logo do BeeWare

-* `Pequeno <./beeware-150.png>`__ 
-* `Médio <./beeware-519.png>`__ 
-* `Vetor <./beeware.eps>`__
+* `Pequeno </contact/media//beeware-150.png>`__ 
+* `Médio </contact/media//beeware-519.png>`__ 
+* `Vetor </contact/media//beeware.eps>`__

 Logo do BeeWare (largo)
 ~~~~~~~~~~~~~~~~~~~~~~~

-.. image:: beeware-wide-143.png
+.. image:: /contact/media/beeware-wide-143.png
    :alt: BeeWare logo (wide)

-* `Pequeno <./beeware-wide-143.png>`__ 
-* `Médio <./beeware-wide-600.png>`__ 
-* `Grande <./beeware-wide-2028.png>`__ 
-* `Vetor <./beeware-wide.eps>`__
+* `Pequeno </contact/media//beeware-wide-143.png>`__ 
+* `Médio </contact/media//beeware-wide-600.png>`__ 
+* `Grande </contact/media//beeware-wide-2028.png>`__ 
+* `Vetor </contact/media//beeware-wide.eps>`__

 Logo Entusiasta do BeeWare
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~

-.. image:: beeware-enthusiasts-150.png
+.. image:: /contact/media/beeware-enthusiasts-150.png
    :alt: BeeWare Enthusiasts logo

-* `Pequeno <./beeware-enthusiasts-150.png>`__ 
-* `Médio <./beeware-enthusiasts-600.png>`__ 
-* `Grande <./beeware-enthusiasts-2000.png>`__ 
-* `Vetor <./beeware-enthusiasts.eps>`__
+* `Pequeno </contact/media//beeware-enthusiasts-150.png>`__ 
+* `Médio </contact/media//beeware-enthusiasts-600.png>`__ 
+* `Grande </contact/media//beeware-enthusiasts-2000.png>`__ 
+* `Vetor </contact/media//beeware-enthusiasts.eps>`__

 Brutus a Abelha
 ~~~~~~~~~~~~~~~~~~

-.. image:: brutus-128.png
+.. image:: /contact/media/brutus-128.png
    :alt: Brutus the Bee

-* `Pequeno <./brutus-32.png>`__ 
-* `Médio <./brutus-128.png>`__ 
-* `Grande <./brutus-256.png>`__  
-* `Extra Grande <./brutus-1024.png>`__ 
-* `Vetor <./brutus.eps>`__
+* `Pequeno </contact/media//brutus-32.png>`__ 
+* `Médio </contact/media//brutus-128.png>`__ 
+* `Grande </contact/media//brutus-256.png>`__  
+* `Extra Grande </contact/media//brutus-1024.png>`__ 
+* `Vetor </contact/media//brutus.eps>`__

 ---
 gutter:
--- a/content/contact/media/contents.lr
+++ b/content/contact/media/contents.lr
@ -22,46 +22,46 @@ Logos
 BeeWare logo
 ~~~~~~~~~~~~

-.. image:: beeware-150.png
+.. image:: /contact/media/beeware-150.png
    :alt: BeeWare logo

-* `Small <./beeware-150.png>`__ 
-* `Medium <./beeware-519.png>`__ 
-* `Vector <./beeware.eps>`__
+* `Small </contact/media/beeware-150.png>`__ 
+* `Medium </contact/media/beeware-519.png>`__ 
+* `Vector </contact/media/beeware.eps>`__

 BeeWare (wide) logo
 ~~~~~~~~~~~~~~~~~~~

-.. image:: beeware-wide-143.png
+.. image:: /contact/media/beeware-wide-143.png
    :alt: BeeWare logo (wide)

-* `Small <./beeware-wide-143.png>`__ 
-* `Medium <./beeware-wide-600.png>`__ 
-* `Large <./beeware-wide-2028.png>`__ 
-* `Vector <./beeware-wide.eps>`__
+* `Small </contact/media/beeware-wide-143.png>`__ 
+* `Medium </contact/media/beeware-wide-600.png>`__ 
+* `Large </contact/media/beeware-wide-2028.png>`__ 
+* `Vector </contact/media/beeware-wide.eps>`__

 BeeWare Enthusiasts logo
 ~~~~~~~~~~~~~~~~~~~~~~~~

-.. image:: beeware-enthusiasts-150.png
+.. image:: /contact/media/beeware-enthusiasts-150.png
    :alt: BeeWare Enthusiasts logo

-* `Small <./beeware-enthusiasts-150.png>`__ 
-* `Medium <./beeware-enthusiasts-600.png>`__ 
-* `Large <./beeware-enthusiasts-2000.png>`__ 
-* `Vector <./beeware-enthusiasts.eps>`__
+* `Small </contact/media/beeware-enthusiasts-150.png>`__ 
+* `Medium </contact/media/beeware-enthusiasts-600.png>`__ 
+* `Large </contact/media/beeware-enthusiasts-2000.png>`__ 
+* `Vector </contact/media/beeware-enthusiasts.eps>`__

 Brutus the Bee
 ~~~~~~~~~~~~~~

-.. image:: brutus-128.png
+.. image:: /contact/media/brutus-128.png
    :alt: Brutus the Bee

-* `Small <./brutus-32.png>`__ 
-* `Medium <./brutus-128.png>`__ 
-* `Large <./brutus-256.png>`__  
-* `X-large <./brutus-1024.png>`__ 
-* `Vector <./brutus.eps>`__
+* `Small </contact/media/brutus-32.png>`__ 
+* `Medium </contact/media/brutus-128.png>`__ 
+* `Large </contact/media/brutus-256.png>`__  
+* `X-large </contact/media/brutus-1024.png>`__ 
+* `Vector </contact/media/brutus.eps>`__

 ---
 summary: Are you from a media organization and want to write something about BeeWare? Here are some resources you may find helpful.
--- a/content/contributing/challenge-coins/contents+es.lr
+++ b/content/contributing/challenge-coins/contents+es.lr
@ -12,7 +12,7 @@ Las monedas de desafío son una tradición militar, que se dice que se originó

 Para obtener más información sobre las monedas de desafío, puedes escuchar el podcast `99% Invisible`_ sobre ellas, o leer sobre ellas en `Wikipedia`_.

-.. figure:: challenge-coin.jpg
+.. figure:: /contributing/challenge-coins/challenge-coin.jpg
    :alt: El frente y la parte posterior de la moneda del desafío de BeeWare.

 *El frente y la parte posterior de la moneda del desafío BeeWare.*
@ -25,7 +25,7 @@ No tiene que ser una contribución de código: una actualización de documentaci

 Y como un incentivo adicional, para aquellas personas que ayudan a otros a obtener sus monedas de desafío, tenemos una segunda moneda: el Pastor de Yaks 

-.. figure:: yak-herder-coin.jpg
+.. figure:: /contributing/challenge-coins/yak-herder-coin.jpg
    :alt: La parte delantera y trasera de la moneda Pastor de Yaks de BeeWare.

 *El frente y la parte posterior de la moneda BeeWare Yak Herder.*
--- a/content/contributing/challenge-coins/contents+pt.lr
+++ b/content/contributing/challenge-coins/contents+pt.lr
@ -4,7 +4,7 @@ Challenge Coins (Moedas de Desafio) são uma tradição militar, dizem ter sua o

 Para saber mais sobre Challenge Coins, você pode ouvir o podcast `99% Invisible`_ sobre elas, ou ler a respeito na `Wikipedia`_.

-.. figure:: challenge-coin.jpg
+.. figure:: /contributing/challenge-coins/challenge-coin.jpg
    :alt: Frente e Verso da BeeWare Challenge Coin.

    *Frente e Verso de uma BeeWare Challenge Coin.*
--- a/content/contributing/challenge-coins/contents+zh.lr
+++ b/content/contributing/challenge-coins/contents+zh.lr
@ -12,11 +12,10 @@ body:

 想要知道更多的挑战硬币， 你可以收听 `99% Invisible`_ 广播，或者阅读 `Wikipedia`_.

-.. figure:: challenge-coin.jpg
-
+.. figure:: /contributing/challenge-coins/challenge-coin.jpg
    :alt: .正面和反面的Beeware 挑战硬币
-    
-    *正面和反面的Beeware 挑战硬币*
+
+*正面和反面的Beeware 挑战硬币*


 BeeWare 挑战硬币是由镍和锌合金并且有瓷釉压铸制成，直径4.5(1 3/4")厘米。
--- a/content/contributing/challenge-coins/contents.lr
+++ b/content/contributing/challenge-coins/contents.lr
@ -12,7 +12,7 @@ Challenge Coins are a military tradition, which is said to originate at the star

 To find out more about Challenge Coins, you can listen to the `99% Invisible`_ podcast about them, or read up about them on `Wikipedia`_.

-.. figure:: challenge-coin.jpg
+.. figure:: /contributing/challenge-coins/challenge-coin.jpg
    :alt: The front and back of the BeeWare Challenge Coin.

    *The front and back of the BeeWare Challenge Coin.*
@ -25,7 +25,7 @@ It doesn't have to be a code contribution: a documentation update counts. A blog

 And as an additional incentive, for those people who help others get their challenge coins, we have a second coin: the Yak Herder

-.. figure:: yak-herder-coin.jpg
+.. figure:: /contributing/challenge-coins/yak-herder-coin.jpg
    :alt: The front and back of the BeeWare Yak Herder Coin.

    *The front and back of the BeeWare Yak Herder Coin.*
--- a/content/contributing/core-team/contents+pt.lr
+++ b/content/contributing/core-team/contents+pt.lr
@ -83,7 +83,7 @@ existem algumas orientações que o time deve seguir:

  * Processo de aceitação deve ser automatizado sempre que possível.
     - Isso significa testes, verificações de sintaxe, de ortografia, cobertura de funcionalidades e mais.
-     - Esse é um `trabalho em desenvolvimento <http://pybee.org/project/projects/tools/beefore/>`_
+     - Esse é um `trabalho em desenvolvimento </pt_BR/project/projects/tools/beefore/>`_



@ -102,7 +102,7 @@ pedir a permissão de poder fazer commits no projeto.

 Todos os novos apicultores serão 'introduzidos' (por falta de uma palavra melhor)
 nos valores e orientações centrais do projeto. Um resumo dos valores centrais pode
-ser encontrado `na página Sobre o projeto <http://pybee.org/project/about/>`_. Espera-se
+ser encontrado `na página Sobre o projeto </pt_BR/project/about/>`_. Espera-se
 que qualquer um que entre no time detenha esses valores e contribua para o debate e
 evolução desses dos mesmos no decorrer do tempo.

--- a/content/contributing/core-team/contents+zh.lr
+++ b/content/contributing/core-team/contents+zh.lr
@ -65,7 +65,7 @@ body:

 * 應該盡可能把接受測試自動化。
    - 包括測試、linting、拼寫檢測、涵蓋範圍等。
-    - 這算是 `製作尚未完工的 <http://pybee.org/project/projects/tools/beefore/>`_
+    - 這算是 `製作尚未完工的 </zh_TW/project/projects/tools/beefore/>`_



@ -74,7 +74,7 @@ body:
 ----------------------------
 新蜂農能不能加入團隊是由現有核心團隊的決定。現在沒有固定的規則，但總的來說一個人已经積累了不少對項目的貢獻以後就可能會收到加入團隊的邀請。收到邀請的人也可能有對一種技術專門的知識（比如，iOS/macOS)，而且邀請不一定是因為他提交了好幾行的代碼。任何已经對項目表示有興趣，並且已經提供貢獻的人能請求收到(commit to the project)提交項目的權利。

-所有新的蜂農會被('inducted' (for lack of a better word) in the core values)“入門”項目的核心價值觀和指導準則。核心價值的總結在 `關於頁 <http://pybee.org/project/about/>`_。加入團隊以後，我們要求成員維護我們的價值觀，而且參加發展價值觀的討論。
+所有新的蜂農會被('inducted' (for lack of a better word) in the core values)“入門”項目的核心價值觀和指導準則。核心價值的總結在 `關於頁 </zh_TW/project/about/>`_。加入團隊以後，我們要求成員維護我們的價值觀，而且參加發展價值觀的討論。

 不管新的或老的蜂農，我們不要求任何蜂農當作唯一維護者。蜂農很多，而且能幫上忙、提出建議、或者提供輔導的蜂農不少。

--- a/content/contributing/core-team/contents.lr
+++ b/content/contributing/core-team/contents.lr
@ -96,7 +96,7 @@ number of general guidelines that the team should follow:

 * Acceptance processes should be automated wherever possible
    - This means tests, linting, spell checking, coverage, and more.
-    - This is a `work in progress <http://pybee.org/project/projects/tools/beefore/>`_
+    - This is a `work in progress </project/projects/tools/beefore/>`_



@ -115,7 +115,7 @@ may ask to be given permission to commit to the project.

 All new apiarists will be 'inducted' (for lack of a better word) in the core
 values and guidelines of the project. A summary of the core values can be found
-`on the about page <http://pybee.org/project/about/>`_. Anyone who joins the
+`on the about page </project/about/>`_. Anyone who joins the
 team will be expected to uphold those values, and contribute to discussions
 about evolving those values over time.

--- a/content/contributing/how/contents+ar.lr
+++ b/content/contributing/how/contents+ar.lr
@ -15,7 +15,7 @@ body:
 المساهمون للمرة الأولى
 ------------------------

-إذا كنت جديدا على عالم المساهمات و البرمجيات المفتوحة رجاءا تفضل بمطالعة `دليل المساهمين المبتدئين <http://pybee.org/contributing/first-time/>`__.
+إذا كنت جديدا على عالم المساهمات و البرمجيات المفتوحة رجاءا تفضل بمطالعة `دليل المساهمين المبتدئين <https://pybee.org/contributing/first-time/>`__.

 المساهمة بالبرمجة
 ---------------------
@ -57,8 +57,8 @@ Something else
 If you've got your own idea for something, or if you don't see any
 tickets, or you want to be mentored on a ticket, or you aren't sure how
 to proceed, contact the project maintainers on
-`Twitter <http://twitter.com/pybeeware/>`__ or
-`Gitter <http://gitter.im/pybee/general>`__. The project maintainers love
+`Twitter <https://twitter.com/pybeeware/>`__ or
+`Gitter <https://gitter.im/pybee/general>`__. The project maintainers love
 collaborating, especially with new contributors, and will gladly answer
 any questions or walk you through any problems you may encounter.

--- a/content/contributing/how/contents+es.lr
+++ b/content/contributing/how/contents+es.lr
@ -46,7 +46,7 @@ Este sitio web
 Algo más
 -------------

-Si tienes tu propia idea para algo, o si no ves ninguna tiquete al respeco o quieres ser mentor en un tiquete, o no estás seguro de cómo para continuar, puedes ponerte en contacto con `Twitter <http://twitter.com/pybeeware/>`__ o en `Gitter <http://gitter.im/pybee/general>`__. Los mantenedores del proyecto aman colaborar, especialmente con los nuevos colaboradores, y con mucho gusto resolverán cualquier pregunta o te ayudarán a través de cualquier problema que puedas encontrar.
+Si tienes tu propia idea para algo, o si no ves ninguna tiquete al respeco o quieres ser mentor en un tiquete, o no estás seguro de cómo para continuar, puedes ponerte en contacto con `Twitter <https://twitter.com/pybeeware/>`__ o en `Gitter <https://gitter.im/pybee/general>`__. Los mantenedores del proyecto aman colaborar, especialmente con los nuevos colaboradores, y con mucho gusto resolverán cualquier pregunta o te ayudarán a través de cualquier problema que puedas encontrar.
 ---
 gutter:

--- a/content/contributing/how/contents+pt.lr
+++ b/content/contributing/how/contents+pt.lr
@ -15,7 +15,7 @@ Existem muitas formas de ajudar o BeeWare.
 Primeiras Contribuições
 ----------------------------

-Se você é novo em contribuir para projetos open source veja o `guia das Primeiras contribuições <../first-time/>`__.
+Se você é novo em contribuir para projetos open source veja o `guia das Primeiras contribuições </pt_BR/contributing/how/first-time/>`__.

 Contribuições com Código
 ------------------------------
@ -57,7 +57,7 @@ Alguma outra coisa
 Se você tiver alguma ideia para algo, ou se você não ver nenhum
 ticket, ou você gostaria de ser ajudado com um ticket, ou se você
 não tem certeza de como proceder, contate os mantenedores do projeto no
-`Twitter <http://twitter.com/pybeeware/>`__ ou `Gitter <http://gitter.im/pybee/general>`__.
+`Twitter <https://twitter.com/pybeeware/>`__ ou `Gitter <https://gitter.im/pybee/general>`__.
 Os mantenedores do projeto amam colaborar, especialmente com
 novos contribuidores e vão ficar felizes em responder qualquer
 pergunta ou ajuda-lo com qualquer a passar por qualquer problema
--- a/content/contributing/how/contents+zh.lr
+++ b/content/contributing/how/contents+zh.lr
@ -15,7 +15,7 @@ body:
 第一次貢獻者
 ------------------------

-如果你從來沒向開源貢獻過，請參閱 `第一次貢獻者的指南 <http://pybee.org/contributing/first-time/>`__.
+如果你從來沒向開源貢獻過，請參閱 `第一次貢獻者的指南 <https://pybee.org/contributing/first-time/>`__.

 貢獻源碼
 ---------------------
@ -50,8 +50,8 @@ body:
 -------------------------

 如果你有自己的想法，找不到有關的票，想收到輔導，或者不知道在哪入手，請在
-`Twitter <http://twitter.com/pybeeware/>`__ 或
-`Gitter <http://gitter.im/pybee/general>`__ 聯繫維護項目著。
+`Twitter <https://twitter.com/pybeeware/>`__ 或
+`Gitter <https://gitter.im/pybee/general>`__ 聯繫維護項目著。
 維護項目著熱愛協作，特別適合新貢獻者協作，而且會高高興興的回答任何問題以
 及幫你解決任何問題。

@ -66,5 +66,7 @@ gutter:
 項目里不只是包括代碼——要成功的軟體項目有著文檔，設計技能，意見以及臭蟲報告。BeeWare社區覺得不只是GitHub上的pull request很重要——所有的貢獻非常重要。

 ---
-incomplete: yes
+incomplete:
+
+yes

--- a/content/contributing/how/contents.lr
+++ b/content/contributing/how/contents.lr
@ -17,7 +17,7 @@ There are many ways to help with BeeWare.

 Never contributed to open source before? Let us help you! Everyone can contribute to open source, and we're here to show you how.

-.. _First-time Contributors: first-time/
+.. _First-time Contributors: /contributing/how/first-time/

 Code Contributions
 -------------------
@ -61,8 +61,8 @@ Something else
 If you've got your own idea for something, or if you don't see any
 tickets, or you want to be mentored on a ticket, or you aren't sure how
 to proceed, contact the project maintainers on
-`Twitter <http://twitter.com/pybeeware/>`__ or
-`Gitter <http://gitter.im/pybee/general>`__. The project maintainers love
+`Twitter <https://twitter.com/pybeeware/>`__ or
+`Gitter <https://gitter.im/pybee/general>`__. The project maintainers love
 collaborating, especially with new contributors, and will gladly answer
 any questions or walk you through any problems you may encounter.

--- a/content/contributing/how/dco/contents.lr
+++ b/content/contributing/how/dco/contents.lr
@ -4,6 +4,6 @@ title: Beginners guide to DCOs
 ---
 hide_from_index: yes
 ---
-body: The BeeWare project uses a mechansim known as a `Developer Certificate of Origin (DCO) <./dco/>`__ to manage the process of ensuring that we are legally allowed to distribute all the code and assets for the project.a DCO is a legally binding statement that asserts that you are the creator of your contribution, and that you wish to allow BeeWare to use your work.
+body: The BeeWare project uses a mechansim known as a `Developer Certificate of Origin (DCO) </contributing/how/dco/what>`__ to manage the process of ensuring that we are legally allowed to distribute all the code and assets for the project.a DCO is a legally binding statement that asserts that you are the creator of your contribution, and that you wish to allow BeeWare to use your work.
 ---
 summary: Because sometimes lawyers need to get involved...
--- a/content/contributing/how/dco/copyright/contents.lr
+++ b/content/contributing/how/dco/copyright/contents.lr
@ -57,7 +57,7 @@ So - a declaration that you've released your code into the public domain is actu
 Developer Certificates of Origin
 ---------------------------------

-There are a number of ways to manage the process of licensing contributions, but the BeeWare project uses a mechanism known as a `Developer Certificate of Origin <../what>`__. For more details on what  DCO is, and what it means, `see our explanatory guide <../what>`__.  If you've need help configuring your system to comply with our DCO `we've got some step by step instructions to help you out <../how>`__.
+There are a number of ways to manage the process of licensing contributions, but the BeeWare project uses a mechanism known as a `Developer Certificate of Origin </contributing/how/dco/what/>`__. For more details on what  DCO is, and what it means, `see our explanatory guide </contributing/how/dco/what/>`__.  If you've need help configuring your system to comply with our DCO `we've got some step by step instructions to help you out </contributing/how/dco/how/>`__.

 ---
 sort_key: 1
--- a/content/contributing/how/dco/what/contents+es.lr
+++ b/content/contributing/how/dco/what/contents+es.lr
@ -6,7 +6,7 @@ body:

 El proyecto BeeWare utiliza un mecanimo conocido como `Certificado de origen del Desarrollador - DCO (por sus siglas en inglés) </es/contribuir/como-ayudar/dco/>`__ para administrar este proceso. El DCO es una declaración jurídicamente vinculante que afirma que usted es el creador de su contribución y que desea permitir que BeeWare utilice su trabajo.

-El acuso de recibo de este permiso se realiza mediante un proceso de inicio de sesión en Git. El *sign-off* es una línea simple al final de la explicación para el parche. El texto del DCO es bastante simple (de `developercertificate.org <http://developercertificate.org>`__)::
+El acuso de recibo de este permiso se realiza mediante un proceso de inicio de sesión en Git. El *sign-off* es una línea simple al final de la explicación para el parche. El texto del DCO es bastante simple (de `developercertificate.org <https://developercertificate.org>`__)::

    Certificado de origen del desarrollador
    Versión 1.1
--- a/content/contributing/how/dco/what/contents.lr
+++ b/content/contributing/how/dco/what/contents.lr
@ -5,9 +5,9 @@ title: What is a DCO?
 body:


-The BeeWare project uses a mechansim known as a `Developer Certificate of Origin (DCO) <./dco/>`__ to manage this process. The DCO is a legally binding statement that asserts that you are the creator of your contribution, and that you wish to allow BeeWare to use your work.
+The BeeWare project uses a mechanism known as a `Developer Certificate of Origin (DCO) </contributing/how/dco/>`__ to manage this process. The DCO is a legally binding statement that asserts that you are the creator of your contribution, and that you wish to allow BeeWare to use your work.

-Acknowledgement of this permission is done using a sign-off process in Git. The sign-off is a simple line at the end of the explanation for the patch. The text of the DCO is fairly simple (from `developercertificate.org <http://developercertificate.org>`__)::
+Acknowledgement of this permission is done using a sign-off process in Git. The sign-off is a simple line at the end of the explanation for the patch. The text of the DCO is fairly simple (from `developercertificate.org <https://developercertificate.org>`__)::

    Developer Certificate of Origin
    Version 1.1
--- a/content/contributing/how/first-time/github/contents+es.lr
+++ b/content/contributing/how/first-time/github/contents+es.lr
@ -14,7 +14,7 @@ Introducción y requisitos previos
 Para contribuir con BeeWare, lo siguiente es necesario para empezar:

 - una cuenta `GitHub <https://github.com>`__
- en el caso de ediciones complejas familiaridad con `Git línea de comandos básicos <https://help.github.com/articles/set-up-git>`__ o familiaridad con una aplicación (`Windows <https://windows.github.com/>`__, `Mac <https://mac.github.com/>`__) para empujar las ediciones realizadas en su ordenador a GitHub.
+- en el caso de ediciones complejas familiaridad con `Git línea de comandos básicos <https://help.github.com/articles/set-up-git/>`__ o familiaridad con una aplicación (`Windows y Mac <https://desktop.github.com/>`__) para empujar las ediciones realizadas en su ordenador a GitHub.

 Hacer un Fork del repositorio
 ------------------------------------------
@ -100,7 +100,7 @@ Ejemplo:
 Realización de un Pull Request
 -------------------------------------------

-Una vez que hayas terminado los cambios, necesitas crear `un pull request <https://help.github.com/articles/using-pull-requests>`__ en GitHub. PyBee será notificado sobre la solicitud de Pull Request, revisaremos tus cambios, sugeriremos cualquier corrección si es necesario y luego uniremos tus cambios con la versión maestra.
+Una vez que hayas terminado los cambios, necesitas crear `un pull request <https://help.github.com/articles/about-pull-requests/>`__ en GitHub. PyBee será notificado sobre la solicitud de Pull Request, revisaremos tus cambios, sugeriremos cualquier corrección si es necesario y luego uniremos tus cambios con la versión maestra.

 En tu propio repositorio en GitHub haz clic en *Compare and Pull Request*

@ -116,16 +116,16 @@ Los correos electrónicos de GitHub le notificarán el proceso de seguimiento.



-.. |Fork button| image:: fork.png
+.. |Fork button| image:: /contributing/how/first-time/github/fork.png
  :class: img-fluid

-.. |Edit button| image:: edit.png
+.. |Edit button| image:: /contributing/how/first-time/github/edit.png
  :class: img-fluid

-.. |GitHub editor| image:: github_editor.png
+.. |GitHub editor| image:: /contributing/how/first-time/github/github_editor.png
  :class: img-fluid

-.. |image4| image:: pull_request.png
+.. |image4| image:: /contributing/how/first-time/github/pull_request.png
  :class: img-fluid

 ---
--- a/content/contributing/how/first-time/github/contents.lr
+++ b/content/contributing/how/first-time/github/contents.lr
@ -20,9 +20,8 @@ For contributing to BeeWare, the following is needed to get started:

 -  a `GitHub account <https://github.com>`__
 -  in the case of complex edits familiarity with `Git command line
-   basics <https://help.github.com/articles/set-up-git>`__ or
-   familiarity with an app (`Windows <https://windows.github.com/>`__,
-   `Mac <https://mac.github.com/>`__) to push your edits made on your
+   basics <https://help.github.com/articles/set-up-git/>`__ or
+   familiarity with an app (`Windows and Mac <https://desktop.github.com/>`__) to push your edits made on your
   computer to GitHub.

 Fork the repository
@ -121,7 +120,7 @@ Making a pull request
 ----------------------------------

 After you have finished your changes you need to create `a pull
-request <https://help.github.com/articles/using-pull-requests>`__ on
+request <https://help.github.com/articles/about-pull-requests/>`__ on
 GitHub. PyBee will get notified about the pull request, review your
 changes, suggest any corrections if needed and then *pull* your changes
 to the master version.
@ -142,16 +141,16 @@ GitHub emails will notify you for the follow up process.



-.. |Fork button| image:: fork.png
+.. |Fork button| image:: /contributing/how/first-time/github/fork.png
  :class: img-fluid

-.. |Edit button| image:: edit.png
+.. |Edit button| image:: /contributing/how/first-time/github/edit.png
  :class: img-fluid

-.. |GitHub editor| image:: github_editor.png
+.. |GitHub editor| image:: /contributing/how/first-time/github/github_editor.png
  :class: img-fluid

-.. |image4| image:: pull_request.png
+.. |image4| image:: /contributing/how/first-time/github/pull_request.png
  :class: img-fluid

 ---
--- a/content/contributing/how/first-time/imposter-syndrome/contents+pt.lr
+++ b/content/contributing/how/first-time/imposter-syndrome/contents+pt.lr
@ -18,7 +18,7 @@ Portanto - não tenha medo de contribuir. Se você chegou até aqui, já demonst

 Agora é hora arregaçar as mangas, e `escolher um projeto onde você possa contribuir`_.

-.. _escolher um projeto onde você possa contribuir: ../what
+.. _escolher um projeto onde você possa contribuir: /pt_BR/contributing/how/first-time/what/
 ---
 sort_key: 1
 ---
--- a/content/contributing/how/first-time/imposter-syndrome/contents.lr
+++ b/content/contributing/how/first-time/imposter-syndrome/contents.lr
@ -21,7 +21,7 @@ So - don't be afraid to contribute. If you've gotten this far, you've demonstrat

 Now it's time to roll up your sleeves, and `pick a project where you can contribute`_.

-.. _pick a project where you can contribute: ../what
+.. _pick a project where you can contribute: /contributing/how/dco/what/
 ---
 sort_key: 1
 ---
--- a/content/contributing/how/first-time/more/contents+pt.lr
+++ b/content/contributing/how/first-time/more/contents+pt.lr
@ -7,7 +7,7 @@ Esses recursos vem de fora da BeeWare, mas estão repletos de informação. (em

 -----

-Você tem algum outro link? `Envie para a lista! <https://github.com/pybee/pybee.github.io/edit/lektor/content/contributing/first-time/more/contents.lr>`_
+Você tem algum outro link? `Envie para a lista! <https://github.com/pybee/pybee.github.io/edit/lektor/content/contributing/how/first-time/more/contents+pt.lr>`_

 ---
 incomplete: no
--- a/content/contributing/how/first-time/more/contents.lr
+++ b/content/contributing/how/first-time/more/contents.lr
@ -12,7 +12,7 @@ These resources come from outside BeeWare, but they are full of useful informati

 -----

-Do you have another link? `Add it to the list! <https://github.com/pybee/pybee.github.io/edit/lektor/content/contributing/first-time/more/contents.lr>`_
+Do you have another link? `Add it to the list! <https://github.com/pybee/pybee.github.io/edit/lektor/content/contributing/how/first-time/more/contents.lr>`_

 ---
 summary: There are many more resources for first time contributors
--- a/content/contributing/how/first-time/setting-up-your-environment/contents+es.lr
+++ b/content/contributing/how/first-time/setting-up-your-environment/contents+es.lr
@ -20,10 +20,10 @@ Para las siguientes instrucciones, vamos a suponer que tu sabes exactamente que
 pyenv
 ~~~~~~

-`pyenv <https://github.com/yyuu/pyenv>` _ es una forma de obtener múltiples versiones de Python trabajando en tu máquina al mismo tiempo. Te permite elegir que versión de Python utilizar para un proyecto en particular.
+`pyenv <https://github.com/pyenv/pyenv>` _ es una forma de obtener múltiples versiones de Python trabajando en tu máquina al mismo tiempo. Te permite elegir que versión de Python utilizar para un proyecto en particular.

 * MacOSX - Puedes instalar pyenv a través de `brew </es/contribuir/como-ayudar/principiantes/que-es/gestor-de-paquetes/>`_, ejecutando :code:`brew install pyenv`
-* Otro - utiliza el `instalador automático <https://github.com/yyuu/pyenv-installer>`_.
+* Otro - utiliza el `instalador automático <https://github.com/pyenv/pyenv-installer>`_.

 Una vez :code: `pyenv` está instalado, necesitas instalar la versión específica de Python. Esta información se almacena en un archivo :code:`.python-version`, que significa que puede tener diferentes versiones de Python utilizadas en diferentes proyectos en tu computadora.

@ -35,7 +35,7 @@ Para instalar y configurar la versión de Python:
    $ pyenv install 3.5.1
    $ pyenv local 3.5.1

-Más información sobre pyenv está disponible en su `sitio web <https://github.com/yyuu/pyenv/blob/master/COMMANDS.md>`_
+Más información sobre pyenv está disponible en su `sitio web <https://github.com/pyenv/pyenv/blob/master/COMMANDS.md>`_

 virtualenv
 ---------------
--- a/content/contributing/how/first-time/setting-up-your-environment/contents+pt.lr
+++ b/content/contributing/how/first-time/setting-up-your-environment/contents+pt.lr
@ -20,7 +20,7 @@ qual versão do Python esperamos que o código funcione.
 Para as próximas instruções, nós vamos presumir que você sabe exatamente
 qual versão do Python você precisa instalar. Normalmente isso está listado no
 arquivo README.md ou no tutorial de informação. Nosso sistema `CI 
-</contributing/first-time/what-is-a/ci>`_ deve falar exatamente qual versão
+</pt_BR/contributing/how/first-time/what-is-a/ci>`_ deve falar exatamente qual versão
 do Python é necessária também. Então se você estiver perdido, tente procurar
 no arquivo :code:`.travis.yml` ou :code:`circle.yml` para a versão específica que
 você precisa.
@ -28,12 +28,12 @@ você precisa.
 pyenv
 ~~~~~~

-`pyenv <https://github.com/yyuu/pyenv>`_ é uma forma de ter múltiplas versões do
+`pyenv <https://github.com/pyenv/pyenv>`_ é uma forma de ter múltiplas versões do
 Python funcionando na mesma máquina ao mesmo tempo. Ele te permite escolher qualquer
 versão que você precisa para um projeto em particular.

- * MacOSX - Você pode instalar pyenv via `brew </contributing/first-time/what-is-a/package-manager>`_, executando :code:`brew install pyenv`
- * Outros - use o `instalador automático <https://github.com/yyuu/pyenv-installer>`_. 
+ * MacOSX - Você pode instalar pyenv via `brew </pt_BR/contributing/how/first-time/what-is-a/package-manager>`_, executando :code:`brew install pyenv`
+ * Outros - use o `instalador automático <https://github.com/pyenv/pyenv-installer>`_. 

 Uma vez que :code:`pyenv` esteja instalado, você precisa instalar a versão especifica
 do Python. Essa informação está guardada em um arquivo :code:`.python-version`, o
@ -48,7 +48,7 @@ Para instalar e configurar uma versão do Python:
    $ pyenv install 3.5.1
    $ pyenv local 3.5.1

-Mais informações sobre o pyenv estão disponíveis em `seu website <https://github.com/yyuu/pyenv/blob/master/COMMANDS.md>`_
+Mais informações sobre o pyenv estão disponíveis em `seu website <https://github.com/pyenv/pyenv/blob/master/COMMANDS.md>`_

 virtualenv
 -----------
@ -60,7 +60,7 @@ determinados pacotes do Python estejam disponíveis por vez é de grande ajuda.

 Uma forma de fazer isso é via `virtualenv <https://virtualenv.pypa.io/en/stable/>`_. 

-Usando `pip </contributing/first-time/what-is-a/package-manager>`_, nós podemos instalar 
+Usando `pip </pt_BR/contributing/how/first-time/what-is-a/package-manager>`_, nós podemos instalar 
 o virtualenv.

 .. code-block:: bash
--- a/content/contributing/how/first-time/setting-up-your-environment/contents.lr
+++ b/content/contributing/how/first-time/setting-up-your-environment/contents.lr
@ -25,7 +25,7 @@ we expect the code to work with.
 For the following instructions, we're going to assume that you know exactly
 which version of Python you need to install. Normally this is listed in the
 README.md file or in the tutorial information. Our `CI
-</contributing/first-time/what-is-a/ci>`_ systems have to be told exactly what
+</contributing/how/first-time/what-is-a/ci>`_ systems have to be told exactly what
 version of Python is required, too. So if you're really stuck, try looking at
 the :code:`.travis.yml` or :code:`circle.yml` file for the specific version you
 need. 
@ -33,12 +33,12 @@ need.
 pyenv
 ~~~~~~

-`pyenv <https://github.com/yyuu/pyenv>`_ is a way to get multiple versions of 
+`pyenv <https://github.com/pyenv/pyenv>`_ is a way to get multiple versions of 
 Python working on your machine at the same time. It allows you to pick and choose whichever
 version you need for a particular project. 

- * MacOSX - You can install pyenv via `brew </contributing/first-time/what-is-a/package-manager>`_,  by running :code:`brew install pyenv`
- * Other - use the `automatic installer <https://github.com/yyuu/pyenv-installer>`_. 
+ * MacOSX - You can install pyenv via `brew </contributing/how/first-time/what-is-a/package-manager>`_,  by running :code:`brew install pyenv`
+ * Other - use the `automatic installer <https://github.com/pyenv/pyenv-installer>`_. 

 Once :code:`pyenv` is installed, you need to install the specific Python
 version. This information is stored in a  :code:`.python-version` file, which
@ -53,7 +53,7 @@ To install and set Python version:
    $ pyenv install 3.5.1
    $ pyenv local 3.5.1

-More information about pyenv is available on `their website <https://github.com/yyuu/pyenv/blob/master/COMMANDS.md>`_
+More information about pyenv is available on `their website <https://github.com/pyenv/pyenv/blob/master/COMMANDS.md>`_

 virtualenv
 -----------
@ -65,7 +65,7 @@ Python packages are available at any one time is handy.

 One way we can do this is via `virtualenv <https://virtualenv.pypa.io/en/stable/>`_. 

-Using `pip </contributing/first-time/what-is-a/package-manager>`_, we can install virtualenv
+Using `pip </contributing/how/first-time/what-is-a/package-manager>`_, we can install virtualenv

 .. code-block:: bash
  
--- a/content/contributing/how/first-time/what-is-a/package-manager/contents+es.lr
+++ b/content/contributing/how/first-time/what-is-a/package-manager/contents+es.lr
@ -18,7 +18,7 @@ así como uno específicamente para los paquetes de Python.
 Mac OS X
 -------------

-`Homebrew <http://brew.sh/>`_ es el estándar para instalar software en su
+`Homebrew <https://brew.sh/>`_ es el estándar para instalar software en su
 Mac. Este es el sistema que se utiliza si ejecuta un comando :code:`brew install`.

 Linux
--- a/content/contributing/how/first-time/what-is-a/package-manager/contents+pt.lr
+++ b/content/contributing/how/first-time/what-is-a/package-manager/contents+pt.lr
@ -13,7 +13,7 @@ operacional, e também para um pacote específico do Python.
 MacOSX
 ---------------

-`Homebrew <http://brew.sh/>`_ é o padrão para instalar softwares no seu Mac.
+`Homebrew <https://brew.sh/>`_ é o padrão para instalar softwares no seu Mac.
 Esse é o sistema usado se você rodar o comando :code:`brew install`.

 Linux
--- a/content/contributing/how/first-time/what-is-a/package-manager/contents.lr
+++ b/content/contributing/how/first-time/what-is-a/package-manager/contents.lr
@ -18,7 +18,7 @@ as well as one specifically for Python packages.
 MacOSX
 ---------------

-`Homebrew <http://brew.sh/>`_ is the standard for installing software on your
+`Homebrew <https://brew.sh/>`_ is the standard for installing software on your
 Mac. This is the system that's used if you run a :code:`brew install` command. 

 Linux
--- a/content/contributing/how/first-time/what/batavia/contents+pt.lr
+++ b/content/contributing/how/first-time/what/batavia/contents+pt.lr
@ -10,16 +10,16 @@ Isso significa que é possível escrever aplicações web 100% em Python - entã
 Antes de você começar
 --------------------------

-Nas próximas instruções , nós vamos assumir que você está familiar com `Github e fazer pull requests </contributing/first-time/github>`__. Nós também vamos assumir algum nível de conhecimento em Python e JavaScript; se qualquer coisa que nós descrevermos não fizer sentido, não se preocupe - nós estaremos mais que felizes em preencher essas lacunas. A partir desse ponto, nós não sabemos o que você não sabe :-)
+Nas próximas instruções , nós vamos assumir que você está familiar com `Github e fazer pull requests </pt_BR/contributing/how/first-time/github>`__. Nós também vamos assumir algum nível de conhecimento em Python e JavaScript; se qualquer coisa que nós descrevermos não fizer sentido, não se preocupe - nós estaremos mais que felizes em preencher essas lacunas. A partir desse ponto, nós não sabemos o que você não sabe :-)

 Esse tutorial irá focar-se nas contribuições de código. Se seu interesse/habilidades estiver em outro lugar(ex, teste, documentação), nos deixe saber, assim podemos fazer outras sugestões.

-Antes de você fazer sua primeira contribuição, de uma volta com Batavia. As instruções no `guia para começar <http://batavia.readthedocs.io/en/latest/intro/getting-started.html>`__ *devem* se suficiente para continuar. Se você ficar preso, me deixe saber e eu vou libertá-lo. E se você ficou preso, esse também será um lugar para sua primeira contribuição - pense em quais instruções poderiam ter feito você *não* ficar preso, e contribua para atualizar o README.
+Antes de você fazer sua primeira contribuição, de uma volta com Batavia. As instruções no `guia para começar <https://batavia.readthedocs.io/en/latest/intro/index.html>`__ *devem* se suficiente para continuar. Se você ficar preso, me deixe saber e eu vou libertá-lo. E se você ficou preso, esse também será um lugar para sua primeira contribuição - pense em quais instruções poderiam ter feito você *não* ficar preso, e contribua para atualizar o README.

 Sua primeira contribuição
 ------------------------------

-Uma vez que você tenha feito Batavia funcionar, você estará pronto para fazer sua primeira contribuição do código. O `guia de contribuição <http://batavia.readthedocs.io/en/latest/internals/contributing.html>`__ irá guiá-lo através do processo de configuração do ambiente de desenvolvimento. Utilize esse guia até você conseguir rodar a suíte de testes do Batavia - uma vez que você esteja pronto para rodar a suíte de testes sem nenhuma falha, você estará pronto para adicionar alguns códigos novos para a base de código do Batavia.
+Uma vez que você tenha feito Batavia funcionar, você estará pronto para fazer sua primeira contribuição do código. O `guia de contribuição <https://batavia.readthedocs.io/en/latest/community/contributing.html>`__ irá guiá-lo através do processo de configuração do ambiente de desenvolvimento. Utilize esse guia até você conseguir rodar a suíte de testes do Batavia - uma vez que você esteja pronto para rodar a suíte de testes sem nenhuma falha, você estará pronto para adicionar alguns códigos novos para a base de código do Batavia.

 Para conseguir implementar uma virtual machine Python completa, Batavia precisa implementar todas as excentricidades do comportamento do Python. Por exemplo, Python sempre deixa você multiplicar uma string por um inteiro (ex, ``“foo” * 3`` => ``“foofoofoo”``). O comportamento do JavaScript pode ser um pouco diferente, dependendo das circunstancias - então nós precisamos criar uma biblioteca que implementa o comportamento desejado do Python.

--- a/content/contributing/how/first-time/what/voc/contents+pt.lr
+++ b/content/contributing/how/first-time/what/voc/contents+pt.lr
@ -17,11 +17,11 @@ Isto é similar ao Jython que te permite rodar Python no Java; mas é diferente
 Antes de você começar
 -----------------------

-Nas próximas instruções, nós vamos assumir que você esta familiarizado com o `Github e a fazer pull requests </contributing/first-time/github>`__. Eu também vou presumir que você tenha algum conhecimento de Python e Java; se qualquer coisa descrita aqui não fizer sentido, não se preocupe - nós estaremos mais do que felizes em preencher essas lacunas. A partir deste ponto, nós não sabemos o que você não sabe :-)
+Nas próximas instruções, nós vamos assumir que você esta familiarizado com o `Github e a fazer pull requests </pt_BR/contributing/how/first-time/github>`__. Eu também vou presumir que você tenha algum conhecimento de Python e Java; se qualquer coisa descrita aqui não fizer sentido, não se preocupe - nós estaremos mais do que felizes em preencher essas lacunas. A partir deste ponto, nós não sabemos o que você não sabe :-)

 Nós vamos assumir que você está interessado em contribuir com código. Se seu interesse/habilidades estiver em outro lugar(ex, testes, documentação), nos deixe saber, assim podemos fazer outras sugestões.

-Antes de você fazer sua primeira contribuição, de uma volta com VOC. As instruções no `guia para começar <https://voc.readthedocs.io/en/latest/intro/getting-started.html>`__ *devem ser* suficientes para prosseguir. Se você ficar preso, nos deixe saber e eu vou ajuda-lo. E se você ficou preso, esse também será um lugar para sua primeira contribuição - pense em quais instruções poderiam ter feito você *não* ficar preso, e contribua para atualizar o README.
+Antes de você fazer sua primeira contribuição, de uma volta com VOC. As instruções no `guia para começar <https://voc.readthedocs.io/en/latest/intro/index.html>`__ *devem ser* suficientes para prosseguir. Se você ficar preso, nos deixe saber e eu vou ajuda-lo. E se você ficou preso, esse também será um lugar para sua primeira contribuição - pense em quais instruções poderiam ter feito você *não* ficar preso, e contribua para atualizar o README.

 Sua primeira contribuição
 -------------------------------
--- a/content/contributing/how/process/contents+pt.lr
+++ b/content/contributing/how/process/contents+pt.lr
@ -14,7 +14,7 @@ Assine seu trabalho
 Antes de nós podermos aceitar sua contribuição no BeeWare, você precisa nos dar permissão para faze-lo. Já que você é um autor de um trabalho
 criativo (um pedaço de código, ou alguma documentação), você automaticamente detêm os direitos desse trabalho. BeeWare não pode usar sua contribuição legalmente a menos que você nos dê permissão para faze-lo.

-O projeto BeeWare usa um mecanismo conhecido como um `Certificado de Origem do Desenvolvedor(DCO) <./dco/>`__ para admnistrar esse processo. O DCO é uma declaração legal obrigatória que atesta que você é o criador de uma contribuição e que você permite que o BeeWare use o seu trabalho.
+O projeto BeeWare usa um mecanismo conhecido como um `Certificado de Origem do Desenvolvedor(DCO) </pt_BR/contributing/how/dco/>`__ para admnistrar esse processo. O DCO é uma declaração legal obrigatória que atesta que você é o criador de uma contribuição e que você permite que o BeeWare use o seu trabalho.

 Para indicar que você concorda com os termos do DCO, você precisa adicionar uma linha em todas suas mensagens de commit::

@ -22,7 +22,7 @@ Para indicar que você concorda com os termos do DCO, você precisa adicionar um

 Se você configurou seu ``user.name`` e ``user.email`` na sua configuração do git, você pode assinar seu commit automaticamente com ``git commit -s``.

-Se você tem mais perguntas sobre o DCO, porque ele é necessário, o que significa e como configurar seu sistema para usa-lo, veja `Guia do Iniciante do DCO <./dco/>`__, ou `entre em contato com o time de desenvolvimento </community/team>`__.
+Se você tem mais perguntas sobre o DCO, porque ele é necessário, o que significa e como configurar seu sistema para usa-lo, veja `Guia do Iniciante do DCO </pt_BR/contributing/how/dco/>`__, ou `entre em contato com o time de desenvolvimento </community/team>`__.

 ---
 incomplete: yes
--- a/content/contributing/how/process/contents+zh.lr
+++ b/content/contributing/how/process/contents+zh.lr
@ -19,7 +19,7 @@ body:

 我們把你的貢獻合並起來之前，你必須給我們許可這樣做。因為你是作品的製造者（源碼或者文檔的作者），時你有知識產權的。BeeWare必須得到你的許可才能合法地使用你的貢獻。

-BeeWare項目是以 `Developer Certificate of Origin (DCO) <./dco/>`__ 來管理這個過程. DCO是一種有法律约束力的宣告，是保證你是貢獻的製造者，而且你想讓BeeWare使用貢獻。
+BeeWare項目是以 `Developer Certificate of Origin (DCO) </zh_TW/contributing/how/dco/>`__ 來管理這個過程. DCO是一種有法律约束力的宣告，是保證你是貢獻的製造者，而且你想讓BeeWare使用貢獻。

 為了表示你同意DCO的條款，把下面的一行加入你的git commit message::

@ -27,7 +27,7 @@ BeeWare項目是以 `Developer Certificate of Origin (DCO) <./dco/>`__ 來管理

 如果在git配置你指定 ``user.name`` 和 ``user.email``, 你能以 ``git commit -s`` 來自動地簽commit message.

-如果你還有關於Developer Certificates of Origin的問題，為什麼需要它，它是什麼意思，以及怎麼配置系統使用它，看看 `The Beginners Guide to DCOs <./dco/>`__, 或者 `聯繫核心團隊 </community/team>`__.
+如果你還有關於Developer Certificates of Origin的問題，為什麼需要它，它是什麼意思，以及怎麼配置系統使用它，看看 `The Beginners Guide to DCOs </zh_TW/contributing/how/dco/>`__, 或者 `聯繫核心團隊 </community/team>`__.

 ---
 incomplete: yes
--- a/content/contributing/how/process/contents.lr
+++ b/content/contributing/how/process/contents.lr
@ -19,7 +19,7 @@ Sign your work

 Before we can merge your contribution into BeeWare, you need to give us permission to do so. Since you're an author of a creative work (a piece of code, or some documentation), you automatically own the copyright for that work. BeeWare can't legally use that contribution unless you give us permission to do so.

-The BeeWare project uses a mechansim known as a `Developer Certificate of Origin (DCO) <./dco/>`__ to manage this process. The DCO is a legally binding statement that asserts that you are the creator of your contribution, and that you wish to allow BeeWare to use your work.
+The BeeWare project uses a mechansim known as a `Developer Certificate of Origin (DCO) </contributing/how/dco/>`__ to manage this process. The DCO is a legally binding statement that asserts that you are the creator of your contribution, and that you wish to allow BeeWare to use your work.

 To indicate that you agree to the terms of the DCO, you just add a line to every git commit message::

@ -27,7 +27,7 @@ To indicate that you agree to the terms of the DCO, you just add a line to every

 If you set your ``user.name`` and ``user.email`` as part of your git configuration, you can sign your commit automatically with ``git commit -s``.

-If you have more questions about Developer Certificates of Origin, why are required, what they mean, and how to configure your system to use them, see `The Beginners Guide to DCOs <./dco/>`__, or `get in touch with the core team </community/team>`__.
+If you have more questions about Developer Certificates of Origin, why are required, what they mean, and how to configure your system to use them, see `The Beginners Guide to DCOs </contributing/how/dco/>`__, or `get in touch with the core team </community/team>`__.

 ---
 incomplete: yes
--- a/content/news/buzz/2017-google-summer-of-code-final-report-dayanne-fernandes/contents+es.lr
+++ b/content/news/buzz/2017-google-summer-of-code-final-report-dayanne-fernandes/contents+es.lr
@ -19,7 +19,7 @@ Resultados
 La propuesta se centra no sólo en el puerto de `Tkinter`_ a `Toga`_, sino en la asignación de los widgets necesarios para una aplicación real utilizando `Toga`_. Para ayudarme a mapear esto he estudiado más sobre `Tkinter`_, `Toga`_, `Colosseum`_, `rubicon-objc`_, `Objective-C`_, `Cocoa`_ y `CSS`_.

 .. _Objective-C: https://developer.apple.com/documentation/objectivec
-.. _Cocoa: https://developer.apple.com/library/content/documentation/General/Conceptual/DevPedia-CocoaCore/Cocoa.html
+.. _Cocoa: http://developer.apple.com/library/content/documentation/General/Conceptual/DevPedia-CocoaCore/Cocoa.html

 .. _CSS: https://www.w3.org/Style/CSS/

--- a/content/news/buzz/2017-google-summer-of-code-final-report-dayanne-fernandes/contents.lr
+++ b/content/news/buzz/2017-google-summer-of-code-final-report-dayanne-fernandes/contents.lr
@ -24,7 +24,7 @@ Results
 The proposal focus not only on the port of `Tkinter`_ to `Toga`_, but on mapping the necessary widgets for a real application using `Toga`_ framework. To help me to map this I studied more about `Tkinter`_, `Toga`_, `Colosseum`_, `rubicon-objc`_, `Objective-C`_, `Cocoa`_ and `CSS`_.

 .. _Objective-C: https://developer.apple.com/documentation/objectivec
-.. _Cocoa: https://developer.apple.com/library/content/documentation/General/Conceptual/DevPedia-CocoaCore/Cocoa.html
+.. _Cocoa: http://developer.apple.com/library/content/documentation/General/Conceptual/DevPedia-CocoaCore/Cocoa.html
 .. _CSS: https://www.w3.org/Style/CSS/

 The work I did during GSoC were sent throught the `PR 65`_, reported on the `Issue 58`_ and the final demonstration of the work can be seen in this `link`_. There were widgets used on `Cricket`_ that weren't ready yet on `Toga`_, so some improvements were necessary on `Toga`_ so that I could use them on `Cricket`_. In summary here are some PRs and issues that I contributed to get my work done in `Cricket`_:
@ -169,4 +169,3 @@ I would like to truly thank my mentors `Russell Keith-Magee`_ and `Elias Dornele

 ---
 pub_date: 2017-08-25
---
--- a/content/news/buzz/a-new-yak-for-the-herd-beekeeper/contents+es.lr
+++ b/content/news/buzz/a-new-yak-for-the-herd-beekeeper/contents+es.lr
@ -8,7 +8,7 @@ Escribir suites de pruebas es una habilidad que es una parte vital del entrenami

 Un paso importante en la "nivelación" de su experiencia de pruebas es comenzar a usar un servicio de integración continua o CI. Un servicio de CI es una herramienta que ejecuta automáticamente su suite de pruebas cada vez que alguien realiza un cambio o cada vez que alguien propone un cambio en forma de una solicitud de PR. El uso de un servicio de CI garantiza que su código *siempre* pase su suite de pruebas - no puede introducirse accidentalmente en un cambio que rompe una prueba, porque obtendrá una notificación de advertencia roja grande.

-Un CI es un servicio tan importante que muchas empresas sólo existen para proporcionar CI-as-a-service. El proyecto BeeWare ha utilizado, para diversos proyectos, TravisCI y https://circleci.com. Ambas herramientas proporcionan niveles gratuitos para proyectos de código abierto y han patrocinado generosamente BeeWare con actualizaciones de capacidad en varias ocasiones.
+Un CI es un servicio tan importante que muchas empresas sólo existen para proporcionar CI-as-a-service. El proyecto BeeWare ha utilizado, para diversos proyectos, `TravisCI <https://travis-ci.com>`__ y `CircleCI <https://circleci.com>`__. Ambas herramientas proporcionan niveles gratuitos para proyectos de código abierto y han patrocinado generosamente BeeWare con actualizaciones de capacidad en varias ocasiones.

 Sin embargo, BeeWare ha tenido una relación interesante con los servicios comerciales de CI. Esto es por dos razones.

@ -38,13 +38,13 @@ No hay nada específico acerca de AWS EC2 o ECS tampoco - se podría utilizar Li

 Todo lo que necesita es un sitio web que puede recibir las notificaciones de eventos de GitHub e iniciar los contenedores de Docker en respuesta.

-A principios de julio, me encontré entre trabajos, y pronuncié la fatídica pregunta: "¿Cuán difícil podría ser?" Y así, hoy, estoy anunciando `BeeKeeper <http://pybee.org/beekeeper>`__ - el propio servicio de CI de BeeWare.
+A principios de julio, me encontré entre trabajos, y pronuncié la fatídica pregunta: "¿Cuán difícil podría ser?" Y así, hoy, estoy anunciando `BeeKeeper </es/proyecto/proyectos/herramientas/beekeeper>`__ - el propio servicio de CI de BeeWare.

 BeeKeeper se despliega como un sitio web de Heroku, escrito con Django. Después de configurarlo con las credenciales de Github y AWS, escucha los webhooks de Github. Cuando se detecta una solicitud de pull o Push, BeeKeeper crea una solicitud de generación; que la solicitud de construcción inspecciona el código en el repositorio en busca de un archivo de configuración ``beekeeper.yml``. Ese archivo de configuración describe el pipeline de tareas que se van a realizar, y para cada tarea, el tipo de máquina que se debe usar, las variables de entorno que se requieran y la imagen de Docker que se utilizará.

 BeeKeeper también permite al administrador del sitio describir qué recursos se utilizarán para satisfacer las compilaciones. Una tarea puede decir que necesita una instancia de "Alta CPU"; pero la instancia BeeKeeper puede determinar lo que significa "alta CPU" - ¿es 4 CPUs o 32? ¿Cuándo esas máquinas son coladas hacia arriba, cuánto tiempo se les permitirá sentarse inactivo antes de ser apagado de nuevo? ¿Cuántas máquinas deben estar permanentemente en el grupo de trabajo? ¿Y cuál es el límite superior de las máquinas que se iniciará?

-Una herramienta complementaria para BeeKeeper es `Waggle <https://pybee.org/waggle>`__. Waggle es una herramienta que prepara una definición local de una tarea para que pueda ser utilizada por BeeKeeper - compila la imagen de Docker y la carga en ECS para que pueda ser referenciada por tareas. (Se llama "Waggle" porque cuando las abejas obreras descubren una buena fuente de néctar, regresan a la colmena y hacen una 'danza' que le dice a otras abejas cómo hacer para encontrar esa fuente).
+Una herramienta complementaria para BeeKeeper es `Waggle </es/proyecto/proyectos/herramientas/waggle>`__. Waggle es una herramienta que prepara una definición local de una tarea para que pueda ser utilizada por BeeKeeper - compila la imagen de Docker y la carga en ECS para que pueda ser referenciada por tareas. (Se llama "Waggle" porque cuando las abejas obreras descubren una buena fuente de néctar, regresan a la colmena y hacen una 'danza' que le dice a otras abejas cómo hacer para encontrar esa fuente).

 También hemos proporcionado un repositorio llamado `Comb <https://github.com/pybee/comb>`__ (nombrado después del peine de miel, las abejas del lugar almacenan todo el néctar que encuentran) que define las configuraciones de la tarea que una instancia de BeeKeeper puedo usar. Hemos proporcionado algunas definiciones simples como parte del repositorio base de Comb; cada implementación de BeeKeeper debe tener uno de estos repositorios propios.

--- a/content/news/buzz/a-new-yak-for-the-herd-beekeeper/contents.lr
+++ b/content/news/buzz/a-new-yak-for-the-herd-beekeeper/contents.lr
@ -12,7 +12,7 @@ CI is such an important service that many companies exist solely to provide CI-a

 However, the BeeWare has had an interesting relationship with commercial CI services. This is for two reasons.

-Firstly, our test suites - especially for `VOC <https://pybee.org/voc>`__ and `Batavia <https://pybee.com/batavia>`__ - take a long time to run. These two projects require tests that repeatedly start and shut down virtual machines (for Java and JavaScript, respectively), and no matter how much you optimize the code being tested, the startup and shutdown time of a virtual machine eventually adds up. We also need to run our test suites on multiple versions of Python - at present, we support Python 3.4, 3.5 and 3.6, with 3.7 on the horizon. There are also subtle changes in micro versions that may require testing.
+Firstly, our test suites - especially for `VOC </project/projects/bridges/voc>`__ and `Batavia </project/projects/bridges/batavia>`__ - take a long time to run. These two projects require tests that repeatedly start and shut down virtual machines (for Java and JavaScript, respectively), and no matter how much you optimize the code being tested, the startup and shutdown time of a virtual machine eventually adds up. We also need to run our test suites on multiple versions of Python - at present, we support Python 3.4, 3.5 and 3.6, with 3.7 on the horizon. There are also subtle changes in micro versions that may require testing.

 We've been able to speed up the duration of a test run by splitting up the test suite and running parts of the suite in parallel, but that forces us up against the second problem. Commercial CI services usually operate on a subscription model; higher subscriptions providing more simultaneous resources. However, our usage pattern is highly unusual. Most of the year, we get a slow trickle of pull requests that require testing. However, a couple of times a year, we have a large sprint, and we have a flood of contributions over a short period of time. At PyCon US, we have had groups of 40 people submitting patches - and they all need their submissions tested by CI. And time is a factor - the sprints only last a couple of days, so a fast turnaround on testing is essential.

@ -38,13 +38,13 @@ There's nothing specific about AWS EC2 or ECS either - you could just as easily

 All you need then is a website that can receive GitHub event notifications, and start Docker containers in response.

-At the start of July, I found myself between jobs, and uttered the fateful question "How hard could it be?" And so, today, I'm announcing `BeeKeeper <http://pybee.org/beekeeper>`__ - BeeWare's own CI service.
+At the start of July, I found myself between jobs, and uttered the fateful question "How hard could it be?" And so, today, I'm announcing `BeeKeeper </project/projects/tools/beekeeper>`__ - BeeWare's own CI service.

 BeeKeeper deploys as a Heroku website, written using Django. After configuring it with Github and AWS credentials, it listens for Github webhooks. When a Pull Request or Push is detected, BeeKeeper creates a build request; that build request inspects the code in the repository looking for a ``beekeeper.yml`` configuration file. That configuration file describes the pipeline of tasks that will be performed, and for each task, the type of machine that should be used, any environment variables that are required, and the Docker image that will be used.

 BeeKeeper also allows the site admin to describe what resources will be used to satisfy builds. A task can say it needs a "High CPU" instance; but the BeeKeeper instance can determine what "High CPU" means - is it 4 CPUs or 32? When those machines are spooled up, how long will they be allowed to sit idle before being shut down again? How many machines should be sitting in the pool permanently? And what is the upper limit on machines that will be started?

-A companion tool to BeeKeeper is `Waggle <https://pybee.org/waggle>`__. Waggle is a tool that prepares a local definition of a task so it can be used by BeeKeeper - it compiles the Docker image, and uploads it into ECS so that it can be referenced by tasks. (It's called "Waggle" because when worker bees discover a good source of nectar, they return to the hive and do a `waggle dance <https://en.wikipedia.org/wiki/Waggle_dance>`__ that tells other bees how to find that source).
+A companion tool to BeeKeeper is `Waggle </project/projects/tools/waggle>`__. Waggle is a tool that prepares a local definition of a task so it can be used by BeeKeeper - it compiles the Docker image, and uploads it into ECS so that it can be referenced by tasks. (It's called "Waggle" because when worker bees discover a good source of nectar, they return to the hive and do a `waggle dance <https://en.wikipedia.org/wiki/Waggle_dance>`__ that tells other bees how to find that source).

 We've also provided a repository called `Comb <https://github.com/pybee/comb>`__ (named after honey comb, the place bees store all the nectar they find) that defines the task configurations that a BeeKeeper instance can use. We've provided some simple definitions as part of the base Comb repository; each BeeKeeper deployment should have one of these repositories of it's own.

@ -52,7 +52,7 @@ There's still a lot of work to do, but we're already using BeeKeeper to Batavia

 Although BeeKeeper was written to meet the needs of the BeeWare project, it's an open source tool available for anyone to use. If you'd like to take BeeKeeper for a spin, come along to the sprints, or `check out the code on GitHub <https://github.com/pybee/beekeeper>`__.

-BeeKeeper is also an example of the sort of product you'd see more of if BeeWare development was funded full time. I was able to build BeeKeeper because I had a spare couple of weeks between jobs. There is no end to the tools and libraries like BeeKeeper and Waggle that could be built to support the software development process - all that is missing is the resources needed to develop those tools. If you'd like to see more tools like BeeKeeper in the world, please consider `joining the BeeWare project as a financial member <https://pybee.org/contributing/membership/>`__. Every little bit helps, and if we can reach a critical mass of supporters, I'll be able to start working on BeeWare full time.
+BeeKeeper is also an example of the sort of product you'd see more of if BeeWare development was funded full time. I was able to build BeeKeeper because I had a spare couple of weeks between jobs. There is no end to the tools and libraries like BeeKeeper and Waggle that could be built to support the software development process - all that is missing is the resources needed to develop those tools. If you'd like to see more tools like BeeKeeper in the world, please consider `joining the BeeWare project as a financial member </contributing/membership/>`__. Every little bit helps, and if we can reach a critical mass of supporters, I'll be able to start working on BeeWare full time.

 ---
 pub_date: 2017-07-31
--- a/content/news/buzz/a-request-for-your-help/contents+es.lr
+++ b/content/news/buzz/a-request-for-your-help/contents+es.lr
@ -6,7 +6,7 @@ body:

 Hace unos 4 años, hice el primer *commit* con `Cricket`_ - la primera herramienta que eventualmente se convertiría en parte de la suite BeeWare. Desde entonces, el proyecto BeeWare ha crecido para abarcar soporte para plataformas móviles, dos implementaciones alternativas de Python y un conjunto de widgets multi-plataforma, así como las herramientas de desarrollo que iniciaron el proyecto originalmente.

-.. _Cricket: http://pybee.org/cricket
+.. _Cricket: /es/proyecto/proyectos/herramientas/cricket/

 Durante la mayor parte de este tiempo, BeeWare ha sido un esfuerzo voluntario. Inicialmente, fue un proyecto en solitario; sin embargo, en el último año en particular, el número de personas que han contribuido a BeeWare ha crecido rápidamente. Más de 300 personas han hecho contribuciones a las diversas herramientas y librerías de BeeWare, debido, al menos en parte, a las `Monedas de Desafío`_ que hemos estado ofreciendo en los sprints.

@ -23,7 +23,7 @@ Tu debes haber notado que en los últimos meses, el progreso ha sido especialmen
 * Un backend de Django para Toga, permitiendo que las aplicaciones de Toga se implementen como aplicaciones web;
 * Un backend de Winforms para Toga, permitiendo que las aplicaciones de Toga funcionen en Windows con un aspecto moderno;

-.. _Jambon Software: https://jambonsw.com
+.. _Jambon Software: https://www.jambonsw.com

 Desafortunadamente, mi contrato con Jambon está llegando a su fin - lo que significa que mis contribuciones a BeeWare volverán a ser lo que mi tiempo libre permite.

--- a/content/news/buzz/a-request-for-your-help/contents.lr
+++ b/content/news/buzz/a-request-for-your-help/contents.lr
@ -6,15 +6,15 @@ body:

 Around 4 years ago, I made the first commit to `Cricket`_ - the first tool that would eventually become part of the BeeWare suite. Since then, the BeeWare project has grown to encompass support for mobile platforms, two alternate Python implementations, and a cross platform widget set - as well as the developer tools that started the project originally.

-.. _Cricket: http://pybee.org/cricket
+.. _Cricket: https://pybee.org/project/projects/tools/cricket/

 For most of this time, BeeWare has been a volunteer effort. Initially, it was a solo project; however, over the last year in particular, the number of people who have contributed to BeeWare has grown rapidly. Over 300 people have now made contributions to the various BeeWare tools and libraries - due, at least in part, to the `Challenge Coins`_ we've been offering at sprints.

-.. _Challenge Coins: http://pybee.org/contributing/challenge-coins/
+.. _Challenge Coins: https://pybee.org/contributing/challenge-coins/

 Of particular note is the `team of 7 people`_ who have joined the project as apiarists, helping share the load of project maintainence. I can't thank these people enough - without their assistance, I wouldn't have made anywhere near as much progress over the last year.

-.. _team of 7 people: http://pybee.org/community/team/
+.. _team of 7 people: https://pybee.org/community/team/

 You may have noticed that over the last few months, progress has been especially rapid. This is because, for the last six months, BeeWare development has been partially funded by very accomodating employers at `Jambon Software`_. My contract with Jambon allowed me to spend significant periods of time being paid to work on BeeWare - and, not surprisingly, it was possible to make enormous progress as a result. The last 6 months has seen:

@ -23,7 +23,7 @@ You may have noticed that over the last few months, progress has been especially
 * A Django backend for Toga, enabling Toga apps to be deployed as web apps;
 * A Winforms backend for Toga, enabling Toga apps to run on Windows with a modern appearance;

-.. _Jambon Software: https://jambonsw.com
+.. _Jambon Software: https://www.jambonsw.com

 Unfortunately, my contract with Jambon is coming to a close - which means my contributions to BeeWare will go back to being what my spare time allows.

@ -35,7 +35,7 @@ So - this is an appeal to you - the Python community. If you are excited by the

 For just **US$10 a month** - you can `join the BeeWare project as a member`_, and help make this dream become a reality. If I can find 1000 people in the Python community who want these these tools and are willing to support their development financially, I can start working on BeeWare full time. Of course, this target is even easier if companies get involved and sponsor at higher tiers.

-.. _join the BeeWare project as a member: http://pybee.org/contributing/membership/
+.. _join the BeeWare project as a member: https://pybee.org/contributing/membership/

 If I can find *more* than 1000 people, then even more becomes possible. The obvious option would be to hire other experienced developers to assist with the work. The idea of having others to bounce ideas off during the development process is very appealing. However, we can also use this as an opportunity to do some social good.

--- a/content/news/buzz/come-sprint-with-us-at-pycon-us-2017/contents+es.lr
+++ b/content/news/buzz/come-sprint-with-us-at-pycon-us-2017/contents+es.lr
@ -18,7 +18,7 @@ body:

 `PyCon US 2017 <https://us.pycon.org/2017/>`__ se está llevando cabo en Portland, Oregon del 17 al 25 de mayo, y está destinado a ser otra increíble conferencia.

-Por segundo año consecutivo, el equipo `BeeWare <http://pybee.org>`__ estará en el sitio con un `stand en el salón de exhibiciones <https://twitter.com/PyBeeWare/status/737043373953978368>`__, junto con otros proyectos de Código Abierto del mundo Python.
+Por segundo año consecutivo, el equipo `BeeWare <https://pybee.org>`__ estará en el sitio con un `stand en el salón de exhibiciones <https://twitter.com/PyBeeWare/status/737043373953978368>`__, junto con otros proyectos de Código Abierto del mundo Python.

 Con este stand, tenemos dos entradas para la conferencia. Esto incluye:

--- a/content/news/buzz/come-sprint-with-us-at-pycon-us-2017/contents.lr
+++ b/content/news/buzz/come-sprint-with-us-at-pycon-us-2017/contents.lr
@ -21,7 +21,7 @@ away. Email contact@pybee.org and tell us why you want to bee there!*
 Oregon from May 17 - 25, and it's bound to be another amazing
 conference.

-For the second year in a row, the `BeeWare team <http://pybee.org>`__
+For the second year in a row, the `BeeWare team <https://pybee.org>`__
 will be on site with a `booth in the Exhibit
 Hall <https://twitter.com/PyBeeWare/status/737043373953978368>`__, along
 with other Open Source projects from the Python world.
@ -47,11 +47,11 @@ What do we want in return?

 Just a little bit of your time.

-The `Bee Team <http://pybee.org/community/team/>`__ will be helping to
+The `Bee Team <https://pybee.org/community/team/>`__ will be helping to
 staff our booth, but we'd also like to see (and give!) talks, so helping
 us out by running the booth would be lovely. (Plus, and I'm sure Russell
 would agree, just helping out on the booth earns you a
-`coin <http://pybee.org/contributing/challenge-coins/>`__)
+`coin <https://pybee.org/contributing/challenge-coins/>`__)

 Plus, we'd love for you to stick around for the famous coding Sprints.
 These are held in the four days after the event, while people are still
--- a/content/news/buzz/hello-website/contents+es.lr
+++ b/content/news/buzz/hello-website/contents+es.lr
@ -20,12 +20,12 @@ Esto también le da a la comunidad BeeWare una gran oportunidad de contribuir. S

 Esperamos que disfrutes del nuevo sitio; si tienes algún comentario, nos lo puedes hacer saber `con un ticket`_ o `en nuestro canal Gitter`_.

-.. _Lektor: http://www.getlektor.com
+.. _Lektor: https://www.getlektor.com
 .. _Armin Ronacher: http://lucumr.pocoo.org/
 .. _disponible en GitHub: https://github.com/pybee/pybee.github.io/tree/lektor
 .. _Modena de Desafío de BeeWare: /es/contribuir/monedas-de-desafio/
 .. _con un ticket: https://github.com/pybee/pybee.github.io/issues/
-.. _en nuestro canal Gitter: http://gitter.im/pybee/general
+.. _en nuestro canal Gitter: https://gitter.im/pybee/general
 ---
 twitter_handle: freakboy3742
 ---
--- a/content/news/buzz/hello-website/contents.lr
+++ b/content/news/buzz/hello-website/contents.lr
@ -20,12 +20,12 @@ This also gives you - the BeeWare community - a great opportunity to contribute.

 We hope you enjoy the new site; if you've got any feedback, let us know `with a ticket`_ or `in our Gitter channel`_.

-.. _Lektor: http://www.getlektor.com
+.. _Lektor: https://www.getlektor.com
 .. _Armin Ronacher: http://lucumr.pocoo.org/
 .. _available on GitHub: https://github.com/pybee/pybee.github.io/tree/lektor
 .. _BeeWare Challenge Coin: /contributing/challenge-coins/
 .. _with a ticket: https://github.com/pybee/pybee.github.io/issues/
-.. _in our Gitter channel: http://gitter.im/pybee/general
+.. _in our Gitter channel: https://gitter.im/pybee/general

 ---
 twitter_handle: freakboy3742
--- a/content/news/buzz/money-money-money/contents+es.lr
+++ b/content/news/buzz/money-money-money/contents+es.lr
@ -10,7 +10,7 @@ body:

 En PyCon AU 2015, y de nuevo en DjangoCon US 2015, di una charla titulada "Dinero, dinero, dinero: Escribiendo software, en un mundo de hombres ricos". La charla fue un resumen de los problemas relacionados con uno de los mayores problemas que veo frente a la comunidad de código abierto: cómo proporcionar los recursos que se necesitan para desarrollar y mantener el software del que nosotros, como comunidad, dependemos. Esto significa proporcionar mantenimiento y apoyo a proyectos establecidos, grandes y pequeños; sino que también proporciona un ecosistema donde las nuevas ideas pueden ser incubadas, desarrolladas y maduradas hasta que presenten alternativas atractivas o beneficios significativos sobre las ofertas de fuentes cerradas.

-Han pasado casi 18 meses desde que presenté esta charla, pero el problema persiste. No he estado solo al notar y llamar la atención sobre este asunto, tampoco. `Nadia Eghbal <https://twitter.com/nayafia>`_ fue encargada de redactar un libro para la Fundación Ford titulado `Caminos y puentes <http://www.fordfoundation.org/library/reports-and-studies/roads-and-bridges-the-unseen-labor-behind-our-digital-infrastructure>`__ resaltando las necesidades crónicas en infraestructura que subyacen a gran parte de la economía moderna. Eric Holscher (mantenedor de `Read the Docs <http://readthedocs.com>`_) `escribió sobre los problemas que tuvo para recaudar fondos <http://ericholscher.com/blog/2016/aug/31/funding-oss-marketing-money/>`_, a pesar de que el servicio que él ofrece corresponde a una parte ampliamente utilizada - posiblemente indispensable - del ecosistema Python.
+Han pasado casi 18 meses desde que presenté esta charla, pero el problema persiste. No he estado solo al notar y llamar la atención sobre este asunto, tampoco. `Nadia Eghbal <https://twitter.com/nayafia>`_ fue encargada de redactar un libro para la Fundación Ford titulado `Caminos y puentes <http://www.fordfoundation.org/library/reports-and-studies/roads-and-bridges-the-unseen-labor-behind-our-digital-infrastructure>`__ resaltando las necesidades crónicas en infraestructura que subyacen a gran parte de la economía moderna. Eric Holscher (mantenedor de `Read the Docs <https://readthedocs.com>`_) `escribió sobre los problemas que tuvo para recaudar fondos <http://ericholscher.com/blog/2016/aug/31/funding-oss-marketing-money/>`_, a pesar de que el servicio que él ofrece corresponde a una parte ampliamente utilizada - posiblemente indispensable - del ecosistema Python.

 Sin embargo, a pesar de esta atención, todavía no llega a estar tan cerca de la atención que debería tener. Y es una cuestión que es de gran importancia para mí, ya que el proyecto BeeWare está buscando formas de financiar el desarrollo necesario para pasar de una "interesante demostración técnica" a una "solución técnica convincente".

@ -309,7 +309,7 @@ Esta es una discusión que necesitamos tener como comunidad - y estoy ansioso po

 * `russell@keith-magee.com <mailto: russell@keith-magee.com>`_
 * `@freakboy3742 <https://twitter.com/freakboy3742>`_
-* `cecinestpasun.com <http://cecinestpasun.com>`_
+* `cecinestpasun.com <https://cecinestpasun.com>`_

 .. _PyPI: https://pypi.python.org/pypi
 ---
--- a/content/news/buzz/money-money-money/contents.lr
+++ b/content/news/buzz/money-money-money/contents.lr
@ -10,7 +10,7 @@ body:

 At PyCon AU 2015, and again at DjangoCon US 2015, I gave a talk entitled "Money Money Money: Writing software, in a rich (wo)man's world". The talk was a summary of the issues around one of the biggest problems that I see facing the open source community: how to provide the resources that are needed to develop and maintain the software that we, as a community depend upon. This means providing maintenance and support for established projects, large and small; but also providing an ecosystem where new ideas can be incubated, developed and matured until they present compelling alternatives or significant benefits over closed source offerings.

-It's been almost 18 months since I first presented this talk, but the issue persists. I haven't been alone in noticing and drawing attention to this issue, either. `Nadia Eghbal <https://twitter.com/nayafia>`_ was commissioned to write a white paper for the Ford Foundation entitled `Roads and Bridges <http://www.fordfoundation.org/library/reports-and-studies/roads-and-bridges-the-unseen-labor-behind-our-digital-infrastructure>`_ highlighting the chronic need for resources to support the basic infrastructure that underpins large parts of the modern economy. Eric Holscher (maintainer of `Read the Docs <http://readthedocs.com>`_) `blogged about the problems he's had raising funds <http://ericholscher.com/blog/2016/aug/31/funding-oss-marketing-money/>`_, despite the fact that the service he delivers is a widely used - arguably indispensible - part of the Python ecosystem.
+It's been almost 18 months since I first presented this talk, but the issue persists. I haven't been alone in noticing and drawing attention to this issue, either. `Nadia Eghbal <https://twitter.com/nayafia>`_ was commissioned to write a white paper for the Ford Foundation entitled `Roads and Bridges <http://www.fordfoundation.org/library/reports-and-studies/roads-and-bridges-the-unseen-labor-behind-our-digital-infrastructure>`_ highlighting the chronic need for resources to support the basic infrastructure that underpins large parts of the modern economy. Eric Holscher (maintainer of `Read the Docs <https://readthedocs.com>`_) `blogged about the problems he's had raising funds <http://ericholscher.com/blog/2016/aug/31/funding-oss-marketing-money/>`_, despite the fact that the service he delivers is a widely used - arguably indispensible - part of the Python ecosystem.

 However, despite this attention, it *still* doesn't get anywhere near as much attention as it should. And it's an issue that is of pressing importance to me, as the BeeWare project is looking for ways to fund the development needed to take us from "interesting technical demo" to "compelling technical solution".

@ -308,7 +308,7 @@ This is a discussion we need to have as a community - and I'm eager to have that

 * `russell@keith-magee.com <mailto:russell@keith-magee.com>`_
 * `@freakboy3742 <https://twitter.com/freakboy3742>`_
-* `cecinestpasun.com <http://cecinestpasun.com>`_
+* `cecinestpasun.com <https://cecinestpasun.com>`_

 .. _PyPI: https://pypi.python.org/pypi

--- a/content/news/events/pycon-us-2016-sprints/contents.lr
+++ b/content/news/events/pycon-us-2016-sprints/contents.lr
@ -6,6 +6,6 @@ event_type: sprint
 ---
 speaker: Philip James, Katie McLaughlin, Russell Keith-Magee
 ---
-url: https://2016.pycon.us
+url: https://us.pycon.org/2016/
 ---
-upcoming: no
+upcoming: no
--- a/content/news/events/pycon-us-2016/contents.lr
+++ b/content/news/events/pycon-us-2016/contents.lr
@ -8,6 +8,6 @@ speaker: Russell Keith-Magee
 ---
 talk_title: A Tale of Two Cellphones
 ---
-url: https://2016.pycon.us
+url: https://us.pycon.org/2016/
 ---
 upcoming: no
--- a/content/news/events/pyohio-2016-sprints/contents.lr
+++ b/content/news/events/pyohio-2016-sprints/contents.lr
@ -4,7 +4,7 @@ date: 2016-08-01
 ---
 event_type: sprint
 ---
-url: http://pyohio.org/sprints/
+url: https://pyohio.org/sprints/
 ---
 speaker: Russell Keith-Magee
 ---
--- a/content/news/events/pyohio-2016/contents+es.lr
+++ b/content/news/events/pyohio-2016/contents+es.lr
@ -6,8 +6,10 @@ event_type: talk
 ---
 speaker: Russell Keith-Magee
 ---
-url: http://pyohio.org/schedule/presentation/249/
+url: https://2016.pyohio.org/schedule/
 ---
 talk_title: Serpientes en el navegador
 ---
 upcoming: no
+---
+description: El video se puede ver en `este enlace <https://www.youtube.com/watch?v=9W2sFRrNJ9A>`__
--- a/content/news/events/pyohio-2016/contents.lr
+++ b/content/news/events/pyohio-2016/contents.lr
@ -6,8 +6,10 @@ event_type: talk
 ---
 speaker: Russell Keith-Magee
 ---
-url: http://pyohio.org/schedule/presentation/249/
+url: https://2016.pyohio.org/schedule/
 ---
 talk_title: Snakes in a Browser
 ---
 upcoming: no
+---
+description: The video is available on `this link <https://www.youtube.com/watch?v=9W2sFRrNJ9A>`__
--- a/content/project/overview/contents+zh.lr
+++ b/content/project/overview/contents+zh.lr
@ -21,9 +21,9 @@ We're not just about software, though. We also aim to be a project with a social
 Where to from here?
 ===================

-If you'd like to know more about the history of BeeWare, `start here <../about/>`__.
+If you'd like to know more about the history of BeeWare,  `start here </zh_TW/project/about/>`__.

-If you'd like to take BeeWare for a test drive, `take a look at the the various ways BeeWare tools can be used <../using/>`__.
+If you'd like to take BeeWare for a test drive, `take a look at the the various ways BeeWare tools can be used </zh_TW/project/using/>`__.

 If you'd like to keep up to date with what we're doing, follow `@PyBeeWare <https://twitter.com/PyBeeWare/>`__ on Twitter. If you'd like to receive updates, hints, tips and announcements about the BeeWare project, `sign up for the Beeware Enthusiasts mailing list  </community/keep-informed/>`__.

@ -33,10 +33,10 @@ gutter:
 Next steps
 ==========

-* The `History of the BeeWare project  <../about/>`__
-* `BeeWare test drive <../using/>`__
+* The `History of the BeeWare project  </zh_TW/project/about/>`__
+* `BeeWare test drive </zh_TW/project/using/>`__
 * `@PyBeeWare on Twitter <https://twitter.com/PyBeeWare/>`__
-* The `Beeware Enthusiasts mailing list  </community/keep-informed/>`__
+* The `Beeware Enthusiasts mailing list  </zh_TW/community/keep-informed/>`__

 ---
 incomplete: no
--- a/content/project/overview/contents.lr
+++ b/content/project/overview/contents.lr
@ -21,9 +21,9 @@ We're not just about software, though. We also aim to be a project with a social
 Where to from here?
 ===================

-If you'd like to know more about the history of BeeWare, `start here <../about/>`__.
+If you'd like to know more about the history of BeeWare, `start here </project/about/>`__.

-If you'd like to take BeeWare for a test drive, `take a look at the the various ways BeeWare tools can be used <../using/>`__.
+If you'd like to take BeeWare for a test drive, `take a look at the the various ways BeeWare tools can be used </project/using/>`__.

 If you'd like to keep up to date with what we're doing, follow `@PyBeeWare <https://twitter.com/PyBeeWare/>`__ on Twitter. If you'd like to receive updates, hints, tips and announcements about the BeeWare project, `sign up for the Beeware Enthusiasts mailing list  </community/keep-informed/>`__.

@ -33,8 +33,8 @@ gutter:
 Next steps
 ==========

-* The `History of the BeeWare project  <../about/>`__
-* `BeeWare test drive <../using/>`__
+* The `History of the BeeWare project  </project/about/>`__
+* `BeeWare test drive </project/using/>`__
 * `@PyBeeWare on Twitter <https://twitter.com/PyBeeWare/>`__
 * The `Beeware Enthusiasts mailing list  </community/keep-informed/>`__

--- a/content/project/projects/applications/podium/contents+es.lr
+++ b/content/project/projects/applications/podium/contents+es.lr
@ -19,3 +19,7 @@ pun:
 customlogo: yes
 ---
 _slug: 
+---
+github_repo: pybee/podium
+---
+image: podium.png
--- a/content/project/projects/applications/podium/contents.lr
+++ b/content/project/projects/applications/podium/contents.lr
@ -17,3 +17,7 @@ help_required:
 pun: 
 ---
 customlogo: yes
+---
+image: podium.png
+---
+github_repo: pybee/podium
--- a/content/project/projects/attic/cassowary/contents+es.lr
+++ b/content/project/projects/attic/cassowary/contents+es.lr
@ -15,7 +15,7 @@ description:
 Una implementación en Python del `algoritmo de resolución de restricciones de Cassowary`_.
 El algoritmo de Cassowary forma el núcleo del mecanismo de disposición visual de OSX y iOS.

-.. _algoritmo de resolución de restricciones de Cassowary: http://www.cs.washington.edu/research/constraints/cassowary/
+.. _algoritmo de resolución de restricciones de Cassowary: http://constraints.cs.washington.edu/cassowary/

 Este proyecto ya no está en uso. Originalmente fue desarrollado para su uso en Toga; sin embargo, Toga ahora utiliza un mecanismo de disposición visual basado en CSS, implementado a través de `Colosseum </es/proyecto/proyectos/librerias/colosseum/>`__.
 ---
@ -26,3 +26,7 @@ rtfd_name: cassowary
 attic: yes
 ---
 _slug: cassowary
+---
+github_repo: pybee/cassowary
+---
+image: cassowary.png
--- a/content/project/projects/attic/cassowary/contents.lr
+++ b/content/project/projects/attic/cassowary/contents.lr
@ -16,12 +16,16 @@ A pure Python implementation of the `Cassowary constraint-solving algorithm`_.
 Cassowary is the algorithm that forms the core of the OS X and iOS visual
 layout mechanism.

-.. _Cassowary constraint-solving algorithm: http://www.cs.washington.edu/research/constraints/cassowary/
+.. _Cassowary constraint-solving algorithm: http://constraints.cs.washington.edu/cassowary/

-This project is no longer in use. It was originally developed for use in Toga; however, Toga now uses CSS-based layout, implemented in `Colosseum <../../libraries/colosseum>`__.
+This project is no longer in use. It was originally developed for use in Toga; however, Toga now uses CSS-based layout, implemented in `Colosseum </project/projects/libraries/colosseum>`__.
 ---
 help_required: 
 ---
 rtfd_name: cassowary
 ---
 attic: yes
+---
+github_repo: pybee/cassowary
+---
+image: cassowary.png
--- a/content/project/projects/attic/cookiecutter-project/contents.lr
+++ b/content/project/projects/attic/cookiecutter-project/contents.lr
@ -13,3 +13,5 @@ short_description: A cookiecutter template for projects
 description: This was a cookiecutter template for setting up new pybee projects. It is no longer used.
 ---
 attic: yes
+---
+github_repo: pybee/cookiecutter-project
--- a/content/project/projects/attic/cookiecutter-website/contents+es.lr
+++ b/content/project/projects/attic/cookiecutter-website/contents+es.lr
@ -15,3 +15,5 @@ short_description: Una plantilla cookiecutter para sitios web
 attic: yes
 ---
 _slug: 
+---
+github_repo: pybee/cookiecutter-website
--- a/Show more
+++ b/Show more