W3C home > Mailing lists > Public > public-webplatform@w3.org > December 2012

Re: Main landing page prototypes completed/subpage structures?/domain leads?

From: Taylor Costello <nottaylorcostello@gmail.com>
Date: Tue, 11 Dec 2012 12:54:43 -0700
Message-ID: <CA+uZHs8s9uGAi+Aa95KmQYYO=+6DF8aqARou2vvyK_rP8w12Dg@mail.gmail.com>
To: Chris Mills <cmills@opera.com>
Cc: Doug Schepers <schepers@w3.org>, "public-webplatform@w3.org" <public-webplatform@w3.org>
I don't think this is true, the template CSS is unrelated to the skin and
will not break during an update. The only time the skin would break is if
you were using a default MediaWiki skin, and then updated, and they
(MediaWiki developers) changed some of the classes. Our Common.css is not
attached to the skin and you can't alter the skin from the wiki itself, the
Common.css can only be used for templates and is not altered or changed by
updates.

On Tue, Dec 11, 2012 at 11:56 AM, Chris Mills <cmills@opera.com> wrote:

> Ack, sorry - I wasn't aware. Please let me know how to modify the skin,
> and I'll fix it.
>
> Chris Mills
> Opera Software, dev.opera.com
> W3C Fellow, web education and webplatform.org
> Author of "Practical CSS3: Develop and Design" (http://goo.gl/AKf9M)
>
> On 11 Dec 2012, at 18:13, Doug Schepers <schepers@w3.org> wrote:
>
> > Hi, Chris-
> >
> > You shouldn't modify those common files, because that blocks MediaWiki
> upgrades. You should only modify the WebPlatform skin files.  I can help
> with that.
> >
> > Regards-
> > -Doug
> >
> > On 12/11/12 1:05 PM, Chris Mills wrote:
> >> Update: I have put CSS to style my landing page topic boxes on
> >> http://docs.webplatform.org/wiki/MediaWiki:Common.css (thanks so much
> >> to Taylor for showing me this!), and refactored my HTML. So we still
> >> have HTML in the landing pages, but it is much cleaned and no longer
> >> full of horrible inline styles. This will work up until the point
> >> someone gives me a cleverer solution.
> >>
> >> So I think we are ready to go with implementing these sub page
> >> updates on the site, as soon as Seb finishes the icons (no pressure
> >> ;-) )
> >>
> >> Chris Mills Opera Software, dev.opera.com W3C Fellow, web education
> >> and webplatform.org Author of "Practical CSS3: Develop and Design"
> >> (http://goo.gl/AKf9M)
> >>
> >> On 10 Dec 2012, at 16:21, Chris Mills <cmills@opera.com> wrote:
> >>
> >>> Hi all,
> >>>
> >>> I have now created landing pages for the main WPD page and all it's
> >>> immediate subpages. So
> >>>
> >>> http://docs.webplatform.org/wiki/TEST:main_page
> >>>
> >>> Would eventually lead to
> >>>
> >>> http://docs.webplatform.org/wiki/TEST:beginners
> >>> http://docs.webplatform.org/wiki/TEST:general_concepts
> >>> http://docs.webplatform.org/wiki/TEST:html
> >>> http://docs.webplatform.org/wiki/TEST:css
> >>> http://docs.webplatform.org/wiki/concepts/accessibility
> >>> http://docs.webplatform.org/wiki/TEST:javascript
> >>> http://docs.webplatform.org/wiki/TEST:dom
> >>> http://docs.webplatform.org/wiki/TEST:svg
> >>>
> >>> Unless anyone has major objections, I suggest we stick to this
> >>> overall layout. I can then get these implements as soon as:
> >>>
> >>> * Seb finishes the first icon set * I can get help from the
> >>> template ninjas in creating me a template that will generate the
> >>> floated topic boxes. * I can get help from someone to add the CSS
> >>> to style said template. I could do this myself if someone gave me
> >>> the keys to the CSS files, and a little help with finding things.
> >>>
> >>> This leads me to follow-on questions:
> >>>
> >>> 1. What will the sub-landing pages look like? I for one think that
> >>> we don't need any special features to implement those. If the page
> >>> is just reference docs, we can auto-generate one of those sortable
> >>> tables. If the page is structured tutorials, we can manually create
> >>> a page of headings and links. If it is a combination, we can use a
> >>> combination of both. Any further thoughts? Would that do for now?
> >>>
> >>> 2. I would like to find topic domain leads for each of the major
> >>> topic areas linked to above. The domain lead for each topic would
> >>> be expected to:
> >>>
> >>> * distribute and manage work being done in each domain *
> >>> periodically check the domain material to make sure it is up to
> >>> date, changes are ok, and disputes are settled reasonably * Seek
> >>> out new people to work on the domain.
> >>>
> >>> what do people think of this idea?
> >>>
> >>> I would quite happily be domain lead for General concepts,
> >>> beginners, HTML, and CSS. But I don't have time to do all 4, so I
> >>> think i'll grab CSS and general concepts for now.
> >>>
> >>> That leaves
> >>>
> >>> beginners HTML accessibility javascript dom svg
> >>>
> >>> Any immediate takers? Where a domain is really large, like
> >>> JavaScript, I think it would be more than reasonable to have
> >>> multiple domain leads.
> >>>
> >>>
> >>> Chris Mills Open standards evangelist and dev.opera.com editor,
> >>> Opera Software Co-chair, web education community group, W3C Author
> >>> of "Practical CSS3: Develop and Design"
> >>> (
> http://my.opera.com/chrismills/blog/2012/07/12/practical-css3-my-book-is-finally-published
> )
> >>>
> >>>
> >>>
> > * Try Opera: http://www.opera.com
> >>> * Learn about the latest open standards technologies and
> >>> techniques: http://dev.opera.com * Contribute to web education:
> >>> http://www.w3.org/community/webed/
> >>>
> >>
> >>
> >
>
>
>
Received on Tuesday, 11 December 2012 19:55:12 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 May 2013 19:57:36 UTC