cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Schultz, Gary - COMM" <GSchu...@commerce.state.wi.us>
Subject RE: Best Way to Build a "Traditional" Website Structure Using Coc oon?
Date Mon, 12 Apr 2004 15:27:45 GMT
The best place to start on css is at Eric Meyer's css/edge web site.
http://www.meyerweb.com/eric/css/edge/. Eric is the css guru. Check out the
css resources listed on the css/edge web page. Many of the resources will
point you to cross browser compatible css techniques. I've learned a
considerable amount from Eric's and the other css resources he mentions on
css/edge.

The use of css should only be a major concern if you are supporting Netscape
4.x or IE 4.x. We do not support Netscape 4.x or IE 4.x. I'm one tweak away
from having my website work in Mozilla 1.0.2 for MacOS 8.x/9.x. I have the
web page layout working in IE 5.0 for Windows, and if I can make it work for
an old version of Mozilla on a legacy Mac, I think I've accomplished good
enough cross browser compatibility. It also works in Konqueror and Epiphany,
so my compatibility crosses over to Linux.

Gary T. Schultz
Web Technical Administrator / GIS Coordinator
Wisconsin Department of Commerce
6th Floor
P.O. Box 7970
Madison, WI 
1-608-266-1283

-----Original Message-----
From: David Swearingen [mailto:david25@yahoo.com]
Sent: Sunday, April 11, 2004 3:54 PM
To: users@cocoon.apache.org
Subject: RE: Best Way to Build a "Traditional" Website Structure Using
Coc oon?


Gary:

I've not considered CSS for layout since I'm comfortable with
tables...but I'm open to hearing if there is a better way to layout
header/footer/nav/body in a way that is consistently handled by most
browsers.

David

--- "Schultz, Gary - COMM" <GSchultz@commerce.state.wi.us> wrote:
> Have you considered cascading style sheets (css) for layout instead
> of
> tables. I'm using that for my web sites and I think it tends to
> simplify
> things. Use Cocoon to build the html element structure and css to
> layout the
> web page. This way you do not have to worry about getting the
> different
> parts of the page in the correct table layout element. The basic
> layout of
> our Commerce Housing website at http://commerce.wi.gov/housing/ is
> css
> based. 
> 
> Gary T. Schultz
> Web Technical Administrator / GIS Coordinator
> Wisconsin Department of Commerce
> 6th Floor
> P.O. Box 7970
> Madison, WI 
> 1-608-266-1283
> 
> 
> -----Original Message-----
> From: David Swearingen [mailto:david25@yahoo.com]
> Sent: Thursday, April 08, 2004 5:04 PM
> To: users@cocoon.apache.org
> Subject: Best Way to Build a "Traditional" Website Structure Using
> Cocoon?
> 
> 
> Newbie question:  I am designing a dynamic website and have chosen
> Cocoon as the architecture.  The website will contain a 'classic'
> structure, with left navigation, masthead, footer, and a body section
> containing content.  The various elements, like the navigation,
> surrounding the content will rarely change of course.  I will define
> these in XML.  So there will be a leftnav.xml, masthead.xml,
> footer.xml.  In a typical website like this the whole thing is in an
> html table, and the top row of the table contains the masthead, a
> left
> cell contains the navigation, the right cell contains the body text,
> and the bottom row contains the footer.  Very straightforward, done
> all
> the time.  I've built numerous sites like this with Struts and other
> tools.
> 
> Now imagine the request comes for a page, like faq.html.  I know how
> to
> make Cocoon grab faq.xml and run it through a XSL transformer to add
> the html markup and then serialize it out.  Done this already.
> 
> But for my website I need to generate the entire table context for
> the
> page, then insert the masthead html, then there's more html that
> closes
> the table cell and opens a new one, generates the left navigation
> html
> from leftnav.xml, closes the cell, spits out my content from faq.xml,
> etc., you get the picture.
> 
> Ideally I want my page structure html -- the code that defines the
> overall page table that holds all the elements -- in one file, and
> the
> masthead, navigation and footer in their own files, and then of
> course
> the content documents are in their respective xml files.  This makes
> for easy site maintenance.
> 
> So what's the best way to do this in Cocoon?  It seems it could be
> accomplished in numerous ways, but I have a feeling there's a
> best-practice here.
> 
> Thanks,
> David
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! Small Business $15K Web Design Giveaway 
> http://promotions.yahoo.com/design_giveaway/
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
> 


__________________________________
Do you Yahoo!?
Yahoo! Tax Center - File online by April 15th
http://taxes.yahoo.com/filing.html

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Mime
View raw message