[CUWiN-Dev] Tentative drum roll... New CUWiN site mock-up now online:

[David Young]

On Wed, Mar 23, 2005 at 08:50:43AM -0600, Sascha Meinrath wrote:
> On Wed, 23 Mar 2005, David Young wrote:
> 
> >On Mon, Mar 21, 2005 at 12:15:58PM -0600, Sascha Meinrath wrote:
> >>Hi all,
> >>
> >>I've been working with Steven on a new website for the CUWiN project. 
> >>The latest mockup (this is about the 4th iteration and the first we 
> >>felt was complete enough to get everyone's feedback on).  Please post 
> >>any feedback to the forum topic http://cuwin.stevesgallery.com/forum/4 
> >>specifically for this purpose.  Keep in mind that this is a ful content 
> >>management system -- so there are different roles which allow access to 
> >>different features.
> >
> >Drupal has a lot of interesting features, but I don't see how it has 
> >improved our site.  The appearance of the website has actually gotten 
> >worse, and the organization has not improved.  More than anything else, 
> >the website needs a usable site architecture.  I have a hard time 
> >finding things that I *know* are on the site.
> 
> I asked Steve _not_ to change the site architecture (which pained him) -- 
> so it currently mirrors our existing one.  If you list what sort of 
> changes you'd like to see we can improve things -- just let me know.

As a developer, it is important that I can

        * get to the "root" of web-browsable source code in one click

        * start downloading a .tgz or a boot-image in two clicks
          (the bozotic SourceForge site accounts for about half the
           clicks; if we have to screen-scrape SourceForge for its mirror
           URLs to get an adequate interface)

        * get to all the docs in one click (now they're spread
          across two or more pages)

        * find the particular doc I am looking for (CUWiN software
          specs, grant text, "Further Reading") quickly

When earlier I mentioned use-cases, that is the kind of thing I meant.

> >This Creative Commons License is new, and it needs to be consented to.
> 
> Yeah, I was just trying to put a name to our current practices for sharing 
> information.  If folks have objections, I'm happy to take other 
> suggestions, return to the (c) CUWiN, etc.

Let's return to (c) CUWiN.  Then we can wait for somebody ask us to
re-use our materials before we take the time to figure out a license.

Dave

-- 
David Young             OJC Technologies
dyoung at ojctech.com      Urbana, IL * (217) 278-3933