The idea is you use skeleton.css (now bootstrap instead) and superfish.css if you want to stick with the scaffold app style, but you can drop them completely otherwise. web2py.css is for some framework-specific things that you might want to keep even if you don't keep the scaffold app style (flash messages, form errors, grid, etc.). Even some of those things you may want to change, but at least it's clear what web2py-specific things need to be styled.
Anthony On Tuesday, April 24, 2012 6:53:58 PM UTC-4, greenpoise wrote: > > I have been reading the book and this is what I found for the default > layout: > > "skeleton.css" contains reset, grid layout and form styles > "web2py.css" contains web2py specific styles > "superfish.css" contains menu styles > > Then somewhere on top, I found base.css and its explanation. Then you have > skeleton.css and the superfish.css. I find that this standard/default > layout to be a maze/ordeal. Is hard to follow. Yes, basic changes can be > done by changing things here and there but I think it gives ZERO desires to > do an abrupt change to the page style. Do you guys follow my thoughts on > this?? How can web2py be improved?? and also, has anyone started a project > from scratch without running into issues??? > > I previously mentioned this in another post and mentioned a CMS (MODx) to > have a really good templating system. I believe web2py could pick some > things from it. I get really frustrated when I dig into this part of making > my app look like what I want. > > > cheers > > d. >
