XML-based background management system-Concept

The front-end page of the website is ever-changing, and it is difficult to meet the requirements with a uniform style. However, the website background generally involves adding, deleting, modifying, and querying data, and there are not many page changes. Therefore, we can build a unified website background management system.

Website background users can be divided into two types: 1: business users (only need to see the business module you need to process .). 2: System backend customizer (different management interfaces are assigned to different user roles .). Business users are generally our customers, while backend customizers are generally ourProgramMember.

Our background management system includes the following modules:

Menu Module

• The background system contains multiple menus.
• Each menu contains one or more links
• Different roles have different visible menus.
• Add, delete, modify, and query

Link Module

• A link corresponds to a background page
• Link included in the menu
• Whether or not each link displays controllable roles
• A link can correspond to only one menu.
• Add, delete, modify, and query

Role Module

• The background can contain multiple roles
• A role can contain multiple users.
• Each role has its own function menu.
• Each role can customize a shortcut menu that contains common links of the role.
• Add, delete, modify, and query

User Module

• There can be multiple users in the background
• One user can correspond to only one role.
• Users can modify their own information and passwords.
• You can select the background Style
• Users can add, delete, modify, and query

User (LOGIN) Log Module

• Record the information of the user logging on to the background.
• Read-only.

The number of users in the background system is usually not large. There is no large amount of information in the background menu, link, and role data, so we can use XML for storage. For security, you can encrypt XML files and prevent downloading. The biggest advantage of storing such information in XML format is that it can be used in all types of databases that the system uses.

Below are some common things in the background

1. Create a unified master page on the background page, reference the unified CSS style, and reference the unified JS library. Write logon verification in the. CS file on the master page.
2. Information List page (in the form of information list)
3. Information add page
4. Information Modification page
5. Information view page
6. Information prompt page
7. In the pop-up window, alert and confirm are rewritten.
8. Image Upload page
9. File upload page
10. Paging Control
11. It is encapsulated by JS operations, such as selecting all, canceling selection, and deleting confirmation.
12. Text Editor
13. ....

Integrate these into a web project template. Add the project template directly when the website is created, and the background framework is set up.

The background system should also have a permission module. Because the permission module is too invasive to the system, the background management system does not consider this. Generally, small projects can meet the requirements of page Link-based authentication. If you need to set permissions, you can develop them based on the specific application.

The 163 mailbox-like interface for the background Interface

 

 

 

Currently, this project is under development in my spare time. After the preliminary framework is built, it will be available for download and use in open source. You are welcome to make some improvements to this idea.