You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Swig is nice, but there are some features of Angular I really would like to have - in particular, signups and logins without leaving the page you are on, more responsive pages (especially for the career pages and the forums), and if we deliver JSON data to the website for use in angular, we can easily use the same "API" to interface with an app (perhaps in the future for our appdev team?)
However, the site would have to be converted to use Angular templating instead of Swig templating. Would it be worth it to make the switch?
The text was updated successfully, but these errors were encountered:
You should definitely switch, but at this point you should switch to Angular 2. For the mobile app you could use Ionic 2 / Angular 2 and have a unified development model for desktop and mobile.
Swig is nice, but there are some features of Angular I really would like to have - in particular, signups and logins without leaving the page you are on, more responsive pages (especially for the career pages and the forums), and if we deliver JSON data to the website for use in angular, we can easily use the same "API" to interface with an app (perhaps in the future for our appdev team?)
However, the site would have to be converted to use Angular templating instead of Swig templating. Would it be worth it to make the switch?
The text was updated successfully, but these errors were encountered: