<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
    <title></title>
  </head>
  <body bgcolor="#ffffff" text="#000000">
    <font face="Georgia">One question to ask is whether the site needs
      "a" new design or several. I am of a minority less enamored with
      design/structure and more interested in full understanding. Would
      Seaside make it possible to support two radically different views
      of the same information without needing to do twice the work?<br>
      <br>
      Cheers,<br>
      Bob<br>
      <br>
      P.S. I saw this today in a totally different context, but it seems
      applicable here as well:<br>
      <br>
      <a class="moz-txt-link-freetext" href="http://www.ted.com/talks/malcolm_gladwell_on_spaghetti_sauce.html">http://www.ted.com/talks/malcolm_gladwell_on_spaghetti_sauce.html</a><br>
      <br>
      <br>
    </font><br>
    On 2/23/11 9:18 AM, Robert Sirois wrote:
    <blockquote cite="mid:BAY158-w25F97C9F00415B9E5C7D7DA6DB0@phx.gbl"
      type="cite">
      <style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
      I like where this conversation is going :p Maybe what we really
      need is to get some ideas out there, put some volunteers in
      charge, and have a little web get-together and discuss it?
      <div><br>
      </div>
      <div>RS<br>
        <br>
        <hr id="stopSpelling">From: <a class="moz-txt-link-abbreviated" href="mailto:sebastian@flowingconcept.com">sebastian@flowingconcept.com</a><br>
        Subject: Re: [Seaside] website maintenance/feedback?<br>
        Date: Wed, 23 Feb 2011 10:53:17 -0300<br>
        To: <a class="moz-txt-link-abbreviated" href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a><br>
        <br>
        <meta http-equiv="Content-Type" content="text/html;
          charset=ISO-8859-1">
        <meta name="Generator" content="Microsoft SafeHTML">
        <div>"...<span class="ecxApple-style-span" style="color: rgb(51,
            0, 51); font-family: tahoma,sans-serif; font-size: small;">As
            I have previously mentioned, the website needs a better
            design...</span>"</div>
        <div><br>
        </div>
        <div>All...</div>
        <div><br>
        </div>
        <div>I not only agree with that, I'm afraid "the hole is
          deeper".</div>
        <div><br>
        </div>
        <div>Actually our community in general needs better branding so
          marketing so copywriting so design.</div>
        <div><br>
        </div>
        <div>Of course that means a website with better design. But the
          issue is more deep than retouching the website.</div>
        <div><br>
        </div>
        <div>Avi's attitude is the kind of thing that creates an
          opportunity for Seaside.</div>
        <div><br>
        </div>
        <div>It could be a chance to start showing people that
          smalltalkers don't ignore design (and I don't mean in theory).</div>
        <div><br>
        </div>
        <div>But the reality is that&nbsp;not much of a difference will
          happen unless we&nbsp;boldly embrace design from the core (code) to
          the skin (UI).</div>
        <div><br>
        </div>
        <div>Avi...&nbsp;</div>
        <div><br>
        </div>
        <div>if you have screenshots to show that's okay but be prepared
          for the next thing: people will start to make bold opinions
          about it (thinking they know what they're talking about even
          if they aren't designers) and having feedback is okay but, as
          you probably know, committees trying to design horses end up
          delivering giraffes because democratically they decided
          they're "improved"</div>
        <div><br>
        </div>
        <div>If you think you can deal with that and make us look
          better, they I'm curious already</div>
        <div><br>
        </div>
        <div>
          <div><a moz-do-not-send="true"
              href="http://twitter.com/#%21/sebastianconcpt"
              target="_blank">sebastian</a></div>
          <div><br>
          </div>
          <div>o/</div>
        </div>
        <div><br>
        </div>
        <div><br>
        </div>
        <br>
        <div>
          <div>On Feb 23, 2011, at 9:59 AM, Avi Shefi wrote:</div>
          <br class="ecxApple-interchange-newline">
          <blockquote>
            <div dir="ltr"><font color="#330033"><font size="2"><font
                    face="tahoma,sans-serif">Julian,<br>
                    I'm willing to manage the website.<br>
                  </font></font></font><font color="#330033"><font
                  size="2"><font face="tahoma,sans-serif">Lately I have
                    been working on a new design mockup for the Seaside
                    website. As I have previously mentioned, the website
                    needs a better design. Hope I'll get to it over the
                    following week and send some screenshots of it.</font></font></font><font
                color="#330033"><font size="2"><font
                    face="tahoma,sans-serif"><br>
                    <br>
                    Regardless of the issue, I have new ideas for
                    Seaside to which I will dedicate some time after I
                    finish some of the currently open issues.<br>
                    <br>
                    <br>
                    Regards,<br>
                    Avi.<br>
                  </font></font></font><br>
              <div class="ecxgmail_quote">
                On Wed, Feb 23, 2011 at 1:40 PM, Julian Fitzell <span
                  dir="ltr">&lt;<a moz-do-not-send="true"
                    href="mailto:jfitzell@gmail.com">jfitzell@gmail.com</a>&gt;</span>
                wrote:<br>
                <blockquote class="ecxgmail_quote" style="padding-left:
                  1ex;">I think I've asked before, but this is a good
                  time to ask again. Is<br>
                  there anyone in the community who would be willing to
                  volunteer their<br>
                  services as "webmaster"? It doesn't necessarily have
                  to involve a lot<br>
                  of work (though I'd love someone to take on the
                  challenge of cleaning<br>
                  up the site organization), but mostly having
                  responsibility for making<br>
                  sure these kinds of comments don't get dropped (filing
                  an issue if<br>
                  appropriate) and that *someone* is doing something
                  about them. We have<br>
                  a number of people in the community with permissions
                  to update the<br>
                  site, so some of the effort could just involve
                  delegation to them and<br>
                  then chasing them up.<br>
                  <font color="#888888"><br>
                    Julian<br>
                  </font>
                  <div>
                    <div><br>
                      On Wed, Feb 23, 2011 at 10:09 AM, Andrew Buchan
                      &lt;<a moz-do-not-send="true"
                        href="mailto:andyhasit@gmail.com">andyhasit@gmail.com</a>&gt;
                      wrote:<br>
                      &gt; Hello,<br>
                      &gt;<br>
                      &gt; I'm starting to use seaside, and finding most
                      of what I need, but have<br>
                      &gt; noticed something on the website that needs
                      fixed, not sure where to<br>
                      &gt; send this to as there is no "webmaster
                      contact" bit, so thought I'd<br>
                      &gt; post it here:<br>
                      &gt;<br>
                      &gt; -------------------<br>
                      &gt;<br>
                      &gt; On page: "<a moz-do-not-send="true"
                        href="http://www.seaside.st/documentation"
                        target="_blank">http://www.seaside.st/documentation</a>"
                      &nbsp; the menu link to<br>
                      &gt; "applications" brings you to the page on
                      "debugging"...<br>
                      &gt;<br>
                      &gt; Also, the pages talking about seaside 3.0:<br>
                      &gt;<br>
                      &gt; <a moz-do-not-send="true"
                        href="http://www.seaside.st/community/development/seaside30"
                        target="_blank">http://www.seaside.st/community/development/seaside30</a><br>
                      &gt; <a moz-do-not-send="true"
                        href="http://www.seaside.st/seaside30"
                        target="_blank">http://www.seaside.st/seaside30</a><br>
                      &gt;<br>
                      &gt; Could both do with being dated, especially as
                      Seaside is one of those<br>
                      &gt; things that people might try, leave, and come
                      back to in a few months<br>
                      &gt; to see if anything has changed, and won't
                      remember what version they<br>
                      &gt; downloaded.<br>
                      &gt;<br>
                      &gt; -------------------<br>
                      &gt;
                      _______________________________________________<br>
                      &gt; seaside mailing list<br>
                      &gt; <a moz-do-not-send="true"
                        href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a><br>
                      &gt; <a moz-do-not-send="true"
href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside"
                        target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
                      &gt;<br>
                      _______________________________________________<br>
                      seaside mailing list<br>
                      <a moz-do-not-send="true"
                        href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a><br>
                      <a moz-do-not-send="true"
href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside"
                        target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
                    </div>
                  </div>
                </blockquote>
              </div>
              <br>
            </div>
            _______________________________________________<br>
            seaside mailing list<br>
            <a moz-do-not-send="true"
              href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a><br>
<a class="moz-txt-link-freetext" href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
          </blockquote>
        </div>
        <br>
        <br>
        _______________________________________________
        seaside mailing list
        <a class="moz-txt-link-abbreviated" href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a>
<a class="moz-txt-link-freetext" href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a></div>
      <pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
seaside mailing list
<a class="moz-txt-link-abbreviated" href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a>
<a class="moz-txt-link-freetext" href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a>
</pre>
    </blockquote>
  </body>
</html>