Django 1.7 was released yesterday. We should recommend using that now.

You can preview tutorial here: http://asendecka.gitbooks.io/djangogirls-tutorial/

We would be super grateful for your feedback, pull requests and advice!

From book.djangogirls.org you get 404 from the link

We should have screenshots made by one person.

In the deploy chapter, we're using the command:

$ heroku create

This is fine, but it could be worth pointing out that it's possible to do:

$ heroku create {NAME}

where {NAME} is replaced with the desired app name (rather than using a default one generated by Heroku).

A friend (Andrew Nesbitt) just went through our tutorial as a Python newbie and sent me his feedback. There are two things we can improve on, so I am just adding it here because I will forget it :)

1. When first adding the templates in http://tutorial.djangogirls.org/html/README.html I had to restart the server to get it to find the new templates, you mention about restarting the server in a later stage in the tutorial but not in that one.
2. I couldn't get http://tutorial.djangogirls.org/template_extending/README.html to work using just the content on the page, kept getting the TemplateDoesNotExists error, even after restarting, I ended up adding the following code to get it to work: https://github.com/andrew/django-girls-tutorial/blob/master/mysite/settings.py#L90-L92

• moving it earlier in the process so we can deploy more often
• slowing things down a little bit - a lot of new things happen there very fast

We should link to Django documentation more than we do currently

Just went looking at the newly added part in the intro chapter (dictionaries, see #77) to check for mistakes and wanted to ask: does anyone mind if I replace the example (django "dolls") with something else?

I was actually a little confused at first - I thought "dolls" (which is sometimes used a little condescendingly) was used instead of "girls" so as not to be too repetitive - but even now that I've realised that it refers indeed to toy dolls, it seems a little... off, especially considering that the tutorial isn't aimed at little girls but adult women mostly.

Following the tutorial instructions will not work cleanly on Ubuntu 14.04; I encountered issues with both the virtual environment and the PostgreSQL setup instructions:

Virtualenv:

$ python3 -m venv venv
Error: Command '['/home/eddie/Slask/tmp/venv/bin/python3', '-Im', 'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 1

PostgreSQL:

$ psql
psql: FATAL:  role "eddie" does not exist

I managed to solve the problems with some googling, but since this is supposed to be a very n00b-friendly guide, that should not be required.

The virtualenv-issue can be solved by installing python-virtualenv and then using the virtualenv-command instead of the command supplied in the tutorial. A fix for the problem is submitted upstream but I have no idea when it will trickle down to Trusty Tahr.

From what I can determine, the psql issue is due to the fact that, by default, only the user postgres has access to the PostgreSQL server by default. I solved it by adding myself as a PostgreSQL superuser, and editing some config files.

I can update the documentation to include the solutions to these issues. Would you like a pull request?

As a teacher I have to say that this course is not very well designed in terms of learning curve. The golden rule of all good handbooks is to make solid grounds - explain and excercise easy things and then gradually introduce more complex topics. I found that just at the very beginning of "Introduction to Python" the reader is bashed with methods and dot notation in VERY confusing way that almost stops them from further reading. It's supposed to be introduction for newbies! Let them play with numbers and strings, give them lists and dictionaries. And then introduce objects with their attributes and methods.

Having said all that I urge you to hand this course to at least a couple of CS teachers and note their comments. I will help as much as I can but unfortunatelly I don't have that much time.

Hello, you could create a PT-BR translation team on Crowdin.
After that, in a first moment, I will take charge of disseminating this project in Brazilian communities.

Gitbook has a nice feature of making glossaries and it automatically links the words to their explanations. We need to add GLOSSARY.md file in the main directory and the structure of the file is really simple:

# Keyword
Explanation

# Keyword
Explanation

"Grab yourself a cupcake and go to the next chapter :)"
"Works like a charm? We're proud! Treat yourself something sweet, you have earned it :)"

Puts a pretty cliche picture on women, don't you think? What about changing these two lines and pictures to:

"Well done so far! Celebrate by doing something good for you - taking a short walk, go have a little chat with someone, watch your favorite youtube video or do anything else you would like to do right now."

"Works like a charm? We're proud! Treat yourself with something special, you have earned it :)"

Setting DEBUG = False breaks static files on Heroku. The simple solution would be to switch DEBUG on again but that's not the best solution in terms of security...

During after-workshop coaches meeting someone suggested that explaining Models as tables (and comparing to spreadsheet) is a much better idea than our current one.

Is there someone who is against this?

I think we should put some useful illustrations in this chapter: https://github.com/asendecka/djangogirls-tutorial/tree/master/django_-_why_you_need_a_webframework. It looks like a big wall of text and it's hard to imagine how Django really works. @asendecka, any ideas for that?:)

The Contributing chapter has some non-native speaker English and might need little love to get all sentences make sense.

Currently the tutorial does not contain a LICENSE. This means all content can't be changed, used and published by others without explicit allowance by the original authors. This is even true for all people that contributed so far.

Because I believe that this is not the intention of the original authors a LICENSE file should be added to the repository.

Parts of the tutorial use content from other tutorials. One of them is my Django tutorial django-marcador. It is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. In my opinion there are two things that need to be changed to meet the requirements of the license:

1. The way credit is given does not match the terms of the CC-BY-SA 4.0 license. it says that a user must "provide the name of the creator and attribution parties, a copyright notice, a license notice, a disclaimer notice, and a link to the material".
2. Because the license is a "ShareAlike" license the Django Girls tutorial must also be licensed under a CC-BY-SA 4.0 license.

License and proper credits could look like this:

# License

This work is licensed under the Creative Commons Attribution-ShareAlike 4.0
International License. To view a copy of this license, visit
http://creativecommons.org/licenses/by-sa/4.0/ or send a letter to Creative
Commons, 444 Castro Street, Suite 900, Mountain View, California, 94041, USA.

## Authors

- Ola Sitarska
- Ola Sendecka
- Baptiste Mispelon
- ...

## Credits

Parts of this work are based on the [django-marcador
tutorial](http://django-marcador.keimlink.de/) licensed under Creative Commons
Attribution-ShareAlike 4.0 International License. The django-marcador tutorial
is copyrighted by Markus Zapke-Gründemann et al.

Of course you can split the authors section into main authors and contributors if you want to.

Possibly doing a sqlite setup on local and using Postgres only for Heroku as suggested by @lukaszb and few others would be a much (much, much!) better way.

I think that it's good that command line chapter was added, but I think we should try to make it more interactive. Not only list and explain commands, but let people try them and see how they work.

In my environment there is no initial user created, when arriving at this passage in the tutorial (section 10 Django ORM (Querysets)):

What users do we have in our database? Try this:

>>> User.objects.all()
[<User: ola>]

I simply ran the following, to get a dummyuser to use:

>>> User.objects.create(username='myuser')

What about adding this command to the tutorial section?

Current state when the blog is finished is that there is no authentication on authoring stuff. So anyone can add/edit posts on any of the created blogs. Not good...

There should be an advanced tutorial on adding authentication and authorization. I might even volunteer to start that now...

@bmispelon or @jezdez, can you provide a working solution?:)

When creating a new post the publish_date is not set and therefore it doesn't appear in the post list.

1. Looks like heroku-push ignores the .gitignore file, and pushes local-settings.py.
   We solved this by putting all the settings in settings.py and got rid of local-settings.py.
2. It doesn't trigger the creation of a Postgres database on Heroku. We had to do this manually.

A lot of the awesome work appears to be duplicated in openhatch (1 and others). It might be worth to reach out and coordinate the efforts.

1 - https://openhatch.org/wiki/Django_for_Designers/Laptop_setup

New chapter missing from summary page

After adding models it'd be cool to go to shell and have a little fun with Querysets to show what models can do.

On the introduction page the link to "follow the contributing guidelines" is broken
(https://github.com/DjangoGirls/tutorial/blob/master/contributing/README.md raises 404 error)

We also need to change in some chapter sqlite to postgres.

• can we cut out the git problem?
• is there an easier way than Heroku?

The chapter "Python installation" uses the term "console" without explaining it first or how one can get one. The next chapter "Introduction to Python" explains hot obtain and use a console.

A beer-driven idea from Tomek and me: What if the tutorial is reordered?

Currently the deployment happens near the end of the day (with a version that is working but insecure...), what if deployment to a public space was moved more in front after the step where one can see first results. So after the step where blog-posts are added via admin-interface and displayed on the front-page, it would be a good point to deploy to heroku and be proud of it.

During the workshop Deployment section took us quite some time so we decided to skip it and finish it at the end if time persists. Other mentors did the same thing after number of different minor errors.

I'd propose to move it at the end of tutorial.

• consistent style for talking to reader ("you", "us", etc)
• reward readers for progress with "congrats", and "keep up the good work!" a lot
• add some cupcakes, illustrations and jokes :)
• easy explanations for hard terms

The README is currently the first page of the book. But in my opinion it would be better if the README would explain the purpose of the project and how to create, edit and contribute to it.

For example it is not obvious for someone who has no experience with gitbook how to install it and serve the book locally.

I hope this is the right place for this issue, I couldn't find anything better!

I'm just going through the Installation book that was linked in the recent email to teams and coaches. I've notices that the "What is Django?" chapter seems a little out of place. Could we remove it from there (it should still stay in the main tutorial ofcourse!) and maybe add the one about the Code Editor instead?

Thanks!

It is mixed right now, we should stick to one notation. Argument for 127.0.0.1: when you use runserver it says you should go to 127.0.0.1:8000. Argument for locahost: it's easier to write :).

There were some problems with static files on Heroku (when you change DEBUG to False). @jezdez had a solution for that, can you remind us what it was?

Move virtualenv and app into a centralised djangogirls folder

The current tutorial plays around with the admin-interface first and thus a user is logged in and everything is working fine.

But once people play around and redo their database, the authenticated user is lost. When you then try to save a new blog-post, everything blows up as it tries to set the anonymous user as author.

As the code is OS agnostic and focuses on CLI not GUI the tutorial starts off making directories and later switches between folder/directory terminology.

In the Deploy chapter, in the Visit your application section, there are two paragraphs there are not clear for me:

You’ve deployed your code to Heroku, and specified the process types in a Procfile. You can now instruct Heroku to execute a process type.

Let’s ensure we have one dyno running the web process type:

You lost me there.

Can anyone maybe add a sentence or two to explain what's process type and dyno? Or maybe to phrase it differently so it's easier to understand?

Thanks a lot for anyone that will! :)

If you're a native English speaker (or just know English well!), have some time on your hands and want to help, we would really appreciate if you could help proof read this tutorial!

You can see preview here: http://book.djangogirls.org/.

How to do it?

• comment this thread with the names of chapter you want to proofread. Make sure that anyone else is not reading them already. If all the chapters are "taken", just read from the beginning to see if there is something others didn't catch.
• fork this repository, change and pull request
• receive a 👍 and 😍 from DjangoGirls! :)

Already corrected chapters:

• Introduction (@mjtamlyn)
• How the Internet works (@mjtamlyn)
• Introduction to Python (@mjtamlyn)
• What is Django? (@mjtamlyn)
• Database (@mcmillan)
• Django installation (@mcmillan)
• Code editor (@mcmillan)
• Starting Django Project (@mcmillan)
• Django models (@rebkwok)
• Django admin (@rebkwok)
• Django urls (@rebkwok)
• Django views - time to create! (@rebkwok)
• Introduction to HTML (@evildmp)

In progress:

TO DO:

• Django ORM
• Django templates
• CSS
• Template extending
• Extend your application
• Deploy!
• Django Forms
• Domain
• Homework

I'll be updating this post.