Manage a Website – Design

Design
Design

This is the second element about websites. In this article, we’ll describe some bases of designing websites. I could say when I’m having hard times in a website to get what I’m looking for. Do you remember the rule of 3 clicks? So, we’ll talk about design thinking, display resolutions, UI and UX and other cool subjects. I’ll not cover Photoshop courses or discuss about color theory.

Read moreManage a Website – Design

Manage a Website – Planning

Planning
Planning

Planning is fundamental in any project. Before starting to write <html> or click on menu Project, New Web Project, we need to set up the bases of our Website project. Some elements are important, and need to be defined in order to have a well-planned project: main goals and requirements, allocated resources, team members, stakeholders, schedule and milestones. Doing a PESTLE analysis remains an excellent tool if we want a successful website.

As I listened once in a video of Jeffrey Snover where he talks about career transition, he invite us to remain focused on driving business forward. In these thoughts, but now talking about websites, our website must focus on the core activity of our organization or the company of your clients.

Read moreManage a Website – Planning

Manage a Website

This is the first of a series of articles where we’ll talk about websites and their environment. Through these articles, we’ll going highlighting some important topics to consider, when building a new website is in first place on our projects list. But nevertheless, you can implement each of these areas to your project at any stage that is.

One of my goals here, is bring to you see the big picture. I’ll not concentrate these lines to a specific industry or job position, because is commonly associate the word website with developers, marketing or media. So, in future articles we’ll go deeper extracting interesting subjects and learning new fields to clarify the role of the website.

Read moreManage a Website

Count in Aggregation

The $sum accumulator operator adds recursively a specific numeric value to a variable in the process loop. This operator will work only in the $group stage.

To do the SQL version of COUNT() function, we need to construct a $group stage where a field count or your favorite name you want to use, and add 1 to the $sum operator. The following code will produce two elements and one document: _id will have a null value and count containing the total of documents processed.

It can be implemented once your main pipeline is executed.

 
{
	$group : {
		_id : null
		,count: { $sum: 1 }
	}
}
 

Always remove the $limit stage operator if you want to see the real count. This operator give to the pipeline the limit or a specific quantity of documents.

This is a parallel article of Aggregate function and Count.

Related Links

http://docs.mongodb.org/v3.0/reference/operator/aggregation/sum/#grp._S_sum

Representational State Transfer (REST) at Front-End (AngularJS) and Back-End

When I started the myLibrary project, I invest some of my time to try and analyze a few choices out there on Internet to put on the Front-End and Back-End. Then AngularJS, an excellent choice as Front-End and ExpressJS working as Back-End.

But down the road, I found that either AngularJS and ExpressJS offer REST functionality. So, which one to use to talk to MongoDB? I could have used only AngularJS with its $http service to get data from the database, but I have decided to maintain independent the Front-End of Back-End. Development and experience aspects!

Read moreRepresentational State Transfer (REST) at Front-End (AngularJS) and Back-End

Consuming data with AngularJS

We often want to display data coming from sources like our databases, but also we can do it sending requests to web services that are out of range of our network to get that data. In our example, we’ll use data stored in Google’s servers using the Book API that returns data in JSON format.

Here’s the final result:

angularjs_consuming_data_fr

Read moreConsuming data with AngularJS

Mongoose Schemas

To be able to execute CRUD operations to interact with our database, we have to model our data. By this, we’ll create schemas that will be used to send data. In our example, we’ll create a document posting document details coming from Client and go to Server where the POST method will receive data and will grave it into the database, through our schema.

Read moreMongoose Schemas