[WORK] [IMPORTANT] [URGENT] ddox generation

[H. S. Teoh via Digitalmars-d]

On Wed, Mar 11, 2015 at 04:49:53PM +0000, Martin Nowak via Digitalmars-d wrote:
> On Wednesday, 11 March 2015 at 05:15:08 UTC, Andrei Alexandrescu wrote:
> >Google returns such links so it's important the pages look
> >professional.  Could somebody fluent with ddox get on this sooner
> >than ASAP please? This is important and urgent, even more so than a
> >blocker on the release because it's already out there.
> 
> We either have to update dpl-docs in lockstep with dlang.org or use
> separate stylesheets in dpl-docs that might lack behind to avoid this
> in future.

IMO, we really should have a staging website that is used for reviewing
changes, esp. large-scale changes like ddox, before we push it to the
official website.  This isn't the first time an embarrassing change made
it to the official website before it was caught. Each time, it causes a
mad scramble to get it fixed, and we end up adopting last-minute hack
solutions because of the time pressure rather than engineering a proper
solution from the start.

(And by staging website I don't mean somebody's personal copy of
dlang.org with proposed changes layered on top, I mean an actual,
fully-functional deployment of dlang.org that incorporates all current
PRs and polished as if it were the actual website, except that it's at a
non-official address. The official dlang.org website would be rsync'd
from this website at periodic intervals when we are confident that any
large-scale embarrassing issues have been ironed out. The staging
website would have a suitable robots.txt to prevent Google from indexing
it as official material, so that the unwary don't accidentally stumble
into it.)


T

-- 
Nothing in the world is more distasteful to a man than to take the path that leads to himself. -- Herman Hesse