[Project]: Some options to host your static website

[szikszail]

1.1. Title

Some options to host your static website

1.2. Details

Hosting static websites, either documentation or a React website is rather usual. There are many ways to do it, either paid or free, for a higher or lower load, with more or less technical knowledge required. This article will compare some such options with either examples or working templates.

2.1. Area

DevOps, Software Development

3.1. Stream

Cloud (aiding engineers to gather experience with cloud)

4.1. Format

Article (covering the idea in a written format)

5.1. Artifact

Article (an article on the Idea Pool WeAreCommunity page), Software (a source code and/or a delivered software/package)

[kornel-filep]

Some options:

• Netlify: https://www.netlify.com/with/react/ - this would be a general use-case
  Gatsby Cloud: https://www.gatsbyjs.com/products/cloud/ - specialised in GatsbyJS, however they were bought by Netlify, so it might merge with the Netlify offering in the future.
• Github Pages: https://pages.github.com - mostly appropriate for documentation or project websites. Using Jekyll you can create websites quickly using markdown.
• AWS, Azure, GCP: all of them have solutions for static web site hosting, but they are mostly enterprise focused.
• Cloudflare: https://pages.cloudflare.com - has support for Hugo, which can generate sites quickly using JSON and Markdown.

[szikszail]

It is a good list. We can take most of them.

However, this article should be framework-agnostic, mainly concentrating on solutions that host static files (HTML, JS, CSS, and assets). Generating these static files can be touched, but that would be a separate topic.

We can choose one of the simple tools to generate the static site (e.g., Jekyll); then, we can check and compare multiple options for hosting those:

1. AWS S3 (+CloudFront)
2. Azure Storage
3. Google Cloud web hosting
4. GitHub Pages
5. Netlify (if possible)
6. Cloudflare (if possible)

[szikszail]

I propose the cover this idea as follows:

1. We create a repository. In this repository, we place:
   1. A documentation (1 markdown file) containing the article's actual content, including pictures, code examples, etc.
   2. The solution used to demonstrate the hosting options: we can use the generated static website from the documentation as a subject.
   3. We would mainly use the GitHub Pages hosting solution to host the documentation.
2. We create an article, summarizing and highlighting points of the actual document we put together.

[kornel-filep]

Sounds good to me @szikszail