At the moment the website is a ~~~single static HTML file~~~ SPA built with lit-html on client side fetching the content from a static JSON file , it fits well since it will not be updated often from a structural point of view but it will be needed to give non-technical content editor the ability to update the contens of the website (at least the texts).

A standalone WordPress installation is excluded from this evaluation since it will be quite overpowered.

Proposals:

• WordPress REST from https://api.bitrock.it
• continue with static JSON file
• Ghost v2.x

Following from #2 , the website will then need to be based on a dynamic template engine to take advantage of the decoupling from the content and reducing source code.

Lit-html will be the ideal solution since we will only need pure aesthetic and stateless components.

For performance and SEO best practices it will be rendered sever-side by Puppeteer on build time.

To achieve scroll animation we are using the scrollIntoView browser API which is wide adopted across browsers, but unfortunately Edge & Safari aren't supporting the smooth behavior at the moment, which execute the nice-looking scroll animation.

Polyfills seems to be available, we need to test their effectiveness and eventually implement one of them on the project.

• image (provided by @alessandromenini )
• title
• description
• author?

Reference: https://www.linkedin.com/post-inspector/inspect/https:%2F%2Fdatabiz.it%2F

Add a flag (ideally an url parameter) to activate a kinda of totem mode of the website, removing navigation links and main CTA button making the hero ideal to be displayed in fullscreen ( a bit like a live wallpaper...) and then automatically scroll the page like a presentation/slideshow.

Follow the same implementation with a Node.js server and deploy on Heroku, refer to bitrockteam/bitrock-website#18 and bitrockteam/bitrock-website#2 .

• databiz.it domain pointing to Heroku deploy
• add Travis CI config
• build pipeline working
• Travis deploying to Heroku

Same as bitrockteam/bitrock-website#2 .

• databiz.it domain pointing to this GH Page
• add Travis CI config
• build pipeline working

Motivation:

Giving the nature of single-page website with very few updates a nice solution to achieve simplicity, performance and separation of contents from (dynamic) templates can be found in VuePress, since we are now growing quite confindents with it.

Switching to VuePress we can return to publish the website on GitHub pages since the result will be a static page, removing the need of a platform (and costs) as Heroku while keeping al current advantages.

Taskslist:

• create a branch to setup the new VuePress v1.0 project
• move contents to static .md files
• plugins to install
  • SASS preprocessing
  • google-analytics
  • back-to-top
  • pwa
• custom components to develop
  • main template with multi content (https://medium.com/@adam.collier/creating-a-blog-with-vuepress-44ec0fed9718)
  • hero with particle.js
  • timeline
  • slider
  • top navigation, generated by config.js file
• apply CSS from current version
• add in public folder
  • static assets
  • internal services redirect pages (ehour, apriporta)
• update TravisCI config to new build pipeline
• databiz.it domain to point GitHub page

• Google Analytics
• Iubenda

Pressing the browser's back button cause to "exit" from the website (since its a one-page).
It would be nice to bind the sliding animation to the browser native history.

By now the hero unit on the website sets the height only when the page in first loaded, keeping it then fixed if the window or the viewport is resized.

Add the ability to make it readapt "live" via JS events or with some good CSS!