New answers tagged cms
For the edit/admin interface, a SPA is fine. For viewing the content, though I wouldn't recommend a SPA. Generally, you want to generate static pages from the content a user enters. This is faster/cheaper at runtime (serving static HTML is far easier than reading content from a DB and then rendering a page), and better for SEO. It's the approach used by ...
Yes, this better for long run. Isolating core app and providing access through api is good practice currently that way no matter what type of client it is , it can make use of the same environment that web app is using, also there is no need to rewrite api for any specific client Make sure u have proper access control for resource accessing in API
Top 50 recent answers are included