Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 1 year ago.
Improve this question
can somebody suggest real world tutorials / example on react.js vue.js applications. The ones I find on youtube are too basic and lack logic. A real-world application consists of an admin dashboard and frontend. The tutorials you find on youtube are just basic crud applications.
is it just me or the kind of tutorials you find youtube are too basic and they lack logic ? because of this I find it really hard to learn and master new technologies. I struggled to learn and master web development even, coz there was too much basic tutorials out there but none of them were based on real world applications. It took me some time, and combining information from different sources to be able to build real world applications in php and be job ready.
Like when you work as a web developer you won't be building crud applications. You'll be building real applications with admin backend and frontend with business logic. I'm not roasting what programming channels do though. I think they they are doing a wonderful job and they still help us in a way. But I feel like there're few tutorials online that are based on real world projects. I'd like to hear somebody's opinion on this.
I'm even thinking of starting my own youtube channel that will strictly be based on real world applications like e-commerce stores, Item ordering sites, classifieds sites, property listing sites etc
The React website has a few good examples listed, the University of Helsinki also released a pretty solid introduction to web development website.
However, with those two basic examples listed, that's exactly what they are: basic. They're very simple examples to get people started with React (there are a ton of equivalents for Vue as well) and React alone. I think the issue you may be facing here is that the scope of the projects you're looking to see is a bit out of scale for what a basic React or Vue tutorial would have. This could even just be a problem with the specific wording that you're using, as there are a ton of great full stack projects utilizing React or Vue that you can find online. Examples of that may include looking through resources like Awesome Open Source's full stack open source projects list or some projects like Free Code Camp's full stack blog may be up your alley if you're looking for something to take you through piece by piece.
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 1 year ago.
Improve this question
Low code is getting somehow much attention recently, and I am looking for hard, fact-based decision criteria for which platform to choose for which purpose or industry.
I found a flow chart at stackify compiled by Ben Putano in 2017 which is a step in the right direction:
The chart references only Appian, outsystems, kony, mendix, agile point, caspio, salesforce, PowerBI, but does not talk about platforms like. LabView, UiPath, Pega, Camunda, Blue Prism.
I would appreciate some theoretical, scientific input on the whole story of low-code and how to classify the different platforms.
We've built no-code platforms classification based on these 4 questions:
What are the skills your team is good at? (Sales, design, product management, programming, etc).
What is your app front-end? (Responsive web app, native mobile app, static website, API, chatbot, etc).
Type of app you want to build? (Dashboard, directory, marketplace, communication app, community, social network, CRM/ERP, etc).
Do you plan to accept payments? (Yes/No).
We use this classification in our no-code tools advisor service: https://www.nocodesetup.com
Based on its performance, we see that ~80% of people finish such survey to get a personalized recommendation about the right no-code tools to build their app.
To choose the right low-code/no-code platform, other questions might be very useful too. But the more questions you add, the more chances people will get stuck answering them.
Another great example of no-code platforms classification by Aron Korenblit (Head of education at airtable.com): http://read.aatt.io/issues/no-code-is-not-a-monolith-207566
Hope this will be useful.
It's much more complex than this, I believe.
There are so many platforms equally capable of getting you the results you need. A thorough evaluation is still needed. At the low-code company I work at, we felt this as a common pain point for lots of prospects - evaluating low-code vendors, which made us create this scorecard where you can assess ANY low-code/no-code vendor to find the best fit for your use case.
You can use the tool to find which platform is the right fit!
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
Are there any good documentation for backbone.js? I am trying to learn it, however reading the official page is not convenient for me because it is not structured well.
For example reading about Models has some explanation considering the Collections, which are described later. So if there is a well structured documentation which describe everything in a convenient for understanding order, please suggest it.
I can tell you what are the resources that I used to get a grasp of Backbone (I am a backend developer turned frontend for necessity on a personal project).
This website has nice examples, from basic to advanced, and was pretty easy for me to follow them. Also these videos are exceptional and proved to be useful for me. Needless to say I am not affiliated to the owners of these resources, I am only bringing my own experience.
Having said that, my current resources for Backbone, now that I "got" it (and delivered a non-trivial project based on it) are the official website and the source code. It is true that the website is non-linear but that will not be a problem when you have digested all its pieces (you will find yourself go there just for a reference). Another story are the little caveats and details that are not written anywhere (official or unofficial docs). For that you need the source code that is well documented. Backbone, at least for me, had a steep learning curve. All the concepts are known if you did development before, but getting them right with Backbone and JS has been another story. The single most important resource to learn it has been starting to play with it! Seriously, you start with a small UI and try to play with events and collections (I used Chrome dev tools directly, no need to set up a real project). Then you grow organically from there.
But I agree that you kinda have to go and look for informations on multiple places...
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 8 years ago.
Improve this question
We are a team of developers that have been doing web application programming for a few years. We are now starting over with a new project and we are aiming at making it a single page application. For the front end we are using angular. We are relatively familiar with angular, we know how to create services, directives, controllers ect. We know how to use built in services like $http and $resource and how to user routes (or states with ui-router) but we are stuck at a pretty early state on how to structure the application.
We are having a hard time finding good resources (blogs, videos, books) that tackle this general issue. Many posts have a very simple approach like:
"To build a SPA you need to use $http, this is how you do it, easy isn't it?"
They can be very good to understand the basics of each component but they do not explain hos to couple it all together. Questions we have are of the following type:
Do we build a central js object to represent the application state? If the application would be a back end for a web shop then the central object would probably be a company which has a list of products, each having a list of orders and each of them has a reference to the customer. Or do we split the representation of the application state in different objects? If so, how do we keep them in sync?
To display a form which edits an entity we create a route that loads a partial into a view and we populate the scope with the entity to edit. Do we fetch the entity from the back end? Or if we already have it in our js model, do we simply fetch it from there so that we don't need to make an http request?
There is a lot more that is unclear and I realize that there will not be a simple answer to any question, rather it is likely to be different design patterns with pros and cons. I do not expect the answers to all my questions as a response to this post, but rather I'd like to find some resource (like I said blog, video, book) that discuss these issues on an application-wide level. Some questions are angular-specific and some are more general around single page applications. Are there such resources?
I am relatively new to AngularJS myself, and I agree it is hard to find info that goes beyond the basics. So far, the most useful tutorials I have found are from Dan Wahlin.
http://weblogs.asp.net/dwahlin/archive/2013/04/12/video-tutorial-angularjs-fundamentals-in-60-ish-minutes.aspx
http://weblogs.asp.net/dwahlin/archive/2013/05/22/dynamically-loading-controllers-and-views-with-angularjs-and-requirejs.aspx
http://blogs.interfacett.com/getting-started-with-angularjs-video-series
The 60-ish minute tutorial was excellent, and his other stuff is good for getting you past the Hello World stage. I've also watch a couple presentations from Misko Hevery, the creator of Angular, and he is very good too.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
Improve this question
Goal: I want to create a website for my High School's Soccer team to show game info, player info, and historical stats/records for as little $ as possible.
I originally planned on writing an ASP.NET site, so I spent some time setting up and loading all the data into MS SQL. However, I've realized I'd rather find a simpler solution than me trying to come up with everything that goes with creating/maintaining the site.
The biggest factor here is tying the database to the site. I want to continue to update the data going forward without messing with the front end too much. I've developed in ASP.NET/C#/VB.NET and am comfortable with CSS/web dev/blogging, so I'm able to do a little dirty work if need be.
Question: Is there a good CMS option for my situation? Also, where to host it on the cheap?
I was a CMS developer for 5 years. Having been through all that, I wouldn't write my own for a single, relatively simple site.
There's SO many options out there. Obviously, the standard Joomla/Wordpress/Drupal solutions are there and are SO cost effective to build. Free software + $5 a month hosting (my personal fav is HostGator) and you've got yourself a very good site. Joomla offers some plugins such as calendars, groups and authorization, etc that makes it ideal for a club or sports team setting. Joomla even has free plugins that are specifically made for tracking sports stats and results. I did sports stats on websites professionally for the US Swimming and Cycling teams as well as two NCAA conferences.....and they aren't fun to deal with at all!
That being said, none of those are .net based!
DotNetNuke is where everyone on the .net side seems to turn. This is my personal feeling, but DotNetNuke and Wordpress both fail in that they are somewhat strict with layouts unless you really know what you're doing. For example, look at a bunch of sites and chances are you'll be able to tell which ones are Wordpress based. That was always my top measure of flexibility.
I'm intrigued right now by Concrete5 because of its ability to content manage any layout with minimal modification. Again, it's PHP based. My personal feeling is that you'd actually come out ahead "switching sides" because of the considerable amount of work product and community that the big free CMS packages offer. Setup is a breeze, so knowledge is less of an issue. But ultimately your comfort zone is what matters.
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 4 years ago.
Improve this question
I'm evaluating DotNetNuke for a project in which an offshore team is going to be doing the development. In short, the application will be a community blogging platform with many similarities to stackoverflow except no questions, just posts. Posts may include an image or video, tags, use info, title, body, community vote (up or down) comments, hotness, and a few other details. They should be taggable, sortable, categorizeable (beyond what a single set of tags provide) In the future the site will carry forums, a calendar, and a couple of other features for which there are modules available for DotNetNuke. Additionally, this site will incorporate a user experience that will include a lot of custom skinning.
Thoughts?
Using a web application framework (such as DotNetNuke) has a ton of benefits to help you get up and running faster and do less work when creating custom functionality.
However, you have to realize that you're basically incorporating tons of code into your project that you may not be familiar with. No matter how good the code is and how easy the framework is to learn, there's still going to be a significant learning curve for you and your team.
Your decision making process (if you're still deciding whether or not to use DotNetNuke), should include (in addition to reading, talking and other general investigation):
Downloading the application from Codeplex and checking out the source.
Investigating the third party modules that are out there.
Downloading a free module or two that comes with source, and try to reverse engineer the creator's development process. How did she integrate with the framework, what features did she take advantage of, what was written from scratch?
One place where DotNetNuke (or any other framework with tons of extensions) available can really shine is taking existing extensions that are available and customize them. If you need to implement a given feature, check out the solutions in the third party extension community first. You can probably find one that gets you a good percentage of the way there and use it as a foundation for your feature.
For example, if you want a photo gallery on your site, you probably don't want to write it from scratch. There are three major photo galleries out there that sell the source code. The core gallery module is free, simple gallery is cheap, and the source for ultra media gallery is available for a reasonable amount compared to writing it yourself. Any of these could give you a good head start in implementing your features.