If you have the basic layout of a page and want to implement it in a React environment, the main task usually is to modularize the layout and provide components for its parts. The header and footer, the main navigation, maybe a sidebar, and, of course the editable content area – all these should be isolated and turned into dedicated components.

With Scrivito, the diversity of web pages is taken account of by taylored page types and the components used to render them. For example, the homepage and standard pages usually include a main navigation, while landing pages don’t.

This applies analogously to any editable area to which content of different types can be added: columns, text, images, boxes, etc. With Scrivito, those types are represented as widgets.

Web applications based on Scrivito are single-page apps running in the visitor’s browser. There’s several advantages to this (first and foremost: speed), but, when using services that require authentication, no remote server is there to hide sensitive data such as login credentials from curious users.

Such use cases can be solved with serverless computing (or serverless infrastructure) services such as AWS Lambda. They free you from having to set up and maintain your own infrastructure merely for accepting or processing form content, or using APIs requiring authentication.

While on-site SEO can be accomplished primarily by following a set of recommendations dealing with site and URL structure, content consistency, site speed, indexing, and so forth, connecting your content to social media comes down to enriching pages with the required pieces of information and rendering social cards from them.

Deploying a Scrivito-based app without any preparatory effort is as simple as uploading the built app to the “Deployment” section in your Scrivito dashboard. This makes your app available on your scrivito.net subdomain.

Scrivito partners with Netlify. After claiming your Netlify website via your Scrivito dashboard, there’s a considerable number of deployment and automation options to choose from. To name just a few:

• Drag/drop your project directory on the “Deploys” section of your site to have it built and published.
• Set up continuous deployment from a branch of your Git repository (e.g. at GitHub) for staging or production.
• Perform A/B tests from two branches.
• Use outgoing webhooks to trigger an action or report a status on specific events during deployment.

Read more at netlify.com.