Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • O org.eclipse.dash.handbook
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 156
    • Issues 156
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 2
    • Merge requests 2
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Eclipse ProjectsEclipse Projects
  • Technology
  • Eclipse Dash
  • org.eclipse.dash.handbook
  • Issues
  • #66
Closed
Open
Issue created Apr 06, 2017 by Eclipse Webmaster@webmasterOwner

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

Assignee
Assign to
Time tracking

Copyright © Eclipse Foundation, Inc. All Rights Reserved.     Privacy Policy | Terms of Use | Copyright Agent