Jump to page: 1 29  
Page
Thread overview
New menus are up
Jan 20, 2015
Rikki Cattermole
Jan 20, 2015
Rikki Cattermole
Jan 20, 2015
Rikki Cattermole
Jan 20, 2015
Rikki Cattermole
Jan 21, 2015
Vladimir Panteleev
Jan 20, 2015
Vladimir Panteleev
Jan 20, 2015
Rikki Cattermole
Jan 20, 2015
Vladimir Panteleev
Jan 20, 2015
Rikki Cattermole
Jan 20, 2015
Jonas Drewsen
Jan 21, 2015
Chris
Jan 20, 2015
MattCoder
Jan 20, 2015
Phil
Jan 20, 2015
Vladimir Panteleev
Jan 20, 2015
Zach the Mystic
Jan 21, 2015
Zach the Mystic
Jan 21, 2015
Vladimir Panteleev
Jan 22, 2015
Zach the Mystic
Jan 20, 2015
Vladimir Panteleev
Jan 21, 2015
H. S. Teoh
Jan 20, 2015
Vladimir Panteleev
Jan 20, 2015
bearophile
Jan 20, 2015
Vladimir Panteleev
Jan 20, 2015
bearophile
Jan 20, 2015
Vladimir Panteleev
Jan 20, 2015
bearophile
Jan 20, 2015
Kiith-Sa
Jan 20, 2015
Vladimir Panteleev
Jan 20, 2015
ixid
Jan 20, 2015
Vladimir Panteleev
Jan 21, 2015
Vladimir Panteleev
Jan 21, 2015
Vladimir Panteleev
Jan 21, 2015
H. S. Teoh
Jan 21, 2015
weaselcat
Jan 21, 2015
weaselcat
Jan 22, 2015
weaselcat
Jan 22, 2015
H. S. Teoh
Jan 21, 2015
Jacob Carlborg
Jan 21, 2015
Jacob Carlborg
Jan 22, 2015
DaveG
Jan 21, 2015
Vladimir Panteleev
Jan 21, 2015
H. S. Teoh
Jan 22, 2015
AndyC
Jan 22, 2015
H. S. Teoh
Jan 22, 2015
Jacob Carlborg
Jan 21, 2015
ixid
Jan 21, 2015
Vladimir Panteleev
Jan 21, 2015
John Colvin
Jan 21, 2015
Tofu Ninja
Jan 21, 2015
MattCoder
Jan 21, 2015
John Colvin
Jan 21, 2015
MattCoder
Jan 21, 2015
MattCoder
January 20, 2015
Take a look at http://dlang.org. New menus are in place for the main site and library.

I think we're in a better place than before. However, there are a few things left to do. I'd very much appreciate help with those.

* New docs don't yet have the new menu implemented.

* Menu tracking works, i.e. if the URL a page matches a menu entry, then the menu will automatically open to that page and mark the entry active. However, that's rather simplistic; for example navigating http://dlang.org/statement.html does not open the "Documentation" menu because the link is not directly present.

A simple and probably desirable fix would be to just make "Language Reference" a top-level menu entry with submenus. Could one of our awesome lieutenants see to it?

* Better colors etc. are always welcome. Please submit your pull requests with screenshots so we can appreciate.


Thanks,

Andrei
January 20, 2015
On 20/01/2015 4:29 p.m., Andrei Alexandrescu wrote:
> Take a look at http://dlang.org. New menus are in place for the main
> site and library.
>
> I think we're in a better place than before. However, there are a few
> things left to do. I'd very much appreciate help with those.
>
> * New docs don't yet have the new menu implemented.
>
> * Menu tracking works, i.e. if the URL a page matches a menu entry, then
> the menu will automatically open to that page and mark the entry active.
> However, that's rather simplistic; for example navigating
> http://dlang.org/statement.html does not open the "Documentation" menu
> because the link is not directly present.
>
> A simple and probably desirable fix would be to just make "Language
> Reference" a top-level menu entry with submenus. Could one of our
> awesome lieutenants see to it?
>
> * Better colors etc. are always welcome. Please submit your pull
> requests with screenshots so we can appreciate.
>
>
> Thanks,
>
> Andrei

Say ugh, when was the last time somebody clicked the ol' "Page wiki" buttons.
Because atleast for intro, it doesn't exist.
January 20, 2015
... aand we already have a contender!

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

Looks better than dlang.org?


Andrei
January 20, 2015
On 1/19/15 7:32 PM, Rikki Cattermole wrote:
> Say ugh, when was the last time somebody clicked the ol' "Page wiki"
> buttons.
> Because atleast for intro, it doesn't exist.

Ah, it was part of the topics I wanted to touch. Looks like page wikis are largely unused, should we just ditch them?


Andrei
January 20, 2015
On Tuesday, 20 January 2015 at 03:32:38 UTC, Rikki Cattermole wrote:
> Say ugh, when was the last time somebody clicked the ol' "Page wiki" buttons.
> Because atleast for intro, it doesn't exist.

They don't need to all exist. The idea is to link to a page that anyone can create, and then anyone else can get to by clicking the same link in the page header.
January 20, 2015
On 1/19/15 7:34 PM, Vladimir Panteleev wrote:
> On Tuesday, 20 January 2015 at 03:32:38 UTC, Rikki Cattermole wrote:
>> Say ugh, when was the last time somebody clicked the ol' "Page wiki"
>> buttons.
>> Because atleast for intro, it doesn't exist.
>
> They don't need to all exist. The idea is to link to a page that anyone
> can create, and then anyone else can get to by clicking the same link in
> the page header.

I fear that newcomers finding many of those page unpopulated would think there's no activity etc. -- Andrei
January 20, 2015
On 20/01/2015 4:34 p.m., Andrei Alexandrescu wrote:
> On 1/19/15 7:32 PM, Rikki Cattermole wrote:
>> Say ugh, when was the last time somebody clicked the ol' "Page wiki"
>> buttons.
>> Because atleast for intro, it doesn't exist.
>
> Ah, it was part of the topics I wanted to touch. Looks like page wikis
> are largely unused, should we just ditch them?
>
>
> Andrei

Yes please.
If we feel the need to link/reference them on a page to page basis, we can.

I would also recommend the page edit button. Switch it for a 'fork me' github ribbon [0].

[0] https://github.com/blog/273-github-ribbons
January 20, 2015
On 1/19/15 7:36 PM, Rikki Cattermole wrote:
> On 20/01/2015 4:34 p.m., Andrei Alexandrescu wrote:
>> On 1/19/15 7:32 PM, Rikki Cattermole wrote:
>>> Say ugh, when was the last time somebody clicked the ol' "Page wiki"
>>> buttons.
>>> Because atleast for intro, it doesn't exist.
>>
>> Ah, it was part of the topics I wanted to touch. Looks like page wikis
>> are largely unused, should we just ditch them?
>>
>>
>> Andrei
>
> Yes please.
> If we feel the need to link/reference them on a page to page basis, we can.
>
> I would also recommend the page edit button. Switch it for a 'fork me'
> github ribbon [0].
>
> [0] https://github.com/blog/273-github-ribbons

This was up for a little while, then it was pulled because of reasons I don't remember. Or at least talked about. -- Andrei
January 20, 2015
On 20/01/2015 4:36 p.m., Andrei Alexandrescu wrote:
> On 1/19/15 7:34 PM, Vladimir Panteleev wrote:
>> On Tuesday, 20 January 2015 at 03:32:38 UTC, Rikki Cattermole wrote:
>>> Say ugh, when was the last time somebody clicked the ol' "Page wiki"
>>> buttons.
>>> Because atleast for intro, it doesn't exist.
>>
>> They don't need to all exist. The idea is to link to a page that anyone
>> can create, and then anyone else can get to by clicking the same link in
>> the page header.
>
> I fear that newcomers finding many of those page unpopulated would think
> there's no activity etc. -- Andrei

Lets be honest here. If changes need to occur to those pages, they get PR'd and fixed.
They don't get discussed on the wiki. They'll get discussed on the N.G.

So I'm 100% in agreement with Andrei, it'll cause more problems then its worth. Plus it makes it look like its a CMS, no thanks.. its not.
January 20, 2015
On 20/01/2015 4:37 p.m., Andrei Alexandrescu wrote:
> On 1/19/15 7:36 PM, Rikki Cattermole wrote:
>> On 20/01/2015 4:34 p.m., Andrei Alexandrescu wrote:
>>> On 1/19/15 7:32 PM, Rikki Cattermole wrote:
>>>> Say ugh, when was the last time somebody clicked the ol' "Page wiki"
>>>> buttons.
>>>> Because atleast for intro, it doesn't exist.
>>>
>>> Ah, it was part of the topics I wanted to touch. Looks like page wikis
>>> are largely unused, should we just ditch them?
>>>
>>>
>>> Andrei
>>
>> Yes please.
>> If we feel the need to link/reference them on a page to page basis, we
>> can.
>>
>> I would also recommend the page edit button. Switch it for a 'fork me'
>> github ribbon [0].
>>
>> [0] https://github.com/blog/273-github-ribbons
>
> This was up for a little while, then it was pulled because of reasons I
> don't remember. Or at least talked about. -- Andrei

That would have been before my time then.
I can understand it would interfere with twitter/mobile and pdf ext. generation.

The only reason I suggest it is because it is what people expect these days. And would advertise that we are passionately open source.
« First   ‹ Prev
1 2 3 4 5 6 7 8 9