Hey! Robert, Thanks a bunch. Concur on the dig on static pages ;-) Well, I think I can set up 4-5 required pages easily with a combination of content and ftl. At least for now looks reasonable. Will know more when I actually try it.
Meanwhile notice that the URL takes the typical application/control/request pattern. For example the polices page URL becomes ecommerce/control/policies Since I am planning to mount ecommerce as root e.g. http://<myecomsite.com>, is there a way to keep the URL for policies page as http://<myecomsite.com>/policies i.e. without the control/ part. In fact rethinking as I am writing this down. http://<myecomsite.com> Regular Landing page of ecommerce (main without the /ecommerce/control/main) http://<myecomsite.com>/policies http://<myecomsite.com>/aboutus http://<myecomsite.com>/contact Since I am planning multiple catalog and plan to have them as menus on the home page, so once the user clicks on a particular catalog that becomes the selection and the navigation changes to http://<myecomsite.com>/<catalog-name> I am considering creating ecommerce clone for each of the catalogs with a catalog-name as the mount point. This is a whole lot of questions, and thinking aloud here. However, will this work? I am still unclear how to handle the root mount point with a few cms style pages right under root without the trailing control/ URL. Perhaps I should create a new component with a different controller (like in products in ecommerce) and not touch ecommerce. The new component can then be mounted a root and act as the cms. Thanks a bunch in advance Paul -- View this message in context: http://ofbiz.135035.n4.nabble.com/static-content-pages-tp4635197p4635207.html Sent from the OFBiz - User mailing list archive at Nabble.com.
