On 25/12/15 15:04, anonymous wrote:

> I don't know what you mean. Could this be a cache thing? Can you give a
> specific example, maybe with a screenshot?

No, it's not a cache thing, the new top menu is there. What I mean is that the Phobos documentation (for example) doesn't use the new design. Same syntax colors for the syntax highlighting, same green color for the Phobos docs and so on.

> This version doesn't use Bootstrap anymore. I just changed some details
> from the current dlang.org, the core mechanism should work the same.
>
> If the current dlang.org looks ok, but mine doesn't, then I must have
> messed up something. It looks fine for me, though, and I have no OS X
> around to check. Further assistance would be appreciated.

It looks exactly like the problem I had with Bootstrap on OS X. It was only a problem on OS X, perhaps on some specific version of Windows as well. This is how it looks like for me using Safari on OS X [1]. This is the bug I reported to Bootstrap [2].

[1] https://drive.google.com/open?id=0B7UtafxGD9vEQmFxT0d1T1JiU1E
[2] https://github.com/twbs/bootstrap/issues/7602

-- 
/Jacob Carlborg

On 26.12.2015 13:19, Jacob Carlborg wrote:

> No, it's not a cache thing, the new top menu is there. What I mean is
> that the Phobos documentation (for example) doesn't use the new design.
> Same syntax colors for the syntax highlighting, same green color for the
> Phobos docs and so on.

Yeah, I hadn't looked into those, yet. Did so now just now, and updated the site. I'm not so sure about coloring the documented symbols the same way as links, though. Maybe some nice blue/green/cyan instead of the link red?

For now, I'm not going to try to implement the expandable phobos docs or the cross references, because they're non-trivial and I think they can be done later on. Also, Adam apparently has similar plans for the phobos docs. I think I'll wait and see what comes from that, first.

> This is how it looks like for me using Safari on OS X [1]. This is
> the bug I reported to Bootstrap [2].
>
> [1] https://drive.google.com/open?id=0B7UtafxGD9vEQmFxT0d1T1JiU1E
> [2] https://github.com/twbs/bootstrap/issues/7602

Does that mean I just have to add `-webkit-appearance: none;` to the select element? Did that just now. Does it work?

On 2015-12-26 18:27, anonymous wrote:

> Does that mean I just have to add `-webkit-appearance: none;` to the
> select element? Did that just now. Does it work?

It does work, but it looks like it affected other bowers as well (Firefox). BTW, I still think that a custom look would be better. Something like the search field in Firefox. It has a the magnifier icon which acts like a menu.

-- 
/Jacob Carlborg

On 26.12.2015 21:21, Jacob Carlborg wrote:
> It does work, but it looks like it affected other bowers as well
> (Firefox).

That's weird. Does it look bad?

> BTW, I still think that a custom look would be better.
> Something like the search field in Firefox. It has a the magnifier icon
> which acts like a menu.

I'm hesitating to go that way, because:
a) I don't want to put more on my plate than necessary at this point.
b) It would require Javascript, right? That's not a problem in itself, but figuring out a good fallback mechanism seems to be difficult here.

On 2015-12-27 13:06, anonymous wrote:
> That's weird. Does it look bad?

https://drive.google.com/open?id=0B7UtafxGD9vEQTVjeXZhSDdRZDA

> b) It would require Javascript, right?

I have no idea.

-- 
/Jacob Carlborg

On 27.12.2015 15:04, Jacob Carlborg wrote:
> https://drive.google.com/open?id=0B7UtafxGD9vEQTVjeXZhSDdRZDA

The caret seems to be a bit high maybe, but otherwise that's how it's supposed to look. Feel free to criticize, of course.

On 2015-12-27 21:42, anonymous wrote:

> The caret seems to be a bit high maybe, but otherwise that's how it's
> supposed to look. Feel free to criticize, of course.

Aha, then there's no problem :)

-- 
/Jacob Carlborg

Most of the audience of the site can be roughly divided into two categories: beginners and experienced users of D.
for beginners:
Looking to this sketch I think it will be useful to add some simple installation instruction for detected user's OS right here (to appreciate the complexity of the D installation before clicking), highlight links to Learn forum and IRC channel as most useful places to resolve problems and make documentation more accessible (btw, try link like http://php.net/preg_replace for example - I want to use dlang.org/Tuple and so on). It will be useful also to provide selector of online examples to allow beginners to see most interesting examples. Now if I want to see another example I need to reload page.
for experienced:
Many of existing blocks like "Why D?", "Learn", online examples are irrelevant to experienced D programmer. May be make switch button to drop out all presentation stuff and leave only more details docs and news sections? Or may be separate page.

On Saturday, 19 December 2015 at 14:33:35 UTC, Jacob Carlborg wrote:
> [1] http://forum.dlang.org/thread/ejpuwwlutklvlozyfnqy@forum.dlang.org
> [2] http://forum.dlang.org/thread/fdbnecqbemseocwzghxw@forum.dlang.org
> [3] http://www.googledrive.com/host/0B7UtafxGD9vESlB3aFBxcjNPOXM

This reminded me when at work we got new design in html/css and had to put it on the site. It looked better but lacked 1/3 of fields and functionality. Then backend developers had to fix design and in the end it was better than before but not as good as html/css from designer.

I think its a good start, but needs some layout changes. IMHO "Why D?" should be almost at the top or near code sample. I will meditate on it.

On 06.01.2016 09:00, welkam wrote:
> This reminded me when at work we got new design in html/css and had to
> put it on the site. It looked better but lacked 1/3 of fields and
> functionality. Then backend developers had to fix design and in the end
> it was better than before but not as good as html/css from designer.

Also check out http://d-ag0aep6g.rhcloud.com/ where I'm currently working on the implementation. It's a little different from the mockup, precisely because I'm trying not to drop features/content.