Hey Patrick, is there room to extend the static/dynamic page/templates feature you’ve added to wappler in order to have static incremental pre-rendered sites a la gatsby/nextjs or there is needed hosting access to CDN’s in order to have this implemented? Or anything else?
Also, will all these features only be for NodeJS or will they be added to PHP, too?
We were actually already discussing something like that, we can use the templates we have now for node to generate static pages. First we will focus on the node and v3 release, after that we will see if a static site generator with templates is possible.
We are also looking at PHP templates, but it is a bit more difficult there since we don’t have full control over the server and routing like with node.
I’m seeing an incredibly fast-paced pattern of NodeJS being nowhere a month ago to being the primary and recommended framework today.
The problem with PHP/ASP/ASP.NET is that you have a lot of different configurations and versions that you need to support. With node we have lot more control over the environment and the server is build-in.
With PHP we always had to check which version is installed, are the required PHP modules installed on the server, which database drivers are installed, what server does it run on (nginx doesn’t support htaccess files which we use for routing). With node we don’t have this problem, we bundle all the required modules directly with it and we choose which modules we are going to use.
Yeah, I figured that was the case. NodeJS is clearly the way forward. I’m just realising I need to be using that ASAP or I’ll be missing out on features. I’m about to start another project so the logical thing is to go with NodeJS for it but should I wait until v3 stable is released or is it safe to use at this beta 4 stage?
Hi @patrick will the data node be editable via UI.
And if it’s in the plans, should I flatten it or is it OK if I nest?
Data will be editable via the UI. @george will work on the implementation of that, not sure if it will support nested data.
How do we convert existing html pages to .ejs pages without losing any of the required dependencies / files e.g. css and dmx references?
What actually is included in this current beta function I don’t want to be wasting my time trying to figure why something is not working or submitting bug reports if the functionality is not supported in this version? What is incomplete and just wont work?
Hi @George, do you know already if it will support nested data?
I’ve found the beta very interesting because it is allowing me to take a deeper look at how Wappler has designed the solution and will most probably give me an edge in the future. It also has allowed me to make the right questions and provide interesting feedback. But it does require time, constant rebuilding and researching. Time that if you don’t want to spend I would just recommend you to wait for the final version.
If you have static html files, just move them to the views folder and rename it to
.ejs. If you use the same folder structure as in the public folder then it should work directly and all dependencies also. You will need to create routes for them to make them reachable.
6 posts were split to a new topic: Firebase hosting and NodeJS
With an index.ejs file already created, the layout view didn’t attach to the index content page.
If anyone has the same problem, I did this to fix it:
-Go to the routing panel
-Delete the existing root path
-Add a new route set to the same “/” with the same properties
Do you have some temporary work around for this?
What’s your use case?
I would like to create a mostly single page app with dynamic meta attributes.
Here you are. It is explained here.
Is it not possible to add partials inside of a layout page?