Questions in regards to building a single-page-application

Hi All,

I’m trying to build a single-page-application. From what I’ve gathered from the articles below and other resources. Weweb automatically functions as a single-page app, as long as you essentially set the fixed sections as a instance. For example side bar. However…I’ve been playing around with it and it’s a bit hard for me to tell if it’s functioning that way I want it to. I’m in free-tier mode. So I can only ‘Preview’ and whenever I click on a link on the nav bar for example. To see how the page will load. The entire preview page reloads…Is there a way around that?

One other thing that I haven’t reverse engineered or figured out yet is. There’s a template for a ‘Dashboard’ when i create a new workspace. Which I believe is essentially this page. https://template-dashboard.weweb.io/account/

I’m trying to figure out why the sidebar appears like it’s reloading/resetting on page change between lets say ‘dashboard’ and ‘account’ page. When it appears to be built under the conditions to make it ‘seamlessly’ load. more like a ‘web app’

On the editor, the sidebar is set as a instance I believe and the pages are different. am I misunderstanding something?

Here’s an example of what I’m trying to recreate without the whole page reloading. (Made on another no-code site)

loading

I had this question too

Once you publish the project the sidebar will behave as you’re expecting. WeWeb folks may correct me here, but I believe that in Preview mode each page is considered separate.

One way to test this in Preview mode is to make a change to your linked section on one page and then check a separate page where you also have that same linked section and you will see the changes reflected :slight_smile:

I see, I guess what I was looking for was to actually test the loading times of each section/page and compare it to some other projects I’m doing. But it seems the only way to do that is to purchase a plan and deploy it.