Skip to main content
added 39 characters in body
Source Link
CodeYogi
  • 2.2k
  • 1
  • 20
  • 35

Sometimes in Single Page Applications (SPAs) there are pages like Welcome, About, Help or Support which are just static content and don't want to load librarieswhich doesn't require frameworks like Angular to load with them. I often see that people just create component for these pages too which is managed by these frameworks.

The other reason is often these pages have different view as compared to when we enter the application.

What is the recommended approach for pages like these? should I am thinking if it’s a good strategy to serveput them viain web serversserver like Apache or Nginx. What areApache's root directory? Do the pros and cons ofrequest for about page needs to be served by the two strategiesapplication server?

Sometimes in Single Page Applications (SPAs) there are pages like Welcome, About, Help or Support which are just static content and don't want to load libraries like Angular to load with them. I often see that people just create component for these pages too which is managed by these frameworks.

The other reason is often these pages have different view as compared to when we enter the application.

I am thinking if it’s a good strategy to serve them via web servers like Apache or Nginx. What are the pros and cons of the two strategies?

Sometimes in Single Page Applications (SPAs) there are pages like Welcome, About, Help or Support which are just static content and which doesn't require frameworks like Angular. I often see that people just create component for these pages too which is managed by these frameworks.

The other reason is often these pages have different view as compared to when we enter the application.

What is the recommended approach for pages like these? should I put them in web server like Apache's root directory? Do the request for about page needs to be served by the application server?

Sometimes in Single Page Applications  (SPAs) there are pages like WelcomeWelcome, AboutAbout, HelpHelp or SupportSupport which are just static content and don't want to load libraries like AngularAngular to load with them. I often see that people just create component for these pages too which is managed by these frameworks.

The other reason is often these pages have different view as compared to when we enter the application.

I am thinking if itsit’s a good strategy to serve them via web servers like ApacheApache or NginxNginx. What are the pros and cons of the two strategies?

Sometimes in Single Page Applications(SPAs) there are pages like Welcome, About, Help or Support which are just static content and don't want to load libraries like Angular to load with them. I often see that people just create component for these pages too which is managed by these frameworks.

The other reason is often these pages have different view as compared to when we enter the application.

I am thinking if its a good strategy to serve them via web servers like Apache or Nginx. What are the pros and cons of the two strategies?

Sometimes in Single Page Applications  (SPAs) there are pages like Welcome, About, Help or Support which are just static content and don't want to load libraries like Angular to load with them. I often see that people just create component for these pages too which is managed by these frameworks.

The other reason is often these pages have different view as compared to when we enter the application.

I am thinking if it’s a good strategy to serve them via web servers like Apache or Nginx. What are the pros and cons of the two strategies?

Source Link
CodeYogi
  • 2.2k
  • 1
  • 20
  • 35

Strategy for delivering static pages in a web application

Sometimes in Single Page Applications(SPAs) there are pages like Welcome, About, Help or Support which are just static content and don't want to load libraries like Angular to load with them. I often see that people just create component for these pages too which is managed by these frameworks.

The other reason is often these pages have different view as compared to when we enter the application.

I am thinking if its a good strategy to serve them via web servers like Apache or Nginx. What are the pros and cons of the two strategies?