digitalmars.D - [dlang.org] getting the redesign wrapped up
- anonymous (59/59) Jan 08 2016 My implementation of the redesign is pretty much complete.
- Mattcoder (5/7) Jan 08 2016 Well I think it's very good, the layout is clean and very
- Adam D. Ruppe (5/9) Jan 08 2016 Once it goes live, I can change it to be whatever you want.
- Jacob Carlborg (14/17) Jan 09 2016 I'm not sure that I like that some of the headers (learn, packages) are
- anonymous (3/7) Jan 10 2016 Agreed. I unlinked Learn and Packages. The links were duplicated in the
- Andrei Alexandrescu (17/72) Jan 09 2016 I give it my seal of approval. It's a large change but something
- anonymous (6/11) Jan 10 2016 [...]
- Andrei Alexandrescu (3/14) Jan 10 2016 Probably we need to fix that, but it's a preexisting matter so don't
- anonymous (3/4) Jan 10 2016 Here we go:
- Andrei Alexandrescu (3/7) Jan 10 2016 ...aaaaaand we're live. Congratulations and many thanks to the folks who...
- Robert burner Schadek (1/1) Jan 10 2016 congratulations
- Saurabh Das (5/13) Jan 10 2016 Congratulations to everyone who's worked on this!
- anonymous (6/8) Jan 10 2016 Website bugs go into the same bug tracker as compiler and library bugs:
- Saurabh Das (6/16) Jan 10 2016 OK. I'll report issues there. Will do a thorough review later
- Vladimir Panteleev (8/16) Jan 10 2016 @anonymous, thank you for the great work and congratulations on
- Andrei Alexandrescu (3/7) Jan 10 2016 You're right, sorry about getting too enthusiastic. Should we undo? --
- Jacob Carlborg (6/8) Jan 10 2016 That depends on how many new issues have appeared, how much trouble they...
- cym13 (3/11) Jan 10 2016 Congrats! This looks great!
- Gary Willoughby (4/16) Jan 10 2016 I like it! It's a vast improvement. My one criticism would be
- deadalnix (20/28) Jan 10 2016 That's awesome. Now :
- Iain Buclaw via Digitalmars-d (5/37) Jan 10 2016 I echo this, and would add a further point that you should have tested a...
- JohnCK (4/8) Jan 10 2016 Wow. Man I don't want to be too harsh, but that was pretty lame.
- cym13 (5/14) Jan 10 2016 Note that this url shouldn't even exist: the link on the main
- anonymous (3/6) Jan 10 2016 downloads.dlang.org is linked from download.html ("Release Archive"). So...
- Andrei Alexandrescu (4/11) Jan 10 2016 We're either too quick or too slow :o).
- anonymous (3/6) Jan 10 2016 Uhm, where can I fix that? downloads.dlang.org isn't part of the of
- JohnCK (8/8) Jan 10 2016 First of all, the site looks better than the old version.
- rsw0x (2/10) Jan 10 2016 It actually seems sort of fitting ; )
- Iain Buclaw via Digitalmars-d (3/11) Jan 10 2016 Don't mock D-man. He will get you in your dreams. :-)
- lobo (6/14) Jan 10 2016 I kinda like it :)
- Iain Buclaw via Digitalmars-d (5/13) Jan 10 2016 This is on Amazon S3.
- Brad Roberts via Digitalmars-d (3/16) Jan 10 2016 These days I just pay for it. Our very capable release manager manages
- anonymous (14/18) Jan 10 2016 We can shuffle things around, of course. One alternative:
- Jacob Carlborg (4/6) Jan 11 2016 Do both?
- deadalnix (4/23) Jan 11 2016 No, nothing more needs to be added. Things needs to be removed,
- anonymous (6/9) Jan 11 2016 As far as I understand, you're saying that Learn is too far down. I'm
- wobbles (6/37) Jan 11 2016 If there was a very slight border around each section (Learn,
- Adam D. Ruppe (41/43) Jan 11 2016 I click on my URL bar and punch in "interesting-site.com". It
- wobbles (15/60) Jan 11 2016 Yeah, I can see why that is an annoyance. But there is ways
- Adam D. Ruppe (14/18) Jan 11 2016 I think the left menu on the current site is of limited value
- wobbles (8/26) Jan 11 2016 Yeah, I really dislike the over use of whitespace in current
- Guillaume Piolat (2/6) Jan 10 2016 This looks gorgeous. Congratulation to our @anonymous contributor!
- Martin Nowak (6/19) Jan 10 2016 Is there a chance to pre- (ddoc) or post-process (html) our
- Andrei Alexandrescu (4/23) Jan 10 2016 Yeah, great tool Martin. I recall it was among the first on the dub
- Martin Nowak (7/10) Jan 11 2016 It's from 2014-Dec-11 and despite a few deprecations it still
- Adam D. Ruppe (38/41) Jan 11 2016 My dom.d in loose mode is able to read ddoc's output. Here's a
- Vladimir Panteleev (28/76) Jan 09 2016 Once this is merged, would you be OK with working together on
- anonymous (9/18) Jan 10 2016 Sure.
- anonymous (4/6) Jan 11 2016 I wanted to have a look at DFeed, but all I get with a local clone is
- Vladimir Panteleev (3/11) Jan 11 2016 Ah, sorry, the build instructions are out of date. That file is
- anonymous (7/9) Jan 11 2016 Alright, after `make` it works.
- Vladimir Panteleev (4/14) Jan 11 2016 Not right now unfortunately. Definitely something I need to add
- anonymous (5/6) Jan 12 2016 As responsive as the main site. I just updated the dlang.org submodule
- Andrei Alexandrescu (3/9) Jan 12 2016 Here's the download source:
- Jack Stouffer (15/42) Jan 09 2016 Also great.
- anonymous (19/35) Jan 10 2016 [...]
- Bastiaan Veelo (6/8) Jan 10 2016 Can I ask not to use dotted frames? It may be my eyes, but I get
- anonymous (3/4) Jan 10 2016 I agree that they're ugly, but they've been ugly before the redesign,
- anonymous (3/5) Jan 10 2016 No blocking issues in sight so far. Time to make a pull request:
- mate (8/8) Jan 10 2016 Thanks and congrats!
- anonymous (5/12) Jan 10 2016 The icons are done using FontAwesome. Do the icons work on their
- anonymous (3/4) Jan 11 2016 That one was pulled prematurely, and then reverted.
- Saurabh Das (36/100) Jan 10 2016 Again, thanks for doing this. The new design overall looks much
- Saurabh Das (3/5) Jan 10 2016 I meant it looks funny when it spans half the height of the page
- anonymous (8/18) Jan 10 2016 [...]
- Jack Stouffer (2/4) Jan 10 2016 Congratulations on getting this merged!
- karabuta (11/24) Jan 16 2016 It's responsive too. sweet!! Nice layout, nice UX, reddish color
My implementation of the redesign is pretty much complete. Check it out: http://d-ag0aep6g.rhcloud.com/ This is an implementation of a design done by one Ivan Smirnov, brought forward by Jacob Carlborg [1]. The dark forum widgets on the home page are in iframes. Their styling will need to be updated at the source, which is forum.dlang.org. Another external dependency is the This Week in D script. Adam, it would be nice if the `setTwid` function could take the date separately. That would allow me to word the text without having "This Week in D" there twice. Other than those two little things I consider this done. From my side it could be merged immediately. But I'm sure there are a thousand things wrong with this. Here are some topics to get you started: 1) Legalities I mentioned this before, but noone reacted. Can we use Ivan's work? Do we have his ok? Do we need it? Jacob mentioned that he can't in contact with him anymore. Is that a problem? 2) Reviewing the code https://github.com/aG0aep6G/dlang.org/commits/Ivan-Smirnov's-redesign This is just one giant commit (the others are independent minor fixes). GitHub refuses to show the diff for the style.css file, because it's too big. Is this acceptable, or do I need to split it up somehow? If I need to split it up, any advice on how to do that? 3) New Pages Aside from the overall style changes and menu reorganization, I also added overview pages for the articles and for the tools: http://d-ag0aep6g.rhcloud.com/articles.html http://d-ag0aep6g.rhcloud.com/tools.html They feature new text that should be proofread. 4) Fonts Vladimir Panteleev has spoken out against web fonts [2]. His argument is that they can look fine on one system but bad on another. Indeed the recently changed code font on dlang.org looks pretty bad for me while the default 'monospace' looks just fine, which is why I reverted that in the redesign. The redesign uses a web font for its main font, though: Roboto Slab. It looks good for me, but I'm not able to test it on a large variety of device/OS/browser combinations. Maybe it's fine, or maybe we should stay away from web fonts categorically. I don't really have an opinion on this. 5) Justified Text Andrei loves it, everybody else hates it. I killed it as the mockup didn't have it. Is that ok, or is justified text a must? 6) Red For Clickables Only? Currently, the site uses red almost exclusively for clickable stuff. But it's also used as a highlight color for non-clickable things. For example in phobos signatures: The left borders of the signature boxes are red, and the documented symbol is highlighted with red. Red does not signal clickability here. I don't like that and I'd prefer to go with another color for generic highlighting, reserving red for clickable stuff. 7) The Logo As requested by Andrei, this does not feature a logo change for now. I'm going to make a pull request for the slicker logo variant [3] when this is through. [1] http://forum.dlang.org/post/n53ps0$2j8f$1 digitalmars.com [2] http://forum.dlang.org/post/xezfeilxblfkibldvsgg forum.dlang.org [3] https://gist.github.com/aG0aep6G/0803ec5ae49f6afb0196
Jan 08 2016
On Friday, 8 January 2016 at 22:32:59 UTC, anonymous wrote:My implementation of the redesign is pretty much complete. check it out: http://d-ag0aep6g.rhcloud.com/Well I think it's very good, the layout is clean and very presentable. I know that isn't your fault, but that logo needs a change. ;) Matt.
Jan 08 2016
On Friday, 8 January 2016 at 22:32:59 UTC, anonymous wrote:Another external dependency is the This Week in D script. Adam, it would be nice if the `setTwid` function could take the date separately. That would allow me to word the text without having "This Week in D" there twice.Once it goes live, I can change it to be whatever you want. In the mean time btw, you could scan the string for parens. I always use the same format: "This Week in D (date)" so you could slice that string to get the date.
Jan 08 2016
On 2016-01-08 23:32, anonymous wrote:My implementation of the redesign is pretty much complete. Check it out: http://d-ag0aep6g.rhcloud.com/I'm not sure that I like that some of the headers (learn, packages) are clickable on the main page. This also causes some icons to be black (gray?) and some to be red. How about a link at the end of the section with the title "Read more", or similar?[3] https://gist.github.com/aG0aep6G/0803ec5ae49f6afb0196I like it :) Ideally we should make something like a base logo with only two colors. The logo needs to be recognizable with this basic design. Then it should be fine to create different variations with different colors, backgrounds, shadows and so on, if necessary. The point is that one would recognize the core from the base logo in all of the variants, then we would have a more flexible logo. -- /Jacob Carlborg
Jan 09 2016
On 09.01.2016 11:35, Jacob Carlborg wrote:I'm not sure that I like that some of the headers (learn, packages) are clickable on the main page. This also causes some icons to be black (gray?) and some to be red. How about a link at the end of the section with the title "Read more", or similar?Agreed. I unlinked Learn and Packages. The links were duplicated in the text already anyway.
Jan 10 2016
On 1/8/16 5:32 PM, anonymous wrote:My implementation of the redesign is pretty much complete. Check it out: http://d-ag0aep6g.rhcloud.com/ This is an implementation of a design done by one Ivan Smirnov, brought forward by Jacob Carlborg [1]. The dark forum widgets on the home page are in iframes. Their styling will need to be updated at the source, which is forum.dlang.org. Another external dependency is the This Week in D script. Adam, it would be nice if the `setTwid` function could take the date separately. That would allow me to word the text without having "This Week in D" there twice. Other than those two little things I consider this done. From my side it could be merged immediately.I give it my seal of approval. It's a large change but something familiar enough in style that current maintainers can continue maintaining.1) Legalities I mentioned this before, but noone reacted. Can we use Ivan's work? Do we have his ok? Do we need it? Jacob mentioned that he can't in contact with him anymore. Is that a problem?Please reach out to Ivan by email. If he comes later, I'm sure he'll love seeing his work implemented with credit. The worst he can do is ask us to take down the page.2) Reviewing the code https://github.com/aG0aep6G/dlang.org/commits/Ivan-Smirnov's-redesign This is just one giant commit (the others are independent minor fixes). GitHub refuses to show the diff for the style.css file, because it's too big. Is this acceptable, or do I need to split it up somehow? If I need to split it up, any advice on how to do that?I think we're fine.3) New Pages Aside from the overall style changes and menu reorganization, I also added overview pages for the articles and for the tools: http://d-ag0aep6g.rhcloud.com/articles.html http://d-ag0aep6g.rhcloud.com/tools.html They feature new text that should be proofread.Nice touch.4) Fonts Vladimir Panteleev has spoken out against web fonts [2]. His argument is that they can look fine on one system but bad on another. Indeed the recently changed code font on dlang.org looks pretty bad for me while the default 'monospace' looks just fine, which is why I reverted that in the redesign. The redesign uses a web font for its main font, though: Roboto Slab. It looks good for me, but I'm not able to test it on a large variety of device/OS/browser combinations. Maybe it's fine, or maybe we should stay away from web fonts categorically. I don't really have an opinion on this.I'd say go with the webfont and let us change it based on forward experience.5) Justified Text Andrei loves it, everybody else hates it. I killed it as the mockup didn't have it. Is that ok, or is justified text a must?Justified font only looks good in conjunction with hyphenation. I'd say make text justified on browsers that support css hyphenation (all but Chrome I recall?) and left align on the others.6) Red For Clickables Only? Currently, the site uses red almost exclusively for clickable stuff. But it's also used as a highlight color for non-clickable things. For example in phobos signatures: The left borders of the signature boxes are red, and the documented symbol is highlighted with red. Red does not signal clickability here. I don't like that and I'd prefer to go with another color for generic highlighting, reserving red for clickable stuff.Up to you.7) The Logo As requested by Andrei, this does not feature a logo change for now. I'm going to make a pull request for the slicker logo variant [3] when this is through.Sounds good. Thanks. Let's put this in motion!! Andrei
Jan 09 2016
On 09.01.2016 22:43, Andrei Alexandrescu wrote:On 1/8/16 5:32 PM, anonymous wrote:[...][...]5) Justified TextJustified font only looks good in conjunction with hyphenation. I'd say make text justified on browsers that support css hyphenation (all but Chrome I recall?) and left align on the others.I.e., revert the change. Done. By the way, in Ubuntu I don't see any hyphenation in Firefox. It works in Windows, though.
Jan 10 2016
On 1/10/16 9:05 AM, anonymous wrote:On 09.01.2016 22:43, Andrei Alexandrescu wrote:Probably we need to fix that, but it's a preexisting matter so don't worry about it. Do you have a PR in place yet? Thx! -- AndreiOn 1/8/16 5:32 PM, anonymous wrote:[...][...]5) Justified TextJustified font only looks good in conjunction with hyphenation. I'd say make text justified on browsers that support css hyphenation (all but Chrome I recall?) and left align on the others.I.e., revert the change. Done. By the way, in Ubuntu I don't see any hyphenation in Firefox. It works in Windows, though.
Jan 10 2016
On 10.01.2016 16:11, Andrei Alexandrescu wrote:Do you have a PR in place yet?Here we go: https://github.com/D-Programming-Language/dlang.org/pull/1187
Jan 10 2016
On 1/10/16 10:23 AM, anonymous wrote:On 10.01.2016 16:11, Andrei Alexandrescu wrote:...aaaaaand we're live. Congratulations and many thanks to the folks who worked on this! -- AndreiDo you have a PR in place yet?Here we go: https://github.com/D-Programming-Language/dlang.org/pull/1187
Jan 10 2016
On Sunday, 10 January 2016 at 17:17:44 UTC, Andrei Alexandrescu wrote:On 1/10/16 10:23 AM, anonymous wrote:Congratulations to everyone who's worked on this! What is the canonical way to report bugs on the website? On mobile, the red "your code here" merges with the code itself.On 10.01.2016 16:11, Andrei Alexandrescu wrote:...aaaaaand we're live. Congratulations and many thanks to the folks who worked on this! -- AndreiDo you have a PR in place yet?Here we go: https://github.com/D-Programming-Language/dlang.org/pull/1187
Jan 10 2016
On 10.01.2016 19:04, Saurabh Das wrote:What is the canonical way to report bugs on the website?Website bugs go into the same bug tracker as compiler and library bugs: https://issues.dlang.org/ Select "dlang.org" for component.On mobile, the red "your code here" merges with the code itself.Yeah, that's not good. I'm not sure what the best fix for this would be. Do you have anything in mind?
Jan 10 2016
On Sunday, 10 January 2016 at 22:11:51 UTC, anonymous wrote:On 10.01.2016 19:04, Saurabh Das wrote:OK. I'll report issues there. Will do a thorough review later this week.What is the canonical way to report bugs on the website?Website bugs go into the same bug tracker as compiler and library bugs: https://issues.dlang.org/ Select "dlang.org" for component.Move the "your code here" to next to the buttons would be a good move. Alternatively, fade out the code below and hide the "your code here" when the box is in focus.On mobile, the red "your code here" merges with the code itself.Yeah, that's not good. I'm not sure what the best fix for this would be. Do you have anything in mind?
Jan 10 2016
On Sunday, 10 January 2016 at 17:17:44 UTC, Andrei Alexandrescu wrote:On 1/10/16 10:23 AM, anonymous wrote:anonymous, thank you for the great work and congratulations on getting it merged and live. Andrei, I am once again disappointed and frustrated at your attitude towards your fellow dlang.org maintainers. Please allow proper time for code review for pull requests, but at this point I feel like talking to a wall.On 10.01.2016 16:11, Andrei Alexandrescu wrote:...aaaaaand we're live. Congratulations and many thanks to the folks who worked on this! -- AndreiDo you have a PR in place yet?Here we go: https://github.com/D-Programming-Language/dlang.org/pull/1187
Jan 10 2016
On 1/10/16 1:05 PM, Vladimir Panteleev wrote:Andrei, I am once again disappointed and frustrated at your attitude towards your fellow dlang.org maintainers. Please allow proper time for code review for pull requests, but at this point I feel like talking to a wall.You're right, sorry about getting too enthusiastic. Should we undo? -- Andrei
Jan 10 2016
On 2016-01-10 21:23, Andrei Alexandrescu wrote:You're right, sorry about getting too enthusiastic. Should we undo? -- AndreiThat depends on how many new issues have appeared, how much trouble they cause and how much trouble it is do a rollback. It might be easier to roll forward. -- /Jacob Carlborg
Jan 10 2016
On Sunday, 10 January 2016 at 17:17:44 UTC, Andrei Alexandrescu wrote:On 1/10/16 10:23 AM, anonymous wrote:Congrats! This looks great!On 10.01.2016 16:11, Andrei Alexandrescu wrote:...aaaaaand we're live. Congratulations and many thanks to the folks who worked on this! -- AndreiDo you have a PR in place yet?Here we go: https://github.com/D-Programming-Language/dlang.org/pull/1187
Jan 10 2016
On Sunday, 10 January 2016 at 19:50:40 UTC, cym13 wrote:On Sunday, 10 January 2016 at 17:17:44 UTC, Andrei Alexandrescu wrote:I like it! It's a vast improvement. My one criticism would be that the logo is far too small. Well done!On 1/10/16 10:23 AM, anonymous wrote:Congrats! This looks great!On 10.01.2016 16:11, Andrei Alexandrescu wrote:...aaaaaand we're live. Congratulations and many thanks to the folks who worked on this! -- AndreiDo you have a PR in place yet?Here we go: https://github.com/D-Programming-Language/dlang.org/pull/1187
Jan 10 2016
On Sunday, 10 January 2016 at 17:17:44 UTC, Andrei Alexandrescu wrote:On 1/10/16 10:23 AM, anonymous wrote:That's awesome. Now : - I have no idea what the code sample is doing. The code sample is not for me or anyone that already knows D, but for newcomer that wonder what the hell D is about. If I can't understand it at first glance, then it is missing it's goal BY FAR. - Learn barely make the cut on my 15' monitor. That's way too low. If one doesn't know D, one doesn't care about news, community or whatever. - Widget are still broken on https. - The download button is small while surrounded by wasted grey area. BIG FAT DOWNLOAD WANTED, DEAD OR ALIVE. - Please don't make me click on the menus. You can also make them work with pure CSS using :hover - A light touch of green would make the page much nicer (complementary color, all that good fun). - Look and feel of packages and forum need to follow. While I complains like a grumpy old man, I'd like to congrats people that makes this happen. This is very good for D. Good job.On 10.01.2016 16:11, Andrei Alexandrescu wrote:...aaaaaand we're live. Congratulations and many thanks to the folks who worked on this! -- AndreiDo you have a PR in place yet?Here we go: https://github.com/D-Programming-Language/dlang.org/pull/1187
Jan 10 2016
On 10 January 2016 at 22:14, deadalnix via Digitalmars-d < digitalmars-d puremagic.com> wrote:On Sunday, 10 January 2016 at 17:17:44 UTC, Andrei Alexandrescu wrote:I echo this, and would add a further point that you should have tested all sub-domains before uploading. Release archive is not looking well. http://downloads.dlang.org/On 1/10/16 10:23 AM, anonymous wrote:That's awesome. Now : - I have no idea what the code sample is doing. The code sample is not for me or anyone that already knows D, but for newcomer that wonder what the hell D is about. If I can't understand it at first glance, then it is missing it's goal BY FAR. - Learn barely make the cut on my 15' monitor. That's way too low. If one doesn't know D, one doesn't care about news, community or whatever. - Widget are still broken on https. - The download button is small while surrounded by wasted grey area. BIG FAT DOWNLOAD WANTED, DEAD OR ALIVE. - Please don't make me click on the menus. You can also make them work with pure CSS using :hover - A light touch of green would make the page much nicer (complementary color, all that good fun). - Look and feel of packages and forum need to follow. While I complains like a grumpy old man, I'd like to congrats people that makes this happen. This is very good for D. Good job.On 10.01.2016 16:11, Andrei Alexandrescu wrote:...aaaaaand we're live. Congratulations and many thanks to the folks who worked on this! -- AndreiDo you have a PR in place yet?Here we go: https://github.com/D-Programming-Language/dlang.org/pull/1187
Jan 10 2016
On Sunday, 10 January 2016 at 21:18:46 UTC, Iain Buclaw wrote:I echo this, and would add a further point that you should have tested all sub-domains before uploading. Release archive is not looking well. http://downloads.dlang.org/Wow. Man I don't want to be too harsh, but that was pretty lame. I mean... put the site on the air without testing? JohnCK.
Jan 10 2016
On Sunday, 10 January 2016 at 21:46:03 UTC, JohnCK wrote:On Sunday, 10 January 2016 at 21:18:46 UTC, Iain Buclaw wrote:Note that this url shouldn't even exist: the link on the main page for the download section points to http://dlang.org/download.html . I believe it is a left-over from a previous version.I echo this, and would add a further point that you should have tested all sub-domains before uploading. Release archive is not looking well. http://downloads.dlang.org/Wow. Man I don't want to be too harsh, but that was pretty lame. I mean... put the site on the air without testing? JohnCK.
Jan 10 2016
On 10.01.2016 23:03, cym13 wrote:Note that this url shouldn't even exist: the link on the main page for the download section points to http://dlang.org/download.html . I believe it is a left-over from a previous version.downloads.dlang.org is linked from download.html ("Release Archive"). So yeah, we dropped the ball on that one.
Jan 10 2016
On 1/10/16 4:46 PM, JohnCK wrote:On Sunday, 10 January 2016 at 21:18:46 UTC, Iain Buclaw wrote:We're either too quick or too slow :o). https://github.com/D-Programming-Language/dlang.org/pull/1189 AndreiI echo this, and would add a further point that you should have tested all sub-domains before uploading. Release archive is not looking well. http://downloads.dlang.org/Wow. Man I don't want to be too harsh, but that was pretty lame. I mean... put the site on the air without testing?
Jan 10 2016
On 10.01.2016 22:18, Iain Buclaw via Digitalmars-d wrote:I echo this, and would add a further point that you should have tested all sub-domains before uploading. Release archive is not looking well. http://downloads.dlang.org/Uhm, where can I fix that? downloads.dlang.org isn't part of the of dlang.org repository, is it?
Jan 10 2016
First of all, the site looks better than the old version. Congratulations and now the criticism: I don't want to hurt anybody's feelings. But look the DMD's Image compared to GDC and LDC: http://i.imgur.com/TrnuxcB.jpg Really looks like a joke. I would say this seems more like 90's but I have doubt if it's older than that. Please let's go change that. JohnCK.
Jan 10 2016
On Sunday, 10 January 2016 at 22:46:34 UTC, JohnCK wrote:First of all, the site looks better than the old version. Congratulations and now the criticism: I don't want to hurt anybody's feelings. But look the DMD's Image compared to GDC and LDC: http://i.imgur.com/TrnuxcB.jpg Really looks like a joke. I would say this seems more like 90's but I have doubt if it's older than that. Please let's go change that. JohnCK.It actually seems sort of fitting ; )
Jan 10 2016
On 10 January 2016 at 23:46, JohnCK via Digitalmars-d < digitalmars-d puremagic.com> wrote:First of all, the site looks better than the old version. Congratulations and now the criticism: I don't want to hurt anybody's feelings. But look the DMD's Image compared to GDC and LDC: http://i.imgur.com/TrnuxcB.jpg Really looks like a joke. I would say this seems more like 90's but I have doubt if it's older than that. Please let's go change that. JohnCK.Don't mock D-man. He will get you in your dreams. :-)
Jan 10 2016
On Sunday, 10 January 2016 at 22:46:34 UTC, JohnCK wrote:First of all, the site looks better than the old version. Congratulations and now the criticism: I don't want to hurt anybody's feelings. But look the DMD's Image compared to GDC and LDC: http://i.imgur.com/TrnuxcB.jpg Really looks like a joke. I would say this seems more like 90's but I have doubt if it's older than that. Please let's go change that. JohnCK.I kinda like it :) It's better than that inbred bucktoothed gopher thing Go has for a mascot...it is all subjective. bye, lobo
Jan 10 2016
On 10 January 2016 at 23:33, anonymous via Digitalmars-d < digitalmars-d puremagic.com> wrote:On 10.01.2016 22:18, Iain Buclaw via Digitalmars-d wrote:This is on Amazon S3. Brad, this is your domain. Can you have a look? (Not sure if you monitor your emails :-)I echo this, and would add a further point that you should have tested all sub-domains before uploading. Release archive is not looking well. http://downloads.dlang.org/Uhm, where can I fix that? downloads.dlang.org isn't part of the of dlang.org repository, is it?
Jan 10 2016
On 1/10/2016 3:09 PM, Iain Buclaw via Digitalmars-d wrote:On 10 January 2016 at 23:33, anonymous via Digitalmars-d <digitalmars-d puremagic.com <mailto:digitalmars-d puremagic.com>> wrote: On 10.01.2016 22:18, Iain Buclaw via Digitalmars-d wrote: I echo this, and would add a further point that you should have tested all sub-domains before uploading. Release archive is not looking well. http://downloads.dlang.org/ Uhm, where can I fix that? downloads.dlang.org <http://downloads.dlang.org> isn't part of the of dlang.org <http://dlang.org> repository, is it? This is on Amazon S3. Brad, this is your domain. Can you have a look? (Not sure if you monitor your emails :-)These days I just pay for it. Our very capable release manager manages the content of it.
Jan 10 2016
On 10.01.2016 22:14, deadalnix wrote:- Learn barely make the cut on my 15' monitor. That's way too low. If one doesn't know D, one doesn't care about news, community or whatever.We can shuffle things around, of course. One alternative: Learn News Documentation Community Packages Contribute http://i.imgur.com/8mQj0rg.png This would make Learn the most prominent item. There is an empty void between Learn and Documentation. It could be filled by putting more into Learn. I don't know what to write there, though. This would sort of split the items in a consumer oriented left column and a contributor oriented right column. Which makes me think that I'm over-thinking this.- Please don't make me click on the menus. You can also make them work with pure CSS using :hoverI think it was Adam who spoke out against :hover menus, preferring to click instead. So we're at 1:1 now, I guess?
Jan 10 2016
On 2016-01-11 00:31, anonymous wrote:I think it was Adam who spoke out against :hover menus, preferring to click instead. So we're at 1:1 now, I guess?Do both? -- /Jacob Carlborg
Jan 11 2016
On Sunday, 10 January 2016 at 23:31:07 UTC, anonymous wrote:On 10.01.2016 22:14, deadalnix wrote:No, nothing more needs to be added. Things needs to be removed, not added. I tested on a 15" screen, not even on a small screen.- Learn barely make the cut on my 15' monitor. That's way too low. If one doesn't know D, one doesn't care about news, community or whatever.We can shuffle things around, of course. One alternative: Learn News Documentation Community Packages Contribute http://i.imgur.com/8mQj0rg.png This would make Learn the most prominent item. There is an empty void between Learn and Documentation. It could be filled by putting more into Learn. I don't know what to write there, though.:hover is pretty much mandatory. Website need to work without JS.- Please don't make me click on the menus. You can also make them work with pure CSS using :hoverI think it was Adam who spoke out against :hover menus, preferring to click instead. So we're at 1:1 now, I guess?
Jan 11 2016
On 11.01.2016 13:54, deadalnix wrote:No, nothing more needs to be added. Things needs to be removed, not added. I tested on a 15" screen, not even on a small screen.As far as I understand, you're saying that Learn is too far down. I'm saying we can fix that by moving it up to the first row. That would fix the problem, right? I don't see how adding some lines to Learn would be problematic then.:hover is pretty much mandatory. Website need to work without JS.The site works without JS. Not as smoothly, but it works.
Jan 11 2016
On Monday, 11 January 2016 at 12:54:46 UTC, deadalnix wrote:On Sunday, 10 January 2016 at 23:31:07 UTC, anonymous wrote:If there was a very slight border around each section (Learn, News, Documentation etc) then that gap between Learn and Documentation wouldn't look so... empty?On 10.01.2016 22:14, deadalnix wrote:No, nothing more needs to be added. Things needs to be removed, not added. I tested on a 15" screen, not even on a small screen.- Learn barely make the cut on my 15' monitor. That's way too low. If one doesn't know D, one doesn't care about news, community or whatever.We can shuffle things around, of course. One alternative: Learn News Documentation Community Packages Contribute http://i.imgur.com/8mQj0rg.png This would make Learn the most prominent item. There is an empty void between Learn and Documentation. It could be filled by putting more into Learn. I don't know what to write there, though.What was Adams gripe with :hover? I can't see a problem with it, as long as clicking still works as it does now (for mobile).:hover is pretty much mandatory. Website need to work without JS.- Please don't make me click on the menus. You can also make them work with pure CSS using :hoverI think it was Adam who spoke out against :hover menus, preferring to click instead. So we're at 1:1 now, I guess?
Jan 11 2016
On Monday, 11 January 2016 at 13:18:26 UTC, wobbles wrote:What was Adams gripe with :hover? I can't see a problem with it, as long as clicking still works as it does now (for mobile).I click on my URL bar and punch in "interesting-site.com". It loads and I move my mouse down to a link or text field that I actually want on the page and click... But as the mouse went down from the address bar to the site, I happened to pass over a hover menu. My click is now intercepted and I'm sent to some entirely different page. Really annoying. (My bank's website had a login right below a hover menu, they have fixed it recently, but for the longest time, I'd want to log in but accidentally be sent to the bank officers list instead!) Or, I'm trying to copy something from a hover element and the page size suddenly changes with it being there... which now puts my mouse pointer outside the hover, which causes it to disappear, which changes the page size again, and now I'm just lost. (A lot of web sites assume the page will be pixel-identical on all screens, but I disable web fonts, so your menus are often not exactly the same size on my screen...) Similarly, something near the edge of a hover can be really hard to click with shaky hands, or sometimes errant margins on hovers (you'd think debugging would catch this, but I see it on live sites too, including big ones like Facebook) mean mousing over the gap to get to a link causes the link to disappear! Really frustrating. I'd imagine it is even worse if you have poor dexterity in general, so there's the accessibility aspect too. There's also no such thing as hover on devices without a mouse, which used to be just fossils like me using our lynx browser, but now includes a large number of people on the touch screens (though I question how many of them are actually doing programming so I don't think we should optimize specifically for them, but sometimes new users will check out a language mentioned to them on such a device so we don't want to leave them completely out either.) Of course, a click fallback handles those people. But even when - especially when - I have a device that supports hover, I dislike it. I think the drop down list is completely worthless on dlang.org anyway. Things moving around are harder to locate than a static thing, your spacial memory leads you to the wrong place then. I'd rather have a single click bring you to an info page with the other links.
Jan 11 2016
On Monday, 11 January 2016 at 14:27:51 UTC, Adam D. Ruppe wrote:On Monday, 11 January 2016 at 13:18:26 UTC, wobbles wrote:Yeah, I can see why that is an annoyance. But there is ways around it, like using transition-delay:0.200s [1] (or some other time that's quite small, so it doesn't impact the user actually trying to look at the drop down menu). That will prevent any annoying issues arising from moving the mouse across the web page.What was Adams gripe with :hover? I can't see a problem with it, as long as clicking still works as it does now (for mobile).I click on my URL bar and punch in "interesting-site.com". It loads and I move my mouse down to a link or text field that I actually want on the page and click... But as the mouse went down from the address bar to the site, I happened to pass over a hover menu. My click is now intercepted and I'm sent to some entirely different page. Really annoying. (My bank's website had a login right below a hover menu, they have fixed it recently, but for the longest time, I'd want to log in but accidentally be sent to the bank officers list instead!) Or, I'm trying to copy something from a hover element and the page size suddenly changes with it being there... which now puts my mouse pointer outside the hover, which causes it to disappear, which changes the page size again, and now I'm just lost. (A lot of web sites assume the page will be pixel-identical on all screens, but I disable web fonts, so your menus are often not exactly the same size on my screen...) Similarly, something near the edge of a hover can be really hard to click with shaky hands, or sometimes errant margins on hovers (you'd think debugging would catch this, but I see it on live sites too, including big ones like Facebook) mean mousing over the gap to get to a link causes the link to disappear! Really frustrating. I'd imagine it is even worse if you have poor dexterity in general, so there's the accessibility aspect too. There's also no such thing as hover on devices without a mouse, which used to be just fossils like me using our lynx browser, but now includes a large number of people on the touch screens (though I question how many of them are actually doing programming so I don't think we should optimize specifically for them, but sometimes new users will check out a language mentioned to them on such a device so we don't want to leave them completely out either.) Of course, a click fallback handles those people. But even when - especially when - I have a device that supports hover, I dislike it.I think the drop down list is completely worthless on dlang.org anyway. Things moving around are harder to locate than a static thing, your spacial memory leads you to the wrong place then. I'd rather have a single click bring you to an info page with the other links.The above solution doesn't solve this of course, as you just think having a drop-down is a bad design decision :) How else would you lay it out? I dont think you could put all the content in that top bar pre-expanded - so you'd have all the menus on the left as it is on the current site? [1] http://dabblet.com/gist/1498446
Jan 11 2016
On Monday, 11 January 2016 at 14:54:12 UTC, wobbles wrote:How else would you lay it out? I dont think you could put all the content in that top bar pre-expanded - so you'd have all the menus on the left as it is on the current site?I think the left menu on the current site is of limited value too. It is really hard to find what I'm actually looking for. (The organization is weird. To me, "D reference" and "standard library" ought to be the same, for example, and why is bug tracker under community?) I'd prefer to simplify it to like 5 menu items, each of which leads to a new page that can further break it down, using the whole screen to lay it out. Really, one of my biggest worries with dlang.org isn't the color scheme, but rather I feel like everything is cramped and content takes a back seat to cramming it all in. That's not to say we need infinite whitespace like so many new sites, I just don't think everything needs to be on every page.
Jan 11 2016
On Monday, 11 January 2016 at 15:06:40 UTC, Adam D. Ruppe wrote:On Monday, 11 January 2016 at 14:54:12 UTC, wobbles wrote:Yeah, I really dislike the over use of whitespace in current trendy sites. And the constant scrolling down to view more info is annoying too (I know CSS z-layer animations are cool, but they dont need to be everywhere!!). Well, while the website is going under such tumultuous changes, is now not the time to fix all the above? Clean everything up and put everything under sane headings/sections etc?How else would you lay it out? I dont think you could put all the content in that top bar pre-expanded - so you'd have all the menus on the left as it is on the current site?I think the left menu on the current site is of limited value too. It is really hard to find what I'm actually looking for. (The organization is weird. To me, "D reference" and "standard library" ought to be the same, for example, and why is bug tracker under community?) I'd prefer to simplify it to like 5 menu items, each of which leads to a new page that can further break it down, using the whole screen to lay it out. Really, one of my biggest worries with dlang.org isn't the color scheme, but rather I feel like everything is cramped and content takes a back seat to cramming it all in. That's not to say we need infinite whitespace like so many new sites, I just don't think everything needs to be on every page.
Jan 11 2016
On Sunday, 10 January 2016 at 15:23:53 UTC, anonymous wrote:On 10.01.2016 16:11, Andrei Alexandrescu wrote:This looks gorgeous. Congratulation to our anonymous contributor!Do you have a PR in place yet?Here we go: https://github.com/D-Programming-Language/dlang.org/pull/1187
Jan 10 2016
On 01/10/2016 03:05 PM, anonymous wrote:On 09.01.2016 22:43, Andrei Alexandrescu wrote:Is there a chance to pre- (ddoc) or post-process (html) our documentation text? I can offer a hyphenation tool (http://code.dlang.org/packages/hyphenate), but wiring it up w/ our dlang.org build requires some work.On 1/8/16 5:32 PM, anonymous wrote:[...][...]5) Justified TextJustified font only looks good in conjunction with hyphenation. I'd say make text justified on browsers that support css hyphenation (all but Chrome I recall?) and left align on the others.I.e., revert the change. Done. By the way, in Ubuntu I don't see any hyphenation in Firefox. It works in Windows, though.
Jan 10 2016
On 1/10/16 4:44 PM, Martin Nowak wrote:On 01/10/2016 03:05 PM, anonymous wrote:Yeah, great tool Martin. I recall it was among the first on the dub repo. Would be great to hook it in and have it insert a bunch of "­"s. -- AndreiOn 09.01.2016 22:43, Andrei Alexandrescu wrote:Is there a chance to pre- (ddoc) or post-process (html) our documentation text? I can offer a hyphenation tool (http://code.dlang.org/packages/hyphenate), but wiring it up w/ our dlang.org build requires some work.On 1/8/16 5:32 PM, anonymous wrote:[...][...]5) Justified TextJustified font only looks good in conjunction with hyphenation. I'd say make text justified on browsers that support css hyphenation (all but Chrome I recall?) and left align on the others.I.e., revert the change. Done. By the way, in Ubuntu I don't see any hyphenation in Firefox. It works in Windows, though.
Jan 10 2016
On Sunday, 10 January 2016 at 23:23:31 UTC, Andrei Alexandrescu wrote:Yeah, great tool Martin. I recall it was among the first on the dub repo. Would be great to hook it in and have it insert a bunch of "­"s. -- AndreiIt's from 2014-Dec-11 and despite a few deprecations it still builds and passes it's tests with the latest compiler :). I could use some help on the html processing though. Wasn't there a binding for an html parser or does someone know a suitable tool?
Jan 11 2016
On Tuesday, 12 January 2016 at 01:02:44 UTC, Martin Nowak wrote:I could use some help on the html processing though. Wasn't there a binding for an html parser or does someone know a suitable tool?My dom.d in loose mode is able to read ddoc's output. Here's a skeleton program you can use to get started: --- import arsd.dom; import std.file; import std.stdio; string hyphenateText(string input) { return input; // FIXME: implement algorithm here } void doHyphenation(Element element) { if(element.hasClass("donthyphenate")) return; if(element.tagName == "script") return; // you might filter other things too if(auto tn = cast(TextNode) element) { tn.contents = hyphenateText(tn.contents); } else { foreach(child; element.childNodes) doHyphenation(child); } } void main() { auto document = new Document(); document.enableAddingSpecialTagsToDom(); // FIXME: pass a different html filename here document.parseUtf8(readText("intro.html"), false, false); doHyphenation(document.mainBody); writeln(document); } --- dom.d is available here: https://github.com/adamdruppe/arsd just download the single file, no need for anything else, it has no dependencies also available on dub: http://code.dlang.org/packages/arsd-official%3Adom/~master
Jan 11 2016
On Friday, 8 January 2016 at 22:32:59 UTC, anonymous wrote:My implementation of the redesign is pretty much complete. Check it out: http://d-ag0aep6g.rhcloud.com/ This is an implementation of a design done by one Ivan Smirnov, brought forward by Jacob Carlborg [1].Very nice work. Thank you for doing this.The dark forum widgets on the home page are in iframes. Their styling will need to be updated at the source, which is forum.dlang.org.Once this is merged, would you be OK with working together on updating the forum to the new design?2) Reviewing the code https://github.com/aG0aep6G/dlang.org/commits/Ivan-Smirnov's-redesign This is just one giant commit (the others are independent minor fixes). GitHub refuses to show the diff for the style.css file, because it's too big. Is this acceptable, or do I need to split it up somehow? If I need to split it up, any advice on how to do that?I think this is fine as it is.3) New Pages Aside from the overall style changes and menu reorganization, I also added overview pages for the articles and for the tools: http://d-ag0aep6g.rhcloud.com/articles.html http://d-ag0aep6g.rhcloud.com/tools.html They feature new text that should be proofread.Perhaps also link to (or even replace with) the wiki pages: http://wiki.dlang.org/Articles http://wiki.dlang.org/Development_tools BTW, I've been meaning to make a MediaWiki skin based on the dlang.org design for a while.4) Fonts Vladimir Panteleev has spoken out against web fonts [2]. His argument is that they can look fine on one system but bad on another. Indeed the recently changed code font on dlang.org looks pretty bad for me while the default 'monospace' looks just fine, which is why I reverted that in the redesign. The redesign uses a web font for its main font, though: Roboto Slab. It looks good for me, but I'm not able to test it on a large variety of device/OS/browser combinations. Maybe it's fine, or maybe we should stay away from web fonts categorically. I don't really have an opinion on this.It looks good here (Firefox/Linux), and I agree that it fits the design nicely. I'll agree with Andrei, let's use it unless we run into some issues.5) Justified Text Andrei loves it, everybody else hates it. I killed it as the mockup didn't have it. Is that ok, or is justified text a must?IIRC the main point of contention was hyphenation (IMO hyphenated text is unusual and harder to read on the web). I agree that if hyphenation is a must, then justified text can be an improvement, but generally it seems to be a highly situational question.6) Red For Clickables Only? Currently, the site uses red almost exclusively for clickable stuff. But it's also used as a highlight color for non-clickable things. For example in phobos signatures: The left borders of the signature boxes are red, and the documented symbol is highlighted with red. Red does not signal clickability here. I don't like that and I'd prefer to go with another color for generic highlighting, reserving red for clickable stuff.It's important to have some way to distinguish links from non-links, e.g. by underlining links (and only links). Unfortunately, in some places underlining all links doesn't work well, e.g. the "Jump to" indices in Phobos docs. I guess it's something that warrants some experimentation. Perhaps just use bold without a color change for symbol highlighting? The red borders look fine to me, I don't think they present any ambiguity.7) The Logo As requested by Andrei, this does not feature a logo change for now. I'm going to make a pull request for the slicker logo variant [3] when this is through.Ironically, the current "official" logo is in the same legal position as the current design - we never got a confirmation from its author whether and how we can use it.
Jan 09 2016
On 09.01.2016 23:24, Vladimir Panteleev wrote:On Friday, 8 January 2016 at 22:32:59 UTC, anonymous wrote:[...]Once this is merged, would you be OK with working together on updating the forum to the new design?Sure.[...]3) New PagesPerhaps also link to (or even replace with) the wiki pages: http://wiki.dlang.org/Articles http://wiki.dlang.org/Development_toolsAdded links. About replacing, let's see later.[...]6) Red For Clickables Only?Perhaps just use bold without a color change for symbol highlighting?That works pretty well with the new de-emphasized template constraints and a monospaced font (as per Jack Stouffer's request). So uncolored, bold symbols and red borders it is.
Jan 10 2016
On 09.01.2016 23:24, Vladimir Panteleev wrote:Once this is merged, would you be OK with working together on updating the forum to the new design?I wanted to have a look at DFeed, but all I get with a local clone is "Internal Server Error". After investigating a bit, I suspect that there should be a web/skel.htt file, but it's not in the repository.
Jan 11 2016
On Monday, 11 January 2016 at 11:48:18 UTC, anonymous wrote:On 09.01.2016 23:24, Vladimir Panteleev wrote:Ah, sorry, the build instructions are out of date. That file is created through the makefile (GNUmakefile).Once this is merged, would you be OK with working together on updating the forum to the new design?I wanted to have a look at DFeed, but all I get with a local clone is "Internal Server Error". After investigating a bit, I suspect that there should be a web/skel.htt file, but it's not in the repository.
Jan 11 2016
On 11.01.2016 15:58, Vladimir Panteleev wrote:Ah, sorry, the build instructions are out of date. That file is created through the makefile (GNUmakefile).Alright, after `make` it works. I've started hacking around, no road blocks so far. Looks like this at the moment: http://i.imgur.com/yjuXFBq.png Is there a way to limit the number of loaded posts? I don't need the full archive. But the newest posts would be nice; I think /frame-discussions ignores ancient posts.
Jan 11 2016
On Monday, 11 January 2016 at 19:39:51 UTC, anonymous wrote:On 11.01.2016 15:58, Vladimir Panteleev wrote:Nice. Is it responsive?Ah, sorry, the build instructions are out of date. That file is created through the makefile (GNUmakefile).Alright, after `make` it works. I've started hacking around, no road blocks so far. Looks like this at the moment: http://i.imgur.com/yjuXFBq.pngIs there a way to limit the number of loaded posts? I don't need the full archive. But the newest posts would be nice; I think /frame-discussions ignores ancient posts.Not right now unfortunately. Definitely something I need to add at some point as the volume of messages grows.
Jan 11 2016
On 12.01.2016 08:24, Vladimir Panteleev wrote:Nice. Is it responsive?As responsive as the main site. I just updated the dlang.org submodule and fixed what got broken. I'm mostly done now. Pull request is over here: https://github.com/CyberShadow/DFeed/pull/51
Jan 12 2016
On 01/12/2016 03:12 PM, anonymous wrote:On 12.01.2016 08:24, Vladimir Panteleev wrote: > Nice. Is it responsive? As responsive as the main site. I just updated the dlang.org submodule and fixed what got broken. I'm mostly done now. Pull request is over here: https://github.com/CyberShadow/DFeed/pull/51Here's the download source: https://github.com/braddr/downloads.dlang.org -- Andrei
Jan 12 2016
On Friday, 8 January 2016 at 22:32:59 UTC, anonymous wrote:My implementation of the redesign is pretty much complete. Check it out: http://d-ag0aep6g.rhcloud.com/Looks great!3) New Pages Aside from the overall style changes and menu reorganization, I also added overview pages for the articles and for the tools: http://d-ag0aep6g.rhcloud.com/articles.html http://d-ag0aep6g.rhcloud.com/tools.html They feature new text that should be proofread.Also great.4) Fonts Vladimir Panteleev has spoken out against web fonts [2]. His argument is that they can look fine on one system but bad on another. Indeed the recently changed code font on dlang.org looks pretty bad for me while the default 'monospace' looks just fine, which is why I reverted that in the redesign.One nitpick here: can you change the function signatures to use a monospace font (any will do really)? Also, can you institute this change to the function signatures as well: https://github.com/D-Programming-Language/dlang.org/pull/11695) Justified Text Andrei loves it, everybody else hates it. I killed it as the mockup didn't have it. Is that ok, or is justified text a must?See my arguments here: https://github.com/D-Programming-Language/dlang.org/pull/11526) Red For Clickables Only? Currently, the site uses red almost exclusively for clickable stuff. But it's also used as a highlight color for non-clickable things. For example in phobos signatures: The left borders of the signature boxes are red, and the documented symbol is highlighted with red. Red does not signal clickability here. I don't like that and I'd prefer to go with another color for generic highlighting, reserving red for clickable stuff.I would take the converse of your conclusion because I have to disagree with the use of red for links. People expect links to be blue and underlined and darker when they are already visited; it's one of the only design standards that exists on the web. If you change links to be blue, then you can keep red as a highlight color.
Jan 09 2016
On 09.01.2016 23:36, Jack Stouffer wrote:On Friday, 8 January 2016 at 22:32:59 UTC, anonymous wrote:[...][...]4) FontsOne nitpick here: can you change the function signatures to use a monospace font (any will do really)?Done.Also, can you institute this change to the function signatures as well: https://github.com/D-Programming-Language/dlang.org/pull/1169It's already in. You have to look at the pre-release docs. The release docs are built with an older dmd. Example:[...]5) Justified TextSee my arguments here: https://github.com/D-Programming-Language/dlang.org/pull/1152I'm going the conservative route for now, keeping the text justified. I don't think hyphenation/justification is worth the troubles, but Andrei is the one that would have to be convinced here.[...]6) Red For Clickables Only?I would take the converse of your conclusion because I have to disagree with the use of red for links. People expect links to be blue and underlined and darker when they are already visited; it's one of the only design standards that exists on the web. If you change links to be blue, then you can keep red as a highlight color.I think that standard is pretty weak, more of a default really. We want a red site, not a blue one. Links are the site's number one source of color. Blue links would make for a blue site with a red bar on top. Re visited links: I removed the :visited styling without thinking too much about it, as I don't consider it very important. Am I wrong?
Jan 10 2016
On Sunday, 10 January 2016 at 14:04:44 UTC, anonymous wrote:Example:Can I ask not to use dotted frames? It may be my eyes, but I get dizzy reading the tables. Maybe format tables like the cheat sheet at the top of the page, which I think looks beautiful. Thanks!
Jan 10 2016
On 10.01.2016 15:27, Bastiaan Veelo wrote:Can I ask not to use dotted frames?I agree that they're ugly, but they've been ugly before the redesign, too. Let's do such stuff in separate pull requests.
Jan 10 2016
On 08.01.2016 23:32, anonymous wrote:My implementation of the redesign is pretty much complete. Check it out: http://d-ag0aep6g.rhcloud.com/No blocking issues in sight so far. Time to make a pull request: https://github.com/D-Programming-Language/dlang.org/pull/1187
Jan 10 2016
Thanks and congrats! I have one issue with icons display on my laptop, although they display well on my phone: http://imgur.com/lZWgWI4 http://imgur.com/KZWBiVr Usually this kind of issues is due to my use of script blocker, but disabling it and reloading the page does not seem to fix it. Any idea?
Jan 10 2016
On 10.01.2016 21:50, mate wrote:I have one issue with icons display on my laptop, although they display well on my phone: http://imgur.com/lZWgWI4 http://imgur.com/KZWBiVr Usually this kind of issues is due to my use of script blocker, but disabling it and reloading the page does not seem to fix it. Any idea?The icons are done using FontAwesome. Do the icons work on their examples page? https://fortawesome.github.io/Font-Awesome/examples/#basic Also, what browser are you using, and what operating system?
Jan 10 2016
The icons are done using FontAwesome. Do the icons work on their examples page? https://fortawesome.github.io/Font-Awesome/examples/#basicYes.Also, what browser are you using, and what operating system?Firefox 43.0.3, on linux (Fedora).
Jan 10 2016
On Sunday, 10 January 2016 at 21:58:19 UTC, mate wrote:Your browser is probably blocking maxcdn's connection. Do you happen to use a host-level adblocker by chance?The icons are done using FontAwesome. Do the icons work on their examples page? https://fortawesome.github.io/Font-Awesome/examples/#basicYes.Also, what browser are you using, and what operating system?Firefox 43.0.3, on linux (Fedora).
Jan 10 2016
On Sunday, 10 January 2016 at 22:25:50 UTC, rsw0x wrote:On Sunday, 10 January 2016 at 21:58:19 UTC, mate wrote:Yes, you spot it! I had not noticed a separate setting in my blocker for web objects such as fonts, and their blocking was still active. I changed that setting, and it’s displaying well now. Thank youYour browser is probably blocking maxcdn's connection. Do you happen to use a host-level adblocker by chance?The icons are done using FontAwesome. Do the icons work on their examples page? https://fortawesome.github.io/Font-Awesome/examples/#basicYes.Also, what browser are you using, and what operating system?Firefox 43.0.3, on linux (Fedora).
Jan 10 2016
On 10.01.2016 16:23, anonymous wrote:https://github.com/D-Programming-Language/dlang.org/pull/1187That one was pulled prematurely, and then reverted. Round 2: https://github.com/D-Programming-Language/dlang.org/pull/1190
Jan 11 2016
On Friday, 8 January 2016 at 22:32:59 UTC, anonymous wrote:My implementation of the redesign is pretty much complete. Check it out: http://d-ag0aep6g.rhcloud.com/ This is an implementation of a design done by one Ivan Smirnov, brought forward by Jacob Carlborg [1]. The dark forum widgets on the home page are in iframes. Their styling will need to be updated at the source, which is forum.dlang.org. Another external dependency is the This Week in D script. Adam, it would be nice if the `setTwid` function could take the date separately. That would allow me to word the text without having "This Week in D" there twice. Other than those two little things I consider this done. From my side it could be merged immediately. But I'm sure there are a thousand things wrong with this. Here are some topics to get you started: 1) Legalities I mentioned this before, but noone reacted. Can we use Ivan's work? Do we have his ok? Do we need it? Jacob mentioned that he can't in contact with him anymore. Is that a problem? 2) Reviewing the code https://github.com/aG0aep6G/dlang.org/commits/Ivan-Smirnov's-redesign This is just one giant commit (the others are independent minor fixes). GitHub refuses to show the diff for the style.css file, because it's too big. Is this acceptable, or do I need to split it up somehow? If I need to split it up, any advice on how to do that? 3) New Pages Aside from the overall style changes and menu reorganization, I also added overview pages for the articles and for the tools: http://d-ag0aep6g.rhcloud.com/articles.html http://d-ag0aep6g.rhcloud.com/tools.html They feature new text that should be proofread. 4) Fonts Vladimir Panteleev has spoken out against web fonts [2]. His argument is that they can look fine on one system but bad on another. Indeed the recently changed code font on dlang.org looks pretty bad for me while the default 'monospace' looks just fine, which is why I reverted that in the redesign. The redesign uses a web font for its main font, though: Roboto Slab. It looks good for me, but I'm not able to test it on a large variety of device/OS/browser combinations. Maybe it's fine, or maybe we should stay away from web fonts categorically. I don't really have an opinion on this. 5) Justified Text Andrei loves it, everybody else hates it. I killed it as the mockup didn't have it. Is that ok, or is justified text a must? 6) Red For Clickables Only? Currently, the site uses red almost exclusively for clickable stuff. But it's also used as a highlight color for non-clickable things. For example in phobos signatures: The left borders of the signature boxes are red, and the documented symbol is highlighted with red. Red does not signal clickability here. I don't like that and I'd prefer to go with another color for generic highlighting, reserving red for clickable stuff. 7) The Logo As requested by Andrei, this does not feature a logo change for now. I'm going to make a pull request for the slicker logo variant [3] when this is through. [1] http://forum.dlang.org/post/n53ps0$2j8f$1 digitalmars.com [2] http://forum.dlang.org/post/xezfeilxblfkibldvsgg forum.dlang.org [3] https://gist.github.com/aG0aep6G/0803ec5ae49f6afb0196Again, thanks for doing this. The new design overall looks much more modern and approachable. Some feedback I do have: Fonts ------- I do not have any problem with Web Fonts. In particular the web fonts created by Google are highly tested and render pretty similarly on many device/browser combinations. This is from practical experience. On the font used, Roboto Slab: I feel that the serif nature of the font makes it clash with the clean design. A sans serif font would look much better. Justified Text ---------------- I'm with Andrei on this one. Justified text is preferable to aligned text for large paragraphs which span the reading width of the page. It always makes it easier to read. For mini-paragraphs, sometimes left aligned does look better. "Your Code Here" widget ----------------------------- The widget that displays and allows you to run code in the browser has been a staple of the D website for a long time now. It's a great feature. There is one issue here: When the code length is large, it takes half the screen before any actual content begins. The grayed out header colour looks funny. I suggest displaying the first 7-9 lines of code in the box and either making the box scrollable, or making it so that clicking on the box expands it to show the entire code. The "Sort lines" example is about the right size. The "Round floating point numbers" is a bit large. PS: Sorry if there were opportunities to give feedback on this earlier and somehow I missed it. I do hope you consider this even it if comes a bit late. Thanks, Saurabh
Jan 10 2016
On Sunday, 10 January 2016 at 17:02:59 UTC, Saurabh Das wrote:[...] The grayed out header colour looks funny.I meant it looks funny when it spans half the height of the page when the example code is long. It looks fine otherwise :)
Jan 10 2016
On 10.01.2016 18:02, Saurabh Das wrote:On the font used, Roboto Slab: I feel that the serif nature of the font makes it clash with the clean design. A sans serif font would look much better.At first I felt so, too, but the font grew on me. I think it works well."Your Code Here" widget -----------------------------[...]I suggest displaying the first 7-9 lines of code in the box and either making the box scrollable, or making it so that clicking on the box expands it to show the entire code.I'd rather just put a hard limit on the length of examples. But scrollable/expandable code would be better than a large empty void below the download button.The "Sort lines" example is about the right size. The "Round floating point numbers" is a bit large.I agree that "Round floating point numbers" is a tad too long. I think it's in an acceptable area, though.
Jan 10 2016
On Friday, 8 January 2016 at 22:32:59 UTC, anonymous wrote:My implementation of the redesign is pretty much complete. Check it out: http://d-ag0aep6g.rhcloud.com/Congratulations on getting this merged!
Jan 10 2016
On Friday, 8 January 2016 at 22:32:59 UTC, anonymous wrote:My implementation of the redesign is pretty much complete. Check it out: http://d-ag0aep6g.rhcloud.com/ This is an implementation of a design done by one Ivan Smirnov, brought forward by Jacob Carlborg [1]. The dark forum widgets on the home page are in iframes. Their styling will need to be updated at the source, which is forum.dlang.org. Another external dependency is the This Week in D script. Adam, it would be nice if the `setTwid` function could take the date separately. That would allow me to word the text without having "This Week in D" there twice. Other than those two little things I consider this done. From my side it could be merged immediately.It's responsive too. sweet!! Nice layout, nice UX, reddish color is a little mmm... But just to suggest further improvement on the UX; 1.The online runner could have a label which tells what it does. Maybe change the "you code here" to "Test Code Here". 2. The top and bottom margin of the various sections (Community, Learn, etc) are more squeezed together especially on smaller viewports. 3. I think the English there is too high level for a beginner, especially the "Why D" justification?
Jan 16 2016