In my experience, the most drop-dead simple content management system to set up and administer is Plone (www.plone.org), which is based on Zope 3 and Python. I think that being based on Python is an advantage for us in that the site could easily be set up to run Csound via the Python Csound API.

Plone also has facilities for storing and presenting soundfiles and text files, both of which are needed.

It has all the usual content management system stuff: built in editor, forms, RSS, etc., etc., etc.

Regards,
Mike

-----Original Message-----
>From: Steven Yi 
>Sent: Nov 30, 2007 2:36 AM
>To: csound@lists.bath.ac.uk
>Subject: [Csnd] Re: Re: Re: Re: Journal link.. - cSounds.com Webmaster Search
>
>Hi Dr. B,
>
>Besides just the aspects of design, I would like to highlight that
>content management systems usually do RSS feeds which is incredibly
>important in my opinion to help users keep informed of news, as well
>as search facilities for searching a site.  Whether Drupal or other
>system is used, these things are good to keep mind besides just the
>design.
>
>steven
>
>On Nov 29, 2007 11:21 PM, Dr. Richard Boulanger  wrote:
>> Steven,
>>
>> Thanks for the suggestions - and the push toward redesign.  I
>> completely agree.
>> I love all the work that David did on the site.  He made it much more
>> user-friendly
>> and useful, but I think that there are many new tools and models now
>> (OLPC, etc.)
>>
>> I liked, but didn't totally love the ardour.org model.  Still - there
>> are many things broken
>> at cSounds.com and many things that I have wanted to include,
>> feature, update for
>> years now....
>>
>> Brent Boylan and Brian Wong have offered to help.  Maybe others will
>> as well.  And maybe
>> the first thing we should do is decide upon a new and more open design.
>>
>> Dr. B.
>>
>>
>>
>> On Nov 30, 2007, at 2:05 AM, Steven Yi wrote:
>>
>> > Regarding the link: The link on csounds.com should probably be changed
>> > to link directly to csounds.com/journal instead of that page that is
>> > shown there that doesn't have the latest journal.
>> >
>> > Regarding the site: it really should be migrated to some kind of
>> > content management system or blog system IMO.  (Drupal might be a good
>> > solution as PHP or Rails are the only real options on what is
>> > available to use for csounds.com).  A nice looking drupal based site
>> > is ardour.org.  As it is now, I find myself hardly looking at
>> > csounds.com as it's very hard to find anything as the categorization
>> > is not as narrow as it could be.  (The way drupal's site's main
>> > categories are listed up top and how those pages are divided could be
>> > a model). Using blog software such as wordpress might be enough as
>> > well.
>> >
>> > steven
>> >
>> > On Nov 29, 2007 8:24 PM, Brent Boylan  wrote:
>> >>
>> >> I have actually been thinking about volunteering to help with the
>> >> site but
>> >> have not wanted to step on any toes, so to speak. There seem to be
>> >> some
>> >> usability issues to address. But if you just want someone to help
>> >> keep
>> >> things up to date I would like to help with that, too. Let me know.
>> >>
>> >> B. Boylan
>> >>
>> >>
>> >>
>> >> Dr. Richard Boulanger-3 wrote:
>> >>>
>> >>> Thanks Rory,
>> >>>
>> >>> I will personally try to get to those links you pointed out as soon
>> >>> as I can.
>> >>>
>> >>> But I am looking for help from someone in the Csound community to
>> >>> keep the site up to date.
>> >>>
>> >>> David Akbari - the previous webmaster of cSounds.com (and former
>> >>> student, assistant,
>> >>> collaborator, and all around brilliant and super csounder) has
>> >>> started in a graduate program
>> >>> in speech and hearing and so he doesn't have much time to work on
>> >>> the
>> >>> site any longer.  Thanks
>> >>> David - and good luck to you in your studies and research.  I can't
>> >>> wait to see (and hear) how
>> >>> you use Csound to assist others and help them hear better.
>> >>>
>> >>> Sooooooooooooo
>> >>>
>> >>> I am looking for a new volunteer to help me update things, change
>> >>> things, revise things, and keep
>> >>> the site going when I am drowning in OLPC, teaching at Berklee, and
>> >>> finishing the 2000+ page
>> >>> Audio Programming Book for MIT Press.
>> >>>
>> >>> Anyone interested in helping out with cSounds.com?
>> >>>
>> >>> Hope so.
>> >>>
>> >>> Dr. B.
>> >>>
>> >>> On Nov 29, 2007, at 3:41 PM, Rory Walsh wrote:
>> >>>
>> >>>> Currently the link to the Csound Journal on the Csounds.com site
>> >>>> does not give a full index of issues. It stops at summer 2006.
>> >>>> Perhaps someone can update it?
>> >>>>
>> >>>> Rory.
>> >>>>
>> >>>>
>> >>>> Send bugs reports to this list.
>> >>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>> >>>> "unsubscribe csound"
>> >>>
>> >>>
>> >>>
>> >>> Send bugs reports to this list.
>> >>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>> >>> "unsubscribe
>> >>> csound"
>> >>>
>> >>>
>> >>
>> >> --
>> >> View this message in context: http://www.nabble.com/Journal-link..-
>> >> tf4899858.html#a14040564
>> >> Sent from the Csound - General mailing list archive at Nabble.com.
>> >>
>> >>
>> >>
>> >>
>> >> Send bugs reports to this list.
>> >> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>> >> "unsubscribe csound"
>> >>
>> >
>> >
>> > Send bugs reports to this list.
>> > To unsubscribe, send email sympa@lists.bath.ac.uk with body
>> > "unsubscribe csound"
>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>
>
>
>Send bugs reports to this list.
>To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

I love python ten thousand times more than php, but hosting providers 
(at least here in italy) have a much worse support for it. Same for Ruby.

I have never tried Plone for this reason.

Michael, what about using a cgi in c for this? It should be pretty 
straightforward.

What kind of functionality would you like to implement? Maybe we can 
hack up an online csound compiler that lets you download the generated file?

-c.

Steven Yi wrote:
> Hi Michael,
>
> Unfortunately the web hosting company csounds.com is on does not support Plone.
>
> steven
>
> On Nov 30, 2007 7:20 AM, Michael Gogins  wrote:
>   
>> In my experience, the most drop-dead simple content management system to set up and administer is Plone (www.plone.org), which is based on Zope 3 and Python. I think that being based on Python is an advantage for us in that the site could easily be set up to run Csound via the Python Csound API.
>>
>> Plone also has facilities for storing and presenting soundfiles and text files, both of which are needed.
>>
>> It has all the usual content management system stuff: built in editor, forms, RSS, etc., etc., etc.
>>
>> Regards,
>> Mike
>>
>>
>> -----Original Message-----
>>     
>>> From: Steven Yi 
>>> Sent: Nov 30, 2007 2:36 AM
>>> To: csound@lists.bath.ac.uk
>>> Subject: [Csnd] Re: Re: Re: Re: Journal link.. - cSounds.com Webmaster Search
>>>
>>> Hi Dr. B,
>>>
>>> Besides just the aspects of design, I would like to highlight that
>>> content management systems usually do RSS feeds which is incredibly
>>> important in my opinion to help users keep informed of news, as well
>>> as search facilities for searching a site.  Whether Drupal or other
>>> system is used, these things are good to keep mind besides just the
>>> design.
>>>
>>> steven
>>>
>>> On Nov 29, 2007 11:21 PM, Dr. Richard Boulanger  wrote:
>>>       
>>>> Steven,
>>>>
>>>> Thanks for the suggestions - and the push toward redesign.  I
>>>> completely agree.
>>>> I love all the work that David did on the site.  He made it much more
>>>> user-friendly
>>>> and useful, but I think that there are many new tools and models now
>>>> (OLPC, etc.)
>>>>
>>>> I liked, but didn't totally love the ardour.org model.  Still - there
>>>> are many things broken
>>>> at cSounds.com and many things that I have wanted to include,
>>>> feature, update for
>>>> years now....
>>>>
>>>> Brent Boylan and Brian Wong have offered to help.  Maybe others will
>>>> as well.  And maybe
>>>> the first thing we should do is decide upon a new and more open design.
>>>>
>>>> Dr. B.
>>>>
>>>>
>>>>
>>>> On Nov 30, 2007, at 2:05 AM, Steven Yi wrote:
>>>>
>>>>         
>>>>> Regarding the link: The link on csounds.com should probably be changed
>>>>> to link directly to csounds.com/journal instead of that page that is
>>>>> shown there that doesn't have the latest journal.
>>>>>
>>>>> Regarding the site: it really should be migrated to some kind of
>>>>> content management system or blog system IMO.  (Drupal might be a good
>>>>> solution as PHP or Rails are the only real options on what is
>>>>> available to use for csounds.com).  A nice looking drupal based site
>>>>> is ardour.org.  As it is now, I find myself hardly looking at
>>>>> csounds.com as it's very hard to find anything as the categorization
>>>>> is not as narrow as it could be.  (The way drupal's site's main
>>>>> categories are listed up top and how those pages are divided could be
>>>>> a model). Using blog software such as wordpress might be enough as
>>>>> well.
>>>>>
>>>>> steven
>>>>>
>>>>>           
>>>>> On Nov 29, 2007 8:24 PM, Brent Boylan  wrote:
>>>>>           
>>>>>> I have actually been thinking about volunteering to help with the
>>>>>> site but
>>>>>> have not wanted to step on any toes, so to speak. There seem to be
>>>>>> some
>>>>>> usability issues to address. But if you just want someone to help
>>>>>> keep
>>>>>> things up to date I would like to help with that, too. Let me know.
>>>>>>
>>>>>> B. Boylan
>>>>>>
>>>>>>
>>>>>>
>>>>>> Dr. Richard Boulanger-3 wrote:
>>>>>>             
>>>>>>> Thanks Rory,
>>>>>>>
>>>>>>> I will personally try to get to those links you pointed out as soon
>>>>>>> as I can.
>>>>>>>
>>>>>>> But I am looking for help from someone in the Csound community to
>>>>>>> keep the site up to date.
>>>>>>>
>>>>>>> David Akbari - the previous webmaster of cSounds.com (and former
>>>>>>> student, assistant,
>>>>>>> collaborator, and all around brilliant and super csounder) has
>>>>>>> started in a graduate program
>>>>>>> in speech and hearing and so he doesn't have much time to work on
>>>>>>> the
>>>>>>> site any longer.  Thanks
>>>>>>> David - and good luck to you in your studies and research.  I can't
>>>>>>> wait to see (and hear) how
>>>>>>> you use Csound to assist others and help them hear better.
>>>>>>>
>>>>>>> Sooooooooooooo
>>>>>>>
>>>>>>> I am looking for a new volunteer to help me update things, change
>>>>>>> things, revise things, and keep
>>>>>>> the site going when I am drowning in OLPC, teaching at Berklee, and
>>>>>>> finishing the 2000+ page
>>>>>>> Audio Programming Book for MIT Press.
>>>>>>>
>>>>>>> Anyone interested in helping out with cSounds.com?
>>>>>>>
>>>>>>> Hope so.
>>>>>>>
>>>>>>> Dr. B.
>>>>>>>
>>>>>>> On Nov 29, 2007, at 3:41 PM, Rory Walsh wrote:
>>>>>>>
>>>>>>>               
>>>>>>>> Currently the link to the Csound Journal on the Csounds.com site
>>>>>>>> does not give a full index of issues. It stops at summer 2006.
>>>>>>>> Perhaps someone can update it?
>>>>>>>>
>>>>>>>> Rory.
>>>>>>>>
>>>>>>>>
>>>>>>>> Send bugs reports to this list.
>>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>>>>> "unsubscribe csound"
>>>>>>>>                 
>>>>>>>
>>>>>>> Send bugs reports to this list.
>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>>>> "unsubscribe
>>>>>>> csound"
>>>>>>>
>>>>>>>
>>>>>>>               
>>>>>> --
>>>>>> View this message in context: http://www.nabble.com/Journal-link..-
>>>>>> tf4899858.html#a14040564
>>>>>> Sent from the Csound - General mailing list archive at Nabble.com.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Send bugs reports to this list.
>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>>> "unsubscribe csound"
>>>>>>
>>>>>>             
>>>>> Send bugs reports to this list.
>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>> "unsubscribe csound"
>>>>>           
>>>>
>>>> Send bugs reports to this list.
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>
>>>>         
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>       
>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>
>>     
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>
>   


-- 
www.cesaremarilungo.com 

I agree.

My only advice is to switch to the most basic theme (which is called 
bluemarine in Drupal) right after the installation. The default theme is 
really nice but it is too bloated to personalize.

It would be great to have consistency among the various sections, too. 
Do you think it would be feasible to have the manual fully integrated 
with the rest of the website? If we use Drupal, we can use the Book 
module (which is in the core distribution). In that way registered users 
would be able to add comments to pages with code snippets and whatnot 
(like in the Drupal documentation).

-c.

Steven Yi wrote:
> I'd recommend not worrying about extra features until after the
> initial site is done.  I think the most important thing is
> reorganizing all of the sections and links so that there aren't 16
> sections on the first page which is too much in my opinion.  I'd also
> say start with the default theme and worry about organizing the
> content first, then deal with theme later.  I was never a fan of the
> current site design and the way it does news and things like that as
> it has usability issues (like you can't bookmark or view a single news
> item by itself).
>
> Westhost does support Ruby On Rails (I use it for blueShare as I also
> use Westhost for my own site), but I think it'd be better to use
> something pre-made like Drupal.
>
> steven
>
>
> On Nov 30, 2007 8:25 AM, Cesare Marilungo  wrote:
>   
>> I love python ten thousand times more than php, but hosting providers
>> (at least here in italy) have a much worse support for it. Same for Ruby.
>>
>> I have never tried Plone for this reason.
>>
>> Michael, what about using a cgi in c for this? It should be pretty
>> straightforward.
>>
>> What kind of functionality would you like to implement? Maybe we can
>> hack up an online csound compiler that lets you download the generated file?
>>
>> -c.
>>
>>
>> Steven Yi wrote:
>>     
>>> Hi Michael,
>>>
>>> Unfortunately the web hosting company csounds.com is on does not support Plone.
>>>
>>> steven
>>>
>>> On Nov 30, 2007 7:20 AM, Michael Gogins  wrote:
>>>
>>>       
>>>> In my experience, the most drop-dead simple content management system to set up and administer is Plone (www.plone.org), which is based on Zope 3 and Python. I think that being based on Python is an advantage for us in that the site could easily be set up to run Csound via the Python Csound API.
>>>>
>>>> Plone also has facilities for storing and presenting soundfiles and text files, both of which are needed.
>>>>
>>>> It has all the usual content management system stuff: built in editor, forms, RSS, etc., etc., etc.
>>>>
>>>> Regards,
>>>> Mike
>>>>
>>>>
>>>> -----Original Message-----
>>>>
>>>>         
>>>>> From: Steven Yi 
>>>>> Sent: Nov 30, 2007 2:36 AM
>>>>> To: csound@lists.bath.ac.uk
>>>>> Subject: [Csnd] Re: Re: Re: Re: Journal link.. - cSounds.com Webmaster Search
>>>>>
>>>>> Hi Dr. B,
>>>>>
>>>>> Besides just the aspects of design, I would like to highlight that
>>>>> content management systems usually do RSS feeds which is incredibly
>>>>> important in my opinion to help users keep informed of news, as well
>>>>> as search facilities for searching a site.  Whether Drupal or other
>>>>> system is used, these things are good to keep mind besides just the
>>>>> design.
>>>>>
>>>>> steven
>>>>>
>>>>> On Nov 29, 2007 11:21 PM, Dr. Richard Boulanger  wrote:
>>>>>
>>>>>           
>>>>>> Steven,
>>>>>>
>>>>>> Thanks for the suggestions - and the push toward redesign.  I
>>>>>> completely agree.
>>>>>> I love all the work that David did on the site.  He made it much more
>>>>>> user-friendly
>>>>>> and useful, but I think that there are many new tools and models now
>>>>>> (OLPC, etc.)
>>>>>>
>>>>>> I liked, but didn't totally love the ardour.org model.  Still - there
>>>>>> are many things broken
>>>>>> at cSounds.com and many things that I have wanted to include,
>>>>>> feature, update for
>>>>>> years now....
>>>>>>
>>>>>> Brent Boylan and Brian Wong have offered to help.  Maybe others will
>>>>>> as well.  And maybe
>>>>>> the first thing we should do is decide upon a new and more open design.
>>>>>>
>>>>>> Dr. B.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Nov 30, 2007, at 2:05 AM, Steven Yi wrote:
>>>>>>
>>>>>>
>>>>>>             
>>>>>>> Regarding the link: The link on csounds.com should probably be changed
>>>>>>> to link directly to csounds.com/journal instead of that page that is
>>>>>>> shown there that doesn't have the latest journal.
>>>>>>>
>>>>>>> Regarding the site: it really should be migrated to some kind of
>>>>>>> content management system or blog system IMO.  (Drupal might be a good
>>>>>>> solution as PHP or Rails are the only real options on what is
>>>>>>> available to use for csounds.com).  A nice looking drupal based site
>>>>>>> is ardour.org.  As it is now, I find myself hardly looking at
>>>>>>> csounds.com as it's very hard to find anything as the categorization
>>>>>>> is not as narrow as it could be.  (The way drupal's site's main
>>>>>>> categories are listed up top and how those pages are divided could be
>>>>>>> a model). Using blog software such as wordpress might be enough as
>>>>>>> well.
>>>>>>>
>>>>>>> steven
>>>>>>>
>>>>>>>
>>>>>>> On Nov 29, 2007 8:24 PM, Brent Boylan  wrote:
>>>>>>>
>>>>>>>               
>>>>>>>> I have actually been thinking about volunteering to help with the
>>>>>>>> site but
>>>>>>>> have not wanted to step on any toes, so to speak. There seem to be
>>>>>>>> some
>>>>>>>> usability issues to address. But if you just want someone to help
>>>>>>>> keep
>>>>>>>> things up to date I would like to help with that, too. Let me know.
>>>>>>>>
>>>>>>>> B. Boylan
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Dr. Richard Boulanger-3 wrote:
>>>>>>>>
>>>>>>>>                 
>>>>>>>>> Thanks Rory,
>>>>>>>>>
>>>>>>>>> I will personally try to get to those links you pointed out as soon
>>>>>>>>> as I can.
>>>>>>>>>
>>>>>>>>> But I am looking for help from someone in the Csound community to
>>>>>>>>> keep the site up to date.
>>>>>>>>>
>>>>>>>>> David Akbari - the previous webmaster of cSounds.com (and former
>>>>>>>>> student, assistant,
>>>>>>>>> collaborator, and all around brilliant and super csounder) has
>>>>>>>>> started in a graduate program
>>>>>>>>> in speech and hearing and so he doesn't have much time to work on
>>>>>>>>> the
>>>>>>>>> site any longer.  Thanks
>>>>>>>>> David - and good luck to you in your studies and research.  I can't
>>>>>>>>> wait to see (and hear) how
>>>>>>>>> you use Csound to assist others and help them hear better.
>>>>>>>>>
>>>>>>>>> Sooooooooooooo
>>>>>>>>>
>>>>>>>>> I am looking for a new volunteer to help me update things, change
>>>>>>>>> things, revise things, and keep
>>>>>>>>> the site going when I am drowning in OLPC, teaching at Berklee, and
>>>>>>>>> finishing the 2000+ page
>>>>>>>>> Audio Programming Book for MIT Press.
>>>>>>>>>
>>>>>>>>> Anyone interested in helping out with cSounds.com?
>>>>>>>>>
>>>>>>>>> Hope so.
>>>>>>>>>
>>>>>>>>> Dr. B.
>>>>>>>>>
>>>>>>>>> On Nov 29, 2007, at 3:41 PM, Rory Walsh wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>                   
>>>>>>>>>> Currently the link to the Csound Journal on the Csounds.com site
>>>>>>>>>> does not give a full index of issues. It stops at summer 2006.
>>>>>>>>>> Perhaps someone can update it?
>>>>>>>>>>
>>>>>>>>>> Rory.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Send bugs reports to this list.
>>>>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>>>>>>> "unsubscribe csound"
>>>>>>>>>>
>>>>>>>>>>                     
>>>>>>>>> Send bugs reports to this list.
>>>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>>>>>> "unsubscribe
>>>>>>>>> csound"
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>                   
>>>>>>>> --
>>>>>>>> View this message in context: http://www.nabble.com/Journal-link..-
>>>>>>>> tf4899858.html#a14040564
>>>>>>>> Sent from the Csound - General mailing list archive at Nabble.com.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Send bugs reports to this list.
>>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>>>>> "unsubscribe csound"
>>>>>>>>
>>>>>>>>
>>>>>>>>                 
>>>>>>> Send bugs reports to this list.
>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>>>> "unsubscribe csound"
>>>>>>>
>>>>>>>               
>>>>>> Send bugs reports to this list.
>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>>>
>>>>>>
>>>>>>             
>>>>> Send bugs reports to this list.
>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>>
>>>>>           
>>>>
>>>> Send bugs reports to this list.
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>
>>>>
>>>>         
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>
>>>
>>>
>>>       
>> --
>> www.cesaremarilungo.com
>>
>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>
>>     
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>
>   


-- 
www.cesaremarilungo.com 

Alright.

Now, the first thing to do, as you said, is a tree-like representation 
of all the sections of the website. I would proceed with a top-down 
approach, leaving the least important stuff / special cases out, ATM. It 
would be good to have at most 4-5 primary links with more subsections 
inside them.

As others already pointed out, this is the main reason to redesign the 
website.

My opinion is that usability comes first. That's also why I would 
discourage using css dropdowns and rollovers and other stuff that would 
bring usability issues.

Styling and theming can be done at any time and it would be better to 
address them later.

Here's my draft proposal:

About
-- About csound
-- History
-- People
Downloads
-- download csound (Csound5, CsoundAV, MacCsound ...)
-- Csound frontends (Blue, Cecilia, ...)
-- Csound sources
Documentation
-- Manuals
-- Docs for developers
Resources
-- Tutorials
-- Instruments
-- UDOs
-- Journal
Forums
-- developers
-- users
-- olpc
-- ...

Other stuff can be put on a sidebar (inside boxes) which could be 
present in any page.

My proposal:

- Support csounds (donations)
- Downloads (could be redundant, but we can make it just a tiny link)
- Radio*
- Featured software projects
- Latest news
- Latest forum posts

* I know that there's streaming available, but what about implementing 
it as a podcast/playilist (with a flash player that plays it and a 
button to subscribe to it as a feed)?

- c.

Steven Yi wrote:
> Hi Cesare,
>
> I don't think it would be feasible to have the manual fully integrated
> with the site.  The manual is quite huge and it would be problematic
> at best to try to import that into the system.  The book module would
> be great for creating new tutorials and things like that, but I don't
> see how it could work out with the manual.  The manual is also in
> multiple languages and it seems the documentation maintainers are
> doing a great job with it as it is, so probably best to keep it just
> as it is, a link from the site.
>
> One thing that might be possible is styling the manual via CSS to use
> the same theme as the site, but that something that's really not a
> primary issue IMO.
>
> steven
>
>
>
> On Nov 30, 2007 9:08 AM, Cesare Marilungo  wrote:
>   
>> I agree.
>>
>> My only advice is to switch to the most basic theme (which is called
>> bluemarine in Drupal) right after the installation. The default theme is
>> really nice but it is too bloated to personalize.
>>
>> It would be great to have consistency among the various sections, too.
>> Do you think it would be feasible to have the manual fully integrated
>> with the rest of the website? If we use Drupal, we can use the Book
>> module (which is in the core distribution). In that way registered users
>> would be able to add comments to pages with code snippets and whatnot
>> (like in the Drupal documentation).
>>
>> -c.
>>
>>
>> Steven Yi wrote:
>>     
>>> I'd recommend not worrying about extra features until after the
>>> initial site is done.  I think the most important thing is
>>> reorganizing all of the sections and links so that there aren't 16
>>> sections on the first page which is too much in my opinion.  I'd also
>>> say start with the default theme and worry about organizing the
>>> content first, then deal with theme later.  I was never a fan of the
>>> current site design and the way it does news and things like that as
>>> it has usability issues (like you can't bookmark or view a single news
>>> item by itself).
>>>
>>> Westhost does support Ruby On Rails (I use it for blueShare as I also
>>> use Westhost for my own site), but I think it'd be better to use
>>> something pre-made like Drupal.
>>>
>>> steven
>>>
>>>
>>> On Nov 30, 2007 8:25 AM, Cesare Marilungo  wrote:
>>>
>>>       
>>>> I love python ten thousand times more than php, but hosting providers
>>>> (at least here in italy) have a much worse support for it. Same for Ruby.
>>>>
>>>> I have never tried Plone for this reason.
>>>>
>>>> Michael, what about using a cgi in c for this? It should be pretty
>>>> straightforward.
>>>>
>>>> What kind of functionality would you like to implement? Maybe we can
>>>> hack up an online csound compiler that lets you download the generated file?
>>>>
>>>> -c.
>>>>
>>>>
>>>> Steven Yi wrote:
>>>>
>>>>         
>>>>> Hi Michael,
>>>>>
>>>>> Unfortunately the web hosting company csounds.com is on does not support Plone.
>>>>>
>>>>> steven
>>>>>
>>>>> On Nov 30, 2007 7:20 AM, Michael Gogins  wrote:
>>>>>
>>>>>
>>>>>           
>>>>>> In my experience, the most drop-dead simple content management system to set up and administer is Plone (www.plone.org), which is based on Zope 3 and Python. I think that being based on Python is an advantage for us in that the site could easily be set up to run Csound via the Python Csound API.
>>>>>>
>>>>>> Plone also has facilities for storing and presenting soundfiles and text files, both of which are needed.
>>>>>>
>>>>>> It has all the usual content management system stuff: built in editor, forms, RSS, etc., etc., etc.
>>>>>>
>>>>>> Regards,
>>>>>> Mike
>>>>>>
>>>>>>
>>>>>> -----Original Message-----
>>>>>>
>>>>>>
>>>>>>             
>>>>>>> From: Steven Yi 
>>>>>>> Sent: Nov 30, 2007 2:36 AM
>>>>>>> To: csound@lists.bath.ac.uk
>>>>>>> Subject: [Csnd] Re: Re: Re: Re: Journal link.. - cSounds.com Webmaster Search
>>>>>>>
>>>>>>> Hi Dr. B,
>>>>>>>
>>>>>>> Besides just the aspects of design, I would like to highlight that
>>>>>>> content management systems usually do RSS feeds which is incredibly
>>>>>>> important in my opinion to help users keep informed of news, as well
>>>>>>> as search facilities for searching a site.  Whether Drupal or other
>>>>>>> system is used, these things are good to keep mind besides just the
>>>>>>> design.
>>>>>>>
>>>>>>> steven
>>>>>>>
>>>>>>> On Nov 29, 2007 11:21 PM, Dr. Richard Boulanger  wrote:
>>>>>>>
>>>>>>>
>>>>>>>               
>>>>>>>> Steven,
>>>>>>>>
>>>>>>>> Thanks for the suggestions - and the push toward redesign.  I
>>>>>>>> completely agree.
>>>>>>>> I love all the work that David did on the site.  He made it much more
>>>>>>>> user-friendly
>>>>>>>> and useful, but I think that there are many new tools and models now
>>>>>>>> (OLPC, etc.)
>>>>>>>>
>>>>>>>> I liked, but didn't totally love the ardour.org model.  Still - there
>>>>>>>> are many things broken
>>>>>>>> at cSounds.com and many things that I have wanted to include,
>>>>>>>> feature, update for
>>>>>>>> years now....
>>>>>>>>
>>>>>>>> Brent Boylan and Brian Wong have offered to help.  Maybe others will
>>>>>>>> as well.  And maybe
>>>>>>>> the first thing we should do is decide upon a new and more open design.
>>>>>>>>
>>>>>>>> Dr. B.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Nov 30, 2007, at 2:05 AM, Steven Yi wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>                 
>>>>>>>>> Regarding the link: The link on csounds.com should probably be changed
>>>>>>>>> to link directly to csounds.com/journal instead of that page that is
>>>>>>>>> shown there that doesn't have the latest journal.
>>>>>>>>>
>>>>>>>>> Regarding the site: it really should be migrated to some kind of
>>>>>>>>> content management system or blog system IMO.  (Drupal might be a good
>>>>>>>>> solution as PHP or Rails are the only real options on what is
>>>>>>>>> available to use for csounds.com).  A nice looking drupal based site
>>>>>>>>> is ardour.org.  As it is now, I find myself hardly looking at
>>>>>>>>> csounds.com as it's very hard to find anything as the categorization
>>>>>>>>> is not as narrow as it could be.  (The way drupal's site's main
>>>>>>>>> categories are listed up top and how those pages are divided could be
>>>>>>>>> a model). Using blog software such as wordpress might be enough as
>>>>>>>>> well.
>>>>>>>>>
>>>>>>>>> steven
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Nov 29, 2007 8:24 PM, Brent Boylan  wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>                   
>>>>>>>>>> I have actually been thinking about volunteering to help with the
>>>>>>>>>> site but
>>>>>>>>>> have not wanted to step on any toes, so to speak. There seem to be
>>>>>>>>>> some
>>>>>>>>>> usability issues to address. But if you just want someone to help
>>>>>>>>>> keep
>>>>>>>>>> things up to date I would like to help with that, too. Let me know.
>>>>>>>>>>
>>>>>>>>>> B. Boylan
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Dr. Richard Boulanger-3 wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>                     
>>>>>>>>>>> Thanks Rory,
>>>>>>>>>>>
>>>>>>>>>>> I will personally try to get to those links you pointed out as soon
>>>>>>>>>>> as I can.
>>>>>>>>>>>
>>>>>>>>>>> But I am looking for help from someone in the Csound community to
>>>>>>>>>>> keep the site up to date.
>>>>>>>>>>>
>>>>>>>>>>> David Akbari - the previous webmaster of cSounds.com (and former
>>>>>>>>>>> student, assistant,
>>>>>>>>>>> collaborator, and all around brilliant and super csounder) has
>>>>>>>>>>> started in a graduate program
>>>>>>>>>>> in speech and hearing and so he doesn't have much time to work on
>>>>>>>>>>> the
>>>>>>>>>>> site any longer.  Thanks
>>>>>>>>>>> David - and good luck to you in your studies and research.  I can't
>>>>>>>>>>> wait to see (and hear) how
>>>>>>>>>>> you use Csound to assist others and help them hear better.
>>>>>>>>>>>
>>>>>>>>>>> Sooooooooooooo
>>>>>>>>>>>
>>>>>>>>>>> I am looking for a new volunteer to help me update things, change
>>>>>>>>>>> things, revise things, and keep
>>>>>>>>>>> the site going when I am drowning in OLPC, teaching at Berklee, and
>>>>>>>>>>> finishing the 2000+ page
>>>>>>>>>>> Audio Programming Book for MIT Press.
>>>>>>>>>>>
>>>>>>>>>>> Anyone interested in helping out with cSounds.com?
>>>>>>>>>>>
>>>>>>>>>>> Hope so.
>>>>>>>>>>>
>>>>>>>>>>> Dr. B.
>>>>>>>>>>>
>>>>>>>>>>> On Nov 29, 2007, at 3:41 PM, Rory Walsh wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>                       
>>>>>>>>>>>> Currently the link to the Csound Journal on the Csounds.com site
>>>>>>>>>>>> does not give a full index of issues. It stops at summer 2006.
>>>>>>>>>>>> Perhaps someone can update it?
>>>>>>>>>>>>
>>>>>>>>>>>> Rory.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Send bugs reports to this list.
>>>>>>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>>>>>>>>> "unsubscribe csound"
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>                         
>>>>>>>>>>> Send bugs reports to this list.
>>>>>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>>>>>>>> "unsubscribe
>>>>>>>>>>> csound"
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>                       
>>>>>>>>>> --
>>>>>>>>>> View this message in context: http://www.nabble.com/Journal-link..-
>>>>>>>>>> tf4899858.html#a14040564
>>>>>>>>>> Sent from the Csound - General mailing list archive at Nabble.com.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Send bugs reports to this list.
>>>>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>>>>>>> "unsubscribe csound"
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>                     
>>>>>>>>> Send bugs reports to this list.
>>>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>>>>>> "unsubscribe csound"
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>                   
>>>>>>>> Send bugs reports to this list.
>>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>                 
>>>>>>> Send bugs reports to this list.
>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>>>>
>>>>>>>
>>>>>>>               
>>>>>> Send bugs reports to this list.
>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>>>
>>>>>>
>>>>>>
>>>>>>             
>>>>> Send bugs reports to this list.
>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>           
>>>> --
>>>> www.cesaremarilungo.com
>>>>
>>>>
>>>>
>>>>
>>>> Send bugs reports to this list.
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>
>>>>
>>>>         
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>
>>>
>>>
>>>       
>> --
>> www.cesaremarilungo.com
>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>
>>     
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>
>   


-- 
www.cesaremarilungo.com 

This looks to me like a great way to stucture the site. Tutorials could go in
documentation, but with so few menu items a new user will find them easily.
I also agree with you on saving styling for later.


Cesare Marilungo wrote:
> 
> Alright.
> 
> Now, the first thing to do, as you said, is a tree-like representation 
> of all the sections of the website. I would proceed with a top-down 
> approach, leaving the least important stuff / special cases out, ATM. It 
> would be good to have at most 4-5 primary links with more subsections 
> inside them.
> 
> As others already pointed out, this is the main reason to redesign the 
> website.
> 
> My opinion is that usability comes first. That's also why I would 
> discourage using css dropdowns and rollovers and other stuff that would 
> bring usability issues.
> 
> Styling and theming can be done at any time and it would be better to 
> address them later.
> 
> Here's my draft proposal:
> 
> About
> -- About csound
> -- History
> -- People
> Downloads
> -- download csound (Csound5, CsoundAV, MacCsound ...)
> -- Csound frontends (Blue, Cecilia, ...)
> -- Csound sources
> Documentation
> -- Manuals
> -- Docs for developers
> Resources
> -- Tutorials
> -- Instruments
> -- UDOs
> -- Journal
> Forums
> -- developers
> -- users
> -- olpc
> -- ...
> 
> Other stuff can be put on a sidebar (inside boxes) which could be 
> present in any page.
> 
> My proposal:
> 
> - Support csounds (donations)
> - Downloads (could be redundant, but we can make it just a tiny link)
> - Radio*
> - Featured software projects
> - Latest news
> - Latest forum posts
> 
> * I know that there's streaming available, but what about implementing 
> it as a podcast/playilist (with a flash player that plays it and a 
> button to subscribe to it as a feed)?
> 
> - c.
> 
> 
-- 
View this message in context: http://www.nabble.com/Journal-link..-tf4899858.html#a14105926
Sent from the Csound - General mailing list archive at Nabble.com.

I just have a few suggestions.  For this project to work, one person should
be in charge of making all the calls.  With Dr. B's blessing, of course. :) 
The person in charge should be the person implementing the changes. 
Otherwise, this project won't go anywhere.

As for the technology beneath, it shouldn't matter whether or not it's
drupal/php, plone, on rails, etc.  What ever tech is chosen should be
invisible to the users that visit the site.  What does matter, as Cesare
pointed out, is usability.

I personally like Cesare's proposal. 

Best, 
Jake 

---- 
The Csound Blog 
http://www.thumbuki.com/csound/blog  





Cesare Marilungo wrote:
> 
> Alright.
> 
> Now, the first thing to do, as you said, is a tree-like representation 
> of all the sections of the website. I would proceed with a top-down 
> approach, leaving the least important stuff / special cases out, ATM. It 
> would be good to have at most 4-5 primary links with more subsections 
> inside them.
> 
> As others already pointed out, this is the main reason to redesign the 
> website.
> 
> My opinion is that usability comes first. That's also why I would 
> discourage using css dropdowns and rollovers and other stuff that would 
> bring usability issues.
> 
> Styling and theming can be done at any time and it would be better to 
> address them later.
> 
> Here's my draft proposal:
> 
> About
> -- About csound
> -- History
> -- People
> Downloads
> -- download csound (Csound5, CsoundAV, MacCsound ...)
> -- Csound frontends (Blue, Cecilia, ...)
> -- Csound sources
> Documentation
> -- Manuals
> -- Docs for developers
> Resources
> -- Tutorials
> -- Instruments
> -- UDOs
> -- Journal
> Forums
> -- developers
> -- users
> -- olpc
> -- ...
> 
> Other stuff can be put on a sidebar (inside boxes) which could be 
> present in any page.
> 
> My proposal:
> 
> - Support csounds (donations)
> - Downloads (could be redundant, but we can make it just a tiny link)
> - Radio*
> - Featured software projects
> - Latest news
> - Latest forum posts
> 
> * I know that there's streaming available, but what about implementing 
> it as a podcast/playilist (with a flash player that plays it and a 
> button to subscribe to it as a feed)?
> 
> - c.
> 
> 

-- 
View this message in context: http://www.nabble.com/Journal-link..-tf4899858.html#a14106090
Sent from the Csound - General mailing list archive at Nabble.com.

Updated:

About
-- About csound
-- History
-- People
Downloads
-- download csound (Csound5, CsoundAV, MacCsound ...)
-- Csound frontends (Blue, Cecilia, ...)
-- Csound sources
Documentation
-- Manuals
-- Docs for developers
Resources
-- Tutorials
-- Instruments
-- UDOs
-- Journal
Community
--Mailing lists
--Forums
News/Archive/?


These would be the buttons on the top of the page, and of course news 
are the main content of the home page itself. The news (or archive or 
whatever) button could simply bring you back to the home page, where the 
news are. Makes sense?

Otherwise the button could point to a page with some kind of index (by 
months?).

But I think pointing back to the home makes more sense. I never search 
inside news on a website by date. Especially if there's a search box 
available and/or tags (and I suggest to use both). You can always browse 
from page to page to read older news posts, like with most blogs.

What do you think?

- c.

Steven Yi wrote:
> Hi Cesare,
>
> Thanks for your time and thoughts you've put into this!  I like the
> breakdown so far.  I do think we need a top level section for news
> that can act like a blog and that people subscribe to via RSS/Atom
> feeds.  I think that would definitely help to increase awareness of
> what is going on with Csound.  I'd put that on the front page as well
> as have an archive section (this is in addition to the link latest
> news link on the right).  I also like the idea of doing the radio as a
> podcast (or just call it Csound Podcast) as I think it's a more
> popular way to do music these days.  Otherwise, I think there needs to
> be somewhere to find out about the mailing list.  My suggestion would
> be to change the top level Forum into "Community" and to link to the
> various mailing lists as well as forums.
>
> Thanks!
> steven
>
> On Dec 1, 2007 3:03 AM, Cesare Marilungo  wrote:
>   
>> Alright.
>>
>> Now, the first thing to do, as you said, is a tree-like representation
>> of all the sections of the website. I would proceed with a top-down
>> approach, leaving the least important stuff / special cases out, ATM. It
>> would be good to have at most 4-5 primary links with more subsections
>> inside them.
>>
>> As others already pointed out, this is the main reason to redesign the
>> website.
>>
>> My opinion is that usability comes first. That's also why I would
>> discourage using css dropdowns and rollovers and other stuff that would
>> bring usability issues.
>>
>> Styling and theming can be done at any time and it would be better to
>> address them later.
>>
>> Here's my draft proposal:
>>
>> About
>> -- About csound
>> -- History
>> -- People
>> Downloads
>> -- download csound (Csound5, CsoundAV, MacCsound ...)
>> -- Csound frontends (Blue, Cecilia, ...)
>> -- Csound sources
>> Documentation
>> -- Manuals
>> -- Docs for developers
>> Resources
>> -- Tutorials
>> -- Instruments
>> -- UDOs
>> -- Journal
>> Forums
>> -- developers
>> -- users
>> -- olpc
>> -- ...
>>
>> Other stuff can be put on a sidebar (inside boxes) which could be
>> present in any page.
>>
>> My proposal:
>>
>> - Support csounds (donations)
>> - Downloads (could be redundant, but we can make it just a tiny link)
>> - Radio*
>> - Featured software projects
>> - Latest news
>> - Latest forum posts
>>
>> * I know that there's streaming available, but what about implementing
>> it as a podcast/playilist (with a flash player that plays it and a
>> button to subscribe to it as a feed)?
>>
>> - c.
>>
>>
>> Steven Yi wrote:
>>     
>>> Hi Cesare,
>>>
>>> I don't think it would be feasible to have the manual fully integrated
>>> with the site.  The manual is quite huge and it would be problematic
>>> at best to try to import that into the system.  The book module would
>>> be great for creating new tutorials and things like that, but I don't
>>> see how it could work out with the manual.  The manual is also in
>>> multiple languages and it seems the documentation maintainers are
>>> doing a great job with it as it is, so probably best to keep it just
>>> as it is, a link from the site.
>>>
>>> One thing that might be possible is styling the manual via CSS to use
>>> the same theme as the site, but that something that's really not a
>>> primary issue IMO.
>>>
>>> steven
>>>
>>>
>>>
>>> On Nov 30, 2007 9:08 AM, Cesare Marilungo  wrote:
>>>
>>>       
>>>> I agree.
>>>>
>>>> My only advice is to switch to the most basic theme (which is called
>>>> bluemarine in Drupal) right after the installation. The default theme is
>>>> really nice but it is too bloated to personalize.
>>>>
>>>> It would be great to have consistency among the various sections, too.
>>>> Do you think it would be feasible to have the manual fully integrated
>>>> with the rest of the website? If we use Drupal, we can use the Book
>>>> module (which is in the core distribution). In that way registered users
>>>> would be able to add comments to pages with code snippets and whatnot
>>>> (like in the Drupal documentation).
>>>>
>>>> -c.
>>>>
>>>>
>>>> Steven Yi wrote:
>>>>
>>>>         
>>>>> I'd recommend not worrying about extra features until after the
>>>>> initial site is done.  I think the most important thing is
>>>>> reorganizing all of the sections and links so that there aren't 16
>>>>> sections on the first page which is too much in my opinion.  I'd also
>>>>> say start with the default theme and worry about organizing the
>>>>> content first, then deal with theme later.  I was never a fan of the
>>>>> current site design and the way it does news and things like that as
>>>>> it has usability issues (like you can't bookmark or view a single news
>>>>> item by itself).
>>>>>
>>>>> Westhost does support Ruby On Rails (I use it for blueShare as I also
>>>>> use Westhost for my own site), but I think it'd be better to use
>>>>> something pre-made like Drupal.
>>>>>
>>>>> steven
>>>>>
>>>>>
>>>>> On Nov 30, 2007 8:25 AM, Cesare Marilungo  wrote:
>>>>>
>>>>>
>>>>>           
>>>>>> I love python ten thousand times more than php, but hosting providers
>>>>>> (at least here in italy) have a much worse support for it. Same for Ruby.
>>>>>>
>>>>>> I have never tried Plone for this reason.
>>>>>>
>>>>>> Michael, what about using a cgi in c for this? It should be pretty
>>>>>> straightforward.
>>>>>>
>>>>>> What kind of functionality would you like to implement? Maybe we can
>>>>>> hack up an online csound compiler that lets you download the generated file?
>>>>>>
>>>>>> -c.
>>>>>>
>>>>>>
>>>>>> Steven Yi wrote:
>>>>>>
>>>>>>
>>>>>>             
>>>>>>> Hi Michael,
>>>>>>>
>>>>>>> Unfortunately the web hosting company csounds.com is on does not support Plone.
>>>>>>>
>>>>>>> steven
>>>>>>>
>>>>>>> On Nov 30, 2007 7:20 AM, Michael Gogins  wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>               
>>>>>>>> In my experience, the most drop-dead simple content management system to set up and administer is Plone (www.plone.org), which is based on Zope 3 and Python. I think that being based on Python is an advantage for us in that the site could easily be set up to run Csound via the Python Csound API.
>>>>>>>>
>>>>>>>> Plone also has facilities for storing and presenting soundfiles and text files, both of which are needed.
>>>>>>>>
>>>>>>>> It has all the usual content management system stuff: built in editor, forms, RSS, etc., etc., etc.
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> Mike
>>>>>>>>
>>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>                 
>>>>>>>>> From: Steven Yi 
>>>>>>>>> Sent: Nov 30, 2007 2:36 AM
>>>>>>>>> To: csound@lists.bath.ac.uk
>>>>>>>>> Subject: [Csnd] Re: Re: Re: Re: Journal link.. - cSounds.com Webmaster Search
>>>>>>>>>
>>>>>>>>> Hi Dr. B,
>>>>>>>>>
>>>>>>>>> Besides just the aspects of design, I would like to highlight that
>>>>>>>>> content management systems usually do RSS feeds which is incredibly
>>>>>>>>> important in my opinion to help users keep informed of news, as well
>>>>>>>>> as search facilities for searching a site.  Whether Drupal or other
>>>>>>>>> system is used, these things are good to keep mind besides just the
>>>>>>>>> design.
>>>>>>>>>
>>>>>>>>> steven
>>>>>>>>>
>>>>>>>>> On Nov 29, 2007 11:21 PM, Dr. Richard Boulanger  wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>                   
>>>>>>>>>> Steven,
>>>>>>>>>>
>>>>>>>>>> Thanks for the suggestions - and the push toward redesign.  I
>>>>>>>>>> completely agree.
>>>>>>>>>> I love all the work that David did on the site.  He made it much more
>>>>>>>>>> user-friendly
>>>>>>>>>> and useful, but I think that there are many new tools and models now
>>>>>>>>>> (OLPC, etc.)
>>>>>>>>>>
>>>>>>>>>> I liked, but didn't totally love the ardour.org model.  Still - there
>>>>>>>>>> are many things broken
>>>>>>>>>> at cSounds.com and many things that I have wanted to include,
>>>>>>>>>> feature, update for
>>>>>>>>>> years now....
>>>>>>>>>>
>>>>>>>>>> Brent Boylan and Brian Wong have offered to help.  Maybe others will
>>>>>>>>>> as well.  And maybe
>>>>>>>>>> the first thing we should do is decide upon a new and more open design.
>>>>>>>>>>
>>>>>>>>>> Dr. B.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Nov 30, 2007, at 2:05 AM, Steven Yi wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>                     
>>>>>>>>>>> Regarding the link: The link on csounds.com should probably be changed
>>>>>>>>>>> to link directly to csounds.com/journal instead of that page that is
>>>>>>>>>>> shown there that doesn't have the latest journal.
>>>>>>>>>>>
>>>>>>>>>>> Regarding the site: it really should be migrated to some kind of
>>>>>>>>>>> content management system or blog system IMO.  (Drupal might be a good
>>>>>>>>>>> solution as PHP or Rails are the only real options on what is
>>>>>>>>>>> available to use for csounds.com).  A nice looking drupal based site
>>>>>>>>>>> is ardour.org.  As it is now, I find myself hardly looking at
>>>>>>>>>>> csounds.com as it's very hard to find anything as the categorization
>>>>>>>>>>> is not as narrow as it could be.  (The way drupal's site's main
>>>>>>>>>>> categories are listed up top and how those pages are divided could be
>>>>>>>>>>> a model). Using blog software such as wordpress might be enough as
>>>>>>>>>>> well.
>>>>>>>>>>>
>>>>>>>>>>> steven
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Nov 29, 2007 8:24 PM, Brent Boylan  wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>                       
>>>>>>>>>>>> I have actually been thinking about volunteering to help with the
>>>>>>>>>>>> site but
>>>>>>>>>>>> have not wanted to step on any toes, so to speak. There seem to be
>>>>>>>>>>>> some
>>>>>>>>>>>> usability issues to address. But if you just want someone to help
>>>>>>>>>>>> keep
>>>>>>>>>>>> things up to date I would like to help with that, too. Let me know.
>>>>>>>>>>>>
>>>>>>>>>>>> B. Boylan
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Dr. Richard Boulanger-3 wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>                         
>>>>>>>>>>>>> Thanks Rory,
>>>>>>>>>>>>>
>>>>>>>>>>>>> I will personally try to get to those links you pointed out as soon
>>>>>>>>>>>>> as I can.
>>>>>>>>>>>>>
>>>>>>>>>>>>> But I am looking for help from someone in the Csound community to
>>>>>>>>>>>>> keep the site up to date.
>>>>>>>>>>>>>
>>>>>>>>>>>>> David Akbari - the previous webmaster of cSounds.com (and former
>>>>>>>>>>>>> student, assistant,
>>>>>>>>>>>>> collaborator, and all around brilliant and super csounder) has
>>>>>>>>>>>>> started in a graduate program
>>>>>>>>>>>>> in speech and hearing and so he doesn't have much time to work on
>>>>>>>>>>>>> the
>>>>>>>>>>>>> site any longer.  Thanks
>>>>>>>>>>>>> David - and good luck to you in your studies and research.  I can't
>>>>>>>>>>>>> wait to see (and hear) how
>>>>>>>>>>>>> you use Csound to assist others and help them hear better.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Sooooooooooooo
>>>>>>>>>>>>>
>>>>>>>>>>>>> I am looking for a new volunteer to help me update things, change
>>>>>>>>>>>>> things, revise things, and keep
>>>>>>>>>>>>> the site going when I am drowning in OLPC, teaching at Berklee, and
>>>>>>>>>>>>> finishing the 2000+ page
>>>>>>>>>>>>> Audio Programming Book for MIT Press.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Anyone interested in helping out with cSounds.com?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hope so.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Dr. B.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Nov 29, 2007, at 3:41 PM, Rory Walsh wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>                           
>>>>>>>>>>>>>> Currently the link to the Csound Journal on the Csounds.com site
>>>>>>>>>>>>>> does not give a full index of issues. It stops at summer 2006.
>>>>>>>>>>>>>> Perhaps someone can update it?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Rory.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Send bugs reports to this list.
>>>>>>>>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>>>>>>>>>>> "unsubscribe csound"
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>                             
>>>>>>>>>>>>> Send bugs reports to this list.
>>>>>>>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>>>>>>>>>> "unsubscribe
>>>>>>>>>>>>> csound"
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>                           
>>>>>>>>>>>> --
>>>>>>>>>>>> View this message in context: http://www.nabble.com/Journal-link..-
>>>>>>>>>>>> tf4899858.html#a14040564
>>>>>>>>>>>> Sent from the Csound - General mailing list archive at Nabble.com.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Send bugs reports to this list.
>>>>>>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>>>>>>>>> "unsubscribe csound"
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>                         
>>>>>>>>>>> Send bugs reports to this list.
>>>>>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>>>>>>>> "unsubscribe csound"
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>                       
>>>>>>>>>> Send bugs reports to this list.
>>>>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>                     
>>>>>>>>> Send bugs reports to this list.
>>>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>                   
>>>>>>>> Send bugs reports to this list.
>>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>                 
>>>>>>> Send bugs reports to this list.
>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>               
>>>>>> --
>>>>>> www.cesaremarilungo.com
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Send bugs reports to this list.
>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>>>
>>>>>>
>>>>>>
>>>>>>             
>>>>> Send bugs reports to this list.
>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>           
>>>> --
>>>> www.cesaremarilungo.com
>>>>
>>>>
>>>>
>>>> Send bugs reports to this list.
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>>
>>>>
>>>>         
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>>
>>>
>>>
>>>       
>> --
>> www.cesaremarilungo.com
>>
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>>
>>     
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>
>   


-- 
www.cesaremarilungo.com 

Another thought: maybe it would be better to use 'Projects' instead of 
'Downloads'. The Download link on the sidebar could be a link to the 
page with links to download all the latest official and unofficial 
csound versions for all platform, and the sources.

In this way we can use 'Projects' to link to a directory of every 
project related to Csound (frontends, utilities, bindings etc.) as well 
as the latest Csound on top of them.

Cesare Marilungo wrote:
> Updated:
>
> About
> -- About csound
> -- History
> -- People
> Downloads
> -- download csound (Csound5, CsoundAV, MacCsound ...)
> -- Csound frontends (Blue, Cecilia, ...)
> -- Csound sources
> Documentation
> -- Manuals
> -- Docs for developers
> Resources
> -- Tutorials
> -- Instruments
> -- UDOs
> -- Journal
> Community
> --Mailing lists
> --Forums
> News/Archive/?
>
>
> These would be the buttons on the top of the page, and of course news 
> are the main content of the home page itself. The news (or archive or 
> whatever) button could simply bring you back to the home page, where 
> the news are. Makes sense?
>
> Otherwise the button could point to a page with some kind of index (by 
> months?).
>
> But I think pointing back to the home makes more sense. I never search 
> inside news on a website by date. Especially if there's a search box 
> available and/or tags (and I suggest to use both). You can always 
> browse from page to page to read older news posts, like with most blogs.
>
> What do you think?
>
> - c.
>
> Steven Yi wrote:
>> Hi Cesare,
>>
>> Thanks for your time and thoughts you've put into this!  I like the
>> breakdown so far.  I do think we need a top level section for news
>> that can act like a blog and that people subscribe to via RSS/Atom
>> feeds.  I think that would definitely help to increase awareness of
>> what is going on with Csound.  I'd put that on the front page as well
>> as have an archive section (this is in addition to the link latest
>> news link on the right).  I also like the idea of doing the radio as a
>> podcast (or just call it Csound Podcast) as I think it's a more
>> popular way to do music these days.  Otherwise, I think there needs to
>> be somewhere to find out about the mailing list.  My suggestion would
>> be to change the top level Forum into "Community" and to link to the
>> various mailing lists as well as forums.
>>
>> Thanks!
>> steven
>>
>> On Dec 1, 2007 3:03 AM, Cesare Marilungo  
>> wrote:
>>  
>>> Alright.
>>>
>>> Now, the first thing to do, as you said, is a tree-like representation
>>> of all the sections of the website. I would proceed with a top-down
>>> approach, leaving the least important stuff / special cases out, 
>>> ATM. It
>>> would be good to have at most 4-5 primary links with more subsections
>>> inside them.
>>>
>>> As others already pointed out, this is the main reason to redesign the
>>> website.
>>>
>>> My opinion is that usability comes first. That's also why I would
>>> discourage using css dropdowns and rollovers and other stuff that would
>>> bring usability issues.
>>>
>>> Styling and theming can be done at any time and it would be better to
>>> address them later.
>>>
>>> Here's my draft proposal:
>>>
>>> About
>>> -- About csound
>>> -- History
>>> -- People
>>> Downloads
>>> -- download csound (Csound5, CsoundAV, MacCsound ...)
>>> -- Csound frontends (Blue, Cecilia, ...)
>>> -- Csound sources
>>> Documentation
>>> -- Manuals
>>> -- Docs for developers
>>> Resources
>>> -- Tutorials
>>> -- Instruments
>>> -- UDOs
>>> -- Journal
>>> Forums
>>> -- developers
>>> -- users
>>> -- olpc
>>> -- ...
>>>
>>> Other stuff can be put on a sidebar (inside boxes) which could be
>>> present in any page.
>>>
>>> My proposal:
>>>
>>> - Support csounds (donations)
>>> - Downloads (could be redundant, but we can make it just a tiny link)
>>> - Radio*
>>> - Featured software projects
>>> - Latest news
>>> - Latest forum posts
>>>
>>> * I know that there's streaming available, but what about implementing
>>> it as a podcast/playilist (with a flash player that plays it and a
>>> button to subscribe to it as a feed)?
>>>
>>> - c.
>>>
>>>
>>> Steven Yi wrote:
>>>    
>>>> Hi Cesare,
>>>>
>>>> I don't think it would be feasible to have the manual fully integrated
>>>> with the site.  The manual is quite huge and it would be problematic
>>>> at best to try to import that into the system.  The book module would
>>>> be great for creating new tutorials and things like that, but I don't
>>>> see how it could work out with the manual.  The manual is also in
>>>> multiple languages and it seems the documentation maintainers are
>>>> doing a great job with it as it is, so probably best to keep it just
>>>> as it is, a link from the site.
>>>>
>>>> One thing that might be possible is styling the manual via CSS to use
>>>> the same theme as the site, but that something that's really not a
>>>> primary issue IMO.
>>>>
>>>> steven
>>>>
>>>>
>>>>
>>>> On Nov 30, 2007 9:08 AM, Cesare Marilungo 
>>>>  wrote:
>>>>
>>>>      
>>>>> I agree.
>>>>>
>>>>> My only advice is to switch to the most basic theme (which is called
>>>>> bluemarine in Drupal) right after the installation. The default 
>>>>> theme is
>>>>> really nice but it is too bloated to personalize.
>>>>>
>>>>> It would be great to have consistency among the various sections, 
>>>>> too.
>>>>> Do you think it would be feasible to have the manual fully integrated
>>>>> with the rest of the website? If we use Drupal, we can use the Book
>>>>> module (which is in the core distribution). In that way registered 
>>>>> users
>>>>> would be able to add comments to pages with code snippets and whatnot
>>>>> (like in the Drupal documentation).
>>>>>
>>>>> -c.
>>>>>
>>>>>
>>>>> Steven Yi wrote:
>>>>>
>>>>>        
>>>>>> I'd recommend not worrying about extra features until after the
>>>>>> initial site is done.  I think the most important thing is
>>>>>> reorganizing all of the sections and links so that there aren't 16
>>>>>> sections on the first page which is too much in my opinion.  I'd 
>>>>>> also
>>>>>> say start with the default theme and worry about organizing the
>>>>>> content first, then deal with theme later.  I was never a fan of the
>>>>>> current site design and the way it does news and things like that as
>>>>>> it has usability issues (like you can't bookmark or view a single 
>>>>>> news
>>>>>> item by itself).
>>>>>>
>>>>>> Westhost does support Ruby On Rails (I use it for blueShare as I 
>>>>>> also
>>>>>> use Westhost for my own site), but I think it'd be better to use
>>>>>> something pre-made like Drupal.
>>>>>>
>>>>>> steven
>>>>>>
>>>>>>
>>>>>> On Nov 30, 2007 8:25 AM, Cesare Marilungo 
>>>>>>  wrote:
>>>>>>
>>>>>>
>>>>>>          
>>>>>>> I love python ten thousand times more than php, but hosting 
>>>>>>> providers
>>>>>>> (at least here in italy) have a much worse support for it. Same 
>>>>>>> for Ruby.
>>>>>>>
>>>>>>> I have never tried Plone for this reason.
>>>>>>>
>>>>>>> Michael, what about using a cgi in c for this? It should be pretty
>>>>>>> straightforward.
>>>>>>>
>>>>>>> What kind of functionality would you like to implement? Maybe we 
>>>>>>> can
>>>>>>> hack up an online csound compiler that lets you download the 
>>>>>>> generated file?
>>>>>>>
>>>>>>> -c.
>>>>>>>
>>>>>>>
>>>>>>> Steven Yi wrote:
>>>>>>>
>>>>>>>
>>>>>>>            
>>>>>>>> Hi Michael,
>>>>>>>>
>>>>>>>> Unfortunately the web hosting company csounds.com is on does 
>>>>>>>> not support Plone.
>>>>>>>>
>>>>>>>> steven
>>>>>>>>
>>>>>>>> On Nov 30, 2007 7:20 AM, Michael Gogins  
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>              
>>>>>>>>> In my experience, the most drop-dead simple content management 
>>>>>>>>> system to set up and administer is Plone (www.plone.org), 
>>>>>>>>> which is based on Zope 3 and Python. I think that being based 
>>>>>>>>> on Python is an advantage for us in that the site could easily 
>>>>>>>>> be set up to run Csound via the Python Csound API.
>>>>>>>>>
>>>>>>>>> Plone also has facilities for storing and presenting 
>>>>>>>>> soundfiles and text files, both of which are needed.
>>>>>>>>>
>>>>>>>>> It has all the usual content management system stuff: built in 
>>>>>>>>> editor, forms, RSS, etc., etc., etc.
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Mike
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> -----Original Message-----
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>                
>>>>>>>>>> From: Steven Yi 
>>>>>>>>>> Sent: Nov 30, 2007 2:36 AM
>>>>>>>>>> To: csound@lists.bath.ac.uk
>>>>>>>>>> Subject: [Csnd] Re: Re: Re: Re: Journal link.. - cSounds.com 
>>>>>>>>>> Webmaster Search
>>>>>>>>>>
>>>>>>>>>> Hi Dr. B,
>>>>>>>>>>
>>>>>>>>>> Besides just the aspects of design, I would like to highlight 
>>>>>>>>>> that
>>>>>>>>>> content management systems usually do RSS feeds which is 
>>>>>>>>>> incredibly
>>>>>>>>>> important in my opinion to help users keep informed of news, 
>>>>>>>>>> as well
>>>>>>>>>> as search facilities for searching a site.  Whether Drupal or 
>>>>>>>>>> other
>>>>>>>>>> system is used, these things are good to keep mind besides 
>>>>>>>>>> just the
>>>>>>>>>> design.
>>>>>>>>>>
>>>>>>>>>> steven
>>>>>>>>>>
>>>>>>>>>> On Nov 29, 2007 11:21 PM, Dr. Richard Boulanger 
>>>>>>>>>>  wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>                  
>>>>>>>>>>> Steven,
>>>>>>>>>>>
>>>>>>>>>>> Thanks for the suggestions - and the push toward redesign.  I
>>>>>>>>>>> completely agree.
>>>>>>>>>>> I love all the work that David did on the site.  He made it 
>>>>>>>>>>> much more
>>>>>>>>>>> user-friendly
>>>>>>>>>>> and useful, but I think that there are many new tools and 
>>>>>>>>>>> models now
>>>>>>>>>>> (OLPC, etc.)
>>>>>>>>>>>
>>>>>>>>>>> I liked, but didn't totally love the ardour.org model.  
>>>>>>>>>>> Still - there
>>>>>>>>>>> are many things broken
>>>>>>>>>>> at cSounds.com and many things that I have wanted to include,
>>>>>>>>>>> feature, update for
>>>>>>>>>>> years now....
>>>>>>>>>>>
>>>>>>>>>>> Brent Boylan and Brian Wong have offered to help.  Maybe 
>>>>>>>>>>> others will
>>>>>>>>>>> as well.  And maybe
>>>>>>>>>>> the first thing we should do is decide upon a new and more 
>>>>>>>>>>> open design.
>>>>>>>>>>>
>>>>>>>>>>> Dr. B.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Nov 30, 2007, at 2:05 AM, Steven Yi wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>                    
>>>>>>>>>>>> Regarding the link: The link on csounds.com should probably 
>>>>>>>>>>>> be changed
>>>>>>>>>>>> to link directly to csounds.com/journal instead of that 
>>>>>>>>>>>> page that is
>>>>>>>>>>>> shown there that doesn't have the latest journal.
>>>>>>>>>>>>
>>>>>>>>>>>> Regarding the site: it really should be migrated to some 
>>>>>>>>>>>> kind of
>>>>>>>>>>>> content management system or blog system IMO.  (Drupal 
>>>>>>>>>>>> might be a good
>>>>>>>>>>>> solution as PHP or Rails are the only real options on what is
>>>>>>>>>>>> available to use for csounds.com).  A nice looking drupal 
>>>>>>>>>>>> based site
>>>>>>>>>>>> is ardour.org.  As it is now, I find myself hardly looking at
>>>>>>>>>>>> csounds.com as it's very hard to find anything as the 
>>>>>>>>>>>> categorization
>>>>>>>>>>>> is not as narrow as it could be.  (The way drupal's site's 
>>>>>>>>>>>> main
>>>>>>>>>>>> categories are listed up top and how those pages are 
>>>>>>>>>>>> divided could be
>>>>>>>>>>>> a model). Using blog software such as wordpress might be 
>>>>>>>>>>>> enough as
>>>>>>>>>>>> well.
>>>>>>>>>>>>
>>>>>>>>>>>> steven
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Nov 29, 2007 8:24 PM, Brent Boylan  
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>                      
>>>>>>>>>>>>> I have actually been thinking about volunteering to help 
>>>>>>>>>>>>> with the
>>>>>>>>>>>>> site but
>>>>>>>>>>>>> have not wanted to step on any toes, so to speak. There 
>>>>>>>>>>>>> seem to be
>>>>>>>>>>>>> some
>>>>>>>>>>>>> usability issues to address. But if you just want someone 
>>>>>>>>>>>>> to help
>>>>>>>>>>>>> keep
>>>>>>>>>>>>> things up to date I would like to help with that, too. Let 
>>>>>>>>>>>>> me know.
>>>>>>>>>>>>>
>>>>>>>>>>>>> B. Boylan
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Dr. Richard Boulanger-3 wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>                        
>>>>>>>>>>>>>> Thanks Rory,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I will personally try to get to those links you pointed 
>>>>>>>>>>>>>> out as soon
>>>>>>>>>>>>>> as I can.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> But I am looking for help from someone in the Csound 
>>>>>>>>>>>>>> community to
>>>>>>>>>>>>>> keep the site up to date.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> David Akbari - the previous webmaster of cSounds.com (and 
>>>>>>>>>>>>>> former
>>>>>>>>>>>>>> student, assistant,
>>>>>>>>>>>>>> collaborator, and all around brilliant and super 
>>>>>>>>>>>>>> csounder) has
>>>>>>>>>>>>>> started in a graduate program
>>>>>>>>>>>>>> in speech and hearing and so he doesn't have much time to 
>>>>>>>>>>>>>> work on
>>>>>>>>>>>>>> the
>>>>>>>>>>>>>> site any longer.  Thanks
>>>>>>>>>>>>>> David - and good luck to you in your studies and 
>>>>>>>>>>>>>> research.  I can't
>>>>>>>>>>>>>> wait to see (and hear) how
>>>>>>>>>>>>>> you use Csound to assist others and help them hear better.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Sooooooooooooo
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I am looking for a new volunteer to help me update 
>>>>>>>>>>>>>> things, change
>>>>>>>>>>>>>> things, revise things, and keep
>>>>>>>>>>>>>> the site going when I am drowning in OLPC, teaching at 
>>>>>>>>>>>>>> Berklee, and
>>>>>>>>>>>>>> finishing the 2000+ page
>>>>>>>>>>>>>> Audio Programming Book for MIT Press.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Anyone interested in helping out with cSounds.com?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hope so.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Dr. B.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Nov 29, 2007, at 3:41 PM, Rory Walsh wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>                          
>>>>>>>>>>>>>>> Currently the link to the Csound Journal on the 
>>>>>>>>>>>>>>> Csounds.com site
>>>>>>>>>>>>>>> does not give a full index of issues. It stops at summer 
>>>>>>>>>>>>>>> 2006.
>>>>>>>>>>>>>>> Perhaps someone can update it?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Rory.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Send bugs reports to this list.
>>>>>>>>>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>>>>>>>>>>>> "unsubscribe csound"
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>                             
>>>>>>>>>>>>>> Send bugs reports to this list.
>>>>>>>>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>>>>>>>>>>> "unsubscribe
>>>>>>>>>>>>>> csound"
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>                           
>>>>>>>>>>>>> -- 
>>>>>>>>>>>>> View this message in context: 
>>>>>>>>>>>>> http://www.nabble.com/Journal-link..-
>>>>>>>>>>>>> tf4899858.html#a14040564
>>>>>>>>>>>>> Sent from the Csound - General mailing list archive at 
>>>>>>>>>>>>> Nabble.com.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Send bugs reports to this list.
>>>>>>>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>>>>>>>>>> "unsubscribe csound"
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>                         
>>>>>>>>>>>> Send bugs reports to this list.
>>>>>>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body
>>>>>>>>>>>> "unsubscribe csound"
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>                       
>>>>>>>>>>> Send bugs reports to this list.
>>>>>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body 
>>>>>>>>>>> "unsubscribe csound"
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>                     
>>>>>>>>>> Send bugs reports to this list.
>>>>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body 
>>>>>>>>>> "unsubscribe csound"
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>                   
>>>>>>>>> Send bugs reports to this list.
>>>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body 
>>>>>>>>> "unsubscribe csound"
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>                 
>>>>>>>> Send bugs reports to this list.
>>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body 
>>>>>>>> "unsubscribe csound"
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>               
>>>>>>> -- 
>>>>>>> www.cesaremarilungo.com
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Send bugs reports to this list.
>>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body 
>>>>>>> "unsubscribe csound"
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>             
>>>>>> Send bugs reports to this list.
>>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body 
>>>>>> "unsubscribe csound"
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>           
>>>>> -- 
>>>>> www.cesaremarilungo.com
>>>>>
>>>>>
>>>>>
>>>>> Send bugs reports to this list.
>>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body 
>>>>> "unsubscribe csound"
>>>>>
>>>>>
>>>>>         
>>>> Send bugs reports to this list.
>>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body 
>>>> "unsubscribe csound"
>>>>
>>>>
>>>>
>>>>       
>>> -- 
>>> www.cesaremarilungo.com
>>>
>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body 
>>> "unsubscribe csound"
>>>
>>>     
>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body 
>> "unsubscribe csound"
>>
>>
>>   
>
>


-- 
www.cesaremarilungo.com 

I recently learned of a nice little google trick that allows one to search
only a specific site. So the good news is, we can already easily search
csounds.com.  For example, the following google query will search
csounds.com for "tablew":

tablew site:www.csounds.com

Furthermore, google provides the Custom Search Engine service, that enables
the placing of a google search box on the site that only searches
csounds.com.  Here's the link:

http://www.google.com/coop/cse/

Best,
Jake




Brian Wong-2 wrote:
> 
> A search function which is comprehensive for the entire content of the
> site (even excluding the forums) would be a major improvement in
> usability...
> 
> Brian Wong
> 

-- 
View this message in context: http://www.nabble.com/Journal-link..-tf4899858.html#a14117086
Sent from the Csound - General mailing list archive at Nabble.com.

For csounds.com it would possibly be better to use a google search box, 
though. The problem is that some content (most notably the csound 
manual) will be hosted outside the CMS.

-c.

Brian Wong wrote:
> The google custom search looks like an easy solution, though whatever 
> CMS is decided on will hopefully include equivalent or better search 
> functionality. Some links :
>  
> Plone : 
> http://plone.org/documentation/phc_topic_area?topic=Navigation#site-searching
> Drupal : http://drupal.org/handbook/modules/search
>  
> BTW, Jake I recently worked through your EAST tutorial and really 
> enjoyed it!
>
>
> ------------------------------------------------------------------------
>
> > Date: Sun, 2 Dec 2007 08:28:50 -0800
> > From: jacobjoaquin@gmail.com
> > To: csound@lists.bath.ac.uk
> > Subject: [Csnd] Re: Journal link.. - cSounds.com Webmaster Search
> >
> >
> > I recently learned of a nice little google trick that allows one to 
> search
> > only a specific site. So the good news is, we can already easily search
> > csounds.com. For example, the following google query will search
> > csounds.com for "tablew":
> >
> > tablew site:www.csounds.com
> >
> > Furthermore, google provides the Custom Search Engine service, that 
> enables
> > the placing of a google search box on the site that only searches
> > csounds.com. Here's the link:
> >
> > http://www.google.com/coop/cse/
> >
> > Best,
> > Jake
> >
> >
> >
> >
> > Brian Wong-2 wrote:
> > >
> > > A search function which is comprehensive for the entire content of the
> > > site (even excluding the forums) would be a major improvement in
> > > usability...
> > >
> > > Brian Wong
> > >
>
>
> ------------------------------------------------------------------------
> Discover a magical Christmas destination. Visit asksanta@live.ca 
> today! 


-- 
www.cesaremarilungo.com 

I think 'downloads' works best for a new user. That's what they will be
looking for. 'Projects' sounds more like it would include instruments or
compositions, to me anyway. I know when I am introduced to new software, I
go to the site, look for what I need to download and go from there. It's
only if I can't find it quickly, or if what I need to download is confusing
or unclear, that I go to a 'new users' or 'documentation' tab to get
answers. Once I've downloaded the files I need, then I will go to
'documentation' if there wasn't any included with the download.

While I am on the topic of downloads, I hope the new download page will be
more descriptive and not just a page of links. I know I mentioned before
about screenshots and platform icons. That's all fluff that can be added
with styling later. What would be ideal is if frontend programs could be
listed in a way that shows which are active projects, maybe showing the date
of the latest release or something. Of course, that could be on the
developer's site with the download, but it could save the user a lot of
hassle if they weren't interested in something that hasn't been updated
since 1998. Just a thought. As far as descriptions of the software, maybe
the authors themselves would like to contribute a paragraph of text to
explain what their program does.

-- 
View this message in context: http://www.nabble.com/Journal-link..-tf4899858.html#a14118683
Sent from the Csound - General mailing list archive at Nabble.com.

Brian,

Thanks!  I just got blue up and running so I could listen to it.  Very nice! 
I've listened to it 10+ times already.  :)

I'm not sure which version of the EAST tutorial you read through. Just to
let you know that there is a newer version which I put together about a year
ago.  It's basically the same tutorial with some fixes to the html and to
the text.  Hopefully once csounds.com is restructured, it will point to v2. 
You can find EAST v2 here:

Exploring Analogue Synth Techniques v2
http://www.thumbuki.com/csound/articles/east/

Thanks again,
Jake

---- 
The Csound Blog 
http://www.thumbuki.com/csound/blog  



Brian Wong-2 wrote:
> 
> For your interest I am attaching a simple piece in blue that I wrote while
> studying your excellent EAST tutorial. It requires the scala file to be in
> your user directory under ../.blue/scl  and includes 3 of your tutorial
> instruments adapted for microtonal use in blue.
> 

-- 
View this message in context: http://www.nabble.com/Journal-link..-tf4899858.html#a14157350
Sent from the Csound - General mailing list archive at Nabble.com.