Skip to content

Restructure tutorialΒ #1777

Open
Open
@ekohl

Description

I've been thinking about this for a long time, but I'm wondering how others think.

The main problem I see is that it takes a long time before you get something visible. I'd suggest to restructure it a bit so there are more intermediate results. I'd propose the following (keeping the start the same):

  • Your first Django project!
  • Django URLs
  • Django views – time to create!
  • Introduction to HTML
  • Deploy!

Now the reader has a basic static blog. One option is to add CSS. I've noticed that most of my mentees like that, but I'm a bit worried that then the reader won't even get to the Django parts. So I'd suggest to then make it dynamic.

  • Django models
  • Django admin
  • Django ORM (Querysets)
  • Dynamic data in templates
  • Django templates

Now there is a working blog, but it's not very nice. So we're going to fix that.

  • CSS – make it pretty
  • Template extending

Now there's a solid base. Here it turns into adding additional functionality.

  • Extend your application
  • Django Forms
  • What's next?

Any thoughts on this?

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions