Describe how project websites work

Submitted by Wayne Beaton @wbeaton

Link to original bug (#514813)

Description

We don't describe how project websites work.

-- Every project gets its own website Git repository for which all project committers have push access. A scripts polls the website Git repository for changes and automatically propagates them to the site. Anything that you push to the master branch just shows up on the website after about a minute.

Consider consolidating separate related sections

https://www.eclipse.org/projects/handbook/#resources-website https://www.eclipse.org/projects/handbook/#trademarks-website https://www.eclipse.org/projects/handbook/#development-website

added Handbook bugzilla labels

Eclipse Genie @genie said:

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

-- The automated Eclipse Genie.

Wayne Beaton @wbeaton said:

Maybe something along these lines:

-- When a project is provisioned, the webmaster creates a website for the project which generally takes the form www.eclipse.org/` (exceptions are made in rare cases) with a corresponding Git repository of the form https://git.eclipse.org/c/www.eclipse.org/.git. Any content that is pushed to the Git repository will show up under www.eclipse.org/` in about a minute.

As provisioned by the webmaster, the website is configured to redirect requests to the project's PMI project page. Project teams may upload individual resources or a complete custom website. Note that the PMI provides a means for displaying links to content.

The project's website repository is not considered a project repository; it should not be listed as a source code repository in the project's PMI metadata. Further, it should not be used as a home for core project resources. The website may, for example, be used as a means of making documentation available to the community, but must not be used as a home for source files (e.g. Markdown or Asciidoc) for that documentation. As core content, documentation sources should be maintained in a code repository.