Re: Content for 3 Landing Pages

Jen wrote a nice writeup and invited thoughts about three top-level 
landing pages.

By your leave, I reference it here instead of inlining:
http://lists.w3.org/Archives/Public/public-webplatform/2014Jan/0061.html

==Main site home page
It would be worth having an RSS feed of the "We need help" and "here's 
the latest", so we can subscribe to a low-volume feed, so that as new 
needs arise or new site changes are made, people can be notified.

This would fill the need to keep people coming back, both to consume the 
new content, and begin a new round of help.

==Docs home page
Under the Docs landing page, note the guides[1] and tutorials[2]. These 
are for a different audience than, say, a hardcore reference page.  It 
makes me think we might want to cater to those still learning as opposed 
to someone who has been there a while and needs to refer to some minute 
detail.

[1] http://docs.webplatform.org/wiki/guides
[2] http://docs.webplatform.org/wiki/tutorials

==Get involved page
It is curious that you wrote, "are you a Spec maintainer?" because it 
reminds me of getting hooks into webplatform information.  IDEs are very 
keen on providing semantic as-you-type help.  Wouldn't it be wonderful 
to let a tool like Eclipse, instead of writing their own help system, 
hook into webplatform information to provide context-sensitive help on 
CSS, JavaScript, HTML elements, and so forth?  Maybe a year ago I asked, 
"just how free is this information?"

Remember Metcalfe's law: "The value of a telecommunications network is 
proportional to the square of the number of users of the system."  We 
can apply that.  We can say the value of webplatform will far surpass 
linear growth of users, so it's our job to prime the pump by opening up 
the information to all new groups of users (even via API lookup through 
their IDE).

Received on Friday, 17 January 2014 00:09:03 UTC