Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:

Take a look at http://dlang.org. New menus are in place for the main 
site and library.

I think we're in a better place than before. However, there are a few 
things left to do. I'd very much appreciate help with those.

* New docs don't yet have the new menu implemented.

* Menu tracking works, i.e. if the URL a page matches a menu entry, then 
the menu will automatically open to that page and mark the entry active. 
However, that's rather simplistic; for example navigating 
http://dlang.org/statement.html does not open the "Documentation" menu 
because the link is not directly present.

A simple and probably desirable fix would be to just make "Language 
Reference" a top-level menu entry with submenus. Could one of our 
awesome lieutenants see to it?

* Better colors etc. are always welcome. Please submit your pull 
requests with screenshots so we can appreciate.


Thanks,

Andrei

Rikki Cattermole <alphaglosined gmail.com> writes:

On 20/01/2015 4:29 p.m., Andrei Alexandrescu wrote:
 Take a look at http://dlang.org. New menus are in place for the main
 site and library.

 I think we're in a better place than before. However, there are a few
 things left to do. I'd very much appreciate help with those.

 * New docs don't yet have the new menu implemented.

 * Menu tracking works, i.e. if the URL a page matches a menu entry, then
 the menu will automatically open to that page and mark the entry active.
 However, that's rather simplistic; for example navigating
 http://dlang.org/statement.html does not open the "Documentation" menu
 because the link is not directly present.

 A simple and probably desirable fix would be to just make "Language
 Reference" a top-level menu entry with submenus. Could one of our
 awesome lieutenants see to it?

 * Better colors etc. are always welcome. Please submit your pull
 requests with screenshots so we can appreciate.


 Thanks,

 Andrei

Say ugh, when was the last time somebody clicked the ol' "Page wiki" 
buttons.
Because atleast for intro, it doesn't exist.

Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:

On 1/19/15 7:32 PM, Rikki Cattermole wrote:
 Say ugh, when was the last time somebody clicked the ol' "Page wiki"
 buttons.
 Because atleast for intro, it doesn't exist.

Ah, it was part of the topics I wanted to touch. Looks like page wikis 
are largely unused, should we just ditch them?


Andrei

Rikki Cattermole <alphaglosined gmail.com> writes:

On 20/01/2015 4:34 p.m., Andrei Alexandrescu wrote:
 On 1/19/15 7:32 PM, Rikki Cattermole wrote:
 Say ugh, when was the last time somebody clicked the ol' "Page wiki"
 buttons.
 Because atleast for intro, it doesn't exist.

 Ah, it was part of the topics I wanted to touch. Looks like page wikis
 are largely unused, should we just ditch them?


 Andrei

Yes please.
If we feel the need to link/reference them on a page to page basis, we can.

I would also recommend the page edit button. Switch it for a 'fork me' 
github ribbon [0].

[0] https://github.com/blog/273-github-ribbons

Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:

On 1/19/15 7:36 PM, Rikki Cattermole wrote:
 On 20/01/2015 4:34 p.m., Andrei Alexandrescu wrote:
 On 1/19/15 7:32 PM, Rikki Cattermole wrote:
 Say ugh, when was the last time somebody clicked the ol' "Page wiki"
 buttons.
 Because atleast for intro, it doesn't exist.

 Ah, it was part of the topics I wanted to touch. Looks like page wikis
 are largely unused, should we just ditch them?


 Andrei

 Yes please.
 If we feel the need to link/reference them on a page to page basis, we can.

 I would also recommend the page edit button. Switch it for a 'fork me'
 github ribbon [0].

 [0] https://github.com/blog/273-github-ribbons

This was up for a little while, then it was pulled because of reasons I 
don't remember. Or at least talked about. -- Andrei

Rikki Cattermole <alphaglosined gmail.com> writes:

On 20/01/2015 4:37 p.m., Andrei Alexandrescu wrote:
 On 1/19/15 7:36 PM, Rikki Cattermole wrote:
 On 20/01/2015 4:34 p.m., Andrei Alexandrescu wrote:
 On 1/19/15 7:32 PM, Rikki Cattermole wrote:
 Say ugh, when was the last time somebody clicked the ol' "Page wiki"
 buttons.
 Because atleast for intro, it doesn't exist.

 Ah, it was part of the topics I wanted to touch. Looks like page wikis
 are largely unused, should we just ditch them?


 Andrei

 Yes please.
 If we feel the need to link/reference them on a page to page basis, we
 can.

 I would also recommend the page edit button. Switch it for a 'fork me'
 github ribbon [0].

 [0] https://github.com/blog/273-github-ribbons

 This was up for a little while, then it was pulled because of reasons I
 don't remember. Or at least talked about. -- Andrei

That would have been before my time then.
I can understand it would interfere with twitter/mobile and pdf ext. 
generation.

The only reason I suggest it is because it is what people expect these 
days. And would advertise that we are passionately open source.

Rikki Cattermole <alphaglosined gmail.com> writes:

On 20/01/2015 4:40 p.m., Rikki Cattermole wrote:
 On 20/01/2015 4:37 p.m., Andrei Alexandrescu wrote:
 On 1/19/15 7:36 PM, Rikki Cattermole wrote:
 On 20/01/2015 4:34 p.m., Andrei Alexandrescu wrote:
 On 1/19/15 7:32 PM, Rikki Cattermole wrote:
 Say ugh, when was the last time somebody clicked the ol' "Page wiki"
 buttons.
 Because atleast for intro, it doesn't exist.

 Ah, it was part of the topics I wanted to touch. Looks like page wikis
 are largely unused, should we just ditch them?


 Andrei

 Yes please.
 If we feel the need to link/reference them on a page to page basis, we
 can.

 I would also recommend the page edit button. Switch it for a 'fork me'
 github ribbon [0].

 [0] https://github.com/blog/273-github-ribbons

 This was up for a little while, then it was pulled because of reasons I
 don't remember. Or at least talked about. -- Andrei

 That would have been before my time then.
 I can understand it would interfere with twitter/mobile and pdf ext.
 generation.

 The only reason I suggest it is because it is what people expect these
 days. And would advertise that we are passionately open source.

I've just tested this client side. Using [0] ribbon implementation.
And the effect it causes [1]. No real interference. Its nice.

[0] https://github.com/simonwhitaker/github-fork-ribbon-css
[1] 
https://drive.google.com/file/d/0B-EiBquZktsLXzZqdkFoWnZ4ZUk/view?usp=sharing

P.S. I've messaged you Andrei. Slight problem with twitter api usage. 
(http connection vs twitter specified by https).

"Vladimir Panteleev" <vladimir thecybershadow.net> writes:

On Tuesday, 20 January 2015 at 03:37:17 UTC, Andrei Alexandrescu 
wrote:
 On 1/19/15 7:36 PM, Rikki Cattermole wrote:
 On 20/01/2015 4:34 p.m., Andrei Alexandrescu wrote:
 On 1/19/15 7:32 PM, Rikki Cattermole wrote:
 Say ugh, when was the last time somebody clicked the ol' 
 "Page wiki"
 buttons.
 Because atleast for intro, it doesn't exist.

 Ah, it was part of the topics I wanted to touch. Looks like 
 page wikis
 are largely unused, should we just ditch them?


 Andrei

 Yes please.
 If we feel the need to link/reference them on a page to page 
 basis, we can.

 I would also recommend the page edit button. Switch it for a 
 'fork me'
 github ribbon [0].

 [0] https://github.com/blog/273-github-ribbons

 This was up for a little while, then it was pulled because of 
 reasons I don't remember. Or at least talked about. -- Andrei

We still have it for the download page:

http://dlang.org/download.html

"Vladimir Panteleev" <vladimir thecybershadow.net> writes:

On Tuesday, 20 January 2015 at 03:32:38 UTC, Rikki Cattermole 
wrote:
 Say ugh, when was the last time somebody clicked the ol' "Page 
 wiki" buttons.
 Because atleast for intro, it doesn't exist.

They don't need to all exist. The idea is to link to a page that 
anyone can create, and then anyone else can get to by clicking 
the same link in the page header.

Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:

On 1/19/15 7:34 PM, Vladimir Panteleev wrote:
 On Tuesday, 20 January 2015 at 03:32:38 UTC, Rikki Cattermole wrote:
 Say ugh, when was the last time somebody clicked the ol' "Page wiki"
 buttons.
 Because atleast for intro, it doesn't exist.

 They don't need to all exist. The idea is to link to a page that anyone
 can create, and then anyone else can get to by clicking the same link in
 the page header.

I fear that newcomers finding many of those page unpopulated would think 
there's no activity etc. -- Andrei

Rikki Cattermole <alphaglosined gmail.com> writes:

On 20/01/2015 4:36 p.m., Andrei Alexandrescu wrote:
 On 1/19/15 7:34 PM, Vladimir Panteleev wrote:
 On Tuesday, 20 January 2015 at 03:32:38 UTC, Rikki Cattermole wrote:
 Say ugh, when was the last time somebody clicked the ol' "Page wiki"
 buttons.
 Because atleast for intro, it doesn't exist.

 They don't need to all exist. The idea is to link to a page that anyone
 can create, and then anyone else can get to by clicking the same link in
 the page header.

 I fear that newcomers finding many of those page unpopulated would think
 there's no activity etc. -- Andrei

Lets be honest here. If changes need to occur to those pages, they get 
PR'd and fixed.
They don't get discussed on the wiki. They'll get discussed on the N.G.

So I'm 100% in agreement with Andrei, it'll cause more problems then its 
worth. Plus it makes it look like its a CMS, no thanks.. its not.

"Vladimir Panteleev" <vladimir thecybershadow.net> writes:

On Tuesday, 20 January 2015 at 03:36:16 UTC, Andrei Alexandrescu 
wrote:
 On 1/19/15 7:34 PM, Vladimir Panteleev wrote:
 On Tuesday, 20 January 2015 at 03:32:38 UTC, Rikki Cattermole 
 wrote:
 Say ugh, when was the last time somebody clicked the ol' 
 "Page wiki"
 buttons.
 Because atleast for intro, it doesn't exist.

 They don't need to all exist. The idea is to link to a page 
 that anyone
 can create, and then anyone else can get to by clicking the 
 same link in
 the page header.

 I fear that newcomers finding many of those page unpopulated 
 would think there's no activity etc. -- Andrei

I could run a script to populate them with a placeholder.

These pages were numerous on the old wiki, and although we could 
look into migrating them, most information is likely outdated by 
now.

Rikki Cattermole <alphaglosined gmail.com> writes:

On 21/01/2015 5:30 a.m., Vladimir Panteleev wrote:
 On Tuesday, 20 January 2015 at 03:36:16 UTC, Andrei Alexandrescu wrote:
 On 1/19/15 7:34 PM, Vladimir Panteleev wrote:
 On Tuesday, 20 January 2015 at 03:32:38 UTC, Rikki Cattermole wrote:
 Say ugh, when was the last time somebody clicked the ol' "Page wiki"
 buttons.
 Because atleast for intro, it doesn't exist.

 They don't need to all exist. The idea is to link to a page that anyone
 can create, and then anyone else can get to by clicking the same link in
 the page header.

 I fear that newcomers finding many of those page unpopulated would
 think there's no activity etc. -- Andrei

 I could run a script to populate them with a placeholder.

 These pages were numerous on the old wiki, and although we could look
 into migrating them, most information is likely outdated by now.

Even if they get created with a stub, its not really adding anything.
De clutter the design and remove them.

In my entire time in the community, I haven't heard about these buttons 
ever being used, let alone referred to.

Worse case scenario, we find out we need them for a few pages. We can 
add some links in the text. No biggy.

Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:

... aand we already have a contender!

https://github.com/D-Programming-Language/dlang.org/pull/790

Looks better than dlang.org?


Andrei

"Jonas Drewsen" <nospam4321 hotmail.com > writes:

On Tuesday, 20 January 2015 at 03:33:19 UTC, Andrei Alexandrescu 
wrote:
 ... aand we already have a contender!

 https://github.com/D-Programming-Language/dlang.org/pull/790

 Looks better than dlang.org?

Yeah definitely... better colors and spacing.

"Chris" <wendlec tcd.ie> writes:

On Tuesday, 20 January 2015 at 08:13:56 UTC, Jonas Drewsen wrote:
 On Tuesday, 20 January 2015 at 03:33:19 UTC, Andrei 
 Alexandrescu wrote:
 ... aand we already have a contender!

 https://github.com/D-Programming-Language/dlang.org/pull/790

 Looks better than dlang.org?

 Yeah definitely... better colors and spacing.

Yes, the colors should be changed. The  skinny white letters on 
the reddish-brown background are highly irritating. The suggested 
color scheme looks much better and is easier to read.

Also, a minor improvement would be to make the block with the 
menu items as wide as the block with the compiler/D version 
that's above it. I think the difference in size is caused by the 
red border around the menu block (which is not really necessary. 
(I think the width of the elements is in sync in the suggestion 
linked to above).

"MattCoder" <stop spam.com> writes:

On Tuesday, 20 January 2015 at 03:29:23 UTC, Andrei Alexandrescu 
wrote:
 Take a look at http://dlang.org. New menus are in place for the 
 main site and library.

Well let be honest the site was in need of some fresh air. And 
the new menu is really good. Congratulations.

Matheus.

Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:

On 1/19/15 7:51 PM, MattCoder wrote:
 On Tuesday, 20 January 2015 at 03:29:23 UTC, Andrei Alexandrescu wrote:
 Take a look at http://dlang.org. New menus are in place for the main
 site and library.

 Well let be honest the site was in need of some fresh air. And the new
 menu is really good. Congratulations.

Thanks! Well it's probably time to start talking content, too. 
https://github.com/D-Programming-Language/dlang.org/pull/792/.

Andrei

"Phil" <phil.j.ellison gmail.com> writes:

Pull 790 would be a big improvement . The current page also 
doesn't seem to be working properly. The right margin is empty 
except for a link to the D Twitter feed at the very top. I assume 
there's supposed to be a widget there showing tweets like before 
(although I never liked that).


On Tuesday, 20 January 2015 at 04:03:23 UTC, Andrei Alexandrescu 
wrote:
 On 1/19/15 7:51 PM, MattCoder wrote:
 On Tuesday, 20 January 2015 at 03:29:23 UTC, Andrei 
 Alexandrescu wrote:
 Take a look at http://dlang.org. New menus are in place for 
 the main
 site and library.

 Well let be honest the site was in need of some fresh air. And 
 the new
 menu is really good. Congratulations.

 Thanks! Well it's probably time to start talking content, too. 
 https://github.com/D-Programming-Language/dlang.org/pull/792/.

 Andrei

"Vladimir Panteleev" <vladimir thecybershadow.net> writes:

On Tuesday, 20 January 2015 at 07:21:31 UTC, Phil wrote:
 Pull 790 would be a big improvement . The current page also 
 doesn't seem to be working properly. The right margin is empty 
 except for a link to the D Twitter feed at the very top. I 
 assume there's supposed to be a widget there showing tweets 
 like before (although I never liked that).

Perhaps an ad blocker or something similar is preventing it from 
showing up in your browser?

See if it works in a different browser.

"Zach the Mystic" <reachzach gggmail.com> writes:

On Tuesday, 20 January 2015 at 04:03:23 UTC, Andrei Alexandrescu 
wrote:
 Thanks! Well it's probably time to start talking content, too.

 Andrei

Quick suggestion: The twitter feed takes up more screen space 
than it's worth, IMO. I think the same amount of space should be 
taken up by a more general (though not explicitly marked) 
"Dynamic Content" section, including:

* a headline or two from latest forum discussions (possibly 
filtered by some heuristic), with a link to the forums
* link the latest issue of This Week in D
* the latest tweet, with links to more tweets

Longer lived dynamic content, such as links to the conference, 
should still feature prominently, of course.

Should I make an enhancement request?

Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:

On 1/20/15 12:10 PM, Zach the Mystic wrote:
 On Tuesday, 20 January 2015 at 04:03:23 UTC, Andrei Alexandrescu wrote:
 Thanks! Well it's probably time to start talking content, too.

 Andrei

 Quick suggestion: The twitter feed takes up more screen space than it's
 worth, IMO. I think the same amount of space should be taken up by a
 more general (though not explicitly marked) "Dynamic Content" section,
 including:

 * a headline or two from latest forum discussions (possibly filtered by
 some heuristic), with a link to the forums
 * link the latest issue of This Week in D
 * the latest tweet, with links to more tweets

 Longer lived dynamic content, such as links to the conference, should
 still feature prominently, of course.

 Should I make an enhancement request?

Yes please. I've already talked to Vladimir about some forum 
integration. -- Andrei

"Zach the Mystic" <reachzach gggmail.com> writes:

On Tuesday, 20 January 2015 at 21:42:52 UTC, Andrei Alexandrescu 
wrote:
 On 1/20/15 12:10 PM, Zach the Mystic wrote:
 Quick suggestion: The twitter feed takes up more screen space 
 than it's
 worth, IMO. I think the same amount of space should be taken 
 up by a
 more general (though not explicitly marked) "Dynamic Content" 
 section,
 including:

 * a headline or two from latest forum discussions (possibly 
 filtered by
 some heuristic), with a link to the forums
 * link the latest issue of This Week in D
 * the latest tweet, with links to more tweets

 Longer lived dynamic content, such as links to the conference, 
 should
 still feature prominently, of course.

 Should I make an enhancement request?

 Yes please. I've already talked to Vladimir about some forum 
 integration. -- Andrei

https://issues.dlang.org/show_bug.cgi?id=14019

"Vladimir Panteleev" <vladimir thecybershadow.net> writes:

On Tuesday, 20 January 2015 at 21:42:52 UTC, Andrei Alexandrescu 
wrote:
 On 1/20/15 12:10 PM, Zach the Mystic wrote:
 On Tuesday, 20 January 2015 at 04:03:23 UTC, Andrei 
 Alexandrescu wrote:
 Thanks! Well it's probably time to start talking content, too.

 Andrei

 Quick suggestion: The twitter feed takes up more screen space 
 than it's
 worth, IMO. I think the same amount of space should be taken 
 up by a
 more general (though not explicitly marked) "Dynamic Content" 
 section,
 including:

 * a headline or two from latest forum discussions (possibly 
 filtered by
 some heuristic), with a link to the forums
 * link the latest issue of This Week in D
 * the latest tweet, with links to more tweets

 Longer lived dynamic content, such as links to the conference, 
 should
 still feature prominently, of course.

 Should I make an enhancement request?

 Yes please. I've already talked to Vladimir about some forum 
 integration. -- Andrei

https://github.com/D-Programming-Language/dlang.org/pull/815

"Zach the Mystic" <reachzach gggmail.com> writes:

On Tuesday, 20 January 2015 at 04:03:23 UTC, Andrei Alexandrescu 
wrote:
 Well let be honest the site was in need of some fresh air. And 
 the new
 menu is really good. Congratulations.

 Thanks! Well it's probably time to start talking content, too.

Here's another guiding thought. The site should self-consciously 
address the needs of the following 4 user demographics:

1. Experienced programmers, new to D. This section contains 
introductory material explaining D's mission or missions.

2. Beginning programmers. Material that treats D as possibly a 
first language.

3. Experienced D users. Reference materials. Important new facts.

4. The community. Publications, social events, news chatter.

Decide on the relative importance of the different demographics 
(I listed them in my personal order). For each given box or 
button, determine which demographic(s) are served. Group items 
together accordingly.

Steven Schveighoffer <schveiguy yahoo.com> writes:

On 1/19/15 10:29 PM, Andrei Alexandrescu wrote:
 Take a look at http://dlang.org. New menus are in place for the main
 site and library.

 I think we're in a better place than before. However, there are a few
 things left to do. I'd very much appreciate help with those.

 * New docs don't yet have the new menu implemented.

 * Menu tracking works, i.e. if the URL a page matches a menu entry, then
 the menu will automatically open to that page and mark the entry active.
 However, that's rather simplistic; for example navigating
 http://dlang.org/statement.html does not open the "Documentation" menu
 because the link is not directly present.

 A simple and probably desirable fix would be to just make "Language
 Reference" a top-level menu entry with submenus. Could one of our
 awesome lieutenants see to it?

 * Better colors etc. are always welcome. Please submit your pull
 requests with screenshots so we can appreciate.

Looks excellent!

3 issues:

1. when browsing the library, the rest of the menu disappears (i.e. the 
rest of the menu is gone). You can click on the "D Lib 2.066.1" menu at 
the top to get back, but it's not obvious. There should at least be a 
"back" or "home" button in that menu.
2. Some of the library expansions don't fit into the column (e.g. 
std.windows.charset).
3. When I expand one section, the existing expanded section collapses. I 
hate this. First, if I want all of them open, I can't do that (this may 
be important on the library navigation). Second, if you have a large 
expanded section open, and you expand a smaller section that is below 
it, it sucks the menu back up above the screen, making you have to 
scroll up. For example, try opening std, then open core. To open core, 
you have to scroll way down. As soon as you open it, the menu gets 
sucked away.

I know your response will be "awaiting your PR" :) I'll try and see if I 
can fix at least the expansion problem.

The menu is a huge HUGE improvement, the old one was too subtle.

-Steve

Steven Schveighoffer <schveiguy yahoo.com> writes:

On 1/20/15 7:36 AM, Steven Schveighoffer wrote:

 I know your response will be "awaiting your PR" :) I'll try and see if I
 can fix at least the expansion problem.

https://github.com/D-Programming-Language/dlang.org/pull/800

-Steve

Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:

On 1/20/15 5:25 AM, Steven Schveighoffer wrote:
 On 1/20/15 7:36 AM, Steven Schveighoffer wrote:

 I know your response will be "awaiting your PR" :) I'll try and see if I
 can fix at least the expansion problem.

 https://github.com/D-Programming-Language/dlang.org/pull/800

I figured if I wanted to go to "core" when "std" is open I wouldn't 
scroll down to find it; I'd just first close the longer menu then expand 
the shorter one.

But no matter. Let's see how this goes. I've merged 800 and pushed the 
new site. Thanks, and all please let us know how it works!


Andrei

Steven Schveighoffer <schveiguy yahoo.com> writes:

On 1/20/15 11:43 AM, Andrei Alexandrescu wrote:
 On 1/20/15 5:25 AM, Steven Schveighoffer wrote:
 On 1/20/15 7:36 AM, Steven Schveighoffer wrote:

 I know your response will be "awaiting your PR" :) I'll try and see if I
 can fix at least the expansion problem.

 https://github.com/D-Programming-Language/dlang.org/pull/800

 I figured if I wanted to go to "core" when "std" is open I wouldn't
 scroll down to find it; I'd just first close the longer menu then expand
 the shorter one.

The use case is probably more like you are down on the std.datetime page 
reading some function signature, then realize that what you really need 
is core.time, so you scroll up until you see the "core" expander, and 
click on it.

Just as a user experience general observation, I should not be able to 
click on something to see what's inside, and have it run away from 
sight, even if that's not the "right way" to do it.

In any case, I see the changes and appreciate the result! Thanks.

-Steve

"Ola Fosheim =?UTF-8?B?R3LDuHN0YWQi?= writes:

On Tuesday, 20 January 2015 at 16:43:43 UTC, Andrei Alexandrescu 
wrote:
 pushed the new site. Thanks, and all please let us know how it 
 works!

Library menu usability issues

1. "prerelease" button should look like a toggle button or 
similar. It changes the main context and is on a different level 
than the other buttons (like a subsite). It should also not 
change size.

2. "object" does not show that it is selected.

3.  Menu item labels are too wide. You need to add set the 
overflow to hidden/ellipsis, but that will make the most 
important portion of the name invisible. So you need to right 
align when needed or change the visuals.

4. "3rd party packages" does not show visually that it points to 
an external site. That's visually deceptive.

And the visuals need more work. :)

"Vladimir Panteleev" <vladimir thecybershadow.net> writes:

On Tuesday, 20 January 2015 at 23:21:48 UTC, Ola Fosheim Grøstad 
wrote:
 4. "3rd party packages" does not show visually that it points 
 to an external site. That's visually deceptive.

Maybe we can instead get code.dlang.org to use the dlang.org 
theme and menu :)

"Ola Fosheim =?UTF-8?B?R3LDuHN0YWQi?= writes:

On Tuesday, 20 January 2015 at 23:23:25 UTC, Vladimir Panteleev 
wrote:
 On Tuesday, 20 January 2015 at 23:21:48 UTC, Ola Fosheim 
 Grøstad wrote:
 4. "3rd party packages" does not show visually that it points 
 to an external site. That's visually deceptive.

 Maybe we can instead get code.dlang.org to use the dlang.org 
 theme and menu :)

;) And then it makes sense to put all those sub-site buttons as a 
task bar on the top. With a visual marker that shows which 
sub-site the current page belongs to.

Steven Schveighoffer <schveiguy yahoo.com> writes:

On 1/20/15 6:21 PM, "Ola Fosheim =?UTF-8?B?R3LDuHN0YWQi?= 
<ola.fosheim.grostad+dlang gmail.com>" wrote:

 3.  Menu item labels are too wide. You need to add set the overflow to
 hidden/ellipsis, but that will make the most important portion of the
 name invisible. So you need to right align when needed or change the
 visuals.

Hm.. what about:

std
   algorithm

instead of:

std
   std.algorithm

-Steve

"H. S. Teoh via Digitalmars-d" <digitalmars-d puremagic.com> writes:

On Tue, Jan 20, 2015 at 10:19:00PM -0500, Steven Schveighoffer via
Digitalmars-d wrote:
 On 1/20/15 6:21 PM, "Ola Fosheim =?UTF-8?B?R3LDuHN0YWQi?=
 <ola.fosheim.grostad+dlang gmail.com>" wrote:
 
3.  Menu item labels are too wide. You need to add set the overflow
to hidden/ellipsis, but that will make the most important portion of
the name invisible. So you need to right align when needed or change
the visuals.

 
 Hm.. what about:
 
 std
   algorithm
 
 instead of:
 
 std
   std.algorithm

[...]

Also, std.range.package -- shouldn't it be simply std.range (without the
.package)? I thought package.d was supposed to be a transparent way to
support importing an entire package, which should be an implementation
detail, not something shown prominently to the user.


T

-- 
Ruby is essentially Perl minus Wall.

Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:

On 1/20/15 10:26 PM, H. S. Teoh via Digitalmars-d wrote:
 On Tue, Jan 20, 2015 at 10:19:00PM -0500, Steven Schveighoffer via
Digitalmars-d wrote:
 On 1/20/15 6:21 PM, "Ola Fosheim =?UTF-8?B?R3LDuHN0YWQi?=
 <ola.fosheim.grostad+dlang gmail.com>" wrote:

 3.  Menu item labels are too wide. You need to add set the overflow
 to hidden/ellipsis, but that will make the most important portion of
 the name invisible. So you need to right align when needed or change
 the visuals.

 Hm.. what about:

 std
    algorithm

 instead of:

 std
    std.algorithm

 [...]

 Also, std.range.package -- shouldn't it be simply std.range (without the
 .package)? I thought package.d was supposed to be a transparent way to
 support importing an entire package, which should be an implementation
 detail, not something shown prominently to the user.

Made my job easier... yah, we should do one more pass to clean stuff up. 
-- Andrei

Steven Schveighoffer <schveiguy yahoo.com> writes:

On 1/19/15 10:29 PM, Andrei Alexandrescu wrote:
 * New docs don't yet have the new menu implemented.

Also forums.

-Steve

"Vladimir Panteleev" <vladimir thecybershadow.net> writes:

On Tuesday, 20 January 2015 at 13:44:09 UTC, Steven Schveighoffer 
wrote:
 On 1/19/15 10:29 PM, Andrei Alexandrescu wrote:
 * New docs don't yet have the new menu implemented.

 Also forums.

I'll get to that once the design stabilizes.

"Ola Fosheim =?UTF-8?B?R3LDuHN0YWQi?= writes:

They are a usability disaster. Try click on "std" then on "etc". 
The menu disappears due to "std" being long.

Steven Schveighoffer <schveiguy yahoo.com> writes:

On 1/20/15 9:25 AM, "Ola Fosheim =?UTF-8?B?R3LDuHN0YWQi?= 
<ola.fosheim.grostad+dlang gmail.com>" wrote:
 They are a usability disaster. Try click on "std" then on "etc". The
 menu disappears due to "std" being long.

Heh, just wrote about that.

https://github.com/D-Programming-Language/dlang.org/pull/800

-Steve

"bearophile" <bearophileHUGS lycos.com> writes:

Andrei Alexandrescu:

 I think we're in a better place than before.

If the browser detects no JavaScript it can present a simpler 
alternative but usable menu.

Bye,
bearophile

"Vladimir Panteleev" <vladimir thecybershadow.net> writes:

On Tuesday, 20 January 2015 at 15:41:30 UTC, bearophile wrote:
 Andrei Alexandrescu:

 I think we're in a better place than before.

 If the browser detects no JavaScript it can present a simpler 
 alternative but usable menu.

All expandable sections should show up as expanded when no JS is
available.

"bearophile" <bearophileHUGS lycos.com> writes:

Vladimir Panteleev:

 All expandable sections should show up as expanded when no JS is
 available.

But currently they aren't doing that, right?

Bye,
bearophile

"Vladimir Panteleev" <vladimir thecybershadow.net> writes:

On Tuesday, 20 January 2015 at 16:31:12 UTC, bearophile wrote:
 Vladimir Panteleev:

 All expandable sections should show up as expanded when no JS 
 is
 available.

 But currently they aren't doing that, right?

They are. It is working for me when I disable JS in Firefox (via 
about:config).

If it doesn't work for you, how can I reproduce the problem?

"bearophile" <bearophileHUGS lycos.com> writes:

Vladimir Panteleev:

 If it doesn't work for you, how can I reproduce the problem?

Today browsers are terribly complex, there's little hope to 
reproduce an environment. So never mind, ignore my precedent 
comment...

Bye,
bearophile

Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:

On 1/20/15 8:33 AM, Vladimir Panteleev wrote:
 On Tuesday, 20 January 2015 at 16:31:12 UTC, bearophile wrote:
 Vladimir Panteleev:

 All expandable sections should show up as expanded when no JS is
 available.

 But currently they aren't doing that, right?

 They are. It is working for me when I disable JS in Firefox (via
 about:config).

 If it doesn't work for you, how can I reproduce the problem?

There was a bug for a while that hid everything. Might be a matter of 
refreshing. -- Andrei

"Kiith-Sa" <kiithsacmp gmail.com> writes:

On Tuesday, 20 January 2015 at 16:33:43 UTC, Vladimir Panteleev 
wrote:
 On Tuesday, 20 January 2015 at 16:31:12 UTC, bearophile wrote:
 Vladimir Panteleev:

 All expandable sections should show up as expanded when no JS 
 is
 available.

 But currently they aren't doing that, right?

 They are. It is working for me when I disable JS in Firefox 
 (via about:config).

 If it doesn't work for you, how can I reproduce the problem?

It's broken with NoScript if dlang.org is allowed but 
ajax.googleapis.com is disallowed.

Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:

On 1/20/15 8:46 AM, Kiith-Sa wrote:
 On Tuesday, 20 January 2015 at 16:33:43 UTC, Vladimir Panteleev wrote:
 On Tuesday, 20 January 2015 at 16:31:12 UTC, bearophile wrote:
 Vladimir Panteleev:

 All expandable sections should show up as expanded when no JS is
 available.

 But currently they aren't doing that, right?

 They are. It is working for me when I disable JS in Firefox (via
 about:config).

 If it doesn't work for you, how can I reproduce the problem?

 It's broken with NoScript if dlang.org is allowed but
 ajax.googleapis.com is disallowed.

We have a bug report from China where google is blocked. Any other point 
we can load jQuery from? -- Andrei

"Vladimir Panteleev" <vladimir thecybershadow.net> writes:

On Tuesday, 20 January 2015 at 19:11:45 UTC, Andrei Alexandrescu 
wrote:
 On 1/20/15 8:46 AM, Kiith-Sa wrote:
 On Tuesday, 20 January 2015 at 16:33:43 UTC, Vladimir 
 Panteleev wrote:
 On Tuesday, 20 January 2015 at 16:31:12 UTC, bearophile wrote:
 Vladimir Panteleev:

 All expandable sections should show up as expanded when no 
 JS is
 available.

 But currently they aren't doing that, right?

 They are. It is working for me when I disable JS in Firefox 
 (via
 about:config).

 If it doesn't work for you, how can I reproduce the problem?

 It's broken with NoScript if dlang.org is allowed but
 ajax.googleapis.com is disallowed.

 We have a bug report from China where google is blocked. Any 
 other point we can load jQuery from? -- Andrei

Yes, the jQuery CDN, or locally.

Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:

On 1/20/15 7:41 AM, bearophile wrote:
 Andrei Alexandrescu:

 I think we're in a better place than before.

 If the browser detects no JavaScript it can present a simpler
 alternative but usable menu.

Yah, it leaves all submenus open. -- Andrei

"ixid" <adamsibson hotmail.com> writes:

On Tuesday, 20 January 2015 at 03:29:23 UTC, Andrei Alexandrescu 
wrote:
 Take a look at http://dlang.org. New menus are in place for the 
 main site and library.

The site is a mess on mobile, a squashed central column and 
overlapping UI elements that aren't meant to.

"Vladimir Panteleev" <vladimir thecybershadow.net> writes:

On Tuesday, 20 January 2015 at 22:49:27 UTC, ixid wrote:
 On Tuesday, 20 January 2015 at 03:29:23 UTC, Andrei 
 Alexandrescu wrote:
 Take a look at http://dlang.org. New menus are in place for 
 the main site and library.

 The site is a mess on mobile, a squashed central column and 
 overlapping UI elements that aren't meant to.

I'll see what I can do to improve the site on small screens.

"Vladimir Panteleev" <vladimir thecybershadow.net> writes:

On Tuesday, 20 January 2015 at 23:49:26 UTC, Vladimir Panteleev 
wrote:
 On Tuesday, 20 January 2015 at 22:49:27 UTC, ixid wrote:
 On Tuesday, 20 January 2015 at 03:29:23 UTC, Andrei 
 Alexandrescu wrote:
 Take a look at http://dlang.org. New menus are in place for 
 the main site and library.

 The site is a mess on mobile, a squashed central column and 
 overlapping UI elements that aren't meant to.

 I'll see what I can do to improve the site on small screens.

WIP:

http://dump.thecybershadow.net/0ab998c7f4e2027fed300de718a4a058/0000013E.png

The hamburger icon will open a side menu, like on Wikipedia and 
YouTube.
The looking glass icon will show a search bar.

Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:

On 1/20/15 4:22 PM, Vladimir Panteleev wrote:
 On Tuesday, 20 January 2015 at 23:49:26 UTC, Vladimir Panteleev wrote:
 On Tuesday, 20 January 2015 at 22:49:27 UTC, ixid wrote:
 On Tuesday, 20 January 2015 at 03:29:23 UTC, Andrei Alexandrescu wrote:
 Take a look at http://dlang.org. New menus are in place for the main
 site and library.

 The site is a mess on mobile, a squashed central column and
 overlapping UI elements that aren't meant to.

 I'll see what I can do to improve the site on small screens.

 WIP:

 http://dump.thecybershadow.net/0ab998c7f4e2027fed300de718a4a058/0000013E.png


 The hamburger icon will open a side menu, like on Wikipedia and YouTube.
 The looking glass icon will show a search bar.

Niiiice... -- Andrei

"Vladimir Panteleev" <vladimir thecybershadow.net> writes:

On Wednesday, 21 January 2015 at 00:45:11 UTC, Andrei 
Alexandrescu wrote:
 On 1/20/15 4:22 PM, Vladimir Panteleev wrote:
 On Tuesday, 20 January 2015 at 23:49:26 UTC, Vladimir 
 Panteleev wrote:
 On Tuesday, 20 January 2015 at 22:49:27 UTC, ixid wrote:
 On Tuesday, 20 January 2015 at 03:29:23 UTC, Andrei 
 Alexandrescu wrote:
 Take a look at http://dlang.org. New menus are in place for 
 the main
 site and library.

 The site is a mess on mobile, a squashed central column and
 overlapping UI elements that aren't meant to.

 I'll see what I can do to improve the site on small screens.

 WIP:

 http://dump.thecybershadow.net/0ab998c7f4e2027fed300de718a4a058/0000013E.png


 The hamburger icon will open a side menu, like on Wikipedia 
 and YouTube.
 The looking glass icon will show a search bar.

 Niiiice... -- Andrei

https://github.com/D-Programming-Language/dlang.org/pull/811

Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:

On 1/20/15 6:08 PM, Vladimir Panteleev wrote:
 https://github.com/D-Programming-Language/dlang.org/pull/811

Deployed. Let's thank Vladimir for this great work! -- Andrei

"H. S. Teoh via Digitalmars-d" <digitalmars-d puremagic.com> writes:

On Tue, Jan 20, 2015 at 06:59:15PM -0800, Andrei Alexandrescu via Digitalmars-d
wrote:
 On 1/20/15 6:08 PM, Vladimir Panteleev wrote:
https://github.com/D-Programming-Language/dlang.org/pull/811

 
 Deployed. Let's thank Vladimir for this great work! -- Andrei

Thanks, Vladimir!


T

-- 
Turning your clock 15 minutes ahead won't cure lateness---you're just making
time go faster!

"weaselcat" <weaselcat gmail.com> writes:

On Wednesday, 21 January 2015 at 02:59:16 UTC, Andrei 
Alexandrescu wrote:
 On 1/20/15 6:08 PM, Vladimir Panteleev wrote:
 https://github.com/D-Programming-Language/dlang.org/pull/811

 Deployed. Let's thank Vladimir for this great work! -- Andrei

Looks great but I'm unable to scroll the sidebar. If I open d 
reference dropdown I can't view all of it. I can file q bug 
report in the morning if needed.

Nexus 5, Firefox.

"weaselcat" <weaselcat gmail.com> writes:

On Wednesday, 21 January 2015 at 06:33:57 UTC, weaselcat wrote:
 On Wednesday, 21 January 2015 at 02:59:16 UTC, Andrei 
 Alexandrescu wrote:
 On 1/20/15 6:08 PM, Vladimir Panteleev wrote:
 https://github.com/D-Programming-Language/dlang.org/pull/811

 Deployed. Let's thank Vladimir for this great work! -- Andrei

 Looks great but I'm unable to scroll the sidebar. If I open d 
 reference dropdown I can't view all of it. I can file q bug 
 report in the morning if needed.

 Nexus 5, Firefox.

Reiterating myself in case it was missed, impossible to browse 
the docs on mobile now.

"weaselcat" <weaselcat gmail.com> writes:

On Wednesday, 21 January 2015 at 21:27:25 UTC, weaselcat wrote:
 On Wednesday, 21 January 2015 at 06:33:57 UTC, weaselcat wrote:
 On Wednesday, 21 January 2015 at 02:59:16 UTC, Andrei 
 Alexandrescu wrote:
 On 1/20/15 6:08 PM, Vladimir Panteleev wrote:
 https://github.com/D-Programming-Language/dlang.org/pull/811

 Deployed. Let's thank Vladimir for this great work! -- Andrei

 Looks great but I'm unable to scroll the sidebar. If I open d 
 reference dropdown I can't view all of it. I can file q bug 
 report in the morning if needed.

 Nexus 5, Firefox.

 Reiterating myself in case it was missed, impossible to browse 
 the docs on mobile now.

Menu text also expands outside of the frame.
https://i.imgur.com/oBd5HRh.png

Should I file bugs for these, or just dump issues I find in this 
thread?

Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:

On 1/21/15 9:50 PM, weaselcat wrote:
 On Wednesday, 21 January 2015 at 21:27:25 UTC, weaselcat wrote:
 On Wednesday, 21 January 2015 at 06:33:57 UTC, weaselcat wrote:
 On Wednesday, 21 January 2015 at 02:59:16 UTC, Andrei Alexandrescu
 wrote:
 On 1/20/15 6:08 PM, Vladimir Panteleev wrote:
 https://github.com/D-Programming-Language/dlang.org/pull/811

 Deployed. Let's thank Vladimir for this great work! -- Andrei

 Looks great but I'm unable to scroll the sidebar. If I open d
 reference dropdown I can't view all of it. I can file q bug report in
 the morning if needed.

 Nexus 5, Firefox.

 Reiterating myself in case it was missed, impossible to browse the
 docs on mobile now.

 Menu text also expands outside of the frame.
 https://i.imgur.com/oBd5HRh.png

 Should I file bugs for these, or just dump issues I find in this thread?

Reports please. I noticed that too. -- Andrei

"H. S. Teoh via Digitalmars-d" <digitalmars-d puremagic.com> writes:

On Thu, Jan 22, 2015 at 05:50:47AM +0000, weaselcat via Digitalmars-d wrote:
[...]
 Menu text also expands outside of the frame.
 https://i.imgur.com/oBd5HRh.png
 
 Should I file bugs for these, or just dump issues I find in this
 thread?

Dunno, but at least for this particular problem, one solution would be
to make each submodule expandable, so you'd have something like:

	std
	» range
	  » primitives

rather than the current:

	std
	» std.range.primitives

which is much longer than it can be.


T

-- 
If the comments and the code disagree, it's likely that *both* are wrong. --
Christopher

Jacob Carlborg <doob me.com> writes:

On 2015-01-21 03:59, Andrei Alexandrescu wrote:

 Deployed. Let's thank Vladimir for this great work! -- Andrei

The icons need higher resolution for retina displays. Especially the 
expand (plus) icons in the menu.

-- 
/Jacob Carlborg

Jacob Carlborg <doob me.com> writes:

On 2015-01-21 08:21, Jacob Carlborg wrote:

 The icons need higher resolution for retina displays. Especially the
 expand (plus) icons in the menu.

Using glyphs/text as icons, with a special font should be considered, i.e.:

* Font Awesome - http://fortawesome.github.io/Font-Awesome/
* Glyphicons - part of Bootstrap [1] or as regular icons [2]

[1] http://getbootstrap.com/components/#glyphicons
[2] http://glyphicons.com

-- 
/Jacob Carlborg

Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:

On 1/21/15 5:39 AM, Jacob Carlborg wrote:
 On 2015-01-21 08:21, Jacob Carlborg wrote:

 The icons need higher resolution for retina displays. Especially the
 expand (plus) icons in the menu.

 Using glyphs/text as icons, with a special font should be considered, i.e.:

 * Font Awesome - http://fortawesome.github.io/Font-Awesome/
 * Glyphicons - part of Bootstrap [1] or as regular icons [2]

 [1] http://getbootstrap.com/components/#glyphicons
 [2] http://glyphicons.com

I was thinking it would be cool if each top menu entry had an icon by 
its left - a fat downward arrow by "Download", a graduation hat by 
"Reference", etc. With these fonts that seem to be easily doable. Any 
takers? -- Andrei

"DaveG" <daveg inter.net> writes:

On Wednesday, 21 January 2015 at 13:39:29 UTC, Jacob Carlborg 
wrote:
 On 2015-01-21 08:21, Jacob Carlborg wrote:

 The icons need higher resolution for retina displays. 
 Especially the
 expand (plus) icons in the menu.

 Using glyphs/text as icons, with a special font should be 
 considered, i.e.:

 * Font Awesome - http://fortawesome.github.io/Font-Awesome/
 * Glyphicons - part of Bootstrap [1] or as regular icons [2]

 [1] http://getbootstrap.com/components/#glyphicons
 [2] http://glyphicons.com

I used font-awesome in a pull request. I see svg just replaced 
png for the plus icons, those could also be switched over so all 
icons come from one place (and look consistent).
https://github.com/D-Programming-Language/dlang.org/pull/816

"Vladimir Panteleev" <vladimir thecybershadow.net> writes:

On Wednesday, 21 January 2015 at 07:21:44 UTC, Jacob Carlborg 
wrote:
 On 2015-01-21 03:59, Andrei Alexandrescu wrote:

 Deployed. Let's thank Vladimir for this great work! -- Andrei

 The icons need higher resolution for retina displays. 
 Especially the expand (plus) icons in the menu.

https://github.com/D-Programming-Language/dlang.org/pull/820

Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:

On 1/21/15 12:42 PM, Vladimir Panteleev wrote:
 On Wednesday, 21 January 2015 at 07:21:44 UTC, Jacob Carlborg wrote:
 On 2015-01-21 03:59, Andrei Alexandrescu wrote:

 Deployed. Let's thank Vladimir for this great work! -- Andrei

 The icons need higher resolution for retina displays. Especially the
 expand (plus) icons in the menu.

 https://github.com/D-Programming-Language/dlang.org/pull/820

Nice. That said, that broke the build. That's what we get for not having 
an autotester... -- Andrei

"H. S. Teoh via Digitalmars-d" <digitalmars-d puremagic.com> writes:

On Wed, Jan 21, 2015 at 01:30:03PM -0800, Andrei Alexandrescu via Digitalmars-d
wrote:
 On 1/21/15 12:42 PM, Vladimir Panteleev wrote:
On Wednesday, 21 January 2015 at 07:21:44 UTC, Jacob Carlborg wrote:
On 2015-01-21 03:59, Andrei Alexandrescu wrote:

Deployed. Let's thank Vladimir for this great work! -- Andrei

The icons need higher resolution for retina displays. Especially the
expand (plus) icons in the menu.

https://github.com/D-Programming-Language/dlang.org/pull/820

 
 Nice. That said, that broke the build. That's what we get for not
 having an autotester... -- Andrei

Yeah we need an autotester for dlang.org, if only to verify it can still
build.

As a nice side-effect, it could possibly also publish the result to a
temporary / staging server so that reviewers can preview what the
changes will look like.


T

-- 
Computers are like a jungle: they have monitor lizards, rams, mice, c-moss,
binary trees... and bugs.

"AndyC" <andy squeakycode.net> writes:

I have not read this entire thread, so I don't know if you 
already know.  std.csv doesn't seem to appear in the menus.  Also 
core.sys.* is missing.

The url does exist though: http://dlang.org/phobos/std_csv.html

There may be others I don't know, I just happened to be searching 
for these specifically.

-Andy

"H. S. Teoh via Digitalmars-d" <digitalmars-d puremagic.com> writes:

On Thu, Jan 22, 2015 at 04:07:02AM +0000, AndyC via Digitalmars-d wrote:
 I have not read this entire thread, so I don't know if you already
 know.  std.csv doesn't seem to appear in the menus.  Also core.sys.*
 is missing.
 
 The url does exist though: http://dlang.org/phobos/std_csv.html
 
 There may be others I don't know, I just happened to be searching for
 these specifically.

[...]

https://github.com/D-Programming-Language/dlang.org/pull/822


T

-- 
Debian GNU/Linux: Cray on your desktop.

Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:

On 1/21/15 12:42 PM, Vladimir Panteleev wrote:
 On Wednesday, 21 January 2015 at 07:21:44 UTC, Jacob Carlborg wrote:
 On 2015-01-21 03:59, Andrei Alexandrescu wrote:

 Deployed. Let's thank Vladimir for this great work! -- Andrei

 The icons need higher resolution for retina displays. Especially the
 expand (plus) icons in the menu.

 https://github.com/D-Programming-Language/dlang.org/pull/820

Pushed. Looks better now? -- Andrei

Jacob Carlborg <doob me.com> writes:

On 2015-01-21 22:38, Andrei Alexandrescu wrote:

 Pushed. Looks better now? -- Andrei

Actually not so much. Is the site updated?

-- 
/Jacob Carlborg

"ixid" <adamsibson hotmail.com> writes:

 WIP:

 http://dump.thecybershadow.net/0ab998c7f4e2027fed300de718a4a058/0000013E.png



That is excellent, a huge improvement!

Joseph Rushton Wakeling via Digitalmars-d <digitalmars-d puremagic.com> writes:

On 20/01/15 04:29, Andrei Alexandrescu via Digitalmars-d wrote:
 Take a look at http://dlang.org. New menus are in place for the main site and
 library.

Small note: the main content part of the page gets _very_ narrow on a
smartphone 
(even with landscape view).  I think this was a problem before but it's 
definitely a problem now.

It could probably be dealt with via some kind of reactive design that places
the 
Twitter feed underneath the side menu (or removes it entirely) if the screen 
width gets too narrow.

"Vladimir Panteleev" <vladimir thecybershadow.net> writes:

On Wednesday, 21 January 2015 at 00:37:00 UTC, Joseph Rushton 
Wakeling via Digitalmars-d wrote:
 On 20/01/15 04:29, Andrei Alexandrescu via Digitalmars-d wrote:
 Take a look at http://dlang.org. New menus are in place for 
 the main site and
 library.

 Small note: the main content part of the page gets _very_ 
 narrow on a smartphone (even with landscape view).  I think 
 this was a problem before but it's definitely a problem now.

 It could probably be dealt with via some kind of reactive 
 design that places the Twitter feed underneath the side menu 
 (or removes it entirely) if the screen width gets too narrow.

On it:

http://forum.dlang.org/post/egjlccktdeeqxhieqqaf forum.dlang.org

Steven Schveighoffer <schveiguy yahoo.com> writes:

On 1/20/15 7:45 PM, Vladimir Panteleev wrote:
 On Wednesday, 21 January 2015 at 00:37:00 UTC, Joseph Rushton Wakeling
 via Digitalmars-d wrote:
 On 20/01/15 04:29, Andrei Alexandrescu via Digitalmars-d wrote:
 Take a look at http://dlang.org. New menus are in place for the main
 site and
 library.

 Small note: the main content part of the page gets _very_ narrow on a
 smartphone (even with landscape view).  I think this was a problem
 before but it's definitely a problem now.

 It could probably be dealt with via some kind of reactive design that
 places the Twitter feed underneath the side menu (or removes it
 entirely) if the screen width gets too narrow.

 On it:

 http://forum.dlang.org/post/egjlccktdeeqxhieqqaf forum.dlang.org

Very nice. I will note though, with the twitter feed, the middle shrinks 
quite a bit before the sides disappear (I agree with removing the feed 
on mobile screens)

-Steve

"John Colvin" <john.loughran.colvin gmail.com> writes:

On Tuesday, 20 January 2015 at 03:29:23 UTC, Andrei Alexandrescu 
wrote:
 Take a look at http://dlang.org. New menus are in place for the 
 main site and library.

 I think we're in a better place than before. However, there are 
 a few things left to do. I'd very much appreciate help with 
 those.

 * New docs don't yet have the new menu implemented.

 * Menu tracking works, i.e. if the URL a page matches a menu 
 entry, then the menu will automatically open to that page and 
 mark the entry active. However, that's rather simplistic; for 
 example navigating http://dlang.org/statement.html does not 
 open the "Documentation" menu because the link is not directly 
 present.

 A simple and probably desirable fix would be to just make 
 "Language Reference" a top-level menu entry with submenus. 
 Could one of our awesome lieutenants see to it?

 * Better colors etc. are always welcome. Please submit your 
 pull requests with screenshots so we can appreciate.


 Thanks,

 Andrei

std.windows.charset results in 404, also the text for it in the 
side-menu overflows.

"Tofu Ninja" <emmons0 purdue.edu> writes:

On Tuesday, 20 January 2015 at 03:29:23 UTC, Andrei Alexandrescu 
wrote:

Can we have the old menus back :<

"MattCoder" <stop spam.com> writes:

On Wednesday, 21 January 2015 at 13:28:22 UTC, Tofu Ninja wrote:
 On Tuesday, 20 January 2015 at 03:29:23 UTC, Andrei 
 Alexandrescu wrote:

 Can we have the old menus back :<

Why would you want that?

Matheus.

"Ola Fosheim =?UTF-8?B?R3LDuHN0YWQi?= writes:

On Wednesday, 21 January 2015 at 13:38:25 UTC, MattCoder wrote:
 On Wednesday, 21 January 2015 at 13:28:22 UTC, Tofu Ninja wrote:
 On Tuesday, 20 January 2015 at 03:29:23 UTC, Andrei 
 Alexandrescu wrote:

 Can we have the old menus back :<

 Why would you want that?

Usability?

The new ones flicker because they don't load with the right class 
set. This should be done on the server.

The flickering is annoying when browsing library pages.

"John Colvin" <john.loughran.colvin gmail.com> writes:

On Wednesday, 21 January 2015 at 14:27:23 UTC, Ola Fosheim 
Grøstad wrote:
 On Wednesday, 21 January 2015 at 13:38:25 UTC, MattCoder wrote:
 On Wednesday, 21 January 2015 at 13:28:22 UTC, Tofu Ninja 
 wrote:
 On Tuesday, 20 January 2015 at 03:29:23 UTC, Andrei 
 Alexandrescu wrote:

 Can we have the old menus back :<

 Why would you want that?

 Usability?

 The new ones flicker because they don't load with the right 
 class set. This should be done on the server.

 The flickering is annoying when browsing library pages.

not seeing any flickering here on OS X 10.10 + Safari

"MattCoder" <stop spam.com> writes:

On Wednesday, 21 January 2015 at 14:47:09 UTC, John Colvin wrote:
 On Wednesday, 21 January 2015 at 14:27:23 UTC, Ola Fosheim 
 Grøstad wrote:
 On Wednesday, 21 January 2015 at 13:38:25 UTC, MattCoder wrote:
 On Wednesday, 21 January 2015 at 13:28:22 UTC, Tofu Ninja 
 wrote:
 On Tuesday, 20 January 2015 at 03:29:23 UTC, Andrei 
 Alexandrescu wrote:

 Can we have the old menus back :<

 Why would you want that?

 Usability?

 The new ones flicker because they don't load with the right 
 class set. This should be done on the server.

 The flickering is annoying when browsing library pages.

 not seeing any flickering here on OS X 10.10 + Safari


Neither I, Linux + FF 34.0!

Matheus.

"Ola Fosheim =?UTF-8?B?R3LDuHN0YWQi?= writes:

On Wednesday, 21 January 2015 at 14:47:09 UTC, John Colvin wrote:
 On Wednesday, 21 January 2015 at 14:27:23 UTC, Ola Fosheim 
 Grøstad wrote:
 On Wednesday, 21 January 2015 at 13:38:25 UTC, MattCoder wrote:
 On Wednesday, 21 January 2015 at 13:28:22 UTC, Tofu Ninja 
 wrote:
 On Tuesday, 20 January 2015 at 03:29:23 UTC, Andrei 
 Alexandrescu wrote:

 Can we have the old menus back :<

 Why would you want that?

 Usability?

 The new ones flicker because they don't load with the right 
 class set. This should be done on the server.

 The flickering is annoying when browsing library pages.

 not seeing any flickering here on OS X 10.10 + Safari

It does not open the menu until after the page is loaded. And if 
it is not in the cache that takes a good 600ms atm.

Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:

On 1/21/15 6:47 AM, John Colvin wrote:
 On Wednesday, 21 January 2015 at 14:27:23 UTC, Ola Fosheim Grøstad wrote:
 On Wednesday, 21 January 2015 at 13:38:25 UTC, MattCoder wrote:
 On Wednesday, 21 January 2015 at 13:28:22 UTC, Tofu Ninja wrote:
 On Tuesday, 20 January 2015 at 03:29:23 UTC, Andrei Alexandrescu wrote:

 Can we have the old menus back :<

 Why would you want that?

 Usability?

 The new ones flicker because they don't load with the right class set.
 This should be done on the server.

 The flickering is annoying when browsing library pages.

 not seeing any flickering here on OS X 10.10 + Safari

I think it has to do with the menu closing and reopening every time. 
Easy to fix. Any takers? -- Andrei

Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:

On 1/21/15 5:28 AM, Tofu Ninja wrote:
 On Tuesday, 20 January 2015 at 03:29:23 UTC, Andrei Alexandrescu wrote:

 Can we have the old menus back :<

Yes: https://web.archive.org/web/20150102192528/http://dlang.org/

"MattCoder" <stop spam.com> writes:

On Tuesday, 20 January 2015 at 03:29:23 UTC, Andrei Alexandrescu 
wrote:

Suggestion: The font-style used in one menu differs from the 
other, ex:

http://i.imgur.com/fRwdFNj.png

Which I think it should be the same, and as you can see in the 
image above, some words doesn't fit in the menu width, for 
example: "std.container.package".

Matheus.

Andrei Alexandrescu <SeeWebsiteForEmail erdani.org> writes:

On 1/21/15 7:57 AM, MattCoder wrote:
 On Tuesday, 20 January 2015 at 03:29:23 UTC, Andrei Alexandrescu wrote:

 Suggestion: The font-style used in one menu differs from the other, ex:

 http://i.imgur.com/fRwdFNj.png

 Which I think it should be the same, and as you can see in the image
 above, some words doesn't fit in the menu width, for example:
 "std.container.package".

That's intentional - module names are rendered in <tt>. It's been 
suggested that I eliminate "std." but all that may be not needed because 
the upcoming redesign :o). -- Andrei