Blog System Structure

A lot of popular blogs have been published in the past few years, and even more popular blogs are getting better, so there is only one word left-fire! Some people want to engage in blogs.ProgramWe need to follow up and develop various blog systems, such as WordPress and zblog. The interface is similar, just a few basic things. Today's articleArticleLet's summarize the structure of the blog system.

Let's talk about the characteristics of the blog system:
1. Web-based user interface
2. Organize blog records by category
3. Customizable Page Templates
4. Comments, response links, and references
5. Provide web service interfaces for related software
6. Support for uploading multimedia files

Basically, all blog systems have the above features, and then expand them based on these features.

The following describes the most important data model.
The data model defines the object types stored in the system and their relationships. The following lists the object models of the basic blog system.
User (users) : A blog system can have multiple users. Each user may have multiple blogs or no blogs.
Blog (blogs) : One server can have multiple blogs or only one blog. Each user may have 0 ~ N blogs, but one blog has at least one user.
Blog record) : The most important part of a blog, written by one or more authors.
Category) : Each blog has a set of categories, and each blog record can specify a category. Blog records can belong to multiple or one category. The classification can be a tree type (that is, a classification system with a parent subset ).
Template) : The appearance of a blog is composed of a set of templates. The template language is used to display the blog page.
Resource) For example, compressed packages, images, and videos can be used in blog records or blogs.
Preference (settings) : Each blog has a set of Parameter options for personalized blog settings.

After the above expression, basically all the things required by a blog are available. If you want other systems, you need to look at the developer's personal preferences, such as links.

Next we will discuss in detail the most importantBlog records.
ID : Unique identifier of a blog record
Permalink) : Fixed URL for search and user access.
Title) : Blog record questions.
Content) : Needless to say, text.
Summary) : A Brief Description of the blog record content.
Link) : If the blog record is forwarded, this attribute records the original URL.
Status) : Status of a blog, such as draft, reviewed, or published.
Published) : The posting time of the blog record.
Update Time (updated) : The Last Update Time of the blog record.
Author (authors) : The person who created the blog record.
Parameter (config) : A blog may record game parameters, such as the blog language, whether the comment can be made, and the plug-ins required for blog record.

the blog record is basically like this. Next, we will describe the data related to the blog record.
category (ctegory) : A blog record may belong to one or more categories. This can be done as needed during the specific design.
attachments) : multimedia files uploaded by users when posting blog records. For example, compressed packages, images, and videos.
comments) : interaction between a visitor and a publisher of a blog record, mainly through comments.
trackbacks) : other blogs may write something on their own blogs, and some text in it will respond to your blog record, then he will send you a response link. The reverse link protocol was designed by the author of MovableType to notify another blog server that its blog record references the blog records from this server. This notification is a reverse link, including question, abstract, URL, and blog name.
reference (referrers) : if other websites respond to your blog by linking to your blog record, your blog server can capture these referenced URLs from Web requests or web server logs. Through it, you can know which websites mentioned or linked to your blog records.

Finally, let's briefly talk about users, permissions, and blog groups.
Reader): Read one or more blogs. Most blog systems are set to anyone.
Commenter): Add comments to one or more blogs. Most blogs allow comments by anyone, and some allow comments by people with relevant permissions.
Editor): You can create, edit, and publish blog records on one or more blogs.
Author (author):The author is allowed to create a blog record on one or more blogs, but cannot publish it. You may have the permission to set the blog record category.
Admin): You can manage blog categories, page templates, bookmarks, and affiliated resources.

This is probably the way the blog system looks. The specific implementation is based on the developer's design and development capabilities.

Finally, someone may ask why such an article is of any significance? I think if we are familiar with the current Internet application architecture, we will be able to easily design any Internet application in our daily work.

Originating in http://www.sourcejoy.com/other_dev_tech/blog_system_struct.html