CMS stands for Content Management System. It is a technique or system to store content. When used for websites, a CMS stores the texts, images, videos, etc. All website CMS'es need a computer to run on. They have to actively search all the content for the specific data that needs to be displayed on the current page.

Example

Let's use an example to show what is happening behind the screen (no pun intended :)):

1. A user browses to your homepage
2. Your website then needs to show something, so it asks the CMS what data to render/show
3. The CMS fetches the data from files on the server or from a database
4. The data is returned to the CMS
5. The CMS sends the data to the website
6. Your homepage is shown with all text and images.

User 1--> Website 2--> CMS 3--> Data(base) 4--> CMS 5--> Website 6--> User

Static vs. dynamic

Both static and dynamic websites can use a CMS behind the scenes (the bold text above). The difference is the moment it uses it.

With a static website all the data is fetched when you "build" the website. You press a button or run a command and your computer starts collecting all the data needed to render every page on your website. It then renders and stores every page, which you upload to a hosting platform.

A dynamic website doesn't do this data collection at "build time". Instead you upload all the data and the site to a server. This server then renders each page only when a user needs them.

If you have any questions about this, don't hesitate to contact me.

There are countless ways to build and design a website, but there are basically two main types:

1. Static websites
2. Dynamic websites

1. Static websites

The first type of website is called static because it doesn't need to render or calculate which data has to be send to whoever opens the website. Everyone downloads the same data and the website is rendered 'client-side' in the browser. This means you don't need to have a complicated server to host your website.

2. Dynamic websites

The second type of website is called dynamic because it does need to calculate what data it should send to the browser. Most of the data is processed server-side. This means you need a server that is capable of doing that.

Pros and cons

Obviously both types have pros and cons. And both have specific use-cases. Let's try to list them below (based on the websites I build):

If you have any questions about this, don't hesitate to contact me.

There are lots of ways to build a website, but I want to keep it simple and offer three:

1. A static website build with either Next.js or Gatsby.js.
2. A dynamic website based on WordPress or a simple Ghost blog.
3. A static front-end (Gatsby.js or Next.js) with a CMS back-end (Ghost, NetlifyCMS, Strapi, WordPress).

Don't know what you want or need? Try answering these questions:

1. Do I have very specific ideas or wishes about the looks? Take option 1.
2. Do I want or need to update texts and images often? Take option 2.
3. Actually it's both... Then try option 3.

If you have any questions about this, don't hesitate to contact me.

A custom project basically works the same as a normal design project. There are a few things we do differently though:

1. Our initial discussion (step 1) will be more detailed.
2. We'll make a more detailed schedule (step 2) as it will cost more time.
3. Depending on the size of the project we'll have more test versions and reviews (step 4, 5).

If you have any questions about this, don't hesitate to contact me.

1. Discuss what you want and need

We'll start with discussing what you want and need. For example:

• How many pages do you want?
• What do you want to show?
• How do you want it to look?
• What colors?
• What's your budget?
• Do you have any special needs?
• When do you want the site?

2. Make a proposal

With that information, I'll make a proposal and send out a quotation with an estimated schedule.

3. Get your website data

Before I can start I need the data and images for your website. We will discuss how we can best share it (Dropbox/OneDrive/Email/upload).

I'll also send an invoice with a prepayment for 25%-50% of the total costs, depending on the total amount.

4. Build the first version of your site

After I get approval, received all the data and we agree on the schedule, I'll start with the design of the first version of the website. Once the first version is done, I'll host the site on a test server. I'll email the address so you can review it whenever it's best for you.

5. Get feedback

This is the time to give feedback on the website. Do you like the colors? Do you want to change or add texts? Do you want to show different images? Etc.

6. Finish your site

With that feedback I'll finish the final version of your website. Again I'll host the site on a test server and email the address so you can review it.

7. Release your site

Once you approve the website, I'll send an invite to the repository on Github¹ or share the data as you like (e.g. Dropbox/OneDrive/Email).

I'll also send out the last invoice for the remaining part of the costs.

1. The repository will stay private.

If you have any questions about this, don't hesitate to contact me.

Hosting

For hosting your website I'll use AWS services in a region closest to your customers. Currently I can host 2 types of websites:

1. Static websites will be hosted through AWS CloudFront.
2. Dynamic websites will be hosted on AWS LightSail.

Currently I can't host a custom build-time CMS like NetlifyCMS for you. Strapi, however, is possible but at a cost of €15.00 per month, due to the server requirements of the admin panel.

Backups¹

1. Static website data is not backed up. There is no need as the data is already stored in my Github account, secured with multi-factor authentication.

2. For dynamic websites, I'll make a daily database backup that will be stored for 14 days. After that I will keep one backup per month. The data, like images, will be backed up once a week. I'll keep at least one backup, but depending on the size this might be more (see fair use).

Server upgrades²

1. If I host a static website for you, updates are not applicable. Updates are only needed if AWS significantly changes their CloudFront service.

2. If I host a dynamic website, I'll run security updates on the OS (Ubuntu) and software once a month. Once every three months I'll do a big update where the server will be restarted. That means your website will be offline for a few minutes, so I'll schedule these updates during the night, limiting inconvenience.

In both cases, whenever a big update or upgrade is needed, I'll let you know 2 weeks in advance.

Fair-use³

The pricing for hosting is based on a normal website. Normal in this case is a bit hard to specify or quantify and I don't want to make it too complicated. So, when your site is using more resources (bandwidth, storage, processing power, etc.) than what you are fairly paying for, I'll let you know. If this use is structural and/or not corrected, I'm forced to move your site to a bigger server and charge accordingly.

Illegal content⁴

I believe in free speech and your website can be about everything you like. There is one but: illegal content is not tolerated. If you upload or place illegal content on your website, I'm forced to shut your website down.

1. As described in article x.x of the Terms of Service
2. As described in article x.x of the Terms of Service
3. As described in article x.x of the Terms of Service
4. As described in article x.x of the Terms of Service

If you have any questions about this, don't hesitate to contact me.

Static page (€750)

A basic static website will be made with Gatsby.js and consists of:

1. A homepage
2. A portfolio or a blog
3. An info page (contact, address, pricelist)
4. Custom page (whatever else you want to show/share)

If you take this site as an example, it would contain: About, Pricing, Contact and a Portfolio or How-to.

Dynamic page (€950)

A basic static website will be made with WordPress and consists of:

1. A homepage
2. A portfolio or a blog
3. An info page (contact, address, pricelist)
4. Custom page (whatever else you want to show/share)
5. Install a theme
6. Setup of admin account and minimal plugins

If you take this site as an example, it would contain: About, Pricing, Contact and a Portfolio or How-to. For plugins I'd install and configure: Akismet Anti-Spam, Autoptimize, Nginx Cache, Redis Object Cache, WPS Hide Login and Yoast SEO.

What I don't do

1. I don't design logo's, banners and other brand imaging
2. I don't make or search for images or pictures
3. I don't write the content you want on your website

If you need any of these things, we can of course get a designer and/or text writer involved.

If you have any questions about this, don't hesitate to contact me.

Static page (€5.00 p/m)

• Static websites will be hosted through AWS CloudFront.
• Every website gets its own SSL certificate from AWS.

Dynamic page (€10.00 p/m)

• Dynamic websites will be hosted on AWS LightSail.
• Every website will get its own SSL certificate from Let's Encrypt.
• WordPress and Ghost will be hosted on single 1GB instance with a MariaDB database, Nginx web server and Redis database caching.
• For WordPress I'll use the latest stable version of PHP, Ghost will run in the latest LTS version of Node.js.

Static front-end with custom CMS

• Static websites will be hosted through AWS CloudFront.
• Every website gets its own SSL certificate from AWS.
• CMS will be hosted on AWS LightSail.

WordPress and Ghost (€15.00 p/m)

• WordPress and Ghost will be hosted on single 1GB instance with a MariaDB database, Nginx web server and Redis database caching.
• For WordPress I'll use the latest stable version of PHP, Ghost will run in the latest LTS version of Node.js.

Strapi (€20.00 p/m)

• Strapi will be hosted on single 2GB instance with a MariaDB database, Nginx web server and Redis database caching.
• Strapi will run in the latest LTS version of Node.js.

Domain name (€0.50 p/m + yearly fee)

You can choose to register a domain name yourself or add it to the hosting package. If you choose to let me manage it, it works something like this:

• You choose a domain name or already have one.
• I'll buy or transfer the domain and link it to your website.
• The domain will always be owned by you and can be transfered to your own service anytime.
• The domain name will be charged once a year. The exact fee depends on the top-level domain (.nl, .com, ...) I will invoice it separately.

• Possible top-level domains: check this list
• Pricing of top-level domains: check this PDF

If you have any questions about this, don't hesitate to contact me.

All terms related to pricing are listed in the Terms of Service. The list below is just a summary and not leading.

1. I generally will ask for a prepayment of 25-50% of the total price.
2. For larger projects (business only), I'll send an invoice with each test version.
3. The payment term is 14 days for businesses (30 days for consumers).
4. Payment can be fulfilled through iDeal or bank transfer.
5. All prices are excluding VAT (21%).

If you have any questions about this, don't hesitate to contact me.

It is possible that you want to change some things on your website. The cost of additions or changes to your website:

• Within 4 weeks after release: free
• Self hosted: € 50 per hour
• Hosted by me: € 30 per hour

If you have any questions about this, don't hesitate to contact me.