On 04/21/2006 16:52, Julian Mehnle wrote: > Koen Martens wrote: > > Now, Julian mentioned that maybe [the mechanisms page] should be split up > > into smaller pages, one for each mechanism/modifier, instead of the one > > page with everything on it as it is now.. Eg: > > > > http://new.openspf.org/SPF_Record_Syntax > > > > or one overview page and several of these: > > > > http://new.openspf.org/auth/The_all_mechanism > > http://new.openspf.org/auth/The_a_mechanism > > > > Personally, i prefer the one page approach. It gives a quick > > overview of the SPF record syntax without clicking or going back in > > the browser, plus it allows for easy printing... > > Scott Kitterman wrote: > > I definitely vote all in one. Additionally since, as Julian mentioned, > > we should shortly have the ability to support anchors in a page, I think > > most of the argument for separate pages goes away. > > I'd prefer the one-page per mechanism/modifier style, with a list of links > to all the other mechanisms and modifiers, perhaps like this (I renamed the > single-mech pages): > > http://new.openspf.org/Mechanism/all > http://new.openspf.org/Mechanism/a > > The reason is that I generally prefer short pages with a strong focus on a > specific topic (IMO that also makes the most sense when having a user > comments facility such as on the PostgreSQL documentation website[1], which > I plan to implement soon). Such single-mech pages could later include > additional info about the differences (if any) in SPFv2.1 syntax/semantics > of each modifier, and other stuff, too. > > As far as printing is concerned, I don't think we should try to structure > our site along the needs of offline media such as printouts. Besides, we > could always offer a facility that bundles several pages (perhaps as > defined by a classical ToC page) in a single HTML document (through page > includes) or even a PDF document. The reverse cannot be done from > monolithic blocks of information. > > References: > 1. > http://www.postgresql.org/docs/8.1/interactive/functions-matching.html#POSI >X-BASIC-REGEXES
My thinking had nothing to do with printing and everything to do with easy of use. The mechanisms page is not so much it's overwhelming. In fact it is one of the most useful pages of the old site and think not much worth messing with at this point. I'd say make it one page and if we need to break it up later for good reason, do it then. Scott K ------- To unsubscribe, change your address, or temporarily deactivate your subscription, please go to http://v2.listbox.com/member/[EMAIL PROTECTED]
