Re: Architecture Question

Hey Y'all: I like having separate pages for each piece of content. For example, the tutorial about writing HTML is web.htm, while the tutorial about MySQL is mysql.htm. This makes Apache logs meaningful and gives users a distinct URL to go to. All files call the same header and footer. Then, for situations where the user needs to interact with a particular bit of website data, like entering/editing product information, they go to product.htm. That script will have all sorts of different views/operations depending on what the user entered and which buttons they push on the forms. This keeps code for a particular element centralized. It's easier then having separate pages for, say, entering new products, editing existing products and deactivating old products. In the end, though, it's a combination of what you feel most comfortable with and what your users will find easiest. --Dan -- T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y More than just answers. Solutions. (SM) http://www.analysisandsolutions.com/ 4015 7 Av #4, Brooklyn NY 11232 v: 718-854-0335 f: 718-854-0409