Normally a simple website may contains 10 ~ 30 pages, so it's easy to upload to hosting server, and all files will locate in "../" root directory in server.
However, what happens if I have hundreds of pages? For example, I want to build a single page for each of my products. When I edit 190+ pages in my ".web" file, the Xara WD becomes extremely slow. More importantly, because all pages are uploaded to "../" root folder, then I get each product with a url of, say, "sitename.com/product1.htm", not "sitename.com/products/catagory1/product1.htm" which is what I dreamed for.
I have mentioned this question before. And thanks to @Acorn, he provided some ideas which I quote below. It's helpful, I tried it. But I really do not sure if I get it correct, because I did lots of manual work in the process of splitting website.
Acorn, can you see this? Here is what I have done:If you've read my reply to your other Post, splitting your site into sub-sites for each Product allows faster updates.
If it is going to turn into an all singing & dancing CMS then this approach will be too limited.
Create two websites:
1. The top site has a master Product page (the one page bit). It has an Embed a website widget the size of your 4 x 3 gallery that also includes the bottom navigation bar.
2. A child site with 44 (or more) smaller pages that each hold a 4 x 3 gallery and a specific navigation bar that reflect the gallery pages position. I would start with First - Previous - Next - Last. There are coding solutions to provide the Go to; the page position and count could be done in a variety of ways. Publish this site and check it navigates as you need.
Back in the Product page, you include the details for the Placeholder and publish and test.
You build a sub-site called Product1.xar and publish it to a sub-folder called Product1.
In Product1.xar, you name each page item#.
In your main site your thumbnails have URLs in the Web Properties > Link to Web or Email address of Product1/item#.
You also need to set Open link to New window or tab.
Acorn
- I build a "category1.web" file for each category of my products, which contains "product1.htm", "product2.htm" etc. Then upload it to "../products/category1" folder in my server.
- do the same for another file "category2.web", upload to "../products/category2" folder.
- In the "mainsite.web" file, I connect each picture of product to their own webpage. For example, link product1 to pege "sitename.com/products/category1/product1.htm" which is pre-uploaded.
Then each product has a unique URL, which is not in root directory. It works in my site.
However, question is:
- I need edit and upload lots of ".web" files before I can edit the "mainsite.web". Because I have lots of product categories.
- Each "category.web" file I need to set the navigation bar which link back to main page, manually.
- After publish, the address like "www.Sitename.com/products/" "www.sitename.products/category1/" will show nothing in browser.
So Im really not sure if I get Acorn's method correct.
BTW, what is ".xar" format, Acorn?? I haven't met it before.
Bookmarks