What is the approximate production process for one person to create a website alone? ?-PHP Tutorial-php.cn

For example, now we want to make a corporate website.

What is the production process? ?

Let me tell you my opinion first (wamp environment):

Determine needs
Specify relevant development documents according to requirements (including: what functions the backend needs, the design of database tables, etc.)
Design the database according to the development documents.
According to the development documents, design php
Use ps, etc. to create the front page (according to the background function)
Write the front code according to the page
Use ajax to set data

I wonder if there are any errors? ? Please share the more common production process. I hope it can be more detailed...

Reply content:

For example, now we want to make a corporate website.

What is the production process? ?

Let me tell you my opinion first (wamp environment):

Determine needs
Specify relevant development documents according to requirements (including: what functions the backend needs, the design of database tables, etc.)
Design the database according to the development documents.
According to the development documents, design php
Use ps, etc. to create the front page (according to the background function)
Write the front code according to the page
Use ajax to set data

I wonder if there are any errors? ? Please share the more common production process. I hope it can be more detailed...

Let me simply tell you my opinion:

First find a web page template (the more popular bootstrap) that can meet your needs as much as possible. In this way, you can make your website look high-end with very little effort :)
Evaluate how many functional points the entire website has, and try to abstract the common functions (this may not be able to find all the common functions at once, but it is better than not doing it)
Evaluate whether the interactivity requirements of the website are high. If the interactivity requirements are high, consider separating the front-end and back-end. The front-end is implemented using some popular MVVM frameworks, and the front-end and back-end use json for interaction
If the interactivity requirements are not high, see if the PHP framework you are using provides a template function. Using templates will also improve the efficiency of development
Design the database table structure according to the function points. Here we consider using ORM on the back end to operate the database to facilitate future maintenance
Tool function point design URL, each URL is actually a function point
Develop front-end and back-end. If the front-end and back-end are separated, whichever one is developed first will do.
Front-end and back-end unit testing
Page testing
Consider deployment methods

There are many ways to build a corporate website, I will list them from simple to complex.

1. Made using cms program. Content management systems like Empire/Dreamweaver/phpcms, etc., or e-commerce system programs like ecshop, all you need to do is find a set of templates (you can also design them yourself), then write the front-end template, and simply set up the backend Just create a column, create a channel, set permissions, etc., and you're done. The process will be quick.

2. Utilize frameworks. Like CI (codeIgniter), tp (thinkphp), laveral, etc., you must first design the database table, and then according to the framework structure, first write the model layer according to the database table, then write the controller to which model layer to interact with data, and finally view layer to display data and implement front-end interaction.

3. Handwritten by myself. I usually first write the front-end page effects based on the design drawing or template, fabricate data, and implement all basic interactions. Then build a database and table, and manually add some fake data to the table. Finally, write the server program of the backend management system to realize the addition, deletion, modification and query of data and run through the business process. Finally, find a template for the backend management system and write the interface of the management system.

My suggestion is to just do what you think is reasonable. Blindly copying other people’s work will make you feel uncomfortable at work. The answers to this kind of question are usually similar for developers of the same level, but the answers for developers of different levels are vastly different. For example, I would pay more attention to demand analysis, repeated communication, and use an agile approach to consider how to implement the core as quickly and simply as possible. Once the business is delivered for the first time, it doesn’t matter how the code is actually written.

The only suggestion is: implement the page effect as late as possible. Gorgeous psd will inevitably bring heavy front-end tasks. The sooner you do it, the more difficult it will be to make subsequent modifications, because the artist is not the project manager. It is very likely that you spent a day implementing a page, but when people saw it, they said that the artist made a mistake. Here There is a problem with the process, and then you will find that changing it is more troublesome than deleting and redoing it, so it is best to run through the process first. Note: This suggestion does not mean that you should not consider the page effect at all. At least the basic layout must be there, but the text size, color, animation, and ajax are not important. Communicate with the customer in advance: I will let you use it as soon as possible, and we will slowly correct any problems that are not good-looking. If you don't inform the customer in advance, they may suspect that there is a problem with your ability, and then explaining it will be a cover-up, which will be difficult to handle.

I also used cms to build a website. But it always feels like it’s not smooth to use. So I decided to write it myself. Suppose it is your first time to work on a project alone. You will find that you will encounter problems along the way that are difficult to imagine, but you can learn a lot of knowledge.
1. If cms basically meets the needs of your corporate website, use cms.
2. If the enterprise website is relatively complex, you can choose a relevant framework. You can learn a lot of knowledge but reduce the workload relatively. If you do it, you'll find that it's much faster to develop the project again.
3. Pure handwriting is not recommended. Because building a website must consider the trade-off between time, money, and knowledge.
4. You think too much and too carefully. Development documents are the general direction and main functions. During the development process, many contents and problems that are not mentioned in the development documents will appear. You can first look for the front-end framework and the background framework. The rest is up to you.

First of all, one person is building a corporate website. Based on my project experience, I put forward the following points:

First of all, is your corporate website just for content publishing or does it have other operations?
Based on the above analysis, search Google or Baidu to find an open source CMS, Weibo system, light blog system, blog system, or e-commerce system, etc., as mentioned above.
Analyze whether the found frameworks meet the current needs, or most of them meet the current needs. Try to choose a PHP system that almost completely meets the current needs, and then start making modifications.
The modification includes several aspects, the front-end template and the back-end program. If you modify the front-end template, you can use the bootstrap front-end framework or the amazeui framework to build the front-end.
End the current corporate website construction and complete it.

Strictly speaking, your question is not a problem. The reason is that the length of your development depends on the different needs, the size of the project, and your own abilities. Wasn't there a popular saying before? "Our company is just short of a programmer~" Laymen always think that only one programmer is enough to build a website, but in fact if you want to achieve a good development effect, the minimum standard configuration is an art front-end and back-end (program ) Test Product Manager.
If the poster wants to develop the website alone, then your minimum business capabilities must be CSS, JS, and PHP. If you want to make it more beautiful, the aesthetics must also be good. This is a bit verbose. In fact, I often develop websites by myself, so I can share my thoughts with you.
1. You need to have a complete plan, specifically what the website is going to do, how many pages it needs, how to jump to the page, and a complete flow chart.

2. Once you have a plan, you can start construction. Choosing a framework that you are comfortable with can save you a lot of time. For example, I am used to agile development of CI.

3. The most critical and troublesome thing is to set the page. Although writing HTML is not difficult, I personally find it very tedious, especially the style adjustment. At this time, I suggest you try to look at more pages from similar websites. If possible, copy the structure and CSS styles and modify them yourself. This is also a good strategy.

4. When the page is almost complete, it’s time to consider interaction. Nowadays, js plug-ins are very abundant. If you don’t want to write js, you can use related plug-ins, which are simple and have cool effects.

5. When the project is almost in progress, I start to think about fixing the bugs. You also said that you are developing alone. Many problems are actually difficult to find with your own thinking. I suggest that the poster can fix the project Copy the URL to a technical exchange group or forum so that everyone can take a look and help you click on it, which can have good results.

Well, that’s pretty much it. Having said so much, I can refer to the small website I developed independently. If you think it is good, don’t be stingy and give it a star~

https://github.com/emocheng/social-networks