<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: So how does it work? (v. rough braindump.)</title>
	<atom:link href="http://www.flamingdesks.com/blog/2008/07/21/so-how-does-it-work/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.flamingdesks.com/blog/2008/07/21/so-how-does-it-work/</link>
	<description>...that might turn into the world's leading desk-sharing/networking service!</description>
	<pubDate>Sat, 19 May 2012 17:41:03 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: The Turk</title>
		<link>http://www.flamingdesks.com/blog/2008/07/21/so-how-does-it-work/#comment-26</link>
		<dc:creator>The Turk</dc:creator>
		<pubDate>Thu, 07 Aug 2008 10:24:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.flamingdesks.com/blog/?p=18#comment-26</guid>
		<description>Hello. Where will I be able to get a moco choco cappuccino???

Those are crucial to my work.</description>
		<content:encoded><![CDATA[<p>Hello. Where will I be able to get a moco choco cappuccino???</p>
<p>Those are crucial to my work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dfletcher</title>
		<link>http://www.flamingdesks.com/blog/2008/07/21/so-how-does-it-work/#comment-4</link>
		<dc:creator>dfletcher</dc:creator>
		<pubDate>Tue, 22 Jul 2008 11:26:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.flamingdesks.com/blog/?p=18#comment-4</guid>
		<description>** HOME PAGE **
I'd like to see the two areas : “Share a desk” and “Find a desk” with a form so people can get started right there.  

** REGISTRATION **
Let's not stop people searching for desks by asking them to register.  Registration for 'Flamers' should be if they want to do something like communicate with a Desk owner (via the site), rate a desk, comment on a desk
Email confirmation : probably is needed.  We can let them log in but limit functionality without the confirmation.

** SHARE PAGE **
Not sure about the new entry for each desk or 'number available' argument.  Would probably opt for a half-way house : when you put your first desk up it takes the basic details of your company : name, address, brief description of company / office and then the details of the desk : photo, description, availability.  Once it's been saved (or even at the bottom of this page) we have a 'Add another desk at this office' link, to add multiple desks.  Then we can have a single office, multiple desks with a photo, availability and description (all optional) of each.  This way, you can add multiple desks quickly by hitting the link again and again, and if you want to go to town you can put more details in for each one.  I'll show you an interface for something like this that we've done recently (Note to self : GfB planner).  

Agree about splitting up the description into facilities etc, and may go further with some attributes of the desk, like Internet access, Wireless etc.. which would be useful to store to run searches on / indicate using icons.

** RESULTS **

This has to run off postcodes from the start.  Plotting them on a map is a doddle so we should include the map from the outset.  Possible problem to think about : postcode data represents a cost : about £2000 for an annual licence.  I don't see much of a way around this, although at first we could pay as you go which would keep costs down while volumes were low.

Flames : tad nervous about this : I can picture bad amateur websites from 5 years ago where 'hot links' were denoted by a number of crappy little flame icons... ewgh

** DESK PAGE **
Include a small map showing the location

** REQUEST FORM **
Question : is there an reason why, if companies would like to, they can't put a contact telephone number on the site for an alternative means of making a request?

If the user hadn't registered they would have to register before accessing this page.

** RESPONSE PAGE **
We could update the desk's availability once it was booked (confirm that the owner wants this first of course)

** FEEDBACK **
I think it's really important for both parties to review each other

** DATABASE **
We'll decide about this at design time.

** FUTURE **
I see maps as pretty key actually.  I think some of the frills may have to wait such as this "Nice calendar interface like Google Analytics or TfL’s site.".  Even the feedback : first up we need to get a site where people can post the desks they've got on offer, and other people can contact them.  The quickest and simplest way of achieving this will be the one we go for.</description>
		<content:encoded><![CDATA[<p>** HOME PAGE **<br />
I&#8217;d like to see the two areas : “Share a desk” and “Find a desk” with a form so people can get started right there.  </p>
<p>** REGISTRATION **<br />
Let&#8217;s not stop people searching for desks by asking them to register.  Registration for &#8216;Flamers&#8217; should be if they want to do something like communicate with a Desk owner (via the site), rate a desk, comment on a desk<br />
Email confirmation : probably is needed.  We can let them log in but limit functionality without the confirmation.</p>
<p>** SHARE PAGE **<br />
Not sure about the new entry for each desk or &#8216;number available&#8217; argument.  Would probably opt for a half-way house : when you put your first desk up it takes the basic details of your company : name, address, brief description of company / office and then the details of the desk : photo, description, availability.  Once it&#8217;s been saved (or even at the bottom of this page) we have a &#8216;Add another desk at this office&#8217; link, to add multiple desks.  Then we can have a single office, multiple desks with a photo, availability and description (all optional) of each.  This way, you can add multiple desks quickly by hitting the link again and again, and if you want to go to town you can put more details in for each one.  I&#8217;ll show you an interface for something like this that we&#8217;ve done recently (Note to self : GfB planner).  </p>
<p>Agree about splitting up the description into facilities etc, and may go further with some attributes of the desk, like Internet access, Wireless etc.. which would be useful to store to run searches on / indicate using icons.</p>
<p>** RESULTS **</p>
<p>This has to run off postcodes from the start.  Plotting them on a map is a doddle so we should include the map from the outset.  Possible problem to think about : postcode data represents a cost : about £2000 for an annual licence.  I don&#8217;t see much of a way around this, although at first we could pay as you go which would keep costs down while volumes were low.</p>
<p>Flames : tad nervous about this : I can picture bad amateur websites from 5 years ago where &#8216;hot links&#8217; were denoted by a number of crappy little flame icons&#8230; ewgh</p>
<p>** DESK PAGE **<br />
Include a small map showing the location</p>
<p>** REQUEST FORM **<br />
Question : is there an reason why, if companies would like to, they can&#8217;t put a contact telephone number on the site for an alternative means of making a request?</p>
<p>If the user hadn&#8217;t registered they would have to register before accessing this page.</p>
<p>** RESPONSE PAGE **<br />
We could update the desk&#8217;s availability once it was booked (confirm that the owner wants this first of course)</p>
<p>** FEEDBACK **<br />
I think it&#8217;s really important for both parties to review each other</p>
<p>** DATABASE **<br />
We&#8217;ll decide about this at design time.</p>
<p>** FUTURE **<br />
I see maps as pretty key actually.  I think some of the frills may have to wait such as this &#8220;Nice calendar interface like Google Analytics or TfL’s site.&#8221;.  Even the feedback : first up we need to get a site where people can post the desks they&#8217;ve got on offer, and other people can contact them.  The quickest and simplest way of achieving this will be the one we go for.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

