Not sure what you mean?
The routing is automatically generated for you. If you follow what's explained in the steps above.
That is true indeed. My advice is If you are not familiar with NodeJS and why/when is it used better wait until the final integration in 3.0 final before start working on a project, as the workflow and options may change.
Hi @Teodor it didnât before I created a Type Page route I selected a Type: URL and realised it was the wrong âTypeâ but it would not edit, just kept reverting back from page to URL. figured out where the file was and could see that the Page and the URL type syntax where included in the same reference to the page. So the only way I could fix it was go in the file and remove the URL reference type form the file now it works. Probably a bug, but wasnât game to mention it!
What are you referring to exactly?
I am referring to the docs above (the first post of this topic). When you create a layout page and a content page from this layout using the Pages Manager, the routes are created automatically.
What were your steps exactly? Were they different than what is explained here?
Converting a html page to and .ejs creating the route has to be done manually, because it doessnât do it automatically, which was easy enough but it is when I experienced the âissueâ, but I now know what is going on with .ejs files now and routing.
We will be improving that and also adding more integration with the pages manager for new files creation so people donât create static files per accident
Well kind off, but I couldnât work out the above example for routes, because the Routes properties doesnât look like the images above, there is the âTypeâ drop down option is where I experienced the error.
It would be good to know when to use: âURLâ vs âPageâ vs âContentâ so to find out I tried them.