Pylons can be confusing to Pyramid

[Jemes Hsu]

Pyramid is carrying a lot of old baggage. Reading about Pyramid, you are reading the history about repoze, ZOPE and Pylons and about Pylons projects. One needs to understand Pylons web framework is different from Pylons projects. There is no Pyramid branded delicate website. All these can make learning about Pyramid a bit confusing to beginners. As an example, the discussion group of Pyramid is at pylons-discussion. First "The Pylons Project was founded by the people behind the Pylons web framework to develop web application framework technology in Python." then Pylons web framework is in legacy status. Suggestion is for website to play down on topics with history, even to the extend of hiding Pylon web framework. Just want Pyramid to thrive. I'm new to Pyramid, still learning it, excited by it and will likely use it for next project. 

[Eric Ongerth]

+1 here, even from myself who had some legacy Pylons apps lying
around.

[Mike Orr]

Switched to bottom-posting to make it easier to discuss this.

On Mon, Jan 30, 2012 at 9:47 PM, Eric Ongerth <erico...@gmail.com> wrote:
> +1 here, even from myself who had some legacy Pylons apps lying
> around.

It's worth re-evaluating the issue. Pyramid has invested a lot in the
joint pylonsproject.org website. I don't think we want to rip it up to
create a separate Pyramid site. But perhaps we can adjust the wording
on the home page and the main documentation page to address this
confusion. I come from a Pylons background so I focus on documentation
for users transitioning from Pylons. Most of our initial users came
from either a Pylons or BFG background -- or they'd heard about Pylons
for years without using it -- and the first thing they want to know is
how Pyramid relates to these frameworks.

But maybe now there's a new generation of users who don't have a
either Pylons or a BFG background, who find all the history and
non-Pyramid alternatives distracting. If so... again, I don't think we
want to rip the manual and website apart to address it. But maybe the
documentation intro or a supplemental doc can start with what Pyramid
*is*, now, standalone, and then at the end mention how the
alternatives relate to it.

--
Mike Orr <slugg...@gmail.com>

[John Anderson]

But maybe now there's a new generation of users who don't have a
either Pylons or a BFG background, who find all the history and
non-Pyramid alternatives distracting. If so... again, I don't think we
want to rip the manual and website apart to address it. But maybe the
documentation intro or a supplemental doc can start with what Pyramid
*is*, now, standalone, and then at the end mention how the
alternatives relate to it.

I'm of this generation.  I haven't used or really care about anything pylons/bfg related.  Pyramid is just pyramid to me, I don't really need the history.

[Blaise Laflamme]

Next website will be Pyramid branded and be available by next pycon :)

[chandrakant kumar]

True, when i started learning pyramid, i tried to search on google and it returned results about 'egyptian pyramids'!

[Chris McDonough]

On Tue, 2012-01-31 at 11:22 +0530, chandrakant kumar wrote:
>
>
> True, when i started learning pyramid, i tried to search on google and
> it returned results about 'egyptian pyramids'!

I'd hope so!

- C

>
>
> --
> You received this message because you are subscribed to the Google
> Groups "pylons-discuss" group.
> To post to this group, send email to pylons-...@googlegroups.com.
> To unsubscribe from this group, send email to pylons-discuss
> +unsub...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/pylons-discuss?hl=en.

[Karthi]

Lol

-K

> To unsubscribe from this group, send email to pylons-discus...@googlegroups.com.

[Iain Duncan]

I concur that it's time. I have new people who I'm exposing to Pyramid and they do find it confusing and wonder "do I have to learn this Pylons stuff too?" ;-)

iain

[Jonathan Vanasco]

small request for the next website:

could the "Projects" and "Documentation" dropdowns please include
links to the "library" packages

example:

Deform lists PylonsProject.com as the homepage on PyPi (
http://pypi.python.org/pypi/deform )

If you click that link , there's no mention of it - or there existing
"library packages" - on the homepage.
If you click into the documentation link, there's no mention of it -
just a nebulous "Library Package Documentation" link.
If you click into "Library Package Documentation", then you finally
get a list of packages and link to the docs.