Hi Erin, I think a developer site (rather than a docs site) makes a lot of sense since a "developer" site implies more community orientation than just static content.
However does this imply that the developer site should adopt some more community centric content such as articles, news posts, forums for peer support, etc? Also when we say "developer", are we also including design and testing too? - Jonathan. --- Jonathan Hung / [email protected] <[email protected]> IDRC - Interaction Designer / Researcher Tel: (416) 977-6000 x3959 Fax: (416) 977-9844 On Fri, Mar 25, 2011 at 10:22 AM, Erin Yu <[email protected]> wrote: > Hi all, > > As we work through the redesign of the tech docs site, it occured to me > that what we are calling it doesn't truly represent what it really is. The > site is much more than just documentation - it is a place for developers to > explore and learn. http://docs.fluidproject.org/ > The conventional (and intuitive) name for sites like this seems to be > "Developer" rather than "Documentation". > > https://developer.mozilla.org/en-US/ > http://developers.facebook.com/ > http://developer.apple.com/ > ... etc. > > What do you think about changing the name/url of our tech docs/demo site to > developer.fluidproject.org? > > Erin > _______________________________________________________ > fluid-work mailing list - [email protected] > To unsubscribe, change settings or access archives, > see http://fluidproject.org/mailman/listinfo/fluid-work > >
_______________________________________________________ fluid-work mailing list - [email protected] To unsubscribe, change settings or access archives, see http://fluidproject.org/mailman/listinfo/fluid-work
