• Remove the value of SECRET_KEY and DEBUG from settings.py and put their values in a .env file.

• is_published returns true if the current date is on or after the question’s publication date.
• can_vote returns true if voting is currently allowed for this question.

• Users can resubmit on any polls and it replaces the previous submit on that poll

• Database setup
• Creating models
• Activating models
• Playing with the API
• Introducing the Django Admin

• add @login_required at vote_for_poll() in polls/views.py
• if has the previous voted show the previous voted as a string, if not has shown nothing.

• Creating a project
• The development server
• Creating the Polls app
• Write the first view

• Divide polls/tests.py to
  • test_auth.py
  • test_detail.py
  • test_index.py
  • test_models.py
  • test_voting.py

• On the polls index page, add “vote” and “results” links for each question.
• Only show “vote” link for a poll where voting is allowed.
• On the polls detail page, add a “Back to List of Polls” link so person can go back without voting.
• On the voting results page, also add a “Back to List of Polls” link.

• Make the votes align in a column, omit the word “votes” after the count – it’s redundant, remove the bullets.

• Writing the first test
• Test a view

If someone navigates to the polls detail page for a poll where voting is not allowed, redirect them to the polls index page and show an error message.

• Use Django Messages Framework for this task

• Customize Styling
• Adding a background-image

• Customize the admin form
• Adding related objects
• Customize the admin change list
• Customize the admin look

• unit tests for is_published and can_vote.

• Use Authentication in Django
• Add URL for login, logout in mysite/urls.py
• Add login.html
• Redirect to home page when the user has been logout
• Edit polls/index.html to show username when the user is authenticated.

• Write a minimal form
• Use generic views: Less code is better

• Add authentication checks vote() in polls/views.py by use a decorator.

• add logging logged in
• add logging logged out
• add logging login failed
• add logging vote success

• add an end_date attribute that is the ending date for voting.
• run migrations to update the database schema.

4. Users have the number of survey items and the number of responses unrestricted.

As Mr James has posted in the classroom this morning, use "poll" instead of "survey" for now.

Saying the number of responses is unrestricted might make some misunderstand that one "user" can vote more than once, which shouldn't be the case. Perhaps adding a clause like "but they are limited to one vote for each poll" for clarity would be good.

1. Users can view a list of the available polls.

7. Web visitors cannot see the question before the opening date.

If "the question" and "polls" refer to the same thing, using the same term again would make it more clear.

3. Users can view and edit previously submitted polls before the end date.

Writing it this way would make it seem like the poll, that is the question and the choices, are editable until the "end date". If by this you actually meant the choice voted for can be changed, using these words instead would make it clearer.

• Writing more views
• Write views that actually do something
• Raising a 404 error
• Use the template system
• Removing hardcoded URLs in templates
• Namespacing URL names

• authentication
• voting

• Sort them so that the newest questions are first