Skip to content

Commit

Permalink
housekeeping: Adjusted README, versioned Glossary + Style Guide (#8)
Browse files Browse the repository at this point in the history
* housekeeping: Adjusted README, versioned Glossary + Style Guide

This is just to tidy up things a bit.

* fix

* refactor

* glossary: adding terms
  • Loading branch information
deblasis authored and LucaBlackDragon committed Feb 14, 2019
1 parent 86ede57 commit ae4ccb8
Show file tree
Hide file tree
Showing 3 changed files with 43 additions and 2 deletions.
33 changes: 33 additions & 0 deletions GLOSSARY.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
# Glossary

Glossary of the translations of technical and React-specific terms.

## Untranslatable terms
- footer
- bug
- browser
- client
- server

# Common Translations

Suggestion on words and terms:

| Original word/term | Suggestion |
| ------------------ | ---------- |
| refactor | rifattorizzare |
| refactoring | rifattorizzazione |
| render | renderizzare (verbo), renderizzato (nome) |
| React component class | classe componente React |
| React component type | tipo componente React |

## Problematic terms

Here's a list of terms that require discussion/agreement, with a link to the issue.

- `to render` (#7)
- `React component class` (#7)
- `React component type` (#7)
- `refactor` (#9)
- `event handler` (#10)
- `event listener` (#10)
10 changes: 8 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,12 @@
# reactjs.org
# it.reactjs.org 🇮🇹

This repo contains the source code and documentation powering [reactjs.org](https://reactjs.org/).
This repo contains the source code and documentation powering [it.reactjs.org](https://it.reactjs.org/).


## Before we start, some useful links:

- [Glossary](GLOSSARY.md)
- [Style Guide](STYLE_GUIDE.md)

## Getting started

Expand Down
2 changes: 2 additions & 0 deletions STYLE_GUIDE.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
<!-- content from the issue here, then we should update the pinned issue to point to the files for maximum visibility -->
👷

0 comments on commit ae4ccb8

Please sign in to comment.