Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
I am developing 1 project but I am little bit confused to choose which technology I should use
I go for AngularJs, but why AngularJs?
I go for WordPress, but why WordPress?
Can anyone suggest me the best option?
The answer is not so simple, because there are many types of fields on which selected technologies can be used and as #steur36 said before, it depends on your project requirements.
Basically, Wordpress is a CMS and its prime functionality is to provide all functionality to run and display a simple webpage (its a mix of frontend and backend). Wordpress could be used with success for small websites or blogs (where the main feature is to provide and/or display basic content, like: text, images/media/gallery, files ect.)
In the other side, there is the AngularJS, a javascript frontend framework where you can focus on visual side of your project and how the content is present to the audience. With AngularJS (or any other javascript frontend framework, like: Ember, Backbone, ect.) you can build the appearance of any webpage or web application, but to store the content, you may also need some RESTful backend server as well (to create queries to the server).
As small summary, Wordpress is great for small and medium websites/blogs (for bigger projects, it might not be adequate). With AngularJS (and probably with some RESTful backend server, because it depends if you really need it) you may create almost any complex projects, but the time of creation will definitely increase relative to Wordpress.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 10 months ago.
Improve this question
For those who understand about software architecture, I would like to know if it is a good pattern to create an application that exposes an API to be consumed by a front-end application (React/Vue/Angular) for the end-user (people) and also renders traditional web views to be used in the administration area?
All of this inside the same server and basically the same application meaning in the root folder of the app I would have to folders: front-end (React/Vue/etc) + back-end (Express/Laravel, etc.)
The back-end not only exposes an API for the front-end but also renders web views for the administration area
The front-end consumes the APIs and renders views for the enduser.
I like this approach because I don't have to fill the front-end (React/Vue/Angular) with views for the administration area, but I don't know if it is something that other people or companies do?
Sure, why not?!
Many headless CMS's already do this. They have an API, a UI for the admin and then let you build your frontend on top of that.
But then again, why not also decouple your backend and admin views?
Expose admin actions on the API and then you can write your UI in whatever you want. You can still use Vue/Angular/React, but it would be stored in a separate repository from the public frontend and potentially be served from elsewhere too.
This may give you greater flexibility and scalability long term, but only you can decide which is the right solution for you.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 11 months ago.
Improve this question
I created a project with React, but now I'm thinking of SEO
My project is very simple, although it shows 3D Models using React Three Fiber
But it also shows pages that are defined depending on some videos obtained from Vimeo (using an API), making the site a little dynamic, since we don't previously know which pages will be shown
The question is, can this site be successfully built using Gatsby, as a Static Sites Framework, or do I have to use an SSR Framework like Vercel's Next, because of the pages that will be generated from an API
Yes Gatsby is a good solution. If you realize in the future that you might need to be re-building the app a little more than you are comfortable with, then you can re-hydrate the browser on the users end to query data that you get from an api. This keeps the benefits of SSG (speed, robustness, and SEO), but adds some flexibility and dynamic nature to your application. You can set it up with the Gatsby docs (which are great for any problems you might have with Gatsby in the future). Extra info below: https://www.gatsbyjs.com/docs/reference/config-files/gatsby-ssr
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I have developed a basic web app using normal client-side code (not using angularjs) and the Laravel framework for the backend. A friend (in the software business) is joining to help me refine it and he questioned me using a PHP framework and instead says he would re-write it using AngularJS.
Is AngularJS capable of full read/write of a database to create a dynamic website? Since AngularJS is a javascript framework, I only understood that to mostly be used for front-end and a project would still need a back-end language like PHP.
Thanks,
Angular is a front-end (i.e. browser) framework - it can't run on the server without lots of backflips and hacks, and wouldn't buy you a whole lot anyway.
You could write the back end using node.js to connect to your databases and possibly get Angular running partially on the server to generate your initial pages. This is a technique known as "isomorphic javascript" (among other terms). It's an optimization, but if what you've got works I'd stick with it.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 7 years ago.
Improve this question
Still did not get. Why use angularjs 2.0 with dart if dart comes with dart-webui with binding and templates and you can annotate whatever you want to be either service (classes), component or whatever.
This is a question.
Because, you are in the middle of a big explosion of technology.
There are many many frameworks and languages being born right now, each of them with their own view of what you need. None of them will have everything you need and must of them will overlap in what they offer. Even technologies from the same vendor.
This is happening in the world of:
Cloud Infrastructure (Azure, Amazon, etc)
UI (Angular, Polymer, Dart, etc)
Storage (SQL, NoSql, Big Data, etc)
and many more ...
It will be up to you to decide what to leverage from what tool if you are using multiples tools that offer the same thing.
I don't see a good reason to use Angular.js 2.0 with Dart because there is also Angular.dart 2.0 which is a better fit if you want to use Dart.
Dart web-ui was the predecessor of Polymer.dart. Polymers primary intent is to create reusable web components (build your own HTML tags). Angular is for building complex web applications. Angular has it's own way of building components but it is designed to support Polymer elements or plain web components as well.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I am considering to use AngularJS for building my catalog on my E-Commerce platform based on CakePHP. I plan to query database using Slim REST API in CakePHP. This is what the catalog would look like.
I am not sure if I should use AngularJS. If I should can someone please help me to know why I should use it and how it shall be a benefit to use AngularJS in building such catalog page?
I personally have used AngularJS, EmberJS, HandlebarsJS and dabbled in some other things. In my humble opinion AngularJS is one of the best frameworks to use. It is backed by Google and heavily used in the web development community. After getting stuck once on a bug in Angular, I emailed one of the AngularJS creators, and received a response from him within a couple days. I've found that although the learning curve isn't the easiest, its easier to learn than many of the other frameworks I've played with.
I quote angular's website:
HTML is great for declaring static documents, but it falters when we try to use it for declaring dynamic views in web-applications. AngularJS lets you extend HTML vocabulary for your application. The resulting environment is extraordinarily expressive, readable, and quick to develop.
Personally I have found that using angular has drastically reduced the amount of code that I've had to write to get a web-application to work in JavaScript. The current company I work at uses Angular to run one of their e-commerce sites. Mobile integration is excellent.
Just looking at your link quickly, that is a very doable application in angular. You'll need a RESTful webservice to get the data, but everything else can be rather easily handled using Angular on the front end. Here is a robust tutorial making a full featured app in angular, I think it should give you a good idea of what is possible with angular.