Develop large and medium-sized applications based on Typecho CMS framework

Develop large and medium-sized applications based on the Typecho CMS framework

Large and medium-sized applications are temporarily defined as: applications with more than or equal to 3 data tables! Sweat it!

Typecho was originally a blog system. Its framework system is different from the general MVC framework on the market. The main code uses the self-created Widget as the base class, and the whole is very simple.

The basic features of Typecho are as follows:

1. Single entrance
   
2. Except for Db configuration, other configurations are stored in DB
   
3. Routing configuration is also stored in DB
   
4. Self-created Widget layer, no traditional Model layer
   
5. Create your own Action layer, similar to the traditional Controller layer
   
6. Hook mechanism
   
7. Pan-Plugin mechanism. Plugin includes methods to register existing Hook Handlers, extend existing Widgets, and register new front-end Routes to map new Actions. Register backend management interface
   
8. Support UI themes

Why should we develop applications based on Typecho

I am not an official developer of Typecho, nor do I work in the related background unit segmentfault. Company, why should I use this niche framework?

In fact, you really don’t need to use Typecho. There are too many frameworks in the PHP world, and you can choose a more advanced framework.

I don’t know when I started to realize that I am a “niche” patient and don’t like to follow the ordinary path. Just like Linux may be niche enough in the desktop field, but I like to use FreeBSD, which is even more niche.

This is just my attempt.

Practice

Principle: Based on the MVC model, add a Service layer.

1. C layer

As we said before, Typecho created its own Action concept, which is the basis of our C layer, but Action has no clear definition. So I will define a Controller base class.

1. M layer

There is no concept of Model in Typecho, all SQL queries are called directly. So the Model base class must also be defined.

1. V layer

View file is the content carrier of View. In order to reduce the learning cost, the template engine is no longer introduced, that is, the PHP syntax is directly used and directly imported into C for execution.

1. Service layer

In complex applications, the biggest problem of MVC is that the reusable code is not refined enough. Some people have the C layer too fat, and some people have the M layer too fat. The introduction of the Service business layer helps to refine and encapsulate the business layer and maximize the reuse of code.

Demo project: Typecho Alumni plug-in project

Code address: https://github.com/web3d/plugins/tree/master/Alumni

Project code structure:

/plugins/Alumni/Base/ Action.php|Model.php|Service.php|Helper.php
/plugins/Alumni/Model/
/plugins/Alumni/Service/
/plugins/Alumni/Action/
/plugins/Alumni/views/default/

/plugins/Alumni/Plugin.php
/plugins/Alumni/panel.php

==========
To be continued...

The above introduces the development of large and medium-sized applications based on the Typecho CMS framework, including PHP syntax and github content. I hope it will be helpful to friends who are interested in PHP tutorials.