coServ

Why coServ

Web applications are getting complicated day by day. Without a proper platofrm, web app developement could be a very time consuming task. So choosing the "right" plaftorm may be the #1 issue before you even start any coding efforts. If you're not satisfied with the existing platforms, maybe you're looking for a web platform like coServ.

coServ intends to minimize any programming overhead by reducing repetition, removing extra rounds of code generation or compilation, and shortening the development pipeline. Every development construct is intutive and requires skills no more than HTML, CSS or Javascript.

coServ offers the following features that could be good for developer's health:

* The practice of HTML coding is transformed to node.js coding. Developers use modules, libraries or functions to render HTML codes.

* Web pages are divided into smaller HTML fragments generated by special node.js modules call palets.

* Palets are less complicated and easier to be implemented than a whole page. Also, palets can be reused.

* Because of palets, HTML refactoring is possible and actually encouraged.

* CSS encapsulation is automatic. Any css decorations inside a palet is not visisble to other palets or pages.

* The model, view and control of a palet are coded in the same node.js module (program).

* Regardless it's backend or front-end, use one single language (Javascript) to do both.

Get started

To install

npm install coserv

Once you've installed coServ, there are several articles to help you start writing interesting web apps. Becasue coServ organizes the web developing tasks in a unique while effective way (which could be unheard of for the first time users), it would be helpful to scan through the following articles to get some interesting insights:

* Tips for jump start programming on coServ

* A short article explaining how to transform the programming space from HTML to JS.

* Another short article to explain how coServ can help to apply the separation of concerns principle.

* A three parts tutorial using a TODO list web app as an example.

1. Part I: Using a command line tool to quickly create web apps.

2. Part II: Adding the controller and re-using palets

3. Part III: How MVC is implemented in coServ

Differences between the current and earlier releases

For those who have been the users of the ealier versions of coServ, you'll notice that this official release (v1.0) is not compatible with the older versions. However, the core concepts and principles of how a web app is constructed and organized remain the same.

Below are highlights of the major differences:

* HTML code generation was done by template literals, while now it's done by node.js modules.

* coServ divides up a web page to smaller fragments. Earlier versions call those HTML fragments as "blocks" while the official release calls it "palet".

* A "block" can be composed of up to four files (HTML, CSS, Javascript and a language resource file), while a palet is defined by a single node.js program (module).

* A new application construct UIC (UI Components) is introduced to further facilitate HTML componentization and refactoring.

* The file structure of a web application remains relatively the same. There are just some minor directory name changes.