Phoenix Development

You can participate in the development of Phoenix by peering in our source code, reporting bugs and requesting new features.

Phoenix content publishing guidelines

Publishing guidelines were implemented (link) to enforce code review and to improve the quality of our website. One major goal of these guidelines is to protect the integrity and quality of the high-volume, high-profile pages of our web sites.

Please note: these guidelines exclude wiki.eclipse.org, as it is a community-driven site.

Global change

Global changes to content and look & feel must have an appropriate bug report, and require at least one +1 from a Phoenix committer.

anything inside eclipse.org-common
changes to global CSS, global nav bars, global look & feel, etc

High-impact change

Committing a high-impact change requires a corresponding bug report and at least one +1 from a Phoenix Committer.

Look & feel change to the home page (of any site)
Look & feel change to any main landing page (Community, Downloads, Projects, etc.)

Content change

Content changes do not require a bug and do not require peer review. Content scanning and spell-checking are required.

content on any page not covered by the above