"DaveG" <daveg@inter.net> wrote:
>> On 1/18/15 5:41 AM, Kiith-Sa wrote:
>>> Also, note that the collapsible menu can be done in pure CSS, >> no JS needed, which would allow it to work consistently even with >> NoScript.
> It is possible with CSS only (I think), but fancy features like animations require CSS3 transitions which has inconsistent support. Do we have a set of "supported" browsers? In this case we shouldn't have any problem degrading gracefully anyway, but it's good to know.
> 
>> On 1/18/15 9:02 AM, aldanor wrote:
>>> This is usually solved by media queries / responsive design / >> grid frameworks, sorry if I'm stating the obvious :)
>> 
>> My understanding is there are various simpler way to do this, > e.g. separate styles for small screen devices, redirection to a > different URL, setting "hidden" to certain DIVs dynamically > etc. etc. As you saying there's no way to do this unless we use > some grid framework...
> We don't need to use a framework, although it might be a good idea if someone has experience with one they think is appropriate. I'll try to get to the menus and making primary layout responsive at some point today.
> 
> -Dave

Thanks!!

Jacob Carlborg <doob@me.com> wrote:
> On 2015-01-18 06:14, weaselcat wrote:
> 
>> Looked at it in a webkit browser and you're right, I take back my first
>> comment Andrei.
>> But it does seem messed up on Firefox.
>> https://i.imgur.com/FVb2Q6y.png
> 
> Looks like the colors are inverted.

I know what happened (but am afk for a while). I only changed colors in one place in the css, the one specific to WebKit. That can be easily seen in cssmenu.css in my pull request.

On Sunday, 18 January 2015 at 17:03:00 UTC, aldanor wrote:
> This is usually solved by media queries / responsive design / grid frameworks, sorry if I'm stating the obvious :)

Yeah, and it is really REALLY easy.

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

Jacob makes a few good points that could improve it a bit but just hiding it on a certain size is better than it is now.

On Sunday, 18 January 2015 at 17:56:41 UTC, aldanor wrote:
> And yet another thing you gain with (most) frameworks is having access to the original SASS/LESS.

I think that's a con, actually. My biggest problem with contributing to the dlang website is that I have to do it blind - it won't make on my computer.

The last thing we need is to make that process even more complicated with even more dependencies.

On Sunday, 18 January 2015 at 17:58:57 UTC, Mengu wrote:
> if i may, i'll go and straightly ask a very great designer friend of mine to help us out. he'll either design a new interface for us or help us make this one better. let me know your call.

BTW I'll write the css myself if some designer wants to send me a .png file of what they want the site to look like. (I shouldn't be promising this given the million other things I have to do, but writing css isn't really that hard compared to coming up with the visual design)

Tough I think the site is basically ok looking right now and just a few minor tweaks would be nice... which is why I wrote them myself.

I encourage others to do the same, just open a pull request and we can hash it out over some concrete code.

On 2015-01-18 17:21, Andrei Alexandrescu wrote:

> Suggestions on how to make it better? -- Andrei

Something flat (i.e. no gradient) or with less difference between the colors in the gradient.

-- 
/Jacob Carlborg

On 2015-01-18 17:23, Andrei Alexandrescu wrote:

> Can we ditch the twitter div on mobile? (Pull request would be nice,
> thanks.) -- Andrei

Adam has already created that: https://github.com/D-Programming-Language/dlang.org/pull/779

-- 
/Jacob Carlborg

On Sunday, 18 January 2015 at 02:18:16 UTC, Andrei Alexandrescu wrote:
> I took the better part of today working on this: https://github.com/D-Programming-Language/dlang.org/pull/780. See demo at http://erdani.com/d/.
>
> What do you all think? Is it an improvement over what we have now?
>
> I'd appreciate your help with reviewing and pulling this, and also with improving the colors (which I'm terrible at) and page tracking as mentioned in the pull request.
>
>
> Thanks,
>
> Andrei

The sidebar colors does look... I liked the old menus better. It was a bit old school but it still looked good (like the reddit menus). The only bad thing about the old menus is that there is to many links
Responsive design is missing. I think we could get some of it for free if we used a framework like bootstrap (rust uses it).
Many different styles on different sections. It feels like I'm redirected all around the web. E.x code.dlang.org vs. dlang.org. Shouldn't all this be under the same site? Maybe we should give some indication that some links are not part of dlang.org.

Googles pagespeed also gives some nice guidelines:
https://developers.google.com/speed/pagespeed/insights/?url=dlang.org

Best regards,
NVolcz

I like the buttons with the dark red gradients on the left. Although the button titles don't seem professional to me, the buttons do.

I'm personally interested in seeing the "story" of D told better. I have more of a conscious opinion of the words of the front page than I do of the look-and-feel. Are the words up for discussion here, or just the look-and-feel for now?

On Sunday, 18 January 2015 at 21:27:25 UTC, NVolcz wrote:
> Googles pagespeed also gives some nice guidelines:
> https://developers.google.com/speed/pagespeed/insights/?url=dlang.org

Nice and for image processing/compression I'd like to recommend this free tool (Win/Linux/Mac):

http://advsys.net/ken/utils.htm#pngoutkziplicense

Matheus.