To clarify, let's break it down step-by-step.

Imagine I have a 50-page website with pages like About Us, Home, Contacts, Products, Categories, Popular Items, etc. The goal is for each page to be in its designated folder rather than the root directory. For example, the *Products* page should be in a folder named "2" or "Products" (the name doesn’t appear in the URL). Inside the *Products* folder, there might be subfolders like *Product 1*, *Product 2*, etc.

How can I organize this in Site Designer within a single project? Is it possible at all?

Maybe I’m misunderstanding how Site Designer works. Should I create each page separately, upload them to specific folders, and then adjust the links? Or is there another way?

P.S. Congratulations to me on my 100th post!

There is no other way.
People who have subfolders, like me on my component sharing pages, usually have one 'main' project at the server root and several other projects put into their own subfolders. In my case, I have separate projects for each framework, and the 'main' project is the index page and the entry pages for each framework. Some people have way more sub-projects, probably making the navigation structure one hell of a job not to get lost in.

And oh, congrats to your 100th post! I had the same 'jubilee' sometime in 2006, I think.

You have cruelly killed my barely breathing hope!
Well, then why does the website designer have the ability to create folders and files built into the resources? There, for example, you can create a Products folder, then create an index.html file in the Products folder. And it seems like a small thing - be able to edit this file and the supporting project.

Then maybe I should just make a multi-page website as usual, as much as the SD allows, and then after exporting, manually transfer all the files to their own folders and manually do the linking? I'm just worried that the css styles won't fly off. Has anyone tried this option?

You can create the folders, but as soon as you create a page, it will end up in the root folder, and you will have to move it manually into one of the folders after export. If you want to go that route, You will have to check where those pages are after every export, and probably move them again - and again. I'm not just brutally killing someone's hopes, I'm just making aware of what is not in the scope of SD.

SD does indeed keep all the pages of a project (.rsd) file at the same level. I regard that as an advantage, and not as a disadvantage. It reduces the potential complexity of the program.

I use the procedure mentioned in Inger's first post in this thread. It probably wouldn't be worth it for just 50 pages, but I use the procedure because the number of pages in my site is well in excess of the 125 page limit of an SD project file.

For just 50 pages I would be inclined simply to use SD's Page Manager to set the .html file names and the order of them in such a way as to make it easy to navigate to any particular file while working in the SD project file. For example, all the file names in the Product category could start with 'prod-'. I may be wrong, but I assume that ease of navigation while working in the project file was the reason for the hope to have each page in its designated folder.

Inger's procedure is easy, especially if one
1. uses the Windows OS which allows multiple SD project files to be open at the same time;
2. uses the whole-page Component technique (mentioned in https://www.coffeecup.com/forums/site-d … e-website/ ) to transfer page layouts from one SD project file to another;
3. lets each of the SD project files keep its own CSS and image etc. files, and doesn't complicate things by trying to have a common CSS file or image folder for the whole website (I don't think that a bit of duplication hurts, and my aim is simplicity).

Frank

About hope—that was a joke!
The program developer is an absolute genius, practically a magician, and I have no doubts about that! If the developer hasn’t included the multi-folder functionality, there must be a valid reason behind it. I completely trust the developer; I just want to understand the “correct” logic in my case to choose the right approach.

Thank you, Frank! I need to process what you wrote, understand it, and then I will respond.

I did understand that it was a joke!
Frank has explained very well the advantages of keeping all the pages together in one project. In another site that I have made (https://kandoraservice.de), in three languages, I was initially thinking of creating a sub-project for each language, but instead, I decided to keep it all in one, just naming the pages with the language abbreviation at the start. That project has about 25 pages per language.

Thanks everyone! Looks like I've more or less decided