Future Lessons

First off this does NOT replace the wiki http://groups.drupal.org/node/2433 (Josh_k should we make the idea wiki sticky... hehe wiki sticky?) however, on g.d.o. we can't comment on a wiki and while its a great tool for collecting info, I find people are more vocal about leaving comments than they are about editing a wiki - I also know who I'm talking with in a comment thread.

I think it'd be a good idea to start scheduling more than a few days in advance ;) If we an agree on some of these we can create the events and have syllabus of sorts.

Jan 28th - CVS with Greggles @ 11 PST
Feb 4th -
Feb 11th -
Feb 18th -

These are just our standard course times - feel free to propose some off times if its helpful.

That said I can present on the following:

phptemplating - in the wiki this is currently:

Making Drupal not look like Drupal (i.e. themeing)

* Pros: This knowledge desperately needs to be shared. Josh already has a great example with workingcalifornians.com. It'd be great if he could show us how he used panels to make it.
* Cons: This is not a two-hour session, needs to be broken up somewhat.

Yes - I don't think its a single session either, but the basics of it can be. Ideally this would be two sessions taught by two different people.

Taxonomy In wiki as :

Taxonomy / Categories

* Pros: I don't get it yet, maybe some others don't get it either: maybe we'd all get it after a quick lesson ;)
A good introduction on the use of taxonomy could be read here http://www.drupal.org/node/81589
A better session would be creating a taxonomy on a real world example from beginning to a finish product
* Cons: Might be boring to many

I would expand on that by saying "Tricks with taxonomy" and cover associated contrib modules suh as "Taxonomy Access Control"

CCK in wiki as

All About CCK, its power, using with views, themeing, etc (from lapur)
* Pros: upgrade paths (new field(set)s) are free, self-normalizing, when you have no need for advanced forms it's easy to set up, ConTemplate module for customizing the regular "node view"
* Cons: performance hit (depending on mem/CPU and the number of non-anonymous requests (which can't be cached)), when you need advanced forms things can become a bit "hacky"

We touched upon the 'deision' as to whether to make a custom node-type or use CCK - I can add to this "Creating a custom field module for CCK" which is an in-between step (for the code - same database issues) For any people who want to start being CCK heavy hitters! (not that I am - but I'm learning quick!)

So, bring it! Who wants what lesson where. If you have a preferred weekend for either of the above, let me know, I'm fairly flexible. I'd rather not teach two weekends in a row - diversity is the spice of life.