On 2015-12-21 14:58, anonymous wrote:
> On 19.12.2015 15:33, Jacob Carlborg wrote:
>> http://www.googledrive.com/host/0B7UtafxGD9vESlB3aFBxcjNPOXM
>
> I know you wait for Walter's and Andrei's approval on this before
> investing more work. That's very reasonable. Luckily, I'm not so
> reasonable ;)
>
> http://d-ag0aep6g.rhcloud.com/
>
> On GitHub if people want to play around with it:
> https://github.com/aG0aep6G/dlang.org/tree/Ivan-Smirnov's-redesign

This is the original repository from Ivan [1].

[1] https://github.com/aldanor/dlang.org-sketch

-- 
/Jacob Carlborg

On 2015-12-21 15:13, Andrei Alexandrescu wrote:

> Nice! A few questions.
>
> What are the changes to the tooling used and the build process?

The original code is written in HTML, JavaScript and Less (CSS). See repository for build instructions [1]. If I move forward with this I would go with vibe.d. I would prefer Sass for the CSS and CoffeeScript for the JavaScript.

> Is there a reasonable decay if javascript is disabled?

No. The top menu uses JavaScript and all the collapsible sections depends on JavaScript. I hope it's possible to change so the collapsible sections are expanded by default.

> Can we defer any changes to the logo so we don't get sidetracked in
> this? Just scale the existing logo to fit and defer any changes to it to
> later.

Using the existing logo in place of the new one looks quite out of place. You can easily test that using the developer tools in your browser. Right click on the image, choose "Inspect Element", modify the "src" attribute of the "img" tag to point to "http://dlang.org/images/dlogo.svg".

[1] https://github.com/aldanor/dlang.org-sketch

-- 
/Jacob Carlborg

On Monday, 21 December 2015 at 15:28:44 UTC, Jacob Carlborg wrote:
> The original code is written in HTML, JavaScript and Less (CSS). See repository for build instructions [1]. If I move forward with this I would go with vibe.d.

+1

On Monday, 21 December 2015 at 15:07:18 UTC, anonymous wrote:
> It's definitely very buggy. This is nowhere near releasable quality.

Let's not underestimate, but let's not overestimate either, I'm pretty confident these bugs could all be fixed in a day of tweaking, probably less than that. It looks reasonable right now.

On 21.12.2015 16:45, Adam D. Ruppe wrote:
> Let's not underestimate, but let's not overestimate either, I'm pretty
> confident these bugs could all be fixed in a day of tweaking, probably
> less than that. It looks reasonable right now.

Possibly, but the whole thing still needs to be implemented properly. I just added all the CSS from the mock-up on top of the existing stuff. We don't want to keep it that way.

Finding all the little issues in the different sections of the site may take its time, too. And then there are forum.dlang.org and visuald.dlang.org.

Also, things like the overcrowded menu bar, and overly long code snippets (on the home page) need decisions, which can take a while if people are not in immediate agreement.

On doing it right, I'm not sure how to approach the Bootstrap grid thing. Use it with raw HTML/CSS? That may be more complicated than just doing things without a framework like that. And switching dlang.org over to some preprocessor is not trivial, and may be deemed "too disruptive for too little gain".

On Monday, 21 December 2015 at 16:50:31 UTC, anonymous wrote:
> On 21.12.2015 16:45, Adam D. Ruppe wrote:
>> Let's not underestimate, but let's not overestimate either, I'm pretty
>> confident these bugs could all be fixed in a day of tweaking, probably
>> less than that. It looks reasonable right now.
>
> Possibly, but the whole thing still needs to be implemented properly. I just added all the CSS from the mock-up on top of the existing stuff. We don't want to keep it that way.
>
> Finding all the little issues in the different sections of the site may take its time, too. And then there are forum.dlang.org and visuald.dlang.org...

Don't forget... less is good: http://motherfuckingwebsite.com/

Bubba.

On Monday, 21 December 2015 at 16:50:31 UTC, anonymous wrote:
> Possibly, but the whole thing still needs to be implemented properly. I just added all the CSS from the mock-up on top of the existing stuff. We don't want to keep it that way.

Guess who wrote a program to clean that up semi-automatically just two weeks ago? In D, too!

> On doing it right, I'm not sure how to approach the Bootstrap grid thing.

Death to bootstrap.

On Monday, 21 December 2015 at 13:58:30 UTC, anonymous wrote:
> On 19.12.2015 15:33, Jacob Carlborg wrote:
>> http://www.googledrive.com/host/0B7UtafxGD9vESlB3aFBxcjNPOXM
>
> I know you wait for Walter's and Andrei's approval on this before investing more work. That's very reasonable. Luckily, I'm not so reasonable ;)
>
> http://d-ag0aep6g.rhcloud.com/
>


Please work towards greenlighting this!
This might be a big, big thing for D adoption and perception.
A prominent download button and call to actions can increase conversions manyfold.

On 12/21/2015 10:28 AM, Jacob Carlborg wrote:
> On 2015-12-21 15:13, Andrei Alexandrescu wrote:
>
>> Nice! A few questions.
>>
>> What are the changes to the tooling used and the build process?
>
> The original code is written in HTML, JavaScript and Less (CSS). See
> repository for build instructions [1]. If I move forward with this I
> would go with vibe.d. I would prefer Sass for the CSS and CoffeeScript
> for the JavaScript.

That's a large leap. I suggest using Ddoc instead of Sass compact CSS files, see the existing instance at https://github.com/D-Programming-Language/dlang.org/blob/master/css/cssmenu.css.dd.

CoffeeScript sounds like a nice thing to add and is from what I've heard reasonably stable.

We can't make the site depend on dub at this time. There have been situations in the past when dub wouldn't build and nobody was available to work on it. At that time only the alternate documentation got broken, but if the site depends on it we're looking at catastrophic failure.

>> Is there a reasonable decay if javascript is disabled?
>
> No. The top menu uses JavaScript and all the collapsible sections
> depends on JavaScript. I hope it's possible to change so the collapsible
> sections are expanded by default.

My understanding is this is a sticky point with some, so probably needs fixing before the release.

>> Can we defer any changes to the logo so we don't get sidetracked in
>> this? Just scale the existing logo to fit and defer any changes to it to
>> later.
>
> Using the existing logo in place of the new one looks quite out of
> place. You can easily test that using the developer tools in your
> browser. Right click on the image, choose "Inspect Element", modify the
> "src" attribute of the "img" tag to point to
> "http://dlang.org/images/dlogo.svg".
>
> [1] https://github.com/aldanor/dlang.org-sketch

Just defer it and we're good.


Andrei

On Monday, 21 December 2015 at 15:09:06 UTC, Adam D. Ruppe wrote:
> Dedicated pages is a good idea and can be done trivially with ddoc macros to avoid repetition of the content in the source.
>
> It could also be a css :hover dropdown instead of JS, but I hate drop downs on hover so I'd prefer the dedicated pages.

We could use the :hover dropdowns as a fallback for the JS, though. It might not be ideal, but isn't that basically the definition of a fallback?