Build a system
Cliqon has been designed and is used to create two different types of web server based software systems. Cliqon can be used to build presentational websites where there is little or no need to augment the facilities in the Administration system as all the things that are required for just a web site are already present in the standard Cliqon system. Cliqon can also be used as a base to build an application which requires both a web site and also a significant amount of addition to the Administration system. Thus we have used the various versions of Cliqon over the years to create a business directory, classified adverts system, an auction house system and system to present golf courses.
Therefore we provide two subsections of documentation. The first we call "build a website". This documents the process that you, the Developer, would adopt, in our opinion, to design and build a presentational website with Cliqon. Our explanation is based upon our own activities in building the new Cliqon.Com website. A reduced version of which is provided as one of the demonstration systems that you can download from the Cliqon website.
The section section, we call "build an application". This documents the process that we took to convert our existing business directory which currently runs on Cliqon Version 3 to this version, Version 4.
To maintain the flow and focus of the documentation, interesting and important elements of the build process that do not naturally fit into the flow are documented in the Cook Book.
Back-end and front-end
We understand but do not necessarily subscribe to the idea of programmers who work on the "back-end" programming of a website and web-designers who work on the "front-end" of a website.
"Front End" typically refers to the stuff that you actually see on the website in the browser (and is often called "client-side"). This covers how the content is presented including all the little user interface elements like menus and dropdowns and transitions and modals. The front end needs to be able to communicate with the user and also with the back end.
"Back End" typically refers to the guts of the application which live on the server (and is often called "server-side"). The back end is more focused on making sure all the right data gets sent out to the browser. It's the portion of iceberg below the surface... lots of stuff needs to go correctly to hand off data to the front end so it can be displayed.
Google may be a relatively straightforward search engine from our point of view, but they employ an army of engineers to make sure that all the moving parts you don't see are working properly.
"Full Stack" developers marry the two sides into one. While each "end" involves learning a significant amount of information, a full stack developer can comfortably speak both database and browser. These days the trend is to seek developers with a great working knowledge of both ends. You will still probably prefer one over the other, but a "Full Stack" developer can build a web application from soup to nuts.
In this program, we teach full stack development for many reasons. For starters, it's much easier to get a job when you've got the kind of flexibility that being Full Stack provides. It also makes it much more fun to learn because you can bring complete applications to life completely on your own.
Created with the Personal Edition of HelpNDoc: Free CHM Help documentation generator