For what it's worth, if we would be happy building a simple landing page to
introduce people to coworking and how to learn more and how to get involved,
then we don't need it to be centralized-- just visible.
That's what I had in mind when I bought whatiscoworking.com (which currently
just sports an inside joke as a placeholder).
It can exist separate from the central movement, but loosely joined, and
perhaps referred to at the top of the wiki and blog ("new to coworking?
click here")
Very simple:
1. What is coworking? (Recommendation: don't define it, describe it.
Sidestep that landmine.)
2. How do I get started?
3. How do I help organize?
We already have these resources started on the wiki, so I think it's more a
matter of presentation. Properly holding people's hands through
understanding what coworking is about.
Wouldn't be half bad to have something like wtfistwitter.com too, and have
multiple perspectives.
T
On Fri, Nov 7, 2008 at 5:19 PM, Alex Hillman
<[EMAIL PROTECTED]>wrote:
> I'm concerned this is a severe overcomplication of the needs for producing
> the simple "site" that is needed as a landing for coworking newbs.
>
> An 8 person team to build 1 or two page site is not something I'm
> comfortable getting involved with. I know how those projects go, and it's
> not a productive environment.
>
> -Alex
> --
> -----
> --
> -----
> Alex Hillman
> im always developing something
> digital: [EMAIL PROTECTED]
> visual: www.dangerouslyawesome.com
> local: www.indyhall.org
>
>
>
> On Fri, Nov 7, 2008 at 5:11 PM, nickf <[EMAIL PROTECTED]> wrote:
>
>>
>> On Nov 7, 9:54 am, "Jacob Sayles" <[EMAIL PROTECTED]> wrote:
>> > Once we've figured out WHAT we
>> > are building then we can try and work on WHO is going to build it, and
>> > HOW it will be maintained over time. We are awash in amazing,
>> > talented people so I'm confident we can make this happen.
>>
>> I agree. We do need to define who will be doing what, etc. To keep
>> things simple here are the roles I see we need*:
>>
>> - Project Lead to manage the overall project
>> - Information Architect to define the structure of the site and pages
>> - Copywriter to write the content for the site if needed
>> - Web Designer to create the visual design of the site
>> - Front-End Web Developer to build the XHTML/CSS pages and perhaps
>> some of JavaScript/AJAX (if needed)
>> - Back-End Web Developer to code the pages if needed, API integration,
>> setup the CMS (if we need one), etc
>> - Server/Host Admin to manage and maintain the server
>> - Web Curator to maintain the site long term, delete any spam, address
>> bugs found later on, etc
>>
>> * Note: these rolls could be combined depending on the skills of the
>> individual volunteering to take on these rolls, I often find designers
>> who can do front-end dev, or backend-devs who like to do front-end dev
>> as well, etc. Certainly we don't need to have one person per roll, in
>> fact I would like to see the team be as small as possible but
>> effective.
>>
>> That said, any takers? :) I'd put my name in the hat for IA unless
>> someone else also wants to do it. I'd put my name in for project lead
>> but I feel there are probably others out there with more experience
>> and understanding of coworking than I have.
>>
>>
>> > P.S. Your space looks great and thank you for inviting me to the news
>> interview.
>>
>> No problem, I am hoping this local news coverage brings more exposure
>> to all of coworking in Seattle and beyond. It was great to have you
>> there with your experience answering the questions I couldn't as a
>> newbie coworking space owner.
>>
>> - Nick
>>
>>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Coworking" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/coworking?hl=en
-~----------~----~----~----~------~----~------~--~---
