> On 26 Oct 2015, at 10:27, Fabian Hueske <fhue...@gmail.com> wrote: > > The website consists of two parts which are maintained in two separate > respositories: > > 1) The project website about features, community, etc. > 2) The documentation of the project > > We have the separation because we want to be able to update source and > documentation in one repository to avoid that the documentation gets out of > sync. The documentation is built every night and hosted at ci.apache.org to > achieve that. > > IMO, this separation makes sense, because the project website is not > changed very often whereas the documentation should be touched whenever the > API or behavior is changed. I think it is very important to have > documentation in sync with the code. In fact, I believe both parts of the > website should not be related to each other, so they shouldn't be a way to > have both parts getting out-of-sync, except for layout / design which is > nice to have but not crucial. We might even think about changing the > color-scheme of the documentation to make the difference more clear.
Yes, Max pointed this out in the beginning. Let’s change the colors/design to make the distinction clear. The confusion comes from the fact that they look similar. It only makes sense to assume that they are hosted on the same web server etc. But as Fabian said, there are good reasons against it. – Ufuk
