task-1, task-2, task-3, task-4, … Everyone who working in front end web page development will have some trivals repeating and repeating. Imagine that you are creating a web page from scratch, you need to design the all the pages arrage the relationships between different pages and other websides. Then you need to implement every single pages. You should figure out the common part and reusable part and put them together, and use some client-side or server-side mothods to merge all different part together and represent a perfectly metched web page to your audience. If you achieve the goal via a client side method such as frameset of iframe tag in web page, then you can hardly prevent user directly visit a fragment of a layer of your final site. In some other scrnarios, some one directly use the same method as you do to put your site fragment into their web pages. Isn’t it annoying?

<script src=”/script/Script.js”></script> ? require(“Script”); ? For most of the websites that you visit everyday, the JavaScript is not only a additional way to promote user experience but also a required method to let the site works as expectation. Nowadays, in such a so called “web 2.0” era, what is loaded and rendered by a browser is not a traditional document-like web-page but a modern program-like web-application. And since the HTML5 and CSS3 ( as well as other “live standands” ) became widely used in most websites form top of Alexa ranking to those personal blog (like this), it’s rare to meet a pure static site(in terms of client end). The scorces drive all of world of web is in JavaScript, our hero. However, just as the name, “JavaScript”, indicates that it’s initial goal is only provide some simple way for website to use, JavaScript is not designed for large scale application. The conflict between the autologous fault of the language nature and the raising demand of a suitable language led to various solutions. Here in this post, I would like to talk about some things about RequireJS, a JavaScript file and module loader who modulize JavaScript code snippits and load them asynchoronously in the standand browswer environment.

Nowadays, the OAuth 2.0 is the most popular stander for authorization and also widely used in the third-party authentication process. Beside, there are lots of other protocols uesd for that purpose. Here in this post, the focus is on the CAS -- Central Authentication Service. (Wiki:CAS) as well as the same named implementation.

Dive deeper into Jekyll This is the third post of the Building the Blog series which will cover some more configurations to Jekyll.