You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,36 +9,36 @@ The Django Girls Tutorial is licensed under a [*Creative Commons Attribution-Sha
9
9
10
10
# Editing basics
11
11
12
-
The source code of the tutorial is [hosted on Github](https://github.com/DjangoGirls/tutorial). The Github[Fork & Pull workflow](https://help.github.com/articles/using-pull-requests) is used to accept and review changes.
12
+
The source code of the tutorial is [hosted on GitHub](https://github.com/DjangoGirls/tutorial). The GitHub[Fork & Pull workflow](https://help.github.com/articles/using-pull-requests) is used to accept and review changes.
13
13
14
14
The tutorial uses the [GitBook](https://www.gitbook.com/) service for publishing its documentation. [See more information about how Gitbook works](https://help.gitbook.com/).
15
15
16
16
The tutorial is written in [Markdown mark up language](https://help.github.com/articles/markdown-basics).
17
17
18
-
You can find any discussions about the contents of the tutorial on the [Github issue tracker](https://github.com/DjangoGirls/tutorial/issues).
18
+
You can find any discussions about the contents of the tutorial on the [GitHub issue tracker](https://github.com/DjangoGirls/tutorial/issues).
19
19
20
20
[Crowdin](https://crowdin.com/project/django-girls-tutorial) platform is used to manage translations. If you want to join an existing translation team or launch a new translation, send an email to the [translation managers](mailto:[email protected]) or contact [support team](mailto:[email protected]). If you want to propose some small changes or fix typos in existing translations, please create a Pull Request.
21
21
22
22
# Getting started and prerequisites
23
23
24
24
For contributing to the tutorial the following is needed to get started:
25
25
26
-
* a [Github account](https://github.com)
27
-
* 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 computer to Github.
26
+
* a [GitHub account](https://github.com)
27
+
* 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 computer to GitHub.
28
28
29
29
## Fork the repository
30
30
31
-
First fork the [DjangoGirls/tutorial](https://github.com/DjangoGirls/tutorial) repository to your personal Github account:
31
+
First fork the [DjangoGirls/tutorial](https://github.com/DjangoGirls/tutorial) repository to your personal GitHub account:
32
32
33
33
34
34
35
35
# Editing chapter content
36
36
37
37
## Simple changes
38
38
39
-
For simple changes like typo corrections you can use the Github online editor:
39
+
For simple changes like typo corrections you can use the GitHub online editor:
40
40
41
-
* Open your local fork page on Github,
41
+
* Open your local fork page on GitHub,
42
42
* go to *README.md* file in any chapter,
43
43
* press the *Edit* icon (pen)
44
44
@@ -48,15 +48,15 @@ and you can edit the chapter directly on github.com.
48
48
49
49
Markdown syntax is used to edit the individual pages of the tutorial.
Save your changes and create a pull request as explained below.
54
54
55
55
## New content and complex changes
56
56
57
57
For adding new chapters, writing longer snippets of text or adding images, you need to get a copy of the tutorial to your local computer.
58
58
59
-
Either use the Github app for your operating system (mentioned above) or `git` command line to get the repository locally. You get the repository address from the front page of your own Github repository fork:
59
+
Either use the GitHub app for your operating system (mentioned above) or `git` command line to get the repository locally. You get the repository address from the front page of your own GitHub repository fork:
@@ -70,7 +70,7 @@ Then you can open the tutorial in Gitbook Editor (*File* > *Open book*).
70
70
71
71
Make any changes in the tutorial using Gitbook and then save changes (*Book* > *Save all*).
72
72
73
-
Then commit the changes using `git` and push the changes to your remote Github repository.
73
+
Then commit the changes using `git` and push the changes to your remote GitHub repository.
74
74
75
75
Example:
76
76
@@ -101,17 +101,17 @@ If you don't want to download the Gitbook Editor app you can also go to the [Git
101
101
102
102
# Making a pull request
103
103
104
-
After you have finished your changes you need to create [a pull request](https://help.github.com/articles/using-pull-requests) on Github. DjangoGirls will get notified about the pull request, review your changes, suggest any corrections if needed and then *pull* your changes to the master version.
104
+
After you have finished your changes you need to create [a pull request](https://help.github.com/articles/using-pull-requests) on GitHub. DjangoGirls will get notified about the pull request, review your changes, suggest any corrections if needed and then *pull* your changes to the master version.
105
105
106
-
In your own repository on Github press do *Compare & pull request*
106
+
In your own repository on GitHub press do *Compare & pull request*
107
107
108
108
109
109
110
110
Fill in the information *why* this change is being made. The reviewer can see the details of the actual change, so you don't need repeat the content of the change.
111
111
112
112
Then press *Create pull request*.
113
113
114
-
Github emails will notify you for the follow up process.
114
+
GitHub emails will notify you for the follow up process.
Copy file name to clipboardExpand all lines: cs/django_templates/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,7 +72,7 @@ Všimla sis, že jsme tentokrát použily lehce odlišnou notaci (`{{ post.title
72
72
73
73
Bylo by dobré vidět, jestli tvá webová stránka bude stále fungovat i na webu, že? Pojďme zkusit další nasazení/deploy na PythonAnywhere. Tady je rekapitulace postupu...
Copy file name to clipboardExpand all lines: en/django_templates/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -71,7 +71,7 @@ Have you noticed that we used a slightly different notation this time (`{{ post.
71
71
72
72
It'd be good to see if your website will still be working on the public Internet, right? Let's try deploying to PythonAnywhere again. Here's a recap of the steps…
Copy file name to clipboardExpand all lines: fr/deploy/README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,11 +8,11 @@ Comme vous l'avez appris, un site web a besoin d'être installé sur un serveur.
8
8
9
9
[1]: https://www.pythonanywhere.com/
10
10
11
-
Nous allons aussi utiliser les services [GitHub][2], ce qui nous permettra d'héberger notre code en ligne. Il existe d'autres entreprises qui proposent des services similaires. Cependant, presque tous⋅tes les développeurs·ses possèdent aujourd'hui un compte Github et, dans quelques instants, vous aussi !
11
+
Nous allons aussi utiliser les services [GitHub][2], ce qui nous permettra d'héberger notre code en ligne. Il existe d'autres entreprises qui proposent des services similaires. Cependant, presque tous⋅tes les développeurs·ses possèdent aujourd'hui un compte GitHub et, dans quelques instants, vous aussi !
12
12
13
13
[2]: https://www.github.com
14
14
15
-
Github va nous servir d'intermédiaire pour envoyer et récupérer notre code sur PythonAnywhere.
15
+
GitHub va nous servir d'intermédiaire pour envoyer et récupérer notre code sur PythonAnywhere.
16
16
17
17
# Git
18
18
@@ -110,7 +110,7 @@ Tapez les instructions suivantes dans votre console (remplacez `<votre-nom-d'uti
110
110
$ git push -u origin master
111
111
112
112
113
-
Entrez votre nom d'utilisateur et mot de passe Github. Vous devriez voir quelque chose comme ceci :
113
+
Entrez votre nom d'utilisateur et mot de passe GitHub. Vous devriez voir quelque chose comme ceci :
@@ -141,7 +141,7 @@ Une fois enregistré sur PythonAnywhere, vous serez automatiquement redirigée s
141
141
142
142
> **Note** : PythonAnywhere utilise Linux. Si vous êtes sous Windows, la console sera un peu différente de celle de votre ordinateur.
143
143
144
-
Importons notre code depuis Github vers PythonAnywhere en créant un "clone" de notre dépôt. Tapez la commande suivante dans la console de PythonAnywhere (n'oubliez pas d'utiliser votre nom d'utilisateur Github à la place de `<your-github-username>`):
144
+
Importons notre code depuis GitHub vers PythonAnywhere en créant un "clone" de notre dépôt. Tapez la commande suivante dans la console de PythonAnywhere (n'oubliez pas d'utiliser votre nom d'utilisateur GitHub à la place de `<your-github-username>`):
0 commit comments