Descrição

Eu fui responsável por traduzir o arquivo tailwind-css.md e recentemente, descobri que esse arquivo na versão original foi adicionado mais uma "Option" , no caso a Option #3: SCSS. Quando eu traduzi, só tinha até a Option #2: CSS-in-JS.

Vocês me permitem adicionar a tradução da Option #3: SCSS no tailwind-css.md?

Link com a Option #3: SCSS
https://github.com/gatsbyjs/gatsby/blob/master/docs/docs/tailwind-css.md

Boa tarde pessoal, o que acham de adicionar o link dos arquivos que ainda não foram distribuídos/corrigidos na listagem das batches pro pessoal conseguir identificar mais facilmente?
Por exemplo:

• headless-cms.md (@lucas-mdiniz) ✔️ #87
• creating-and-modifying-pages.md (@RodrigoEC) 🏃‍♂️
• schema-sift.md

Se quiser posso fazer esse mapeamento e mandar pra vocês.

We’re looking for a Senior Frontend Engineer to join our stellar team. Our positions are 100% remote, working with teams mainly based in the United States.

What you’ll do

• Work in a multidisciplinary team combining the art of design with the art of programming;
• Work closely with other teams to help decide which features to build and how to build them;
• Ensure the design translates the values ​​and needs of the company;
• Deliver clean code.

Local

You get to work 100% remote in teams mainly based in the United States, from Brazil.

Requisitos

In order to succeed in this position, you will need

• Advanced/fluent English skills – Excellent written and verbal communication skills;
• JavaScript with strong ReactJS experience – TypeScript is a plus;
• Understands common front-end build tools like npm, yarn, webpack, etc;
• Strong HTML/CSS experience, preferably with a media company or publishing background (i.e. high attention to detail);
• Experience with GatsbyJS or other static site-generators;
• Previous experience with WordPress – PHP or Ruby on Rails development experience are a plus;
• High degree of attention to detail and methodical when solving problems;
• Self-motivated with a high-sense of urgency around work;
• Strong ownership and accountability;
• Comfortable working in a Kanban/Agile environment;
• Used to task management tools like Jira.

Nossa empresa

We at Ubiminds are a talent powerhouse, sourcing, recruiting and hiring sought-after tech professionals, from mid-level to leadership positions. Find out firsthand what it's like to work remotely for American SaaS companies from Brazil by listening to what customers and employees have to say: https://www.youtube.com/watch?v=GxfqmIPKxN8.

Como se candidatar

Apply at https://ubiminds.com/sr-frontend-engineer/

Labels

🏢 Remoto
👴 Sênior
⚖️ PJ

Batch 3

Revisores Oficiais

• @jessescn
• @iaurg
• @henry-ns
• @thayannevls

Para os novos tradutores

Siga os passos descritos no nosso CONTRIBUTING.md. Daremos um limite de 2 SEMANAS para que cada tradução seja finalizada, no intuito de manter a tradução sempre dinâmica.
Escolha apenas uma página para tradução por vez. Ao finalizar você poderá escolher a próxima.

Páginas

Aqui estão listadas as páginas que foram traduzidas, estão em processo de tradução ou estão disponíveis para serem traduzidas da pasta docs/. Você pode conferir os estados delas verificando as suas labels.

Labels

• 👀 - Sob Revisão
• 🏃‍♂️ - Em Progresso
• ✔️ - Feita!

As labels 👀 e ✔️ devem ser seguidas do número da PR aberta referente a tradução

Paginas docs/

• headless-cms.md (@lucas-mdiniz) ✔️ #87
• creating-a-transformer-plugin.md (@peaonunes) ✔️ #84
• path-prefix.md (@peaonunes) ✔️ #65
• building-an-e-commerce-site.md (@emilioheinz) ✔️ #83
• using-gatsby-professionally.md (@lcnogueira) ✔️ #64
• configuring-ca-certificates.md (@emilioheinz) ✔️ #108
• testing.md (@junagao) ✔️ #68
• gatsby-on-linux.md (@luchiago) ✔️ #71
• add-a-manifest-file.md (@tamirisapbonicenha) ✔️ #91
• tailwind-css.md (@tavareshenrique) ✔️ #78
• query-extraction.md (@istumpf) ✔️ #114
• build-caching.md (@luchiago) ✔️ #97
• using-fragments.md (@fbandeirac) ✔️ #136
• creating-and-modifying-pages.md (@RodrigoEC) ✔️ #174
• graphql.md (@jefferson2z) ✔️ #67
• adding-forms.md (@tavareshenrique) ✔️ #93
• node-creation.md (@maiconrs95) 🏃‍♂️
• api-files-gatsby-config.md (@peaonunes) ✔️ #129
• routing.md (@iaurg) ✔️ #94
• gatsby-for-freelancers.md (@rafaeelaudibert) ✔️ #150
• debugging-html-builds.md (@fbandeirac) ✔️ #193
• bulma.md (@renatamarques97) ✔️ #100
• why-gatsby-uses-graphql.md (@mauriciomutte) ✔️ #134
• testing-css-in-js.md (@Mex978) ✔️ #147
• porting-to-gatsby.md (@abnersajr) ✔️ #106
• using-gatsby-without-graphql.md (@thaisquintana) 🏃‍♂️
• porting-from-create-react-app-to-gatsby.md (@brunagil) 🏃‍♂️
• sourcing-from-ghost.md (@sosolidkk) ✔️ #139
• sourcing-from-graphcms.md (@luizeboli) ✔️ #277
• linking-between-pages.md (@abnersajr) ✔️ #103
• static-folder.md (@luizcieslak) ✔️ #128
• building-a-portfolio.md (@vinifarias) ✔️ #80
• what-you-dont-need-plugins-for.md (@luchiago) ✔️ #140
• conceptual-guide.md (@abnersajr) ✔️ #102
• deploying-to-render.md (@netochaves) ✔️ #153
• sourcing-from-drupal.md (@rafaeelaudibert) ✔️ #165
• webpack-and-ssr.md (@AntonioLeonan) ✔️ #208
• adding-page-transitions.md (@junagao) ✔️ #85
• static-query.md (@thiagorowof) ✔️ #184
• using-gatsby-image.md (@AleBL) ✔️ #169
• creating-a-sitemap.md (@elainemattos) ✔️ #137
• localization-i18n.md (@renatamarques97) ✔️ #99
• winning-over-developers.md (@lcnogueira) ✔️ #196
• winning-over-executives.md (@Mex978) ✔️ #159
• security-in-gatsby.md (@thiagorowof) ✔️ #144
• schema-sift.md (@felipefbs) ✔️ #233
• importing-assets-into-files.md (@gabrielbadao) 🏃‍♂️
• plugins.md (@furlanf) ✔️ #116
• thinking-in-gatsby.md (@vinifraga) ✔️ #178
• babel.md (@junagao) ✔️ #66
• loading-plugins-from-your-local-plugins-folder.md (@AntonioLeonan) ✔️ #218
• telemetry.md (@AntonioLeonan) ✔️ #158
• glamor.md (@abnersajr) ✔️ #105
• gatsby-lifecycle-apis.md (@Lucaas-Eduardo) 👀 #219
• sourcing-from-sanity.md (@zambo) 👀 #264
• adding-a-list-of-markdown-blog-posts.md (@AleBL) ✔️ #216
• overview.md (@Nerd0000) ✔️ #122
• upgrading-node-js.md (@thiagorowof) ✔️ #187
• awesome-gatsby-resources.md (@thiagorowof) ✔️ #186
• building-a-blog.md (@vinifraga) ✔️ #207
• global-css.md (@vinipbk) ✔️ #164
• sourcing-from-databases.md (@AntonioLeonan) ✔️ #227
• debugging.md (@vinifraga) ✔️ #170
• what-is-a-plugin.md (@CarlosEduLima) ✔️ #143
• gatsby-internals-terminology.md (@zambo) 🏃‍♂️
• remark-plugin-tutorial.md (@thisisernesto) ✔️ #271
• custom-html.md (@Quemia) ✔️ #133
• deploying-to-netlify.md (@sosolidkk) ✔️ #163
• sourcing-from-agilitycms.md (@gabsoares11) 👀 #290
• asset-prefix.md 🏃🏻‍♂️ (@fillipeags)
• client-only-routes-and-user-authentication.md
• gatsby-image.md (@jefferson2z)✔️#212
• api-files.md (@vinifarias) ✔️ #79
• scaling-issues.md (@matheusoak) 🏃‍♂️
• gatsby-vendor-partnership.md
• building-apps-with-gatsby.md
• faster-recruiting.md (@abnersajr) ✔️ #110
• performance-tracing.md
• interactive-pages.md (@vinifraga) ✔️ #206
• creating-a-source-plugin.md
• sourcing-from-contentstack.md
• adding-search.md (@sosolidkk) ✔️ #149
• migrating-from-v0-to-v1.md
• lower-bids-more-profit.md
• sourcing-from-contentful.md (@adeonir) 🏃‍♂️
• files-gatsby-looks-for-in-a-plugin.md
• making-your-site-accessible.md (@junagao) ✔️ #181
• sourcing-from-private-apis.md
• gatsby-config.md (@Wil-g2) ✔️ #182
• images-and-files.md (@TCsTheMechanic) ✔️ #203
• starters.md (@pellizzetti) ✔️ #130
• caching.md (@LeuAlmeida) ✔️ #202
• working-with-images-in-markdown.md (@Lucas-Dalamarta) ✔️ #282
• client-data-fetching.md
• winning-over-marketers.md
• add-404-page.md (@ArthurFerrao) ✔️ #63
• building-an-image-heavy-site.md
• preoptimizing-images.md (@ LeuAlmeida) 🏃‍♂️
• adding-comments.md (@Alessandro265) ✔️ #123
• deploying-to-heroku.md (@peaonunes) ✔️ #221
• debugging-the-build-process.md
• winning-over-engineering-leaders.md (@italohdc) 🏃‍♂️
• sass.md (@renatamarques97) ✔️ #115
• creating-a-local-plugin.md 🏃🏻‍♂️ (@aintluks)
• v2-release-notes.md (@AntonioLeonan) ✔️
• audit-with-lighthouse.md (@araujogui) ✔️ #284
• testing-components-with-graphql.md
• using-a-plugin-in-your-site.md (@adeonir) ✔️ #215
• how-gatsby-boosts-career.md (@tavareshenrique) ✔️ #166
• sourcing-from-kentico-cloudhea.md
• eslint.md (@abnersajr) ✔️ #107
• schema-generation.md (@Mex978) ✔️ #190
• sourcing-from-buttercms.md
• debugging-async-lifecycles.md
• visual-testing-with-storybook.md
• typography-js.md (@junagao) ✔️ #154
• add-page-metadata.md (@ArthurFerrao) ✔️ #72
• gatsby-in-the-enterprise.md
• sourcing-from-hosted-services.md
• deploying-to-gitlab-pages.md (@thayannevls) ✔️ #232
• how-plugins-apis-are-run.md 🏃🏻‍♂️ (@AngeloBonini)
• third-party-graphql.md
• gatsby-link.md (@atarrisse) ✔️ #286
• gatsby-for-agencies.md 🏃🏻‍♂️ (@mauriciomutte)
• testing-react-components.md (@junagao) ✔️ #74
• babel-plugin-macros.md (@pklepa) ✔️ #281
• adding-website-functionality.md
• data-storage-redux.md
• graphql-reference.md
• query-behind-the-scenes.md
• local-https.md (@OfficialMarinho) ✔️ #274
• sourcing-content-from-json-or-yaml.md
• first-professional-project.md (@lcnogueira) ✔️ #98
• setting-up-gatsby-without-gatsby-new.md
• resource-handling-and-service-workers.md
• debugging-replace-renderer-api.md
• optimizing-site-performance-with-guessjs.md
• graphql-concepts.md (@DouglasMV) ✔️ #96
• sanitize-your-stack.md (@sosolidkk) ✔️ #195
• creating-global-styles.md
• answering-it-security.md (@mauriciomutte) ✔️ #161
• how-to-add-a-list-of-markdown-blog-posts.md
• cheat-sheet.md (@renatamarques97) ✔️ #119
• page-creation.md (@tavareshenrique) ✔️ #127
• building-a-contact-form.md
• using-graphql-playground.md (@mauriciomutte) 👀 #175
• production-app.md
• add-a-service-worker.md (@pklepa ) 🏃
• gatsby-agency-partnership.md
• guides.md (@Nerd0000) ✔️ #104
• performance.md (@pellizzetti) ✔️ #168
• going-gatsby-only.md
• graphql-api.md (@vyk1) ✔️ #288
• adding-pagination.md (@junagao) 🏃‍♂️
• write-pages.md (@drd-2rcl) ✔️ #228
• creating-a-starter.md (@OfficialMarinho) 🏃‍♂️
• gatsby-internals.md
• linking-and-prefetching-with-gatsby.md
• adding-analytics.md (@MiguelMachado-dev) ✔️ #117
• preparing-for-site-launch.md (@araujogui ) ✔️ #292
• emotion.md (@luchiago) ✔️ #113
• building-a-site-with-asynchronous-data.md
• adding-search-with-elasticlunr.md (@vinifraga) ✔️ #220
• adding-tags-and-categories-to-blog-posts.md
• api-proxy.md (@sosolidkk ) 🏃
• schema-input-gql.md
• themes.md (@furlanf) ✔️ #162
• seo.md (@Wil-g2) ✔️ #135
• sourcing-from-prismic.md
• theme-api.md
• adding-page-transitions-with-plugin-transition-link.md
• running-queries-with-graphiql.md
• reach-router-and-gatsby.md
• sourcing-from-netlify-cms.md (@Lucas-Dalamarta ) 🏃
• centralizing-your-sites-navigation.md
• deploying-to-surge.md
• gatsby-repl.md (@pellizzetti) ✔️ #111
• deploying-to-aerobatic.md
• migrating-from-v1-to-v2.md
• working-with-video.md
• maintaining-a-plugin.md
• preparing-your-environment.md (@junagao) ✔️ #160
• how-code-splitting-works.md
• adding-search-with-algolia.md
• progressive-web-app.md (@benyAlves) ✔️ #291
• add-seo-component.md (@jpedroschmitz) ✔️ #118
• add-custom-webpack-config.md
• browser-support.md (@gabrielferreiraa) ✔️ #61
• preparing-for-deployment.md (@gabrielferreiraa) ✔️ #92
• coming-from-react-to-gatsby.md (@gabrielferreiraa) ✔️ #132
• add-offline-support-with-a-service-worker.md
• html-generation.md
• debugging-cache-issues.md (@7glaucio) ✔️ #176
• overview-of-the-gatsby-build-process.md
• how-gatsby-works-with-github-pages.md (@adeonir) ✔️ #229
• using-client-side-only-packages.md
• winning-over-stakeholders.md (@lcnogueira) ✔️ #124
• node-interface.md (@henry-ns) ✔️ #230
• styled-components.md (@junagao) ✔️ #59
• convincing-others.md (@lcnogueira) ✔️ #86
• page-query.md
• winning-over-clients.md (@sosolidkk) ✔️ #185
• use-static-query.md
• releases-and-migration.md (@vinifraga) ✔️ #179
• partnering-with-gatsby.md
• prpl-pattern.md
• v1-release-notes.md
• api-reference.md (@vinifraga) ✔️ #177
• programmatically-create-pages-from-data.md
• api-files-gatsby-node.md (@ArthurFerrao) ✔️ #82
• internal-data-bridge.md
• schema-customization.md (@DouglasMV) ✔️ #125
• post-css.md (@VictorKunzler) ✔️ #167
• theme-ui.md (@luizeboli) ✔️ #273
• rendering-sidebar-navigation-dynamically.md
• pixabay-source-plugin-tutorial.md
• location-data-from-props.md
• adding-search-with-js-search.md (@alessandraburckhalter) 👀 #285
• api-specification.md
• api-files-gatsby-ssr.md
• styling.md (@vinifarias ) ✔️ #58
• naming-a-plugin.md (@TCsTheMechanic) ✔️ #70
• upgrade-gatsby-and-dependencies.md
• query-execution.md
• sourcing-from-prose.md (@vinifraga) ✔️ #204
• sourcing-from-the-filesystem.md
• building-with-components.md
• schema-gql-type.md
• gatsby-on-windows.md (@renatamarques97) ✔️ #141
• gatsby-for-companies.md
• deploying-to-aws-amplify.md (@sosolidkk) ✔️ #268
• gatsby-project-structure.md (@vinipbk) ✔️ #180
• end-to-end-testing.md (@jpedroschmitz) 🏃‍♂️
• deploying-to-zeit-now.md (@gcmatheusj) 🏃‍♂️
• css-in-js.md (@lucas-mdiniz) ✔️ #131
• layout-components.md (@RodrigoEC) ✔️ #269
• page-node-dependencies.mdgraphql.md
• working-with-gifs.md (@mauriciomutte) ✔️ #156
• node-tracking.md 🏃🏻‍♂️ (@alessandraburckhalter)
• building-a-site-with-authentication.md (@peaonunes) ✔️ #270
• component-libraries.md (@furlanf) 👀 #198
• sharing-components-across-websites.md (@AleBL) ✔️ #194
• sourcing-from-wordpress.md
• api-files-gatsby-browser.md
• static-vs-normal-queries.md
• environment-variables.md
• multi-core-builds.md
• basic-hardware-software-requirements.md (@vinifraga) ✔️ #226
• creating-slugs-for-pages.md (@vinifarias) ✔️ #88
• different-organization-types.md (@pklepa) ✔️ #266
• css-libraries-and-frameworks.md (@notstoe) ✔️ #272
• schema-connections.md
• content-and-data.md (@abnersajr) ✔️ #75
• css-modules.md (@luchiago) ✔️ #81
• making-components-discoverable.md (@tavareshenrique) ✔️ #152
• creating-prefixed-404-pages-for-different-languages.md (@rosariopfernandes) ✔️ #287
• deploying-and-hosting.md (@abnersajr) ✔️ #109
• creating-plugins.md (@ArthurFerrao) ✔️ #76
• gatsby-core-philosophy.md (@DouglasMV) ✔️ #90
• adding-an-rss-feed.md (@MiguelMachado-dev) 🏃‍♂️
• how-shadowing-works.md
• adding-markdown-pages.md (@vinipbk) 🏃‍♂️
• best-practices-for-orgs.md (@vinifarias) ✔️ #69
• working-with-images.md (@CarlosEduLima) ✔️ #157
• deploying-to-s3-cloudfront.md (@RodrigoEC) ✔️ #289
• customization.md (@Nerd0000) ✔️ #95
• importing-media-content.md (@luchiago) ✔️ #120
• unit-testing.md (@Lucaas-Eduardo) ✔️ #148

Paginas docs/mdx

• customizing-components.md (@AntonioHamilton) 👀 #197
• index.md (@mrcsvg) 🏃‍♂️
• getting-started.md (@johanguse) ✔️ #138
• markdown-syntax.md (@lancaluis) ✔️ #275
• plugins.md (@arthurbarroso) ✔️ #265
• programmatically-creating-pages.md
• writing-pages.md

Paginas docs/glossary

• graphql.md (@lancaluis) ✔️ #276
• webpack.md (@vinicius98s) ✔️ #267
• node.md (@sosolidkk) ✔️ #222
• react.md (@netochaves) ✔️ #224

Paginas docs/recipes

• deploying-your-site.md (@luizeboli) ✔️ #279
• pages-layouts.md (@luizeboli) ✔️ #280
• querying-data.md (@atarrisse) 🏃
• sourcing-data.md
• styling-css.md 🏃🏻‍♂️ (@ThWember)
• transforming-data.md
• working-with-images.md
• working-with-starters.md (@lancaluis) ✔️ #278
• working-with-themes.md (@RodrigoEC ) 🏃

Paginas docs/themes

• building-themes.md (@lancaluis) 🏃‍♂️
• conventions.md
• converting-a-starter.md
• getting-started.md (@AleBL) ✔️ #223
• shadowing.md
• theme-composition.md (@7glaucio) ✔️ #214
• using-a-gatsby-theme.md (@gabrigode) ✔️ #146
• using-multiple-gatsby-themes.md (@maykonmenezes) ✔️ #200
• what-are-gatsby-themes.md (@7glaucio) ✔️ #225
• accessibility-statement.md (@PatrickWalter387) ✔️ #191

Eu tava lendo aqui:

https://github.com/gatsbyjs/gatsby-pt-BR/blob/master/CONTRIBUTING.md

E no Glossário tem o link para uma planilha do Google:

https://docs.google.com/spreadsheets/d/1TLztI-jrPslCt0fgk4B9tGnhhS_7JQZJfMql1ePsIZo/edit

Quando abro aparece esse aviso:

"O arquivo esta na lixeira do proprietário"

Batch 2

Revisores Oficiais

• @jessescn
• @rafaeelaudibert
• @dennissiq
• @jay-jlm
• @iaurg
• @mjr
• @abnersajr

Para os novos tradutores

Siga os passos descritos no nosso CONTRIBUTING.md. Daremos um limite de 2 SEMANAS para que cada tradução seja finalizada, no intuito de manter a tradução sempre dinâmica.

Páginas

Aqui estão listadas as páginas que foram traduzidas, estão em processo de tradução ou estão disponíveis para serem traduzidas da pasta contributing/. Você pode conferir os estados delas verificando as suas labels.

Labels

• 🏃‍♂️ - Em Progresso
• 👀 - Sob Revisão
• ✔️ - Feita!

Paginas contributing/

• blog-and-website-contributions (@abnersajr) ✔️ #13
• code-contributions (@jessescn) ✔️ #26
• community-contributions (@vsmjr) ✔️ #142
• community (@mauriciomutte) ✔️ #25
• contributor-swag (@rafaeelaudibert) ✔️ #18
• docs-contributions (@abnersajr) ✔️ #22
• gatsby-governance-model (@peaonunes) ✔️ #19
• how-to-contribute (@dennissiq) ✔️ #16
• how-to-file-an-issue (@emilioheinz) ✔️ #15
• how-to-label-an-issue (@thaisquintana) ✔️ #41
• how-to-make-an-reproducible-test-case (@peaonunes) ✔️ #30
• how-to-open-a-pull-request (@guilhermepiovesan) ✔️ #29
• how-to-pitch-gatsby (@peaonunes ) ✔️ #209
• how-to-run-a-gatsby-workshop (@thiagorowof) ✔️ #42
• how-to-write-a-stub (@iaurg) ✔️ #62
• managing-pull-requests (@drd-2rcl) ✔️ #54
• organize-a-gatsby-event (@vsmjr) ✔️ #52
• pair-programming (@abnersajr) ✔️ #24
• rfc-process (@helloncanella) ✔️ #60
• setting-up-your-local-dev-environment (@fmoliveira) ✔️ #44
• site-showcase-submissions (@gutofoletto) ✔️ #53
• submit-to-creator-showcase (@luizcieslak) ✔️ #33
• submit-to-plugin-library (@Rahmon) ✔️ #45
• submit-to-starter-library (@dennissiq) ✔️ #37
• triaging-github-issues (@vinifarias) ✔️ #32
• using-an-online-dev-environment (@emilioheinz) ✔️ #39
• where-to-participate (@vsmjr) ✔️ #199
• why-contribute-to-gatsby (@lucas-mdiniz) ✔️ #51

Com a resolução de conflitos vindo do repositório principal, alguns arquivos necessitam ter partes re-traduzidas. Com o intuito de acelerar o processo, eu estou abrindo essa issue para este propósito.

Fique livre para requisitar de 1-5 arquivos de uma vez (já que muitos possuem apenas poucas partes para traduzir.

Caso queira ajudar, é só comentar na issue qual(s) arquivo(s) você tem interesse em traduzir

Obs: Revisores podem editar essa issue direto.

tutorial/

• part-zero/index.md ✔️ (@iaurg) #240
• part-one/index.md ✔️ (@iaurg) #240
• part-eight/index.md ✔️ (@iaurg) #240

contributing/

• blog-and-website-contributions.md ✔️ (@luizeboli) #250
• code-contributions.md ✔️ (@henry-ns) #245
• docs-contributions.md ✔️ (@borelbruno) #257
• how-to-open-a-pull-request.md ✔️ (@iaurg) #262
• managing-pull-requests.md ✔️ (@iaurg) #262
• organize-a-gatsby-event.md ✔️ (@henry-ns) #247
• pair-programming.md ✔️ (@iaurg) #262
• setting-up-your-local-dev-environment.md ✔️ (@afucher) #256

Docs/

• themes/using-a-gatsby-theme.md ✔️ (@lancaluis) #258
• building-an-e-commerce-site.md ✔️ (@MatheusGoncalvs) #255
• gatsby-cli.md ✔️ (@afucher) #249
• gatsby-on-linux.md ✔️ (@felipefbs) #238
• gatsby-on-windows.md ✔️ (@felipefbs) #239
• glossary.md ✔️ (@felipefbs) #253
• making-your-site-accessible.md ✔️ (@MatheusGoncalvs) #263
• plugins.md ✔️ (@JuanVieiraPrado) #246
• porting-to-gatsby.md ✔️ (@luizeboli) #261
• recipes.md ✔️ (@IsaqueIgor) #242
• routing.md ✔️ (@luizeboli) #251
• static-folder.md ✔️ (@felipefbs) #254
• styled-components.md ✔️ (@henry-ns) #236
• tailwind-css.md ✔️ (@henry-ns) #236
• what-is-a-plugin.md ✔️ (@henry-ns) #237
• what-you-dont-need-plugins-for.md ✔️ (@henry-ns) #237
• winning-over-clients.md ✔️ (@IsaqueIgor) #242

Alguns dos arquivos da documentação possuem links para imagens, porém as mesmas não foram importadas para esse repositório. Seria interessante verificar nos docs já prontos (ingles, espanho, etc) se as imagens estão disponíveis, e atualizar o repositório com essas imagens.

Arquivos com imagens com links quebrados (extremely WIP, quem encontrar mais, avisar nos comentários para que possamos editar esse comentário top-level):

• /contributing/contributor-swag.md

EDIT:
No repositório em espanhol, o link para as imagens não estão quebrados. As imagens podem ser encontrados nos seguintes caminhos:

• docs/images
• contributing/images
• tutorial/images

--------------------- ! UPDATE IMPORTANTE ! ------------------

Todos os arquivos já foram designados, futuramente abriremos novos para tradução!

Maintainers: NUNCA mergem uma PR com somente uma aprovação!

Revisores Oficiais

• @jessescn
• @rafaeelaudibert
• @dennissiq
• @jay-jlm
• @iaurg
• @mjr
• @abnersajr

-----------------------------------------------------------------

Para os novos tradutores

Siga os passos descritos no nosso CONTRIBUTING.md. Daremos um limite de 2 SEMANAS para que cada tradução seja finalizada, no intuito de manter a tradução sempre dinâmica.

Labels

• [] 🏃‍♂️ - Em Progresso
• [] 👀 - Sob Revisão
• [] ✔️ - Feita!

Páginas

Aqui estão listadas as páginas que foram traduzidas, estão em processo de tradução ou estão disponíveis para serem traduzidas. Você pode conferir os estados delas verificando as suas labels.

Community

• community/code-of-conduct (@jessescn) ✔️ #5

Tutorial

• tutorial/index (@iaurg) ✔️ #11
• tutorial/part-zero (@dennissiq) ✔️ #4
• tutorial/part-one (@jpedroschmitz) ✔️ #89
• tutorial/part-two (@crisgon) ✔️ #121
• tutorial/part-three (@gutofoletto) ✔️ #27
• tutorial/part-four (@renanmav) ✔️ #14
• tutorial/part-five (@luizcieslak) ✔️ #34
• tutorial/part-six (@gabrielferreiraa) ✔️ #56
• tutorial/part-seven (@ArthurFerrao) ✔️ #55
• tutorial/part-eight (@gabrielreisn) ✔️ #35

Docs

• docs/index (@iaurg) ✔️ #11
• docs/quick-start (@gvarandas) ✔️ #38
• docs/recipes (@lucasruy) ✔️ #40
• docs/glossary (@mjr) ✔️ #17
• docs/gatsby-cli (@jay-jlm) ✔️ #7

Definição do termo original em inglês

Source Plugin
A plugin that adds additional data sources to Gatsby that can then be queried by your pages and components.

Significado relevante de 'source':

Do Collins English Dictionary (trecho):

verb
In business, if a person or firm sources a product or a raw material, they find someone who will supply it.

Acredito que uma localização bem sucedida seria uma que conseguisse manter essa idéia de consumir um recurso (no caso, dados) a partir de uma fonte que fornece os dados.