Could someone with access to the dlang.org site please rebuild and update the documentation so that it finally becomes usable (fast).

Meanwhile feel free to use http://dlang.dawg.eu.

http://d.puremagic.com/issues/show_bug.cgi?id=10903

On Friday, 6 September 2013 at 06:13:44 UTC, Martin Nowak wrote:
> Could someone with access to the dlang.org site please rebuild and update the documentation so that it finally becomes usable (fast).
>
> Meanwhile feel free to use http://dlang.dawg.eu.

Thank you for sharing this link! Much more usable than the official site.

Graham

On Friday, 6 September 2013 at 13:00:41 UTC, Graham Fawcett wrote:
> On Friday, 6 September 2013 at 06:13:44 UTC, Martin Nowak wrote:
>> Could someone with access to the dlang.org site please rebuild and update the documentation so that it finally becomes usable (fast).
>>
>> Meanwhile feel free to use http://dlang.dawg.eu.
>
> Thank you for sharing this link! Much more usable than the official site.

I may have been too hasty in complaining about the official site. I think someone rebuilt the docs, as you asked, because today it's much faster than usual.

Many thanks to you and Brad for making these improvements!

Graham

On Friday, 6 September 2013 at 06:14:49 UTC, Martin Nowak wrote:
> http://d.puremagic.com/issues/show_bug.cgi?id=10903

The real bug title should probably be "Allow more of the core development team access to upload to dlang.org".

Yourself and many others should be able to update the public website. As far as I know it's just Walter and Andrei at the moment who can do it. Right now is the perfect example of why only having two uploaders is a problem. Both of them are busy at a conference.  I believe Walter defers all the uploading to Andrei.  Trusted group of developers is larger enough that it doesn't make sense to have all of the burden and bottleneck on Andrei.

Even better, I think, would be to have the website just update automatically from git (nightly, perhaps).  Have a script that generates the website from a git tag (or even better, a branch called "public" so hotfixes can be made) and uploads it to dlang.org.  Also add preview.dlang.org which just uploads the website generated from d-p-l/{dlang.org,phobos,druntime}:master (sometimes people report bugs in the website that have already been fixed in master).

On Fri, Sep 06, 2013 at 07:29:33PM +0200, Brad Anderson wrote:
> On Friday, 6 September 2013 at 06:14:49 UTC, Martin Nowak wrote:
> >http://d.puremagic.com/issues/show_bug.cgi?id=10903
> 
> The real bug title should probably be "Allow more of the core development team access to upload to dlang.org".
> 
> Yourself and many others should be able to update the public website. As far as I know it's just Walter and Andrei at the moment who can do it. Right now is the perfect example of why only having two uploaders is a problem. Both of them are busy at a conference. I believe Walter defers all the uploading to Andrei.  Trusted group of developers is larger enough that it doesn't make sense to have all of the burden and bottleneck on Andrei.

+1 for improving our bus factor.


> Even better, I think, would be to have the website just update automatically from git (nightly, perhaps).  Have a script that generates the website from a git tag (or even better, a branch called "public" so hotfixes can be made) and uploads it to dlang.org.  Also add preview.dlang.org which just uploads the website generated from d-p-l/{dlang.org,phobos,druntime}:master (sometimes people report bugs in the website that have already been fixed in master).

+1.

It would be a good way for git HEAD users to see what the current state of the docs look like without needing to build it themselves (the current dlang.org repo introduces all kinds of dependencies on all kinds of stuff -- like latex, kindlegen, etc., that people may not have. I find myself running make -j6 several times just to coax it to build the stuff it can instead of aborting on stuff that isn't installed on my machine).


T

-- 
Frank disagreement binds closer than feigned agreement.

On Friday, 6 September 2013 at 06:13:44 UTC, Martin Nowak wrote:
> Meanwhile feel free to use http://dlang.dawg.eu.

Woah! Why is this so much faster than dlang.org?

On Fri, Sep 06, 2013 at 08:17:10PM +0200, Gary Willoughby wrote:
> On Friday, 6 September 2013 at 06:13:44 UTC, Martin Nowak wrote:
> >Meanwhile feel free to use http://dlang.dawg.eu.
> 
> Woah! Why is this so much faster than dlang.org?

If I had to guess, it's because we finally nuked hyphenate.js and hyphenate-selectively.js, both of which are big resource hogs that provide only barely-noticeable functionality.


T

-- 
Who told you to swim in Crocodile Lake without life insurance??

On 9/6/13 11:24 AM, H. S. Teoh wrote:
> On Fri, Sep 06, 2013 at 08:17:10PM +0200, Gary Willoughby wrote:
>> On Friday, 6 September 2013 at 06:13:44 UTC, Martin Nowak wrote:
>>> Meanwhile feel free to use http://dlang.dawg.eu.
>>
>> Woah! Why is this so much faster than dlang.org?
>
> If I had to guess, it's because we finally nuked hyphenate.js and
> hyphenate-selectively.js, both of which are big resource hogs that
> provide only barely-noticeable functionality.

s/barely-noticeable/awesome/

I just updated the site. Yes, we should have more people with the rights to update.


Andrei

On 2013-09-06 19:36, H. S. Teoh wrote:

> +1.
>
> It would be a good way for git HEAD users to see what the current state
> of the docs look like without needing to build it themselves (the
> current dlang.org repo introduces all kinds of dependencies on all kinds
> of stuff -- like latex, kindlegen, etc., that people may not have. I
> find myself running make -j6 several times just to coax it to build the
> stuff it can instead of aborting on stuff that isn't installed on my
> machine).

We would need some kind of versioning. One version of the site for the latest release and one for git HEAD.

-- 
/Jacob Carlborg