Headless CMS

Definitions & benefits

Tools & Concepts

Open source

Features

Authentication

Custom plugins & Marketplace

Webhooks

Multilingual CMS

APIs

Dynamic Zones

User roles & permissions

Content Modeling

Security & Privacy

Use Cases

Ecommerce

Blog

Forum

About Strapi

Life at Strapi

Releases & Roadmap

Events

Community

News

The Tutorials section covers an introduction to Strapi, some advanced technical content, product updates and releases. From basic workaround to in-depth development guides. 

Tutorials

How tos

Get all the latest updates, news and events.

Subscribe to the newsletter 📣

Are you trying to figure out which computing approach is suitable for your business? On-premises and cloud computing are different approaches to managing and accessing computing resources. On-premises solutions are installed and run locally on the same physical or virtual servers that a company uses to run its business. And cloud computing refers to delivering computing resources over the internet rather than using local servers or personal devices. 

This article will compare on-premises and cloud computing based on location, responsibility, scalability, and cost to help you select the best approach for your business.

## What is Cloud?

Cloud solutions are a popular option for companies of all sizes because it eliminates the need for businesses to invest in and maintain physical infrastructure, allowing them to access computing resources on an as-needed basis. 

Companies can access and use computing resources, such as data storage, processing power, and software applications, on an as-needed basis, rather than investing in and maintaining their own physical infrastructure. You can access data and applications from anywhere, which is particularly beneficial for companies with remote or distributed teams.

## Types Of Cloud

There are several types of cloud computing, each with its characteristics and benefits:

### Public Cloud
In a public cloud, computing resources are owned and operated by a third-party cloud service provider and made available to the public over the internet. Public clouds are generally easy to use and scalable but may have less control and security than private clouds.

### Private Cloud: 
In a private cloud, computing resources are dedicated to a single organization and are typically operated on-premises or in a dedicated data center. Private clouds offer more control and security than public clouds but may be more expensive and require more maintenance.

### Hybrid Cloud
A hybrid cloud combines a public and a private cloud, where the organization can use both types of cloud computing to meet its specific needs. For example, an organization may use a public cloud for general computing tasks and a private cloud for sensitive or confidential data. Hybrid clouds offer flexibility and the ability to scale resources as needed.

### Community Cloud
A community cloud is a hybrid shared by a group of organizations with common computing needs and goals. Community clouds offer the benefits of both public and private clouds but are typically more expensive than public clouds.

### Multicloud
A multi-cloud environment uses multiple cloud service providers to meet its computing needs. This can give the organization more flexibility and options but also be more complex to manage. In a multi-cloud environment, workloads can be distributed across clouds based on specific requirements and objectives, such as security, compliance, and cost. 

Overall, the choice of a cloud solution will depend on the specific needs and resources of the organization, as well as its priorities in control, security, cost, and scalability.

## Pros and Cons of Cloud

Here are some pros and cons of cloud computing:

### Pros:
- **Cost**: Cloud computing typically has a lower upfront cost and offers a pay-as-you-go pricing model, which can benefit companies with limited budgets or unpredictable resource needs.
- **Scalability**: Cloud solutions are generally more scalable than on-premise solutions, as they can easily be adjusted to meet changing resource needs.
- **Flexibility**: They can be accessed from any location with an internet connection, which can benefit companies with remote or mobile workers.
- **Maintenance**: The cloud provider typically handles the maintenance, updates, and management of the infrastructure and resources. This can save time and resources for the company.

### Cons:
- **Dependency on internet connection**: Cloud solutions require an internet connection to be accessed, which can be a limitation for companies in areas with poor or unreliable internet connectivity.
- **Security**: While Cloud providers often have strict security measures in place, companies may be concerned about the security of their data when it is stored and accessed remotely.
- **Customization**: They may not offer the same level of customization as on-premises solutions, as the company is limited to the resources and options provided by the cloud provider.
- **Loss of control**: With Cloud computing, the company is dependent on the cloud provider for the availability and performance of the computing resources. This can be a concern for companies that value control and autonomy.

## Who Are Cloud Service Providers?

A cloud service provider is a corporation that specializes in providing businesses and people with cloud computing services. Infrastructure as a service (IaaS), software as a service (SaaS), and platform as a service are examples of these services (PaaS). 

Cloud service providers frequently provide public and private cloud computing solutions, allowing organizations to select the best match for their needs. These providers often have high-availability cloud computing systems in place to assure the security and continuation of their clients' companies. These systems are intended to reduce downtime and guarantee that organizations can rely on cloud services.

## What is On-Premise?

On-premises refers to software or hardware installed and run locally on the same physical or virtual servers that a company uses to run its business. The company is responsible for maintaining, updating, and managing the infrastructure and resources required to run the software or hardware.

## Pros and Cons of On-Premise

Here are some pros and cons of on-premises solutions:

### Pros:
- **Control**: With on-premises solutions, the company has complete control over the hardware and software and the infrastructure and resources required to run them. This can benefit companies with specific requirements or the need to customize their solutions.
- **Security**: On-premises solutions can offer better security, as the company controls the physical location and access to the data. This can be especially important for companies handling sensitive or confidential information.
- **Performance**: On-premises solutions may offer better performance, as the company controls the hardware and infrastructure and can optimize them for their specific needs.

### Cons:
- **Cost**: On-premises solutions often require a more significant upfront investment in hardware and infrastructure.
- **Maintenance**: The company is responsible for maintaining, updating, and managing the infrastructure and resources required to run the software or hardware. This can be time-consuming and require specialized skills and resources.
- **Scalability**: On-premises solutions may not be as scalable as cloud solutions, as it can be more difficult and costly to increase or decrease resources as needed.
- **Flexibility**: They may be less flexible than cloud solutions, as they require the company to be physically present to access and use them.

## On-Premise Vs. Cloud: Differences

On-premises and cloud computing are different approaches to managing and accessing computing resources. Here are some key differences between the two:

### Deployment
**On-Premises:** In an on-premises environment, all of the necessary resources and infrastructure are located within the enterprise's IT infrastructure. This means that the enterprise is responsible for maintaining and managing the hardware, software, and other resources required to run the solution. 

This approach offers the enterprise a high level of control over the solution, as they have complete access to and ownership of all the resources and infrastructure. However, it also means that the enterprise must allocate the necessary resources and personnel to maintain and manage the solution, which can be time-consuming and costly.

**Cloud**: Public cloud computing involves using resources hosted by a service provider, which businesses can access and use as needed. It offers scalability, flexibility, and a pay-as-you-go model and can be accessed from anywhere with an internet connection.

### Compliance:
**On-premises**:  These solutions allow companies to control their data storage and handling practices, which is essential for compliance with regulatory mandates such as HIPAA or FERPA. Failing to comply with these regulations can have serious consequences, so businesses must manage their data to ensure compliance carefully.

**Cloud**: Businesses that use cloud computing must carefully evaluate their provider's compliance with industry regulations and ensure that sensitive data is secure and privacy is protected for customers, partners, and employees.

### Control:
**On-Premises:** In an on-premises setup, companies keep all of their data on-site and completely control how it is used. This can be positive or negative, depending on the specific circumstances. For example, companies in regulated industries or those with particularly strict privacy concerns may be more hesitant to adopt cloud computing due to the potential loss of control over their data. On-premises solutions offer more control and autonomy but also require more maintenance and management from the company.

**Cloud**: Data ownership is a key concern in cloud computing, as data and encryption keys may be stored by a third-party provider. This can create risks in the event of downtime, as businesses may not be able to access their data. It is important for companies to carefully evaluate the security and availability of their data when choosing a cloud provider.

### Security:
**On-Premises:** On-premises environments can provide a higher level of security and privacy, which is especially important for industries with sensitive information, such as government and banking. Despite the benefits of the cloud, security concerns may lead these industries to prioritize on-premises solutions despite their higher cost.

**Cloud**: Security is still the main obstacle to adopting cloud computing. High-profile cloud breaches and the potential loss of employee personal information or intellectual property have caused IT departments to be wary of the security risks.

## Conclusion

In conclusion, on-premises and cloud computing are two different approaches to managing and accessing computing resources. On-premises solutions are installed and run locally on the same physical or virtual servers that a company uses to run its business, while cloud computing refers to the delivery of computing resources over the internet.

Both on-premises and cloud computing have their own pros and cons, and the best choice for a company will depend on its specific needs and resources.

If you would like to continue learning about hosting your Strapi application and how to do it, here are some valuable resources that you may find useful: 
- [6 Top Deployment Options For Your Strapi Application](https://strapi.io/blog/6-top-deployment-options-for-your-strapi-application)
- [Deploying Strapi to Your Own VPS](https://strapi.io/blog/deploying-strapi-to-your-own-vps)
- [How to Deploy Strapi Docker Container On AWS Elastic Beanstalk](https://strapi.io/blog/how-to-deploy-strapi-docker-container-on-aws-elastic-beanstalk)
- [Deploying Strapi MySQL on a Traditional Hosting Provider](https://strapi.io/blog/deploying-strapi-my-sql-on-a-traditional-hosting-provider)
- [How to Deploy and Scale Strapi on a Kubernetes Cluster](https://strapi.io/blog/how-to-deploy-and-scale-strapi-on-a-kubernetes-cluster-1-2)

Continue discussing this topic further or connect with more people using Strapi on our [Discord community](https://discord.com/invite/strapi). It is a great place to share your thoughts, ask questions, and participate in live discussions.

[![Cloud CTA.png](/uploads/Cloud_CTA_d2b64e7adc.png)](https://strp.cc/3XziQPo)

In this article, we will compare on-premises and cloud computing in terms of location, responsibility, scalability, and cost to help you decide which approach is best for your business.

The Ecosystem section covers everything related to the world of Headless CMS and Strapi's place in it. 

Ecosystem

On-Premise Vs Cloud Solutions_ Which Is The Best For Your Business_.png

medium_On-Premise Vs Cloud Solutions_ Which Is The Best For Your Business_.png

small_On-Premise Vs Cloud Solutions_ Which Is The Best For Your Business_.png

thumbnail_On-Premise Vs Cloud Solutions_ Which Is The Best For Your Business_.png

On-Premise Vs Cloud Solutions: Which Is The Best For Your Business?

My name is Fagbuyiro David, a software developer and technical writer. i like sharing my experience as a developer with others.

 
In this tutorial, we will be looking at what Strapi is, how to install Strapi, and a few global key features in Strapi. I will also talk about the importance of these features with a brief explanation of the features and installation process.

## An Overview of Strapi
Strapi is an [open-source headless CMS](https://strapi.io/) for creating quick and readily-manageable APIs. It allows developers to create flexible API structures with a beautiful user interface easily. 

Strapi can be used with various databases, including PostgreSQL and many others. Strapi enables users to consume APIs from a content type via Get, Post, Delete, and Put requests, mostly performed manually.


## Installing Strapi
To install Strapi successfully, a few basic things must be implemented.

- Strapi does not support Node 15. Only LTS versions are supported (v14 and v16). Other versions of Node.js may not be compatible with the latest release of Strapi. 

- We will use Node 14, so after downloading Node 14 (LTS) from the [Node official site](https://nodejs.org/en/blog/release/v14.17.3/) during your installation, make sure you are connected to the internet during the installation so it can download all the other attachments needed.


## What is Strapi?

[Strapi is an open-source, Node. JS-based, headless CMS](https://strapi.io/) that saves the user a variety of time-consuming tasks at the same time as giving them the liberty to apply their preferred equipment and frameworks.

## How to Install Strapi

Once you have the above software installed, enter the on your Terminal the following commands:

**yarn command**
 ```yarn create strapi-app my-project --quickstart```

Or

**npx command**
```npx create-strapi-app@latest my-project --quickstart```

### Steps to Follow After the Installation
1. Open your command prompt and type the below command to confirm if it has been installed successfully and what version has been installed.

```bash
    #For Node.js, you type: 
    node -v 
    
    #For the NPM version, type:
    npm -v
```

2. After the version confirmation, you need to enter the below command to create the first Strapi project:

```bash
    npx create-strapi-app@latest my-strapiproject1
```

*Running the above command will prompt you to choose your installation type.*

3. Navigate to the first option, “**Quickstart**” with your navigation keys “up and down", then press the **Enter key** to proceed and follow the instructions to continue.


![Strapi installation screenshot](https://lh6.googleusercontent.com/Dgjqn0Wg4KCqQu6ru7od_Ezh5EJiogPvOq1tegU0KIZbKl1Gs-z5ZwvHJricDXdEVjM-IgFo8RND5uPMT7P1rEWL8vYFvs9dXIWb5eH9jqS2Kj1U-r6enwdaqHOK1oC14mBoQxr1BqNLEPywWQ)

4. The final step is to run your created project by typing the below command in your command prompt after successfully creating your first Strapi project and installing the required packages.

On your terminal, navigate to the folder where Strapi is installed and run the command below to start the Strapi application.

```bash
        npm run develop
```

The above command will open the registration page for the application. Once you've registered successfully, you'll be redirected to your dashboard page to manage your application.

![Strapi dashboard](https://lh3.googleusercontent.com/HYANaaGn0RcvLDbI0Hr21H-R52pHj44x_0r113trp13x8JOkeqDdtXF_RTlx0Dpw9drPXOjs_Rc9EI_y8x--BRFd2UEPARBFSufDQhMo80PaijCGuR-x614nP9eFbre7-UQkUGExNNSK9ajdjg)


## Benefits of Using Strapi
1.**Better Rendering**
You can now produce pages at deployment time and serve them over a CDN. With Strapi and a site generator, only the most applicable zone of the mound is running when a user makes a request, speeding the entire operation by degrading the series of ways.

2.**Advanced Security**
You do not have to worry about vulnerability or insecurities while utilizing Strapi with your static websites. You do not have any reason or need for a server-side language to be executed, thereby reducing your attack surface area and the threat of malware code injection.

3.**Establishment Features**
Strapi Enterprise Edition includes developed Role-Based Access Control( RBAC), Single Sign On( SSO), and establishment Support.

4.**Scaling Traffic Over Cost**
Because your files are loaded through the CDN, the CDN effortlessly compensates for improved traffic when your app gets further queries.


## Global Key Strapi Features

1. **RBAC:** 
RBAC refers to Role-Based Access Control, a group of operations and permissions you can grant to users. Assigning permissions to users or user groups is more complicated than using roles to add, delete, or modify permissions. Roles become especially helpful as the size and complexity of your user base grow.


![Roles in Strapi Feature](https://lh3.googleusercontent.com/3SjM1EoktM2dpJmbG5BkGSKHF5P-Mm87TVWoMmRCEa3RgcT4RNASjVZW-9lQZTuAMKRqcZqNTh5Y8RpTQvMI__efP3BZnmPziFGNivM2uSv2d8s3fnJXXZhejsp2HaJiquNfJ2tRNBdFzQykVcPHQBg)



**The three roles in Strapi Community Edition are:**
- **Super Admins**: The Super Admins have access to and control all features and settings.
- **Editor:** The Editors can edit, publish, and manage user-generated content.
- **Authors:** The authors are limited to managing and publishing the information they have produced.


*You may configure all of your users in the permissions settings' user section, where you can find them all. You will have access to a created URL link upon user creation that you can provide to your new user to complete their registration.*


More Custom Roles are available in the [Enterprise Edition](https://strapi.io/pricing-self-hosted): unlimited custom roles in the Bronze, Silver, and Gold plans.  The Bronze is [available for free to students, open-source, and non-profits](https://strapi.io/blog/announcing-free-strapi-enterprise-editions-for-students-open-source-and-non-profits).


2. **Dynamic zones** 

Teams may design reusable content models with the least number of changes feasible with Dynamic Zones. 

Dynamic zones are areas of your application where you let content editors dynamically choose what component to include. So, when you design the application, you define which components can be included in a dynamic zone when creating each content instance( e.g. the homepage). Editors then decide which component to select for that zone. A dynamic zone includes one or more components.


3. **Providers**

Providers extend the plugin's essential capabilities, such as uploading media files to Rackspace instead of the local server or using Amazon SES for emails instead of Sendmail. Certain plugins can be enhanced by installing and configuring additional providers.


You can find a list of Providers available in the[ Strapi Marketplace](https://market.strapi.io/providers). 


### Installing Providers in Strapi

The following format can install new providers with npm or yarn *@strapi/provider-<plugin>-<provider> --save.* For example, to install providers using the Aws S3:

```
    # Install the AWS S3 provider for the Upload plugin
    npm install @strapi/provider-upload-aws-s3 --save
    # Install the Sendgrid provider for the Email plugin
    npm install @strapi/provider-email-sendgrid --save
```

### Configuring Providers
In the`. /config/plugins.js` file, newly installed providers, are enabled and configured. If this file does not already exist, it must be created. Each provider will have a unique set of configuration options. To learn more, go to the corresponding entry for that provider in the Marketplace or npm (opens a new window). The example below shows the configurations for the Upload plugins.

```js
    // path: ./config/plugins.js
    module.exports = ({ env }) => ({
      // ...
      upload: {
        config: {
          provider: 'aws-s3', // For community providers, pass the full package name (e.g. provider: 'strapi-provider-upload-google-cloud-storage')
          providerOptions: {
            accessKeyId: env('AWS_ACCESS_KEY_ID'),
            secretAccessKey: env('AWS_ACCESS_SECRET'),
            region: env('AWS_REGION'),
            params: {
              Bucket: env('AWS_BUCKET'),
            },
          },
        },
      },
      // ...
    });
```
Please, [click](https://docs.strapi.io/developer-docs/latest/development/providers.html#configuring-providers) [here](https://docs.strapi.io/developer-docs/latest/development/providers.html#configuring-providers) [for the configuration of the email plugins and how to create providers after installation](https://docs.strapi.io/developer-docs/latest/development/providers.html#configuring-providers). Strapi's default [security middleware](https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/configurations/required/middlewares.html#internal-middlewares-configuration-reference) includes a very stringent content security policy that limits loading images and media to "self" only. For more information, see the example setup on the [provider page](https://www.npmjs.com/package/@strapi/provider-upload-aws-s3) or the [middleware documentation](https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/configurations/required/middlewares.html#internal-middlewares-configuration-reference).

## Draft and Publish 
This *Draft and Publish* feature allows you to leave your content as a draft and publish it later using the draft and publish tool. The draft and publish feature is turned on for all newly generated collections and single types. However, the feature can be turned off at the content-type level (i.e. it can be enabled for one content-type but disabled for another).

To use the *Draft and Publish* feature in Strapi, you need to have your content-type already created. You can create a collection type using the collection type builder plugin. 

Once you are done with that, navigate through **Content Manager > Select Collection Type** from the sidebar and click on **Create a New Entry**.

Fill in the input you want to display and click on the Save button. Now we are done with the draft, the next step is to **publish your article**. Click on the **publish** button beside the **save** button. That is how to use the *Draft and Publish* feature in Strapi.

![The Publish Feature in Strapi](https://paper-attachments.dropbox.com/s_A0481687BBBE0700E1EF7AE142FA39739A8844B49F68D1D7B813D7FC2265ADA4_1658859467359_publish.PNG)

### To deactivate the draft and publish feature for a content-type:

- Select Content-type Builder under Plugins on the sidebar.
- Choose the collection or individual type you wish to disable the draft and publish function.
- To access the configuration, click the Edit button.
- Select "Advanced Settings" from the tab.
- Select the FALSE option in the DRAFT/PUBLISH area.
- To confirm the feature's removal, click the Finish button.

![Disable the Draft and Publish a Feature in Strapi](https://paper-attachments.dropbox.com/s_A0481687BBBE0700E1EF7AE142FA39739A8844B49F68D1D7B813D7FC2265ADA4_1658859108427_bio.PNG)

> Note: Some roles and permissions may be necessary for publishing content. For instance, the default roles in the community version only permit authors to generate and edit drafts, whereas editors are allowed to publish content.

## Unpublishing Content

Published content may be taken down and reverted to draft status. Click on the Unpublish button in the content editor's top right corner to remove content from publication.


## Internationalization in Strapi

As a Strapi user, you can develop, manage, and distribute localized content in several languages, or "locales," using the Internationalization (i18n) plugin. Refer to the [W3C definition](https://www.w3.org/International/questions/qa-i18n.en#i18n) for more details on internationalization.

The i18n plugin allows admin panel users to generate several localized versions of their content ([see user guide](https://docs.strapi.io/user-docs/latest/content-manager/translating-content.html)). It also permits developers to create localized projects by collecting and consuming the appropriate content based on the user's country/language.

All Strapi applications running version 3.6.0 or higher include the Internationalization plugin by default. Lower versions require a migration ([see Update Strapi version](https://docs.strapi.io/developer-docs/latest/update-migration-guides/update-version.html#upgrading-the-dependencies)) as well as manual installation of the plugin.

The plugin can be installed using the Terminal by running one of the following commands:


    npm run strapi install i18n


![Internationalization Plugin Installation in Strapi](https://paper-attachments.dropbox.com/s_A0481687BBBE0700E1EF7AE142FA39739A8844B49F68D1D7B813D7FC2265ADA4_1658906135195_image.png)


## Features of the Internationalization Plugin (i18n)

The i18n plugin is beneficial in so many ways. Let’s discuss some of the features of the i18n plugin.


- **Flexibility**: It uses various components and modifies the structure of each locale's structure and dynamic zones.
- **Clear Navigation:** When reviewing the list of contents or updating an entry, you can easily switch between locales.
- **Smooth Editing:** With a single click, you can copy and paste text from one locale to another, keeping some content consistent across all locales.

 

##  How to Add a New Language to Locales:

To add “Spanish” to our language locales:

- Click on “Settings” under the “General” section. 
- Click on “Internationalization” right under “Global Settings”.
- Click on “Add new Locale.”
- Select “Spanish (es)” in the Locales section and then **save**.

![Internationalization Settings in Strapi](https://paper-attachments.dropbox.com/s_A0481687BBBE0700E1EF7AE142FA39739A8844B49F68D1D7B813D7FC2265ADA4_1658913361909_lang+locales.PNG)
 

## Conclusion
Understanding the Strapi features play an important role in content management. After going through this article, I hope you understand how to install Strapi, the version of node.js that works with Strapi, some key features to know about Strapi, and the main roles of the users in the Strapi community edition according to RBAC. You also learned the installation of the internationalization plugin and how to add a new language to our Locales. For more Strapi features and installation please visit the [Strapi marketplace.](https://market.strapi.io/)


Learn what Strapi is, a few global key features, and how to get started. 

medium_5 Things to Keep in Mind Before Creating a Strapi Plugin.png

small_5 Things to Keep in Mind Before Creating a Strapi Plugin.png

thumbnail_5 Things to Keep in Mind Before Creating a Strapi Plugin.png

5 Things to Keep in Mind Before Creating a Strapi Plugin.png

Global Summary of Some Strapi Key Features

Knowing what type of website best suits your needs is critical. After all, your website is the digital face of your brand, and choosing the right type determines whether you achieve your goals.

At the most basic level, websites are of two primary types: Static websites vs Dynamic websites. Choosing between these website types will depend on your specific needs and goals for your online presence.

In this article, we'll go over everything you need to know about static and dynamic websites. We'll also unpack key elements to take into account when determining what website is ideal for you.


## What is a Static Website?

A static website is a website whose content doesn't change unless manually updated. It’s otherwise known as a flat or stationary web page. Think of it like a printed book – once published, the pages stay the same until a new edition is released.

Static sites are often the go-to choice for displaying content that doesn't require frequent content updates. They're quick to set up, easy to host, and generally cost-effective.

**Some examples of static websites include the following:**

- Portfolios
- Personal blogs
- Newsletter content
- Event announcements
- Informational materials (e.g., an _‘About Us’_ page)

On the technical side of things, static sites contain web pages with fixed content written in HTML code, CSS, and JavaScript. The files are sent from a Content Delivery Network (CDN) to the browser and then stored on a web server.


## What is a Dynamic Website?

A dynamic website is a website that updates its content every time a user visits it. Each update depends on a number of criteria, including viewer demographics, time of day, location, user interaction, data sources, etc.

Unlike static websites, the content on a dynamic site constantly changes and evolves automatically. It’s like a chameleon that transforms based on fresh information.

**Examples of dynamic websites include:**

- Social media platforms
- Online marketplaces
- E-commerce sites
- Writing blogs
- News sites
- Calendars

[Dynamic websites](https://strapi.io/blog/generate-dynamic-website-menus-with-strapi) thrive on flexibility and interactivity. They’re ideal for complex applications where real-time updates and user engagement are paramount.


## Pros and Cons of a Static Website

Static websites come with a number of benefits as well as shortcomings you should be aware of before creating one.

The table below breaks down the pros and cons of static websites to help inform your decision. 

|                                                                                                                        |                                                                                                                              |
| ---------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| **Pros**                                                                                                               | **Cons**                                                                                                                     |
| Building and deploying static websites takes less time compared to dynamic websites                                    | Static website upgrades can be difficult and time-consuming, especially if they're enormous                                  |
| You can replicate the fundamental code of your static web pages to keep things identical while distinguishing yourself | It can be difficult to add additional material to scale a static website once the fundamental framework has been established |
| Static websites are more secure compared to dynamic web page                                                           | Static websites may have stagnant material, making your company or brand appear old                                          |
| Static websites are easier for search engines to rank since they load faster                                           | You can't connect with guests or give them unique experiences with a static website                                          |
| Complex software is not required to create static web pages                                                            | Maintaining a static website can be demanding due to the time and work they require                                          |


## Pros and Cons of a Dynamic Website

In the last section, we talked about the pros and cons of a static site. Now, let’s apply the same to dynamic websites.

|                                                                                                                                  |                                                                                                                       |
| -------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
| **Pros**                                                                                                                         | **Cons**                                                                                                              |
| Dynamic websites allow for rich user interactions like comments, forums, and personalized accounts.                              | Dynamic websites tend to be more expensive than static ones                                                           |
| Dynamic websites automatically update their content and data to ensure users always have the latest information.                 | Dynamic sites typically have design and layout constraints when it comes to presenting materials                      |
| Dynamic websites provide more flexibility by connecting to a content management system (CMS).                                    | With more interactive features and database connections, dynamic websites may be more vulnerable to security threats. |
| Dynamic websites adapt to users’ preferences and behavior for a tailored experience.                                             | Building and maintaining dynamic websites requires more technical expertise and resources.                            |
| Dynamic websites let you coordinate information requests and storage, and their materials can be changed by more than one person | Handling multiple user requests and database queries can affect the speed and performance of dynamic sites            |


## Static Website vs Dynamic Website

Let's look at some of the key differences between static vs dynamic websites:


### A Dynamic Website Negatively Impacts Performance

A dynamic website handles more requests than a static website. Dynamic sites are always linked to a database or data repository from which they constantly pull data. As a result, it takes time to analyze and execute the dynamic functionality compared to static websites, which rarely require a database.

In general, static content loads faster than dynamic ones because static websites are cached in the browser, and dynamic websites are not. On top of that, since it is pre-rendered, a static web page loads quickly. When a visitor visits it, the page doesn't need to go through a database and analyze all of the content.

The data is directly rendered from the CDN. Because of its quick load time, a static web page also makes it easier to rank higher in search engines.


### Static Websites Take Less Time, but Dynamic Websites are More Efficient

One significant difference between a static and dynamic website is that a static one takes less time to design and upload than a dynamic one.

Building a dynamic site takes more time because it requires one or more tech tools. In contrast, a static website is simple to build and doesn't require any special tool. In fact, you can build a static website in a day.

It's worth noting that while dynamic websites may require more time to set up at first, they are far more efficient in the long run.


### Maintaining Dynamic Websites Costs Less

If you're wondering which is cheaper in the long run in this static vs dynamic website debate, the answer is dynamic websites. This is because the database or content management system (CMS) will make the required modifications for your dynamic website, unlike static ones.


### Dynamic Websites are More Interactive and Functional

With more personalization options, dynamic sites prioritize functionality and user experience. For this reason, people often visit dynamic websites more than static ones since dynamic content is updated more frequently. A prime example here is social media platforms like Twitter and Instagram.


### Static Websites are Easily Replicable

You can replicate the basic code of a static web page, allowing you to make changes to the page while keeping everything stable. This is a better alternative to updating your static page code every time you need to send a change to your visitors.


### Static Websites are More Flexible

Yes, flexibility. Even though it has a static appearance, it is quite versatile. Without being a difficult effort for a designer, each static web page from a website might have a separate layout and design.


### Static Sites Take Less Time to Build

One significant distinction between a static and dynamic website is that a static page takes less time to design and upload and easy operation of its software.


### Static Sites Load Quickly

Because it is pre-rendered, a static web page loads quickly. A static page doesn't need to go through a database and analyze all of the content when a visitor visits it.

The data is directly rendered from the CDN. Because of its quick load time, a static web page is also easier to rank higher in search engines.


## What is Strapi?

[Strapi is an open-source Node. JS-based, headless CMS](https://strapi.io/) that handles time-consuming tasks for users, giving them the freedom to apply their preferred equipment and frameworks.


### How to install Strapi

To install Strapi successfully, there are a few basic things to put in place.

- Strapi does not support Node 15 and above. For a successful installation, you need Node14(LTS) or Node12(LTS) but most preferably Node14 (LTS).

After downloading Node14 (LTS) from the [Node official site](https://nodejs.org/en/blog/release/v14.17.3/) during your installation, ensure you’re connected to the internet during the installation so it can download all the other attachments needed.


### Steps to Follow After the Installation

1. Open your command prompt and type the below command to confirm if it has been installed successfully and what version has been installed.


For Node.js, you type: 
```
node -v 
```

For the NPM version, type:

```
npm -v 
```

2. After the version confirmation, you need to enter the below command to create the first Strapi project:

```
npx create-strapi-app@latest my-strapiproject1
```

_Running the above command will prompt you to choose your installation type._

3. Navigate to the first option, “**Quickstart,**” with your navigation keys “up and down," then press the **Enter key** to proceed and follow the instructions to continue.

![](https://lh7-us.googleusercontent.com/hsUHBPxur5EyPNVPd6gn5Mls-PUNOGjW-breeyeXULafst2jl9zkTI-s1Ku-6GQDaoQWAQZkW9vsWVVMtczJlCAzj_BKSSbrOywdYJBVVfNUh0TYPTCXEJdEA-asYD77XX1r5ZDXBZrnfY2VA61swRA)

4. The final step is to run your created project by typing the below command in your command prompt after successfully creating your first Strapi project and installing the required packages.

On your terminal, navigate to the folder where Strapi is installed and run the command below to start the Strapi application.

```
npm run develop 

```

The above command will open the registration page for the application. Once you've registered successfully, you'll be redirected to your dashboard page to manage your application.

![](https://lh7-us.googleusercontent.com/zBWuPoTm9YBsAi4TMv5ynBst-PoZcG1sJBlpBf6IebIdvc00NKV1K9C2xpd8dDHHV5ZdZPZe9hLtK7hUCizpTqVpvsLZV4Fe7LiZNzKy0Ro2bd7_kjcTQidj2HtNdDEJrOVWKVFRqeU6LediHxxy4ok)


### Why You Should Use Strapi in Your Dynamic Website

When it comes to building a dynamic website, choosing the right backend tool can make all the difference. Here's why you should consider using Strapi for your dynamic website:

- **Better development time:** With Strapi's intuitive admin panel and API-driven architecture, you can quickly set up and manage your content. This saves you time and effort during the development process.
- **Higher productivity:** Strapi's modular approach and plugin ecosystem allow you to integrate various features and functionalities seamlessly. The outcome is higher productivity and faster iterations.
- **Effective data management:** Strapi provides robust data management capabilities to help organize your website's content and structure, regardless of complexity.
- **Localization of user content:** With built-in localization support, Strapi allows you to deliver personalized content tailored to your users' preferences.
- **Improved user authentication:** Strapi's system provides better security and access control. This protects your website's sensitive data and ensures a secure environment for your users.


### Why You Should Use Strapi in Your Static Website

1. **Better Rendering:** You can now produce pages at deployment time and serve them over a CDN. With Strapi and a site generator, only the most applicable zone of the mound runs when a user makes a request. This speeds up the entire operation by degrading the series of ways.
2. **Advanced Security:** You don’t have to worry about vulnerability or insecurities when using Strapi with your static websites. You also don’t have any need for a server side scripting language to be executed. This reduces the surface area of your attack and the threat of malware code injection.
3. **Establishment Features:** Strapi Enterprise Edition includes developed Role-Based Access Control( RBAC), Single Sign On ( SSO), and Establishment Support.
4. **Scaling Traffic Over Cost:** Because your files are loaded through the CDN when your app gets further queries, the CDN effortlessly compensates for improved traffic.


## How to Manage Static Website Content in Strapi

We understand that static websites are sites without frequent content updates. But we need to make sure that static websites are maintained effectively to be productive.

The following are some of the Strapi tools that can be used to manage the content of your static website effectively.

- **Creating Content Types in Strapi:** To create content types in Strapi, you have to make use of the content-type website builder, which is only accessible to create and update content types when your Strapi application is in a development environment, else it will be in a read-only mode in other environments. For more information on creating a new content type in Strapi, please refer to [this](https://docs.strapi.io/user-docs/latest/content-types-builder/creating-new-content-type.html#creating-a-new-content-type).


- **Strapi SEO Plugin:** This plugin is a robust Strapi-based comment moderation solution for users, which completely covers the user-moderator process.
- **Internationalization Plugin:** Strapi users can develop, manage, and distribute localized information in several languages, or "locales," using the internationalization (i18n) plugin. For more information about the installation and concept of the internalization plugin in Strapi, please refer to the [Internationalization](https://docs.strapi.io/developer-docs/latest/plugins/i18n.html#installation) [Plugin](https://docs.strapi.io/developer-docs/latest/plugins/i18n.html#installation).
- **Publisher Plugin:** It is a Strapi plugin that allows you to quickly schedule the publishing and unpublishing of any type of content.


## How to Manage Dynamic Content in Strapi

The Strapi marketplace is where you can get industry-leading software and customized plugins to best boost your productivity and add special functionalities to your Strapi app and website.

- **Uploading Media in Strapi:** The Media Library found in the admin panel is implemented using the Upload plugin. You can use it to upload any type of file to your server or an external one.
- **Using the Comments plugin**: With its moderation panel, bad word screening, abuse reporting, and other features, a plugin for Strapi Headless CMS offers end-to-end comments.
- **Email templates**: From the Strapi CMS admin panel, you may create your email templates and leverage the magic to send emails programmatically from your controllers or services. For more information on the Strapi email template and designer, please [refer to this page](https://www.npmjs.com/package/strapi-plugin-email-designer).
- **Authentication:** Strapi authenticates users through a token-based authentication method by giving them a JWT token after a successful password login. For more information about Strapi authentication, check out this article on [Strapi authentication with Next.js](https://strapi.io/blog/a-beginners-guide-to-authentication-and-authorization-in-strapi) or Strapi authentication request documentation.


## Dynamic And Static Building Tools Using Strapi

**Dynamic website tools using Strapi:**

- JavaScript
- React

**Static website tools using Strapi**:

- [**Next.js**](https://strapi.io/integrations/nextjs-cms): It is another tactic solution built on top of React. Next.js's general purpose is to ease development with a smoother and less congested experience. It can be used to construct fast web apps, server-rendered apps, and static web pages, among several other features.
- [**Gatsby**](https://strapi.io/integrations/gatsby-cms)**:** It is built on React and makes use of GraphQL to gather information from various sources. That means it works well with a variety of content management systems, making it easy to set up websites and apps. Gatsby is also recognized for its speed, as it uses pre-fetched information for other sites and only loads the sections of a website that are required at the time. It may also be utilized for progressing single-page websites and has a large [plugin ecosystem](https://www.gatsbyjs.com/plugins).
- [**Hugo**](https://strapi.io/integrations/hugo-cms): It is a Go-based static site generator. It features a lightning-fast build process that makes creating static web pages a breeze. It's arguably the quickest static site generator on the market right now. Hugo comes with a theme library with over a hundred themes to choose from when creating a website.


## Examples of Static and Dynamic Websites

**Static website generators**: A static website generator is a program that creates a completely static HTML website from a set of templates and raw data. In essence, it automates the process of developing individual HTML pages, making them ready to be delivered to users beforehand.

**Examples of static website generators**:

- [**Jekyll's**](http://jekyllrb.com/)
- [**Hugo's**](http://gohugo.io/)
- [**Hexo's**](http://hexo.io/)
- [**GitBook**](https://gitbook.com/)
- [**Octopress**](http://octopress.org/)
- [**Gatsby**](http://github.com/gatsbyjs)
- [**Pelican**](http://getpelican.com/)
- [**Brunch**](http://brunch.io/)


## Conclusion

Strapi is an open-source Node. js-based, Headless CMS that saves developers time while allowing them to use their preferred tools and frameworks. It also allows content editors to optimize the delivery of content (text, photos, video, etc.) across any device.

Strapi is an all-in-one solutions for developing and deploying dynamic websites of any scale with static delivery—it's the best of both worlds.
