Hi Tim, > Maybe it's the attitude? Turn the perceived inaccessibility to Pylons' > advantage and appeal more directly to the hardcore crowd. Give it a > more rugged image and a bit of a bite. Use a tag line like "heavy-duty > rapid web development," "a powerful, customizable web framework," or > "rapid web development for enthusiasts." It certainly fits with what I > think of a pylon--a strong, proud, imposing structure. Don't bother > with the "our MVC, rapid development framework makes websites quicker > and better than those other MVC, rapid development frameworks" pack. > It's a crowded field and from an uninformed perspective they can all > blend together pretty quickly. Instead, emphasize Pylons' raw power > and potential for customization, and in fairly aggressive terms. Say > that, yes, it has a steeper learning curve, but in the end you'll have > a app that you can be proud of and that's truly your own. And you can > do it without the cruft of Java, the chaos of PHP, or the roadblocks > of your typical MVC framework. Make it tempting for the people who > want to know how a system ticks and how to get the most out of their > code. Then provide the tools and resources for them to do just that > I like all your suggestions and whole-heartedly agree. The brand we seem to be converging on is "Pylons: Power to the developer" and everything you've written neatly summarizes the ideas that tag line is supposed to represent. > I'd also argue for using "customizable" over "flexible." The former > word implies more direct interaction and control. You hear about car > enthusiasts customizing their cars, not their cars being flexible or > adaptable (or case modders with cases, etc). It gives a better sense > of "Yes, I can change this system to fit my preferences and > requirements." Just a personal preference, though, of course. > I'm happy with that, good point. As part of the next stage I'm keen to slightly restructure Pylons so that the way the packages are organised better reflects what they actually do so that people can instantly see how customisable Pylons is by picking and choosing the best packages. > The bullet points for me, as far as feature set goes: > > 1.a. Rapid development and MVC (which applies to just about everything > post-RoR) > 1.b. A second generation modern web frameworks, building on ideas from > Rails, Django, etc, and learning from their flaws > 2. Designed for customization; modular, configurable at any level > 3. Leverages the experience and power of more specialized libraries: > Paste for low-level WSGI/HTTP, Mason->Myghty->Mako, SQLAlchemy > 4. Good tools for testing and debugging > I like the idea of calling it a "second generation framework" in particular but all your points are valid. > I don't typically post unless I feel it's something that hasn't been > said and might benefit the project or the community. Hope my comments > are useful in that regard. > Point taken, thanks for the advice.
James --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
