In the case you described, the template would have to be kept in memory and the old, previous content of the project would first have to be removed before the new content can be loaded. The WebsiteX5 project concept does not provide for this, since the projects consist of template and content and are only treated together by WebsiteX5.

Thank you for answer. This is a bit of a disadvantage. You can make a huge project in Wordpress. Website X5 forces you to split a large project into several smaller ones, but they then behave like separate websites even though the template uses the same components. However, Website X5 names them differently in each project, and then the same template looks completely different. It's a shame that it's not possible to insert a code to use one template in the Code Menu.

If you want, I'll turn the post into a suggestion for the developers to read.

Yes of course you can. I think this function would be useful for others as well. When creating large e-shops, it is not good to have long loading pages when switching to another category (project).

maybe I didn't understand, but in my opinion you could just duplicate the project and you would have identical templates and settings ...
then in the various projects, you would remove the parts you didn't need.
Having said that, if you use the automatic generation of product pages in ecommerce, you can easily manage even projects with many products, without the need to split it up...
also because splitting an ecommerce only generates a lot of practical problems (more unconnected shopping carts, etc. etc.).

Well, for example, I will have a large website (not e-commerce) where there will be an extensive photo gallery of dogs and cats. Since the project has a large size, it is appropriate to divide it into several projects according to the comments here. Then I will have one project DOGS and another CATS. When I copy the project I will have the same template, but the moment I upload both to the website, they act as if they have a different template. This then causes that if I move in the DOGS category, the transition between pages is smooth, but the moment I switch from the DOGS category (project) to the CATS category (project), it takes longer to load, because the template, CSS, etc. are loaded again. Even though it will project copied to the site, the pages behave as two different projects even if the content of the templates is identical.

The slight delay in switching should probably bother cat and dog lovers less if the content is good.

if you have a lot of images, use dynamic galleries that do not weigh down the site.
That way you will have only one project.
I apologise because I had understood (from the title) that you end up with different templates despite the duplication, instead you meant that you notice that when passing from one project to another the template is loaded again...
Granted that I doubt you notice this slowdown, I doubt just as strongly that such a request would be taken up by Incomedia, I think it would be impossible to realise and make little sense, in my opinion of course.

I know it is already told in the thread but anyway:

You should not split the e-commerce in sub-projects. Why not?

A user will have to know exactly what category he has to start in, if he will search for products. The search only functions in the actual project or sub-project.

If a user wants to buy products in more categories he will have to visit 3 baskets and he will have the products for a category in as many orders as you have categories.

You should never present a huge amounts of photos on X5-pages. Instead use album software for that.

You can then use X5 pages to show few images on a form that is eye-catching or "nice".

Some examples:

Here: https://www.bramminginfo.dk/minibyen.html you see a slideshow from an album. It is shown in an iframe and the only thing that is on a X5-page is a html-object with few lines of code (for the iframe).

The slideshow is set up to start with a random image, 4 seconds between images and is set as non-breakable.

A bit down the page is a grey area, that shows some text and some images in a circle that can be flipped. These images is integrated in a X5-object - the circular object.

The album can be seen here on a X5-page https://www.bramminginfo.dk/billeder.html and here as stand-alone https://bramminginfo.dk/lokationsbilleder/

The album can have several sub-levels (sub-folders). Images can have titles, dates and text shown. It is a matter of settings. If the image is geo-tagged a button (M) is shown and when clicked, the position will be shown on GoogleMaps.

The text can have html-code so it is possible to have links and other stuff. The album can be toggled in "normal" or "full-screen" view. The album has a very effective breadcrumb menu so it is easy to move up and down the levels.

IN the album can be set up if a html-page with the sub-level should be created. This makes it possible save a sub-level as PDF. The PDF can be mailed and when the thumbnal-images in the PDF is clicked the image from the album will be shown from your server.

An add-on in the album is a serch-app. Using this app the whole album can be searched for text and it can be set up how many sub-levels should be searched.

In the album that has a folder for nearly each page on the site, the images is resized to 1000px width.

Here is an album where the images is in medium resolution. The images can be zoomed via the mouse-scroll button.

The album requires no database. It is easy to install, maintain and use.

This is only some few of the functions in the LuxAlbum. It is totally free to use.

There are also free database based albums. Like zen-photo https://www.zenphoto.org/

And then the JsAlbum that is free but you have to pay for it if you want to have more than few images in the album.

The link to the medium-sized images disappeared

It is here: https://bramminginfo.dk/udstillingsalbum/index.php

@Chosea, but which is the site? put the address (url) here
I think that if you notice long loading times... you either have heavy images, or you have an overly complex and heavy page structure.
So you have to sort it out