> > - I personally don't like nextgen nextgen, a bit gimmicky > > True. But we need something concise and a bit catchy, and it was the > best I came up with while writing the page. If you've got better test, > I personally am not that attached to what we have now.
Will ponder! It's important though for sure. For example Django's "Web Development Done Right" says a *lot* about the project, for better and for worse depending on your perspective. > > >> with the most powerful and flexible Object Relational Mapper (ORM) in the > >> world, and > > sounds like hyperbole and will turn off people who disagree instantly. > > But it's the truth. ;) I can tone it down a bit though. Oh you're preaching to the choir there! ;-) > > > This reminds of some of the old Django docs that really rubbed me the > > wrong way. SA doesn't need to be exagerrated > > This isn't docs, this is the marketing face of the project. There is > a difference. > But I agree that we may want to done down things a bit. I'm just thinking from a marketing perspective and reflecting back on my initial exposures to Django, TG, and Pylons. I am pretty much a TG target user, someone who doesn't need the lowlevel no frills basis of pylons, but likes to get my hands dirty and prefers many options of libraries over 1 Right Way. And I was turned off by the hyperbole of the Django docs because I know enough to recognize that there isn't one right way but too little to build it all myself. So IMHO, our target market does not need the same kind of GeeWhiz We Rock marketing. But it still needs marketing for sure! > > > - I think the integration with Pylons should be more prominently > > mentioned, it's very important because whether we like it or not, TG is > > seen as languishing right now and the merge/build-over with pylons if a > > real life saver > > I agree somewhat. But I don;t want to emphasize the number of changes > too much. The key here will be to highlight the tangible benefits of the > pylons connection more. > > As to design concerns, I just used the existing design we had for TG. > > I'm looking at doing a new design, and that one will have more floating width > so that we can make use of wider screens. yeah I figured that. Might be good to get more estate though. If css aid is needed that is somewhere I can pitch in easily. I've been doing a lot of that lately. Thanks for all the work put into the TG2 docs and public face, they are looking like they will be really good! Iain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
