created Jan 5, 2019
One problem: not much distinction given between a "web app" and a "website".
If the web app operates over the public internet, then I assume that the web app requires users to login and work from a dashboard. Web apps used for banking, tax preparing, and content management are examples.
These web apps are tools, meant to complete tasks. These web apps don't need to worry about being indexed by search engines. Users login, do work, and move on.
These publication-like websites work fine with HTML and some CSS on the client side. The server-side can be static HTML, produced by whatever means, such as a complex git-based workflow, a simple web-based CMS, or an author using an editor on a local machine with the user FTPing the HTML files to the server.
Little mention in the thread about the number of web app users or website visitors expected. A small web app that's used internally at a corporation probably does not need to worry about scaling via load balancers, etc.
Something to learn this month: