Hi Becka - I'm glad you figured it out, and even happier that you'd like to contribute to making the docs better!
Fixes to the docs where you found problems/errors are certainly welcome; you can do that in a ticket or a pull request, which ever you find easier. There's some information about how to contribute to the documentation here: https://docs.djangoproject.com/en/1.9/internals/contributing/writing-documentation/ The Heroku-specific stuff, though, is a bit problematic for Django's official docs. We've generally shied away from calling out specific commercial services in our official documentation. Those things can be read as endorsements, and we don't want to be in the practice of endorsing specific services. We'd prefer to leave that sort of thing up to the company in question (and indeed in this case Heroku's got a quite good guide over in their documentation). Changing that stance isn't impossible, but it probably involves a larger discussion than you might want to start at this point! So if you want to document the Heroku-specific stuff, I'd recommend you put that elsewhere, perhaps on your own site. Thanks, Jacob On Tue, Mar 15, 2016 at 2:02 PM, Becka <[email protected]> wrote: > Hi, > > I'm pretty new to Django, and am hugely interested in making it easier for > folks to get into Django and to start contributing . > > I had a pretty terrible time both connecting my app to Postgres, and then > deploying to Heroku, and needed a lot of help because of general > documentation missing online, or being very very hard to find. The steps > outlined in some tutorials are hugely inaccurate, and it's impossible to > know which ones to use when starting out. > > The psycopg2 package documentation wasn't helpful enough as a manual, and > I wound up making mistakes that I wasn't able to undo or even figure out, > since I was working on my own. I'm lucky to live in San Francisco, where > help is easy to find. > > Now that I've gone through the process though, I'd like to add this to the > tutorial, as well as the steps to deploying on Heroku. Are these within > the scope of a Django ticket? > > Thanks, > > Becka > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CANOxe%2B1JBcS4LW-auzp85_a%3Dko1YYKKjF8mr904c_rJsqSvPGw%40mail.gmail.com > <https://groups.google.com/d/msgid/django-developers/CANOxe%2B1JBcS4LW-auzp85_a%3Dko1YYKKjF8mr904c_rJsqSvPGw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAK8PqJFFJcXizbjdOePD2LgrrZH7Q%3DG0x3jSzRaqyU%3D-w%3D0ZRQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
