The slides printed for attendees of the Pycon 2010 Long Pinax Tutorial. James Tauber was the co-author and deserves tons of credit for his work. So does Brian Rosner and the rest of the Pinax team.

1. Pinax Long Tutorial PyCon 2010

2. Introduction ~10 minutes

3. Who are we? - James Tauber Pinax Founder CEO of Eldarion http://jtauber.com

4. Who are we? - Daniel Greenfeld Pinax Core Developer Software Engineer for NASA's Science Mission Directorate Author/Instructor for Holden Web, LLC (holdenweb.com) Developer for Eldarion http://pydanny.com

6. History of Pinax 2008: James Tauber decides to stop repeating himself 0.5 — First official release 2009: First full year of Pinax 0.7 — Groups, Static Media, Move to pip and virtualenv, Section 508 2010: Today 0.9 — Next great thing

7. Philosophy of Pinax By integrating numerous reusable Django apps to take care of the things that many sites have in common, it lets you focus on what makes your site different. In other words... D on't R epeat Y ourself

8. What will we be doing? Installing Pinax Reviewing the core underlying layer Changing the look and feel Various Pinax tricks Building on what Python and Django gives us Deployment Community

9. Pinax Installation ~10 minutes

13. Core Underlying Components ~10 minutes

14. Core: Accounts Avatar Email Addresses Language OpenID Password Management Signup Timezone

16. Core: Groups Groups in Pinax are containers with user membership and content. They are a base on which to write your own app and plug in whatever content apps you need. Examples: Tribes (Wiki, Photos) Projects (Tasks, Wiki) Guilds (Events)

17. Core: Static Media Handling css, images, javascript Project vs Pinax Theme vs App level Separation of static media from user-contributed media. build_static management command for deployment

18. Pinax Projects ~10 minutes

20. Using pinax-admin List all the currently available projects in Pinax pinax-admin clone_project -l Cloning a project pinax-admin clone_project social_project djangofans

22. Pinax specific settings.py ~5 minutes

23. Some Pinax Settings SITE_NAME (used in some default templates) CONTACT_EMAIL (used in some default templates) PINAX_THEME (prefix for template resolution) ACCOUNT_OPEN_SIGNUP (can anyone join?) ACCOUNT_REQUIRED_EMAIL (is email address required?) ACCOUNT_EMAIL_VERIFICATION (must email be verified?) EMAIL_CONFIRMATION_DAYS (how long before expiry?) LOGIN_REDIRECT_URLNAME (first page to go after login)

24. Media/Static Files Settings MEDIA_URL / MEDIA_ROOT (URL and filesystem location for files uploaded/stored by Django only) STATIC_URL / STATIC_ROOT (URL and filesystem location for site assets such as CSS, JS and images) SERVE_MEDIA (Used in urls.py to hook-up MEDIA_URL and STATIC_URL used for development)

26. Modification of core Pinax applications ~10 minutes

27. Profiles Frequently extended application You always want a custom field

28. Modification of core Pinax applications Before you change a core application: Can you accomplish your tasks with CSS? Can you accomplish your tasks with Javascript? Can you accomplish your tasks with template changes? Can you create a new application that does the work?

29. But my task needs a code/database change! pinax-env/lib/python2.x/site-packages/Pinax/pinax/apps/<app> pinax-env/src/Pinax/pinax/apps/<app> Don't make changes in Pinax itself!

30. But my task needs a code/database change! Option 1: Use the apps directory of your project cd apps/ django-admin.py startapp profiles Option 2: Use virtualenv/pip Create a stand alone app (best done eggified) pip install -e my-app

31. Adding Django applications ~10 minutes

32. Won't conversion be hard? Remember: Pinax is just Django with an opinion pip install <django-app> (Don't forget to add it to your requirements.txt file) make changes to INSTALLED_APPS, etc in settings.py make template changes

33. Modification of templates ~10 minutes

34. Customize templates, don't change them cp -r site-packages/pinax/templates/default/profiles my-project/templates Don't edit the Pinax templates directory!

35. Themes in Pinax Change your look and feel by just changing settings.py! PINAX_THEME = &quot;default&quot; But only one theme is currently shipped with Pinax PINAX_THEME = &quot;default&quot;

36. Changing the logo Step 1: Add your image to <my-project>/media Step 2: In <my-project>/templates/site_base.html in the logo_link_image block change the name of the logo image to match your own. (but really you should be making more style changes than just the logo)

38. Changing the look and feel ~10 minutes

41. Adding CSS In templates/site_base.html {% block extra_head_base %}: <link rel=&quot;stylesheet&quot; href=&quot;{{ MEDIA_URL }}custom.css&quot; /> mkdir site_media mkdir site_media/media touch custom.css body { background-color: #000; }

42. Changing Avatar defaults ~10 minutes

43. django-avatar by default uses Gravatar Pros: Gravatars follow a user's account name across the Internet Means users get a default avatar anywhere Cons: You might not want the default Gravatar avatar image You might not want to lock user avatars into a single service

44. Changing the default Gravatar logo In settings.py AVATAR_DEFAULT_URL = STATIC_URL + &quot;<our_custom_avatar.jpg>&quot; AVATAR_GRAVATAR_BACKUP = False

45. django-groups ~10 minutes

46. What are groups? Groups in are containers with user membership and content. Example: A project with tasks and wiki A guild with a forum and events

50. Looking at django-groups pinax-admin clone_project sample_group_project sgp cd sgp python manage.py syncdb python manage.py runserver

51. django-uni-form ~10 minutes

54. Django forms rock!

55. Tables are for tabular data

56. In Section 508, some tabular forms are allowed

57. Out of the box pretty Django forms are tabular

58. Django Uni-Form = Django forms docs + template tag + Uni-Form css/js forms library

59. Basic Usage

61. Advanced Django Uni-Form ~10 minutes

62. Making form generation easier {% load uni_form_tags %} {% with form.helper as helper %} {% uni_form form helper %} {% endwith %}

63. Adding action handlers {% load uni_form_tags %} {% with form.helper as helper %} {% uni_form form helper %} {% endwith %}

64. Media Handling ~10 minutes

66. Static media is good Caching Security Separating servers

67. build_static tool python manage.py help build_static Copy static media files from apps and other locations in a single location. --dry-run (don't copy but show what will be done) --link (create symlinks rather than copy) Project vs Pinax Theme vs App level

71. JavaScript, jQuery and Pinax ~5 minutes

72. Why was jQuery chosen for Pinax? Because Pinax has an opinion But you can still use YUI, Mootools, or plain old JavaScript

73. Best practice for JavaScript use

74. django-ajax-validation ~5 minutes

75. django-ajax-validation In urls.py: from my_app.forms import MyAppForm (r&quot;^validate/$&quot;, &quot;ajax_validation.views.validate&quot;, { &quot;form_class&quot;: MyAppForm, &quot;callback&quot;: lambda request, *args, **kwargs: {&quot;user&quot;: request.user} }, &quot;myapp_form_validate&quot;),

77. django-pagination ~2 minutes

79. Testing your Pinax application ~5 minutes

80. Why should you bother testing? &quot;Untested code is broken code&quot; Martin Aspelli &quot;Code without tests is broken as designed&quot; Jacob Kaplan-Moss &quot;All the cool kids are doing tests&quot; Chris Shenton &quot;If I go to another testing talk I'm going to die&quot; Daniel Greenfeld

81. Pinax Deployment ~10 minutes

85. Community ~10 minutes

90. Q & A