How To Write An Engine For A Website

Table of contents:

How To Write An Engine For A Website
How To Write An Engine For A Website

Video: How To Write An Engine For A Website

Video: How To Write An Engine For A Website
Video: Making my web game engine 2024, May
Anonim

The days of static sites, as well as sites that only partially provide dynamic content, are irrevocably gone. Server capacities allow using CMS to build even small Internet resources. Today, there are many free CMS available with functionality for every taste. Many of them are developed by teams of professionals and have proven themselves very well. However, even today many enthusiasts strive to write an engine for a website from scratch.

How to write an engine for a website
How to write an engine for a website

It is necessary

  • - access to the Internet;
  • - modern browser.

Instructions

Step 1

Plan the functionality of the engine. Answer general questions about the purpose and type of product being developed. Decide if it will be a universal CMS, or something more focused (blog, e-commerce platform, community site, news portal). Answer specific questions about the capabilities required. Consider whether your site needs an image gallery, forum, news feed, file archive, etc. Should such functionality be tightly integrated into the kernel, or can it be presented in the form of extension modules.

Step 2

Think over the architecture of the engine. Typically, the architecture of modern CMS follows the MVC paradigm. At this stage, it makes sense to study the already existing solutions, of which there are a very large number.

Step 3

Determine the technologies on the basis of which the main functionality of the product will be implemented. Select a programming language. PHP is now the de facto standard for CMS development. Although you can consider using ASP. NET, Java, Python. Choose storage technologies. Typically, modern CMSs use databases as their main storage location. But in some cases, you can rely on the file system. Highlight other technologies that will be required to run the engine (graphics processing libraries, spell checkers, cryptographic modules, etc.).

Step 4

Review the documentation for the products and technologies on which the project will be built. Determine the appropriateness of each product or technology. If necessary, make adjustments to the list of technologies, find acceptable alternatives.

Step 5

Make a plan or terms of reference for the development. Even if it is not planned to involve anyone other than the project initiator in the development, following a clear plan or points of the terms of reference will save a lot of time and make the work much more efficient. When starting a project, it makes sense to draw up a task for the development of the core (and, possibly, test modules) of a CMS with minimal functionality.

Step 6

Implement part of the project in accordance with the previously developed terms of reference.

Step 7

Test the functionality implemented in the previous step. Identify errors. Make a list of bugs and tasks for revision. Assign bugs to fix priority metrics. Sort errors according to their priority.

Step 8

Correct any errors found. Perhaps, at this stage, other problems in the operation of the system will be identified. Complete the list of errors, correct each of them.

Step 9

Determine the need for further revision or modification of the site engine. Answer the question about the conformity of the existing functionality to the previously planned one, about the satisfaction of the system operation parameters with the presented quality criteria. If further development is required, skip to step 5 for the next iteration of product development.

Recommended: