For some reason the FAQ, install guide, and pyramid quick tutorial links are all broken at:
http://docs.pylonsproject.org/docs/pyramid.html

I think that intersphinx support needs to be added to correct a lot of the missing terminology in the pyramid docs launch page. We could also just stop using :app:Pyramid syntax there.

Pretty please? It's impossible to find every time I need to change it. It's probably not discoverable for anyone else either.

Please add current logos. Thank you!

I downloaded these PDFs, and they seem to be corrupted:

http://media.readthedocs.org/pdf/pyramid/latest/pyramid.pdf
http://media.readthedocs.org/pdf/pyramid/1.5-branch/pyramid.pdf

http://www.pylonsproject.org/ should present the organization of the Pylons Project and each of its projects' metadata.

Currently https://github.com/Pylons/pylonsrtd (rendered at http://docs.pylonsproject.org/en/latest/) and https://github.com/Pylons/pylonshq (rendered at http://www.pylonsproject.org/) is confusing, and lacks purpose and focus. The Pylons Project itself should not have any documentation. Each of its projects should have their own documentation.

I propose merging content from pylonsrtd and pylonshq into a new repo https://github.com/Pylons/pylonsprojectorg so that we satisfy the following goals.

1. Don't depend on Sphinx and RTD to build the marketing site for the PP organization.
2. Have a single place to edit the marketing site for the PP organization.
3. Use a distinguishing name for the repository that is associated to its URL.

In "Overriding a Renderer at Runtime" the example uses

from pyramid.event import subscriber
from pyramid.event import NewRequest

instead of "from pyramid.events".

It's both in the 1.3 branch and in latest:
http://docs.pylonsproject.org/projects/pyramid/en/1.3-branch/narr/renderers.html#overriding-a-renderer-at-runtime
http://docs.pylonsproject.org/projects/pyramid/en/latest/narr/renderers.html#overriding-a-renderer-at-runtime

Do the same thing that we did for pyramid_cookbook by replacing git submodule with the new pylons-sphinx-themes package.

We have marketing content in pylonsrtd (http://docs.pylonsproject.org/en/latest/) that belongs in pylonsproject.org.

The following is a complete list of reST files that need to be reviewed.

• community:
  • addons-devenvs.rst -> https://trypyramid.com/resources-extending-pyramid.html
  • codestyle.rst -> http://pylonsproject.org/community-coding-style-standards.html
  • conduct.rst -> http://pylonsproject.org/community-code-of-conduct.html
  • contributing.rst -> http://pylonsproject.org/community-how-to-contribute.html
  • featuresbugs.rst -> http://pylonsproject.org/community-how-to-participate.html
  • testing.rst -> http://pylonsproject.org/community-unit-testing-guidelines.html
• denials:
  • pyramid.rst -> https://trypyramid.com/community.html
• docs:
  • libraries.rst -> http://pylonsproject.org/projects.html
  • pylons.rst -> http://docs.pylonsproject.org/projects/pylons-webframework/en/latest/
  • pyramid.rst -> https://trypyramid.com/resources.html
• faq:
  • pylonsproject.rst -> http://pylonsproject.org/about-pylons-project.html
• glossary.rst -> Not migrating
• index.rst - Update upon completion of migration.
• podcasts.rst -> https://trypyramid.com/community.html
• promote:
  • badges.rst -> https://trypyramid.com/media.html
  • desktops.rst -> https://trypyramid.com/media.html
  • logos.rst -> https://trypyramid.com/media.html and http://pylonsproject.org/about-artwork.html
• README.rst - Update upon completion of migration.