First of all, the site looks better than the old version. Congratulations and now the criticism:

I don't want to hurt anybody's feelings. But look the DMD's Image compared to GDC and LDC: http://i.imgur.com/TrnuxcB.jpg

Really looks like a joke. I would say this seems more like 90's but I have doubt if it's older than that.

Please let's go change that.

JohnCK.

On Sunday, 10 January 2016 at 22:46:34 UTC, JohnCK wrote:
> First of all, the site looks better than the old version. Congratulations and now the criticism:
>
> I don't want to hurt anybody's feelings. But look the DMD's Image compared to GDC and LDC: http://i.imgur.com/TrnuxcB.jpg
>
> Really looks like a joke. I would say this seems more like 90's but I have doubt if it's older than that.
>
> Please let's go change that.
>
> JohnCK.

It actually seems sort of fitting ; )

On 10 January 2016 at 23:46, JohnCK via Digitalmars-d < digitalmars-d@puremagic.com> wrote:

> First of all, the site looks better than the old version. Congratulations and now the criticism:
>
> I don't want to hurt anybody's feelings. But look the DMD's Image compared to GDC and LDC: http://i.imgur.com/TrnuxcB.jpg
>
> Really looks like a joke. I would say this seems more like 90's but I have doubt if it's older than that.
>
> Please let's go change that.
>
> JohnCK.
>


Don't mock D-man.  He will get you in your dreams.  :-)

On 10 January 2016 at 23:33, anonymous via Digitalmars-d < digitalmars-d@puremagic.com> wrote:

> On 10.01.2016 22:18, Iain Buclaw via Digitalmars-d wrote:
>
>> I echo this, and would add a further point that you should have tested all sub-domains before uploading.  Release archive is not looking well.
>>
>> http://downloads.dlang.org/
>>
>
> Uhm, where can I fix that? downloads.dlang.org isn't part of the of dlang.org repository, is it?
>


This is on Amazon S3.

Brad, this is your domain.  Can you have a look?  (Not sure if you monitor
your emails :-)

On Sunday, 10 January 2016 at 22:46:34 UTC, JohnCK wrote:
> First of all, the site looks better than the old version. Congratulations and now the criticism:
>
> I don't want to hurt anybody's feelings. But look the DMD's Image compared to GDC and LDC: http://i.imgur.com/TrnuxcB.jpg
>
> Really looks like a joke. I would say this seems more like 90's but I have doubt if it's older than that.
>
> Please let's go change that.
>
> JohnCK.

I kinda like it :)

It's better than that inbred bucktoothed gopher thing Go has for a mascot...it is all subjective.

bye,
lobo

On 1/10/16 4:44 PM, Martin Nowak wrote:
> On 01/10/2016 03:05 PM, anonymous wrote:
>> On 09.01.2016 22:43, Andrei Alexandrescu wrote:
>>> On 1/8/16 5:32 PM, anonymous wrote:
>> [...]
>>>> 5) Justified Text
>> [...]
>>> Justified font only looks good in conjunction with hyphenation. I'd say
>>> make text justified on browsers that support css hyphenation (all but
>>> Chrome I recall?) and left align on the others.
>>
>> I.e., revert the change. Done.
>>
>> By the way, in Ubuntu I don't see any hyphenation in Firefox. It works
>> in Windows, though.
>
> Is there a chance to pre- (ddoc) or post-process (html) our
> documentation text?
> I can offer a hyphenation tool
> (http://code.dlang.org/packages/hyphenate), but wiring it up w/ our
> dlang.org build requires some work.

Yeah, great tool Martin. I recall it was among the first on the dub repo. Would be great to hook it in and have it insert a bunch of "­"s. -- Andrei

On 1/10/16 4:46 PM, JohnCK wrote:
> On Sunday, 10 January 2016 at 21:18:46 UTC, Iain Buclaw wrote:
>> I echo this, and would add a further point that you should have tested
>> all sub-domains before uploading.  Release archive is not looking well.
>>
>> http://downloads.dlang.org/
>
> Wow. Man I don't want to be too harsh, but that was pretty lame. I
> mean... put the site on the air without testing?

We're either too quick or too slow :o). https://github.com/D-Programming-Language/dlang.org/pull/1189

Andrei

On 10.01.2016 22:14, deadalnix wrote:
>   - Learn barely make the cut on my 15' monitor. That's way too low. If
> one doesn't know D, one doesn't care about news, community or whatever.

We can shuffle things around, of course. One alternative:

Learn News
Documentation Community
Packages Contribute

http://i.imgur.com/8mQj0rg.png

This would make Learn the most prominent item.

There is an empty void between Learn and Documentation. It could be filled by putting more into Learn. I don't know what to write there, though.

This would sort of split the items in a consumer oriented left column and a contributor oriented right column. Which makes me think that I'm over-thinking this.

>   - Please don't make me click on the menus. You can also make them work
> with pure CSS using :hover

I think it was Adam who spoke out against :hover menus, preferring to click instead. So we're at 1:1 now, I guess?

On Sunday, 10 January 2016 at 22:25:50 UTC, rsw0x wrote:
> On Sunday, 10 January 2016 at 21:58:19 UTC, mate wrote:
>>> The icons are done using FontAwesome. Do the icons work on their examples page?
>>>
>>> https://fortawesome.github.io/Font-Awesome/examples/#basic
>>
>> Yes.
>>
>>> Also, what browser are you using, and what operating system?
>>
>> Firefox 43.0.3, on linux (Fedora).
>
> Your browser is probably blocking maxcdn's connection.
> Do you happen to use a host-level adblocker by chance?

Yes, you spot it! I had not noticed a separate setting in my blocker for web objects such as fonts, and their blocking was still active. I changed that setting, and it’s displaying well now.

Thank you

On Sunday, 10 January 2016 at 22:11:51 UTC, anonymous wrote:
> On 10.01.2016 19:04, Saurabh Das wrote:
>> What is the canonical way to report bugs on the website?
>
> Website bugs go into the same bug tracker as compiler and library bugs:
>
> https://issues.dlang.org/
>
> Select "dlang.org" for component.
>
OK. I'll report issues there. Will do a thorough review later this week.

>> On mobile, the red "your code here" merges with the code itself.
>
> Yeah, that's not good. I'm not sure what the best fix for this would be. Do you have anything in mind?

Move the "your code here" to next to the buttons would be a good move. Alternatively, fade out the code below and hide the "your code here" when the box is in focus.