Serverless full static website

Serverless or not serverless?

What means serverless? A website that can be hosted on any webserver, full static, that doesn't require any API or any other server or database to connect to.

I decided to go with VueJS because is the best that I know so I could reuse the same components created in other project with no problems.

With Whoobe you can decide to go full static serverless or if you need a production deployment you can still connect to it.

It's your choice depending on a single project.

Going servless full static

Whoobe will generate your landing page/website homepage based on the article set as homepage = true

Whoobe generates websites, ecommerce or landing pages automatically without any extra settings.

At the end of the generation process you will have your landing page in the target folder you set (default is ./dist in the whoobe-nuxt installation folder)

Deploy your website/pages

In local environment just deploy the ./dist folder to a webserver.

If you are using services like Netlify or Vercel,

create a repo with you ./dist folder
create a project on your hosting provider
connect your project to your repo without setting any build command, just a plain ./dist output folder settings

Anytime you will commit a new version your website will be updated.

If you plan to use Whoobe in a cloud you need to:

create a repo of Whoobe Generator
deploy on a provider like Vercel
run the generate from Whoobe Studio
deploy with a webhook the Whoobe Generator

Updating pages and content

When you need to update any content (page, media, etc) using Whoobe Studio it will automatically update your CMS data.

Then you can run a new generate command, commit your changes and your site will be updated automatically.

Pros of serverless

The main benefits are:

working in local environment (development) to create, change, update any content
no server is needed
no extra cost for expensive infrastructure (AWS, Google Cloud, Azure, etc.)
no server maintenance or update
no database backup
fastest deployment time
limit downtime risks due to server bottlenecks
fast response
secure by the core since is just HTML, CSS and JS
easy portability and backup (using repos)

Cons of serverless

When you have a website that has many updates, or even many editors, publishers you may need a production Whoobe CMS deployment

frequent updates requires a new generate command