New menus are up (page 4)

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

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.

January 20, 2015

Re: New menus are up

Posted by Steven Schveighoffer
in reply to Andrei Alexandrescu

Permalink

Steven Schveighoffer

Posted in reply to Andrei Alexandrescu

Permalink

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

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

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.

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?

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

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.

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. :)

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 :)

Forums