Hi, I have a couple ideas for organizing our tutorials more clearly: - each tutorial should have a "headline" statement that summarizes what skill(s) the reader will learn, and what it assumes they already know (with links to more basic tutorials that teach those more basic skills). That way, a reader should be able to figure out immediately which tutorial genuinely fits his / her goals.
- I notice a general pattern in our tutorials, of two fundamentally different kinds of material * using Pygr with existing databases, i.e. how to "plug in" existing databases so Pygr can access them * using Pygr to create your own databases. (this material really needs to be expanded, because in the past I often assumed that readers already had their own databases, and just wanted to plug them in to Pygr). This subdivision of two themes is present in nearly all our tutorials. For example, part of the worldbase tutorial describes using worldbase to access various datasets, whereas another part explains how to add your own datasets to worldbase. I propose breaking this into two separate, shorter tutorials (linked to each other, of course), so it's easier for users to see what skills are covered where, and to quickly find the tutorial that covers what they want to learn at any given moment. What do other people think? -- Chris --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
