This is a guest post by Debbie O'Brien (@Debs_obrien), the Head of Learning and Developer Advocate at NuxtJS.
Static Sites in the '90s
...
For further actions, you may consider blocking this person and/or reporting abuse
Nice 😄, Any use cases when we should not use static sites ?
I wouldn’t necessarily build an app as a static site app, or a static web app, if your app is rendered on the server (like a Java web app), or if you’re building a monolith app. Also, if you heavily depend on a web server, like Apache or nginx to serve your app. CMS apps are also not suited for static web apps.
CREATE:Frontend , session as good :)
So what is the best use cases to build static sites ?
Any websites where the content doesn’t change every hour for example. I have built hotel sites, travel agent, the NuxtJS docs, personal websites, websites for companies. Small e-commerce sites. The list goes on.
Thanks, I understand, So now we have
Azure Static Web Apps and Azure Functions API, with these 2 technologies we can even create dynamic sites like hotel sites, travel agent, personal websites, websites for companies, Small e-commerce sites etc.So do we now really need sever side technologies like
PHP, Java, C#, Go, instead We can do all things usingAPIisn't ?Exactly
Do we need server side technologies- well we can still write serverless functions in java and go and c# for example but what I think we don't need anymore is frontend and backend code mixed together to create an application. So let the backend create amazing API's which the frontend can use to create amazing apps/sites.
Thanks, Appreciate, 😄,
CREATE:Frontend, session as good :)Apart from SEO, why we should invest in server side rendering if we can utilize client (visitor) machine for computation for client side rendering?
Frankly, to me it looks like the trend has been started to monetize hosting business.
yes, great question. If only we could just get rid of the servers but sometimes it is good to have server side rendering for large e commerce sites for example as you need constant data changes per minute and don't want to or can't regenerate the site for every single change. There are ways around this sometimes. For example with Nuxt.js you can have a static site that has part of your site as a spa with a spa fallback so for a travel agent you could have a static site with all the hotel details as static but the booking engine page could be a spa inside the static site and that will be rendered client side and as the results of your search don't need seo a spa fallback works perfect here. hope that helps
Thanks for more details, but you can get the same result with something like socket.io (or any bidirectional communication) and that also without regenerating site on client or server side.
It's cool to build static webapp or app with server side rendering, but the usecase (need) is very narrow.
I got tired of JavaScript and built mkws.sh/.
A website template for the modern web. ⭐️ Star to support our work!
Refo
A website template for the modern web
Powerful developer experience meets lightweight output
Effortless Static Site Generation with Flexibility
Feeling overwhelmed by the static site generator landscape? Refo offers a refreshingly simple and customizable approach built entirely on Node.js.
Unlike Jekyll, Gatsby, Astro and others, we let you leverage the power of Node.js modules directly. This means you can generate any kind of website you can imagine, all with the flexibility of your favorite Node.js libraries and servers.
Key benefits:
SVGs, utilizerawimports, andstyleyour components with ease.Go beyond the limitations…