> On Dec 26, 2014, at 6:09 AM, Steve Piercy <[email protected]> wrote: > > On 12/25/14 at 10:56 PM, [email protected] (John Anderson) pronounced: > >> There is a lot of confusion around the "Pylons" organization and I think in >> general our http://www.pylonsproject.org/ website doesn't help alleviate >> any of that confusion. For example you can't even go to >> http://www.pylonsproject.org/projects and get a list of Pylons projects, >> this just redirects to Pyramid's about page. > > http://www.pocoo.org does a nice job of being the *organization* web site. I > think http://www.pylonsproject.org should follow suit. > >> I feel we should decide which are "official" pylons projects and make it >> extremely obvious which ones fall under this umbrella. Off the top of my >> head the following are ones probably worth listing under this umbrella: >> >> https://github.com/Pylons/colander >> https://github.com/Pylons/deform >> https://github.com/Pylons/substanced >> https://github.com/Pylons/venusian >> https://github.com/Pylons/waitress >> https://github.com/Pylons/webtest >> https://github.com/Pylons/webob > > Agreed. > >> Now they all already live under the /Pylons/ organization on github but >> there are plenty of less "complete" projects underneath that organization >> that makes it hard to track down which are ready for prime time. > > Yes. GitHub is not a good way to present "featured" or "official" projects. > >> The other big issue is a lot of these live under their domain, under >> pythonpaste.org, or don't have a website outside of readthedocs at all. >> >> I propose that we create subdomains for each of them and make sure to be >> consistent on including a footer that mentions that they are pylons >> projects. This would be similar to how the Apache organization manages >> their projects: >> >> http://kafka.apache.org/ >> https://spark.apache.org/ >> http://cassandra.apache.org/ >> >> and how pocoo does it: >> >> http://flask.pocoo.org/ >> http://click.pocoo.org/ >> http://werkzeug.pocoo.org/ > > Agreed. > http://pyramid.pylonsproject.org/ > >> It would probably also make sense to try to maintain a more consistent >> brand across each projects website as well. Allowing each project to have >> some personality of their own will be important by keeping a standard color >> scheme and layout would help people recognize a pylons project immediately. > > At the last PyCon Pyramid sprint, we started doing just that with: > http://trypyramid.com/ > > We went with Bootstrap 3 and kept it stupid simple with very few changes. > Thus if any *real* designer wants to take up the mantle, it should be very > easy for them to do so.
FWIW, 2 years ago Blaise and I worked on an effort that we, alas, never finished, to have a Pyramid-targeted landing page. I wrote/re-wrote/re-re-re-re-re-wrote some marketing copy for Pyramid. —Paul > > A page has only three basic parts. > > ======================= > Project Logo/navigation > ----------------------- > Content > ----------------------- > Pylons Project branding > ======================= > > --steve > >> What do you wonderful humans think? >> >> - sontek >> > > ------------------------ > Steve Piercy, Soquel, CA > > -- > You received this message because you are subscribed to the Google Groups > "pylons-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/pylons-discuss. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/d/optout.
