faq

In a static site, the text content and sources of images are hard coded (static) in the HTML file; it shows the same content to all users since the server sends the same response for every request. More information about this on Wikipedia.

• Whether a static or dynamic site is the right choice, depends on the use case.
• Static sites are fast and cheap to host; forms, payments or logins are easy to implement via APIs; no database is required; the downside is that it requires a developer/webmaster to update the content.
• The content of dynamic sites is easy to update with a CMS such as WordPress; content can be generated for individual users; in general, dynamic sites are slower due to the involvement of a database and therefore more expensive to host.
• For a general overview read the blog post or a recent article For a more in-depth discussion about recent trends in this respect read or watch this.

React.js and Vue.js are great. I would have used React if it had made sense for a high performance site with static content, optimized for search engines and usability. But it does not. It would be like going after mosquitoes with a bazooka:

The size of the core of each of these frameworks which is needed to display the content is already bigger than the HTML/CSS/JS of this site (uncompressed react/react-dom is over 100kb while the home of this demo is 82kb including fonts, excluding images). Assuming that additional libraries are used, even more. Additional to this comes the code in order to display the content and functionality.

The loss of performance by sending the framework to the browser and the time the browser needs to parse the code of the framework in order to display the content, might be minimal compared to other sites. But if you play on a highly competitive environment, this can make the difference. Sure, React and Vue are already very lightweight and probably the best solutions for dynamic sites. But using it for displaying a static site with a few pages (which is the case for many company or campaign sites) would be an overkill.

Note: those frameworks are based on JavaScript, all the magic they do can be done from scratch by pure JavaScript. As soon as projects reach a certain degree of complexity, yes, then the use of frameworks makes highly sense.

Yes. Dynamic data, such as stock market prices, weather data, upcoming events and so on, can be consumed from an API and will be displayed with a small delay (depending on the API around 0.1 - 2s). For example, you have a restaurant and want to update the menu which changes every week, that's possible.

Pretty low compared to a site using a CMS. I.e. this site is hosted on a AWS. In order to hijack it, one would have to hack into Amazon - and there is an army of experts waiting who try hard to prevent this. The main risk is when the webmaster is sloppy by not securing the login data for the cloud properly; i.e. when these data are given to freelance devs and are not changed afterwards.

There are solutions like dynamic static site builders, but it's probably not the best solution (yet). For blogs, you better use a CMS such as WordPress or if you are looking for a high performance solution use a RESTful API as backend with a frontend such as React or Vue which are made for high performance and flexibility.

It depends. Simple things, yes, but some basic knowledge of HTML is useful. If you just need to change a telephone number or an address, then it's rather easy and made in 2mins. In other cases, it's not recommended since the styling can break if it's not done properly.