Hi, The design on b.a.o is horrible. :( Leaving that aside I'd like to have all our info organised on the same website. BTW, the b.a.o doesn't provide any SEO AFAICS (check view-source: https://blogs.apache.org/couchdb/entry/apache_couchdb_1_6_0).
While I agree that editing on c.a.o is simpler, why do you think that the Jekyll prototype comes with high costs? What are the steps in the proposed publishing scenario that you would deem as too difficult for a bunch of developers? Thanks, Radu On Mon, Dec 29, 2014 at 8:37 PM, Bertrand Delacretaz <[email protected] > wrote: > Have you considered using https://blogs.apache.org/ for the > blogs/news/SEO side of things that your prototype seems to cover? We > can get a blog just by asking, and we could keep the main site for > more static information (and still graft your CSS on it). > > I agree that having a single website that does it all is nice, but as > I said the cost in terms of lost ease of maintenance is high, and that > gets worse as project members come and go as is often the case in our > projects. >
