I am working moving a static site into CMSMS and I am at a loss as to how to handle the file/folder structure.
I have put alot of time and effort in the structure of the existing static site and would like to keep some of it compartmentalized; i.e. there are multiple custom homes including a details page, floorplan page, images and pdfs. I already setup the static site so that each custom home is in it's own folder with a folder tree below it.
So what I have done so far is made a folder called 'content' in the root of the site. I will start moving the content of the static site (pics and pdfs) into a folder structure in this folder.
Can anyone tell me a better place to put content, or if the name 'content' for the folder might cause problems for me in future development like CMSMS having its own 'content' folder?
thanks in advance... great scripts I am loving it!
How do you structure your site?
-
jptechnical
- Forum Members
- Posts: 131
- Joined: Wed Jan 12, 2005 12:18 am
-
uptoeleven
- Forum Members
- Posts: 96
- Joined: Sat Dec 04, 2004 10:30 pm
How do you structure your site?
I don't know if this will cause a problem. I would always be nervous of changing file paths on a database driven site as there is no guarantee that the database will be kept consistent with the file structure. My advice would be to set up an installation of CMS on your own machine as a development environment. There are several pacakages out there that can provide a complete "out of the box" installation of php, mysql and admin tools that will run on Windows or on a Mac. Try it out in there.
-
jptechnical
- Forum Members
- Posts: 131
- Joined: Wed Jan 12, 2005 12:18 am
How do you structure your site?
Well it isnt so much a problem with file paths, it is more the best place to put files in the first place.
If someone is making a large site and will have some static pages in there with the dynamic, where would they put the root of their content?
Mainly I want to have a folder than wont neccessarily be overwritten in the upgrade paths as well as an easy way of keeping track of files so I dont have this huge directory of orphaned files to week through... instead I can keep them well organized.
Speaking of running locally... I have a great package for running my projects on a local machine. Checkout microweb http://www.indigostar.com/microweb.htm. I have purchased the full licensed product but only on a couple occaisions. But the trial version just has a nag screen. I use it alot for demoing OSCommerce and POSTNUKE to customers. Now I will be using it to demo CMSMS!
MicroWeb allows you to create a working web site on a CD-ROM. Using a web browser, a user can run CGI programs as well as view html files on the CD-ROM.
That is all fine and well but it also runs excellent locally. Just extract the folder and run the executable and it starts the wwwserver, php, mysql and viola you are up and running. It automatically makes an entry in your host file so that whatever you specify the domain as it will autoresolve to localhost.
If someone is making a large site and will have some static pages in there with the dynamic, where would they put the root of their content?
Mainly I want to have a folder than wont neccessarily be overwritten in the upgrade paths as well as an easy way of keeping track of files so I dont have this huge directory of orphaned files to week through... instead I can keep them well organized.
Speaking of running locally... I have a great package for running my projects on a local machine. Checkout microweb http://www.indigostar.com/microweb.htm. I have purchased the full licensed product but only on a couple occaisions. But the trial version just has a nag screen. I use it alot for demoing OSCommerce and POSTNUKE to customers. Now I will be using it to demo CMSMS!
MicroWeb allows you to create a working web site on a CD-ROM. Using a web browser, a user can run CGI programs as well as view html files on the CD-ROM.
That is all fine and well but it also runs excellent locally. Just extract the folder and run the executable and it starts the wwwserver, php, mysql and viola you are up and running. It automatically makes an entry in your host file so that whatever you specify the domain as it will autoresolve to localhost.
