Hi, Although I am still going through the tutorial, I am thinking about how to best structure a site that would use Agavi. I have a few questions about this:
- What is an Agavi "app". Should it be a whole site or just one "feature" of a site (e.g. blog) - What is an Agavi "module". Why have things in separate modules? Although at this stage I might not fully understand the answers (and so I may post again later), I would like to start thinking about a particular site I would like to make with specific features: - A few nearly-static pages - A news/blog page (I think I should be able to make that one!) - Basic events calendar (it will be similar to a blog actually, maybe just ordered differently) - Gallery (it is Flash based, so the output is just XML, but the 'upload' pages need to be html based) - A login page On the nearly-static pages I would like to include the next few events/last few news items (I'm thinking that 'slots' should be used here...?) What would be a good way of structuring this site: what should be the modules? How should the 'nearly-static' content be stored? I am more used to a more CMS where you have pages (often with fixed URLS), and in the pages you include calls to the code runs on a particular page. I'm not sure how such a thing should be expressed using Agavi. Regards, Michal. _______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users
