A dynamic web application tends to have many sorts of routine code which are essentially common in most dynamic web applications.
By the routing for a web application we mean mapping URLs (requests) to actions (responses) of the application. In this paper, we show that by configuring the routing for a web application together with preparing static libraries and modifying dynamic templates to generate the modules which are needed by the application, we can generate most of the routine code necessary for the application. Configurations for the routing and other settings for an application are written uniformly in JSON format. Then, reading the JSON configurations our scripts set up static libraries and generate necessary modules from templates and write files which conduct the routing.
Our system sets up everything you need to run a web application from the web directories for the application and the basic libraries to the modules for the application and the files for routing. You can add another web application to the web setting for the web application you have generated.
To show by example the applicability of our web code generating system we first construct a book request page with a very little configuration on the application. Next as a more complicated example, we apply our system to a web application which involves a specific function i.e. reading a marksheet for which the system cannot generate code, showing how the system can generate a web application which utilizes the code not generated by the system.

Document repository systems have been developed actively for decades and have become quite popular on the internet. Now we can recognize several typical types of document repositories and find the full-text-search functionality as a useful search method for document repositories, so we think it has some significance to show as a mile stone an implementation scheme which covers basic types and functionality of the current document repositories which have full-text-search functionality.
The basic functions covered by our scheme are: to create, read, update, delete (so called CRUD) of documents and a session control with an optional authentication. We present a description for each part of CRUD of our scheme.
We implemented a library according to our scheme and developed small document repositories using the library. Our repository library and its applications form web applications whose script language is Perl. The implementation loosely follows the MVC (Model, View, Control) model for modularity and each MVC part of the library and its application named TEST are described. We also present a description of another application of our library which the author is conducting in the department he belongs to. We show some views of these applications.
We conclude that our library works fine for the needs of building small repositories in a short time.

Thanks to the open technologies around the world wide web, the authors as just college teachers have been able to develop a compact and practical online quiz system we call QDB to satisfy needs in their classes. In this paper, first we introduce our system to give ideas what the system can do. Then we show the effectiveness of the system by describing the effects of practical uses of the system in our classes for years including the effect of the recently added retry-functionality. Then as an example of the feasibility of our development we explain how simple to implement the retry-functionality because of the compactness of the system and again the great power the open technologies give us and show the speed of the system. As conclusion we suggest possibilities of a compact and flexible system as a form (or a part) of e-learning systems made to your order.