Kooboo CMS Introduction

Kooboo positioning is a CMS, Content management platform, from a more strict sense, it should be the site of rapid development platform. In view of the general Web site development process analysis and refinement, focusing on the general needs of the site to solve, put forward a set of rapid development of the concept and method of the site. Under the guidance of these concepts and methods, to carry out the development of the website, standardize the development process, improve the development efficiency, reduce maintenance costs, improve the quality of the site.

We are developing a Web site and will generally face the following issues:

Content storage, which is a fundamental issue. Content is the whole site of the body, but also the soul, lost content, the site can not body its value. Website development of the most important work is the content of the processing, that is, the content of the increase, delete, change, check the processing. Or, more directly, the developer's operations on the database. And how to content data, directly affect the development efficiency. Developers inevitably have to deal with a large number of SQL statements, or use tools and frameworks like ORM to improve development efficiency. However, developers need to face a lot of development and configuration work anyway. The first problem that kooboo to solve is to get developers out of repetitive, heavy work to achieve a generalized storage that developers don't even need to care whether the data is stored in a database or in a local file. content Storage, developers should design the corresponding data structure (Schema, content type) according to the field they need, and set up the corresponding content directory (folder), can use the corresponding interface to manipulate the content, and do not need to care about SQL or other storage details, At the same time, the content relationship is not a simple one-dimensional relationship, can deal with 1 pairs of many, many-to-many relationship. And, through the background of Kooboo can directly maintain these content, do not need to re-develop a separate background to maintain site content, reduce development tasks.

Multi-site processing, content sharing issues. In reality, we may face the fact that organizations in an organizational relationship need to have content-sharing, but structurally separate sites. When we encounter this kind of problem, our usual way is to develop the website for each agency, to realize the purpose through certain technical means, or share the database, or share the directory when we encounter the data that need to be shared. Another typical scenario is that when we are developing a global website, it is impossible to avoid the problems of language and culture in each region. Language alone, we can solve through the resource files, but when the site in addition to the language to be different, a part of the site content to be based on the region's cultural characteristics of some changes, how to achieve reuse and customization through the smallest changes? Content also needs to be localized according to different regions, this is not simply through the resource text can be solved. In the same way, you can expand on these ideas to develop a series of reusable functions that are similar to the same kind of corporate web sites. In Kooboo, every website is just part of this platform. This platform can have a lot of sites that have a direct relationship, or no relationship at all. All websites can have their own independent domain name. Between sites, there can be direct or indirect inheritance relationships. The various elements of the site can be shared and reused between inherited sites. The child station can fully inherit all the code and content of the parent site, and can also make some specific changes to the elements of the parent site as needed to achieve the maximum reuse through minimal changes, and it is not a simple physical copy , that is, if any changes occur to the parent site, It is also reflected in the inherited Web site. This is the inheritance of the site, inheritance can not only inherit content, but also inherit code and templates, can support localization, that is, to meet the three basic characteristics of object-oriented.

Template management. For a website, the most intuitive experience for users is the UI of the website. For dynamic pages, the design interface is the design template. In Kooboo, using the traditional WebForm. aspx page as a template continues the development experience of the ASP. At the same time, it provides perfect skin management, script management, resource management, and provides a powerful online grammar compiler that frees programmers from complex path-style references and grammatical memories. templates can be divided into layout templates and content templates, which are templates that control the layout of the entire page, and the concept is equivalent to masterpage; a content template is a template for a piece of content in a page, and it is concerned with the presentation of a part of the page .

Page management. Unlike the page concept of ASP. WebForm, in Kooboo, "page" is not a physical existence. aspx page template. A page is simply a combination of templates and data, with some configuration values for URL performance. These configuration information determines which page templates are placed on the page, where the template is selected, what parameters the page needs to pass, and how those parameters are passed (normal or SEO friendly); Determines where the page is to query for what you want (datarule) ; The person who determines which roles can access the page. At the same time page management, can also be used to generate the foreground page navigation menu.

The extension plug-in. A perfect development platform, inevitably to provide the ability to solve some special situations, but also for some common functions, such as forums, blogs, wikis and other functions of the entire module reuse, in order to provide resource reuse sharing. In Kooboo, there are two types of plugins: the page plugin and the module plugin. The page plugin (pageplugin), which is a controller extension that runs on a general controller, is developed for specific requirements of a particular page: a site front page, possibly 80% pages for display, and a part that may require the submission of data , the submitted data can be processed in the view through the traditional WebForm postback, but also by writing a page plug-in to separate out, from the MVC component, write page plug-in is more consistent with the framework requirements; Another possibility is that some of the data required by the page is not stored in Kooboo, but rather needs to be obtained from other sources through other channels (example WebService), and you need to write a plugin to achieve your goal. Module plug-in is a complete feature package developed for the full functionality of an application, which may be a simple blogging system, a forum, or other small functionality that can be reused, which can be added to any location on the page template (as used with normal content templates). In Kooboo, each module plug-in can be used as a standalone website, not necessarily run on the Kooboo platform, you can think of it as a mini site, if you understand the ASP. NET MVC2, you can understand it as an area-like feature. Develop a module plug-in, that is, to develop a common MVC site that you can develop and debug independently.

Site packages. Once a website is developed, it may need to be ported from the development platform to the production environment platform. At this point, you can export the designed site and then, on another Kooboo platform, select the import operation. Soon, you will find that the site package can also have another application. If you design a site template, and then based on this template to quickly generate a number of similar sites, which is the way many sites quickly generate software practices. That is, a site design, not only can be inherited reuse, but also can be exported to reuse, to achieve maximum reuse.

These are the core features of Kooboo, but when you dive into Kooboo, you'll find more useful features, including:

Built-in full-text search, using lucene.net, automatically updates full-text index files while maintaining content, and enables fast full-text search functionality with a simple API.

Simple workflow management, built-in a simple workflow function, convenient for content maintenance to implement process review process.

Automatic merging and compression of scripts and style files, by setting up a simple switch to configure the site to run in debug mode or Release mode. When running on release, compressed script files and style files are automatically merged.

Error management, the site in the event of a mistake, you can configure the page to go to according to the error category.

These features are the core issues that Kooboo to address, and I'll use Kooboo 1.2 in a later series to expand the details of each feature point in depth. Kooboo 1.2 will be released in a later two weeks, please look forward to it.

Official site: http://www.kooboo.com/

CodePlex site: http://kooboo.codeplex.com/

Live Demo:http://www.kooboo.com/demo

Official Forum: http://forum.kooboo.com/

Kooboo wiki:http://wiki.kooboo.com

Kooboo CMS Introduction