Added a resources page on community.ko

[Olivier Churlaud]

Hi

Sorry I misused the word namespace. I meant subpage.

I felt like the issue was not the number of subpage but the name of the page.

Would community.kde.org/Talks_and_papers work?

If not, I'm not sure to understand what you would prefer, as community.ko/Talks/Resources doesn't bring much (talks would be empty and everything would be in Resources)

I'm not trying to do "my way" (I don't have one) but to keep with the work we did during the sprint at Cern, in the same spirit and structure.

Cheers
Olivier 

Le 10 octobre 2017 22:25:01 GMT+02:00, Jaroslaw Staniek <staniek at kde.org> a écrit :
>On 10 October 2017 at 21:48, Olivier Churlaud <olivier at churlaud.com>
>wrote:
>> Hi
>>
>> Le lundi 9 octobre 2017, 21:56:42 CEST Jaroslaw Staniek a écrit :
>>> On 9 October 2017 at 21:49, Olivier Churlaud <olivier at churlaud.com>
>wrote:
>>> > Hi,
>>> >
>>> > I don't know if it changes much, but it adds another layer in the
>page
>>> > tree.>
>>> >  I can imagine that someone could write an essay and link it there
>as
>>> >
>>> > well...
>>>
>>> In wiki terms it adds a subpage. Navigating will be clean as soon as
>>> https://community.kde.org/Talks exists too (a home page for the
>>> topic). This is usually just the right order of adding hierarchy
>pages.
>>> Old-school wikis (also KDE's old wiki) used an all-global approach
>>> with bad consequences for browsing experience.
>>>
>>
>> You are right in theory. The issue with that is maintainance. Imagine
>that one
>> day you want to reorganize : if you have too many layers it will be
>very
>> difficult, that's why we chose to use one or two namespace (be it
>resources or
>> Talk) and put eveything below, at the same level. The logic will be
>given by
>> the path people will follow through their clicks.
>>
>> If Talks is better, then let's change that this way. To be more
>precise, I
>> would do "Talks and Papers".
>>
>> Is it ok this way? if so, I'll change it next week on tuesday.
>
>I am not asking for too many layers but more than zero and I am far
>from theory. :)
>Please excuse me sharing some practice that can be maybe of general
>value.
>
>Picking right and short title / URL is the way to avoid later
>modification. Moving and removing pages can be performed by admins.
>A good start for a new simple page is to have it named in a generic
>way and have with everything inside. You have Talks Resources but
>shall notice we have no Talks page so this is the point to start. You
>can add Resources section there and reorganize later if the page is
>huge. This is also how wikimedia's projects work, then extract to
>content to separate pages if it's already too big. Except they can
>afford (staff) to use graphs (via Mediawiki Category) exclusively, not
>just subpage trees.
>
>The mediawiki's search engine favors page titles so if you use
>Resources we will all be getting them in results also while looking
>for Qt Resources (QRC), KDE PIM resources and so on. [1]
>
>I am not sure you used the namespace anywhere in this context:
>https://www.mediawiki.org/wiki/Help:Namespaces or it is just
>accidental. We've covered subpages, pages, sections and categories,
>not namespaces which we IMHO should avoid.
>
>Cheers.
>
>[1]
>https://community.kde.org/index.php?search=Resources&title=Special%3ASearch&fulltext=1
>
>> Cheers,
>> Olivier
>>> > Le 8 oct. 2017 à 21:29, Jaroslaw Staniek <staniek at kde.org> a écrit
>:
>>> >
>>> > On Sunday, 8 October 2017, Olivier Churlaud <olivier at churlaud.com>
>wrote:
>>> >> Hi,
>>> >>
>>> >> I wanted to share with you that I added a page for KDE talks and
>>> >> resources
>>> >> on
>>> >> https://community.kde.org/Resources
>>> >
>>> > Thanks, to improve navigation how about Talks/Resources?
>>> >
>>> >> It is linked from the main page. It can be a good way to have
>here
>>> >> resources
>>> >> produced by the community. It's currently a unique page with
>bullet
>>> >> points, we
>>> >> can think about having more structure in the future if this feels
>needed.
>>> >>
>>> >> I attached there my impress template, based on the one Volker
>sent the
>>> >> other
>>> >> day. Attach yours as well if you want to share it.
>>> >>
>>> >> Cheers,
>>> >> Olivier
>>> >
>>> > --
>>> > regards, Jaroslaw Staniek
>>> >
>>> > KDE:
>>> > : A world-wide network of software engineers, artists, writers,
>>> > : translators
>>> > : and facilitators committed to Free Software development -
>http://kde.org
>>> >
>>> > Calligra Suite:
>>> > : A graphic art and office suite - http://calligra.org
>>> >
>>> > Kexi:
>>> > : A visual database apps builder - http://calligra.org/kexi
>>> >
>>> > Qt Certified Specialist:
>>> > : http://www.linkedin.com/in/jstaniek
>>
>>
>
>
>
>-- 
>regards, Jaroslaw Staniek
>
>KDE:
>: A world-wide network of software engineers, artists, writers,
>translators
>: and facilitators committed to Free Software development -
>http://kde.org
>Calligra Suite:
>: A graphic art and office suite - http://calligra.org
>Kexi:
>: A visual database apps builder - http://calligra.org/kexi
>Qt Certified Specialist:
>: http://www.linkedin.com/in/jstaniek

-- 
Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma brièveté.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-community/attachments/20171010/bd83fae0/attachment.htm>