Merge branch 'dev' into jc-block-production

Author: minimalsm

.all-contributorsrc

@@ -52,7 +52,7 @@ Markdown will be translated as whole pages of content, so no specific action is
 
   - _tl;dr Each individual JSON entry should be a complete phrase by itself_
 
-- This is done using the `Translation` component. However there is an alternative method for regular JS: `gatsby-theme-i18n` with `/src/utils/translations.ts`
+- This is done using the `Translation` component. However there is an alternative method for regular JS: using the `t` function from `gatsby-plugin-react-i18next`
 
   - **Method one: `<Translation />` component (preferred if only needed in JSX)**
 
@@ -63,19 +63,18 @@ Markdown will be translated as whole pages of content, so no specific action is
     ;<Translation id="language-json-key" />
     ```
 
-  - **Method two: `translateMessageId()`**
+  - **Method two: `t()`**
 
     ```tsx
-    import { useIntl } from "react-intl"
-    import { translateMessageId } from "src/utils/translations"
+    import { useTranslation } from "gatsby-plugin-react-i18next"
 
     // Utilize anywhere in JS using
-    const intl = useIntl()
-    translateMessageId("language-json-key", intl)
+    const { t } = useTranslation()
+    t("language-json-key")
     ```
 
     ```tsx
-    const siteTitle = translateMessageId("site-title", intl)
+    const siteTitle = t("site-title")
     ```
 
 ## React Hooks

README.md

@@ -0,0 +1,53 @@
+# Deploy and review process
+
+This documentation outlines our current processes for how we deploy the latest changes to ethereum.org, and how we prioritize items in our review process.
+
+## Deploy process
+
+Anything merged into the `dev` branch of [ethereum.org](http://ethereum.org) will go live on ethereum.org at the next release. Currently, we deploy the latest changes to [ethereum.org](http://ethereum.org) twice per week (Monday and Thursday). When deploying, we merge the `dev` branch into the `master` branch. The `master` branch is the latest live version of [ethereum.org](https://ethereum.org).
+
+Occasionally, we’ll also do a patch deploy to fix an urgent or widespread issue.
+
+## Review process
+
+### General review process
+
+We use a first-in, first-out system for reviewing pull requests. The longer a pull request has been open, the higher priority it is for our team to review. In some cases—for example, fixing a high-priority issue or merging low-hanging fruit for a deploy—we will stray from this process and use our best judgement to get higher-impact changes deployed more quickly.
+
+We aim to have every new PR merged or closed within 30 days of opening. As outlined in the following sections, different types of pull requests do have different levels of priority, and this may influence how promptly a pull request is acted on.
+
+### Translations
+
+Translation pull requests are considered high priority. These are when the translated and reviewed files from our translation management platform are submitted as a pull request. They are important to our core value of bringing Ethereum education to as many languages as possible. They also are the accumulation of months of work by translators and reviewers, and any delay to this already long process is undesirable.
+
+**Timeline:** PRs should be merged within 1-4 days of opening (by the next release).
+
+### Feature and bug fixes
+
+Any new feature correlated to an approved issue or bug fix is high-priority. Similar to translators, code contributors dedicate a large amount of their time to improving [ethereum.org](http://ethereum.org) as a resource and addressing their efforts quickly is desirable. All bug fixes should be handled swiftly, but new features that were not discussed, requested or approved do not fall under this timeline.
+
+**Timeline:** Features or bug fixes should be reviewed within 1-12 days. In the case of bugs, more severe bugs will be reviewed more promptly.
+
+### Content
+
+Content PRs are considered medium-priority. Depending on their content, they can be very high-impact but also a high effort to go through the various stages of content review to ensure the content meets the standards we aim for. Content PRs can be broken into two categories: major content (e.g. a new page) and minor content changes (e.g. a new section to an existing page). Typo or grammar fixes are considered separately.
+
+**Timeline:** Major content should be merged within 15-30 days of opening. Minor content changes within 5-15 days of opening.
+
+### Typographical and grammatical errors
+
+Typographical and grammatical errors are medium-priority as small errors of this kind can have second-order ramifications for the linguists of the ~50 languages we currently translate to. Though technically a subgroup of ‘content PRs’, typos and grammar errors take significantly less time to review and, as a result, are treated differently.
+
+**Timeline:** Typo or grammar pull requests should be merged within 1-8 days of opening.
+
+### Adding products
+
+Adding new products is currently a low-to-medium priority (depending on the type of product). These pull requests often take a long time to review as we must extensively research products to ensure we not sending our users to any dubious or unsafe products.
+
+**Timeline:** PRs should be closed or merged within 30 days of opening.
+
+### Adding tutorials
+
+Adding new tutorials to [ethereum.org](http://ethereum.org) is currently low-priority. We are currently in the middle of an epic to revamp our tutorials. As part of this, we’ll be reviewing our existing tutorials, purging outdated or low-quality tutorials, and refining our listing criteria for future tutorials to meet our increased standards. Please always create an issue to discuss the usefulness of your proposed tutorial before opening a PR.
+
+**Timeline:** PRs should be closed or merged within 30 days of opening.

docs/best-practices.md

@@ -9,6 +9,7 @@
   - [Gatsby Docs](https://www.gatsbyjs.org/docs/)
 - [React](https://reactjs.org/) - A JavaScript library for building component-based user interfaces
 - [Typescript](https://www.typescriptlang.org/) - TypeScript is a strongly typed programming language that builds on JavaScript
+- [Chakra UI](https://chakra-ui.com/) - A UI library (Migration in progress)
 - [GraphQL](https://graphql.org/) - A query language for APIs
 - [Algolia](https://www.algolia.com/) - Site indexing, rapid intra-site search results, and search analytics. [Learn more on how we implement Algolia for site search](./docs/ALGOLIA_DOCSEARCH.md).
   - Primary implementation: `/src/components/Search/index.ts`

docs/deploy-and-review-process.md

@@ -343,6 +343,14 @@
     "langDir": "ltr",
     "dateFormat": "MM/DD/YYYY"
   },
+  {
+    "code": "ta",
+    "hrefLang": "ta",
+    "name": "Tamil",
+    "localName": "தமிழ்",
+    "langDir": "ltr",
+    "dateFormat": "MM/DD/YYYY"
+  },
   {
     "code": "th",
     "hrefLang": "th",

docs/stack.md

@@ -1,6 +1,6 @@
 {
   "name": "ethereum-org-website",
-  "version": "6.7.4",
+  "version": "6.13.0",
   "description": "Website of ethereum.org",
   "main": "index.js",
   "repository": "git@github.com:ethereum/ethereum-org-website.git",

i18n/config.json

@@ -1,5 +1,16 @@
 import type { ComponentStyleConfig } from "@chakra-ui/theme"
 
+const disabledStylesSolid = {
+  bg: "disabled",
+  opacity: 1,
+}
+
+const disabledStylesOutline = {
+  color: "disabled",
+  borderColor: "disabled",
+  opacity: 1,
+}
+
 const commonOutline = {
   border: "1px",
   color: "text",
@@ -9,6 +20,9 @@ const commonOutline = {
     color: "primary",
     bg: "background",
     borderColor: "primary",
+    _disabled: {
+      ...disabledStylesOutline,
+    },
   },
   _active: {
     color: "primary",
@@ -18,11 +32,12 @@ const commonOutline = {
   _focus: {
     color: "primary",
     borderColor: "background",
+    _disabled: {
+      ...disabledStylesOutline,
+    },
   },
   _disabled: {
-    color: "disabled",
-    borderColor: "disabled",
-    opacity: 1,
+    ...disabledStylesOutline,
   },
 }
 
@@ -33,6 +48,9 @@ export const Button: ComponentStyleConfig = {
     _hover: {
       textDecoration: "none",
       boxShadow: "primary",
+      _disabled: {
+        boxShadow: "none",
+      },
     },
     _focus: {
       boxShadow: "outline",
@@ -53,13 +71,15 @@ export const Button: ComponentStyleConfig = {
       _hover: {
         bg: "primary",
         opacity: 0.8,
+        _disabled: {
+          ...disabledStylesSolid,
+        },
       },
       _active: {
         bg: "primaryHover",
       },
       _disabled: {
-        bg: "disabled",
-        opacity: 1,
+        ...disabledStylesSolid,
       },
     },
     outline: {
@@ -70,5 +90,17 @@ export const Button: ComponentStyleConfig = {
       color: "primary",
       borderColor: "primary",
     },
+    icon: {
+      appearance: "none",
+      background: "inherit",
+      padding: "initial",
+      border: 0,
+      color: "inherit",
+      boxShadow: "none",
+      _hover: {
+        color: "primary",
+        boxShadow: "none",
+      },
+    },
   },
 }

package.json

@@ -0,0 +1,32 @@
+import type { ComponentStyleConfig } from "@chakra-ui/theme"
+
+export const Tabs: ComponentStyleConfig = {
+  variants: {
+    primary: {
+      tab: {
+        borderTopRadius: "0.3rem",
+        borderBottom: "1px solid",
+        borderBottomColor: "primary",
+        px: 4,
+        py: "0.3rem",
+        _selected: {
+          color: "background",
+          bg: "primary",
+        },
+      },
+      tabpanels: {
+        mt: 4,
+      },
+      tabpanel: {
+        p: 6,
+        bg: "ednBackground",
+        border: "1px solid",
+        borderColor: "lightBorder",
+        borderRadius: "lg",
+      },
+    },
+  },
+  defaultProps: {
+    variant: "primary",
+  },
+}

src/@chakra-ui/gatsby-plugin/components/Button.ts

@@ -3,11 +3,13 @@ import { Link } from "./Link"
 import { Tag } from "./Tag"
 import { Modal } from "./Modal"
 import { Checkbox } from "./Checkbox"
+import { Tabs } from "./Tabs"
 
 export default {
   Button,
   Link,
   Tag,
   Modal,
   Checkbox,
+  Tabs,
 }