On Jun 1, 2007, at 11:11 AM, Mike Orr wrote:
> I like PylonsHQ. What we should do is put "Pylons Headquarters" at
> the top of the site as a segue from the domain name to the site.
> Pylonshq is short and easy to type. I just hate compound words as
> domain names: footemplate, fooframework, fooinc. pylons-framework.org
> is much better if we need that "framework" word. But how many people
> see a link with the raw URL in it, with nothing else around it? Not
> the people we're marketing to. Just deep links to mailing-list
> messages and the like.
>
> Pylonshq.org is available. Why don't we snap it up and make it an
> alias. Then we'll have the ability to make it the primary site later.
> Would we really lose our Google ranking if we made .com a redirect to
> .org? Lots of sites have both.
Done, I'll setup the redirect tonight. I like the idea of having
Headquarters put in the title, since that is in the URL and was our
original intention. I'm not a fan of putting 'framework' in the
domain, partly because I'm not sure that phrase will always apply or
even really applies right now.
> The introduction can be improved, certainly. I wasn't here when
> Pylons was started or the website was created, but my sense is that
> Pylons has evolved since then. Its first adherents were looking for
> *any* framework that was Paste-ified (and thus WSGI-ified) from the
> ground up, and Pylons was it. Now we're getting more Pythoneers who
> want "something more modular than Turbogears", non-Pythoneers who want
> "something like Rails", newbies who want "something easy to code,
> scalable, performant, and stable". The trick is to address all these
> audiences. If we focus totally on newbies, that leaves everybody else
> cold. Plus we need to focus on building 1.0 right now, not on
> bringing in hordes of newbies Because...
We definitely need new copy for the website introduction and
overview. Any volunteers?
> - we need all hands on deck
> - we don't have the resources to train a huge influx of newbies.
> after we get 1.0 and the documentation finished, then we'll be in a
> better position
> - upcoming changes may require changes in applications or cause a
> period of instability. Not what newbies are thrilled about.
> - other frameworks frankly do a better job of meeting newbie's
> needs. Why compete with them in a half-assed way?
I definitely agree.
> You're right that WSGI is no longer important enough to fill 1/3 of
> the introduction. WSGI has become an infrastructure piece that all
> frameworks should support or else. Nevertheless, Pylons' use of WSGI
> as the core rather than an add-on is worth noting, as well as the ease
> of of plugging multiple applications into the same URL space via Paste
> or within a Pylons controller should be noted.
I think its important in that its WSGI through-out the core, but yes,
it is becoming more common so it could be considered more of a
documentation thing rather than a 'core concept for the description'
type thing.
> The first and last sentences are vague. TurboGears uses hyperlinks to
> substantiate each claim. Mako gives you many of its features in a
> nutshell. SQLAlchemy has a table of features and elaborations, and a
> link to testimonials. Cheetah does the same, tells where it is being
> used ("to generate C++ code, Java, sql, form emails, and even Python
> code"), and has a couple quotes on the home page.
>
> Regarding the logo, I'm more concerned about the theme than the
> details. What guidelines are we going to give the designer? Just
> "make a logo"? Or "make a logo containing an electrical tower"? It's
> really up to us to choose our mascot, not leave it to the logo
> designer, otherwise he may go off totallyon a tangent. Though it's
> worth asking him if he has some different ideas. I like the current
> yin-yang snakes in the Python logo but I didn't like some of the
> previous logos and refused to wear T-shirts that had them. Quixote
> has some windmill logos but what's so "Quixote" about them?
The current theme that I plan on giving the designer:
Imagine two pylons some ways apart, with a hand and part of arm
reaching up to hold onto the line between them. It'd be zoomed in on
the hand holding the power line, with some - \ | / - above it to show
it being energized. Something like that perhaps, with only some of
the Pylon in view. The hand shouldn't be realistic and prolly some
vague shape of a hand.
Generally, we're aiming to not have such a 'heavy' feel to the
website as well, since the thick dark colors really make it feel
weighted down. Something where it's easier to highlight news and
"new" stuff going on, new screencasts, etc.
Cheers,
Ben
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To post to this group, send email to pylons-discuss@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
