At 3/26/02 01:04 PM -0800, Matt Schalit wrote: >Mike Noyes wrote: >>>>If you're talking about including the sub menus in the pages >>>>themselves, I don't think we can do that with phpWebSite. > > I didn't realize the layout was tied to a theme >and to a php way of making menus.
Matt, It's tied to the phpWebSite code. PhpWebSite is a Content Management System (CMS) written in php 4.x using pear database abstraction. It attempts to meet W3C XHTML and accessability standards. It supports multiple themes, languages (i18n), and modules (plug-ins). A demo of phpWebSite that you can play with is here: http://phpwebsite.appstate.edu/demo/ A CVS demo of the new core is here: http://phpwebsite.appstate.edu/cvsdemo/ PhpWebSite version 0.8.2 is at rc1. It should be available shortly. > I come from the old school of webmasters where I started >with cern httpd and ncsa mosaic and everything was left >margin adjusted. When w3 came out with tables and the >ability to center in the early 90's, that's when I was >doing a lot of web design for the Remote Access Astronomy >Project. > > We just put the right graphics up and layed out the >design using tables and later using frames. Building >a site like openssl.org using basic html 2.0 or 3.0 >code would be fairly straightforward. I didn't realize >that the move to php puts a lot of constraints on things >because I'm not familiar with it. This was fine when sites were static, but most are dynamic now. Dynamic sites make use of databases etc. Writing one from scratch takes a considerable amount of knowledge and time. > So now I'll switch my track of requests. Before I wanted >a simple layout like openssl.org's. > > Now I request all source code to be reachable from a > single menu item. Once the left hand column menu > item for Source Code is clicked, everything we have > is listed as links in the right hand window. There > doesn't have to be a specific link to every file, > but rather I'd suggest it all be listed and linked > towards. > > I request all documentation to be reachable from a > documents menu item in the same way as my source code > request. This business of digging all over place to > find where code and docs are hidden in each developer's > stuff is what makes people frustrated, I gather. I'll take a look at this, but it may cause maintainability problems (e.g. a new page is created and links to it have to be changed on multiple pages.). > I'd rather that the left hand column doesn't expand > itself. When it does so, people have to focus on two > things that changed, the left hand menus and the right > hand page. This is a minor point now that you've told > me how things are done with php. This is an easy change in our config.php. I can specify that the menu is always expanded. Would that suffice? >I've never searched for php themes. Do you have any >pointers? Yes. :-) http://phpwsthemes.sourceforge.net/ http://www.postnuke.com/ http://phpnuke.com/ Note: any phpnuke or postnuke theme will require modification to work with phpWebSite. http://directory.google.com/Top/Computers/Programming/Languages/PHP/Scripts/Content_Management/ -- Mike Noyes <[EMAIL PROTECTED]> http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
